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
1
Points to cover
•
Origins
•
The Basics
•
Why we exist
•
Ambition, scope
•
How we operate
•
What we’re doing
2
Origins
Ethane
Martin
Casado
1. Programmatic control of Enterprise networks
2. Global policy, directly enforced
3. Global vantage point
4. OpenFlow
1. NSF/GENI
2. OpenFlow/SDN on 10 campuses
3. Research demonstrations
4. Now on 100+ campuses
5. US, Europe, Asia
Research Community:
How to deploy new ideas?
1. Data Center Networks
2. WANs
3. Enterprise and WiFi
4. Vendors & startups emerging
Industry Trend:
Networks being built this way
3
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
Remember mainframes?
AppAppAppAppAppAppAppAppAppAppApp
Specialized
Applications
Open Interface
Specialized
Operating
System
Windows
(OS)
Specialized
Hardware
or
Linux
or
Mac
OS
Open Interface
Microprocessor
Horizontal
Open interfaces
Rapid innovation
Huge industry
Vertically integrated
Closed, proprietary
Slow innovation
Small industry
6
That’s what today’s routers are
Routing, management, mobility
management,
access control, VPNs, …
Featur
e
Feature
OS
Custom Hardware
Million of 6,000 RFCs
lines
of source
code
Billions of Bloated
gates
Power Hungry
• Vertically integrated, complex, closed, proprietary
•
Networking industry with “mainframe” mindset
7
What SDN really is
AppAppAppAppAppAppAppAppAppAppApp
Specialized
Features
Open Interface
Specialized
Control
Plane
Control
Plane
or
Control
Plane
or
Control
Plane
Open Interface
Specialized
Hardware
Merchant
Switching Chips
Vertically integrated
Closed, proprietary
Slow innovation
Horizontal
Open interfaces
Rapid innovation
8
The transition
Feature
Feature
Network OS
Feature
Feature
OS
Feature
Feature
Custom Hardware
OS
Feature
Feature
Custom Hardware
OS
Feature
Custom Hardware
Feature
OS
Feature
Custom Hardware
Feature
OS
Custom Hardware
9
Separation of control, forwarding planes
3. Consistent, well-defined global view
Feature Ctl. Program
2. At least one
Network OS
probably many
Open- and closedsource
1. Open interface to packet forwarding
Network OS
Flow
Table
Packet
Forwarding
“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
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
11
Rich environment above OpenFlow
Apps
Control Program A Control Program B
Tools
Abstract Network View
Virtualization
Control Program C
Global Network View
Network OS(s)
Control Program D
Slicing Layer: FlowVisor
Packet
Forwarding
Packet
Forwarding
Packet
Forwarding
Packet
Forwarding
Packet
Forwarding
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)
13
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
14
ONF governance
Board of Directors
• Users, not vendors
Executive Director (employee)
Technical
Advisory Group
Board of
Directors
• Reports to the Board; vendor neutral
Technical Advisory Group
• Advises Board on fundamental technical issues
Working Groups
Council
of Chairs
• Chartered by the Board
• Chaired by Board appointee
Technical
Working
Group
...
15
Chairs Council
of Chairs
Technical
Working
Group
Market
Education
Activities
Executive
Director
Regional
Activities
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)
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
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
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
ETRI
Extreme Networks
EZchip
F5 Networks
Freescale Semi
Fujitsu
Gigamon
Goldman Sachs
Hitachi
HP
Huawei
IBM
Infinera
Infoblox
Intel
IP Infusion
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
16
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
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
19
ONF: innovating in technology and standardization
www.OpenNetworking.org
Dan.Pitt@OpenNetworking.org
20