1 / 21

SDN Standardization in ONF: ONF Structure, OpenFlow Spec & ONF’s SDN Architecture

ITU Workshop on Software Defined Networking (SDN) Standardization Landscape (Geneva, Switzerland, 4 June 2013). SDN Standardization in ONF: ONF Structure, OpenFlow Spec & ONF’s SDN Architecture. Fabian Schneider (NEC Laboratories Europe), Vice-chair Architecture WG, ONF

lea
Download Presentation

SDN Standardization in ONF: ONF Structure, OpenFlow Spec & ONF’s SDN Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. ITU Workshop on Software Defined Networking (SDN)Standardization Landscape (Geneva, Switzerland, 4 June 2013) SDN Standardization in ONF:ONF Structure, OpenFlow Spec & ONF’s SDN Architecture Fabian Schneider (NEC Laboratories Europe), Vice-chair Architecture WG, ONF fabian.schneider@neclab.eu Geneva, Switzerland, 4 June 2013

  2. ONF: What and Why • ONF owns OpenFlow spec standardization • Mission: Dedicated to the promotion and adoption of SDN for the benefit of users • ONF’s view on SDN: • Physical separation of forwarding and control • Simplification of networking devices • ONF is not only “yet another SDO” • Too many SDOs are vendor-driven • Disruptive tech won’t evolve from legacy SDO • Being an SDO is not enough to achieve mission Geneva, Switzerland, 4 June 2013

  3. OpenFlow approach in a Nutshell Apps Control Plane Network Apps Custom Control Plane Data Plane Custom Silicon The OpenFlow protocol provides a standardized protocol to separate control/ management plane from data plane Rules (Match/Action tuples) Support for quick & dynamic networkconfiguration OF 1.0 – OF 1.3.2,OF-Config 1.1.1 Geneva, Switzerland, 4 June 2013

  4. OpenFlow protocols & SDN Applications • SDN is much more than just OpenFlow protocols • Whole eco-system: • SDN Apps • Network OS • Network Elements • Interfaces in between Control Plane API API API API Network Operating System Data Plane SDN Switch/Network Element Geneva, Switzerland, 4 June 2013

  5. Self-perception, Governance, Structure, Membership ONF Overview Geneva, Switzerland, 4 June 2013

  6. ONF’s self-perception Promote SDN as a whole – its commercialization – for users Standardize what needs to be standardized by a committee Believe in OpenFlow protocols as the Southbound API standard Advocate of experimentation, coding, open-source Geneva, Switzerland, 4 June 2013

  7. ONF Governance • Board of Directors: Users, not vendors • Executive Director (employee) • Reports to Board; vendor-neutral • TAG: ONF’s CTO function • Working Groups • Chartered by Board • Chaired by Board appointee • CoC coordinatesbetween different WGs Geneva, Switzerland, 4 June 2013

  8. Current ONF Structure & WGs Board of Directors Executive Director(Dan Pitt) Technical Advisory Group (TAG) Council of Chairs (CoC) Arch & Frame-work Config & Manage-ment Exten-sibility Fwd’ingAbstrac-tions Migration Optical Transport Testing & Interop Market Edu-cation Geneva, Switzerland, 4 June 2013

  9. ONF member statistics • OpenFlow industry acceptance • 22 users • 70+ products, 30M+ ports • Incumbent support for OpenFlow spec • Board: 8 companies & 2 Professors • 96 Members • operators, service providers, vendors, chip makers; both incumbent & startups Geneva, Switzerland, 4 June 2013

  10. Current work items, Peak into Architecture ONF AcTIVITIES Geneva, Switzerland, 4 June 2013

  11. Current Activity • Build out the OpenFlow substrate • Optical, Wireless/Mobile, Security, OAM • Plug-fests and Conformance testing • Develop ONF’s SDN Architecture • Support services above OpenFlow protocol • Northbound interface study • Hooks for NFV • How to migrate from legacy networks • Foster Chipset/HW Ecosystem Geneva, Switzerland, 4 June 2013

  12. Peak into ONF’s SDN Architecture Geneva, Switzerland, 4 June 2013

  13. Three Critical Properties of ONF’s SDN Architecture • Apps are network aware: SDN-enabled Apps • Communicate their requirements/polices to the network • Can monitor network state and adapt accordingly • Logically centralized NW: SDN Network Controller • Controller translates from app req’s to low-level rules • Controller summarizes the network state for apps • Well-understood driver-like model for devices: SDN Datapath • Programmatic low-level control of all Fwding and config • API for capabilities advertisement and publishing stats • No resource contention with other entities • Controller “owns” this device, subject to capabilities advertisement* Geneva, Switzerland, 4 June 2013

  14. ONF Collaborations & LIAISONs Geneva, Switzerland, 4 June 2013

  15. Strategic ONF Collaborations Geneva, Switzerland, 4 June 2013

  16. Established ONF Liaisons Geneva, Switzerland, 4 June 2013

  17. Conclusions and Recommendations • SDN: the future of networking • open, programmable, vendor-neutral, standards where it needs to be • Industry: broad acceptance of OpenFlow and investment everywhere • ONF: driving the global commercialization of open, standards-based SDN • Try to avoid duplication of work across SDOs More info @ www.opennetworking.org

  18. Backup slides following … Questions?

  19. 96 Members, the IT/Net Spectrum • SK Telecom • Spirent • Sunbay AG • Swisscom • Tail-f Systems • Tekelec • Telecom Italia • Telefonica • Tellabs • Tellac Networks • Tencent • Texas Instruments • Thales • Tilera • Transmode • Turk Telekom/Argela • TW Telecom • Vello Systems • Verisign • Verizon • Vmware/Nicira • Xpliant • Yahoo! • ZTE • 6Wind • A10 Networks • Active Broadband Networks • ADVA Optical • Alcatel-Lucent/Nuage • Aricent • Arista Networks • Big Switch Networks • Broadcom • Brocade • Centec Networks • Ceragon • China Mobile • Ciena • Cisco • Citrix • CohesiveFT • Colt • Cyan • Dell/Force10 • Deutsche Telekom • Ericsson • ETRI • Extreme Networks • F5/LineRate • Facebook • France Telecom/ Orange • Freescale • Fujitsu • Gigamon • Goldman Sachs • Google • Hitachi • HP • Huawei • IBM • Infinera • Infoblox • Intel • Initune Networks • IP Infusion • Ixia • Juniper Networks • KDDI • Korea Telecom • Lancope • Level3 Comms • LSI • Luxoft • Marvell • MediaTek • Mellanox • Metaswitch Networks • Microsoft • Midokura • NCL Comms K.K. • NEC • Netgear • Netronome • Netscout • Nokia Siemens Netw. • NoviFlow • NTT Communications • Oracle • Overture Networks • Pica8 • Plexxi • Qosmos • Rackspace • Radware • Riverbed Technology • Samsung Geneva, Switzerland, 4 June 2013 19

  20. ONF Operator Members Colt Deutsche Telekom France Telecom/OrangeTelecom ItaliaSwisscomTelefonicaTurk Telekom China Mobile Korea TelecomKDDI NTT CommunicationsSK Telecom Tencent Verizon Level 3 TW Telecom Geneva, Switzerland, 4 June 2013 20

  21. And then there is… • Many members in common • ONF: define Spec’s and Arch • Open Daylight: • Implements ONF standards (OF Specs) • Builds on ONF Arch (controller & apps) • One instantiation of a northbound API • Subject to contribution, experimentation, iteration • For some environment/use case (not all)

More Related