Nathan Tracy, OIF Technical Committee Chair and TE Connectivity was invited to speak at ECOC's Market Focus on OIF Interoperability – The Key to Unlocking the Benefits of SDN

1. OIF Interop – The Key to Unlocking
the Benefits of SDN
Nathan Tracy
OIF Technical Committee Chair
ECOC 2016
Market Focus
September 20, 2016

2. About the OIF
The Optical Internetworking Forum:
• Represents an end-to-end ecosystem
membership base of 100+ members
• Accelerating market adoption and
ROI for new technologies
• OIF 100G DWDM work united the industry
around a 100G framework and IAs for
photonics, FEC and module MSA
• Electrical work defines critical backplane,
chip and module interfaces for 100-400G
• Open and agile work plan
• Find gaps obstructing deployment and fill
them internally or working with other SDOs
• Distributed Control, Centralized Control –
whatever best fits operator needs!
www.oiforum.com
Network
Operators
System
Suppliers
Transceiver
Suppliers
Component
Suppliers

3. Transport Network Virtualization
• Network resources dynamically allocated for high utilization
• Resources can be partitioned into slices for service or user
• Control exposed through open interfaces
→ Proprietary, vendor-specific silos
→ Complex to operate, integrate across
vendors/technologies
→ Logically centralized, vendor-agnostic
control and service orchestration
→ Virtualization of physical network resources
OSS Platform
Proprietary OS
Vendor X HW
Proprietary OS
Vendor Y HW
Proprietary OS
Vendor Z HW
Current Networks Software-Defined Networks
OSS Platform/SDN Apps
Virtualized Multi-vendor Multi-
domain Network
SDN SW
SDN-enabled
HW
Open APIs
Vendor EMS
SDN Control Infrastructure

4. OIF’s Aim:
Transport SDN Toolkit
• Essential tools for Transport SDN deployment
• Address carrier operations environment
• Brownfield as well as Greenfield
• Enable differentiated services
• Speed service development through standard network APIs
• Deliver scalability, security and high performance
• Hierarchical structure with mix of local and central functions
APIs
Services
SDN Architecture for Transport
+ New program –
coming soon!
Interoperability testing

5. Working Protection
Request On Line
Real-time planning
Real-time setup
Autonomous Control
Dynamic expansion
Optimization
• Multi-level SLA
• Recovery
• Network migration
Seconds
Online
Network Slicing Goal
Real Time
Open APIs
Robust Data Plane
Physical Optical Network
Virtual Network Topology
Network as a Service
Online Slicing
Path Computation
Survivability Analysis
Global Optimization
Tenants
T-SDN
Controller

6. Virtual Transport Network Services
• Virtual networking service evolution
• Offering progressively greater control via APIs
• Reflected in OIF SDN work
Fixed
Connection
Dynamic
Connection
Dynamic
Connection
Client
site A
Client
site B
Client site A
Client site B
Client site D
Client site C
Client site A
Client site B
Client site D
Client site C
Virtual network
with vNE & vLink
Client
controller
Ctrl of
virtual XC
Connection controlled
by network providers
Leased Line
Endpoints Only
Fixed virtual
network topology
Static
Dynamic Dynamic
Connection
Virtual network
with vNE & vLink
Client
controller Rent virtual network
resources from provider
Client site
Virtual network
recursive creation
Client site
Client site
Client site
Client site
Client siteClient site
Dynamic/recursive virtual
network topology

7. Achieving Interoperability
Challenges for Developing Common APIs
Existing Tools
• Current API work is being done in fragmented silos
• Some linkage of APIs to existing protocol environments
Keys to achieving interoperable common APIs
• Define standard model across vendors and technologies
• Common Information model is key to interoperability
• ONF has led a Common Information Model project – aligning
ONF, ITU-T, TMF, MEF, OIF modeling
• Verify APIs provide the necessary functionality
• Use case review and convergent SDO work
• Prototype, Demonstrate, Test Code!

8. OIF Interoperability Demonstration &Testing
2014 OIF Transport SDN Demonstration
• OIF/ONF Interop Demonstration
• 5 carriers worldwide
• Multiple HW and SW vendors
• Equipment in carrier labs
• Optical and Ethernet switch
domains
• Some testing of OpenFlow
optical extensions
• Multi-domain network
• Prototype common API
provides access to domains
• Higher level orchestration
across domains
2014 Demonstration

9. Application
Layer
Control Layer
Infrastructure Layer
Domain 1
NE NE NE
Domain 2
NE NE NE
Domain 3
NE NE NE
Network
Orchestrator
Domain
Controller
Domain
Controller
Domain
Controller
SBI
NBI
SBI
Cloud
Orchestrator
Compute Storage
NBI
Multi-Domain Framework for Testing
Transport SDN
framework for carrier
networks
• Can be realized over
diverse carrier networks
• multiple technology
layers
• multiple domains with
differing SBI
• greenfield and
brownfield
• Need for standards on
application layer
interface to control
layer (NBI)

10. ONF Transport API Standards
Network Resources
SDN Controller
NENESDN Controller
NENEApplication
Transport
API
SBIs (e.g. Openflow,
vendor-specific)
NE NE NE
NE
NE
NE NE
NE NENENE
NE
NE
NENE
NE
Topology
Service
Connectivity
Service
Path
Computation
Service
Shared Network Information Context
Virtual
Network
Service
Notification
Service
NBI from SDN Controller to Application • ONF Standards Project closely
coordinated with OIF work
• Interface to a Transport Network
Controller allowing access to
Topology, Connectivity,
Virtualization and other services
• Functional Requirements
published as TR-527 (see
https://www.opennetworking.or
g/images/stories/downloads/sd
n-resources/technical-
reports/TR-
527_TAPI_Functional_Requireme
nts.pdf)
• UML/YANG/JSON models in
draft (see
https://github.com/OpenNetwor
kingFoundation/ONFOpenTrans
port )

11. OIF 2016 SDN T-API Interop Demo
What and Who:
• OIF is managing the demo, partnering with ONF on technical work
• Open to OIF and ONF members as well as non-members
• Carriers: China Telecom, China Unicom, SK Telecom, Telefonica, Verizon
• System vendors: ADVA, Ciena, Coriant, Fiberhome, Huawei Technologies Co., Ltd.,
Infinera, Juniper, NEC Corporation, Sedona, SM Optics, ZTE
Why:
• Help enable wide scale deployment of commercial SDN by testing the recently
approved ONF Transport Application Programming Interface (T-API)
• The interoperability test and demonstration will address multi-layer and multi-domain
environments in global carrier labs
• Builds on 2014 demo which was based on prototype T-APIs and helped advance
transport SDN standardization
• Additional use cases based upon the API standards will be clarified during the testing
and defined through OIF implementation agreements to provide a common set of
requirements
When, Where, How:
• August-Sept: Technical spec development
• October-November: Carrier-hosted lab testing
• 1Q17: Demo read-out events and white paper

12. Next Steps
• Interoperability is technically feasible, as demonstrated in labs, but
still missing from commercial products
• The OIF will help carriers unlock the benefits of SDN for their optical
networks through three interrelated programs:
• Interop demonstrations hosted by participating operators leveraging key
interfaces such as the Transport API to bind together multi-layer and
multi-domain carrier networks;
• Implementation Agreements that document the use of industry
standards;
• Coming soon - a new program to address the gap between paper
specification or early implementation and products that carriers can
deploy.
• The new program, along with well established and successful interop
testing and IA process, will help realize commercial transport SDN
deployment and the promised benefits of accelerated time-to-
revenue coupled with increased operational efficiency

13. Thank You!
www.oiforum.com