OpenFlow: enabling innovation in campus networks

By Nick McKeown, T. Anderson, Hari Balakrishnan, G. Parulkar, Larry L. Peterson, Jennifer Rexford, Scott Shenker, Jonathan S. Turner. CCRV, 2008

9,391 citations recorded by the source corpus.

Subfields: Computer Networks and Communications

View Paper: https://www.semanticscholar.org/paper/0742fa40bf9be455fc6338e3a40ed6f0113d4a61

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Computer Networks and Communications

Citations in the corpus

NetKAT: semantic foundations for networks (2014, background): “For example, the OpenFlow API [21] clearly specifies the capabilities and behavior of switch hardware and defines a low-level language for manipulating their configurations.”
A Survey of Network-based Intrusion Detection Data Sets (2019, methodology): “Typical flow-based formats are NetFlow [41], IPFIX [40], sFlow [42] and OpenFlow [43].”
OpenFlow-Based Server Load Balancing Gone Wild (2011, methodology): “The emerging OpenFlow [8] platform enables switches to forward traffic in the high-speed data plane based on rules installed by a control plane program running on a separate controller.”
The Road to SDN (2013, methodology): “…[78] ForCES protocol [86] RCP [26], SoftRouter [47] PCE [25], 4D [35] IRSCP[77] Ethane [16] Ethane[16] OpenFlow and network OS section 2.3 OpenFlow[51] Onix [46] ONOS [55] network virtualization: section 3 MBone [50] 6Bone[43] RON [4] Planet-Lab [18] Impasse[61] GENI[59] VINI [7] Open vSwitch…”
One Sketch to Rule Them All: Rethinking Network Flow Monitoring with UnivMon (2016, background): “We believe that this “minimality” of the UnivMon design will naturally motivate hardware vendors to invest time and resources to develop optimized hardware implementations, in the same way that a minimal data plane was key to get vendor buy-in for SDN [40].”
Toward Software-Defined Cellular Networks (2012, background): “Today's OpenFlow [11] switches already support many features needed in cellular networks.”
Participatory networking: an API for application control of SDNs (2013, positive): “,[25, 34, 46]) improve the deployability of PANE.”
Protocol-oblivious forwarding: unleash the power of SDN through a future-proof forwarding plane (2013, background): “OpenFlow [1] separates the control and forwarding planes to improve network application programmability and allow the two planes to evolve independently.”
Forwarding metamorphosis: fast programmable match-action processing in hardware for SDN (2013, background): “The vector ﬂows through a sequence of logical match stages, each of which abstracts a logical unit of packet processing (e.g., Ethernet or IP processing) in Figure 1a.”
Optimizing the "one big switch" abstraction in software-defined networks (2013, methodology): “Over the past few years, many applications ( e.g., server load balancing, virtual-machine migration, and access control) have been built using the popular OpenFlow API [1].”
P4: programming protocol-independent packet processors (2013, background): “While forwarding devices could be programmed in many ways, having a common, open, vendor-agnostic interface (like OpenFlow) enables a control plane to control forwarding devices from diﬀerent hardware and software vendors.”
Abstractions for network update (2012, background): “For example, the OpenFlow API allows a controller to install rules that each specify a pattern that matches on bits in the packet header, actions performed on matching packets (such as drop, forward, or divert to the controller), a priority (to disambiguate between overlapping patterns), and timeout”
Distributed SDN Control: Survey, Taxonomy, and Challenges (2018, methodology): “On the other hand, OpenFlow [24] received major attention”