Karl Gass OIF PLL Vice Chair - Optical Track NGON 2016 July 1, 2016

Size: px

Start display at page:

Download "Karl Gass OIF PLL Vice Chair - Optical Track NGON 2016 July 1, 2016"

Meghan Ray
6 years ago
Views:

1 TRANSPORT SDN & NFV WHAT DOES IT MEAN FOR OPTICAL TWORKING? Karl Gass OIF PLL Vice Chair - Optical Track NGON 2016 July 1, 2016

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

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 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 Open and agile workplan Find gaps obstructing deployment and fill them internally or working with other SDOs Distributed Control, Centralized Control whatever best fits operator needs!

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

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 SDN Architecture for Transport Services APIs Carrier Requirements Interoperability demos

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

Developing an IA for Virtual Transport Network Services Virtual networking service evolution Each service type offers greater control Dynamic Dynamic Connection Fixed Connection Client site A Static

6 Developing an IA for Virtual Transport Network Services Virtual networking service evolution Each service type offers greater control Dynamic Dynamic Connection Fixed Connection Client site A Static Client site B A B Dynamic Connection Connection controlled by network providers D C Endpoints Only A B Dynamic Connection Client controller Ctrl of virtual XC D C Virtual network with v & vlink Fixed virtual network topology Virtual network recursive creation Client controller Rent virtual network resources from provider Virtual network with v & vlink Dynamic/recursive virtual network topology Leased Line

7 OIF Service Definition IA Service Attributes Service Capabilities Recovery Requirements OAM Requirements Harmonize Services Definitions for all players, i.e. Transport Network Services - Providers - Users - Equipment/SW Vendors

Enabling Multi-Domain Transport SDN Domain 1 Compute Transport API Domain Controller SBI Cloud Orchestrator Network Orchestrator Domain Controller Domain 2 SBI Application Layer Storage Transport API

8 Enabling Multi-Domain Transport SDN Domain 1 Compute Transport API Domain Controller SBI Cloud Orchestrator Network Orchestrator Domain Controller Domain 2 SBI Application Layer Storage Transport API Control Layer Domain Controller Domain 3 Infrastructure Layer 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 (Transport API)

9 Existing Tools Achieving Common APIs The Tools and Remaining Challenges 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 Common Information Model project aligning ONF, ITU, TMF, MEF, OIF Verify APIs provide the necessary functionality Use case review and convergent SDO work Prototype, Demonstrate, Open Source Code!

2014 Demonstration Implementation Experience OIF/ONF Interop Demonstration 5 carriers worldwide Multiple HW and SW vendors Equipment in carrier labs Optical and Ethernet switch

10 2014 Demonstration Implementation Experience 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

11 NBI from SDN Controller to Application ONF Transport API Standards Topology Service SDN Controller Application Connectivity Service Transport API SBIs (e.g. Openflow, vendor-specific) Path Computation Service SDN Controller Virtual Network Service Shared Network Information Context Notification Service 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 /stories/downloads/sdn- resources/technical-reports/tr- 527_TAPI_Functional_Requirements.pdf) UML/YANG/JSON models in draft (see dation/onfopentransport ) Network Resources 11

12 2016 Global Transport SDN/NFV Demo In Development OIF-managed, co-op with ONF/others Carrier hosted (OIF and ONF carriers worldwide) Leading vendors bringing real optical switching systems Testing timeframe Fall 2016 Target Test Area: Standardized Transport API for Multi-Domain SDN Based on ONF T-API Spec, Info Model, Data Models Refine options, naming/addressing, functionality for carriers Potential SDN-based Demonstration Applications: Packet/Optical Integration NFV enablement using Transport SDN Last call to join! Keep posted for future results!

13 Thank You!

Nathan Tracy OIF Technical Committee Chair ECOC 2016 Market Focus September 20, 2016

OIF Interop The Key to Unlocking the Benefits of SDN Nathan Tracy OIF Technical Committee Chair ECOC 2016 Market Focus September 20, 2016 About the OIF Network Operators System Suppliers Transceiver Suppliers