40 likes | 155 Views
This document explores the concept of programmable networks as articulated by Stephen Wolff of Cisco Systems. A network is deemed “programmable” if its nodes can make forwarding decisions based on aspects of packet contents beyond just the IP destination address. Key aspects include Deep Packet Inspection (DPI), user and operator access to the control plane (like OpenFlow), and the manipulation of network state. It discusses collaborative efforts, including trials and innovations spearheaded by Stanford and Internet2, and addresses the challenges and flexibilities such networks present in management and development.
E N D
Programmable networks Stephen Wolff Cisco Systems
Definitions – IP networks only • A network is “programmable” if the current or future forwarding decision of any node is affected by packet contents other than IP Destination Address (and TTL, L/SSR, etc.) • DPI & IPS • Operator access to control plane, e.g.: OpenFlow • User access to control plane, e.g.: DARPA Active Nets • A network is “programmable” if it maintains and manipulates state
Implementation • Collaboration with Stanford (McKeown) • Trial implementation of OpenFlow • Collaboration with Internet2 • Experiments with AXP • Cisco Developer Network • <http://developer.cisco.com/web/partner> • Internal development
Implications • Flexibility: greater • Permits implementation of features the manufacturer never thought of or couldn’t justify • Management, maintenance, and trouble-shooting: harder