kerri
Uploaded by
6 SLIDES
209 VIEWS
60LIKES

On Programmability and Software Defined Networking

DESCRIPTION

The concepts of programmability and software-defined networking (SDN) can be confusing within the industry. This article explores the nuances of these terms, distinguishing between the forwarding plane and control plane. We delve into technologies such as OpenFlow (OF), SDN, Netconf, and SDKs, clarifying their roles in facilitating automation in configuration, management, and monitoring. Additionally, we highlight industry misconceptions and the necessity for programmatic interfaces across various control planes, emphasizing that OF is a foundational tool rather than the end solution for automation needs in networking.

1 / 6

Download Presentation

On Programmability and Software Defined Networking

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. On Programmability and Software Defined Networking • Lots of confusion in the industry over which “programmability” and “software defined networking” actually mean • So first, what are the programmable entities we’re talking about? • Forwarding Plane v. Control Plane v. “network” • So OF/SDN, Netconf, SNMP, CLI, SDKs, OpenStack, SDNP, …

  2. What is Stipulated? • OF/SDN was originally designed to be a platform for developing control planes • Programmatic automation of configuration, management, monitoring, data mining, telemetry, … is a requirement in today’s networks • SDKs, Netconf, Cloud Stacks, SDNP, draft-marques-…

  3. What is my Assertion? • Enabling programmatic automation of configuration, management, monitoring, data mining, … is largely orthogonal to OF/SDN • Why? • Since this capability will need to be provided on current control planes *and*future control planes, including OF/SDN

  4. What is the Industry Confusion? • What is the difference between OF/SDN and the need for network-wide programmatic automation? • OF is a programmatic interface to a single switch’s forwarding plane • Well, sort of (cf Hybrid Switch Integrated Mode proposal) • OF/SDN is about abstractions for building control planes • SDNP, OpenStack, … are about programmatic interfaces to the network • OF/SDN control planes will also need programmatic interfaces to the network • Perhaps the same ones, e.g., IF-MAP (http://www.if-map.org/)

  5. Interesting Quote From Martin (Nicira) "We need to get beyond, 'OpenFlow is going to solve world peace.' OpenFlow is like USB, it's a protocol, a very simple protocol and it's designed at systems builders." OpenFlow and beyond: future opportunities in networking, GigaOM 09/2011 Point here is that OF is assembly language for building control planes rather than an API for programmatic automation of configuration, management, monitoring, ….

  6. Thanks!

More Related