<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p><font size="+1"><font face="Lucida Grande">Indeed, happy to help
          with this.</font></font></p>
    <p><font size="+1"><font face="Lucida Grande">Stephanie</font></font><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 2017-05-05 05:45, Rafik Dammak
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAH5sTh=CtGodN2ZWPMMR2zvWzmgMczwABiBfYriM29y+d0J61A@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <div dir="ltr">Hi all,
        <div><br>
        </div>
        <div>we have a new public comment open and I am sending this as
          a call for volunteers who want to take the lead on drafting a
          NCSG statement. It is a good opportunity for those with strong
          interest on data protection. </div>
        <div><br>
        </div>
        <div>I think that Stephanie participated in the group tasked to
          discuss the Whois conflict with national laws and she can
          probably share some background here.</div>
        <div><br>
        </div>
        <div>Best,</div>
        <div><br>
        </div>
        <div>Rafik<br>
          <br>
          <div class="gmail_quote">---------- Forwarded message
            ----------<br>
            <br>
            <div bgcolor="white" link="blue" vlink="purple" lang="EN-US">
              <div class="m_1661760520410877506WordSection1">
                <p class="MsoNormal"><span
                    style="font-size:11.0pt;font-family:Calibri"> </span></p>
                <div style="border:none;border-top:solid #b5c4df
                  1.0pt;padding:3.0pt 0in 0in 0in">
                  <p class="MsoNormal"><b><span
                        style="font-family:Calibri;color:black">From: </span>
                    </b><span style="font-family:Calibri;color:black">ICANN
                      News Alert <<a moz-do-not-send="true"
                        href="mailto:no-reply@external.icann.org"
                        target="_blank">no-reply@external.icann.org</a>><br>
                      <b>Reply-To: </b>"<a moz-do-not-send="true"
                        href="mailto:no-reply@external.icann.org"
                        target="_blank">no-reply@external.icann.org</a>"
                      <<a moz-do-not-send="true"
                        href="mailto:no-reply@external.icann.org"
                        target="_blank">no-reply@external.icann.org</a>><br>
                      <b>Date: </b>Thursday, May 4, 2017 at 01:30<br>
                      <b>To: </b>Marika Konings <<a
                        moz-do-not-send="true"
                        href="mailto:marika.konings@icann.org"
                        target="_blank">marika.konings@icann.org</a>><br>
                      <b>Subject: </b>[Ext] ICANN News Alert -- Revised
                      ICANN Procedure for Handling Whois Conflicts with
                      Privacy Law: Assessment and Next Steps Now
                      Available for Public Comment</span></p>
                </div>
                <div>
                  <p class="MsoNormal"> </p>
                </div>
                <div style="border:solid #cccccc 1.0pt;padding:8.0pt
                  8.0pt 8.0pt 8.0pt">
                  <div>
                    <p class="MsoNormal"><a moz-do-not-send="true"
href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=FlLnWuWfHq02ox_3kxWHFf4D9p7Hlq8vaIH10JNTVvI&s=6V4WSfJlCvfGHagL0A61eO3gp0CdwQGAaDKw_lwpNWo&e="
                        target="_blank"><span
                          style="text-decoration:none"><img
                            moz-do-not-send="true"
                            id="m_1661760520410877506_x0000_i1025"
src="https://www.icann.org/sites/default/files/assets/icann-primary-logo-94x94-en.png"
                            alt="CANN" height="94" border="0" width="94"></span>[icann.org]</a>
                    </p>
                    <h2>News Alert</h2>
                    <p
                      style="margin-right:0in;margin-bottom:7.5pt;margin-left:0in">
                      <span style="font-family:Arial"><a
                          moz-do-not-send="true"
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_announcement-2D2017-2D05-2D03-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=FlLnWuWfHq02ox_3kxWHFf4D9p7Hlq8vaIH10JNTVvI&s=6Eivc2vwZqN_e1JXuWLbbADqE8SwODCZpZh_nucxv68&e="
                          target="_blank">https://www.icann.org/news/<wbr>announcement-2017-05-03-en[<wbr>icann.org]</a></span></p>
                    <div class="MsoNormal"
                      style="margin-top:15.0pt;text-align:center"
                      align="center">
                      <hr align="center" size="2" width="100%">
                    </div>
                    <h2 style="margin-bottom:0in;margin-bottom:.0001pt">Revised
                      ICANN Procedure for Handling Whois Conflicts with
                      Privacy Law: Assessment and Next Steps Now
                      Available for Public Comment</h2>
                    <p
style="margin-right:0in;margin-bottom:0in;margin-left:0in;margin-bottom:.0001pt">3
                      May 2017</p>
                    <p>LOS ANGELES – 3 May 2017 – The Internet
                      Corporation for Assigned Names and Numbers (ICANN)
                      today published a paper, "Revised ICANN Procedure
                      for Handling Whois Conflicts with Privacy Law:
                      Assessment and Next Steps," for public comment.</p>
                    <p><strong><a moz-do-not-send="true"
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system_files_files_whois-2Dprivacy-2Dconflicts-2Dprocedure-2D03may17-2Den.pdf&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=FlLnWuWfHq02ox_3kxWHFf4D9p7Hlq8vaIH10JNTVvI&s=AFF2DPSvZ3TgeLC-8lrmCCBUTDPwPef3SVwBvlXW0KI&e="
                          target="_blank">Read the Revised ICANN
                          Procedure for Handling Whois Conflicts with
                          Privacy Law: Assessment and Next
                          Steps[icann.org]</a></strong> [PDF, 159 KB].</p>
                    <p>This paper is available for public comment
                      through 12 June 2017. Feedback will be
                      incorporated into a report of public comments and
                      provided to the Generic Names Supporting
                      Organization (GNSO) Council for their review and
                      consideration.</p>
                    <p><strong><a moz-do-not-send="true"
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2Dcomments_whois-2Dprivacy-2Dlaw-2D2017-2D05-2D03-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=FlLnWuWfHq02ox_3kxWHFf4D9p7Hlq8vaIH10JNTVvI&s=q6EIeQotm2_QYjG4lebrrBkaHljOPA1SRCgXvOoCNVc&e="
                          target="_blank">Comment on the Revised ICANN
                          Procedure for Handling Whois Conflicts with
                          Privacy Law: Assessment and Next
                          Steps[icann.org]</a></strong>.</p>
                    <p>In accordance with the <a moz-do-not-send="true"
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_pages_whois-2Dprivacy-2Dconflicts-2Dprocedure-2D2008-2D01-2D17-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=FlLnWuWfHq02ox_3kxWHFf4D9p7Hlq8vaIH10JNTVvI&s=JVtDVVlkiVKJlfNhAHNYjoWK5MSHkcxOLn9mfm2Hb64&e="
                        target="_blank">
                        ICANN Procedure for Handling Whois Conflicts
                        with Privacy Law (Whois Procedure)[icann.org]</a>,
                      this paper opens a review process to gather
                      community input on the effectiveness of the
                      revised Whois Procedure, which was made effective
                      on 18 April 2017. Furthermore, as requested by the
                      GNSO Council, ICANN is publishing this paper to
                      provide analysis of and solicit community input on
                      the practicality and feasibility of the triggers,
                      as well as suggestions for moving forward with the
                      review. Outputs from this assessment and comment
                      process are expected to inform the next periodic
                      review of the procedure.</p>
                    <p>The Whois Procedure has recently been updated,
                      although no ICANN-accredited registrar or registry
                      operator to date has formally invoked the
                      procedure. As a result, this analysis is based
                      solely on community discussions and input received
                      during the
                      <a moz-do-not-send="true"
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_drafts_iag-2Dreview-2Dwhois-2Dconflicts-2Dprocedure-2D23may16-2Den.pdf&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=FlLnWuWfHq02ox_3kxWHFf4D9p7Hlq8vaIH10JNTVvI&s=iA9BlMBg6D_w9aDcbBYK0tHeze09v7D_jlxJiE932k0&e="
                        target="_blank">
                        previous review[gnso.icann.org]</a> [PDF, 155
                      KB], which related to allowing for evaluation of
                      an additional trigger for invoking the procedure.
                      It also draws upon ICANN's experience
                      administering other processes where a contracted
                      party is seeking ICANN's approval for new
                      services, or waiving certain contractual
                      requirements, as a point of comparison for the
                      implementation of the procedure.</p>
                    <h3>About ICANN</h3>
                    <p><em>ICANN's mission is to help ensure a stable,
                        secure and unified global Internet. To reach
                        another person on the Internet, you have to type
                        an address into your computer - a name or a
                        number. That address has to be unique so
                        computers know where to find each other. ICANN
                        helps coordinate and support these unique
                        identifiers across the world. ICANN was formed
                        in 1998 as a not-for-profit public-benefit
                        corporation and a community with participants
                        from all over the world. ICANN and its community
                        help keep the Internet secure, stable and
                        interoperable. It also promotes competition and
                        develops policy for the top-level of the
                        Internet's naming system and facilitates the use
                        of other unique Internet identifiers. For more
                        information please visit:
                        <a moz-do-not-send="true"
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=FlLnWuWfHq02ox_3kxWHFf4D9p7Hlq8vaIH10JNTVvI&s=W1cz9M9nk_PfKsxr4Zt6P_5CLDlAKZTsgrAVo_569x8&e="
                          target="_blank">
                          www.icann.org[icann.org]</a>.</em></p>
                  </div>
                </div>
                <p class="MsoNormal" style="margin-bottom:12.0pt"> </p>
              </div>
            </div>
            <br>
          </div>
          <br>
        </div>
      </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">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>