{"id":310,"date":"2013-03-25T05:59:32","date_gmt":"2013-03-25T02:59:32","guid":{"rendered":"https:\/\/opticstransport.com\/?p=310"},"modified":"2013-03-25T05:59:32","modified_gmt":"2013-03-25T02:59:32","slug":"naas-as-step-towards-sdn","status":"publish","type":"post","link":"https:\/\/telecomlighthouse.com\/blog\/naas-as-step-towards-sdn\/","title":{"rendered":"NaaS as step towards SDN"},"content":{"rendered":"<p>API is the most powerful feature of SDN- the programmable network. It will open a world of opportunities in terms of flexibilities and features for both operators and app developers. The current networks are rigid and make operators \u201clock in\u201d to vendors. SDN will help avoid this lock in by making a network a flexible platform which will respond as operators desire. This will reduce OPEX that comes because of manual provisioning of services and will help in bringing innovation because the operators may develop new applications easily and flexibly.<\/p>\n<p>SDN focuses on Network as a service or what is termed as \u201cNaaS\u201d in cloud computing. With Naas operators will have control over bandwidth, routing and QoS of their data. They will be able to give differentiated services. With SDN, operators can leverage the existing NaaS initiatives and build up their <a href=\"https:\/\/telecomlighthouse.com\/blog\/faq-about-software-defined-networking-sdn\/\">SDN infrastructure<\/a> from there. The knowledge and skills gained with NaaS today will be and prove very useful to develop SDN ecosystem of apps. The experience of these operators can help the new comers into SDN to learn from them.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>API is the most powerful feature of SDN- the programmable network. It will open a world of opportunities in terms of flexibilities and features for both operators and app developers. The current networks are rigid and make operators \u201clock in\u201d to vendors. SDN will help avoid this lock in by making a network a flexible [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-310","post","type-post","status-publish","format-standard","hentry","category-sdn"],"_links":{"self":[{"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/posts\/310","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/comments?post=310"}],"version-history":[{"count":0,"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/posts\/310\/revisions"}],"wp:attachment":[{"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/media?parent=310"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/categories?post=310"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/tags?post=310"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}