Automated Provisioning of BGP Customers

IEEE Network

Volumn 17, Issue 6, 2003, Pages 44-55

  Gottlieb, Joel ^a,b   Greenberg, Albert ^a,c,d   Rexford, Jennifer ^a,b   Wang, Jia ^a,b  

^a AT AND T LABS RESEARCH   (United States)

^b AT AND T LABS RESEARCH   (United States)

^c LUCENT TECHNOLOGIES   (United States)

^d Network Services Research Center   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

BORDER GATEWAY PROTOCOLS (BGP);

DATABASE SYSTEMS; INTERFACES (COMPUTER); INTERNET; ROUTERS; TELECOMMUNICATION SERVICES;

NETWORK PROTOCOLS;

EID: 0344583783     PISSN: 08908044     EISSN: None     Source Type: Journal    
DOI: 10.1109/MNET.2003.1248660     Document Type: Article

References (13)

1. Y. Rekhter and T. Li, "A Border Gateway Protocol 4 (BGP-4)," IETF RFC 1771, Mar. 1995.
2. J. W. Stewart, BGP4: Inter-Domain Routing in the Internet, Addison-Wesley, Jan. 1999.
3. R. Mahajan, D. Wetherall, and T. Anderson, "Understanding BGP miscongurations," Proc. ACM SIGCOMM, Aug. 2002.
4. S. Halabi and D. McPherson, Internet Routing Architectures, 2nd ed., Cisco Press, 2001.
5. I. van Beijnum, BGP: Building Reliable Networks with the Border Gateway Protocol, O'Reilly, Sept. 2002.
6. IANA, "Special-Use IPv4 Addresses," IETF RFC 3330, Sept. 2002.
7. J. Hawkinson and T. Bates, "Guidelines for Creation, Selection, and Registration of an Autonomous System (AS)," IETF RFC 1930, Mar. 1996.
8. G. Huston, "Interconnection, Peering, and Settlements," Proc. INET, June 1999.
9. E. Chen and J. Stewart, "A Framework for Inter-Domain Route Aggregation," IETF RFC 2519, Feb. 1999.
10. C. Alaettinoglu et al., "Routing Policy Specification Language (RPSL)," IETF RFC 2622, Aug. 1999.
11. D. Meyer et al., "Using RPSL in Practice," IETF RFC 2650, June 1999.
12. J. Stewart et al., "Using a Dedicated AS for Sites Homed to a Single Provider," IETF RFC 2270, Jan. 1998.
13. P. Ferguson and D. Senie, "Network Ingress Filtering: Defeating Denial of Service Attacks which Employ IP Source Address Spooling," IETF RFC 2267, Jan. 1998.