<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:"맑은 고딕";}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1616402518;
mso-list-template-ids:757739954;}
@list l1
{mso-list-id:1826360032;
mso-list-template-ids:-317704942;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Dear Thick WHOIS IRT,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Below is a brief update on the project status;<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt">The transition from Thin to Thick for .JOBS remains on schedule. On 1 August 2017 .JOBS began accepting Thick data from registrars. On 1 September 2017, their
first monthly Transition Progress Metrics report was received per the policy “<i>4.7 Between 1 August 2017 and 1 February 2019, Registry Operator SHALL provide to ICANN all Transition Progress Metrics for all registrars at minimum, Monthly by 23:59 UTC of
the first day of the next month.” </i>Per the report, over 2000 domain names have made the transition with multiple registrars participating. We will continue to provide updates as we receive them.<o:p></o:p></span></li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt">As previously
<i><a href="https://www.icann.org/news/blog/thick-whois-transition-update"><span style="font-style:normal">reported</span></a></i>, per a request from Verisign, the 1 August 2017 transition date for .COM and .NET, has been rescheduled to 29 November 2017.
<i><o:p></o:p></i></span></li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt">Verisign and Registrar Stakeholder Group (RrSG) reached an impasse when they could not agree on a Registry-Registrar Agreement (RRA). Verisign believes that
changes in this RRA are necessary to address the legal risk and obligation of accepting Thick WHOIS data. The RrSG has raised several concerns stating they need clarity regarding the impact of GDPR on ICANN contracts before proceeding with Verisign’s proposed
RRA.<o:p></o:p></span></li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt">According to the RRA amendment<a href="https://www.icann.org/resources/pages/rra-amendment-procedure-2015-04-06-en"> procedure</a>, ICANN, as the ultimate approver
of the RRA, is to work with the registrars and Verisign to attempt to resolve the registrars’ concerns prior to ICANN’s approval or rejection of the RRA. Since April of 2017, ICANN has facilitated multiple in person and telephonic meetings with Verisign and
the RrSG leadership, but no significant progress has been made by either party. Recently, the RrSG has<a href="https://www.icann.org/en/system/files/correspondence/bunton-to-atallah-17aug17-en.pdf"> written</a> to ICANN organization requesting an extension
to the Policy effective dates of 1 May 2018 and 1 February 2019.<o:p></o:p></span></li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt">ICANN60: A public session for the Thick WHOIS Policy Implementation Review Team has been requested for 1215-1315 on Monday, 30 October 2017. As we get closer
to the meeting, we’ll confirm the time and location and provide a meeting invite for the IRT.<o:p></o:p></span></li></ol>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">— <o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Kind Regards,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Dennis S. Chang<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">GDD Services & Engagement Program Director<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">+1 213 293 7889<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Skype: dennisSchang<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">www.icann.org "One World, One Internet"<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>