<meta name="viewport" content="width=device-width"/>
<span style="font-family: Tele-GroteskNCNor;font-size: 18px"><br><br><br>FYI<br><br>Best regards <br><br>Wolf-Ulrich Knoben </span>
<p style="font-family:Helvetica">
-----Original-Nachricht-----<br/>
<b>Von:</b> Marika Konings <<a href='mailto:marika.konings@icann.org'>marika.konings@icann.org</a>><br>
<b>Betreff:</b> [council] FW: Verisign request to extend Thick Whois Implementation Date<br>
<b>Datum:</b> 24.06.2017, 18:07 Uhr<br>
<b>An:</b> council@gnso.icann.org <<a href='mailto:council@gnso.icann.org'>council@gnso.icann.org</a>><br>
</p>
<html xmlns="http://www.w3.org/1999/xhtml"><head></head><body bgcolor="#FFFFFF" text="#000000"><div>
<div class="WordSection1">
<p class="MsoNormal">For your information, please see below.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Marika<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Karla Hakansson <karla.hakansson@icann.org><br>
<b>Date: </b>Saturday, June 24, 2017 at 16:12<br>
<b>To: </b>Marika Konings <marika.konings@icann.org><br>
<b>Cc: </b>Cyrus Namazi <cyrus.namazi@icann.org><br>
<b>Subject: </b>Verisign request to extend Thick Whois Implementation Date<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="font-family:"Calibri Light",sans-serif">Hello Marika,
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Calibri Light",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Calibri Light",sans-serif">Please communicate the following update to the GNSO:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Calibri Light",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Calibri Light",sans-serif">In the process of implementing the Thick Whois Policy for .com and .net, Verisign proposed certain Amendments to the COM/NET Registry Registrar Agreement (RRA) to fulfill their obligation
to begin accepting Thick Whois data from the registrars beginning 1 August 2017. Per the
<a href="https://www.icann.org/en/system/files/files/rra-amendment-procedure-25aug11-en.pdf">
published process</a>, ICANN forwarded the proposed RRA Amendments to the Registrar Stakeholder Group (RrSG) on 29 March 2017 to review and provide comments. On 21 April 2017 the RrSG formally objected to the proposed Amendment stating:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Calibri Light",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><i><span style="font-family:"Calibri Light",sans-serif">“…the .com/.net amendments have raised serious questions in the RrSG around how we'll operate and interact with .com/.net under the upcoming European GDPR,
and we feel we need clarity on these issues before the amendments can be accepted.</span></i><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in;text-indent:-.5in"><i><span style="font-family:"Calibri Light",sans-serif"> </span></i><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><i><span style="font-family:"Calibri Light",sans-serif">Indeed, the RrSG is now looking towards the impact of the GDPR on the 1000s of registries we regularly work with, and it's clear that we need to ensure we
have more clarity and understanding, as well as a solution for data handling that will work across ALL registries.”</span></i><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Calibri Light",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Calibri Light",sans-serif">Following this communication, the RrSG submitted a letter to ICANN and Verisign on 4 May 2017 requesting Verisign to modify its proposed Amendment, and for ICANN to create a data protection
policy in support of the RAA for both registries and registrars. </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in;text-indent:-.5in"><span style="font-family:"Calibri Light",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Calibri Light",sans-serif">Since the 4 May 2017 communication ICANN has facilitated multiple discussions between Verisign and the RrSG in an attempt to resolve the outstanding issues with the RRA Amendments. The
goal of those discussions has been to resolve the concerns about the proposed RRA Amendments so they can be in place by 1 July 2017. This deadline is imposed by Verisign to provide registrars with a thirty-day period in order for changes to the RRA to become
effective before Verisign begins accepting Thick Whois data in their production environment. As of 21 June 2017, the RRA Amendment has not been accepted by the RrSG. ICANN strives for consensus whenever possible before approving RRA amendments, and without
further discussions, is not prepared to approve an RRA amendment that the RrSG has rejected.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Calibri Light",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Calibri Light",sans-serif">On 20 June 2017
<a href="https://www.icann.org/resources/pages/correspondence">Verisign formally submitted a request to ICANN</a> to extend the 1 August 2017 Thick Whois implementation enforcement date by at least 120 days, or 29 November 2017. The extension request, currently
under review, is not expected to compromise the 1 May 2018 Thick Whois deadline for all new .COM and .NET registrations or the 1 February 2019 deadline for the completion of the Thick Whois transition.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Calibri Light",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Calibri Light",sans-serif">Please let me know if you have any questions.
</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt">Karla Hakansson</span></b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt">Director, Registry Services</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt">ICANN – Global Domains Division</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt">(e) <a href="mailto:Karla.hakansson@icann.org">
Karla.hakansson@icann.org</a></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt">(t) +1.310.699.5834</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt">(s) karlahakansson </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt">12025 Waterfront Drive, Suite 300</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt">Los Angeles, CA 90094-2536</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt"><a href="http://www.icann.org/">www.icann.org</a>
</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</body>
</html>