<div dir="ltr"><div>Careful guys! <br></div><div><br></div><div>The sentence <br></div><div><br></div><div>"The Court reasoned that because it is possible for a registrant
to provide the same data elements for the registrant as for the
administrative and technical contacts, ICANN did not demonstrate
that it is necessary to collect additional data elements for those
contacts. The Court also noted that a registrant could consent and
provide administrative and technical contact data at its
discretion.
" <br></div><div><br></div><div>**does not** implies the right to publish those data on a public registry like WhoIs. That would be a big mistake worth EUR 20M in fines.</div><div><br></div><div>Regards,</div><div>Pino</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 31 May 2018 at 14:37, Kathy Kleiman <span dir="ltr"><<a href="mailto:kathy@kathykleiman.com" target="_blank">kathy@kathykleiman.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>Hi All, <br>
</p>
<p>Good news! Yesterday, the German Court ruled for EPAG, the
Germany-based, ICANN-accredited registrar owned by Tucows. The
following is posted on ICANN's website today:</p>
<p>"ICANN asked the Court to intervene after learning that EPAG no
longer intended to collect such data, citing the GDPR law
implementation as its rationale. ICANN had long required full
WHOIS data to be collected, and was requiring registrars such as
EPAG to continue to collect the data after the GDPR went into full
effect. ICANN modified its requirements surrounding how others
could access this data, limiting access only to those who could
demonstrate a legitimate purpose (such as in cases of criminal
activity, intellectual property infringement or Internet Security
problems). Assessing and identifying a legitimate purpose is a
requirement identified in the GDPR.<br>
<br>
"In rejecting the injunctive relief, the Court ruled that it would
not require EPAG to collect the adminsitrative and technical data
for new registrations. However, the Court did not indicate in its
ruling that collecting such data would be a violation of the GDPR.
Rather, the Court said that the collection of the domain name
registrant data should suffice in order to safeguard against
misuse the security aspects in connection with the domain name
(such as criminal activity, infringement or security problems).<br>
<br>
"The Court reasoned that because it is possible for a registrant
to provide the same data elements for the registrant as for the
administrative and technical contacts, ICANN did not demonstrate
that it is necessary to collect additional data elements for those
contacts. The Court also noted that a registrant could consent and
provide administrative and technical contact data at its
discretion."</p>
<p><a class="m_-7735897548895546903moz-txt-link-freetext" href="https://www.icann.org/news/announcement-4-2018-05-30-en" target="_blank">https://www.icann.org/news/<wbr>announcement-4-2018-05-30-en</a></p>
<p>Best, Kathy<br>
</p><div><div class="h5">
<br>
<div class="m_-7735897548895546903moz-cite-prefix">On 5/31/2018 4:55 AM, Ayden Férdeline
wrote:<br>
</div>
<blockquote type="cite">
<div>I suspect - and this is me being generous in my speculation -
that ICANN knows their legal strategy is misguided and
incorrect, but they are facing political pressure on the
domestic front. The NTIA Administrator David Redl has called
ICANN out a few times in speeches for not preserving the WHOIS
status quo, so I suspect lawsuits like this one are done partly
to placate the US government. However I do think arrogance,
incompetence, and a lack of awareness of what exactly the
European Union is and what its regulations are is also playing a
part in the actions being advanced by ICANN org.<br>
</div>
<div><br>
</div>
<div class="m_-7735897548895546903protonmail_signature_block">
<div class="m_-7735897548895546903protonmail_signature_block-user">
<div>Ayden <br>
</div>
</div>
<div class="m_-7735897548895546903protonmail_signature_block-proton m_-7735897548895546903protonmail_signature_block-empty"><br>
</div>
</div>
<div><br>
</div>
<div>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br>
</div>
<div> On 31 May 2018 10:45 AM, Giuseppe De Francesco
<a class="m_-7735897548895546903moz-txt-link-rfc2396E" href="mailto:defrancescog@GMAIL.COM" target="_blank"><defrancescog@GMAIL.COM></a> wrote:<br>
</div>
<div> <br>
</div>
<blockquote class="m_-7735897548895546903protonmail_quote" type="cite">
<div dir="ltr">
<div>Dear all,<br>
</div>
<div><br>
</div>
<div>I've been a silent reader until now because GDPR
jurisprudence is still building up, and my daily GDPR
compliance work doesn't qualify me to argue with a bunch of
lawyers, but this is getting off track, and I feel that it
is time to chime in. There is enough knowledge about Data
Protection (DP) expressed via Article 29 Working Party
(A29WP) over the years to clear issues like this without
even having to talk about it.<br>
</div>
<div><br>
</div>
<div>The only problem I see here is about culture. USA vs EU
cultural gap. To any EU person, Whois has always been
borderline illegal, but we didn't have any law like the GDPR
yet. Therefore, we had to keep it to ourselves. Meanwhile,
Americans made a lot of money by monetising the Right to
Privacy offering Whois protection as a domain add-on. It's
just as shameful as monetising public water.<br>
</div>
<div><br>
</div>
<div>Now we have the GDPR coming into force after two years
grace period (I define those "2 years of denial"), and
everybody tries to find a loophole in the GDPR to get away
with DP violations. Well, let me break this to you guys:
there aren't any loopholes, just accept this fact and move
on. Google Spain ruling (<a href="http://bit.ly/GoogleSpainRuling" target="_blank">http://bit.ly/<wbr>GoogleSpainRuling</a>)
should have clarified that in the EU we have a different
approach to DP. If Google got kicked before the GDPR, do you
think that now is the time to look for loopholes? Please...
<br>
</div>
<div><br>
</div>
<div>Best regards,<br>
</div>
<div>Pino<br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
<div class="gmail_extra">
<div><br>
</div>
<div class="gmail_quote">
<div>On 31 May 2018 at 08:23, valentina hvale pellizzer <span dir="ltr"><<a href="mailto:valentina@oneworldplatform.net" target="_blank">valentina@oneworldplatform.<wbr>net</a>></span>
wrote:<br>
</div>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" class="gmail_quote">
<div bgcolor="#FFFFFF">
<p>Well <br>
</p>
<p>I know will sound foolish but why would be staff
accountability off the table? than what is the sense
of all these committee, consultations, working groups,
big transitions, big policies. <br>
</p>
<p>Find it very depressing and exploitive<br>
</p>
<p>hvale<br>
</p>
<div><br>
</div>
<div class="m_-7735897548895546903m_2390314032224398252moz-cite-prefix">On
05/31/2018 09:13 AM, Ayden Férdeline wrote:<br>
</div>
<blockquote type="cite">
<div>It was a very strange legal strategy that ICANN
employed. Now that it has failed, I wonder what
action ICANN org will take next -- I presume staff
accountability for mishandling the issue, and
putting forward such questionable advice, is off the
table, but what's plan D? What will finally give
ICANN org the "clarity" it so desperately craves? <br>
</div>
<div><br>
</div>
<div><span class="m_-7735897548895546903highlight" style="background-color:rgb(255,255,255)"><span class="m_-7735897548895546903colour" style="color:rgb(51,51,51)"><span class="m_-7735897548895546903font" style="font-family:helvetica,arial,sans-serif"><span class="m_-7735897548895546903size" style="font-size:16px">"While<span> </span></span></span></span></span><abbr title="Internet Corporation for Assigned Names and
Numbers" style="box-sizing:border-box;font-weight:300;unicode-bidi:bidi-override;direction:ltr;border-bottom:1px dotted rgb(153,153,153);text-decoration:none;color:rgb(51,51,51);font-family:helvetica,arial,sans-serif;font-size:16px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">ICANN</abbr><span class="m_-7735897548895546903highlight" style="background-color:rgb(255,255,255)"><span class="m_-7735897548895546903colour" style="color:rgb(51,51,51)"><span class="m_-7735897548895546903font" style="font-family:helvetica,arial,sans-serif"><span class="m_-7735897548895546903size" style="font-size:16px"><span> </span>appreciates
the prompt attention the Court paid to this
matter, the Court's ruling today did not
provide the clarity that<span> </span></span></span></span></span><abbr title="Internet Corporation for Assigned Names and
Numbers" style="box-sizing:border-box;font-weight:300;unicode-bidi:bidi-override;direction:ltr;border-bottom:1px dotted rgb(153,153,153);text-decoration:none;color:rgb(51,51,51);font-family:helvetica,arial,sans-serif;font-size:16px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">ICANN</abbr><span class="m_-7735897548895546903highlight" style="background-color:rgb(255,255,255)"><span class="m_-7735897548895546903colour" style="color:rgb(51,51,51)"><span class="m_-7735897548895546903font" style="font-family:helvetica,arial,sans-serif"><span class="m_-7735897548895546903size" style="font-size:16px"><span> </span>was
seeking when it initiated the injunction
proceedings," said John Jeffrey,<span> </span></span></span></span></span><abbr title="Internet Corporation for Assigned Names and
Numbers" style="box-sizing:border-box;font-weight:300;unicode-bidi:bidi-override;direction:ltr;border-bottom:1px dotted rgb(153,153,153);text-decoration:none;color:rgb(51,51,51);font-family:helvetica,arial,sans-serif;font-size:16px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">ICANN</abbr><span class="m_-7735897548895546903highlight" style="background-color:rgb(255,255,255)"><span class="m_-7735897548895546903colour" style="color:rgb(51,51,51)"><span class="m_-7735897548895546903font" style="font-family:helvetica,arial,sans-serif"><span class="m_-7735897548895546903size" style="font-size:16px">'s General Counsel
and Secretary.</span></span></span></span><br>
</div>
<div><br>
</div>
<div class="m_-7735897548895546903m_2390314032224398252protonmail_signature_block">
<div class="m_-7735897548895546903m_2390314032224398252protonmail_signature_block-user">
<div>—Ayden <br>
</div>
</div>
<div class="m_-7735897548895546903m_2390314032224398252protonmail_signature_block-proton
m_2390314032224398252protonmail_signature_block-empty"><br>
</div>
</div>
<div><br>
</div>
<div>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br>
</div>
<div>On 31 May 2018 6:14 AM, Rafik Dammak <a href="mailto:rafik.dammak@GMAIL.COM" class="m_-7735897548895546903m_2390314032224398252moz-txt-link-rfc2396E" target="_blank"><rafik.dammak@GMAIL.COM></a>
wrote:<br>
</div>
<div><br>
</div>
<blockquote type="cite" class="m_-7735897548895546903m_2390314032224398252protonmail_quote">
<div dir="ltr">
<div>Hi all,<br>
</div>
<div>you can find here the update on litigation
initiated by ICANN <a href="https://www.icann.org/news/announcement-4-2018-05-30-en" target="_blank">https://www.icann.org/ne<wbr>ws/announcement-4-2018-05-30-<wbr>en</a>.
the court rejected injunction requested by
ICANN.<br>
</div>
<div><br>
</div>
<div>Best Regards,<br>
</div>
<div><br>
</div>
<div>Rafik<br>
</div>
</div>
</blockquote>
<div><span class="m_-7735897548895546903HOEnZb"><span class="m_-7735897548895546903colour" style="color:#888888"></span></span><br>
</div>
<div><span class="m_-7735897548895546903HOEnZb"><span class="m_-7735897548895546903colour" style="color:#888888"></span></span><br>
</div>
</blockquote>
<span class="m_-7735897548895546903HOEnZb"><span class="m_-7735897548895546903colour" style="color:#888888">
<div><br>
</div>
<pre cols="72" class="m_-7735897548895546903m_2390314032224398252moz-signature">--
valentina pellizzer
President
One World Platform
<a href="https://oneworldplatform.net/" class="m_-7735897548895546903m_2390314032224398252moz-txt-link-freetext" target="_blank">https://oneworldplatform.net/</a>
mobile: +387 (0)61 484 038
twitter: @froatosebe
Fingerprint 30AA 9445 D878 A6C9 FE41 E90D 52A5 36A6 B249 EDA9
</pre>
</span></span></div>
</blockquote>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>-- <br>
</div>
<div data-smartmail="gmail_signature" class="m_-7735897548895546903gmail_signature">
<table cellspacing="0" cellpadding="0" border="0">
<tbody>
<tr>
<td style="line-height:0;vertical-align:bottom;padding-right:10px;padding-top:20px;padding-bottom:20px" width="107" valign="bottom" align="left"><a style="text-decoration:none" href="https://about.me/pinodefrancesco?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=gmail_api&utm_content=thumb" target="_blank"><img style="margin:0;padding:0;display:block;border:1px solid #eeeeee" alt="" src="https://thumbs.about.me/thumbnail/users/p/i/n/pinodefrancesco_emailsig.jpg?_1511955753_888" class="m_-7735897548895546903proton-embedded" width="105" height="70"> </a><br>
</td>
<td style="line-height:1.1;vertical-align:bottom;padding-top:20px;padding-bottom:20px" valign="bottom" align="left">
<div><img style="border:0;margin:0;padding:0;width:1;height:1;overflow:hidden" src="https://about.me/t/sig?u=pinodefrancesco" class="m_-7735897548895546903proton-embedded" width="1" height="1"> <br>
</div>
<div>Giuseppe
(Pino) De Francesco<br>
</div>
<div><a href="https://about.me/pinodefrancesco?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=gmail_api&utm_content=thumb" target="_blank">about.me/pinodefrancesco</a><br>
</div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</blockquote>
<div><br>
</div>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><table cellspacing="0" cellpadding="0" border="0">
<tbody>
<tr>
<td style="line-height:0;vertical-align:bottom;padding-right:10px;padding-top:20px;padding-bottom:20px" width="107" valign="bottom" align="left">
<a href="https://about.me/pinodefrancesco?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=gmail_api&utm_content=thumb" style="text-decoration:none" target="_blank">
<img src="https://thumbs.about.me/thumbnail/users/p/i/n/pinodefrancesco_emailsig.jpg?_1511955753_888" alt="" style="margin:0;padding:0;display:block;border:1px solid #eeeeee" width="105" height="70">
</a>
</td>
<td style="line-height:1.1;vertical-align:bottom;padding-top:20px;padding-bottom:20px" valign="bottom" align="left">
<img src="https://about.me/t/sig?u=pinodefrancesco" style="border:0;margin:0;padding:0;width:1;height:1;overflow:hidden" width="1" height="1">
<div style="font-size:18px;font-weight:bold;color:#333333;font-family:'Proxima Nova',Helvetica,Arial,sans-serif!important">Giuseppe (Pino) De Francesco</div>
<a href="https://about.me/pinodefrancesco?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=gmail_api&utm_content=thumb" style="text-decoration:none;font-size:12px;color:#2b82ad;font-family:'Proxima Nova',Helvetica,Arial,sans-serif!important" target="_blank">about.me/pinodefrancesco
</a>
</td>
</tr>
</tbody>
</table>
</div>
</div>