<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p><font size="+1"><font face="Lucida Grande"> and here is the draft
          redline version</font></font><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 2016-09-28 22:34, Stephanie Perrin
      wrote:<br>
    </div>
    <blockquote
      cite="mid:1da0802d-2e65-58fe-ef2d-772f6cf611ad@mail.utoronto.ca"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <p><font size="+1"><font face="Lucida Grande">I apologize for
            missing the last two meetings.  I was travelling and had
            difficulty connecting.  I have listened to the call of the
            21st, and I am going to listen to the next one as soon as it
            arrives.  I have a number of concerns with the current draft
            purpose statement, and am consulting my NCSG colleagues on a
            proposed redraft which I have done.  As soon as I hear back
            from them I will share it with the list, understanding that
            this is not the same as being on the call.  My concerns are
            basically the following:</font></font></p>
      <p><font size="+1"><font face="Lucida Grande">1.  The purpose of
            the purpose clause exercise was, as far as I understood it,
            to come up with a succinct purpose for the exercise in which
            we are engaged....to limit the exercise to the minimum until
            such  time as we have agreed on policy, as it is generally
            understood that many policy issues have crept into the WHOIS
            and RDS without benefit of a full PDP delberation.  Our
            remit is not to assume those policy issues are a fait
            accompli, it is to examine them, thus the limited scope of
            the purpose clause.  It is a business requirements statement
            for the exercise.<br>
          </font></font></p>
      <p><font size="+1"><font face="Lucida Grande">2.  Several implicit
            assumptions appear to have crept in, namely that an RDS is
            necessary, and that data will be released through it.  We
            have not got there yet.  Discussion of rationales for the
            RDS is straying way too far, in my view. <br>
          </font></font></p>
      <p><font size="+1"><font face="Lucida Grande">3.  While a
            statement of purpose is necessary for the interpretation of
            ICANN's policies with respect to the collection, use,
            retention and disclosure of personal information in the
            context of its registration activities, this is not it.  We
            cannot through this exercise set up a purpose for that,
            because it requires policy decisions, and we are not there
            yet.  A goal can be compliance with national and regional
            law, and with internationally recognized human rights
            obligations, but not crafting the actual purpose statement. 
            I hope that is clear, it is a wee bit convoluted.</font></font></p>
      <p><font size="+1"><font face="Lucida Grande">I will send my
            proposed redline version as soon as possible.  Apologies
            once again for missing the calls.<br>
          </font></font></p>
      <p><font size="+1"><font face="Lucida Grande">Stephanie Perrin</font></font><br>
      </p>
      <br>
      <div class="moz-cite-prefix">On 2016-09-28 13:17, Hollenbeck,
        Scott wrote:<br>
      </div>
      <blockquote
cite="mid:831693C2CDA2E849A7D7A712B24E257F4A48D145@BRN1WNEXMBX01.vcorp.ad.vrsn.com"
        type="cite">
        <meta name="Generator" content="Microsoft Word 14 (filtered
          medium)">
        <style><!--
/* Font Definitions */
@font-face
        {font-family:Cambria;
        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;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:#0563C1;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:#954F72;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;
        font-weight:normal;
        font-style:normal;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:595.0pt 842.0pt;
        margin:1.0in 1.0in 1.0in 1.0in;}
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="color:#1F497D">I found (and
              fixed) two more instances of “gTLD domain names”. Update
              attached.<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
          <div>
            <p class="MsoNormal"><span
                style="font-size:11.0pt;color:#1F497D">Scott</span><span
                style="color:#1F497D"><o:p></o:p></span></p>
          </div>
          <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
          <div style="border:none;border-left:solid blue
            1.5pt;padding:0in 0in 0in 4.0pt">
            <div>
              <div style="border:none;border-top:solid #B5C4DF
                1.0pt;padding:3.0pt 0in 0in 0in">
                <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
                    <a moz-do-not-send="true"
                      class="moz-txt-link-abbreviated"
                      href="mailto:gnso-rds-pdp-wg-bounces@icann.org">gnso-rds-pdp-wg-bounces@icann.org</a>
                    [<a moz-do-not-send="true"
                      class="moz-txt-link-freetext"
                      href="mailto:gnso-rds-pdp-wg-bounces@icann.org">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>]
                    <b>On Behalf Of </b>Marika Konings<br>
                    <b>Sent:</b> Wednesday, September 28, 2016 1:12 PM<br>
                    <b>To:</b> <a moz-do-not-send="true"
                      class="moz-txt-link-abbreviated"
                      href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
                    <b>Subject:</b> [gnso-rds-pdp-wg] For your review -
                    updated RDS Statement of Purpose<o:p></o:p></span></p>
              </div>
            </div>
            <p class="MsoNormal"><o:p> </o:p></p>
            <p class="MsoNormal"><span style="font-size:11.0pt">Dear
                All,<o:p></o:p></span></p>
            <p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
            <p class="MsoNormal"><span style="font-size:11.0pt">Please
                find attached for your review the updated statement of
                purpose which aims to reflect the changes discussed
                during yesterday’s meeting. You are all encouraged to
                review this version, especially the section ‘<span
                  style="color:black">Specific Purposes for Registration
                  Data and Registration Directory Services’, and share
                  your input with the mailing list prior to next week’s
                  meeting. Also note that a couple of WG members (Marc
                  &amp; Fabrizio) volunteered to provide updated
                  language for two specific parts of the document which
                  have been flagged accordingly, so please hold your
                  comments on those parts until the proposed language
                  has been circulated. <o:p></o:p></span></span></p>
            <p class="MsoNormal"><span
                style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
            <p class="MsoNormal"><span
                style="font-size:11.0pt;color:black">Best regards,<o:p></o:p></span></p>
            <p class="MsoNormal"><span
                style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
            <p class="MsoNormal"><span
                style="font-size:11.0pt;color:black">Marika</span><span
                style="font-size:11.0pt"><o:p></o:p></span></p>
            <p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
            <p class="MsoNormal" style="text-autospace:none"><b><span
                  style="font-size:10.0pt">Marika Konings</span></b><span
style="font-size:10.0pt;font-family:&quot;Cambria&quot;,&quot;serif&quot;"><o:p></o:p></span></p>
            <p class="MsoNormal" style="text-autospace:none"><span
                style="font-size:10.0pt">Senior Policy Director &amp;
                Team Leader for the GNSO, Internet Corporation for
                Assigned Names and Numbers (ICANN) </span><span
style="font-size:10.0pt;font-family:&quot;Cambria&quot;,&quot;serif&quot;"><o:p></o:p></span></p>
            <p class="MsoNormal" style="text-autospace:none"><span
                style="font-size:10.0pt">Email: <a
                  moz-do-not-send="true"
                  href="mailto:marika.konings@icann.org">marika.konings@icann.org</a>  </span><span
style="font-size:10.0pt;font-family:&quot;Cambria&quot;,&quot;serif&quot;"><o:p></o:p></span></p>
            <p class="MsoNormal" style="text-autospace:none"><i><span
                  style="font-size:10.0pt"> </span></i><span
style="font-size:10.0pt;font-family:&quot;Cambria&quot;,&quot;serif&quot;"><o:p></o:p></span></p>
            <p class="MsoNormal" style="text-autospace:none"><i><span
                  style="font-size:10.0pt">Follow the GNSO via Twitter
                  @ICANN_GNSO<o:p></o:p></span></i></p>
            <p class="MsoNormal" style="text-autospace:none"><i><span
                  style="font-size:10.0pt">Find out more about the GNSO
                  by taking our <a moz-do-not-send="true"
                    href="http://learn.icann.org/courses/gnso">interactive
                    courses</a> and visiting the <a
                    moz-do-not-send="true"
href="http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers">GNSO
                    Newcomer pages</a>.</span></i><span
style="font-size:10.0pt;font-family:&quot;Cambria&quot;,&quot;serif&quot;"><o:p></o:p></span></p>
            <p class="MsoNormal"><o:p> </o:p></p>
          </div>
        </div>
        <br>
        <fieldset class="mimeAttachmentHeader"></fieldset>
        <br>
        <pre wrap="">_______________________________________________
gnso-rds-pdp-wg mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></pre>
      </blockquote>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
gnso-rds-pdp-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></pre>
    </blockquote>
    <br>
  </body>
</html>