OIF's Technical Committee Vice Chair Jonathan Sadler, Coriant explains the OIF"s Transport SDN interoperability goals to OFC2016 attendees

1. Transport SDN Interoperability Program
Jonathan Sadler, Coriant
Networking Interoperability WG

2. The Need
 Interoperability testing is needed to evaluate multi-vendor interop and
advance CP maturity
 Essential stepping-stone to move CP from research labs to live networks
 Initial exposure and feasibility demo, feedback into standards process
 Critical tool for early detection and correction of interoperability issues –
in specifications, vendor implementations and operations concepts
I-NNI
I-NNI
OIF
UNI
OIF
E-NNI
OIF
UNI
Vendor B
Vendor A
Vendor C
Vendor D
1

3. OIF Work Products
OIF Networking Interoperability Demonstrations
UNI 1.0
signaling
UNI 1.0r2/
E-NNI 1.0
signaling
E-NNI 1.0
routing
UNI 2.0
signaling
E-NNI 2.0
signaling
ASON/GMPLS
Interworking
20012002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014
E-NNI 2.0
routing
E-NNI 2.0
security
E-NNI 2.0
recovery
E-NNI 2.0
multilayer
E-NNI 2.0
OTNv3
Transport
SDN
Framework
SUPERCOMM
Draft UNI 1.0
signaling
OFC
Draft E-NNI 1.0
signaling +
routing
SUPERCOMM
UNI/E-NNI 1.0
SONET/SDH +
EoS data plane
SUPERCOMM
Draft EPL over
SONET/SDH +
EVPL data plane
ECOC
EPL over
SONET/SDH +
BW mod
Worldwide
EVPL over
transport +
restoration
OFC-NFOEC
Ethernet
services over
OTNv3
2015
L123
Global
Transport SDN
Prototype Demo
OIF Interop History
2

4. Historical standards process lifecycle
Interoperability issues not found until deployment
Ideas Project Specification
Implementation
Implementation
Deployment
3

5. Interoperability input is integrated from the start
The OIF Lifecycle
Ideas Project Specification
Implementation
Prototype
Experience
Early Interop
Experience
Implementation
Deployment
4

6. OIF Interop Goals
Facilitate learning from early prototyping
• Early implementations explore new approaches / technologies
• OIF 2005 Interop Event – Ethernet services over SDH
• Multi-layer model
• OIF 2014 Interop Event – Transport SDN NBIs
• APIs using REST JSON
• Experiences from early prototypes validate approaches
later used in OIF Implementation Agreements
Specifications based on experience are useful to industry
5

7. OIF Interop Goals
Enable service providers to
get early experience
• Held in Carrier labs worldwide
• HW and SW vendors
• Real optical switches
• Test interoperability of software
• Tests facilitated by Worldwide network connecting labs
• Enables pair-wise testing amongst all participants
• Validating use cases, approaches focuses work
• Vendors get direct feed back from service providers
Service provider observations feed spec development
6

8. OIF Interop Goals
Drive Specification clarity
• Interop Testing validates draft specifications
• Identify ambiguous text
• Find places specification text is incomplete
• When two implementations are found to not interop,
specification text is reviewed for areas to improve
• Findings document generated with recommendations
• Liaisons sent to other organizations involved in test
Interop Testing experiences refine specifications
7

9. What’s next?
Planning for next OIF/ONF Transport SDN test event
• Joint activity with ONF
• Significant interest from carriers, vendors
Potential test areas:
• Standardized OpenFlow Optical extensions
• Based on Technical Spec v1.1 to be issued by ONF
• Testing of work on Standard Transport API
• Based on ONF T-API Spec, Info Model, Data Models
• Refine options, naming/addressing, functionality for carriers
• SDN-based Services and Applications
• Packet/Optical Integration with real-time event handling
• NFV enablement with VTNS and other applications
Targeting late 2016 testing, early 2017 readout
8

10. THANK YOU
9