DevoFlow: scaling flow management for high-performance networks
By Andrew R. Curtis, Jeffrey C. Mogul, Jean Tourrilhes, Praveen Yalagandula, P. Sharma, S. Banerjee. Conference on Applications, Technologies, Architectures, and Protocols for Computer Communication, 2011
1,333 citations recorded by the source corpus.
Subfields: Computer Networks and Communications, Information Systems
View Paper: https://www.semanticscholar.org/paper/54a4e43121e7464c22540f42aa48ea70ce5ab6e4
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
- Danda B. Rawat
- S. Reddy
- Jennifer Rexford
- Guofei Gu
- Mourad Debbabi
- Raouf Boutaba
- Yosr Jarraya
- Taous Madi
In Information Systems
- Jennifer Rexford
- Guofei Gu
- Sergey Gorbunov
- Martín Casado
- Brighten Godfrey
- Bruno Astuto Arouche Nunes
- S. Muthu Muthukrishnan
- Fei Hu
Citations in the corpus
- OFLOPS: An Open Framework for OpenFlow Switch Evaluation (2012, background): “[6] discuss some design limitations of the protocol when deployed in large network environments.”
- A Survey on Software-Defined Network and OpenFlow: From Concept to Implementation (2014, background): “For example, in [81] authors have measured the flow”
- Data Center Network Virtualization: A Survey (2013, methodology): “Recent research efforts have been carried to deploy OpenFlow in data center networks [41], [62], [63].”
- Heavy-Hitter Detection Entirely in the Data Plane (2016, background): “Further, identifying such “heavy hitters” at small time scales (comparable to traffic variations [1, 5]) can enable dynamic routing of heavy flows [16, 35] and dynamic flow scheduling [41].”
- Abstractions for network update (2012, background): “Wildcard cloning: An alternative mechanism exploits the wildcard clone feature of the DevoFlow extension of OpenFlow [17].”
- Planck (2014, methodology): “To emulate previous traffic engineering projects that rely on polling [2, 6], we implement a global first fit routing algorithm that greedily reroutes every flow either once a second, which is referenced by the name Poll-1s, or once every 100 ms, which is called Poll-0.”
- FloodGuard: A DoS Attack Prevention Extension in Software-Defined Networks (2015, background): “While there are many studies and solutions on the scalability issue [20], [12], [10], [32], [14], there is very little research on the even more challenging security issue.”
- On Controller Performance in Software-Defined Networks (2012, methodology): “, [6, 18]) to address perceived architectural inefficiencies.”
- Dynamic Controller Provisioning in Software Defined Networks (2013, background): “DevoFlow [5] and DIFANE [16] falls in the first category of techniques.”
- Software Defined Networking Architecture, Security and Energy Efficiency: A Survey (2017, background): “DevoFlow load balancing has been implemented in [142] in enterprise networks and data center environments to reduce the burden on controller by providing the switches with a set of additional wild card rules and minimize the overall energy consumption.”
- SoftCell: scalable and flexible cellular core network architecture (2013, methodology): “the access switch, similar to the DevoFlow “clone” function [16].”
- A survey: Control plane scalability issues and approaches in Software-Defined Networking (SDN) (2017, methodology): “In this subsection, we present everal SDN architectures [50,51,56] that leverage the data plane y devolving some limited control functions (such as sending rules o other network devices to be added, deleted or updated in their ow tables etc.”
- SIMPLE-fying middlebox policy enforcement using SDN (2013, background): “Challenge = Data plane constraints: SDN switches are limited by the number of forwarding rules they can support; these rules are in TCAM and a switch can support a few thousand rules (e.g., 1500 TCAM entries in 5406zl switch [14]).”
- Improving network management with software defined networking (2013, background): “[1] [2] ● Procera has four control domains — time, data usage, authentication status, and traffic flow.”