Composing Software Defined Networks
By Christopher Monsanto, Joshua Reich, Nate Foster, Jennifer Rexford, David Walker. Symposium on Networked Systems Design and Implementation, 2013
581 citations recorded by the source corpus.
View Paper: https://www.semanticscholar.org/paper/3d95c58c595130caa94cdc1fcdb0f9b9f12cb805
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
- Anirudh Sivaraman
- Fetia Bannour
- Jennifer Rexford
- Yosr Jarraya
- Rashid Amin
- Martin Reisslein
- Danda B. Rawat
- Mohammad Alizadeh
Citations in the corpus
- A Survey and a Layered Taxonomy of Software-Defined Networking (2014, background): “[71] defines an extension to Frenetic language with a sequential composition operator so that one module acts on the packets produced by another module.”
- The beacon openflow controller (2013, background): “• Python: POX [5], Pyretic [17], and RYU [7].”
- FloodGuard: A DoS Attack Prevention Extension in Software-Defined Networks (2015, methodology): “Motivated by existing work [23], [11], [16], we attempt to use program analysis techniques to solve the first challenge.”
- Software Defined Networking Architecture, Security and Energy Efficiency: A Survey (2017, background): “Abstraction tools like Frentic [47] and pyretic [49] are among the most commonly used ones.”
- Optimizing the "one big switch" abstraction in software-defined networks (2013, background): “We, and more broadly the community at large [10, 11, 12], have observed that such high-level policies may be specified in two parts, as shown in Figure 1: • An endpoint policy: Endpoint policies, like access control and load balancing, view the network as one big switch that hides internal topology ”
- NetKAT: semantic foundations for networks (2014, background): “Categories and Subject Descriptors D.3.2 [Programming Languages]: Language Classifications—Specialized application languages Keywords Software-defined networking, Frenetic, Network programming languages, Domain-specific languages, Kleene algebra with tests, NetKAT.”
- A survey on service function chaining (2016, background): “Recent advancements in the field of SDN and NFV allow ISPs to deploy many network services over the virtualized infrastructures [4, 24, 58, 65, 89].”
- SIMPLE-fying middlebox policy enforcement using SDN (2013, background): “Recent work provides abstractions to compose different policy modules [31].”
- Packet Transactions: High-Level Programming for Line-Rate Switches (2015, background): “Examples include Frenetic [54], Pyretic [71], and Maple [95].”
- Distributed SDN Control: Survey, Taxonomy, and Challenges (2018, background): “• The second category contains higher level APIs that rely on domain-specific programming languages such as Frenetic [41], Procera [42] and Pyretic [43] as an indirect way for applications to interact with the controller.”
- A Survey of Software-Defined Networking: Past, Present, and Future of Programmable Networks (2014, background): “The work in [75] proposes modularization to avoid that rules installed to perform one task do not override other rules.”
- Hybrid SDN Networks: A Survey of Existing Approaches (2018, background): “example, Pyretic [325] provides network programmers and operators with a high-level abstraction for building modular control applications.”
- Survey on Network Virtualization Hypervisors for Software Defined Networking (2015, methodology): “We proceed to explain these classification categories in detail.”