Reinventing Internet Infrastructure with OpenFlow and Software Defined Networking

1. Stanford Clean Slate Program http://cleanslate.stanford.edu Reinventing Internet Infrastructure with OpenFlow and Software Defined Networking Guru Parulkarparulkar@stanford.edu Funded by Cisco, Deutsche Telekom, DoCoMo, Ericsson, Google, LightSpeed, MDV, NEC, NSF, Xilinx

2. OpenFlow Team at Stanford With Martin Casado and Scott Shenker And contributions from many others

3. OpenFlow: Three Stories • A platform for innovations within • Enterprise, backbone, & data center networks • An architecture direction for Future Internet • Unifying packet and circuit networks • An architecture providers like for their own reasons • Enabling an ecosystem

4. Internet has many problems Plenty of evidence and documentation Internet’s “root cause problem” It is Closed for Innovations

5. Million of linesof source code 500M gates 10Gbytes RAM We have lost our way Routing, management, mobility management, access control, VPNs, … App App App 5400 RFCs Operating System Specialized Packet Forwarding Hardware Bloated Power 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”

6. OpenFlow: Enable Innovations “within” the Infrastructure Net Services PC OpenFlow Switch OpenFlow Protocol API SSL Controller Secure Channel sw • Add/delete flow entries • Encapsulated packets • Controller discovery Flow Table hw

7. OpenFlow Enabled Switches/Routers/APs Juniper MX-series WiFi NEC IP8800 WiMax (NEC) Cisco Catalyst 3750 (Fall 2009) CienaCoreDirector HP Procurve 5400 Cisco Catalyst 6k Arista 7100 series (Fall 2009) More to follow... Quanta LB4G

8. Sliced and Virtualized OpenFlow Infrastructure C C Research Team A Controller Research Team B Controller Production Net Controller OpenFlow Protocol C FLOWVISOR Control Plane API OpenFlow Protocol D D D D D D D Isolated Network Slices D D Physical Infrastructure Packet & Circuit Switches: wired, wireless, optical media D D D D D D D D D D D D D D D D D D

9. Example Network Services • Static “VLANs” • New routing protocol: unicast, multicast, multipath, load-balancing • Network access control • Mobile VM management • Mobility and handoff management • Energy management • Packet processor (in controller) • IPvX • Network measurement and visualization • …

10. OpenFlow Deployments Research and Production Deployments on commercial hardware • Stanford Deployments • Wired: CS Gates building, EE CIS building, EE Packard building (soon) • WiFi: 100 OpenFlowAPs across SoE • WiMAX: OpenFlow service in SoE • Other deployments • Internet2 • JGN2plus, Japan • 10-15 research groups have switches

11. OpenFlow as GENI Networking Substrate Eight universities and two national research backbones

12. OpenFlow Deployment in JapanNEC and JGN2Plus (NICT) • Network virtualization and slicing • HD video distribution in different slices • Baseball game • Snow festival

13. European Deployment Pan-European experimental facility • L2 Packet • Emulation • Wireless • Content delivery • L2 L3Packet • Optics • Content delivery • L2 Packet • Wireless • Routing • L2 Packet • Optics • Content delivery • L2 Packet • Shadow networks

14. OpenFlow Deployments Outside US • Several smaller scale efforts already on going • Interest in Korea, China, Brazil, …

15. OpenFlow: A Hack to Experiment? Is there a bigger architecture story?

16. OpenFlow: Enable Innovations “within” the Infrastructure Net Services PC OpenFlow Switch OpenFlow Protocol API SSL Controller Secure Channel sw • Add/delete flow entries • Encapsulated packets • Controller discovery Flow Table hw

17. 3. Well-defined open API Architecturally what It Means 2. At least one good operating system Extensible, possibly open-source App App App 1. Open interface to hardware Network Operating System Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware

18. OpenFlow: Architecture Concepts • Separate data from control • A standard protocol between data and control • Define a “generalized flow” based data path • Very flexible and generalized flow abstraction • Delayer or open up layers1-7 • Hierarchically centralized “open” controller with API • For control and management applications • Virtualization of data and control planes • Backward compatible • Though allows completely new header

19. Building Larger Internet Arch • Inter-domain routing framework • Network access and authentication • Security architectures • Mobility management • Packet and circuit unification • Traffic engineering • …

20. Why new generation providers like it and want to build an ecosystem?

21. New Generation Providers Already Buy into It In a nutshell • Driven by cost and control • Started in data centers….

22. Example: New Data Center Cost 200,000 servers Fanout of 20 a 10,000 switches $5k commercial switch a $50M $1k custom-built switch a $10M Savings in 10 data centers = $400M Control Optimize for features needed Customize for services & apps Quickly improve and innovate • The value prop applies to enterprise and service provider networks

23. What New Generation Providers have been Doing Within the Datacenters • Buy bare metal switches • Write their own control/management applications on a common platform Another way to look at it …

24. 3. Well-defined open API “Meeting of Minds” with Providers 2. At least one good operating system Extensible, possibly open-source App App App 1. Open interface to hardware Network Operating System Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware

25. Interest is Much Broader • Datacenter operators also operate WAN infrastructures • They want to cut cost and get more control • Legacy network operators learning from new providers • They also want to cut cost and get more control • Be more innovative and competitive • Convergence of cellular and Internet infrastructure • Another big impetus Net result: the change may come to all parts of the Internet infrastructure – sooner than you would think

26. Consequences • More innovation in network services • Owners, operators, 3rd 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 with reducing Capex & OpEx

27. Ecosystem Coming TogetherRole for Everyone to Contribute • Researchers and R&E Networks • Providers: old and new • Google, Amazon, Yahoo!, (Microsoft, Facebook), • DT, DoCoMo, (Level3, BT, Verizon, …) • Box vendors • Enterprise and backbone • Packet and circuit (electronic and photonics) • Incumbents and startups • Chip vendors • Broadcom, Dune, Marvell, …. The Value Chain

28. OpenFlow/SDN As Networking Substrate • A platform for innovations • Within enterprise, backbone, & data center networks • Providers buy into the architecture • For their own reasons • Ecosystem is coming together

29. Handheld UI Browser OS HW The Stanford Clean Slate Programhttp://cleanslate.stanford.edu Applications The Problem The 40year old Internet is showing its age: • Infrastructure not economically sustainable • Untrustworthy, unreliable and unpredictable • Does not support architectural innovations • Ill-suited for emerging technologies and applicationse.g., ubiquitous computing with mobile wireless devices, web based computing, sensorizednetworked physical world, … Computation Substrate Economics Data Substrate Our Approach Bring together Stanford’s world-class breadth & depth Research with emphasis on fundamental change andimpact on real practice of networking Create and Distribute “Platforms for Innovations” Funding:NSF, Cisco, Deutsche Telekom, DoCoMo, Ericsson, Google, NEC, Xilinx Network Substrate Radio technology

30. Vision: Three tiers of computing servers data Internet PC,TV at home, on the road, in hotels, on the plane Borrow the display, keyboard, memory, etc My window into the Internet. My cache of personal data. The key to my online data. Will identify me to others. Make payments, open physical locks. Great opportunities • Revolution in Mobile Computing will change our field. • Opportunity to bring change before ossification.

31. Barriers • Big-brother portals will own our data • We will be locked-in to applications • Wireless capacity will stay closed • Network will stay ossified Today Vision • Problem with the network. • 3G: Cellular networks a IP • IP: Bad for mobility, security, management • Need a network that continually evolves • When they’ve got our data, they’ve got us! • Surrounded by capacity we can’t use • Inefficient: Costs more, poorer quality • We need an alternative • Big-brother portals luring us to their repository • We have to provide an alternative • Healthcare, Financial: May never take off Where we willend up otherwise

32. Handheld UI Secure mobile browser Energy aware secure OS HW Platform The Big Picture Applications PocketSchool,Image WEB, Augmented Reality Computation Substrate Network of VMs, Mobile VMs Fiz web services environment Economics Data Substrate PRPL Virtual Data System Network Substrate OpenFlow Radio technologyMulti-Gb/s, 99% coverage

33. Stanford Clean Slate Team Education Applications Paul Kim Roy Pea HCI Scott Klemmer Security Dan Boneh John Mitchell Languages John Ousterhout Monica Lam Distributed Systems David Mazieres Phil Levis OS Mendel Rosenblum Architecture Christos Kozyrakis Economics Ramesh Johari Guru Parulkar Nick McKeown Networking Fouad Tobagi + 40 graduate studentsand 6 staff engineers BalajiPrabhakar Radio Arogyaswami Paulraj Departments of EE, CS, MS&E and School of Education

34. Thank You!!