Safe Harbor

Schedule Slot Description Start End

1 Introduction 6:00 6:15

2 Dan Pitt – ONF 6:15 6:35

3 David Meyer 6:35 6:55

4 Break 6:55 7:10

5 Jennifer Rexford 7:10 7:30

6 Mike Freedman 7:30 7:50

7 Closing Remarks 7:50 8:00

8 Social 8:00 ~

Why SDN? A reflective look at networking…

IETF/IEEE

Vendors ?

Network Operators

Source: http://xkcd.com

Occupy DC?

Is the Internet Broken?

Hey AT&T customers: Your FaceBook data went to China and S. Korea this morning…

Source: http://www.blyon.com/

March 22, 2011

Suspects?

Persons of Interest?

Turns out it’s nobody's fault

Or is it?

ARPA NET April 1971

Internet Circa 2005

Source: http://www.blyon.com/

Source: http://xkcd.com/802/

Dan Pitt Open Networking Foundation

Todays Subjects

v  Musings on OpenFlow and SDN

v  Service-Centric Networking with Serval

v  Frenetic – A declarative approach to programming distributed collections of network switches.

David Meyer Musings on OpenFlow and SDN

Saltzer.. On the Naming and Binding of Network Destinations

1.   Service and Users. These are the functions that one uses, and the clients that use them. Examples of services are one that tells the time of day, one that performs accounting, or one that forwards packets. An example of a client is a particular desktop computer

2.   Nodes. These are computers that can run services or user programs. Some nodes are clients of the network, while others help implement the network by running forwarding services. (We will not need to distinguish between these two kinds of nodes.)

3.   Network attachment points. These are the ports of a network, the places where a node is attached. In many discussions about data communication networks, the term "address" is an identifier of a network attachment point.

4.   Paths. These run between network attachment 5.  Routes. Selects which path is chosen for the next-hop

Turns out network

addresses are just

“names”.. So where

is the topology?

IPV4 (2006) Source: http://xkcd.com/195/

Names, Addresses, Paths, Routes

Mike Freedman Service-Centric Networking

Break

“We have suggested that in general a gateway will be required in association with each TCP. Since these gateways form a network of their own, routing and formatting packets, and since there may eventually be many of them, it is advisable to keep them as identical as possible. We therefore suggest that the gateway routings be specified in some reasonably universally available higher level language. If possible, the gateway code should be machine compiled from the higher level language specification. We hope in this way , the implementation effort and variability will be minimized in implementations at various hosts.”

Gateway design for computer network interconnection David C. Walden and Randall D. Rettberg, BBN

Jennifer Rexford Frenetic

Closing Remarks Example meeting organization

By Track:

v  Development Track

v  Data Center Problems

v  Wide Area and Internet

v  BeyondIP