Unlock the Benefits of Transport SDN OIF Transport SDN API Interop Demo

Size: px

Start display at page:

Download "Unlock the Benefits of Transport SDN OIF Transport SDN API Interop Demo"

Shawn Alexander
5 years ago
Views:

1 Unlock the Benefits of Transport SDN OIF Transport SDN API Interop Demo June 13 th, 2017 Optinet China Conference 2017 Junjie Li, China Telecom OIF Board Member

2 Agenda Motivation and Overview Key Findings Next Step Current OIF Works 2

About the OIF Network Operators System Suppliers Transceiver Suppliers Component Suppliers The Optical Internetworking Forum: Represents an end-to-end ecosystem membership base of 100+ members

3 About the OIF Network Operators System Suppliers Transceiver Suppliers Component Suppliers 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 G Enabling interoperability in optical transmission networks, to create an open ecosystem Implementation Agreements Large scale interoperability testing Certification 3

4 Optical Networks Transformation from closed networks Vendor-specific management systems OSS open SW to open networks OSS / Apps Open APIs SDN Control Infrastructure Proprietary OS Vendor X HW Proprietary OS Vendor Y HW Proprietary OS Vendor Z HW open HW Virtualized Multi-vendor Multidomain Network Proprietary, vendor-specific silos Complex to operate across vendors and technologies Interoperable networks Open APIs to OSS/Apps End to end orchestration Addressing optical control plane interoperability. 4

5 The OIF and Transport SDN Goal: accelerate commercial deployment by defining, testing and assuring interoperability of key network functions and interfaces Work to date: Use cases and reference architecture Carrier requirements and framework 2014 interop demo partnered with ONF, tested pre-standard ONF OpenFlow extensions and APIs, led to ONF T-API specs 2016: OIF SDN Transport API Interoperability Demo Validate specs in multi-layer, multi-domain environments in carrier labs Communicate findings whitepaper, read-out events, liaisons It s all about interoperability 5

6 OIF SDN Framework Service Requests Focus of 2016 Interop Event Control Components Service Management Service Request Topology Connection Management Path Query Topology Routing Control Directory Link Management Signaling Proto Dataplane Config Discovery Routing Proto Dataplane 6

7 2016 SDN Transport API Interoperability Demonstration Accelerating Momentum on the Road to Next-Generation Architectures Open Networking Foundation 7

8 2016 SDN T-API Interop Demo 8

9 Timeline Extensive preparation and testing ETSI NFV ONF Interim BCE OECC ONF Workday 3Q OIF ECOC 2016 L123 SDN 4Q OIF 1Q OIF MWC 2017 OFC May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Q16 OIF Tech Spec Start Contract/NDA Test start Test end Readouts Proposed and accepted as an ETSI NFV PoC by ETSI TST WG See Domain_Transport_SDN (Hiroshi Dempo, NEC, editor) 9

10 T-API modules tested Source: ONF TR

11 T-API modules tested (cont ) Topology Service Retrieve most basic data about controlled network Abstract view of devices and connections Connectivity Service Creation, List, Query, Retrieval, Deletion Multiple and programmable constraints Multi layers supported, ETH demoed Notification Service Autonomous notification from the network of significant events Notification has proven higher efficiency than periodical polling 11

12 2016 SDN T-API Worldwide Interop Topo 12

13 Use Cases Tested #1: ESTI-NFV POC Demo #2: Multi-Domain Service Provisioning #3: Low Latency L0 Path across Metro/Regional Data Centers #4: Variable Bandwidth Paths across Core 13

NFV POC Demo The target scope for Interop Network controller for the WAN Architectural model: Multi-layered Multi-vendor domains Network Controller Model

14 NFV POC Demo The target scope for Interop Network controller for the WAN Architectural model: Multi-layered Multi-vendor domains Network Controller Model Hierarchical: E2E/ Domain Network Controller NBI/ SBI: TAPI Network elements in the WAN Optical network Nodes Packet network Nodes ETSI GS NFV-MAN 001 V

15 Agenda Motivation and Overview Key Findings Next Step Current OIF Works 16

16 Demo Findings Transport API is a solution that enables SDN for Carriers Networks with an evolutionary approach. It automates and simplifies the operation of transport domains for L0, L1 and L2 services. Network topology information elements can be taken from the underlying network infrastructure configured by multiple vendors network equipment. T-API implementation deployed in a hierarchical SDN controllers tree enables real-time orchestration of on-demand connectivity setup, control and monitoring across diverse multi-layer, multi-domain, multi-vendor, networks. 17

17 Findings T-API T-API provides functions necessary for multi-domain orchestration Topology view Connection establishment Topology abstraction T-API localizes interoperability to Orchestrator/Controller interface GMPLS requires NEs in a sequence to have a consistent behavior in order to achieve interoperability T-API supports multiple technologies Ethernet OTN DWDM 18

18 Findings - GAPS Controllers abstract the network in different ways E.g. Unidirectional vs Bidirectional links Controllers provide/report different capabilities E.g. Connectivity restrictions Division of responsibility between controllers unclear E.g. Multi-domain Path Computation Maintaining RPC and REST styles is confusing Not all implementations supported both styles 19

19 Agenda Motivation and Overview Key Findings Next Step Current OIF Works 20

20 Next Steps T-API needs to be validated for additional use cases Use of topology interface for Path Computation Service Management interface T-API evolution is needed to meet current Transport Network uses Protected Services Generalized Notification Service Based on demo feedback, ONF will align T-API with YANG Best Practices Object ID format and lifecycle Separation of Configuration, Operational Data 21

21 Next Steps T-API 2.0 Based on demo feedback, further align T-API with YANG Best Practices Object ID format and lifecycle Separation of Configuration, Operational Data T-API functionality extended for additional use cases Path computation refinements, e.g., forwarding attributes, constraints Protected and Recoverable Services OAM, Generalized Notification and Telemetry Carrier Input to OIF: Help Bring T-API to the Market Interoperability Testing of TAPI 2.0 Implementations Potential Certification Planning 2018 Interop Test 22

22 Agenda Motivation and Overview Key Findings Next Step Current OIF Works 23

23 Current OIF Works CFP2-DCO and CFP8-ACO CEI-56G and CEI-112G FlexE 400G ZR OIF VTNS Specification OIF Certification Project 24

24 OIF UNI Certification Project From Testing to Certification Issue to be solved : Multi-vendor interoperability of the optical control plane is still missing from commercial products, although various demonstrations have proven it is feasible. Certification is a powerful tool to bridge the gap between technical standards and commercial implementations: it will provide a unique reference and a market advantage to compliant, interoperable products. In line with its mission is to enable global interoperability in optical transmission networks, OIF surveyed the market and decided to create a certification program for interoperable products starting with the Optical Control Plane UNI. 25

25 Technical White Paper and Executive Summary Paper Please download at Thank You!

OIF SDN Transport API NFV Proof of Concept. May 4, 2017 Layer 123 NFV World Congress Lyndon Ong, Ciena OIF MA&E Committee Co-Chair

OIF SDN Transport API NFV Proof of Concept May 4, 2017 Layer 123 NFV World Congress Lyndon Ong, Ciena (lyong@ciena.com) OIF MA&E Committee Co-Chair Agenda NFV/SDN Relationship Transport API OIF Transport