Your SlideShare is downloading. ×
Transport SDN @ OIF
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Transport SDN @ OIF

288
views

Published on

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
288
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
27
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Transport SDN @ OIF Hans-Martin Foisel Deutsche Telekom OIF Carrier WG Chair Member of OIF-BoDMember of OIF BoD May 29, 2014
  • 2. OutlineOutline • Transport SDN Trends and Business Drivers• Transport SDN – Trends and Business Drivers • OIF Role and StructureOIF Role and Structure • Transport SDN Architecture & Requirements • Goal of the OIF Transport SDN Framework Document • ONF-OIF Transport SDN Prototype Demonstration 2014 • Summary
  • 3. TrendsTrends C i i t h l d d h d• Carrier environment has evolved and changed • All IP services • Changing traffic patternsg g p • Need for new business models • Network standardization environment has changed and there i i i h iis increasing emphasis on • Virtualized environment • Separation of HW and SW • Separation of transport and control functions • Software implementation of network functions • Standard (COTS) hardware• Standard (COTS) hardware • Application aware routing • Programmable optical networks • New forums – ONF, NFV, OGF, OpenDaylight, … • SDN – an approach for optimizing networking
  • 4. Business DriversBusiness Drivers I d i il bilit (I d ili• Improved service availability (Improved resilience and reliability) • Simplified operations and decreased OPEX (Increased network automation programmability(Increased network automation, programmability and flexibility) • Faster service provisioning for accelerated time-to- market/revenue and ROI improved QoS/QoEmarket/revenue and ROI, improved QoS/QoE • Application aware networking• Application aware networking
  • 5. Orchestration - One main Aspect of SDNOrchestration One main Aspect of SDN Processing Storage T t g Transport
  • 6. What is the OIF?What is the OIF? Si 1998 OIF h b ht t th i d t f th• Since 1998 OIF has brought together industry groups from the data and optical worlds • Mission: To foster the development and deployment of interoperable products and services for data switching and routing using optical networking technologiesrouting using optical networking technologies • Our 100+ member companies represent the entire industryOur 100 member companies represent the entire industry ecosystem: • Carriers and network users C t d t d• Component and systems vendors • Testing and software companies
  • 7. Where we fit IETF ASON A hit t & ITU-T InteropInterop TestingTesting GMPLS Protocols ASON Architecture & Requirements IEEE OTN/Optical Interfaces 100G Interfaces ONF Ethernet Alliance 100G Interfaces ONF NFV Transport SDN CP management ImplementationImplementation AgreementsAgreements Infiniband Trade Assn 100G Interfaces Common NFV TMF Ethernet Services Trade Assn Fibre Channel T11 Electrical Interfaces MEF
  • 8. How OIF is organizedHow OIF is organized *Carrier WG *PLUG Ph i l L U G*PLUG: Physical Layer User Group
  • 9. Transport SDN Use CasesTransport SDN Use Cases • Internal working document – not for publication• Internal working document – not for publication • Used to distill carrier requirements for Transport SDN • Examples:Examples: • DC-DC Interconnect • BoD • TaaS • Multi-layer NM t k l d b l i• Network aware server load balancing • Cloud Box • PoD for Hybrid Cloud IaaS/STaaS• PoD for Hybrid Cloud IaaS/STaaS • Bandwith Exchanges • Virtualized IMS • Workload Migration
  • 10. Carrier Requirements on T t N t k i SDN A hit tTransport Networks in SDN Architectures Requirements on Transport SDNRequirements on Transport SDN • Document is based on contributions of major carriers worldwidecarriers worldwide • Comprises requirements on Transport SDN • Orchestrator (transport network relevant part) • Control and management planes • Data plane • Being used as guidance within OIF but alsog g communicated to other SDO and forums
  • 11. SDN Reference Architecture C t f T t SDNComponents of Transport SDN Service Service Service Orchestrator Application PlaneSDN northbound: OGF NSI, … Orchestrator Mgt- & C t l OF, MTOSI, REST, … DC Mgt/ Controller Control- PlaneTN Controller T t TN Controller Mgt TN Controller MgtDC Mgt/ Controller DC Mgt/ Controller Transport Network SDN southbound: OF, XML, SNMP, PCEP, … (could be NE-internal) Data Plane Data Center Transport
  • 12. SDN Architecture - StandardizationSDN Architecture Standardization ONFITU-T, IETF, OIF ASON / GMPLS OpenFlow Switch Spec. 1.4.0 OF Config. & Mgt Protocol 1.1 ASON / GMPLS (G.8080 / G.771x,…) MPMP –– CLI/GUICLI/GUIMPMP –– EMS/NMSEMS/NMS OFOF –– ControllerControllerControl PlaneControl Plane OF Packet SwitchesL1/L2 Transport NEs
  • 13. General RequirementsGeneral Requirements • Requirements are not aimed at a particular (set) of• Requirements are not aimed at a particular (set) of protocols, HW and SW implementations • Packet & circuit switching• Packet & circuit switching • Centralized & distributed control instances Allow multiple protocols• Allow multiple protocols • Modular SW and HW (COTS) D li f t k l• Decoupling of network layers • Guarantee interoperability among different vendor implementations carrier network domains data centerimplementations, carrier network domains, data center functions, … • Well defined interfaces for increasing level of• Well defined interfaces for increasing level of interoperability www.oiforum.com
  • 14. SDN Framework DocumentSDN Framework Document • TN Controller Decomposition • How does ASON Architecture S iS iS i apply to TN Controllers? • What components exist with a ll ? Orchestrator ServiceServiceService controller? • What APIs need to be exposed by a controller? TN Controller by a controller? • How can component replacement be facilitated?replacement be facilitated?
  • 15. SDN Framework DocumentSDN Framework Document • TN Controller Decomposition • How does ASON Architecture S iS iS i apply to TN Controllers? • What components exist with a ll ? Orchestrator ServiceServiceService OF CVNI OGF NSI controller? • What APIs need to be exposed by a controller? TN Controller CVNI SNC Service Level Reroute Abstract Network ASON Call Control by a controller? • How can component replacement be facilitated?Connect Path Computation Di t PCEPCEConnConn ReqReq replacement be facilitated? Control Directory LRM TopologyOIF ENNI OIF ENNI TopoTopo ControllerRSVP OSPFTAP OF CDPI
  • 16. Putting the Pieces Together OIF Implementation Agreements and Interoperability Demos OIF Implementation Agreements OIF Implementation Agreements and Interoperability Demos OIF Implementation Agreements UNI 1.0 i li UNI 1.0r2/ E-NNI 1 0 E-NNI 1.0 routing UNI 2.0 signaling E-NNI 2.0 signaling ASON/GMPLS Interworking E-NNI 2.0 routing PCE E-NNI ML AM UNI2 0 Extsignaling E-NNI 1.0 signaling routing signaling signalingInterworking 2001 2014 routing 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 UNI2.0 Ext. 2001 2014 SUPERCOMM OFC ECOC Worldwide OFC-NFOEC 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 SUPERCOMM Joint ONF-OIFSUPERCOMM Draft UNI 1.0 signaling OFC Draft E-NNI 1.0 signaling + routing ECOC EPL over SONET/SDH + BW mod Worldwide EVPL over transport + restoration OFC NFOEC Ethernet services over OTNv3 SUPERCOMM UNI/E-NNI 1.0 SONET/SDH + EoS data plane Joint ONF OIF Cloud bursting over optical networks SUPERCOMM Draft EPL over SONET/SDH + EVPL data plane OIF Networking Interoperability Demonstrations
  • 17. Joint OIF/ONF P t t D t ti 2014Prototype Demonstration 2014 • Application: Cloud Bursting over optical networks • Short lived, high-capacity between Data-centers • Implemented using OTN connections created via central interface • Ethernet service over OTN as the dataplane • Protocol Features: Subset OT WG Extensions (ONF Lead) • CDPI and/or CVNI – level of interoperability tbd • Experimental encoding of extensions • Potential additional features: Controller NBIs (OIF Lead) • Multi-domain (E/W or Controller hierarchy) • Network application interfaces (PCE, Topology)
  • 18. Vision: Inter-Domain Interworking • On-demand services are provisioned, based on ASON/GMPLS control plane f nctions: M lti domain M lti la er M lti Vision: Inter Domain Interworking control plane functions: Multi-domain, Multi-layer, Multi- technology • OIF control plane follows ASON multi-domain architecturep and allows UNI, E-NNI protocol separate from domain operation • Interworking with SDN domains is ensured D i CDomain A D i B Interworking with SDN domains is ensured Domains can use different control technologies internally: NMS, OF, PCE, ASON/GMPLS Domain CDomain A Domain B UNI E-NNI UNIE-NNI Client Client NM SDNClient Layer Topology NE NE Domains can use different data plane technologies internally p gy Server NE NE NE NE NE NE NE NE NE NE NENE Layer Topology
  • 19. SummarySummary • SDN has great promise to improve transport control• SDN has great promise to improve transport control • Programmability • Ability to deliver new behaviors not (yet) considered byAbility to deliver new behaviors not (yet) considered by standards, vendors, … • Simplified multi-layer control • Common behaviors in heterogeneous NE deployments • Application awareness • OIF is providing guidance to accelerate deployment • Use cases and architecture • Carrier requirements • Framework document • Demonstrations
  • 20. Thank you for your kind attention! www.oiforum.com

×