<div dir="ltr">



















<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:"Calibri",sans-serif"><span style="font-size:12pt;font-family:"Times New Roman",serif" lang="EN-US">Thank you Alan and Andrei for the updates. <br></span></p><p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:"Calibri",sans-serif"><br><span style="font-size:12pt;font-family:"Times New Roman",serif" lang="EN-US"><span></span></span></p>

<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:"Calibri",sans-serif"><span style="font-size:12pt;font-family:"Times New Roman",serif" lang="EN-US">Please excuse my newcomer confusion - not meaning to stir the pot here -
but I'm wondering how close At-Large's/ALAC's position is to that of the SSAC? Do we agree with their report 100%? My initial thinking is that representing
users, we might want a somewhat more diversified approach than that offered by the SSAC, ensuring full GDPR compliance (I'm happy to
elaborate if needed). Also, would it make sense to take on the
positions of other communities 
<span style="font-size:12pt;font-family:"Times New Roman",serif" lang="EN-US">in our statement</span>, if only for the sake of future consensus
building? As already briefly mentioned to Alan, I'm happy to help with the
drafting if needed. <span></span></span></p>





<div><br></div><div>Best to all,</div><div>Joanna Kulesza <br></div><div>

<div><div>--------------------------------<br><div id="gmail-signature_old"><font style="font-size:10pt">Joanna Kulesza, PhD<br>assistant professor of international law and Internet governance <br>Faculty of Law and Administration, University of Lodz<br>Kopcinskiego Street 8/12, 90-232 Lodz, Poland<br>publications: <a href="https://unilodz.academia.edu/JoannaKulesza/" style="color:rgb(0,0,238)">https://unilodz.academia.edu/JoannaKulesza/</a><br>website: <a href="https://pl.linkedin.com/in/kuleszajoanna" style="color:rgb(0,0,238)">https://pl.linkedin.com/in/kuleszajoanna</a></font></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr">wt., 28 sie 2018 o 08:27 Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>> napisał(a):<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
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" target="_blank">
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</div>

_______________________________________________<br>
ALAC mailing list<br>
<a href="mailto:ALAC@atlarge-lists.icann.org" target="_blank">ALAC@atlarge-lists.icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" rel="noreferrer" target="_blank">https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br>
<br>
At-Large Online: <a href="http://www.atlarge.icann.org" rel="noreferrer" target="_blank">http://www.atlarge.icann.org</a><br>
ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" rel="noreferrer" target="_blank">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a></blockquote></div>