OIF Update on Transport SDN

John McDonough OIF Vice President

NEC America

Next Generation Optical Networking Congress22nd - 25th June 2015

Nice Acropolis

Agenda� Abstract� About the OIF� Why Does Transport Need SDN?� Challenges� Guidance to accelerate deployment� 2014 Global Transport SDN Demonstration Addressing the Challenge� Multi – Domain Carrier Transport SDN Framework� Components of SDN Transport� Goal: Seamless Interworking� Moving Transport SDN Forward - OIF Activities� Carrier Requirements on Transport Networks in SDN Architectures � General Requirements� Putting the Pieces Together� Summary1

Abstract� Recent proof-of-concept and prototype technology demonstrations

have shown progress in the evolution to commercial SDN deployment. Service providers, network element providers and software vendors are collaborating in standards bodies, industry foraand laboratories to identify and address technical and business challenges standing in the way of even early market adoption.

� In this session, the OIF reviews findings from its Global Transport SDN Prototype Demo and outline steps aimed at clearing the roadblocks to wide-scale transport SDN deployment.

2

About the OIF The Optical Internetworking Forum:• Represents an end-to-end ecosystem

membership base…• Focused on multi-layer and multi-

domain transport interoperability…• Positioned at the industry

crossroads…• Optimized for IA development and

interop testing…• Fills gaps, removes obstacles…• Accelerates market adoption and

ROI for new technologies…• Improves network efficiency, lowers

Opex/Capex for network operators…• Unlike any other forum or SDO

www.oiforum.com

3

Why Does Transport Need SDN?• Optical and transport networks continue to be difficult and expensive to

manage• Many manual processes• Very long provisioning times

• SDN and virtualization have the promise of: • Simplifying optical transport network control• Adding management flexibility • Allowing the rapid development of new service offerings by enabling

programmable control of optical transport networks• To improve optical networking operations cost and ROI by:

• Automating services provisioning and deployment• Improving network resource utilization

4

Challenges• Operational simplicity

• On-board new clients rapidly• Differentiated service delivery

• Automate resource allocation on the fly• Scalability

• Support X transactions per hour• Security

• Service isolation and authentication per client• Continuous Availability

• Disaster avoidance / recovery• Current transport business model

5

OIF is providing guidance to accelerate deployment by Addressing some Challenges

Network Orchestration

Controller Hierarchy

Multi-domain Architecture

SDN Framework SDN APIsService Request

Path Computation

Topology

� Providing carriers with essential tools in the Transport SDN toolkit

• How to apply SDN to a carrier’s multi-domain, multi-layer transport network

• Transport SDN API specifications to allow deployment of SDN applications

• Prototyping and testing of real implementations for experience and interoperability

2014 Global Transport SDN DemonstrationAddressing the Challenge

Multi-Domain Carrier Transport SDN Framework

� Application Layer• Business apps• Network apps• Orchestration

� Isolated from Controller

• Accesses Control layer via NorthBound Interface such as REST/JSON

Application Layer

Control Layer

Infrastructure LayerDomain 1

NE NE NE

Domain 2

NE NE NE

Domain 3

NE NE NE

Network Orchestrator

Parent Controller

DomainController

DomainController

DomainController

SBI

NBI

SBI

CloudOrchestrator

Compute Storage

SDN Reference Architecture Components of Transport SDN

Goal: Seamless Interworking

• Efficient, Agile Multi-layer, Multi-vendor, Multi-domain Carrier Networks

Domain CDomain A Domain B

NE

NENE

NENE NE NE

NE

NENE NENE

UNI E-NNI UNIE-NNIClient Client

Control plane

Transport plane

NM SDN

Domains can use Network Management, SDN or distributed control plane internally

Domains can use different technologies internally

No 1:1relation

Apps & Orchestration

app app app

10

General Requirements

• Requirements are not aimed at a particular set of protocols, HW and SW implementations

• Packet & circuit switching• Centralized & distributed control instances• Allow multiple protocols• Modular SW and HW (COTS)• Decoupling of network layers

• Guarantee interoperability among different vendor implementations, carrier network domains, data center functions, …

• Well defined interfaces for an increased level of interoperability

Moving Transport SDN ForwardOIF Activities

SDN Reference ArchitectureCarrier SDN RequirementsMeaningful demo and testing in carrier environment showing

• Status of technology• Interfaces and interoperability• Operation tools needed• Pertinent use cases

Framework for Transport SDN• Define framework• Identify open interfaces• SDN and ASON

• API implementation agreements• Joint work with ONF

• Virtual Transport Network Service definition

12

Now available!

Carrier Requirements on Transport Networks in SDN Architectures • Based on contributions of major

carriers worldwide• Comprises requirements on

Transport SDN• Orchestrator (transport network

relevant part)• Control and management

planes• Data plane

• Being used as guidance within OIF but also communicated to other SDO’s and forums

OIF Implementation Agreements

OIF Networking Interoperability Demonstrations

Putting the Pieces Together

UNI 1.0 signaling

UNI 1.0r2/ E-NNI 1.0 signaling

E-NNI 1.0routing

UNI 2.0 signaling

E-NNI 2.0 signaling

ASON/GMPLS Interworking

2001 2014

E-NNI 2.0 routing

SUPERCOMMDraft UNI 1.0

signaling

OFCDraft E-NNI 1.0

signaling + routing

SUPERCOMMDraft EPL over SONET/SDH +

EVPL data plane

ECOCEPL over

SONET/SDH + BW mod

WorldwideEVPL over transport + restoration

OFC-NFOECEthernet

services over OTNv3

2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013

Joint OIF-ONFCloud bursting over optical

networks

PCEE-NNI ML AM UNI2.0 Ext.

SUPERCOMMUNI/E-NNI 1.0 SONET/SDH +

EoS data plane

Summary

• SDN has great promise to improve transport control• Programmability• Simplified multi-layer control• Common behaviors in heterogeneous NE deployments• Application awareness

• OIF is providing guidance to accelerate deployment• Use cases and architecture• Carrier requirements• Framework document• Demonstrations• Implementation Agreements

Thank You!Would like to participate in these activities please contact the

below OIF website

www.oiforum.com