<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
FYI:<br><div><br><div>Begin forwarded message:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>From: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica">"<a href="mailto:GNSO.SECRETARIAT@GNSO.ICANN.ORG">GNSO.SECRETARIAT@GNSO.ICANN.ORG</a>" <<a href="mailto:gnso.secretariat@gnso.icann.org">gnso.secretariat@gnso.icann.org</a>></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>Date: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica">December 24, 2007 12:40:42 PM PST</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>To: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica">"council >> 'Council GNSO'" <<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>Subject: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica"><b>[council] Update: ICANN Projects Underway to Improve Whois Accuracy</b></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div> <div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">[To: council[at]gnso.icann.org; liaison6c[at]gnso.icann.org]</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">[To: ga[at]gnso.icann.org; announce[at]gnso.icann.org]</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">[To: regional-liaisons[at]icann.org]</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a href="http://www.icann.org/announcements/announcement-2-21dec07.htm">http://www.icann.org/announcements/announcement-2-21dec07.htm</a></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Update: ICANN Projects Underway to Improve Whois Accuracy</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">21 December 2007</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">The following compliance projects, intended to improve Whois data accuracy and Whois service accessibility, are underway by ICANN.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">I. ICANN Commences Whois Data Accuracy Study</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a href="http://www.icann.org/announcements/announcement-2-21dec07.htm#I">http://www.icann.org/announcements/announcement-2-21dec07.htm#I</a></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">II. Registrar Whois Data Reminder Policy Audit</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a href="http://www.icann.org/announcements/announcement-2-21dec07.htm#II">http://www.icann.org/announcements/announcement-2-21dec07.htm#II</a></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">III. Registrar Investigation of Whois Inaccuracy Claims Audit</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a href="http://www.icann.org/announcements/announcement-2-21dec07.htm#III">http://www.icann.org/announcements/announcement-2-21dec07.htm#III</a></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">IV. Whois Accessibility Study</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a href="http://www.icann.org/announcements/announcement-2-21dec07.htm#IV">http://www.icann.org/announcements/announcement-2-21dec07.htm#IV</a></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">I. ICANN Commences Whois Data Accuracy Study</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Over the years ICANN constituencies and others have observed apparent inaccuracies in Whois contact information provided by registrants when registering and maintaining their domain names. In an attempt to contribute to community discussion regarding Whois policy, ICANN has undertaken a study of domain name Whois contact information accuracy.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">With a great deal of Internet community interest behind it, ICANN commenced this study in November 2007 by developing a sampling plan to draw a representative sample of domain names from the gTLD name population.<span class="Apple-converted-space"> </span>In consultation with a statistician, ICANN developed an algorithm to determine the appropriate sample population size – one that provides acceptable accuracy and certainty levels. In the first phase of this study, ICANN will select a sample from what is (for statistical purposes) an infinitely large data base that will provide a measure of accuracy to +/- 5% with a certainty of 95%.<span class="Apple-converted-space"> </span>Staff will then randomly select domain names in accordance with statistical sampling practices.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">ICANN is currently defining the steps staff will take to determine the accuracy of Whois contact information associated with each registered domain name and address within the representative sample.<span class="Apple-converted-space"> </span>It is ICANN’s goal to ensure that staff uses practical and reasonably reliable means to assess accuracy of each data set.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">After finalizing the methodology to determine the Whois data accuracy of each data set, staff will execute the steps for each registered domain name within the representative sample.<span class="Apple-converted-space"> </span>Staff anticipates several steps will be necessary to determine Whois data accuracy.<span class="Apple-converted-space"> </span>Therefore, staff will conduct this study in phases.<span class="Apple-converted-space"> </span>ICANN will publish status reports as staff completes work in connection with each phase of the study.<span class="Apple-converted-space"> </span>The first report regarding this study will be published by February 2008.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">II. Registrar Whois Data Reminder Policy Audit</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">ICANN adopted the Whois Data Reminder Policy (WDRP), through the consensus policy process, on 27 March 2003. Partially aided by staff audit and compliance efforts, there is a very high level of compliance by registrars with this policy implementation. This is illustrated by the fact that most registrar activities in compliance with this requirement are timed to occur coincidentally with the annual ICANN compliance audit.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">The WDRP requires all Registrars to:</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span class="Apple-converted-space"> </span>* present current Whois information to each registrant on an annual basis.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span class="Apple-converted-space"> </span>* request each registrant review the information and if necessary, make any corrections.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span class="Apple-converted-space"> </span>* remind each registrant that the provision of false Whois information can be grounds for cancellation of their domain name.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">All ICANN-accredited registrars must comply with the WDRP for registrations they sponsor in all top-level domains for which they are accredited.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">The WDRP audit requests that all registrars respond to a survey designed to obtain information regarding registrar compliance with the WDRP. Additionally, ICANN request registrars to provide a sample copy of the WDRP notice transmitted to their registrants for assessment by ICANN staff.<span class="Apple-converted-space"> </span>Staff determines whether the notice is compliant with WDRP requirements.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">ICANN transmitted the WDRP survey to ICANN-accredited registrars in October 2007.<span class="Apple-converted-space"> </span>Registrars were given until 16 November 2007 to respond to the WDRP survey and provide a copy of their WDRP notices.<span class="Apple-converted-space"> </span>ICANN will publish its 2007 WDRP Report in February 2008. As has become tradition, ICANN has witnessed registrar compliance with this contractual requirement, sending the notices to registrants, within the past few weeks.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">III. Registrar Investigation of Whois Inaccuracy Claims Audit</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">ICANN commenced an audit in November 2007 to assess registrar compliance with Registrar Accreditation Agreement (RAA) requirements concerning the investigation of Whois inaccuracy claims filed through ICANN’s Whois Data Problem Report System (WDPRS).</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">ICANN’s WDPRS receives and tracks complaints regarding incomplete or inaccurate Whois data entries. ICANN assesses and reports annually the WDPRS activity and apparent level of success this tool has in improving Whois accuracy. As a result, ICANN can make a preliminary determination as to whether complaints of inaccuracy are routinely investigated by registrars. This investigation is a contractual requirement.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">ICANN recently transmitted Notices of Concern to registrars that appeared to take inadequate action in response to WDPRS complaints. Prior to sending the notices, staff analyzed complaints and complainant follow-up correspondence. As an example, the Notices of Concern included a sample of domain names complainants filed as of 7 July 2007 that remained unchanged on 7 December 2007.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Staff requested registrars provide ICANN with details regarding the steps taken to investigate the claimed inaccuracies as required by Section 3.7.8 of the RAA.<span class="Apple-converted-space"> </span>If after analyzing registrar responses ICANN determines that registrars breached section 3.7.8 of the RAA, ICANN will issue breach notices to those registrars not in compliance with this requirement and who have not filed a plan to cure this failure. ICANN will publish a report regarding the purpose, methodology and findings concerning the Registrar Investigation of Whois Inaccuracy Claims Audit by February 2008.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">IV. Registrar Whois Accessibility Audit</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span class="Apple-converted-space"> </span>Pursuant to Section 3.3.1 of the RAA, a registrar is required to provide free port 43 Whois service, allowing the public query-based access to up-to-date data concerning all active registered gTLD names under the registrar’s sponsorship.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">To monitor and enforce registrar compliance with port 43 Whois service requirements, ICANN developed an application to regularly, and on an ongoing basis, determine if registrars maintain port 43 Whois service for public use. ICANN’s new application is being used to conduct a Registrar Whois Accessibility Audit.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">After obtaining gTLD names from VeriSign, ICANN selected up to five (5) domain names from each unique registrar in the VeriSign Whois database. [1] ICANN used the domain names selected to query the Whois servers of 850 registrars to determine if the registrars were providing free port 43 Whois service as required by the RAA. Responses to ICANN’s queries were divided into five (5) categories. [2] The first query revealed that 745 registrars returned “good” responses indicating that the Whois service for those 745 registrars was available to the public at the time of the query. ICANN is examining the responses that were not returned “good” and where appropriate, informing registrars of port 43 Whois service violations. To monitor whether registrars’ port 43 Whois services are functioning in conformance with RAA requirements, ICANN will commence regular, weekly queries and inform registrars when port 43 Whois service violations are observed. A report regarding the Registrar Whois Accessibility Audit will be published in February 2008.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">--<span class="Apple-converted-space"> </span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Glen de Saint Géry</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">GNSO Secretariat - ICANN</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">gnso.secretariat[at]gnso.icann.org</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a href="http://gnso.icann.org">http://gnso.icann.org</a></div> </blockquote></div><br><div> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div><br class="Apple-interchange-newline"><br class="khtml-block-placeholder"></div><div><br class="khtml-block-placeholder"></div><div>IP JUSTICE</div><div>Robin Gross, Executive Director</div><div>1192 Haight Street, San Francisco, CA 94117 USA</div><div>p: +1-415-553-6261 f: +1-415-462-6451</div><div>w: <a href="http://www.ipjustice.org">http://www.ipjustice.org</a> e: <a href="mailto:robin@ipjustice.org">robin@ipjustice.org</a></div><br class="Apple-interchange-newline"></span><br class="Apple-interchange-newline"> </div><br></body></html>