Matthew Caesar and Jennifer Rexford

EECS Department
University of California, Berkeley
Technical Report No. UCB/CSD-05-1377
2005

http://www2.eecs.berkeley.edu/Pubs/TechRpts/2005/CSD-05-1377.pdf

The Internet has quickly evolved into a vast global network owned and operated by thousands of different administrative entities. During this time, it became apparent that vanilla shortest-path routing would be insufficient to handle the myriad operational, economic, and political factors involved in routing. ISPs began to modify routing configurations to support routing policies, i.e. goals held by the router's owner that controlled which routes were chosen and which routes were propagated to neighbors. BGP, originally a simple path-vector protocol, was incrementally modified over time with a number of mechanisms to support policies, adding substantially to the complexity. Much of the mystery in BGP comes not only from the protocol complexity but also from a lack of understanding of the underlying policies and the problems ISPs face which they address. In this paper we shed light on goals operators have and their resulting routing policies, why BGP evolved the way it did, and how common policies are implemented using BGP. We also discuss recent and current work in the field that aims to address problems that arise in applying and supporting routing policies.

BibTeX citation:

@techreport{Caesar:CSD-05-1377,
    Author = {Caesar, Matthew and Rexford, Jennifer},
    Title = {BGP Routing Policies in ISP Networks},
    Institution = {EECS Department, University of California, Berkeley},
    Year = {2005},
    URL = {http://www2.eecs.berkeley.edu/Pubs/TechRpts/2005/6507.html},
    Number = {UCB/CSD-05-1377},
    Abstract = {The Internet has quickly evolved into a vast global network owned and operated by thousands of different administrative entities. During this time, it became apparent that vanilla shortest-path routing would be insufficient to handle the myriad operational, economic, and political factors involved in routing. ISPs began to modify routing configurations to support routing policies, i.e. goals held by the router's owner that controlled which routes were chosen and which routes were propagated to neighbors. BGP, originally a simple path-vector protocol, was incrementally modified over time with a number of mechanisms to support policies, adding substantially to the complexity. Much of the mystery in BGP comes not only from the protocol complexity but also from a lack of understanding of the underlying policies and the problems ISPs face which they address. In this paper we shed light on goals operators have and their resulting routing policies, why BGP evolved the way it did, and how common policies are implemented using BGP. We also discuss recent and current work in the field that aims to address problems that arise in applying and supporting routing policies.}
}

EndNote citation:

%0 Report
%A Caesar, Matthew
%A Rexford, Jennifer
%T BGP Routing Policies in ISP Networks
%I EECS Department, University of California, Berkeley
%D 2005
%@ UCB/CSD-05-1377
%U http://www2.eecs.berkeley.edu/Pubs/TechRpts/2005/6507.html
%F Caesar:CSD-05-1377