<div dir="ltr">hi all<div><br></div><div>On a procedural point - Bruce, the CCWG&#39;s second proposal does recommend that the AOC be drawn to a close. </div><div><br></div><div>Is your message a statement that ICANN does not agree with that recommendation?  Or is it simply an assurance that ICANN has no plans to end the AOC, implicitly remaining open to adopting that recommendation?</div><div><br></div><div>best</div><div>Jordan</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 2 September 2015 at 14:34, Stephanie Perrin <span dir="ltr">&lt;<a href="mailto:stephanie.perrin@mail.utoronto.ca" target="_blank">stephanie.perrin@mail.utoronto.ca</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000">
    May I draw to everyone&#39;s attention the fact that there are now 101
    national privacy laws in the world. (Greenleaf, 2014).  All input
    received from the assembled data commissioners in charge of
    overseeing compliance with those laws has indicated that they
    contradict the next sentence:  <font color="#ff0000">Such existing
      policy requires that ICANN implement measures to maintain timely,
      unrestricted and public access to accurate and complete WHOIS
      information, including registrant, technical, billing, and
      administrative contact information.</font>
    <div><font color="#ff0000"><font color="#330033">This advice,
          elaborating how the various components of that sentence are
          not in compliance with data protection rights has been sent to
          ICANN in various ways since 2000 (I am rounding off there,
          there were certainly earlier indications of problems provided
          from the inception of ICANN).  Does it not seem that it is
          time to review the wisdom of a policy that disregards privacy
          rights?<br>
          Kind regards, <br>
          Stephanie Perrin<br>
        </font>
      </font></div><div><div class="h5">
    <br>
    <br>
    <div>On 2015-09-01 21:31, Steve DelBianco
      wrote:<br>
    </div>
    </div></div><blockquote type="cite"><div><div class="h5">
      
      <div>
        <div><font face="Calibri,sans-serif">Thanks, Bruce.  For
            comparison purposes, I pasted the CCWG’s proposed language
            below your text.</font></div>
        <div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:16px">
        </div>
      </div>
      <div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:16px">
        <br>
      </div>
      <span style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:16px">
        <div style="font-family:Calibri;font-size:12pt;text-align:left;color:black;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt">
          <span style="font-weight:bold">From: </span>&lt;<a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank">accountability-cross-community-bounces@icann.org</a>&gt;
          on behalf of Bruce Tonkin<br>
          <span style="font-weight:bold">Date: </span>Tuesday,
          September 1, 2015 at 9:24 PM<br>
          <span style="font-weight:bold">To: </span>&quot;<a href="mailto:accountability-cross-community@icann.org" target="_blank">accountability-cross-community@icann.org</a>&quot;<br>
          <span style="font-weight:bold">Subject: </span>[CCWG-ACCT]
          Proposed WHOIS language<br>
        </div>
        <div><br>
        </div>
        <div>
          <div>
            <div>Below is some suggested language regarding WHOIS
              reviews for consideration by the CCWG when considering
              what to incorporate into the bylaws regarding the AoC
              reviews.</div>
            <div><br>
            </div>
            <div>Note the Board has no plans to cancel the current AoC -
              so the language in the AoC -  still stands until the
              community and NTIA wish to change it.  
            </div>
            <div><br>
            </div>
            <div>This language however tries to contemplate an
              environment where we are introducing a new gTLD Directory
              Service as a result of policy development within  the
              GNSO, as well as most likely continuing to run the
              existing WHOIS service for some time.</div>
            <div><br>
            </div>
            <div>Regards,</div>
            <div>Bruce Tonkin</div>
            <div><br>
            </div>
            <div>ICANN commits to enforcing its policy relating to the
              current WHOIS and any future gTLD Directory Service,
              subject to applicable laws, and working with the community
              to explore structural changes to improve accuracy and
              access to gTLD registration data, as well as consider
              safeguards for protecting data. </div>
            <div><br>
            </div>
            <div>This Review includes a commitment that becomes part of
              ICANN Bylaws, regarding enforcement of the current WHOIS
              and any future gTLD Directory Service policy requirements.</div>
            <div><br>
            </div>
            <div>The Board shall cause a periodic Review to assess the
              extent to which WHOIS/Directory Services policy is
              effective and its implementation meets the legitimate
              needs of law enforcement, promotes consumer trust, and
              safeguards data.
            </div>
            <div><br>
            </div>
            <div>The Review Team shall assess the extent to which prior
              Review recommendations have been completed, and the extent
              to which implementation has had the intended effect.</div>
            <div><br>
            </div>
            <div>This periodic Review shall be convened no less
              frequently than every five years, measured from the date
              the Board took action on previous review recommendations.</div>
            <div>_______________________________________________</div>
          </div>
        </div>
      </span>
      <div>
        <div><font color="#ff0000">From CCWG 2nd draft proposal, page
            81:</font></div>
        <div><font color="#ff0000"><br>
          </font></div>
        <div><font color="#ff0000">ICANN commits to enforcing its
            existing policy relating to WHOIS/Directory Services,
            subject to applicable laws. Such existing policy requires
            that ICANN implement measures to maintain timely,
            unrestricted and public access to accurate and complete
            WHOIS information, including registrant, technical, billing,
            and administrative contact information.</font></div>
        <div><font color="#ff0000"><br>
          </font></div>
        <div><font color="#ff0000">The Board shall cause a periodic
            Review to assess the extent to which WHOIS/Directory
            Services policy is effective and its implementation meets
            the legitimate needs of law enforcement and promotes
            consumer trust. </font></div>
      </div>
      <div><font color="#ff0000"><br>
        </font></div>
      <div><font color="#ff0000">This Review will consider the OECD
          guidelines regarding privacy, as defined by the OECD in 1980
          and amended in 2013.</font></div>
      <div><font color="#ff0000"><br>
        </font></div>
      <span>
        <div>
          <div>
            <div><font color="#ff0000" face="Calibri,sans-serif">The
                Review Team shall assess the extent to which prior
                Review recommendations have been implemented.</font></div>
          </div>
        </div>
      </span>
      <div><font color="#ff0000"><br>
        </font></div>
      <div><font color="#ff0000">This periodic Review shall be convened
          no less frequently than every five years, measured from the
          date the previous Review was convened.</font></div>
      <br>
      <fieldset></fieldset>
      <br>
      </div></div><span class=""><pre>_______________________________________________
Accountability-Cross-Community mailing list
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
</pre>
    </span></blockquote>
    <br>
  </div>

<br>_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr" style="font-size:small">Jordan Carter<br><br>Chief Executive <br><b>InternetNZ</b><br></div><div dir="ltr" style="font-size:small"><br>+64-495-2118 (office) | +64-21-442-649 (mob)<br>Email: <a href="mailto:jordan@internetnz.net.nz" style="color:rgb(17,85,204)" target="_blank">jordan@internetnz.net.nz</a> <br>Skype: jordancarter<br></div><div style="font-size:small">Web: <a href="http://www.internetnz.nz" target="_blank">www.internetnz.nz</a> </div><div dir="ltr" style="font-size:small"><br><i>A better world through a better Internet </i></div><br></div></div></div></div></div></div>
</div>