<HTML><HEAD>
<META charset=US-ASCII http-equiv=Content-Type content="text/html; charset=US-ASCII">
<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; BACKGROUND-COLOR: #ffffff">
<DIV>
<DIV>This is great, Milton. Chris, I am glad you raised the issue. </DIV>
<DIV>I think that Milton's words below echo our NCUC presentation in Tunisia, </DIV>
<DIV>and will make a terrific conclusion (opening?) to the comments I drafted. </DIV>
<DIV>Together we explain our concerns and then the alternatives that resolve them.</DIV>
<DIV>Not bad :-) Kathy</DIV>
<DIV><BR><FONT face=Arial><<If Whois data remains fully accessible on a public and <BR>anonymous basis, we strongly favor the elimination of all <BR>personally identifiable contact data as a required element <BR>of Whois except for:<BR><BR>Registrant Name<BR>Registrant Country of Residence<BR><BR>Technical Contact Name <BR>Technical Contact Address <BR>Technical Contact E Mail address <BR>Technical Contact Phone number <BR>Technical Contact Fax number <BR><BR>All other data elements containing contact information, <BR>including new ones desired by other constituencies, could <BR>be continued as voluntary elements; i.e., registrants <BR>would have the right to fill them out or leave them blank as <BR>desired. <BR><BR>We favor continued mandatory inclusion of the following data <BR>elements:<BR><BR>Domain Status <BR>Domain Name ID <BR>Domain Name <BR>Registrar ID* <BR>Name of Registrar <BR>Name Server(s) <BR>Name Server ID* <BR><BR>Most of these are technical in nature. Note that we have <BR>eliminated domain creation and expiration dates. <BR>We believe that the inclusion of that information promotes <BR>spamming and manipulative or fraudulent service offerings <BR>from competing registrars. We can think of no legitimate purpose <BR>that is served by requiring that information to be public; for <BR>example, when one looks up someone's telephone number in a <BR>white pages directory there is no statement about when the <BR>line was rented. If that information is necessary for law <BR>enforcement purposes it can be subpoenaed from registrar <BR>records. <BR><BR>Our recommendations are intended to return Whois to its <BR>original purpose as a technical coordination vehicle. We note <BR>that the best way to improve accuracy of the data is to <BR>provide privacy and security. Domain name registrants' <BR>incentives to provide accurate information will dramatically <BR>increase once they feel the information is secure. <BR><BR>If these data elements are not fully removed from the Whois <BR>database, NCUC favors immediate adoption of privacy <BR>protections for the WHOIS fields, and the creation of an <BR>"opt-out" policy that allows a domain name registrant to fully <BR>understand and freely choose whether or not to allow his/her <BR>personal data to be published in worldwide directories and <BR>available anonymously in any form. These options would apply <BR>to all of the data elements we favor removing from the data <BR>elements above. <BR><BR>===END OF PROPOSAL===</FONT></DIV></DIV>
<DIV></DIV></BODY></HTML>