ACM Home Page
Please provide us with feedback. Feedback
Identifying BGP routing table transfers
Full text PdfPdf (292 KB)
Source Joint International Conference on Measurement and Modeling of Computer Systems archive
Proceedings of the 2005 ACM SIGCOMM workshop on Mining network data table of contents
Philadelphia, Pennsylvania, USA
SESSION: Routing & configuration management table of contents
Pages: 213 - 218  
Year of Publication: 2005
ISBN:1-59593-026-4
Authors
Beichuan Zhang  University of Arizona
Vamsi Kambhampati  Colorado State University
Mohit Lad  University of California, Los Angeles
Daniel Massey  Colorado State University
Lixia Zhang  University of California, Los Angeles
Sponsors
SIGCOMM: ACM Special Interest Group on Data Communication
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 0,   Downloads (12 Months): 26,   Citation Count: 1
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
Save this Article to a Binder    Display Formats: BibTex  EndNote ACM Ref   
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1080173.1080188
What is a DOI?

ABSTRACT

BGP routing updates collected by monitoring projects such as RouteViews and RIPE have been a vital source to our understanding of the global routing system. The updates logged by these monitoring projects are generated either by individual route changes, or are part of BGP table transfer. In particular, a session reset between a monitoring station and its BGP peers can result in the peer sending its entire BGP routing table to the monitoring station. In this paper, we present a Minimum Collection Time (MCT) algorithm that accurately identify the start and duration of routing table transfers. Using three months of data from 14 different peers, MCT can identify routing table transfers triggered by BGP session resets with 100% accuracy, and can pinpoint the exact starting time of table transfers in 90% of the cases.


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
Cisco documentation: Configuring BGP, 2003.
2
 
3
H. Kong. The consistency verification of Zebra BGP data collection. Technical report, Agilent Labs, China, 2003.
4
5
 
6
RIPE Routing Information Service. http://www.ripe.net/projects/ris/.
 
7
The RouteViews project. http://www.routeviews.org/.
8
 
9
J. Wu, Z.M. Mao, J. Rexford, and J. Wang. Finding a needle in a haystack: Pinpointing significant BGP routing changes in a IP network. In Symposium on Networked System Design and Implementation (NSDI), May 2005.


Collaborative Colleagues:
Beichuan Zhang: colleagues
Vamsi Kambhampati: colleagues
Mohit Lad: colleagues
Daniel Massey: colleagues
Lixia Zhang: colleagues