<div><div dir="auto">Hi, Chuck, Regarding below, has a decision been made by leadership whether to invite the org folks to meet with us in Abu Dhabi as Greg A. was suggesting?</div><div dir="auto"><br></div><div dir="auto">Thanks </div><div dir="auto">Jonathan </div><br><div class="gmail_quote"><div>On Fri, Oct 20, 2017 at 2:46 AM jonathan matkowsky <<a href="mailto:jonathan.matkowsky@riskiq.net">jonathan.matkowsky@riskiq.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div dir="auto">The other week I was asking this group about the significance of the ePrivacy Directive and asked to get some feedback.</div><div dir="auto"><br></div><div dir="auto">The memo says:</div><div dir="auto"><br></div><div dir="auto"><div dir="auto">While our memorandum series will primarily focus on the GDPR, we will also address other relevant pieces of EU legislation that may have effect on the processing of personal data through the Whois services, such as but not limited to the EU ePrivacy Directive 2002/58/EC and the proposed new EU ePrivacy Regulation aimed to replace the said directive in May 2018.</div><div dir="auto"><br></div><div dir="auto">This is exactly what I was asking to understand.</div><div dir="auto"><br></div><div dir="auto">That said, I do want to continue our work, but I also have limited resources—as do we all—so the sooner we can get this information, the better. It may help us in deciding the most efficient way forward, or at least help confirm we aren’t wasting our time in how we move forward here?</div><div dir="auto"><br></div><div dir="auto">Thanks </div><div dir="auto">Jonathan </div></div></div><div><br><div class="gmail_quote"><div>On Thu, Oct 19, 2017 at 9:40 AM Greg Aaron <<a href="mailto:gca@icginc.com" target="_blank">gca@icginc.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="m_7775193058745579155m_7299029587959283055WordSection1">
<p class="m_7775193058745579155m_7299029587959283055MsoPlainText"><a name="m_7775193058745579155_m_7299029587959283055__MailEndCompose">Dear Chuck:<u></u><u></u></a></p>
<p class="m_7775193058745579155m_7299029587959283055MsoPlainText"><span><u></u> <u></u></span></p>
<p class="m_7775193058745579155m_7299029587959283055MsoPlainText"><span>ICANN meetings are for information-sharing. And since we have two efforts working on some of the exact same issues, I suggest that some info-sharing could be very helpful to our volunteers.
<u></u><u></u></span></p>
<p class="m_7775193058745579155m_7299029587959283055MsoPlainText"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span><span style="color:windowtext">The ICANN Org effort with Hamilton is clearly going to be more comprehensive than the narrow effort our WG has received from Wilson Sonsini. And as you know, the
Org effort will set a precedent which will be important for our WG to understand.
<u></u><u></u></span></span></p>
<p class="MsoNormal"><span><span style="color:windowtext"><u></u> <u></u></span></span></p>
<p class="MsoNormal"><span><span style="color:windowtext">The new memo, and those to come, are about the impact of GDPR on registration data and WHOIS. I draw your attention to the end of the blog post:<u></u><u></u></span></span></p>
<p class="MsoNormal"><span><span style="color:windowtext">“As a reminder, this legal analysis is intended to serve as building block for community discussions about how to approach GDPR issues in the domain name space. [WHOIS.]<u></u><u></u></span></span></p>
<p class="MsoNormal"><span><span style="color:windowtext">Here's where we need help from the multistakeholder community:<u></u><u></u></span></span></p>
<p class="MsoNormal"><span><span style="color:windowtext">Please review the initial legal analysis and provide feedback. This includes identifying possible questions, and how best to interact with data protection agencies
and others to get to the next step of the analysis.<u></u><u></u></span></span></p>
<p class="MsoNormal"><span><span style="color:windowtext">It will be helpful to receive your feedback at the earliest opportunity, so as to inform the upcoming discussions at ICANN60, and to feed into future iterations of
the legal analysis.”<u></u><u></u></span></span></p>
<p class="MsoNormal"><span><span style="color:windowtext"><u></u> <u></u></span></span></p>
<p class="MsoNormal"><span><span style="color:windowtext">The RDS WG is the main place where the multistakeholder community is considering WHOIS. So one would think that ICANN Org would have already reached out to our
WG. I am surprised that it has not. So, I think it’s appropriate for us to invite the Org folks in. The goal is to understand that work and ask questions. Maybe the RDS WG could then formulate some feedback as requested above. After all, we’ve been
thinking about this stuff for almost two years now..<u></u><u></u></span></span></p>
<p class="MsoNormal"><span><span style="color:windowtext"><u></u> <u></u></span></span></p>
<p class="MsoNormal"><span>As part of the briefing, it would be good to hear about this effort's schedule and workplan. The memo says: "We intend to provide a series of memorandums, which will address different aspects
of the issue and where the scope and topics of each such memorandum will be discussed and agreed with ICANN. We understand that ICANN intends to make each memorandum publicly available." I do not see any of those details in the memo or blog. For example,
what topics will be the subjects of the forthcoming memos? There’s clearly a plan for that.<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span>I have no idea of any of that will come out in the GDPR session on Thursday, but since that consists of panel presentations, I am unsure and would prefer that our WG definitely get a briefing and
a chance to ask questions.</span><span><span style="color:windowtext"><u></u><u></u></span></span></p>
<p class="MsoNormal"><span><span style="color:windowtext"><u></u> <u></u></span></span></p>
<p class="MsoNormal"><span><span style="color:windowtext">All best,<u></u><u></u></span></span></p>
<p class="MsoNormal"><span><span style="color:windowtext">--Greg<u></u><u></u></span></span></p>
<p class="MsoNormal"><span><span style="color:windowtext"><u></u> <u></u></span></span></p>
<span></span>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:windowtext">From:</span></b><span style="color:windowtext"> <a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">gnso-rds-pdp-wg-bounces@icann.org</a> [mailto:<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">gnso-rds-pdp-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>Stephanie Perrin<br>
<b>Sent:</b> Thursday, October 19, 2017 11:19 AM<br>
<b>To:</b> <a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a></span></p></div></div></div></div><div bgcolor="white" lang="EN-US" link="blue" vlink="purple"><div class="m_7775193058745579155m_7299029587959283055WordSection1"><div><div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><span style="color:windowtext"><br>
<b>Subject:</b> Re: [gnso-rds-pdp-wg] ICANN Legal Opinion on GDPR - Part 1<u></u><u></u></span></p></div></div></div></div><div bgcolor="white" lang="EN-US" link="blue" vlink="purple"><div class="m_7775193058745579155m_7299029587959283055WordSection1">
<p class="MsoNormal"><u></u> <u></u></p>
<p><span style="font-size:13.5pt;font-family:"Lucida Grande",serif">I am curious as to how the questions are being framed. Who is the client, ICANN the MS body, ICANN the CEO and staff (who have been found to be a co-controller and therefore have an interest
in avoiding fines) or ICANN the Board.</span><u></u><u></u></p>
<p><span style="font-size:13.5pt;font-family:"Lucida Grande",serif">There are different interests at stake here, I think it would be useful to get a fuller understanding of how Teresa Swineheart is handling the development of questions.</span><u></u><u></u></p>
<p><span style="font-size:13.5pt;font-family:"Lucida Grande",serif">Stephanie Perrin</span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On 2017-10-19 10:43, Chuck wrote:<u></u><u></u></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Greg,<u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>Having just finished reading the Hamilton memo, I don't understand why you<u></u><u></u></pre>
<pre>think the WG needs a presentation? What would a presentation from Teresa or<u></u><u></u></pre>
<pre>other ICANN staff person provide us that we couldn't get from the memo<u></u><u></u></pre>
<pre>itself and other sources such as the ICANN Blog, etc.?<u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>Can you identify any advice from Hamilton that would supplant work we have<u></u><u></u></pre>
<pre>been doing? If so, please identify it.<u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>In my opinion:<u></u><u></u></pre>
<pre>- The advice of ways forward fits nicely into our policy development<u></u><u></u></pre>
<pre>processes.<u></u><u></u></pre>
<pre>- The Hamilton Memo confirms much of what we already heard from the DP<u></u><u></u></pre>
<pre>experts and Wilson Sonsini so we now have it from three separate sources.<u></u><u></u></pre>
<pre>- You are absolutely that we "need to understand and track the legal<u></u><u></u></pre>
<pre>advice being made" and that it overlaps what we are doing but I think that<u></u><u></u></pre>
<pre>will help us.<u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>Chuck<u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>-----Original Message-----<u></u><u></u></pre>
<pre>From: Greg Aaron [<a href="mailto:gca@icginc.com" target="_blank">mailto:gca@icginc.com</a>] <u></u><u></u></pre>
<pre>Sent: Thursday, October 19, 2017 7:25 AM<u></u><u></u></pre>
<pre>To: Chuck <a href="mailto:consult@cgomes.com" target="_blank"><consult@cgomes.com></a>; 'Alan Greenberg' <a href="mailto:alan.greenberg@mcgill.ca" target="_blank"><alan.greenberg@mcgill.ca></a>;<u></u><u></u></pre>
<pre>'GNSO RDS PDP' <a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank"><gnso-rds-pdp-wg@icann.org></a><u></u><u></u></pre>
<pre>Subject: RE: [gnso-rds-pdp-wg] ICANN Legal Opinion on GDPR - Part 1<u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>Dear WG leadership:<u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>As we expected, this ICANN Org effort will have a profound effect on our<u></u><u></u></pre>
<pre>work. We will need to understand and track the legal advice being made,<u></u><u></u></pre>
<pre>which overlaps with and in some places may supplant work we have been doing.<u></u><u></u></pre>
<pre>And the memo's "Finding New Ways Forward" section (3.9) provides advice for<u></u><u></u></pre>
<pre>the policy-making process. Clearly our WG needs (deserves) a presentation<u></u><u></u></pre>
<pre>at Abu Dhabi from Teresa Swinehart, who is heading up this effort. <u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>Could this be done at the WG meeting on Wednesday 1 November? <u></u><u></u></pre>
<pre>Wednesday will be better attended, both in-person and remotely. (Some<u></u><u></u></pre>
<pre>members may still be in transit during the WG's early Saturday morning<u></u><u></u></pre>
<pre>meeting. And the Saturday meeting is at a challenging time for those<u></u><u></u></pre>
<pre>participating remotely -- ~6:30 a.m. Saturday morning in Europe / 12:30<u></u><u></u></pre>
<pre>a.m. Saturday East Coast USA.)<u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>As part of the briefing, it would be good to hear about this effort's<u></u><u></u></pre>
<pre>schedule, workplan, and immediate next steps. The memo says: "We intend to<u></u><u></u></pre>
<pre>provide a series of memorandums, which will address different aspects of the<u></u><u></u></pre>
<pre>issue and where the scope and topics of each such memorandum will be<u></u><u></u></pre>
<pre>discussed and agreed with ICANN. We understand that ICANN intends to make<u></u><u></u></pre>
<pre>each memorandum publicly available."<u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>All best,<u></u><u></u></pre>
<pre>--Greg<u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre><u></u> <u></u></pre>
<pre><u></u> <u></u></pre>
<pre>-----Original Message-----<u></u><u></u></pre>
<pre>From: <a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">gnso-rds-pdp-wg-bounces@icann.org</a><u></u><u></u></pre>
<pre>[<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>] On Behalf Of Chuck<u></u><u></u></pre>
<pre>Sent: Thursday, October 19, 2017 8:51 AM<u></u><u></u></pre>
<pre>To: 'Alan Greenberg' <a href="mailto:alan.greenberg@mcgill.ca" target="_blank"><alan.greenberg@mcgill.ca></a>; 'GNSO RDS PDP'<u></u><u></u></pre>
<pre><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank"><gnso-rds-pdp-wg@icann.org></a><u></u><u></u></pre>
<pre>Subject: Re: [gnso-rds-pdp-wg] ICANN Legal Opinion on GDPR - Part 1<u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>I want to call attention to the following paragraph:<u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>"The memo highlights the complexity of these issues in the domain name<u></u><u></u></pre>
<pre>space, and concludes that the current open, publicly available WHOIS<u></u><u></u></pre>
<pre>services cannot remain unchanged. The WHOIS system has to become adaptable<u></u><u></u></pre>
<pre>to address the GDPR from the European perspective, as well as other changing<u></u><u></u></pre>
<pre>regulations around the world."<u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>After input from Data Protection experts, the Wilson Sonsini memo and now<u></u><u></u></pre>
<pre>this memo, do any in the WG disagree with this statement?<u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>Chuck<u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre><u></u> <u></u></pre>
<pre><u></u> <u></u></pre>
<pre>-----Original Message-----<u></u><u></u></pre>
<pre>From: <a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">gnso-rds-pdp-wg-bounces@icann.org</a><u></u><u></u></pre>
<pre>[<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>] On Behalf Of Alan Greenberg<u></u><u></u></pre>
<pre>Sent: Thursday, October 19, 2017 5:04 AM<u></u><u></u></pre>
<pre>To: GNSO RDS PDP <a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank"><gnso-rds-pdp-wg@icann.org></a><u></u><u></u></pre>
<pre>Subject: Re: [gnso-rds-pdp-wg] ICANN Legal Opinion on GDPR - Part 1<u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>Full Blog post is at<u></u><u></u></pre>
<pre><a href="https://www.icann.org/news/blog/data-protection-and-privacy-update" target="_blank">https://www.icann.org/news/blog/data-protection-and-privacy-update</a>. Alan<u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>At 19/10/2017 12:23 AM, Alan Greenberg wrote:<u></u><u></u></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Perhaps it has already been posted, but if not, ICANN has received the <u></u><u></u></pre>
<pre>first part of the independent legal analysis of the GDPR in relation to <u></u><u></u></pre>
<pre>WHOIS that had been commissioned.<u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>It can be found at<u></u><u></u></pre>
<pre><a href="https://www.icann.org/en/system/files/files/gdpr-memorandum-part1-16oct" target="_blank">https://www.icann.org/en/system/files/files/gdpr-memorandum-part1-16oct</a><u></u><u></u></pre>
<pre>17-e<u></u><u></u></pre>
</blockquote>
<pre>n.pdf.<u></u><u></u></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre><u></u> <u></u></pre>
<pre>Alan<u></u><u></u></pre>
</blockquote>
<pre><u></u> <u></u></pre>
<pre>_______________________________________________<u></u><u></u></pre>
<pre>gnso-rds-pdp-wg mailing list<u></u><u></u></pre>
<pre><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><u></u><u></u></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>_______________________________________________<u></u><u></u></pre>
<pre>gnso-rds-pdp-wg mailing list<u></u><u></u></pre>
<pre><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><u></u><u></u></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>_______________________________________________<u></u><u></u></pre>
<pre>gnso-rds-pdp-wg mailing list<u></u><u></u></pre>
<pre><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><u></u><u></u></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><u></u><u></u></pre>
</blockquote>
<p class="MsoNormal"><u></u> <u></u></p>
</div></div>
_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></blockquote></div></div><div>-- <br></div><div class="m_7775193058745579155gmail_signature" data-smartmail="gmail_signature">Jonathan Matkowsky</div></blockquote></div></div><div dir="ltr">-- <br></div><div class="gmail_signature" data-smartmail="gmail_signature">Jonathan Matkowsky</div>
<br>
<span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)">******************************</span><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)"><wbr>******************************</span><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)"><wbr>*******<br></span><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)">This message was sent from RiskIQ, and is intended only for the designated recipient(s). It may contain confidential or proprietary information and may be subject to confidentiality protections. If you are not a designated recipient, you may not review, copy or distribute this message. If you receive this in error, please notify the sender by reply e-mail and delete this message. Thank you.</span><p style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)"></p><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)">******************************</span><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)"><wbr>******************************</span><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)"><wbr>*******</span>