@conference {18560,
	title = {Design and implementation of a routing control platform},
	booktitle = {Proceedings of the 2nd conference on Symposium on Networked Systems Design \& Implementation - Volume 2},
	series = {NSDI{\textquoteright}05},
	year = {2005},
	month = {2005///},
	pages = {15 - 28},
	publisher = {USENIX Association},
	organization = {USENIX Association},
	address = {Berkeley, CA, USA},
	abstract = {The routers in an Autonomous System (AS) must distribute the information they learn about how to reach external destinations. Unfortunately, today{\textquoteright}s internal Border Gateway Protocol (iBGP) architectures have serious problems: a "full mesh" iBGP configuration does not scale to large networks and "route reflection" can introduce problems such as protocol oscillations and persistent loops. Instead, we argue that a Routing Control Platform (RCP) should collect information about external destinations and internal topology and select the BGP routes for each router in an AS. RCP is a logically-centralized platform, separate from the IP forwarding plane, that performs route selection on behalf of routers and communicates selected routes to the routers using the unmodified iBGP protocol. RCP provides scalability without sacrificing correctness. In this paper, we present the design and implementation of an RCP prototype on commodity hardware. Using traces of BGP and internal routing data from a Tier-1 backbone, we demonstrate that RCP is fast and reliable enough to drive the BGP routing decisions for a large network. We show that RCP assigns routes correctly, even when the functionality is replicated and distributed, and that networks using RCP can expect comparable convergence delays to those using today{\textquoteright}s iBGP architectures.},
	url = {http://dl.acm.org/citation.cfm?id=1251203.1251205},
	author = {Caesar,Matthew and Caldwell,Donald and Feamster, Nick and Rexford,Jennifer and Shaikh,Aman and van der Merwe,Jacobus}
}
