ACM Home Page
Please provide us with feedback. Feedback
A measurement framework for pin-pointing routing changes
Full text PdfPdf (121 KB)
Source Applications, Technologies, Architectures, and Protocols for Computer Communication archive
Proceedings of the ACM SIGCOMM workshop on Network troubleshooting: research, theory and operations practice meet malfunctioning reality table of contents
Portland, Oregon, USA
SESSION: Routing II table of contents
Pages: 313 - 318  
Year of Publication: 2004
ISBN:1-58113-942-9
Authors
Renata Teixeira  Univ. Calif. San Diego, La Jolla, CA
Jennifer Rexford  AT&T Labs--Research, Florham Park, NJ
Sponsors
SIGCOMM: ACM Special Interest Group on Data Communication
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 4,   Downloads (12 Months): 25,   Citation Count: 15
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/1016687.1016704
What is a DOI?

ABSTRACT

Changes in the end-to-end path between two hosts can lead to sudden changes in the round-trip time and available bandwidth, or even the complete loss of connectivity. Determining the reason for the routing change is crucial for diagnosing and fixing the problem, and for holding a particular domain accountable for the disruption. Active measurement tools like traceroute can infer the current path between two end-points, but not where and why the path changed. Analyzing BGP data from multiple vantage points seems like a promising way to infer the root cause of routing changes. In this paper, we explain the inherent limitations of using BGP data alone and argue for a distributed approach to troubleshooting routing problems. We propose a solution where each AS continuously maintains a view of routing changes in its own network, without requiring additional support from the underlying routers. Then, we describe how to query the measurement servers along the AS-level forwarding path from the source to the destination to uncover the location and the reason for the routing change.


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
V. Jacobson, "Traceroute." ftp://ftp.ee.lbl.gov/traceroute.tar.gz.
2
 
3
A. McGregor and M. Luckie, "IP measurement protocol (IPMP)." Internet Draft, draft-mcgregor-ipmp-04.txt, February 2004.
 
4
J. Bennett, "The case for an Internet Measurement Protocol," November 11 2003. E-mail posting on the Internet Measurement Research Group, http://www1.ietf.org/mail-archive/working-groups/imrg/current/msg00154.html.
5
6
 
7
"Route Views." http://www.routeviews.org.
 
8
"RIPE NCC RIS." http://www.ripe.net/ripencc/ris.
 
9
 
10
M. Caesar, L. Subramanian, and R. H. Katz, "Towards localizing root causes of BGP dynamics," Tech. Rep. CSD-03-1292, UC Berkeley, November 2003.
11
 
12
T. G. Griffin, "What is the sound of one route flapping?." presentation at the Network Modeling and Simulation Summer Workshop, 2002.
13
 
14
"A Border Gateway Protocol 4 (BGP-4)." Internet Draft draft-ietf-idr-bgp4-24.txt, work in progress, November 2003.
 
15
E. Chen and J. Stewart, "A Framework for Inter-Domain Route Aggregation," RFC 2519, IETF, February 1999.
 
16
G. Huston, "Interconnection, peering, and settlements," in Proc. INET, June 1999.
17
18
 
19
A. Shaikh and A. Greenberg, "OSPF monitoring: Architecture, design, and deployment experience," in Proc. USENIX/ACM NSDI, March 2004.
20
 
21
A. Feldmann, A. Greenberg, C. Lund, N. Reingold, and J. Rexford, "NetScope: Traffic engineering for IP networks," IEEE Network Magazine, pp. 11--19, March 2000.
 
22

CITED BY  15

Collaborative Colleagues:
Renata Teixeira: colleagues
Jennifer Rexford: colleagues