Downloaded 28 times
Uploaded byDeborah Porchivina
Next steps on Transport SDN - OIF Panel OFC 2015
This document discusses next steps for software-defined networking (SDN) in the transport domain. It proposes further prototyping and testing of a multi-domain, multi-layer SDN carrier framework to provide essential SDN tools for carriers. This includes developing transport SDN API specifications to allow SDN deployment across multiple technologies. Lessons from a previous joint OIF/ONF prototype demonstrated the potential to realize an SDN architecture for carriers across wide-area networks. The document outlines ongoing and future work items at OIF related to developing a transport SDN northbound interface and information model.
More Related Content
Similar to Next steps on Transport SDN - OIF Panel OFC 2015
Next steps on Transport SDN - OIF Panel OFC 2015
- 1. Next steps onTransport SDN Lyndon Ong Co-Chair, OIF MA&E Committee Ciena OFC 2015 Expo Theater II March 25
- 2. Carrier SDN Frameworkand Toolkit Prototype Testing OpenFlow Extensions Framework SDN SBI SDN NBI Service Request Path Computation Topology Providing carriers with essential tools in the Transport SDN toolbox • SDN Carrier Framework supporting multi-domain, multi- layer Transport SDN • Transport SDN API specifications to allow SDN deployment over multiple technologies • Further prototyping and testing of real implementations for experience and interoperability
- 3. SDN: an OpenNetwork Control Architecture Infrastructure Layer Control Layer Application Layer Business Applications NBI Controller Framework NBI NBI Network Services • Diverse applications • Planning, optimization, services, etc.Common APIsCommon APIs Standard InterfacesStandard Interfaces Open PlatformOpen Platform • Common framework • Multi‐vendor NW SW • Routing, Resiliency • Standard, programmatic interfaces across layers • Open/common device data models
- 4. Multi-Domain Carrier TransportSDN Framework Validated in the Joint OIF/ONF Prototype Demo in Fall 2014 Multi-vendor, Multi- domain Demo • 5 Carrier Labs • 9 Vendors Ethernet, L1 and L0 switching OpenFlow Optical Transport Extensions Simple Prototype NBI for Connectivity Service and Topology Whitepaper available with details 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
- 5. Takeaways from theOIF/ONF Demo Successful demonstration of SDN Architecture for carriers • Can be realized over WAN and provide carrier benefits • Highly Flexible • Multiple technology layers • Multiple domains • Greenfield and brownfield OpenFlow Optical Transport Extensions • No major interoperability problems identified, only minor notes • Now being approved as an ONF Technical Specification Transport NBI/API • Key area for multi-domain services • REST/JSON base advantages • Development time, flexibility, debugging • Need work on commonality, esp. Information Model
- 6. Moving Forward atOIF SDN Framework whitepaper Virtual Network Service definition Transport API work • Joint work with ONF Potential 2016 interop demonstration 5
- 7. SDN Framework Documents multi-domain/multi-layercarrier architecture Uses well-known ITU-T ASON architecture as a basis for identifying key application interfaces • Service Request, Connection, Topology and Path Computation APIs in particular 6 ASONCallControl ConnectionControl Directory Signaling PC Routing PCTAP LRM Discovery Agent RoutingControl Net TopologyPath Query SNC SNC + Reroute Service Level Business Application Business Application Virtualization/AbstractionASON Control Components* * Figure does not imply specific distribution of components, e.g., centralized or distributed
- 8. Virtual Network ServiceDefinition Take advantage of virtualization in SDN Offer customers controllable network slice 7 Leased Line VPN VNS 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 Renting P2P connections Leasing virtual network (connection) Leasing virtual network + connection control over the virtual network Similar to SCS (PVNS) Static Dynamic VNS Virtual network with vNE & vLink Client controller Rent virtual network resources from provider (SVNS) Client site Virtual network recursive creation Client site Client site Client site Client site Client siteClient site Leasing virtual network + recursive virtual network creation
- 9. SBI and NBIwork Completing Transport SDN Southbound Interface – ONF Follow-On OpenFlow Extensions • Autonomous Functions – programmability of local functions • Generation and processing of Performance Monitoring (bit errors or SNR) • Pre-programmed local protection functions to meet service requirements Northbound Interface – OIF API Project • Use ONF work aiming at commonality across platforms • Common Core Information Model across technologies • Mappable to REST/JSON interfaces • OIF Project to define API specs • Use joint OIF/ONF prototyping and testing, ideally with open source participation such as ONOS, ODL
- 10. Transport SDN NBI SDNNorthBound Interface • Common interface for controlling and analyzing networks • Service request interface • Connection interface • Topology interface • Path Computation interface • Flexible interface • Different levels of control • Potential abstraction • Virtual networks • Utilizes Common Information Model • Consistency rather than divergence Domain 1 NE NE NE User App Domain Controller Protect App Optimize App NBI
- 11. 2016 Demo Plans Projectingforward – 2016 likely demo timeframe Potential topics: • Standardized OpenFlow Optical extensions • Based on Technical Spec issued by ONF • Testing with Open Source Controllers • ODL, ONOS • Approved IAs for Transport APIs • Cooperative efforts by OIF and ONF • Based on Common Information Model work 10