<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<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:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:Verdana;
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;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:"\@Microsoft JhengHei";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;
mso-fareast-language:ZH-CN;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;
mso-fareast-language:ZH-CN;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";
color:black;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;
mso-fareast-language:ZH-CN;}
span.font
{mso-style-name:font;}
span.size
{mso-style-name:size;}
span.colour
{mso-style-name:colour;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle28
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle29
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle31
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle32
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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]-->
</head>
<body bgcolor="white" lang="EN-GB" link="blue" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US">Thank you for making my point differently but more eloquently.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US">For you the means justified the end. The end, plainly, was to find a way to allow ICANN to escape from what you considered to be “fundamentally dishonourable” arrangements or a set
of promises extracted by the USG under duress.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US">So how do you think it’s going in the sunny uplands of freedom? ICANN is run by a duopoly of Registries and Registrars with the ICANN bureaucracy as a dependent. And within the
duopoly there is another duopoly. Two companies (Verisign and GoDaddy) alone account for 40% of its total revenues, or they did last time I checked.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US">George</span><span style="color:windowtext;mso-fareast-language:EN-US"> Bernard Shaw famously said all professions are a conspiracy against the laity. ICANN has taken this to new
heights. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US">It has erected a redoubt of labyrinthine, obscure, expensive and protracted processes all of which combine to discourage new entrants, preserve the status quo or slow down the rate
of change to the greatest extent possible, always in favour of the financial interests of Registries, Registrars and ICANN itself.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US">“Bottom up, consensus-driven multi-stakeholder model” might mean something to the initiated but in the end it is simply a method of working that counts for nothing if it produces
mayhem or evil. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US">Speaking of the “ICANN community” is an attempt to give an undeserved democratic patina to what is, in reality, a collection of groups or entities with a material interest in the
affairs of ICANN. And not being part of one of those insider groups means ICANN can and will trample on or ignore your rights or concerns.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US">The ICANN “community” should include stakeholders without loud voices, deep pockets, big muscles and time to fly around the world to attend ICANN gatherings. Equally it should include
many more people whose livelihoods are not likely to be affected by the outcome of decisions ICANN might make.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US">There is nothing wrong, and a great deal that is right about ICANN wanting to talk to as many people as possible before making a decision, but ICANN is not a modern-day Pontius Pilate,
able to dodge any responsibility for its own actions by referring to a “community” that only exists within their own self- constructed and self-serving bubble</span><span style="color:windowtext;mso-fareast-language:EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="color:windowtext;mso-fareast-language:EN-US"><o:p> </o:p></span></a></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="color:windowtext">From:</span></b><span lang="EN-US" style="color:windowtext"> Mueller, Milton L [mailto:milton@gatech.edu]
<br>
<b>Sent:</b> 19 January 2018 21:38<br>
<b>To:</b> John Carr <JohnC1912@msn.com>; NCSG-DISCUSS@LISTSERV.SYR.EDU<br>
<b>Subject:</b> RE: Data Protection and Privacy Update: Seeking Community Feedback on Proposed Compliance Models<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">I don’t understand what you are talking about. Of course there was an intention to honor the AoC when it was signed. The AoC did not “get ICANN out of the clutches of the
federal government, it was an example of how ICANN was still in the clutches of the federal government, although at the time, it was a small step away from more direct USG control.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">Everything about it – including the totally illegitimate commitment to maintain a policy imposed on it by the USG and ignoring ICANN’s organic policy development process
– was “honored” if one can use that word for a fundamentally dishonorable commitment - until the reforms of 2016.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span lang="EN-US" style="color:windowtext">From:</span></b><span lang="EN-US" style="color:windowtext"> John Carr [<a href="mailto:JohnC1912@msn.com">mailto:JohnC1912@msn.com</a>]
</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">In other words there was never a genuine intention to honour it. It was insincerely signed simply to get ICANN out of the clutches of the Federal Government?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Sent from <a href="https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgo.microsoft.com%2Ffwlink%2F%3FLinkId%3D550986&data=02%7C01%7C%7C0d295d3077ff4a0946bb08d55f84e667%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636519946758216548&sdata=Lasm2e%2F%2Fz5vLfCWTmQZOGjqnc6AdW5nK8DJLjhNrH8c%3D&reserved=0">
Mail</a> for Windows 10<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun;color:windowtext">
<hr size="2" width="98%" align="center">
</span></div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Mueller, Milton L <<a href="mailto:milton@gatech.edu">milton@gatech.edu</a>><br>
<b>Sent:</b> Tuesday, January 16, 2018 7:13:35 PM<br>
<b>To:</b> John Carr; <a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU">NCSG-DISCUSS@LISTSERV.SYR.EDU</a><br>
<b>Subject:</b> RE: Data Protection and Privacy Update: Seeking Community Feedback on Proposed Compliance Models</span><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun;color:windowtext">
<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun;color:windowtext"> <o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">The Affirmation of Commitments is an artifact of an ICANN subject to unilateral control by the US government. The Whois commitment in it reflects political pressure placed on the Commerce Department
by US-based trademark and law enforcement interests. Post-transition, the Affirmation has no meaning or consequence other than what was agreed in the accountability reforms of 2016.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">--MM<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="color:windowtext">From:</span></b><span lang="EN-US" style="color:windowtext"> John Carr [<a href="mailto:JohnC1912@msn.com">mailto:JohnC1912@msn.com</a>]
<br>
<b>Sent:</b> Monday, January 15, 2018 2:03 PM<br>
<b>To:</b> Mueller, Milton L <<a href="mailto:milton@gatech.edu">milton@gatech.edu</a>>;
<a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU">NCSG-DISCUSS@LISTSERV.SYR.EDU</a><br>
<b>Subject:</b> RE: Data Protection and Privacy Update: Seeking Community Feedback on Proposed Compliance Models<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">In the “Affirmation of Commitments”” didn’t ICANN promise to maintain WHOIS as an accurate and public data base? Shouldn’t the objective be to stay as close to that as possible in every national jurisdiction
where that is legally allowed?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">Or has ICANN decided that the promise it made in the Affirmation should now be formally abandoned or changed?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="color:windowtext">From:</span></b><span lang="EN-US" style="color:windowtext"> NCSG-Discuss [<a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU">mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU</a>]
<b>On Behalf Of </b>Mueller, Milton L<br>
<b>Sent:</b> 15 January 2018 16:24<br>
<b>To:</b> <a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU">NCSG-DISCUSS@LISTSERV.SYR.EDU</a><br>
<b>Subject:</b> Re: Data Protection and Privacy Update: Seeking Community Feedback on Proposed Compliance Models<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" 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 lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" 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 lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" 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 lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Dr. Milton Mueller<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Professor, School of Public Policy<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Georgia Institute of Technology<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><a href="https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.internetgovernance.org%2F&data=02%7C01%7C%7C3dd1a12959b643f67bc008d55c34a8b6%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636516303589985847&sdata=XX34ciGttsvyAXPD99%2F%2FC1jwcDyKMTh6mYtFW%2BmnryA%3D&reserved=0"><span style="color:#1F497D;text-decoration:none"><img border="0" width="205" height="44" style="width:2.1354in;height:.4583in" id="Picture_x0020_1" src="cid:image001.jpg@01D391BF.46161630" alt="IGP_logo_gold block_email sig"></span></a></span><span lang="EN-US" style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="color:windowtext">From:</span></b><span lang="EN-US" style="color:windowtext"> NCSG-Discuss [<a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU">mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU</a>]
<b>On Behalf Of </b>Paul Rosenzweig<br>
<b>Sent:</b> Monday, January 15, 2018 9:35 AM<br>
<b>To:</b> <a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU">NCSG-DISCUSS@LISTSERV.SYR.EDU</a><br>
<b>Subject:</b> Re: Data Protection and Privacy Update: Seeking Community Feedback on Proposed Compliance Models<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:windowtext">I tend to agree with Sam on this … the GDPR is a good standard, but it is not a universal standard. And just as we don’t want ICANN to be in the business of content regulation we don’t want it
to be the standard setter for world wide privacy. Our goal should be to identify the minimum contractually necessary and then allow divergence across the globe. The more difficult question is what, precisely, that minimum is …
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:windowtext">P<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:windowtext"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US" style="color:windowtext">Paul Rosenzweig<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:windowtext"><a href="mailto:paul.rosenzweig@redbranchconsulting.com"><span style="color:#0563C1">paul.rosenzweig@redbranchconsulting.com</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:windowtext">O: +1 (202) 547-0660<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:windowtext">M: +1 (202) 329-9650<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:windowtext">VOIP: +1 (202) 738-1739<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:windowtext"><a href="https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.redbranchconsulting.com%2F&data=02%7C01%7C%7C3dd1a12959b643f67bc008d55c34a8b6%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636516303589985847&sdata=JmGak3hCCgog8E4O2e4aI7SQO%2FvbTITL19dKUYfcrjg%3D&reserved=0"><span style="color:#0563C1">www.redbranchconsulting.com</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:windowtext">My PGP Key: <a href="https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkeys.mailvelope.com%2Fpks%2Flookup%3Fop%3Dget%26search%3D0x9A830097CA066684&data=02%7C01%7C%7C3dd1a12959b643f67bc008d55c34a8b6%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636516303589985847&sdata=wWQcZO1MhOrDHAlX7uGqja0xhyYqjGzt00yxcVcXIRk%3D&reserved=0">
<span style="color:#0563C1">https://keys.mailvelope.com/pks/lookup?op=get&search=0x9A830097CA066684</span></a><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US" style="color:windowtext"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="color:windowtext">From:</span></b><span lang="EN-US" style="color:windowtext"> NCSG-Discuss [<a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU">mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU</a>]
<b>On Behalf Of </b>Sam Lanfranco<br>
<b>Sent:</b> Sunday, January 14, 2018 10:59 AM<br>
<b>To:</b> <a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU">NCSG-DISCUSS@LISTSERV.SYR.EDU</a><br>
<b>Subject:</b> Re: Data Protection and Privacy Update: Seeking Community Feedback on Proposed Compliance Models<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p><span lang="EN-US">Colleagues,<o:p></o:p></span></p>
<p><span lang="EN-US">I may have an overly simplistic view of the issue here, but I would like to put it on the table. ICANN has a narrow remit within the growing area of global, regional (e.g. EU), and national Internet governance. It exercises that remit
through a serious of contracts with entities (registrars and registries) that operate under diverse national Internet governance jurisdictions.
<o:p></o:p></span></p>
<p><span lang="EN-US">With differing specific data protection language in diverse contexts, it is highly unlikely that ICANN can draft “higher standard” contract language that will satisfy the data privacy regulations of all, most, or even many, national data
privacy regimes. So, what is the path forward here?<o:p></o:p></span></p>
<p><span lang="EN-US">There seem to be two components of a path forward. First, ICANN must figure out how it exercises ICANN agency as a stakeholder in the various legislative policy venues in which data privacy and other Internet governance policy is debated
and where regulations are formed. Some ICANN stakeholders already “have skin in those games” and are already present in those policy debates. ICANN writes contract language and needs to be engaged as a stakeholder.
<o:p></o:p></span></p>
<p><span lang="EN-US">Second, in contrast to seeking “higher standard” contract language, ICANN may need to look for “minimum conditions” contract language that offers contracted parties maximum freedom to negotiate with and meet the conditions of national
Internet governance policies. At the same time ICANN can use its agency as a stakeholder to press for “higher standard” national policies that harmonize regulations, and facilitate the work and interests of various stakeholders in the Internet ecosystem.
<o:p></o:p></span></p>
<p><span lang="EN-US">In short, the path forward may be (a) more ICANN agency as a stakeholder, and (b) minimal contract language to maximize the ability of contracted parties to deal with national policies and regulations.
<o:p></o:p></span></p>
<p style="margin-bottom:12.0pt"><span lang="EN-US">Sam L. <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">On 1/14/2018 10:02 AM, Ayden Férdeline wrote:<o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span lang="EN-US">Hi Caleb,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">While I appreciate that not all countries have data protection laws, privacy remains a fundamental human right. My suggestion is thus that we should adopt the highest level of protection for all domain name registrants.
And I suspect it is a lot easier to implement one model, rather than fragmented models for different jurisdictions.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Please also remember that ICANN sets policy by contract; i.e. registries, registrars, and registrants agree by contract to follow the rules and policies created by ICANN, and these policies can be revised and deleted.
So while ICANN must of course comply with the law, it can adopt and impose a higher standard on the contracted parties.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Many thanks,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Ayden<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span lang="EN-US">-------- Original Message --------<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Subject: Re: Data Protection and Privacy Update: Seeking Community Feedback on Proposed Compliance Models<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Local Time: 14 January 2018 3:56 PM<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">UTC Time: 14 January 2018 14:56<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">From: <a href="mailto:muyiwacaleb@GMAIL.COM">
muyiwacaleb@GMAIL.COM</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">To: <a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU">
NCSG-DISCUSS@LISTSERV.SYR.EDU</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">Hello Badii and Ayden,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">For me, i think the Model 2A serves the purposes. Don't forget that not all countries have data protection laws or policy in place.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Hence, based on jurisdiction, they cannot be governed by laws that is peculiar to a certain continent or sovereign state. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Caleb Ogundele<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">On Sun, Jan 14, 2018 at 3:36 PM, Ayden Férdeline <<a href="mailto:icann@ferdeline.com">icann@ferdeline.com</a>> wrote:<o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span lang="EN-US">I could live with the second model.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">The key differentiation between Model 2A and 2B is its applicability: 2A applies only "where the registrant, registry, registrar or a processor are located in the European Economic Area"; 2B "applies to all registrations
on a global basis without regard to location of registry, registrar registrant, and processing activities"<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">On this basis I think Model 2B is the best path forward. To have fragmented approaches for different regions would be a mistake, in my opinion.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Given the short turnaround time here (we need to agree on a position and submit a comment by 29 January) and other obstacles between now and then (Intersessional, GNSO Council Strategic Planning Session), may I suggest
that we schedule a call next week to discuss our response?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Best wishes, Ayden<o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span lang="EN-US">-------- Original Message --------<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Subject: Data Protection and Privacy Update: Seeking Community Feedback on Proposed Compliance Models<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Local Time: 13 January 2018 7:40 PM<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">UTC Time: 13 January 2018 18:40<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">From: <a href="mailto:farzaneh.badii@GMAIL.COM">
farzaneh.badii@GMAIL.COM</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">To: <a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU">
NCSG-DISCUSS@LISTSERV.SYR.EDU</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Verdana",sans-serif">Please see the CEO blog on Data protection and privacy:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Verdana",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span class="font"><span lang="EN-US" style="font-family:"Verdana",sans-serif"><a href="https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.icann.org%2Fnews%2Fblog%2Fdata-protection-and-privacy-update-seeking-community-feedback-on-proposed-compliance-models&data=02%7C01%7C%7C3dd1a12959b643f67bc008d55c34a8b6%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636516303589985847&sdata=7h8a35c%2B3XtTan6p9CktIk29I609aKLp5e1%2B8OGNlCk%3D&reserved=0">https://www.icann.org/news/blog/data-protection-and-privacy-update-seeking-community-feedback-on-proposed-compliance-models</a></span></span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">We should understand these models, discuss them and provide feedback. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Best<o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span class="font"><span lang="EN-US" style="font-family:"Verdana",sans-serif">Farzaneh</span></span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</div>
</div>
</blockquote>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">-- <o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span class="colour"><b><span lang="EN-US" style="font-size:13.5pt;color:#33CCFF">Ogundele Olumuyiwa Caleb</span></b></span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span class="colour"><b><i><span lang="EN-US" style="color:#993300"><a href="mailto:muyiwacaleb@gmail.com">muyiwacaleb@gmail.com</a></span></i></b></span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span class="colour"><b><i><span lang="EN-US" style="color:#666666">234 - 8077377378</span></i></b></span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span class="colour"><b><i><span lang="EN-US" style="color:#666666">234 - 07030777969</span></i></b></span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</blockquote>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<pre><span lang="EN-US">-- <o:p></o:p></span></pre>
<pre><span lang="EN-US">------------------------------------------------<o:p></o:p></span></pre>
<pre><span lang="EN-US">"It is a disgrace to be rich and honoured<o:p></o:p></span></pre>
<pre><span lang="EN-US">in an unjust state" -Confucius<o:p></o:p></span></pre>
<pre><span lang="EN-US"> </span><span lang="ZH-CN" style="font-family:"MS Gothic"">邦有道，</span><span lang="ZH-CN" style="font-family:"Microsoft JhengHei",sans-serif">贫且贱焉，耻也。邦无道，富且贵焉，耻也</span><span lang="EN-US"><o:p></o:p></span></pre>
<pre><span lang="EN-US">------------------------------------------------<o:p></o:p></span></pre>
<pre><span lang="EN-US">Dr Sam Lanfranco (Prof Emeritus & Senior Scholar)<o:p></o:p></span></pre>
<pre><span lang="EN-US">Econ, York U., Toronto, Ontario, CANADA - M3J 1P3<o:p></o:p></span></pre>
<pre><span lang="EN-US">email: <a href="mailto:Lanfran@Yorku.ca">Lanfran@Yorku.ca</a> Skype: slanfranco<o:p></o:p></span></pre>
<pre><span lang="EN-US">blog: <a href="https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsamlanfranco.blogspot.com&data=02%7C01%7C%7C3dd1a12959b643f67bc008d55c34a8b6%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636516303590142118&sdata=7qh0w0BkhwzoXXxrV3pFEGtGVsfYKzmIoU0UEMyyFKc%3D&reserved=0">https://samlanfranco.blogspot.com</a><o:p></o:p></span></pre>
<pre><span lang="EN-US">Phone: +1 613-476-0429 cell: +1 416-816-2852<o:p></o:p></span></pre>
</div>
</div>
</div>
</div>
</div>
</body>
</html>