<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font face="Times New Roman, Times, serif">Hi. Yes, "adequate
access" is a very blurry term. However, tiered access is one of
the key topics being explored in the EPDP process -- and I guess
there will be very intense discussions about what is considered
"adequate" and for whom. The controversy is already in full
swing.</font></p>
<p><font face="Times New Roman, Times, serif">Marita</font><br>
</p>
<br>
<div class="moz-cite-prefix">On 8/28/2018 3:35 PM, Joanna Kulesza
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CANhOcow--onkwdTWMUab8jH_2PKf6hySudEGB9SDCVLDhd3jDw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
Thank you Alan, I fully see your point. As already said, if the
group do decide to go for a more nuanced response, I'm happy to
help with the drafting. Just to briefly respond to Marita's
suggestion: I would assume the details of any "adequate access"
are bound to stir controversy. Yet if the group decide we are for
full endorsement, I will halt my concerns.<br>
<br>
Just my two cents. Thanks!<br>
J. <br>
<br>
W dniu wtorek, 28 sierpnia 2018 Alan Greenberg <<a
href="mailto:alan.greenberg@mcgill.ca" moz-do-not-send="true">alan.greenberg@mcgill.ca</a>>
napisał(a):<br>
> I can only give you my opinion. I cannot say whether our
position is identical to that of SSAC, but I cannot see anything
in that document that I do not believe is in support of our needs.
I do not think that we have the bacndwidth to work from scratch at
the moment, and in a timely manner. Voicing support for this
report was a quick action that I believed we could take without
compromising our position.<br>
><br>
> I would be interested in understanding what we do not agree
with and we could certainly add those caveats if there was
agreement.<br>
><br>
> And thank you for jumping in! :-)<br>
><br>
> Alan<br>
><br>
> At 28/08/2018 05:09 AM, Joanna Kulesza wrote:<br>
><br>
> Thank you Alan and Andrei for the updates.<br>
><br>
> 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 in our statement, 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.<br>
><br>
> Best to all,<br>
> Joanna Kulesza<br>
> --------------------------------<br>
> 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/"
moz-do-not-send="true">https://unilodz.academia.edu/JoannaKulesza/</a><br>
> website: <a href="https://pl.linkedin.com/in/kuleszajoanna"
moz-do-not-send="true">https://pl.linkedin.com/in/kuleszajoanna</a><br>
><br>
> wt., 28 sie 2018 o 08:27 Alan Greenberg <<a
href="mailto:alan.greenberg@mcgill.ca" moz-do-not-send="true">alan.greenberg@mcgill.ca</a>
> napisał(a): 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>
> So far, the SSAC and the NCSG has done so. Their input can be
found at <a href="https://community.icann.org/x/Ag9pBQ"
moz-do-not-send="true">https://community.icann.org/x/Ag9pBQ</a>.<br>
> The SSAC's input consisted of their recent report SAC101. A
copy is attached for your convenience.<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>
> I open the floor for discussion and will initiate a Consensus
Call later in the week.<br>
> Alan _______________________________________________ ALAC
mailing list <a href="mailto:ALAC@atlarge-lists.icann.org"
moz-do-not-send="true">ALAC@atlarge-lists.icann.org</a> <a
href="https://atlarge-lists.icann.org/mailman/listinfo/alac"
moz-do-not-send="true">https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br>
> At-Large Online: <a href="http://www.atlarge.icann.org"
moz-do-not-send="true">http://www.atlarge.icann.org</a> ALAC
Working Wiki: <a
href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+%28ALAC%29"
moz-do-not-send="true">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
ALAC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a>
<a class="moz-txt-link-freetext" href="https://atlarge-lists.icann.org/mailman/listinfo/alac">https://atlarge-lists.icann.org/mailman/listinfo/alac</a>
At-Large Online: <a class="moz-txt-link-freetext" href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</a>
ALAC Working Wiki: <a class="moz-txt-link-freetext" href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a></pre>
</blockquote>
<br>
</body>
</html>