The Open Networking Foundation:

Slides:



Advertisements
Similar presentations
Computer Networks TCP/IP Protocol Suite.
Advertisements

1 open alliance to network the physical world 2 Nov David E. Culler.
1 Building a Fast, Virtualized Data Plane with Programmable Hardware Bilal Anwer Nick Feamster.
ITU Workshop on Software Defined Networking (SDN) Standardization Landscape (Geneva, Switzerland, 4 June 2013) SDN Standardization in ONF: ONF Structure,
OpenFlow and Software Defined Networks. Outline o The history of OpenFlow o What is OpenFlow? o Slicing OpenFlow networks o Software Defined Networks.
Future Internet Research and Experiments EU vs USA 7 June, 2012 Róbert Szabó Dept. of Telecommunications and Media Informatics Budapest University of Technology.
Chapter 1: Introduction to Scaling Networks
An OpenFlow Extension for the OMNeT++ INET Framework
MobileFlow: Toward Software-Defined Mobile Networks
Towards Software Defined Cellular Networks
1 IU Campus GENI/Openflow Experience Matt Davy Quilt Meeting, July 22nd 2010.
Packet and Circuit Convergence with OpenFlow Stanford Clean Slate Program Funded by Cisco, Deutsche Telekom, DoCoMo, Ericsson,
Software Defined Networking
1 Cloud Computing Prof. Ravi Sandhu Executive Director and Endowed Chair April 12, © Ravi Sandhu World-Leading.
Contents Shortcomings of QoS in the Current Internet About OpenFlow
OpenCloud Connect Overview. 2 Cloud Services Market MEF drove $50B Carrier Ethernet market OCC has similar ambitions for OpenCloud OCC wants open standards.
SDN Technology Overview
OpenFlow Costin Raiciu Using slides from Brandon Heller and Nick McKeown.
Mobile Communication and Internet Technologies
Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain Pontus Sköldström - Wolfgang John – Elisa Bellagamba November.
OpenFlow : Enabling Innovation in Campus Networks SIGCOMM 2008 Nick McKeown, Tom Anderson, et el. Stanford University California, USA Presented.
Austin technology incubator New Strategies for the 21 st Century Incubator Presented by: Erin Defosse Former Director Austin Technology Incubator REV XXXX.
© Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Software Defined Networking.
CSE390 – Advanced Computer Networks Lecture 22: Software designed networking Based on slides by J. Princeton & N. Stanford & S. Shenker.
Virtualization and OpenFlow Nick McKeown Nick McKeown VISA Workshop, Sigcomm 2009 Supported by NSF, Stanford Clean.
Professor Yashar Ganjali Department of Computer Science University of Toronto
Software Defined Networks Saurav Das Guru Parulkar Nick McKeown With contributions from many others… A Presentation to the OIF 12 th July, 2011.
NATIONAL & KAPODISTRIAN UNIVERSITY OF ATHENS INTERDEPARTMENTAL GRADUATE PROGRAM IN MANAGEMENT AND ECONOMICS OF TELECOMMUNICATION NETWORKS Master Thesis.
An Overview of Software-Defined Network
CSE534 – Fundamentals of Computer Networks Lecture 22: Software designed networking Based on slides by J. Princeton & N. Stanford &
An Overview of Software-Defined Network Presenter: Xitao Wen.
Software-defined Networks October 2009 With Martin Casado and Scott Shenker And contributions from many others.
Professor Yashar Ganjali Department of Computer Science University of Toronto
Software Defined Network (SDN) and Network Virtualization
OpenFlow/Software Defined Networks 1. Exec Summary OpenFlow/SDN enables innovations within – Enterprise, backbone, & data center networks – Represents.
How SDN will shape networking
Nick McKeown, Tom Anderson, Hari Balakrishnan, Guru Parulkar, Larry Peterson, Jennifer Rexford, Scott Shenker, Jonathan Turner, SIGCOM CCR, 2008 Presented.
Information-Centric Networks10b-1 Week 13 / Paper 1 OpenFlow: enabling innovation in campus networks –Nick McKeown, Tom Anderson, Hari Balakrishnan, Guru.
OpenFlow: Enabling Technology Transfer to Networking Industry Nikhil Handigol Nikhil Handigol Cisco Nerd.
Introduction to SDN & OpenFlow Based on Tutorials from: Srini Seetharaman, Deutsche Telekom Innovation Center FloodLight Open Flow Controller, floodlight.openflowhub.org.
Software-Defined Networks Jennifer Rexford Princeton University.
Specialized Packet Forwarding Hardware Feature Specialized Packet Forwarding Hardware Operating System Operating System Operating System Operating System.
Software Defined Networks and OpenFlow SDN CIO Summit 2010 Nick McKeown & Guru Parulkar Stanford University In collaboration with Martin Casado and Scott.
Brent Salisbury CCIE#11972 Network Architect University of Kentucky 9/22/ OpenStack & OpenFlow Demo.
Aditya Akella (Based on slides from Aaron Gember and Nick McKeown)
OpenDaylight project introduction An open source project under the Linux Foundation with the goal of furthering the adoption and innovation of Software.
Software Defined Networking Mike Freedman COS 461: Computer Networks
SDN AND OPENFLOW SPECIFICATION SPEAKER: HSUAN-LING WENG DATE: 2014/11/18.
SDN and Openflow. Motivation Since the invention of the Internet, we find many innovative ways to use the Internet – Google, Facebook, Cloud computing,
Closed2Open Networking Linux Day 2015 Napoli, October Antonio Pescapè,
SOFTWARE DEFINED NETWORKING/OPENFLOW: A PATH TO PROGRAMMABLE NETWORKS April 23, 2012 © Brocade Communications Systems, Inc.
SDN and Beyond Ghufran Baig Mubashir Adnan Qureshi.
Global Software Defined Data Center (SDDC) Market Published: October2013 Single User PDF: US$ 2500 Corporate User PDF: US$ 3500 Order this report.
Outline PART 1: THEORY PART 2: HANDS ON
Data Center Networks and Software-defined Networking
Open Networking and SDN
OpenFlow/SDN tutorial OFC/NFOEC March, 2012
Road to SDN Review the main features of SDN
SDN challenges Deployment challenges
IP/MPLS Backbone Transition to SDN: OpenDaylight Advisory Board
Week 6 Software Defined Networking (SDN): Concepts
© 2016 Global Market Insights, Inc. USA. All Rights Reserved Software Defined Networking Market to grow at 54% CAGR from 2017 to 2024:
Software Defined Networking (SDN)
Stanford University Software Defined Networks and OpenFlow SDN CIO Summit 2010 Nick McKeown & Guru Parulkar In collaboration with Martin Casado and Scott.
Software Defined Networking
© 2016 Global Market Insights, Inc. USA. All Rights Reserved Network Function Virtualization Market to reach $70bn by 2024: Global Market.
The Stanford Clean Slate Program
Software Defined Networking (SDN)
Handout # 18: Software-Defined Networking
Software Defined Networking
Presentation transcript:

The Open Networking Foundation: OpenFlow & SDN from lab to market IEEE ComSoc SV chapter July 11, 2012 Dan Pitt, Executive Director Dan.Pitt@OpenNetworking.org

Points to cover Origins The Basics Why we exist Ambition, scope How we operate What we’re doing

Networks being built this way Origins Programmatic control of Enterprise networks Global policy, directly enforced Global vantage point OpenFlow Ethane Martin Casado NSF/GENI OpenFlow/SDN on 10 campuses Research demonstrations Now on 100+ campuses US, Europe, Asia Research Community: How to deploy new ideas? Data Center Networks WANs Enterprise and WiFi Vendors & startups emerging Industry Trend: Networks being built this way

Why we exist Users Solving problems of scale, flexibility, east-west traffic (data centers) Solving problems of cost, service introduction (service providers) Solving problems of applications, administration, security (enterprises) Networking Catching up to computing (distributed systems, virtualization) Becoming part of the computing infrastructure Standards User-led Faster 4

Domain problems Carriers End-customer monthly bill: unchanged Global IP traffic: up 40-50% per year CAPEX, OPEX need: down 40-50% per Gb/s per year CAPEX, OPEX reality: down 10-20% per year Service-creation velocity Data-center operators East-west traffic, already have global view Unbelievable scale Enterprises Everything else is virtualized Need flexibility to match IT to business needs 5

Vertically integrated Remember mainframes? App Specialized Applications Linux Mac OS Windows (OS) or Open Interface Specialized Operating System Specialized Hardware Microprocessor Open Interface The mainframe industry in the 1980s was vertical and closed: it consisted of specialized hardware, operating system and applications --- all from the same company. A revolution happened when open interfaces started to appear. The industry became horizontal. Innovation exploded. Vertically integrated Closed, proprietary Slow innovation Small industry Horizontal Open interfaces Rapid innovation Huge industry

That’s what today’s routers are Routing, management, mobility management, access control, VPNs, … Million of lines of source code Feature Feature 6,000 RFCs OS Custom Hardware Billions of gates Bloated Power Hungry Vertically integrated, complex, closed, proprietary Networking industry with “mainframe” mindset

Vertically integrated What SDN really is App Specialized Features Control Plane or Open Interface Specialized Control Plane Merchant Switching Chips Open Interface Specialized Hardware Vertically integrated Closed, proprietary Slow innovation Horizontal Open interfaces Rapid innovation

Network OS The transition Feature OS 9 Custom Hardware Custom Hardware

Feature Ctl. Program Network OS Separation of control, forwarding planes 3. Consistent, well-defined global view Feature Ctl. Program 2. At least one Network OS probably many Open- and closed-source Network OS 1. Open interface to packet forwarding Flow Table “If header = x, send to port 4” “If header = y, overwrite header with z, send to ports 5,6” “If header = ?, send to me” Packet Forwarding Packet Forwarding Packet Forwarding Packet Forwarding Packet Forwarding 10

ONF basics ONF is a foundation for the advancement of SDN (including standardization) is not a simple SDO Vision Make Software-Defined Networking the new norm for networks Mission Foster a vibrant market for SDN products, services, applications, users Goals Create the most relevant standards in record time to support a switching ecosystem based on the OpenFlow protocol Accelerate understanding of how to realize the abstractions above OpenFlow

Slicing Layer: FlowVisor Rich environment above OpenFlow Apps Tools Control Program A Control Program B Abstract Network View Virtualization Control Program C Global Network View Network OS(s) Control Program D Packet Forwarding Slicing Layer: FlowVisor 12

ONF legal A non-profit industry consortium 501(c)(6) Incorporated 2010, Launched March 22, 2011 Funded by member dues Open to any org. that pays annual dues, agrees to bylaws, IPR policy IPR policy RAND-Z: royalty-free use of protocol, OpenFlow trademark, logo Automatic cross-licensing of all related IP to all other members No licensing charges to members No protection for non-members ONF itself: no IP Open interfaces, not open source or reference implementations (yet)

ONF principles Operation Fast, lean, efficient Absent politics AMAP A startup ourselves, iterating with customers, agile, learning Standards creation Driven by users and user needs Developed by those close to implementation/deployment Standardize as little as necessary Vendor differentiation without lockin, market fragmentation More and more like a software community No names on drafts Relevant, implementable now; protocol-agnostic eventually Rapid real-world experience

Technical Advisory Group ONF governance Board of Directors Users, not vendors Executive Director (employee) Reports to the Board; vendor neutral Technical Advisory Group Advises Board on fundamental technical issues Working Groups Chartered by the Board Chaired by Board appointee Council of Chairs Executive Director Board of Directors Technical Advisory Group . . . Technical Working Group Market Education Activities Regional Chairs Council of Chairs

7 Board companies, 65 others Urs Hölzle (Sr. VP, Engineering, Google), chairman Najam Ahmad (Director, Network Engineering, Facebook) Adam Bechtel (VP, Infrastructure Group, Yahoo) Stuart Elby (VP, Network Architecture, Verizon) Axel Clauberg (VP, IP & Optical, Deutsche Telekom) Yukio Ito (Sr. VP, Services & Infrastructure, NTT Communications Clyde Rodriguez (GM, Windows Azure Networking, Microsoft) Nick McKeown (Professor, EE and CS, Stanford) Scott Shenker (Professor, EECS, UC Berkeley and ICSI) ETRI Extreme Networks EZchip F5 Networks Freescale Semi Fujitsu Gigamon Goldman Sachs Hitachi HP Huawei IBM Infinera Infoblox Intel IP Infusion Ixia Juniper Networks Korea Telecom LineRate Systems LSI Luxoft Marvell Mellanox Metaswitch Networks Midokura NCL Comms K.K. NEC Netgear Netronome Nicira Networks Nokia Siemens Netw. NoviFlow Oracle Orange/France Telecom Pica8 Plexxi Inc. Radware Riverbed Technology Samsung SK Telecom Spirent Telecom Italia Tencent Texas Instruments Vello Systems VMware ZTE A10 Networks ADVA Optical Alcatel-Lucent Aricent Argela/Turk Telekom Big Switch Networks Broadcom Brocade Ciena Cisco Citrix Colt CompTIA Cyan Optics Dell/Force10 Elbrys Ericsson 16

OpenFlow standards Evolution path: OF 1.0 (03/2010): Most widely used version, MAC, IPv4, single table (from Stanford) OF 1.1 (02/2011): MPLS tags/tunnels, multiple tables, counters (from Stanford) OF 1.2 (12/2011): IPv6, extensible expression OF-Config 1.0 (01/2012): Basic configuration: queues, ports, controller assign OF 1.3.0 (04/2012): Tunnels, meters, PBB support, more IPv6 OF-Config 1.1 (04/2012): Topology discovery, error handling OF-Test 1.0 (2H2012): Interoperability & conformance test processes, suites, labs Goals: Widespread adoption, experimentation w/OF 1.3.x Accommodate current merchant silicon Move beyond limitations of current merchant silicon 17

Technical activities Chartered Working Groups Extensibility (chair: Jean Tourrilhes, HP): OpenFlow protocol Config-mgmt (chair: Deepak Bansal, Microsoft): basic switch configuration Testing-interop (chair: Michael Haugh, Ixia): conformance, interop., benchmarking Hybrid (chair: Jan Medved, Cisco): mixed OpenFlow/legacy switches & networks Discussion Groups OpenFlow-Future: forwarding-plane models NorthboundAPI: how the network relates to the applications NewTransport: OpenFlow for optical, circuits, wireless Market Education (chair: Isabelle Guis, Big Switch): marketing, customer value 18

Conclusions ONF now the home of OpenFlow Take OpenFlow 1.1 to commercial strength – Job One Family of standards: foundation, building blocks, choices Protocols; configuration and management; compliance and interoperability Development, deployment, experience, feedback SDN beyond OpenFlow SDN abstractions, object models, interactions Ecosystem for new features, new players, new business models Technical standards + market education Market pull to drive the ecosystem

ONF: innovating in technology and standardization www.OpenNetworking.org Dan.Pitt@OpenNetworking.org