ACM Home Page
Please provide us with feedback. Feedback
The case for separating routing from routers
Full text PdfPdf (143 KB)
Source Applications, Technologies, Architectures, and Protocols for Computer Communication archive
Proceedings of the ACM SIGCOMM workshop on Future directions in network architecture table of contents
Portland, Oregon, USA
SESSION: Routing table of contents
Pages: 5 - 12  
Year of Publication: 2004
ISBN:1-58113-942-9
Authors
Nick Feamster  MIT Computer Science & AI Lab
Hari Balakrishnan  MIT Computer Science & AI Lab
Jennifer Rexford  AT&T Labs Research
Aman Shaikh  AT&T Labs Research
Jacobus van der Merwe  AT&T Labs Research
Sponsors
SIGCOMM: ACM Special Interest Group on Data Communication
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 15,   Downloads (12 Months): 97,   Citation Count: 24
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1016707.1016709
What is a DOI?

ABSTRACT

Over the past decade, the complexity of the Internet's routing infrastructure has increased dramatically. This complexity and the problems it causes stem not just from various new demands made of the routing infrastructure, but also from fundamental limitations in the ability of today's distributed infrastructure to scalably cope with new requirements.The limitations in today's routing system arise in large part from the fully distributed path-selection computation that the IP routers in an autonomous system (AS) must perform. To overcome this weakness, interdomain routing should be separated from today's IP routers, which should simply forward packets (for the most part). Instead, a separate Routing Control Platform (RCP) should select routes on behalf of the IP routers in each AS and exchange reachability information with other domains.Our position is that an approach like RCP is a good way of coping with complexity while being responsive to new demands and can lead to a routing system that is substantially easier to manage than today. We present a design overview of RCP based on three architectural principles path computation based on a consistent view of network state, controlled interactions between routing protocol layers, and expressive specification of routing policies and discuss the architectural strengths and weaknesses of our proposal.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
A Border Gateway Protocol 4 (BGP-4). Internet Draft draft-ietf-idr-bgp4-24.txt, work in progress, November 2003.
 
2
AGARWAL, S., CHUAH, C.-N., AND KATZ, R. H. OPCA: Robust interdomain policy routing and traffic control. In Proc. IEEE OpenArch (April 2003).
3
4
5
 
6
BATES,T.,CHANDRA, R., AND CHEN, E. BGP Route Reflection -An Alternative to Full Mesh IBGP. RFC 2796, April 2000.
7
 
8
DRAVES, R., KING, C., VENKATACHARY, S., AND ZILL, B. Constructing optimal IP routing tables. In Proc. IEEE INFOCOM (March 1999).
9
10
11
 
12
FEAMSTER, N., AND BALAKRISHNAN, H. Verifying the correctness of wide-area Internet routing. Tech. Rep. MIT-LCS-TR-948, Massachusetts Institute of Technology, May 2004.
13
 
14
FEAMSTER, N., REXFORD, J., SHAIKH, A., AND VAN DER MERWE, J. Routing control platform: Architecture and practical concerns. http://www.research.att.com/~kobus/rcp-tr.pdf, June 2004.
15
16
 
17
Forwarding and Control Element Separation (ForCES) Charter. http://www.ietf.org/html.charters/forces-charter.html.
 
18
GOODELL, G., AIELLO,W.,GRIFFIN,T.,IOANNIDIS, J., MCDANIEL,P.,AND RUBIN, A. Working around BGP: An incremental approach to improving security and accuracy of interdomain routing. In Proc. Network and Distributed Systems Security 2003, Internet Society (February 2003).
 
19
 
20
21
 
22
HANDLEY, M., HUDSON, O., AND KOHLER, E. XORP: An open platform for network research. In Proc. SIGCOMM Workshop on Hot Topics in Networking (HotNets) (October 2002).
 
23
HASKIN, D. A BGP/IDRP Route Server alternative to a full mesh routing. RFC 1863, October 1995.
 
24
HORING, S., MENARD, J. Z., STAEHLER, R. E., AND YOKELSON, B. J. Stored program controlled network: Overview. Bell System Technical Journal 61, 7 (September 1982), 1579--1588.
 
25
 
26
LAKSHMINARAYANAN, K., STOICA, I., AND SHENKER, S. Routing as a Service. Tech. Rep. UCB-CS-04-1327, UC Berkeley, 2004.
 
27
LAWSER, J. J., LECRONIER, R. E., AND SIMMS, R. L. Stored program controlled network: Generic network plan. Bell System Technical Journal 61, 7 (September 1982), 1589--1598.
 
28
MAHAJAN, R., WETHERALL, D., AND ANDERSON, T. Interdomain routing with negotiation. Tech. Rep. CSE-04-06-02, University of Washington, May 2004.
29
30
 
31
MCPHERSON, D., GILL,V.,WALTON, D., AND RETANA,A. Border gateway protocol (BGP) persistent route oscillation condition. RFC 3345, August 2002.
32
33
 
34
RouteScience. Whitepaper available from http://www.routescience.com/technology/tec_whitepaper.html.
 
35
SHAIKH, A., AND GREENBERG, A. OSPF monitoring: Architecture, design, and deployment experience. In Proc. First Symposium on Networked Systems Design and Implementation (NSDI) (San Francisco, CA, March 2004).
 
36
Sockeye. http://www.sockeye.com/.
 
37
SUBRAMANIAN, L., ROTH,V.,STOICA, I., SHENKER, S., AND KATZ, R. Listen and whisper: Security mechanisms for BGP. In Proc. First Symposium on Networked Systems Design and Implementation (NSDI) (San Francisco, CA, March 2004).
38
39
 
40
VILLAMIZAR, C., CHANDRA, R., AND GOVINDAN, R. BGP Route Flap Damping. RFC 2439, November 1998.
 
41
YANG, L., ET AL. Forwarding and Control Element Separation (ForCES) Framework. RFC 3746, April 2004.
42

CITED BY  24

Collaborative Colleagues:
Nick Feamster: colleagues
Hari Balakrishnan: colleagues
Jennifer Rexford: colleagues
Aman Shaikh: colleagues
Jacobus van der Merwe: colleagues