<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html;
      charset=windows-1252">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p><font size="+1"><font face="Lucida Grande">There are a lot of new
          comments on the website
          <a class="moz-txt-link-freetext" href="https://www.icann.org/resources/pages/gdpr-legal-analysis-2017-11-17-en">https://www.icann.org/resources/pages/gdpr-legal-analysis-2017-11-17-en</a></font></font></p>
    <p><font size="+1"><font face="Lucida Grande">Ours have been
          acknowledged but not posted as yet.  I am going to focus on
          some of the rather important ones, like this correspondence
          from the European Commission.  We can bicker about the models
          until the cows come home, what is needed now in my view is
          analysis to combat some of the contributions, which if history
          is anything to go by, will accept some of the submissions as
          truth.  There is a lot of work to do here, volunteers willing
          to do a summary (template might be useful) would be most
          welcome.</font></font></p>
    <p><font size="+1"><font face="Lucida Grande">Kind regards, <br>
        </font></font></p>
    <p><font size="+1"><font face="Lucida Grande">Stephanie<br>
        </font></font></p>
    <p><font size="+1"><font face="Lucida Grande"> </font></font><a
href="https://www.icann.org/en/system/files/correspondence/avramopoulos-et-al-to-marby-29jan18-en.pdf">https://www.icann.org/en/system/files/correspondence/avramopoulos-et-al-to-marby-29jan18-en.pdf</a></p>
    <p><a
href="https://www.icann.org/en/system/files/correspondence/avramopoulos-et-al-to-marby-29jan18-en.pdf"><br>
      </a></p>
    <div><br>
    </div>
    <div><br>
    </div>
    <div class="moz-cite-prefix">On 2018-01-30 10:31, Mueller, Milton L
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CY1PR0701MB12741DD726784132D6386F68A1E40@CY1PR0701MB1274.namprd07.prod.outlook.com">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <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:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;
        color:black;}
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;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;
        color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0in;
        margin-right:0in;
        margin-bottom:0in;
        margin-left:.5in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;
        color:black;}
span.EmailStyle18
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
span.EmailStyle19
        {mso-style-type:personal-reply;
        font-family:"Calibri",sans-serif;
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
/* List Definitions */
@list l0
        {mso-list-id:782043871;
        mso-list-type:hybrid;
        mso-list-template-ids:1496759818 383695534 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        color:black;}
@list l0:level2
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level3
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
@list l0:level4
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level5
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level6
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
@list l0:level7
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level8
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level9
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
--></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">Kathy see
            comments below<o:p></o:p></span></p>
        <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">
          <p style="margin-left:.5in;text-indent:-.25in;mso-list:l0
            level1 lfo1"><!--[if !supportLists]--><span
              style="mso-list:Ignore">1.<span style="font:7.0pt
                "Times New Roman"">      
              </span></span><!--[endif]-->"The purpose of Whois must be
            strictly tied to ICANN's mission." ==> that's absolutely
            true but we don't have that purpose yet (and I have to tell
            you that the RDS Working Group is not doing a great job of
            analyzng "purpose" right now<span style="color:#1F497D"><o:p></o:p></span></p>
          <p>Then we agree. You should then support the comments, which
            focuses on developing a mission-consistent purpose. Your
            logic escapes me<o:p></o:p></p>
          <p><i>unlimited "all you can eat access" by everyone, </i>including
            intellectual property attorneys and law enforcement. That is
            happily going to change!!<o:p></o:p></p>
          <p><span style="color:#1F497D">No, Kathy, it isn’t unless we
              go with model 3 and then define a limited
              mission-consistent purpose for Whois<o:p></o:p></span></p>
          <p class="MsoListParagraph"
            style="text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span
              style="mso-list:Ignore">2.<span style="font:7.0pt
                "Times New Roman"">      
              </span></span><!--[endif]-->"Whois service, like the DNS
            itself, should be globally uniform and not vary by
            jurisdiction." ==> Yes, and that's what the ECO Model and
            Model 2B provide. But, unfortunately, that's Model 3 does
            not provide uniformity; Model 3 provide great
            differentiation of protection, with only private individuals
            being protected, and not the political, sexual, religious,
            educational groups that I discussed in one of my recent
            emails - the array of groups that we protect engaged in huge
            amount of controversial and critical speech and services. <b>The
              ICANN Model 3 here is very clear: </b>"<b>Display unless
              field includes personal data." (ICANN's Proposed Interim
              Models for Compliance, pages 12-14).</b>  Thus, for
            noncommercial organizations, exposure of
            Registrant/Admin/Tech name, address, phone and email will
            remain completely open. Model 2B and ECO do better and
            protect legal and natural persons. That's hugely important -
            and a tribute to our years of work on this subject!<span
              style="color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"><o:p> </o:p></p>
          <p class="MsoNormal"><span style="color:#1F4E79">No, Model 3
              does not have the registrant name. Check your facts,
              please. I don’t think there is anything wrong with having
              the tech contacts name, but here I agree with you that
              the4re is room for discussion and debate about which data
              elements could be made public and which couldn’t. That is
              why it is so unfortunate that the people we had working on
              this issue dropped the ball and put us in a position to
              have to hurriedly develop a position on this. It is also a
              reason why it is bad to have these critical policy
              diuscussions hidden on the PC list and not taking place
              before the membership.<o:p></o:p></span></p>
          <p class="MsoNormal"><o:p> </o:p></p>
          <p class="MsoListParagraph"
            style="text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span
              style="mso-list:Ignore">3.<span style="font:7.0pt
                "Times New Roman"">      
              </span></span><!--[endif]-->"No tiered access solution
            that involves establishing new criteria for access can
            feasibly be created in the next 3 months."  ==> We are
            unlikely to go from infinite public access to completely
            restricted private access right now. The Multistakeholder
            Process won't support that. But the ECO model does a lot to
            help on this particular issue. I'll outline in my next
            email.<span style="color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"><o:p> </o:p></p>
          <p class="MsoNormal"><span
style="color:#1F4E79;mso-style-textfill-fill-color:#1F4E79;mso-style-textfill-fill-alpha:100.0%"><span
                style="color:windowtext">So it sounds like you are
                agreeing that 2B is _<i>not</i>_ an option. Again we are
                in violent agreement.<o:p></o:p></span></span></p>
          <p class="MsoNormal"><span
style="color:#1F4E79;mso-style-textfill-fill-color:#1F4E79;mso-style-textfill-fill-alpha:100.0%"><o:p> </o:p></span></p>
          <p class="MsoNormal"><o:p> </o:p></p>
          <p class="MsoNormal"><o:p> </o:p></p>
          <p class="MsoNormal" style="margin-left:.25in"><o:p> </o:p></p>
        </div>
      </div>
    </blockquote>
  </body>
</html>