Design and implementation of a routing control platform
By Matthew C. Caesar, D. Caldwell, N. Feamster, Jennifer Rexford, A. Shaikh, J. V. D. Merwe. Symposium on Networked Systems Design and Implementation, 2005
468 citations recorded by the source corpus.
View Paper: https://www.semanticscholar.org/paper/8a1eb31bb9ee8af5f00b773f02fdce2b8c6a5178
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
- Yosr Jarraya
- Jennifer Rexford
- Brandon Heller
- N. Feamster
- Ion Stoica
- Amin Tootoonchian
- Andrew R. Curtis
- Taous Madi
Citations in the corpus
- PCC Vivace: Online-Learning Congestion Control (2018, background): “available bandwidth and ECN) for better informed decisions [5, 7, 20].”
- Towards secure and dependable software-defined networks (2013, background): “, routing [3]) while simultaneously enabling the introduction of sophisticated network policies, such as security and dependability.”
- A Survey of Software-Defined Networking: Past, Present, and Future of Programmable Networks (2014, unknown): “d) 4D Project: Starting in 2004, the 4D project [87], [48], [29] advocated a clean slate design that emphasized separation between the routing decision logic and the protocols governing the interaction between network elements.”
- NOX: towards an operating system for networks (2008, unknown): “This requires (as in [3, 8, 14] and elsewhere) centralizing network state.”
- A clean slate 4D approach to network control and management (2005, background): “RCP assumes routers are already correctly con.gured with signi.cant amounts of state, such as IP addresses and an Interior Gateway Protocol (IGP).”
- A new approach to interdomain routing based on secure multi-party computation (2012, methodology): “Inside a domain, these updates are handled in a manner similar to RCP [2], or one could have a small set of top-level route reflectors distribute the information.”
- Traffic engineering in software defined networks (2013, methodology): “Separating interdomain routing from individual routers and using a logically centralized Routing Control System was proposed in [2], [4] as a means to make routing systems more manageable, less complex and be accommodative of new service needs.”
- Revisiting Traffic Anomaly Detection Using Software Defined Networking (2011, background): “While there has been significant previous work in this domain [14,16,17], recently Openflow [7,28] has become the standard bearer for the SDN paradigm.”
- Dynamic scheduling of network updates (2014, background): “Categories and Subject Descriptors: C.2.1 [ComputerCommunication Networks]: Network Architecture and Design— Network communications; C.2.3 [Computer-Communication Networks]: Network Operations—Network management Keywords: Software-defined networking; network update”
- Debugging the data plane with anteater (2011, background): “As a result, these tools generally focus on checking correctness of a single protocol such as BGP [14, 15] or firewalls [2, 43].”
- The Road to SDN (2013, methodology): “65 • Logically centralized control of the network, as seen in the RCP (Routing Control Platform) 12,26 and SoftRouter 47 architectures, as well as the PCE (Path Computation Element) 25 protocol at the IETF.”
- Detecting BGP configuration faults with static analysis (2005, background): “The protocol that disseminates BGP routes within an AS should enforce path visibility and route validity; the Routing Control Platform [5] offers one possible solution.”
- Design and Implementation of a Consolidated Middlebox Architecture (2012, background): “Finally, the use of centralization to simplify network management is also well known [31] [21] [15].”
- Onix: A Distributed Control Platform for Large-scale Production Networks (2010, background): “Second, Onix allows for aggregation in which the network managed by a cluster of Onix nodes appears as a single node in a separate cluster’s NIB.”
- Distributed SDN Control: Survey, Taxonomy, and Challenges (2018, unknown): “RCP [88] and RouteFlow [89] are practical examples of successful intraAS platforms that use OpenFlow to provide conventional IP routing services in a centralized manner.”
- A data-oriented (and beyond) network architecture (2007, methodology): “We follow the model of RCP [4] in centralizing the design as much as possible, thereby reducing problems of consistency and coordination.”