algiers, algeria, 8 september 2013 sdn and its standardization takashi egawa [email protected]...

Algiers, Algeria, 8 September 2013

SDN and its standardization

Takashi [email protected]

NEC CorporationITU-T Rapporteur, Q.14/13

ITU Workshop on “Standardization on IMT, M2M, IoT,

Cloud Computing and SDN”

(Algiers, Algeria, 8 September 2013)

mailto:[email protected]

Open interface is provided for network resourcesYou 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 ite.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

switches links storagesprocessors ….


Issues to make SDN effective (1)

The target of the interface; what to control/manage?Flow table in switches? (OpenFlow protocol’s 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 networksoftware architecture: various software invarious layers

Which interface?What function?What parameter?


Issues to make SDN effective (2)

Control plane and data plane should be separatedControl function should be logically centralized

4

Open interface must be easy to implement

ICTresource

OpenInterface

Control function

controller controller

ICTresource

ICTresource

ICTresource

ICTresource

Differentphysicalentity

Logically one entity

multiple controllerfor e.g., redundancy


Core concepts of SDN are very oldA 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 yearsIn telecom carrier networks,control = operater’s. data = customer’s. Some sort of separation is a MUST

5Algiers, Algeria, 8 September 2013

Time to revisit SDN concept

Virtualizationit is becoming popular, in particular in data-centers

OpenFlow protocolit destroyed ‘distribution = just’ illusion

CustomizationTraditional IP network is difficult to customize. But if possible, …

6

Technologies, requirements that makes SDN useful


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 ICTinfrastructure

Purpose Purpose Purpose

Highly secure,closed network

To make everything virtual is a long-time dream


Items that makes SDN useful (1): Virtualization (2)

Many ICT resources are becoming REALLY abundantCPU performance is still increasing, end-users don’t care it anymoreThe amount of memory and storage are still increasingAccess links are fast enough to be shared among multiple purposesGbps access is too much for email and simple web!

OK, let’s invent a way to use themIsolation and/or separation are a good way to achieve it --- we human love ‘territory’

Computing resources are already virtualized. Network’s turn

Data-centers created a market for virtualization. Time to expand the market by applying it to other areas


Items that makes SDN useful (2): OpenFlow protocol

OpenFlow protocol destroyed the myth of ‘distributed system is good’

It was a sort of religionOpenFlow-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, let’s use it.

If centralized is efficient, let’s use it.


Items that makes SDN useful (3): Customization

Customization is becoming even more importantMore customer, application, traffic are in the networksCustomized traffic engineering is really necessaryOpenFlow has shown the possibility

We may now able to realize service-aware networks


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 2013 11

Various activities discuss specific part of SDN

Collaboration among SDOs/open source activities critical. Joint Coordination Activity on SDN (JCA-SDN) establishedITU-T discuss overall architecture of carrier networks

12

Core transport

Network Services

Applications

Each cloud service

ONF

managem

en

t

TMF

IETFAccess

transport

Use

r Term

inal BBF

ETSINFV

Open Stack Cloud stackOpenDaylight

OSS

SDO

OIF

SG11, 13

Q.12/15


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 servicesDescribed in Y.3001, 3011 and othersiSCP (independent Scalable Control Plane, counterpart of IETF Forces) for control/data separationDescribed in Y.2621, 2622

The discussion on SDN itself has startedSDN Framework document is now under development A brief document that defines what is SDN from ITU viewpoint, and what ITU should doDiscussion to apply SDN to NICE started (Y.S-NICE-reqts)

SG11 is discussing SDN signalingSG15, 17 is interested in SDN


List of ITU-T SDN-related work itemsSG13

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/05Y.3011 (Framework of network virtualization for future networks): fin, 2011/09Y.FNvirtreq (Requirement of network virtualization for Future Networks): target 2013/11Y.SDN-FR (Framework of SDN): target 2013/11Y.FNsdn-fm (Requirements of formal specification and verification methods for software-defined networking): target 2014/07Y.Sup-SDNusecases (Supplement for use-cases of telecom SDN): target 2014/07Y.S-NICE-reqts (Requirements and capability framework for NICE implementation making usage of software-defined networking technologies): target 2014/09

SG11Q.SBAN (Scenarios and signaling requirements for software-defined BAN (SBAN)): target 2014/11Q.Supplement-SDN (Framework of signalling for SDN): target 2014/11Q.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 2013 14

SG13’s roadmap

Basic common part as ‘common SDN’Will discuss ITU-T specific SDN in various groups (Qs)

15

Use CasesQs/13

Common SDN

Gaps

Common SDN

ONF TMF IETF BBFETSINFV OIF

Collaboration and coordination

2013 2014 2015 ~ 2016

ITU-T SDN

Y.SDN -FRQ14/13

Functional requirements and architectures of common SDN

Q14/13

Functional architectures and mechanisms of ITU-T SDN

New1/13

SDN Interworking requirements and functionsQ11/13

Common capabilities (QoS , Security, Mobility) and mechanismsto support SDN

Q 6,8,9/13

Use of SDN into existing networks such as NGN -eQ2, 3/13

Functional requirements of ITU-T SDNQ14/13

Analysis of Regulatoryimplications of SDN and future networks

New2/13

Open stack, Cloud stack

Figure fromTD-18 (TSAG)


Conclusion

SDN enables you to define networks with softwareIf 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 basisNow emerging thanks to virtualization and others

Many SDOs are contributing to SDN in their areaITU-T will provide the total view for carrier networks

Collaboration will be provided through JCA-SDN

ITU-T SG13 and other SGs started discussionSDN framework Recommendation is the 1st target


algiers, algeria, 8 september 2013 sdn and its standardization takashi egawa [email protected]...

Documents

sdn algiers

sdn useful algiers

sdn standardization

sdn effective

sdn collaboration

sdn concept virtualization

redundancy algiers

networks open interface