<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">Sorry, I meant webinar
        -- not wiki -- of course.</font></p>
    <p><font face="Times New Roman, Times, serif">Marita</font><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 8/28/2018 5:41 PM, Marita Moll
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:7872e90a-e116-0c78-98e9-23382c9e5de9@ca.inter.net">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <p><font face="Times New Roman, Times, serif">In response to Alan,
          for me, it's just a case of not knowing what I don't know. We
          are pressed for time. So we can't hold a wiki to bring
          everyone up to speed on all parts of the document. If we don't
          need to endorse the whole thing while still endorsing what we
          feel is essential at the moment, good middle road to take.</font></p>
      <p><font face="Times New Roman, Times, serif">Marita</font><br>
      </p>
      <br>
      <div class="moz-cite-prefix">On 8/28/2018 5:18 PM, Alberto Soto
        wrote:<br>
      </div>
      <blockquote type="cite"
        cite="mid:046701d43f14$b9aff7c0$2d0fe740$@ibero-americano.org">
        <meta http-equiv="Content-Type" content="text/html;
          charset=utf-8">
        <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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        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;}
p.msonormal0, li.msonormal0, div.msonormal0
        {mso-style-name:msonormal;
        mso-margin-top-alt:auto;
        margin-right:0cm;
        mso-margin-bottom-alt:auto;
        margin-left:0cm;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
span.EstiloCorreo19
        {mso-style-type:personal-reply;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:70.85pt 3.0cm 70.85pt 3.0cm;}
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]-->
        <div class="WordSection1">
          <p class="MsoNormal"><span style="mso-fareast-language:EN-US"
              lang="EN-US">In my opinion, Marita's suggestion is an
              affirmation of what is in the SAC101. And I agree.<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="mso-fareast-language:EN-US"
              lang="EN-US">Regards<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="mso-fareast-language:EN-US"
              lang="EN-US"><o:p> </o:p></span></p>
          <p class="MsoNormal"><span style="mso-fareast-language:EN-US"
              lang="EN-US">Alberto<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="mso-fareast-language:EN-US"
              lang="EN-US"><o:p> </o:p></span></p>
          <div>
            <div style="border:none;border-top:solid #E1E1E1
              1.0pt;padding:3.0pt 0cm 0cm 0cm">
              <p class="MsoNormal"><b><span lang="ES">De:</span></b><span
                  lang="ES"> ALAC <a class="moz-txt-link-rfc2396E"
                    href="mailto:alac-bounces@atlarge-lists.icann.org"
                    moz-do-not-send="true"><alac-bounces@atlarge-lists.icann.org></a>
                  <b>En nombre de </b>Alan Greenberg<br>
                  <b>Enviado el:</b> martes, 28 de agosto de 2018 05:43
                  p.m.<br>
                  <b>Para:</b> Holly Raiche <a
                    class="moz-txt-link-rfc2396E"
                    href="mailto:h.raiche@internode.on.net"
                    moz-do-not-send="true"><h.raiche@internode.on.net></a>;
                  Joanna Kulesza <a class="moz-txt-link-rfc2396E"
                    href="mailto:jkuleszaicann@gmail.com"
                    moz-do-not-send="true"><jkuleszaicann@gmail.com></a><br>
                  <b>CC:</b> <a class="moz-txt-link-abbreviated"
                    href="mailto:alac@atlarge-lists.icann.org"
                    moz-do-not-send="true">alac@atlarge-lists.icann.org</a><br>
                  <b>Asunto:</b> Re: [ALAC] EPDP Early input<o:p></o:p></span></p>
            </div>
          </div>
          <p class="MsoNormal"><o:p> </o:p></p>
          <p class="MsoNormal">As I replied to Marita, I can live with
            the short statement she suggested but I would also like to
            understand what reservations there are about the specific
            issues addressed in SAC101. Although there are items there
            that I was not previously aware of, as far as I can tell
            (and I may have missed something), all of their
            recommendations are in support of providing adequate access
            for security professionals.<br>
            <br>
            Alan<br>
            <br>
            At 28/08/2018 04:17 PM, Holly Raiche wrote:<br>
            <br>
            <o:p></o:p></p>
          <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
            <p class="MsoNormal">Joanna, Marita- that’s what this list
              is for - listening to each other, and I”m really pleased
              to hear both of your voices.  The only way we can ever
              reach a real consensus is to speak up - and then listen
              respectfully - so great that both of you spoke up.<br>
              <br>
              Holly<br>
              On 29 Aug 2018, at 6:03 am, Joanna Kulesza <<a
                href="mailto:jkuleszaicann@gmail.com"
                moz-do-not-send="true">jkuleszaicann@gmail.com</a> >
              wrote:<br>
              <br>
              <br>
              <o:p></o:p></p>
            <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
              <p class="MsoNormal">Thank you Marita. I am fully aware of
                that controversy hence my concern. SSAC view of
                adequate/tiered access might (?) be different from ours,
                that's the reason for my questions. Just a newcomer
                looking to learn ;) <br>
                <br>
                Looking forward to hearing other views,<br>
                J.<br>
                <br>
                W dniu wtorek, 28 sierpnia 2018 Marita Moll <<a
                  href="mailto:mmoll@ca.inter.net"
                  moz-do-not-send="true">mmoll@ca.inter.net</a>>
                napisaÅ‚(a):<br>
                > 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.<br>
                ><br>
                > Marita<br>
                ><br>
                > On 8/28/2018 3:35 PM, Joanna Kulesza wrote:<br>
                ><br>
                > 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 justt 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>
                ><br>
                > _______________________________________________<br>
                > ALAC mailing list<br>
                > <a href="mailto:ALAC@atlarge-lists.icann.org"
                  moz-do-not-send="true">ALAC@atlarge-lists.icann.org</a><br>
                > <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>
                ><br>
                > At-Large Online: <a
                  href="http://www.atlarge.icann.org/"
                  moz-do-not-send="true">http://www.atlarge.icann.org</a>
                <br>
                > 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>
                > _______________________________________________<br>
                ALAC mailing list<br>
                <a href="mailto:ALAC@atlarge-lists.icann.org"
                  moz-do-not-send="true">ALAC@atlarge-lists.icann.org</a><br>
                <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>
                <br>
                At-Large Online: <a
                  href="http://www.atlarge.icann.org/"
                  moz-do-not-send="true">http://www.atlarge.icann.org</a><br>
                ALAC Working Wiki: <a
href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+%28ALAC"
                  moz-do-not-send="true">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC</a>
                )<o:p></o:p></p>
            </blockquote>
            <p class="MsoNormal"><br>
              _______________________________________________<br>
              ALAC mailing list<br>
              <a href="mailto:ALAC@atlarge-lists.icann.org"
                moz-do-not-send="true">ALAC@atlarge-lists.icann.org</a><br>
              <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>
              <br>
              At-Large Online: <a href="http://www.atlarge.icann.org/"
                moz-do-not-send="true">http://www.atlarge.icann.org</a><br>
              ALAC Working Wiki: <a
href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+%28ALAC"
                moz-do-not-send="true">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC</a>
              )<o:p></o:p></p>
          </blockquote>
        </div>
        <br>
        <fieldset class="mimeAttachmentHeader"></fieldset>
        <br>
        <pre wrap="">_______________________________________________
ALAC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ALAC@atlarge-lists.icann.org" moz-do-not-send="true">ALAC@atlarge-lists.icann.org</a>
<a class="moz-txt-link-freetext" href="https://atlarge-lists.icann.org/mailman/listinfo/alac" moz-do-not-send="true">https://atlarge-lists.icann.org/mailman/listinfo/alac</a>

At-Large Online: <a class="moz-txt-link-freetext" href="http://www.atlarge.icann.org" moz-do-not-send="true">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+%28ALAC%29" moz-do-not-send="true">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a></pre>
      </blockquote>
      <br>
      <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>