Algiers, Algeria, 8 September 2013 SDN and its standardization Takashi Egawa NEC Corporation ITU-T Rapporteur, Q.14/13 ITU Workshop on Standardization on IMT, M2M, IoT, Cloud Computing and SDN (Algiers, Algeria, 8 September 2013)

Open interface is provided for network resources You define how switches and others behave e.g., if packet header field xxx matches xxx, the packet is forwarded (switch), or discarded (proprietary firewall) e.g., an application notifies your program security breach is found. Your program disable a link (port) to isolate it e.g., your processor (virtual machine) notices … Commands to provision, control, manage Software-Defined Networking (SDN) 2 Your program (software) defines networks Open Interface Your program (software) ICT resources switcheslinksstoragesprocessors …. Algiers, Algeria, 8 September 2013

Issues to make SDN effective (1) The target of the interface; what to control/manage? Flow table in switches? (OpenFlow protocols approach) Routing table in routers? Controller itself? Resource abstraction: how they should be modeled? e.g., resources provided at controller level: link: node A to B? information flow pipe to end-users living in Tokyo? … 3 Open interface must be easy to understand & use Typical network software architecture: various software in various layers Which interface? What function? What parameter? Algiers, Algeria, 8 September 2013

Issues to make SDN effective (2) Control plane and data plane should be separated Control function should be logically centralized 4 Open interface must be easy to implement ICT resource Open Interface Control function controller ICT resource Different physical entity Logically one entity multiple controller for e.g., redundancy Algiers, Algeria, 8 September 2013

Core concepts of SDN are very old A textbook written in 80s discussed software definable network at concept-level, such idea always existed Virtually all equipment of today has open interface (I/F) Huge number of control I/F and management I/F has been developed, standardized, and used Programs has been using these I/F, and automating operations C/D separation has been common in telco for many years In telecom carrier networks, control = operaters. data = customers. Some sort of separation is a MUST 5 Algiers, Algeria, 8 September 2013

Time to revisit SDN concept Virtualization it is becoming popular, in particular in data- centers OpenFlow protocol it destroyed distribution = just illusion Customization Traditional IP network is difficult to customize. But if possible, … 6 Technologies, requirements that makes SDN useful Algiers, Algeria, 8 September 2013

Items that makes SDN useful (1): Virtualization (1) If we could make a pool of network resources and realize everything as its instances… (servers, firewalls, all appliances are specialized computers. If you can ignore performance, non-specialized computers can become anything) Then we are free from hardware restrictions! all difficulties will go to complicated system|software architecture, and its management 7 Abundant computers, enormous processing power, ubiquitous links, switches, abundant storages, … are shared among purposes/customers… Temporary, local ICT system Global ICT infrastructure Purpose Highly secure, closed network To make everything virtual is a long-time dream Algiers, Algeria, 8 September 2013

Items that makes SDN useful (1): Virtualization (2) Many ICT resources are becoming REALLY abundant CPU performance is still increasing, end-users dont care it anymore The amount of memory and storage are still increasing Access links are fast enough to be shared among multiple purposes Gbps access is too much for and simple web! OK, lets invent a way to use them Isolation and/or separation are a good way to achieve it --- we human love territory Computing resources are already virtualized. Networks turn Data-centers created a market for virtualization. Time to expand the market by applying it to other areas 8 Algiers, Algeria, 8 September 2013

Items that makes SDN useful (2): OpenFlow protocol OpenFlow protocol destroyed the myth of distributed system is good It was a sort of religion OpenFlow-based system showed centralized system is sometimes very efficient and fast Now we are free! Good time to re-visit fundamental telco network architecture If distributed is preferable, lets use it. If centralized is efficient, lets use it. 9 Algiers, Algeria, 8 September 2013

Items that makes SDN useful (3): Customization Customization is becoming even more important More customer, application, traffic are in the networks Customized traffic engineering is really necessary OpenFlow has shown the possibility We may now able to realize service-aware networks 10 Algiers, Algeria, 8 September 2013

In SDN, there are so many different voices. ITU is now trying to capture the essence, and started SDN standardization for telecom carriers Algiers, Algeria, 8 September

Various activities discuss specific part of SDN Collaboration among SDOs/open source activities critical. Joint Coordination Activity on SDN (JCA-SDN) established ITU-T discuss overall architecture of carrier networks 12 Core transport Network Services Applications Each cloud service ONF management TMF IETF Access transport User Terminal BBF ETSI NFV Open Stack Cloud stack OpenDaylight OSS SDO OIF SG11, 13 Q.12/15 Algiers, Algeria, 8 September 2013

SDN related activity in ITU-T SG13 and other SGs In SG13, SDN, network virtualization, iSCP had been discussed Future Networks uses SDN and network virtualization as technologies to combat ever-increasing services Described in Y.3001, 3011 and others iSCP (independent Scalable Control Plane, counterpart of IETF Forces) for control/data separation Described in Y.2621, 2622 The discussion on SDN itself has started SDN Framework document is now under development A brief document that defines what is SDN from ITU viewpoint, and what ITU should do Discussion to apply SDN to NICE started (Y.S-NICE-reqts) SG11 is discussing SDN signaling SG15, 17 is interested in SDN 13 Algiers, Algeria, 8 September 2013

List of ITU-T SDN-related work items SG13 Y.2621 (Requirements of independent Scalable Control Plane (iSCP) in FPBN) Y.2622 (Architecture of an independent scalable control plane in future packet based networks) Y.3001 (Future networks: Objectives and design goals): fin, 2011/05 Y.3011 (Framework of network virtualization for future networks): fin, 2011/09 Y.FNvirtreq (Requirement of network virtualization for Future Networks): target 2013/11 Y.SDN-FR (Framework of SDN): target 2013/11 Y.FNsdn-fm (Requirements of formal specification and verification methods for software- defined networking): target 2014/07 Y.Sup-SDNusecases (Supplement for use-cases of telecom SDN): target 2014/07 Y.S-NICE-reqts (Requirements and capability framework for NICE implementation making usage of software-defined networking technologies): target 2014/09 SG11 Q.SBAN (Scenarios and signaling requirements for software-defined BAN (SBAN)): target 2014/11 Q.Supplement-SDN (Framework of signalling for SDN): target 2014/11 Q.IPv6UIP (Scenarios and signalling requirements of unified intelligent programmable interface for IPv6): target 2014/12 Discussions exists at SG15 Q.12, and SG17 Algiers, Algeria, 8 September

SG13s roadmap Basic common part as common SDN Will discuss ITU-T specific SDN in various groups (Qs) 15 Figure from TD-18 (TSAG) Algiers, Algeria, 8 September 2013

Conclusion SDN enables you to define networks with software If you write programs, you have enormous freedom Many issues remains to make good open programming I/F Where should be the I/F? What resource model? … SDN has historical basis Now emerging thanks to virtualization and others Many SDOs are contributing to SDN in their area ITU-T will provide the total view for carrier networks Collaboration will be provided through JCA-SDN ITU-T SG13 and other SGs started discussion SDN framework Recommendation is the 1 st target 16 Algiers, Algeria, 8 September 2013