<?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.springerlink.com/index/9m5715325617164p.pdf">http://www.springerlink.com/index/9m5715325617164p.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">
The lack of adoption of a DNS-based geographic location service as proposed in RFC 1876 has lead to the deployment of
alternative ways to locate Internet hosts. The two main alternatives rely either on active probing of individual hosts or on
doing exhaustive tabulation of IP address ranges and their corresponding locations. Using active measurements, we show that the
geographic span of blocks of IP addresses make their location difficult to choose. Using the single location for a block of IP
addresses as an estimation of the location of its IP addresses leads to significant localization errors, whatever the choice
made for the location of the block. Even using as the location of a block the one that minimizes the global localization error
for all its IP addresses leads to large errors. The notion of the geographic span of a block of IP addresses is fuzzy, and
depends in practice very much on the uncertainty associated to the location estimates of its IP addresses.



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

