<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:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Thanks, Paul.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">I’m chatting with Marika now, and we hope to finalize the 19 JAN agenda today.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">J.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black">"policy@paulmcgrady.com" <policy@paulmcgrady.com><br>
<b>Date: </b>Monday, January 9, 2017 at 10:32<br>
<b>To: </b>"James M. Bladel" <jbladel@godaddy.com>, GNSO Council List <council@gnso.icann.org><br>
<b>Subject: </b>RE: FW: [council] Letter to GNSO Council from "thick" WHOIS Implementation Review Team (IRT)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Verdana;color:black">Thanks James. The IPC has its regular call tomorrow, so if there is any way possible to have a draft Jan 19 Council call agenda capturing non-motion items like this, that would
be supremely helpful. Otherwise, i'm afraid that many of the topics that end up on the agenda for discussion will be slowed down by "I have to get back to you" wince we won't have another IPC call between now and then.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Verdana;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Verdana;color:black">Best,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Verdana;color:black">Paul<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Verdana;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:Verdana;color:black"> <o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 6.0pt;margin-left:6.0pt;margin-top:5.0pt;margin-bottom:5.0pt" id="replyBlockquote">
<div id="wmQuoteWrapper">
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:Verdana;color:black">-------- Original Message --------<br>
Subject: FW: [council] Letter to GNSO Council from "thick" WHOIS<br>
Implementation Review Team (IRT)<br>
From: "James M. Bladel" <<a href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a>><br>
Date: Sun, January 08, 2017 10:56 am<br>
To: GNSO Council List <<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>><br>
<br>
Councilors – <br>
<br>
Please see the note from Amr (below) and the letter from the “thick WHOIS” IRT (attached), outlining some challenges associated with the implementation of this GNSO Policy and changes to national privacy laws. I propose that we add this topic, and potential
next steps, as a discussion item for our next call on 19 JAN.<br>
<br>
Thank you,<br>
<br>
J.<br>
<br>
<br>
On 12/17/16, 09:13, "<a href="mailto:owner-council@gnso.icann.org">owner-council@gnso.icann.org</a> on behalf of Amr Elsadr" <<a href="mailto:owner-council@gnso.icann.org">owner-council@gnso.icann.org</a> on behalf of
<a href="mailto:aelsadr@egyptig.org">aelsadr@egyptig.org</a>> wrote:<br>
<br>
Hi,<br>
<br>
The “thick” WHOIS IRT has asked me to forward a letter (attached) sent on its behalf to the GNSO Council. If folks recall, the “thick” WHOIS Consensus Policy recommendations included this:<br>
<br>
> "As part of the implementation process a legal review of law applicable to the transition of data from a thin to thick model that has not already been considered in the EWG memo is undertaken and due consideration is given to potential privacy issues that
may arise from the discussions on the transition from thin to thick Whois, including, for example, guidance on how the long-standing contractual requirement that registrars give notice to, and obtain consent, from each registrant for uses of any personally
identifiable data submitted by the registrant should apply to registrations involved in the transition. Should any privacy issues emerge from these transition discussions that were not anticipated by the WG and which would require additional policy consideration,
the Implementation Review Team is expected to notify the GNSO Council of these so that appropriate action can be taken.”<br>
<br>
In June, 2015, ICANN’s Legal Dept. submitted a memo in follow up of the above recommendation, which can be found on this page:
<a href="https://www.icann.org/resources/pages/thick-whois-2016-06-27-en">https://www.icann.org/resources/pages/thick-whois-2016-06-27-en</a>.<br>
<br>
The IRT believes that the privacy/data protection law environment has changed since the production of the legal memo by ICANN Legal. Although the IRT has not reached any consensus on recommending further policy work as a result of its findings, there is agreement
that the shifting privacy/data protection environment may complicate the transition from “thin” to “thick” WHOIS for some contracted parties. This letter is meant to brief the Council on the IRT’s work in that regard.<br>
<br>
Thanks.<br>
<br>
Amr<br>
<br>
<br>
<o:p></o:p></span></p>
</div>
</blockquote>
</div>
</body>
</html>