<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Thanks Carlton<div><br></div><div>I really like that suggestion - it is a document only of principles, but ones that ALAC clearly supports, and that fit well into our EPDP discussions and, because of the shortness of time, we can all agree on</div><div><br></div><div>Holly<br><div><div>On 29 Aug 2018, at 9:16 am, Carlton Samuels <<a href="mailto:carlton.samuels@gmail.com">carlton.samuels@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:large">The At-Large is well-advised to take SSAC publications seriously. For in regard to problem definition, analysis and recommendations to solution they are thorough, devoid of hysteria and exhibits an internal logic any sentient being can apply.</div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:large"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:large">A suggestion. <a href="https://www.icann.org/en/system/files/files/ssac2018-17-26jun18-en.pdf">SAC2018-17</a> details the high-level recommendations as principles that the SSAC believes should guide ePDP deliberations. The SSAC say these recommendations are extracted from the SAC101 Advisory; in their own words, "<i>several of the recommendations are specifically designed as inputs to the ePDP</i>" then in construction and particularized further in SAC2018-17. </div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:large"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:large">I have read SAC101 publication and on balance of fact, so affirm. If you recall, this is the kind of approach some of us advised the ALAC should embrace to guide participation of At-Large representatives on the ePDP. One cannot now say that such a document - meaning an At-Large developed and ALAC-endorsed document - emerged from that lot of interventions. </div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:large"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:large"> What I can say is the SSAC-enunciated principles look very much like those the rational mind of an At-Large participant would support. I would urge you reject this malignant At-Large propensity to re-invent the wheel. Endorse the principles as outlined in SAC2018-17 and save yourselves a bother without a redeemable quality.</div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:large"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:large">-Carlton </div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr"><br>==============================<br><i><font face="comic sans ms, sans-serif">Carlton A Samuels</font></i><br><font face="comic sans ms, sans-serif"><i>Mobile: 876-818-1799<br><font color="#33CC00">Strategy, Process, Governance, Assessment & Turnaround</font></i></font><br>=============================</div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Aug 28, 2018 at 9:39 AM Marita Moll <<a href="mailto:mmoll@ca.inter.net">mmoll@ca.inter.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><p><font face="Times New Roman, Times, serif">Sorry to have missed
the call -- still confusing midnight Monday with midnight Tuesday
-- I guess I will get used to the format.</font></p><p><font face="Times New Roman, Times, 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>
</font></p><p><font face="Times New Roman, Times, 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>
</font></p><p><font face="Times New Roman, Times, serif">If that is the point
we want to make.<br>
</font></p><p><font face="Times New Roman, Times, serif">Marita</font><br>
</p>
<br>
<div class="m_5247469474182915676moz-cite-prefix">On 8/28/2018 2:23 AM, Alan Greenberg
wrote:<br>
</div>
<blockquote type="cite">
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
<br>
<fieldset class="m_5247469474182915676mimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
ALAC mailing list
<a class="m_5247469474182915676moz-txt-link-abbreviated" href="mailto:ALAC@atlarge-lists.icann.org" target="_blank">ALAC@atlarge-lists.icann.org</a>
<a class="m_5247469474182915676moz-txt-link-freetext" href="https://atlarge-lists.icann.org/mailman/listinfo/alac" target="_blank">https://atlarge-lists.icann.org/mailman/listinfo/alac</a>
At-Large Online: <a class="m_5247469474182915676moz-txt-link-freetext" href="http://www.atlarge.icann.org/" target="_blank">http://www.atlarge.icann.org</a>
ALAC Working Wiki: <a class="m_5247469474182915676moz-txt-link-freetext" href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" target="_blank">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a></pre>
</blockquote>
<br>
</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>
_______________________________________________<br>ALAC mailing list<br><a href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a><br>https://atlarge-lists.icann.org/mailman/listinfo/alac<br><br>At-Large Online: http://www.atlarge.icann.org<br>ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</blockquote></div><br></div></body></html>