Transcript FlowNet A Clean-Slate De-layered Internet

A Simple Unified Control
Plane for Packet and Circuit
Networks
Saurav Das, Guru Parulkar, Nick McKeown
Stanford University
Motivation
RESEARCH
Many great ideas
PRODUCTION
none transferred to
Production networks
NEEDED: Realistic ways to try out ideas at scale
2
New Ideas
• Mobility Management
• Network Security
• Energy Management
• Alternatives to BGP, new routing
• Network Measurement
• Things we haven’t thought of…
3
Motivation
Exceedingly high barrier to change
Deployment
Idea
Standardize
Wait 10 years
• Massive installed base of equipment & protocols – requires backward
compatibility
• Rigid nature of platform – closed system, vendor proprietary OS
• Fear of network instability - discourages network operators from
innovation - conservatively managed
• Power to control network no longer in SP’s hand
Motivation
We lost our way
Router
Software
Control
Hardware
Datapath
20Million lines 5389 RFCs
of source code
Barrier to entry
500M gates
10Gbytes RAM
Power Hungry
( 15 kW/shelf )
Bloated
Motivation
We lost our way
IPSec
Firewall
Router
Software
Control
OSPF-TE
RSVP-TE
HELLO
HELLO
HELLO
Hardware
Datapath
Many complex functions baked into the infrastructure
More coming ……
6
Motivation
We lost our way
PWE3
CORBA
Transport
NE
Software
Control
HELLO
HELLO
RSVP-TE
OSPF-TE
HELLO
Hardware
Datapath
Lots of baggage from L3
More extensions coming ……
7
A Clean Slate Approach
Goal: Put an Open platform in hands of
researchers/students to test new ideas at scale
Approach:
1. Define OpenFlow feature
2. Work with vendors to add OpenFlow to their
switches
3. Deploy on college campus networks
4. Create experimental open-source software
- researchers can build on each other’s work
8
Open Source Networking
What will networks look like in 10 years from now?
9
De-coupling Control & Data Planes
Control
Routing
Signaling
Data
10
De-coupling Control & Data Planes
Controller
Control
Signaling
Data
11
De-coupling Control & Data Planes
Decoupled
Automated
Control
Controller
Simple, Robust, Reliable
Data Path
Control
Signaling
Data
12
The Flow Abstraction
Exploit the flow table in switches, routers, and chipsets
Flow 1.
Rule
(exact & wildcard)
Action
Statistics
Flow 2.
Rule
(exact & wildcard)
Action
Statistics
Flow 3.
Rule
(exact & wildcard)
Action
Statistics
Rule
(exact & wildcard)
Default Action
Statistics
e.g. Port, VLAN ID,
L2, L3, L4, …
e.g. unicast, mcast,
map-to-queue, drop
Flow N.
Count packets & bytes
Expiration time/count
OpenFlow Switching
Controller
http://openflowswitch.org
OpenFlow Switch
sw Secure
Channel
hw Flow
Table
• Add/delete flow entry
• Encapsulated packets
• Controller discovery
A Flow is any combination of above fields
14
described in the Rule
OpenFlow is Backward Compatible
Ethernet Switching
Switch MAC
Port src
MAC Eth
dst
type
VLAN IP
ID
Src
IP
Dst
IP
Prot
TCP
sport
TCP
dport
Action
*
00:1f:.. *
*
*
*
*
*
port6
Switch MAC
Port src
MAC Eth
dst
type
VLAN IP
ID
Src
IP
Dst
IP
Prot
TCP
sport
TCP
dport
Action
*
*
*
5.6.7.8 *
*
*
port6
VLAN IP
ID
Src
IP
Dst
IP
Prot
TCP
sport
TCP
dport
Action
*
*
*
*
22
drop
*
*
IP Routing
*
*
*
Application Firewall
Switch MAC
Port src
*
*
*
MAC Eth
dst
type
*
*
OpenFlow allows layers to be combined
Flow Switching
Switch MAC
Port src
MAC Eth
dst
type
VLAN IP
ID
Src
IP
Dst
IP
Prot
port3 00:2e.. 00:1f.. 0800 vlan1 1.2.3.4 5.6.7.8 4
TCP
sport
TCP
Action
dport
17264 80
port6
VLAN + App
Switch MAC
Port src
*
*
MAC Eth
dst
type
*
VLAN IP
ID
Src
IP
Dst
IP
Prot
TCP
sport
TCP
Action
dport
vlan1 *
*
*
*
80
VLAN IP
ID
Src
IP
Dst
IP
Prot
TCP
sport
TCP
Action
dport
*
*
*
port6,
port7
Port + Ethernet + IP
Switch MAC
Port src
MAC Eth
dst
type
port3 00:2e.. *
0800 *
*
5.6.7.8
4
port 10
Flow Example
Controller
Routing
A Flow is the fundamental
unit of manipulation within a switch
Rule
Action
Statistics
OpenFlow
Protocol
Rule
Action
Statistics
Rule
Action
Statistics
OpenFlow Status
Commercial hardware
Juniper, HP, Cisco, NEC, (Broadcom)
Deployed in 3 buildings at Stanford
Deployed in Internet2
Plans for deployment in
7 other campuses,
Other RENS – NLR, JGNII, Federica
Can we create a way for
networking researchers to test
their ideas at scale…
..in networks that include both
packet and circuit switches
19
OpenFlow & Circuit Switches
Packet Flows
Switch MAC
Port src
MAC Eth
dst
type
VLAN IP
ID
Src
IP
Dst
IP
Prot
TCP
sport
TCP
dport
Action
Exploit the cross-connect table in circuit switches
Circuit Flows
In
Port
VCG Starting Signal
In
20
Lambda
Time-Slot Type
Out
Port
VCG Starting Signal
Out
20
Lambda
Time-Slot Type
Once we have a Flow abstraction,
… does it really matter what the underlying
switching technology is … packet or circuit?
20
Mapping Packet Flows to Circuit Flows
IP 10.12.3.4
VLAN 1025
+VLAN2, P1
+VLAN7, P1
VLAN2
VCG 3
VLAN7
VCG7
OpenFlow
(software)
R
A
S
P1
P3
P1
P2
VCG3
VCG7
1
VC4 7
VC4 4
VC4 10
VC4
OpenFlow
(software)
R
Packet
Switch
Fabric
A
Packet
Switch
Fabric
GE
ports
S
IN
OUT
TDM
Circuit
Switch
Fabric
TDM
ports
21
Simple Unified Control Plane
Flow
Network
22
Simple Unified Control Plane
Packet and Circuit Flows
Commonly Controlled & Managed
Simple,
Robust,
Reliable
network
of Flow
Switches
Flow
Network
23
… that switch at different granularities: packet, time-slot, lambda & fiber
Network
OpenFlow enables innovation
Recovery
• Service Provider not handcuffed to
the limitations of the platform
• Returns control to the stakeholders
of the network
• Open-source networking
Congestion
Routing
Control
Traffic
QoS
Power
Engineering
Mgmt
Security
Discovery
24
Example of what we could try..
Congestion
Control
25
Example of what we could try..
Traffic
Engineering
26
Example of what we could try..
Traffic
Engineering
27
Example of others may try..
• All Optical Network control
• New ways to plan and dimension networks
• Network recovery
• Network discovery
• Power management
• Things we haven’t thought of…
28
Summary
• OpenFlow allows research community to try new ideas
at scale
in networks with packet and circuit switches
 leading to transfer of technology from research
to industry – a transfer that barely exists today

• Suggests how networks might be architected in the
future
 allow new ideas to be tested in one slice
 before being deployed in the production slice
http://openflowswitch.org
• We are in the process of convincing circuit switch
vendors to add the OpenFlow interface
29