1. Software-defined Networks October 2009 With Martin Casado and Scott Shenker And contributions from many others

2. Outline Trends – Towards “Software-defined Network” – Towards “Slicing” of network infrastructure – Government role

3. Million of lines of source code 5400 RFCsBarrier to entry 500M gates 10Gbytes RAM BloatedPower Hungry Many complex functions baked into the infrastructure OSPF, BGP, multicast, differentiated services, Traffic Engineering, NAT, firewalls, MPLS, redundant layers, … An industry with a “mainframe-mentality” We have lost our way Specialized Packet Forwarding Hardware Operating System Operating System App Routing, management, mobility management, access control, VPNs, …

4. Operating System Reality App Specialized Packet Forwarding Hardware Operating System Operating System App Lack of competition means glacial innovation Closed architecture means blurry, closed interfaces

5. Glacial process of innovation made worse by captive standards process Deployment IdeaStandardize Wait 10 years Driven by vendors Consumers largely locked out Lowest common denominator features Glacial innovation

6. Specialized Packet Forwarding Hardware Ap p Specialized Packet Forwarding Hardware Ap p Specialized Packet Forwarding Hardware Ap p Specialized Packet Forwarding Hardware Ap p Specialized Packet Forwarding Hardware Operating System Operating System Operating System Operating System Operating System Operating System Operating System Operating System Operating System Operating System Ap p Network Operating System App Change is happening in non-traditional markets

7. App Simple Packet Forwarding Hardware App Simple Packet Forwarding Hardware Network Operating System 1. Open interface to hardware 3. Well-defined open API 2. At least one good operating system Extensible, possibly open-source The “Software-defined Network”

8. Slicing the physical network

9. Simple Packet Forwarding Hardware Network Operating System 1 Open interface to hardware Virtualization or “Slicing” Layer Network Operating System 2 Network Operating System 3 Network Operating System 4 App Many operating systems, or Many versions Open interface to hardware Isolated “slices” Simple Packet Forwarding Hardware

10. Consequences More innovation in network services – Owners, operators, 3 rd party developers, researchers can improve the network – E.g. energy management, data center management, policy routing, access control, denial of service, mobility Lower barrier to entry for competition – Healthier market place, new players

11. Is change likely?

12. The change has already started In a nutshell – Driven by cost and control – Started in data centers…. and may spread – Trend is towards an open-source, software-defined network – Growing interest for cellular and telecom networks

13. Example: New Data Center Cost 200,000 servers Fanout of 20  10,000 switches $5k commercial switch  $50M $1k custom-built switch  $10M Savings in 10 data centers = $400M Control 1.Optimize for features needed 2.Customize for services & apps 3.Quickly improve and innovate Large data center operators are moving towards defining their own network in software.

14. Windows (OS) Windows (OS) Windows (OS) Windows (OS) Linux Mac OS Mac OS x86 (Computer) x86 (Computer) Windows (OS) Windows (OS) App Linux Mac OS Mac OS Mac OS Mac OS Virtualization layer App Controller 1 App Controller 2 Controller 2 Virtualization or “Slicing” App OpenFlow Controller 1 NOX (Network OS) NOX (Network OS) Controller 2 Controller 2 Network OS Trend Computer IndustryNetwork Industry

15. How can government help?

16. What NSF is supporting Trials of “Software-defined Network” & OpenFlow US College Campus Trials – UW, Georgia Tech, Princeton, Rutgers, UW-Madison, Clemson, Indiana, Stanford – Vendors with prototype OpenFlow: Cisco, Juniper, HP, NEC, Ciena, Arista, Quanta, …. National College Backbone Trials Data Center Clusters (with Google, Yahoo!, HP, etc.)

17. UW Stanford Univ Wisconsin Indiana Univ Rutgers Princeton Clemson Georgia Tech Internet2 NLR Nationwide OpenFlow Trials Production deployments before end of 2010 Production deployments before end of 2010

18. The role of government When funding new infrastructure – Mandate open interface to equipment (OpenFlow) – Recommend trials of “software-defined networks” Risk Invest in the wrong equipment, and we are stuck with “same old” equipment for 10 years

19. App Simple Packet Forwarding Hardware App Simple Packet Forwarding Hardware Network Operating System Software-defined Wireless Networks Applies equally to wireless networks Mobility manager, AAA, billing, MVNO, Wireless service provider, … WiFi, WiMAX, LTE

20. Outline Trends – Towards “Software-defined Network” – Towards “Slicing” of network infrastructure – Government role Dream – Making available the abundant wireless capacity around us – Technical trend – Business hurdles

21. Observations We are not short of wireless capacity: It is abundant, but off limits Cell phone today = 6 radios Cell phone in 2020 = 20 radios? Can we: – Decouple service providers from physical networks? – Allow user to decide to connect to any or many wireless networks simultaneously?

22. WiFi AP WiMAX LTE WiMAX LTE WiFi AP My Employer A home Nationwide infrastructure owners Service providers in cloud Slicing Open flow-based interface App “Newco” OS “Newco” OS “Vodafone” OS “Vodafone” OS “AT&T” OS “AT&T” OS Services Service Providers and Infrastructure

23. Thank you!