<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">+1 <div><br></div><div>That makes sense <br><br><div id="AppleMailSignature">Kris</div><div><br>On 26 Oct 2017, at 13:12, Paul Keating <<a href="mailto:Paul@law.es">Paul@law.es</a>> wrote:<br><br></div><blockquote type="cite"><div><div>I agree Michael,</div><div><br></div><div>However, I am not sure how this moves the ball anywhere since I believe that liability attaches to the processor as well. A case in point is the actual display of WHOIS data to the public – whether or not it is WHOIS pertaining to a registrant/customer.</div><div><br></div><div>From my point of view I consider WHOIS to be a necessary data set for any number of reasons. My goal is to find a methodology that allows WHOIS data to be collected and made available with appropriate protections for privacy concerns. By appropriate I mean a system that balances the privacy concerns against the needs of the general public.</div><div><br></div><div>Paul</div><div><br></div><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> <<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org">gnso-rds-pdp-wg-bounces@icann.org</a>> on behalf of theo geurts <<a href="mailto:gtheo@xs4all.nl">gtheo@xs4all.nl</a>><br><span style="font-weight:bold">Date: </span> Thursday, October 26, 2017 at 8:29 AM<br><span style="font-weight:bold">To: </span> <<a href="mailto:michael@palage.com">michael@palage.com</a>>, 'RDS PDP WG' <<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>><br><span style="font-weight:bold">Subject: </span> Re: [gnso-rds-pdp-wg] Joint Controller / Article 26 / Hamilton Memo<br></div><div><br></div><blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"><div>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div text="#000000" bgcolor="#FFFFFF">
You are right Michael. <br>
<br>
Though there is a chance that this is covered more in-depth in part
2?<br>
<br>
Theo <br>
<br>
<div class="moz-cite-prefix">On 25-10-2017 23:55, <a class="moz-txt-link-abbreviated" href="mailto:michael@palage.com">michael@palage.com</a>
wrote:<br>
</div>
<blockquote type="cite" cite="mid:0ef601d34ddb$f29f5060$d7ddf120$@palage.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
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-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.m-59333515633959626m7775193058745579155m7299029587959283055msoplaintext, li.m-59333515633959626m7775193058745579155m7299029587959283055msoplaintext, div.m-59333515633959626m7775193058745579155m7299029587959283055msoplaintext
{mso-style-name:m_-59333515633959626m_7775193058745579155m_7299029587959283055msoplaintext;
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;}
span.m-59333515633959626apple-converted-space
{mso-style-name:m_-59333515633959626apple-converted-space;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
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:windowtext;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle27
{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]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="color:windowtext">Hello All, <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">I must admit
it has been hard to keep up with the flood of recent list
traffic. However, I would like to interject a legal issue
raised in the Hamilton Memo which I do not believe has been
properly discussed to date. Specifically, Hamilton’s
determination that both ICANN and Registration Authorities
(Registries and Registrars) are Joint Controllers, see
Paragraph 3.4.4 of Hamilton Memo. <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">Article 26
of the GDPR on the issue of Joint Controller states that “</span>Where
two or more controllers jointly determine the purposes and
means of processing, they shall be joint controllers.” For
the purpose of this analysis I will focus exclusively on
Registries as well as the fact that there seems to have been a
lot of list traffic in connection with the recent actions of
.AMSTERDAM and .FRL. Prior to ICANN, the legacy gTLDs were
thin registries. Over the years ICANN has mandated through
various RFPs/Applicant Guidebooks the requirement that a TLD
be operated in a thick format. But for a Consensus Policy
mandating VeriSign to convert .COM and .NET from thin to thick
there was no desire or need for Verisign to have access to
this data. How can parties be “joint” controllers, when one
party has the unilateral right to impose its will on the
other?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I am puzzled why Hamilton made this legal
determination and whether it knew of these historical data
points. I am also puzzled why Hamilton believes that ICANN as
a Joint Controller can unilaterally undertake a DPIA without
consultation with the other joint controllers. I would submit
that history and this action, point toward ICANN being the
sole Data Controller, and “most” registries being a Data
Processor. As evidenced by VeriSign, most gTLD registries do
not need thick data to perform their core business functions.
They are only deemed a Joint Controller because ICANN has
mandated that they collect and process the PII of registrants.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I would welcome any additional insight on
this Article 26 issue.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Michael<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<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>
</div></div>
_______________________________________________
gnso-rds-pdp-wg mailing list
<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></blockquote></span>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>gnso-rds-pdp-wg mailing list</span><br><span><a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a></span><br><span><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></span></div></blockquote></div></body></html>