<html xmlns:v="urn:schemas-microsoft-com:vml" 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=us-ascii"><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:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Garamond;
panose-1:2 2 4 4 3 3 1 1 8 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Garamond",serif;
color:#1F497D;}
.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><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond",serif;color:#1F497D'>So in my day job I was one of the GDPR implementation leads and we’ve just wrapped up the initial work. We were assisted by an external consultancy. That said, if anything SSAC did not go far enough.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond",serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond",serif;color:#1F497D'>ICANN has a contractual basis for data collection related to the contracts it signs. The claim of legitimate interest is stretched well beyond it’s intent and in fact the EU has opined on the balancing test required. My understanding of the balancing test would call into question even legitimate law enforcement requests where the PII was of an individual or organization known to be persecuted. In that case, couldn’t exert legitimate interest if it fails the balance test.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond",serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond",serif;color:#1F497D'>I am sympathetic to the needs of security researchers and law enforcement but ICANN data collection does not exist for them, though it is used by them. The proper scope is identifying what data SSAC and RSAC need and use to advance ICANN’s mission.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond",serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond",serif;color:#1F497D'>While rationale for data collection is one pain point, another that my org discover was in terms of data transfer/processing. Legitimate interest is not recognized rationale there. Moreover as a US nonprofit ICANN is ineligible for PrivacyShield which could give it some cover.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond",serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond",serif;color:#1F497D'>Finally and perhaps to make matters worse, the technical spec instruct registries on data collection. I confess that at this point I’m not sure whether ICANN is acting as a data controller or a data processor. In a sense, the registries are data controllers and ICANN is the data processor, thrusting the onus of compliance upon registries. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond",serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond",serif;color:#1F497D'>I’m at the limits of my GDPR for the day so additional thoughts would be welcome.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond",serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond",serif;color:#1F497D'>Best,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond",serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond",serif;color:#1F497D'>John<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond",serif;color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> ALAC <alac-bounces@atlarge-lists.icann.org> <b>On Behalf Of </b>Holly Raiche<br><b>Sent:</b> Tuesday, August 28, 2018 2:17 PM<br><b>To:</b> Marita Moll <mmoll@ca.inter.net>; ALAC <alac@atlarge-lists.icann.org><br><b>Cc:</b> Alan Greenberg <alan.greenberg@mcgill.ca><br><b>Subject:</b> Re: [ALAC] EPDP Early input<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks Marita<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I like your wording. Ys it is a big document and I like your wording as to wha it is in the report that we endorse. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Holly<o:p></o:p></p><div><div><p class=MsoNormal>On 29 Aug 2018, at 1:18 am, Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>Marita, I am not sure that your synopsis is all that different from endorsing the entire paper when you start examining the rationales, but I would be happy to accept that if we can get closure on it quickly. Time is our enemy in this overall EPDP process.<br><br>Alan<br><br><br>At 28/08/2018 10:38 AM, Marita Moll wrote:<br><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal><span style='font-family:"Times New Roman",serif'>Sorry to have missed the call -- still confusing midnight Monday with midnight Tuesday -- I guess I will get used to the format.<br></span><br><span style='font-family:"Times New Roman",serif'>I just read this really well done SSAC report which is clear and thorough. But there is a lot in there. I wonder if we should do a blanket endorsement of everything without careful analysis. <br></span><br><span style='font-family:"Times New Roman",serif'>Could we not have a more nuanced position? For example, we could say that, in line with our mandate to support end-users, we support SSAC's position on ensuring that security professionals and law enforcement have adequate access to WHOIS/RDS data. <br></span><br><span style='font-family:"Times New Roman",serif'>If that is the point we want to make.<br></span><br><span style='font-family:"Times New Roman",serif'>Marita</span><br><br>On 8/28/2018 2:23 AM, Alan Greenberg wrote:<br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal style='margin-bottom:12.0pt'>As I mentioned on the ALAC call that has just completed, all EPDP participant groups have been given the opportunity to provide "early input" into the EPDP. <br><br>So far, the SSAC and the NCSG has done so. Their input can be found at <a href="https://community.icann.org/x/Ag9pBQ">https://community.icann.org/x/Ag9pBQ</a>.<br><br>The SSAC's input consisted of their recent report SAC101. A copy is attached for your convenience.<br><br>I would like to suggest that the ALAC submit a statement saying that we support SAC101, as it is in line with our stated position of trying to ensure that security professionals and law enforcement have adequate access to WHOIS/RDS data.<br><br>I open the floor for discussion and will initiate a Consensus Call later in the week.<br><br>Alan <br><br><o:p></o:p></p><pre>_______________________________________________<o:p></o:p></pre><pre>ALAC mailing list<o:p></o:p></pre><pre><a href="mailto:ALAC@atlarge-lists.icann.org"><o:p></o:p></a></pre><pre><span class=MsoHyperlink><a href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a></span><o:p></o:p></pre><pre><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac"><o:p></o:p></a></pre><pre><span class=MsoHyperlink><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac">https://atlarge-lists.icann.org/mailman/listinfo/alac</a></span><o:p></o:p></pre><pre><o:p> </o:p></pre><pre>At-Large Online:<o:p></o:p></pre><pre><a href="http://www.atlarge.icann.org/">http://www.atlarge.icann.org</a><o:p></o:p></pre><pre>ALAC Working Wiki:<o:p></o:p></pre><pre><a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)"><o:p></o:p></a></pre><pre><span class=MsoHyperlink><a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a></span><o:p></o:p></pre></blockquote><p class=MsoNormal><br>_______________________________________________<br>ALAC mailing list<br><a href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a><br><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac">https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br><br>At-Large Online: <a href="http://www.atlarge.icann.org/">http://www.atlarge.icann.org</a><br>ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC</a> )<o:p></o:p></p></blockquote></div><p class=MsoNormal>_______________________________________________<br>ALAC mailing list<br><a href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a><br><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac">https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br><br>At-Large Online: <a href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</a><br>ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a><o:p></o:p></p></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>