OpenFlow

What does OpenFlow/Software Defined Networking provide?
- the first significant change in networking in the last 1 to 2 decades
- enables virtualization and provide services on the network
Networking Now
- Base of Specialized Packet Forwarding Hardware
- Operating System
- Features
- Networking has been stagnant in its evolution (Ethernet, Wifi, IP)
- Rate of change in networking has been slow; need better tools to facilitate change
SDN/OpenFlow
- Growing community (200+ deployments)
- Open network flow, as opposed to Closed Systems
- Architecture consists of switches that are controlled by a Network Operating System, with Features enabled as part of the NOS
- Control Protocol
- Open architecture, configurable by users
- Features can turn into a service (SaaS model)
- 3rd party or service providers can be utilized in the network
OpenFlow Network Virtualization
- Flow entries are handled by Virtualization ("Slicing") layer
- Allows for splits of resources and instructions on how to handle those resources in the network
- Allows for decision making within IPv4 or IPv6 packet components
- Control at the "conversation" level - source and destination
Why is SDN/OpenFlow important?
- Give more control to network owners and operators
- Enable innovation in networking and the development of new services
- Provide a more diverse choice of hardware and software
- Opportunity to build more robust foundation
Use Cases
- For Network Administration
* Guest Access (Wireless & Wired)
* Campus Wireless
* Data Center
* Campus Backbone Network
* Delegated Management
- Residences
- For Science Community
* Connecting to other Research Communities
- For Network Researchers
* Shared infrastructure
- Network-wide load balancing, firewalling
- Bandwidth Management
Questions:
- Security concerns: with a central controller for the network, you need security controls. The open source protocol will allow for quick iteration of fixes for securing the network ongoing. The cohesive view of the network helps keep control of who/what enters/exits the network.
- How many controllers can/should be deployed? Each department could have their own controller; IT Networking would own the virtualization layer (Flowvisor) and would control which controllers can participate in the network.
- How long can dumb device be online when the controller goes down? So far several approaches; fail open, keep state static at time of controller failure.
- How does OpenFlow/SDN fit into the new world as described by John Hennessey in his morning remarks? Fits perfectly because it allows for the "balancing act" of centralized control and edge services.