<?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://ieeexplore.ieee.org/xpl/freeabs_all.jsp?tp=&amp;arnumber=4092228&amp;isnumber=4092164">http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?tp=&amp;arnumber=4092228&amp;isnumber=4092164</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">
2008-06-16


</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 problem of removing sensitive information from data before it is
released publicly, or turned over to less trusted analysts, underlies
much of the unwillingness to share data. The solution is to sanitize, or
deidentify, parts of the data. When dealing with network addresses, the
set of available addresses is finite. This limits some aspects of the
sanitization. We analyze this problem in detail, and suggest approaches
to ameliorate it



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

