From the paper's abstract -
Software Defined Networking (SDN) is an exciting technology that enables innovation in how we design and manage networks. Although this technology seems to have appeared suddenly, SDN is part of a long history of efforts to make computer networks more programmable. In this paper, we trace the intellectual history of programmable networks, including active networks, early efforts to separate the control and data plane, and more recent work on OpenFlow and network operating systems. We highlight key concepts, as well as the technology pushes and application pulls that spurred each innovation. Along the way, we debunk common myths and misconceptions about the technologies and clarify the relationship between SDN and related technologies such as network virtualization.
http://dl.acm.org/citation.cfm?id=2602219
4. and a few definitions
Decides how to forward packets (Routing, Dropping, Firewall Rules)
Does the actual forwarding (or dropping, or filtering) of the data packets
Control Plane
Data Plane
11. Active Networking
Driving Factors
Technology - Cheaper computing, Virtual machines (sandboxes), WORA, security, a la Java
Users - Faster new service deployment, Finer control to dynamically meet app/network needs, platforms
for scalable research
13. Control & Data Plane Separation
Vision
- Conventional routing protocols were primitive for traffic engineering
- Data and control planes are tightly coupled in conventional routers
14. Control & Data Plane Separation
Driving Factors
Technology - Vendors built packet forwarding logic in data plane hardware
Users - Increased size and complexity of service providers
15. Control & Data Plane Separation
Legacy
- Open interface between control and data planes (ForCES, Netlink)
- Logically centralized control of the network (RCP, SoftRouter)
- Further clean-slate architectures - 4D, Ethane (set the stage for OpenFlow)
16. OpenFlow & the NOS
Vision (and Reality)
- Campus networks @Stanford
- Right balance between full programmability & real world deployment
- Followed by controllers like NOX
17. OpenFlow & the NOS
Driving Factors
Technology - Gradual opening up of switch chipset vendor APIs, Industry demand for more network
device control
Users - People getting together - Equipment vendors, chipset designers, network operators, networking
researchers
18. OpenFlow & the NOS
And after OpenFlow
- Conceptual unification of network devices/functions
- Rise of network operating systems
- Distributed state management techniques (e.g. the Onix controller)
19. Myths about SDN
First packet of every traffic should go to the controller
Controller must be physically centralized (e.g. Google's WAN)
OpenFlow == SDN