<?xml version="1.0" standalone="no"?>
                    <!DOCTYPE div SYSTEM "/www/backend/www-xml-443/dtd/caidaML.dtd">
                    <!-- do NOT ERASE the DOCTYPE declaration! --><div>


<tr bgcolor="#f4f4f4">
  <td>
<font face="helvetica,arial" size="2">
<b>URL:</b>
</font>
</td>
  <td>
<font face="helvetica,arial" size="2">
<a href="http://www.sigcomm.org/sigcomm2002/papers/rocketfuel.pdf">http://www.sigcomm.org/sigcomm2002/papers/rocketfuel.pdf</a>
</font>
  </td>
</tr>


<tr bgcolor="#e9e9e9">
  <td>
<font face="helvetica,arial" size="2">
<b>Entry Date:</b>
</font>
</td>
  <td>
<font face="helvetica,arial" size="2">
2002-5-30


</font>
  </td>
</tr>


<tr bgcolor="#f4f4f4">
  <td>
<font face="helvetica,arial" size="2">
<b>Abstract:</b>
</font>
</td>
  <td>
<font face="helvetica,arial" size="2">
To date, realistic ISP topologies have not been accessible to the research
community, leaving work that depends on topology on an uncertain footing. In
this paper, we present new Internet mapping techniques that have enabled us to
directly measure router-level ISP topologies. Our techniques reduce the number
of required traces compared to a brute-force, all-to-all approach by three
orders of magnitude without a significant loss in accuracy. They include the
use of BGP routing tables to focus the measurements, exploiting properties of
IP routing to eliminate redundant measurements, better alias resolution, and
the use of DNS to divide each map into POPs and backbone. We collect maps from
ten diverse ISPs using our techniques, and find that our maps are substantially
more complete than those of earlier Internet mapping efforts. We also report on
properties of these maps, including the size of POPs, distribution of router
outdegree, and the inter-domain peering structure. As part of this work, we
release our maps to the community.



</font>
  </td>
</tr>


<tr bgcolor="#e9e9e9">
  <td>
<font face="helvetica,arial" size="2">
<b>Results:</b>
</font>
</td>
  <td>
<font face="helvetica,arial" size="2">
<ul>
  <li>
  Presents new techniques to measure router-level ISP topologies. These and
  other techniques are used by Rocketfuel to discover ISP maps that consist of
  backbone, access and directly connected neighouring domain routers along with
  the IP-level interconnections between them.  The new techniques reduce the
  number of required traces compared to a brute-force, all-to-all approach by
  three orders of magnitude without significant loss in accuracy.

  The techniques used are:
  <ul>
    <li>
      Use of BGP routing tables (obtained from Routeviews) to focus
      measurements. Only traceroutes are performed that will likely transit the
      ISP.
    </li>

    <li>
      Exploiting properties of IP routing to eliminate likely redundant
      traceroutes.
    </li>

    <li>
      Alias resolution: Uses the existing technique (from Mercator) of
      eliciting a "UDP port unreachable" message (from Mercator). New techiques
      used are router identification hints such as IP identifier (IP
      fragmentation), ICMP rate-limiting by routers of "unreachable" messages,
      and TTL values in "unreachable" messages.
    </li>

    <li>
    o Use of hints embedded in DNS names to determine which routers belong
      to the ISP, the role of routers (e.g. backbone vs access), and the
      geographical location of routers (to determine POPs).
    </li>
  </ul>
  </li>

  <li>
  Collected maps from ten ISPs and claim that they are substantially more
  complete than earlier Internet mapping efforts. The maps and raw measurement
  data are released to the community.
  </li>

  <li>
  Report refined results for the distribution of POP sizes and router
  outdegree, and the inter-domain peering structure.
  </li>

  <li>
  Found that ISPs have differing backbone designs but similar POP designs.
  </li>

  <li>
  To evaluate the ISP maps produced by Rocketfuel the maps are compared with:

    <ul>
    <li>
      Public ISP maps. Found that public ISP maps often have missing POPs,
      optimistic deployment projections, and contain parts of partner networks
      of other IPSs.
    </li>

    <li>
      An email survey with three ISPs. Results are favorable.
    </li>

    <li>
      The total number of routers found by scanning sampled subnets. 41-79% of
      such routers were found by Rocketfuel (64-96% of backbone routers and
      35-92% of access routers).
    </li>
      
    <li>
      Peerings from Routeviews BGP tables. In the worst case (Sprint) 70% of
      peerings visible in RV were found. Rocketfuel finds a small number of
      additional peerings.  BGP tables find more small (low AS degree)
      neighbours, whereas Rocketfuel finds more large neighbours.
    </li>

    <li>
      Skitter maps. Rocketfuel finds seven times as many nodes and links in the
      area of focus. Skitter finds a small number of additional nodes and
      links.
    </li>
  </ul>
  </li>

  <li>
  To evaluate alias resolution, a comparison was made with:

    <ul>
    <li>
      Mercator. A superset of Mercator aliases was found which was almost
      three times as large.
    </li>

    <li>
      DNS-predicted aliases of Ebone (119 out of 139 correct) and Sprint (240
      out of 303? correct).
    </li>
    </ul>
  </li>
</ul>



</font>
  </td>
</tr>


<tr bgcolor="#f4f4f4">
  <td>
<font face="helvetica,arial" size="2">
<b>Datasets:</b>
</font>
</td>
  <td>
<font face="helvetica,arial" size="2">
<ul>
  <li>
  Analysis of ten ISPs: Abovenet, AT&amp;T, Ebone, Exodus, Level3, Sprint,
  Telstra,
  Tiscali (Europe), Verio, VSNL (India), using 294 public traceroute servers
  representing 784 vantage points.
  </li>

  <li>
  Routeviews BGP table snapshots.
  </li>

  <li>
  Email survey of three ISPs.
  </li>

  <li>
  Public ISP maps.
  </li>

  <li>
  For comparison with Skitter:
  <ul>
    <li>Skitter data of Nov 27 2001 and Nov 28 2001.</li>
    <li>Rocketfuel data of Jan 2002.</li>
  </ul>
  </li>
</ul>


</font>
  </td>
</tr>


<tr bgcolor="#e9e9e9">
  <td>
<font face="helvetica,arial" size="2">
<b>References:</b>
</font>
</td>
  <td>
<font face="helvetica,arial" size="2">
<ul>
<li>Complements:
  <ul>
    <li>
    k. claffy, T. E. Monk, and D. McRobb. Internet tomography. In Nature,
    January 1999.
    </li>
  </ul>
</li>

<li>Refines some of:
  <ul>
    <li>
    M. Faloutsos, P. Faloutsos, and C. Faloutsos. On power-law relationships of
    the Internet topology. In ACM SIGCOMM, 1999.
    </li>

    <li>
    R. Govindan and H. Tangmunarunkit. Heuristics for Internet map discovery.
    In IEEE INFOCOM, 2000.
    </li>
  </ul>
</li>

<li>Comparable:
  <ul>
    <li>
    H. Burch and B. Cheswick. Mapping the Internet. IEEE Computer, 32(4):97 98,
    102, 1999.
    </li>

    <li>
    k. claffy, T. E. Monk, and D. McRobb. Internet tomography. In Nature,
    January 1999.
    </li>

    <li>
    R. Govindan and H. Tangmunarunkit. Heuristics for Internet map discovery.
    In IEEE INFOCOM, 2000.
    </li>
  </ul>
</li>

<li>Builds on:
  <ul>
    <li>
    V. N. Padmanabhan and L. Subramanian. An investigation of geographic
    mapping techniques for Internet hosts. In ACM SIGCOMM, August 2001.
    </li>
  </ul>
</li>

</ul>



</font>
  </td>
</tr>
</div>

