Towards an accurate AS-level traceroute tool
Proceedings of the 2003 conference on Applications, technologies, architectures, and protocols for computer communications
DIMES: let the internet measure itself
ACM SIGCOMM Computer Communication Review
Avoiding traceroute anomalies with Paris traceroute
Proceedings of the 6th ACM SIGCOMM conference on Internet measurement
iPlane: an information plane for distributed services
OSDI '06 Proceedings of the 7th USENIX Symposium on Operating Systems Design and Implementation - Volume 7
Observing the evolution of internet as topology
Proceedings of the 2007 conference on Applications, technologies, architectures, and protocols for computer communications
In search of the elusive ground truth: the internet's as-level connectivity structure
SIGMETRICS '08 Proceedings of the 2008 ACM SIGMETRICS international conference on Measurement and modeling of computer systems
Scamper: a scalable and extensible packet prober for active measurement of the internet
IMC '10 Proceedings of the 10th ACM SIGCOMM conference on Internet measurement
A Socratic method for validation of measurement-based networking research
Computer Communications
Measured impact of crooked traceroute
ACM SIGCOMM Computer Communication Review
Revisiting IP-to-AS mapping for AS-level traceroute
Proceedings of The ACM CoNEXT Student Workshop
On the incompleteness of the AS-level graph: a novel methodology for BGP route collector placement
Proceedings of the 2012 ACM conference on Internet measurement conference
DataTraffic Monitoring and Analysis
| Hi-index | 0.00 |
Although traceroute has the potential to discover AS links that are invisible to existing BGP monitors, it is well known that the common approach for mapping router IP address to AS number (IP2AS) based on the longest prefix matching is highly error-prone. In this paper we conduct a systematic investigation into the potential errors of the IP2AS mapping for AS topology inference. In comparing traceroute-derived AS paths and BGP AS paths, we take a novel approach of identifying mismatch fragments between each path pair. We then identify the origin and cause of each mismatch with a systematic set of tests based on publicly available data sets. Our results show that about 60% of mismatches are due to IP address sharing between peering BGP routers in neighboring ASes, and only about 14% of the mismatches are caused by the presence of IXPs, siblings, or prefixes with multiple origin ASes. This result helps clarify an argument that comes from previous work regarding the major cause of errors in converting traceroute paths to AS paths. Our results also show that between 16% and 47% of AS adjacencies in two public repositories for traceroute-derived topology are false.