<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=us-ascii"><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;}
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.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;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{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: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]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:14.0pt'>Hello All,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'>So I just finished listening to the IGF 2017 Session entitled ICANN – Looking ahead – Challenges and Opportunities. I would recommend this as a MUST listen session when the archive is made available. I was able to do a screen scrape and capture the transcript for those that are interested I could send to you directly. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'>What I found rather concerning is a statement from Goran that ICANN would be circulating three models with the community in January from which he would choose one that would be the basis for ICANN compliance. Here is that specific excerpt:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;color:black'>And in a very short period of time we come up with three different models. I always like three different models, that will be composed for the community so the community can comment on potential solutions to this problem. And after that, as Becky said, I have to make a decision. Because as the President and CEO of ICANN I have to make a decision how my organize will be compliant with the law.</span><span style='font-size:14.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'>I provided a remote intervention which asked the basis for how ICANN predetermined that only three models would be considered by the community. Listed below is the question and response from Goran:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;color:black'>>> How have we determined only three models will be considered by the community. >> We have asked the community for giving us models and we seem to -- and the reason I am saying three, it seems like the proposes we are getting in from the community actually rotates around three different solutions. So that's why. And we're going to publish them and we're going to ask community for input on that. So we constructed a system for having that input, but then we have to respond because it is very hard to motivate, to go to the DPAs and say we think we now comply with the laws, but we also have three alternatives to be in compliance with the law. I think that would be a problem, and I say that as a former regulator.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'>I personally found this answer from Goran unacceptable. So I asked a follow-up question toward the end of the session that does not appear to have been captured in the transcript. Specifically I asked if ICANN could share the three models they were considering now, instead of waiting until January and his response was non-responsive. Goran was again non responsive to this question.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'>So here is my proposal for an additional topic for tomorrow’s call. ICANN has largely been non-responsive (some in this group may characterize ICANN’s actions as being ignorant) to Data Privacy concerns for 18 years of its existence. While the GDPR has recently gotten its attention, it has provided de minimis leadership in actually solving the problem, although it does deserve credit for the WSGR and Hamilton Memos. However, I believe ICANN OWES us a high level summary of the three model types it is considering NOW (not in January). To be clear, I am NOT seeking access to the more specific models that ICANN will drop on us in January. I find it unacceptable that ICANN is putting contracting parties at risk under GDPR while its CEO decides which “one” model it will deem acceptable under ICANN compliance. When convenient, ICANN cloaks itself in the joint controller paradigm yet ignores the explicit wording of Article 26 which states “Where two or more controllers jointly determine the purposes and means of processing, they shall be joint controllers. They shall in a transparent manner determine their respective responsibilities for compliance with the obligations under this Regulation.” <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'>I will stop this email now before I further expand upon my disappointment in ICANN leadership regarding this subject as I need to finish a more in-depth analysis of the Hamilton #2 memo before tomorrow’s call. Perhaps Hamilton memo #3 will arrive before Christmas (on the eve of ICANN’s traditional extended holiday shutdown period) because I am sure us humble volunteers can re-arrange our holiday plans to read this before ICANN graciously shares with the community its three pre-determined (yet highly guarded) models that Goran will choose from.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'>Best regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'>Michael<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt'><o:p> </o:p></span></p></div></body></html>