The OIF's Lyndon Ong discusses Essential Tools for Transport SDN Development at Layer123 SDN & NFV World Congress, October 15, 2015.

1. SDN Framework and API
Lyndon Ong
OIF MA&E Committee Co-Chair
Ciena
Layer123 SDN & NFV World Congress
Dusseldorf, Germany
October 15, 2015

2. Transport SDN Toolkit
Work in Progress
Essential tools for Transport SDN deployment
• How to apply SDN to a carrier’s multi-domain, multi-layer
transport network
• How to make SDN interoperable, high performance and
secure for carrier use
• How to operationalize SDN
Architecture
Identifiers
Framework
SCN APIs
Integration with MP
Interoperability demos
Security

3. OIF/ONF Global Transport SDN Demo
Where to go from here?
OIF/ONF Joint Prototype Demo in
Fall 2014 – reported last L123
World Congress
Multi-layer control
Multi-vendor, Multi-domain Demo
• 5 Carrier Labs
• 9 Vendors
OpenFlow Optical Transport
Extensions
Prototype NBI for Connectivity Service
and Topology
Whitepaper available with details

4. Moving Transport SDN Forward
OIF Framework for Transport SDN and Work in Progress
 SDN Reference Architecture
 Carrier SDN Requirements
 Meaningful demo and testing in carrier
environment
 Framework for Transport SDN
• http://www.oiforum.com/documents/frame
work-for-transport-sdn-components-and-
apis
4

5. Application
Layer
Control Layer
Infrastructure Layer
Domain 1
NE NE NE
Domain 2
NE NE NE
Domain 3
NE NE NE
Network
Orchestrator
Parent
Controller
Domain
Controller
Domain
Controller
Domain
Controller
SBI
NBI
SBI
Cloud
Orchestrator
Compute Storage
SDN Framework for Transport
Multi-Domain Integration
Transport SDN Demo
validated framework for
carriers
• Can be realized over WAN
and provide carrier benefits
• Highly flexible - multiple
technology layers, multiple
domains, greenfield and
brownfield
Lack of definition for how
user applications interact
with transport network
resource functions
• The programmability of
Transport SDN requires some
of the internal interfaces used
by ASON to become open

6. SDN Access to Network Control
NB Interfaces
 Standard APIs defined for interfaces to functional entities
 APIs for Call/Connection Control, Topology, Path Query, Virtualization
 Replace internal, proprietary interfaces
 Decoupling of functional blocks enables augmentation and/or replacement
 Important for delivering new network behaviors
Business
Application
Business
Application
Virtualization/Abstraction

7. API Divergence Problem
Absent Standards
Potential APIs
• Vendor-specific
• Controller-specific
• Technology-specific
• Language-specific
• SDO-specific
Need commonality
• Common core model
• Common minimal subset
• Plus extensions

8. Achieving Common APIs
The Tools and Remaining Challenges
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
 Getting to a common Information Model and API specification
 ONF Common Information Model project – aligns ONF, ITU, TMF, MEF,
OIF
 Verifying APIs provide the necessary functionality
 Use case review
 Refinement for transport network applications

9. OIF Transport API Project
Work in Progress
Progress standards for Transport APIs
Joint with ONF OpenTransport WG T-API Project
• Common, Standardized Transport API Specifications
• Functional Specification
• Information Model
• YANG Data Model/JSON Schema
 Draft documents made openly available via Open Source
(ONF “Snowmass” OpenTransport project)
 https://github.com/OpenNetworkingFoundation/ONFOpenTransp
ort
• Open Source Implementation project “Englewood”
OIF Demonstrations and Implementation Agreements to follow

10. Thank You!
www.oiforum.com
10