<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Yeah, I think the broad action like explaining in general + a
      call for a community-developed model would be attacking this, er,
      paper (I won't even call it a model!) indirectly anyway. Once the
      community agrees to start the process of accreditation -- I
      believe there is no way to implement bilateral/unilateral actions
      of certain constituencies because it will contradict to the
      on-going process at ICANN -- or may be am naïve but at least the
      risk of this IPC/BC "proposal" or whatever passing though anyhow
      would be significantly reduced. <br>
    </p>
    <p>Cheers,</p>
    <p>Tanya <br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 18/06/18 16:30, Stephanie Perrin
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:f73f536f-f8ef-7bb3-6846-b9ca18325232@mail.utoronto.ca">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <p><font size="+1"><font face="Lucida Grande">I am also of two
            minds... this is why I am trying to get a blog out on the
            matter, prior to Panama.  We need to explain a few of the
            fundamental facts about accreditation.  I thought I would
            try to do that in a very basic blog.  Given the actual
            number of requests for data that the registrars are
            receiving (and that the ccTLDs have been receiving prior to
            this whole GDPR thing) the volume may not support a tiered
            access model....so I think it is more important to comment
            to ICANN more broadly, not respond to them.  On the other
            hand....guess who ICANN listens to, we may therefore need to
            get a direct attack on the record.  We should discuss this
            in Panama in my view.</font></font></p>
      <p><font size="+1"><font face="Lucida Grande">cheers Steph</font></font><br>
      </p>
      <div class="moz-cite-prefix">On 2018-06-18 10:24, Dr. Tatiana
        Tropina wrote:<br>
      </div>
      <blockquote type="cite"
        cite="mid:e3304948-09e1-a464-15fb-439a33faf01d@mpicc.de">
        <p>Ayden,</p>
        <p>thank you. I am of two mind about this - I don't want us to
          legitimise it anyhow, but not tearing it apart and not
          resisting it might do us more good than bad. We might stand on
          the position that the model has to be developed by the
          community (and in this regard this model has a major
          procedural flow), however, it means that we have to insist on
          the Council that the work on the accreditation should start
          urgently. I am afraid not everyone on the council would share
          the same sentiment - IPC/BC apparently could say they have a
          model proposal and CPH might potentially argue that they have
          other priorities. May be CPH could be convinced when they take
          into account Akram's position. <br>
        </p>
        <p>I think we have to argue procedure-wise first without going
          into the content of this proposal - otherwise by fighting
          about the content we just somehow legitimise it more. Walking
          a thin line here, because they might try to advance it and
          push it forward - but the point that the major parts of the
          community had no participation and no influence on the content
          might play a role in declining this process-wise.</p>
        <p>Would be happy to hear further thoughts....</p>
        <p>Cheers,</p>
        <p>Tanya <br>
        </p>
        <br>
        <div class="moz-cite-prefix">On 18/06/18 15:52, Ayden Férdeline
          wrote:<br>
        </div>
        <blockquote type="cite"
cite="mid:9TqLBwIPS_mhG2fO7R9JYKZnb28TkW5M4ZvgmxzxEJc6X9P5Remd7kHiVezNrUZirBHj7_-7bfmp2J36Qgwspb6rNnQjSHFAmqCR1LBxADA=@ferdeline.com">
          <div>Thoughts -- do we legitimise this process by commenting,
            tearing it apart, or just pay no attention to it? It is a
            very problematic proposal.... I hope it is not being taken
            seriously anywhere, but given Akram's comments quoted in
            Domain Incite last week (i.e. we will have an accreditation
            model very soon as the community wants it), maybe it is...</div>
          <div><br>
          </div>
          <div class="protonmail_signature_block">
            <div class="protonmail_signature_block-user">
              <div>- Ayden  <br>
              </div>
            </div>
            <div class="protonmail_signature_block-proton
              protonmail_signature_block-empty"><br>
            </div>
          </div>
          <div><br>
          </div>
          <div>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br>
          </div>
          <div> On 18 June 2018 3:37 PM, Vayra, Fabricio (Perkins Coie)
            <a class="moz-txt-link-rfc2396E"
              href="mailto:FVayra@perkinscoie.com"
              moz-do-not-send="true"><FVayra@perkinscoie.com></a>
            wrote:<br>
          </div>
          <div> <br>
          </div>
          <blockquote class="protonmail_quote" type="cite">
            <div class="WordSection1">
              <p class="MsoNormal">Please see attached version 1.6 of
                the Accreditation and Access Model that includes tweaks
                to the second paragraph under the introduction in Annex
                I: Registration Directory Service Accreditation
                Authority (RDSAA).<br>
              </p>
              <p class="MsoNormal"> <br>
              </p>
              <p class="MsoNormal">Thanks and we look forward to your
                further input.<br>
              </p>
              <p class="MsoNormal"> <br>
              </p>
              <p class="MsoNormal"><b><span class="colour"
                    style="color:black"><span class="font"
                      style="font-family:Arial, sans-serif"><span
                        class="size" style="font-size:10pt">Fabricio
                        Vayra</span></span></span></b><b><span
                    class="colour" style="color:rgb(214, 0, 28)"><span
                      class="font" style="font-family:Arial, sans-serif"><span
                        class="size" style="font-size:10pt"> </span></span></span></b><b><span
                    class="colour" style="color:rgb(117, 120, 123)"><span
                      class="font" style="font-family:Arial, sans-serif"><span
                        class="size" style="font-size:10pt">| </span></span></span></b><b><span
                    class="colour" style="color:rgb(214, 0, 28)"><span
                      class="font" style="font-family:Arial, sans-serif"><span
                        class="size" style="font-size:10pt">Perkins Coie
                        LLP</span></span></span></b><br>
              </p>
              <p class="MsoNormal"><b><span class="colour"
                    style="color:rgb(117, 120, 123)"><span class="font"
                      style="font-family:Arial, sans-serif"><span
                        class="size" style="font-size:7.5pt">PARTNER</span></span></span></b><br>
              </p>
              <p class="MsoNormal"><span class="colour"
                  style="color:rgb(117, 120, 123)"><span class="font"
                    style="font-family:Arial, sans-serif"><span
                      class="size" style="font-size:7.5pt">D.
                      +1.202.654.6255</span></span></span><br>
              </p>
              <p class="MsoNormal"> <br>
              </p>
              <div>
                <div style="border:none;border-top:solid #E1E1E1
                  1.0pt;padding:3.0pt 0in 0in 0in">
                  <div><b>From:</b> Vayra, Fabricio (WDC) <br>
                  </div>
                  <div> <b>Sent:</b> Saturday, June 16, 2018 1:29 AM<br>
                  </div>
                  <div> <b>To:</b> '<a class="moz-txt-link-abbreviated"
                      href="mailto:accred-model@icann.org"
                      moz-do-not-send="true">accred-model@icann.org</a>'
                    <a class="moz-txt-link-rfc2396E"
                      href="mailto:accred-model@icann.org"
                      moz-do-not-send="true"><accred-model@icann.org></a><br>
                  </div>
                  <div> <b>Subject:</b> Version 1.6 of the
                    Accreditation and Access Model<br>
                  </div>
                </div>
              </div>
              <p class="MsoNormal"> <br>
              </p>
              <p class="MsoNormal">Attached for discussion and
                additional comment is version 1.6 of the Accreditation
                and Access Model.  This, following further comment and
                input from many parts of the community, is a much richer
                and robust model.  Notably, this version 1.6 contains
                new:<br>
              </p>
              <p class="MsoNormal"> <br>
              </p>
              <ul style="margin-top:0in" type="disc">
                <li style="margin-left:2.25pt;mso-list:l1 level1 lfo3"
                  class="MsoNormal">Annex D: Accreditation Approach for
                  Intellectual Property Owners and Agents<br>
                </li>
                <li style="margin-left:2.25pt;mso-list:l1 level1 lfo3"
                  class="MsoNormal">Annex J: Lawful Bases for Access to
                  WHOIS Data<br>
                </li>
              </ul>
              <p class="MsoNormal"> <br>
              </p>
              <p class="MsoNormal">Many thanks to those who made
                constructive contributions to further developing this
                model.<br>
              </p>
              <p class="MsoNormal">  <br>
              </p>
              <p class="MsoNormal">Thank you again for your input and
                support.<br>
              </p>
              <p class="MsoNormal"> <br>
              </p>
              <p class="MsoNormal"><b><span class="colour"
                    style="color:black"><span class="font"
                      style="font-family:Arial, sans-serif"><span
                        class="size" style="font-size:10pt">Fabricio
                        Vayra</span></span></span></b><b><span
                    class="colour" style="color:rgb(214, 0, 28)"><span
                      class="font" style="font-family:Arial, sans-serif"><span
                        class="size" style="font-size:10pt"> </span></span></span></b><b><span
                    class="colour" style="color:rgb(117, 120, 123)"><span
                      class="font" style="font-family:Arial, sans-serif"><span
                        class="size" style="font-size:10pt">| </span></span></span></b><b><span
                    class="colour" style="color:rgb(214, 0, 28)"><span
                      class="font" style="font-family:Arial, sans-serif"><span
                        class="size" style="font-size:10pt">Perkins Coie
                        LLP</span></span></span></b><br>
              </p>
              <p class="MsoNormal"><b><span class="colour"
                    style="color:rgb(117, 120, 123)"><span class="font"
                      style="font-family:Arial, sans-serif"><span
                        class="size" style="font-size:7.5pt">PARTNER</span></span></span></b><br>
              </p>
              <p class="MsoNormal"><span class="colour"
                  style="color:rgb(117, 120, 123)"><span class="font"
                    style="font-family:Arial, sans-serif"><span
                      class="size" style="font-size:7.5pt">D.
                      +1.202.654.6255</span></span></span><br>
              </p>
              <p class="MsoNormal"> <br>
              </p>
            </div>
            <div><br>
            </div>
            <div>
              <hr><span class="font" style="font-family:Arial"><span
                  class="size" style="font-size:10px"><br>
                  NOTICE: This communication may contain privileged or
                  other confidential information. If you have received
                  it in error, please advise the sender by reply email
                  and immediately delete the message and any attachments
                  without copying or disclosing the contents. Thank you.</span></span></div>
          </blockquote>
          <div><br>
          </div>
          <!--'"--><br>
          <fieldset class="mimeAttachmentHeader"></fieldset>
          <br>
          <pre wrap="">_______________________________________________
NCSG-PC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:NCSG-PC@lists.ncsg.is" moz-do-not-send="true">NCSG-PC@lists.ncsg.is</a>
<a class="moz-txt-link-freetext" href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" moz-do-not-send="true">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a>
</pre>
        </blockquote>
        <br>
        <br>
        <fieldset class="mimeAttachmentHeader"></fieldset>
        <pre class="moz-quote-pre" wrap="">_______________________________________________
NCSG-PC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:NCSG-PC@lists.ncsg.is" moz-do-not-send="true">NCSG-PC@lists.ncsg.is</a>
<a class="moz-txt-link-freetext" href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" moz-do-not-send="true">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a>
</pre>
      </blockquote>
      <!--'"--><br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
NCSG-PC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:NCSG-PC@lists.ncsg.is">NCSG-PC@lists.ncsg.is</a>
<a class="moz-txt-link-freetext" href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>