A study on traceroute potentiality in revealing the Internet AS-level topology

Abstract

Several works over the past few years have shown that the Internet AS-level topology is partially hidden from the current Internet measurement infrastructures. Most have focused on the incompleteness of the connectivity extracted from BGP data. A few have analysed the connectivity collected by traceroute measurement infrastructures showing the amount of connections introduced by traceroute campaigns. None, however, have investigated in detail the underlying rationale, i.e. the economic nature of the Internet. In this paper we fill this gap by analysing five traceroute infrastructures, found to be active in October 2013, with the p2c-distance metric, which is specifically designed to capture the complex economic dynamics that rule the Internet. We found that the traceroute infrastructures that currently run topology discovery measurements (Ark, DIMES and Portolan), together with BGP route collectors, are able to reveal the full connectivity of 23.50% of the Internet core ASes. This is a considerable improvement given that the BGP infrastructure alone is able to cover only 15.90% of the Internet core. This percentage could be increased up to 48.48% if the remaining two infrastructures (Dasu/Ono and RIPE Atlas) performed topology discovery campaigns. We also found that the placement of traceroute probes is not optimal from a topology discovery perspective, as it causes several probes to provide only redundant connectivity information. We show that the same number of traceroute probes optimally deployed, would be able to completely reveal the full AS connectivity of the Internet core.

A worldwide study on the geographic locality of Internet routes

“…Thus, we group measurements by pairs of ASes. To obtain a reasonably wide coverage in terms of ASes and geographic spread, we choose to rely on RIPE Atlas [42], which is characterized by a significant presence in all the regions of the world [43]. The coverage of the collected dataset, in terms of address space, networks, 2 Some mechanisms could lead to different IP-level paths for (s 1 , d 1 ) and (s 2 , d 2 ), even when s 1 and s 2 belong to the same subnetwork s, and d 1 and d 2 belong to the same subnetwork d. Examples of such mechanisms include traffic engineering policies and load balancing.…”

Implementing and Evaluating Health as a Service in Fog and Cloud Computing using Raspberry Pi

“…The number of hops in Fog computing is one, but in case of Cloud computing, the number varies as it is in the WAN. Different Cloud servers are tested for their distance by the number of hops and by using "tracert" command [49][50][51]. It is shown in Table 4.…”

It Bends But Would It Break? Topological Analysis of BGP Infrastructures in Europe

“…Future work will focus on trying to complement existing data with a more exhaustive model of the infrastructure, drawing from different data sources. Several research initiatives have been recently started in this direction [85], [88], [89].…”