Dear Team members,<br><br>Thank you, again, for participating in this conference call with ICANN Staff. <br><br>Below, and attached, is a summary of the Team's recommendations to help facilitate our discussion. <div>
<br>Regards,<br>Denise<br><br>Denise Michel<br>ICANN<br>Advisor to the President & CEO<br><a href="mailto:denise.michel@icann.org">denise.michel@icann.org</a><br>+1.408.429.3072 mobile<br>+1.310.578.8632 direct<div><br>
</div><div>
<table class="MsoTableLightListAccent1" border="1" cellspacing="0" cellpadding="0" align="left" width="732" style="width:731.7pt;border-collapse:collapse;border:none;margin-left:6.0pt;margin-right:6.0pt">
<tbody><tr style="height:7.15pt">
<td width="732" valign="top" style="width:731.7pt;border:solid #4f81bd 1.0pt;border-bottom:none;background:#4f81bd;padding:0in 5.4pt 0in 5.4pt;height:7.15pt">
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:.25in"><b><span style="font-size:9.0pt;font-family:Arial;color:white">WHOIS Policy Review Team Draft
Report Recommendations</span></b></p>
</td>
</tr>
<tr style="height:7.15pt">
<td width="732" valign="top" style="width:731.7pt;border:solid #4f81bd 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:7.15pt">
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><b><span style="font-size:9.0pt;font-family:Arial">Single WHOIS Policy</span></b></p>
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><span style="font-size:9.0pt;font-family:Arial">1) ICANN's WHOIS
policy is poorly defined and decentralized; Team recommends Board oversee
creation and publication of a single WHOIS policy document; include gTLD
WHOIS policy in Registry & Registrar contracts, GNSO consensus policies
& procedures.</span></p>
</td>
</tr>
<tr style="height:7.15pt">
<td width="732" valign="top" style="width:731.7pt;border-top:none;border-left:solid #4f81bd 1.0pt;border-bottom:none;border-right:solid #4f81bd 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:7.15pt">
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><b><span style="font-size:9.0pt;font-family:Arial">Policy Review – WHOIS Data Reminder Policy (WDRP)</span></b></p>
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><span style="font-size:9.0pt;font-family:Arial">2) Board should
ensure that Compliance develops metrics to track impact of annual data
reminder notices to registrants, and that these metrics be used to develop
and publish performance targets to improve data accuracy over time (if not
feasible, develop & implement an alternative policy). </span></p>
</td>
</tr>
<tr style="height:7.15pt">
<td width="732" valign="top" style="width:731.7pt;border:solid #4f81bd 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:7.15pt">
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><b><span style="font-size:9.0pt;font-family:Arial">Strategic Priority</span></b></p>
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><span style="font-size:9.0pt;font-family:Arial">3) ICANN should
make WHOIS a strategic priority, allocate sufficient resources to ensure
Compliance is fully resourced to take a proactive regulatory role, encourage
a culture of compliance; Board should ensure a senior member of the executive
team is responsible for overseeing WHOIS compliance.</span></p>
</td>
</tr>
<tr style="height:7.15pt">
<td width="732" valign="top" style="width:731.7pt;border-top:none;border-left:solid #4f81bd 1.0pt;border-bottom:none;border-right:solid #4f81bd 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:7.15pt">
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><b><span style="font-size:9.0pt;font-family:Arial">Outreach</span></b></p>
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><span style="font-size:9.0pt;font-family:Arial">4) ICANN should
ensure that WHOIS policy issues are accompanied by cross-community outreach,
including outreach to interested communities outside of ICANN.</span></p>
</td>
</tr>
<tr style="height:7.15pt">
<td width="732" valign="top" style="width:731.7pt;border:solid #4f81bd 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:7.15pt">
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><b><span style="font-size:9.0pt;font-family:Arial">Data Accuracy</span></b></p>
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><span style="font-size:9.0pt;font-family:Arial">5) ICANN should
take appropriate measures to reduce the number of unreachable WHOIS registrations
(as defined by the 2010 NORC Data Accuracy Study) by 50% within 12 months and
by 50% again over the following 12 months.</span></p>
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><span style="font-size:9.0pt;font-family:Arial">6) ICANN shall
publish annually an accuracy report on measured reduction in “unreachable
WHOIS registrations.”</span></p>
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><span style="font-size:9.0pt;font-family:Arial">7) ICANN should
publish status reports (at least annually) (with figures) on its progress
towards achieving goals set out by the Team, the first to be issued before
next review.</span></p>
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><span style="font-size:9.0pt;font-family:Arial">8) ICANN should
ensure that there is a clear, unambiguous and enforceable chain of contractual
agreements with Registries, Registrars, and Registrants to require the
provision and maintenance of accurate WHOIS data; as part of this, ICANN
should ensure that clear, enforceable and graduated sanctions apply to
Registries, Registrars, Registrants that don’t comply with WHOIS policies,
including de-registration and/or de-accreditation for serious or serial
non-compliance.</span></p>
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><span style="font-size:9.0pt;font-family:Arial">9) ICANN should
ensure that requirements for accurate WHOIS data are widely and pro-actively
communicated to current and prospective registrants, and should ensure that
its Registrant Rights and Responsibilities document is pro-actively, prominently
circulated to all new and renewing registrants.</span><span style="font-size:9.0pt;font-family:Arial"> </span></p>
</td>
</tr>
<tr style="height:7.15pt">
<td width="732" valign="top" style="width:731.7pt;border-top:none;border-left:solid #4f81bd 1.0pt;border-bottom:none;border-right:solid #4f81bd 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:7.15pt">
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><b><span style="font-size:9.0pt;font-family:Arial">Data Access – Privacy Services</span></b></p>
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><span style="font-size:9.0pt;font-family:Arial">10) ICANN should
develop and manage a system of clear, consistent and enforceable requirements
for all privacy services consistent with national laws, balancing between
stakeholders with competing but legitimate interests, including, at a
minimum, privacy, law enforcement and industry around LE. These should include: WHOIS entry must
clearly label that this is a private registration; privacy services must
provide full contact details as required that are available and responsive (see
above); standardized relay and reveal processes and timeframes; rules for the
appropriate level of publicly available information on the Registrant; maintenance
of a dedicated abuse point of contact for the privacy service provider; privacy
service provider shall conduct periodic due diligence checks.</span></p>
</td>
</tr>
<tr style="height:7.15pt">
<td width="732" valign="top" style="width:731.7pt;border:solid #4f81bd 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:7.15pt">
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in"><span style="font-size:9.0pt;font-family:Arial">11) ICANN should develop a graduated and enforceable series of
penalties for privacy service providers who violate the requirements, with a
clear path to de-accreditation for repeat, serial</span></p>
</td>
</tr>
<tr style="height:19.8pt">
<td width="732" valign="top" style="width:731.7pt;border-top:none;border-left:solid #4f81bd 1.0pt;border-bottom:none;border-right:solid #4f81bd 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:19.8pt">
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><b><span style="font-size:9.0pt;font-family:Arial">Data Access - Proxy Services</span></b></p>
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><span style="font-size:9.0pt;font-family:Arial">12) ICANN should
facilitate the review of existing practices by reaching out to proxy
providers to create a discussion that sets out current processes followed by
these providers.</span><span style="font-size:9.0pt;font-family:Arial"></span></p>
</td>
</tr>
<tr style="height:11.7pt">
<td width="732" valign="top" style="width:731.7pt;border:solid #4f81bd 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:11.7pt">
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><span style="font-size:9.0pt;font-family:Arial">13) Registrars
should be required to disclose to ICANN their relationship with any
Affiliated Retail proxy service provider.</span></p>
</td>
</tr>
<tr style="height:43.65pt">
<td width="732" valign="top" style="width:731.7pt;border-top:none;border-left:solid #4f81bd 1.0pt;border-bottom:none;border-right:solid #4f81bd 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:43.65pt">
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><span style="font-size:9.0pt;font-family:Arial">14) ICANN should
develop a set of voluntary best practice guidelines for appropriate proxy
services</span> <span style="font-size:9.0pt;font-family:Arial">consistent with national laws, striking a balance between
stakeholders with competing but legitimate interests, including, at a
minimum, privacy, law enforcement and industry around LE. Voluntary
guidelines may include: proxy services provide full contact details as
required; publication by the proxy service of its process for revealing and
relaying information; standardization of reveal/relay processes & timeframes,
consistent with national laws; maintenance of a dedicated abuse point of
contact for the proxy service provider; due diligence checks on licensee
contact information.</span></p>
</td>
</tr>
<tr style="height:17.1pt">
<td width="732" valign="top" style="width:731.7pt;border:solid #4f81bd 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:17.1pt">
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><span style="font-size:9.0pt;font-family:Arial">15) ICANN should
encourage and incentivize registrars to interact with the retail service
providers that adopt the best practices.</span></p>
</td>
</tr>
<tr style="height:26.1pt">
<td width="732" valign="top" style="width:731.7pt;border-top:none;border-left:solid #4f81bd 1.0pt;border-bottom:none;border-right:solid #4f81bd 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:26.1pt">
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><span style="font-size:9.0pt;font-family:Arial">16) The
published WHOIS Policy should include an affirmative statement that clarifies
that a proxy means a relationship in which the Registrant is acting on behalf
of another; the WHOIS data is that of the agent, and the agent alone obtains
all rights and assumes all responsibility for the domain name and its manner
of use.</span></p>
</td>
</tr>
<tr style="height:61.05pt">
<td width="732" valign="top" style="width:731.7pt;border:solid #4f81bd 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:61.05pt">
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><b><span style="font-size:9.0pt;font-family:Arial">Data Access – Common
Interface</span></b></p>
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><span style="font-size:9.0pt;font-family:Arial">17) To improve
access to the WHOIS data of .COM & .NET gTLDs (the Thin Registries),
ICANN should set-up a dedicated, multilingual interface website to provide
thick WHOIS data for them. (An “Alternative for public comment”: to make
WHOIS data more accessible for consumers, ICANN should set-up a dedicated,
multilingual interface website to allow “unrestricted and public access to
accurate and complete WHOIS information” to provide thick WHOIS data for all
gTLD domain names. </span></p>
</td>
</tr>
<tr style="height:114.75pt">
<td width="732" valign="top" style="width:731.7pt;border:solid #4f81bd 1.0pt;border-top:none;padding:0in 5.4pt 0in 5.4pt;height:114.75pt">
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><b><span style="font-size:9.0pt;font-family:Arial">Internationalized
Domain Names</span></b></p>
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><span style="font-size:9.0pt;font-family:Arial">18) The ICANN Community should task a working group (WG) within 6
months of publication to finalize (i) encoding, (ii) modifications to data
model, and (iii) internationalized services, to give global access to gather,
store and make available internationalized registration data. Such WG
should report no later than one year from formation, using existing IDN
encoding. The WG should aim for consistency of approach across gTLDs
and – on a voluntary basis – the ccTLD space.</span></p>
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><span style="font-size:9.0pt;font-family:Arial">19) The final data model and services should be incorporated and
reflected in Registrar and Registry agreements within 6 months of adoption of
the WG’s recommendations by the ICANN Board. If these recommendations
are not finalized in time for the next revision of such agreements, explicit
placeholders for this purpose should be put in place in the agreements for
the new gTLD program at this time, and in the existing agreements when they
come up for renewal (as is case for adoption of consensus policies).</span></p>
<p class="MsoNormal" style="margin-top:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in;background:white"><span style="font-size:9.0pt;font-family:Arial">20) Requirements for registration data accuracy and availability in
local languages should be finalized (following initial work by IRD-WG and
similar efforts, especially if translation or transliteration of data is
stipulated) along with the efforts on internationalization of registration
data. Metrics should be defined to measure accuracy and availability of data
in local languages and (if needed) corresponding data in ASCII, and
compliance methods and targets should be explicitly defined accordingly.</span></p>
</td>
</tr>
</tbody></table>
<p class="MsoNormal"> </p>
<br></div></div>