<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Dear Holly and all,<div><br></div><div>I think it’s of the essence that the ALAC is able to provide feedback and help shape whatever model is suggested. ICANN Org has been emphatic in that they will provide support to a community wide exercise that aims to shape a proposed model but it will not provide support to isolated efforts. </div><div><br></div><div>I have read different points of view regarding this proposed model and it feels like it doesn’t really have the support the BC/IPC thinks it has, hence the importance of having input from the ALAC and the rest of the community. </div><div><br></div><div>Maybe the BC/IPC proposal is a good starting point but we have to keep in mind it is just that: a starting point that should allow community wide feedback and go through a community wide process to find consensus on the end outcome. </div><div><br></div><div>Kind regards </div><div><br></div><div>León <br><br><div id="AppleMailSignature">Enviado desde mi iPhone</div><div><br>El abr. 8, 2018, a la(s) 3:30 p. m., Holly Raiche <<a href="mailto:h.raiche@internode.on.net">h.raiche@internode.on.net</a>> escribió:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=windows-1252">Thanks Bastiaan<div><br></div><div>The link you sent doesn’t resolve but I think it’s the same document. My strong suggestion - leadership team - is to put this issue on the policy wiki - given that we have said this is an important issue, we should comment on it</div><div><br></div><div>Over to staff and the leadership team!</div><div><br></div><div>Holly<br><div><div>On 9 Apr 2018, at 1:19 am, Bastiaan Goslings <<a href="mailto:bastiaan.goslings@ams-ix.net">bastiaan.goslings@ams-ix.net</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="content-type" content="text/html; charset=utf-8"><div dir="auto">Hi Holly<div><br></div><div>Thanks a lot - very good to raise this issue.</div><div><br></div><div>I assume the draft you refer to is <a href="https://www.icann.org/en/system/files/files/gdpr-comments-ipbc-whois-access-accreditation-process-1-2-23mar18-en.pdf">https://www.icann.org/en/system/files/files/gdpr-comments-ipbc-whois-access-accreditation-process-1-2-23mar18-en.pdf</a> ?</div><div><br></div><div>I haven’t read it yet...</div><div><br><div>Bastiaan<div><br><div>--<br><div>Envoyé de mon iPhone</div></div></div></div><div><br>On 8 Apr 2018, at 07:41, Holly Raiche <<a href="mailto:h.raiche@internode.on.net">h.raiche@internode.on.net</a>> wrote:<br><br></div><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=windows-1252">
<!--[if gte mso 9]><xml>
<o:DocumentProperties>
<o:Template>Normal.dotm</o:Template>
<o:Revision>0</o:Revision>
<o:TotalTime>0</o:TotalTime>
<o:Pages>1</o:Pages>
<o:Words>378</o:Words>
<o:Characters>2156</o:Characters>
<o:Company>ISOC-AU</o:Company>
<o:Lines>17</o:Lines>
<o:Paragraphs>4</o:Paragraphs>
<o:CharactersWithSpaces>2647</o:CharactersWithSpaces>
<o:Version>12.0</o:Version>
</o:DocumentProperties>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:Zoom>0</w:Zoom>
<w:TrackMoves>false</w:TrackMoves>
<w:TrackFormatting/>
<w:PunctuationKerning/>
<w:DrawingGridHorizontalSpacing>18 pt</w:DrawingGridHorizontalSpacing>
<w:DrawingGridVerticalSpacing>18 pt</w:DrawingGridVerticalSpacing>
<w:DisplayHorizontalDrawingGridEvery>0</w:DisplayHorizontalDrawingGridEvery>
<w:DisplayVerticalDrawingGridEvery>0</w:DisplayVerticalDrawingGridEvery>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:DontGrowAutofit/>
<w:DontAutofitConstrainedTables/>
<w:DontVertAlignInTxbx/>
</w:Compatibility>
</w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" LatentStyleCount="276">
</w:LatentStyles>
</xml><![endif]-->
<!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-ascii-font-family:Cambria;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Cambria;
mso-hansi-theme-font:minor-latin;
mso-ansi-language:EN-US;}
</style>
<![endif]-->
<!--StartFragment--><p class="MsoNormal">Folks</p><p class="MsoNormal"><o:p> </o:p>As we said in the ALAC Statement on the GDPR – now being
voted upon – one of the outstanding critical issues will be accreditation of
those who are given access to personal information from the Whois database. </p><p class="MsoNormal"><o:p> </o:p>The IPC/BC community within the GNSO has developed a ‘<i>Draft Accreditation and Access Model for
non-public Whois Data</i>’ which
they are putting forward for discussion.
Indeed, they recently held a webinar on the model – at the usually
impossible time for Australia. They have also set up a mailing list on the
issue and the documents they used for the webinar are supposed to be available
for those on the mailing list. (I haven’t seen them as yet)</p><p class="MsoNormal"><o:p> </o:p>The first thing to note about that model is that is that it
is very much the creature of the IPC/BC constituency. The NCSG were not consulted and are developing their
response to the accreditation model.
My understanding is that the Registries/Registrars also did not provide
input into that model. We should also comment - either through a Google Doc or on the wiki, but - in a very short space of time - we should be developing at least some response to the IPC/BC proposal. No response to their model could otherwise be taken as tacit community consent to its proposals. </p><p class="MsoNormal"> My two major issues with the model are as below.
Please feel free to comment as well.</p><p class="MsoNormal"><o:p> </o:p>My basic issue with their Access Model is that it confuses
data ‘use’ with the ‘purpose’ of collection. Under basic data protection law, personal information can
only be collected for specified and legitimate purposes <b>of the data collector</b>
(ICANN and registrars) and not further processed in ways
inconsistent with the legitimate
purpose(s). The ALAC has suggested
that feedback from the European DPAs will assist in determining the purposes
consistent with ICANN and the Registries purpose in collection of that data.
The purpose suggested in the Interim Model is not as broad as suggested by this
Access Model and, in my view, preferable. (See Annex A, Access Model).</p><p class="MsoNormal"><o:p> </o:p>The Access Model proposed suggests that, once parties are
accredited, they would gain access to all the Whois Information. In my view, any access to personal
information should be <b>in limited
circumstances only</b> - that
blanket access not be given. In a
law enforcement context, search warrants generally need some kind of judicial
sanction, based on apprehension of possible criminality, before premises can be
searched and/or persons apprehended. While an access request test probably
would not be quite that stringent, I could not support access seekers being
given blanket permission to access personal information generally; there should
be a requirement for reasonable grounds to suspect unlawful or harmful action
in specific circumstances (carefully defined) before access given. </p><div><br></div><div>Holly</div>
<!--EndFragment--></blockquote><blockquote type="cite"><span>_______________________________________________</span><br><span>ALAC mailing list</span><br><span><a href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a></span><br><span><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac">https://atlarge-lists.icann.org/mailman/listinfo/alac</a></span><br><span></span><br><span>At-Large Online: <a href="http://www.atlarge.icann.org/">http://www.atlarge.icann.org</a></span><br><span>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></span></blockquote></div></div></blockquote></div><br></div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>ALAC mailing list</span><br><span><a href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a></span><br><span><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac">https://atlarge-lists.icann.org/mailman/listinfo/alac</a></span><br><span></span><br><span>At-Large Online: <a href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</a></span><br><span>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></span></div></blockquote></div></body></html>