<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>I think this discussion has some support for the idea that
      ICANN's contract language should shoot for a minimum of data
      collection consistent with its remit. That would both not encumber
      registrars with contract language and leave them to deal with the
      demands of their national jurisdiction, without having to come
      back to ICANN in search of contract language exceptions. <br>
    </p>
    <p>I don't know if we have any degree of support for the idea that
      ICANN should be present as a stakeholder in the wider Internet
      governance deliberations. I have suggested that ICANN, and its
      various constituencies, should be there both to remind others of
      ICANN's limited remit (to prevent pressure for scope creep) and
      keep informed of emerging governance tendencies where ICANN might
      need to work to protect a DNS where "...  DNS would be globally
      compatible and the market for DNS services would be globally open
      and competitive." <br>
    </p>
    Sam L.<br>
    <br>
    <div class="moz-cite-prefix">On 1/15/2018 11:23 AM, Mueller, Milton
      L wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CY1PR0701MB12742C1BAD29856F9FE8ECB1A1EB0@CY1PR0701MB1274.namprd07.prod.outlook.com">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <meta name="Generator" content="Microsoft Word 15 (filtered
        medium)">
      <!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
      <style><!--
/* Font Definitions */
@font-face
        {font-family:"MS Gothic";
        panose-1:2 11 6 9 7 2 5 8 2 4;}
@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;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
        {font-family:Verdana;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:"\@MS Gothic";
        panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
        {font-family:"Microsoft JhengHei";
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:"\@Microsoft JhengHei";
        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:11.0pt;
        font-family:"Calibri",sans-serif;
        color:black;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        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:12.0pt;
        font-family:"Times New Roman",serif;}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Courier New";
        color:black;}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:Consolas;
        color:black;}
p.msonormal0, li.msonormal0, div.msonormal0
        {mso-style-name:msonormal;
        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;}
span.font
        {mso-style-name:font;}
span.size
        {mso-style-name:size;}
span.colour
        {mso-style-name:colour;}
span.EmailStyle23
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
span.EmailStyle25
        {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;}
--></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"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">I do not think
            we want to maximize the ability of registrars to conform to
            national law. ICANN was created specifically to be a global
            governance agency so that DNS would be globally compatible
            and the market for DNS services would be globally open and
            competitive. Encouraging variations in practices across
            jurisdictions moves us away from that goal.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">The simple
            solution to this dilemma is for Whois to conform narrowly to
            ICANN’s legitimate purpose in collecting the data and thus _<i>minimize</i>_
            the data that it collects and makes publicly available.
            Thus, while I agree ICANN not should press for higher
            national privacy standards, I do agree with Ayden that if it
            minimizes what it collects and makes available it flies
            above the problem of jurisdictional variation. If specific
            jurisdictions want to regulate local registrars to force
            them to collect and/or disseminate more, that is
            (unfortunately) something they will have to deal with, but
            ICANN should make its global whois requirements well above
            the threshold that would violate the privacy laws of any
            country.
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">In this respect
            ICANN is not the standard setter for all worldwide privacy,
            but it is, and is supposed to be, the global standard setter
            for DNS policy.
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Dr. Milton
            Mueller<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Professor,
            School of Public Policy<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Georgia
            Institute of Technology<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><a
            href="http://www.internetgovernance.org/"
            moz-do-not-send="true"><span
              style="color:#1F497D;text-decoration:none"><img
                id="Picture_x0020_1"
                src="cid:part1.ECD6EED4.BBA5FF95@yorku.ca"
                alt="IGP_logo_gold block_email sig" class="" height="44"
                width="205" border="0"></span></a><span
            style="color:#1F497D"><o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
      </div>
    </blockquote>
    <br>
  </body>
</html>