<?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.caida.org/publications/papers/1999/GTrace/GTrace.pdf">http://www.caida.org/publications/papers/1999/GTrace/GTrace.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">
2010-10-22


</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">
Traceroute [Jacobson88], originally written by Van Jacobson in 1988, has become a classic tool for determining the
routes that packets take from a source host to a destination host. It does not provide any information regarding the physical
location of each node along the route, which makes it difficult to effectively identify geographically circuitous unicast
routing. Indeed, there are examples of paths between hosts just a few miles apart that cross the entire United States and back,
phenomena not immediately evident from the textual output of traceroute. While such path information may not be of much
interest to many end users, it can provide valuable insight to system administrators, network engineers, operators and
analysts. We present a tool that depicts geographically the IP path information that traceroute provides, drawing the nodes on
a world map according to their latitude/longitude coordinates.




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

