<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Well said.</p>
<p>Stephanie Perrin<br>
</p>
<br>
<div class="moz-cite-prefix">On 2018-05-31 4:45 AM, Giuseppe De
Francesco wrote:<br>
</div>
<blockquote
cite="mid:CAE=boEFh2POxPzri57Gk1TP0OD2ZRnUgsr7NpMW5PWGrAKHvvA@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div dir="ltr">
<div>Dear all,</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.</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.</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 moz-do-not-send="true"
href="http://bit.ly/GoogleSpainRuling">http://bit.ly/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,</div>
<div>Pino<br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 31 May 2018 at 08:23, valentina
hvale pellizzer <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:valentina@oneworldplatform.net"
target="_blank">valentina@oneworldplatform.net</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>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</p>
<p>hvale<br>
</p>
<br>
<div class="m_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_2390314032224398252highlight"
style="background-color:rgb(255,255,255)"><span
class="m_2390314032224398252colour"
style="color:rgb(51,51,51)"><span
class="m_2390314032224398252font"
style="font-family:helvetica,arial,sans-serif"><span
class="m_2390314032224398252size"
style="font-size:16px">"While<span> </span></span></span></span></span><abbr
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)"
title="Internet Corporation for Assigned Names and
Numbers">ICANN</abbr><span
class="m_2390314032224398252highlight"
style="background-color:rgb(255,255,255)"><span
class="m_2390314032224398252colour"
style="color:rgb(51,51,51)"><span
class="m_2390314032224398252font"
style="font-family:helvetica,arial,sans-serif"><span
class="m_2390314032224398252size"
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
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)"
title="Internet Corporation for Assigned Names and
Numbers">ICANN</abbr><span
class="m_2390314032224398252highlight"
style="background-color:rgb(255,255,255)"><span
class="m_2390314032224398252colour"
style="color:rgb(51,51,51)"><span
class="m_2390314032224398252font"
style="font-family:helvetica,arial,sans-serif"><span
class="m_2390314032224398252size"
style="font-size:16px"><span> </span>was
seeking when it initiated the injunction
proceedings," said John Jeffrey,<span> </span></span></span></span></span><abbr
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)"
title="Internet Corporation for Assigned Names and
Numbers">ICANN</abbr><span
class="m_2390314032224398252highlight"
style="background-color:rgb(255,255,255)"><span
class="m_2390314032224398252colour"
style="color:rgb(51,51,51)"><span
class="m_2390314032224398252font"
style="font-family:helvetica,arial,sans-serif"><span
class="m_2390314032224398252size"
style="font-size:16px">'s General Counsel and
Secretary.</span></span></span></span><br>
</div>
<div><br>
</div>
<div
class="m_2390314032224398252protonmail_signature_block">
<div
class="m_2390314032224398252protonmail_signature_block-user">
<div>—Ayden <br>
</div>
</div>
<div
class="m_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
moz-do-not-send="true"
class="m_2390314032224398252moz-txt-link-rfc2396E"
href="mailto:rafik.dammak@GMAIL.COM" target="_blank"><rafik.dammak@GMAIL.COM></a>
wrote:<br>
</div>
<div> <br>
</div>
<blockquote
class="m_2390314032224398252protonmail_quote"
type="cite">
<div dir="ltr">
<div>Hi all,<br>
</div>
<div>you can find here the update on litigation
initiated by ICANN <a moz-do-not-send="true"
href="https://www.icann.org/news/announcement-4-2018-05-30-en"
target="_blank">https://www.icann.org/<wbr>news/announcement-4-2018-05-<wbr>30-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><br>
<span class="HOEnZb"><font color="#888888"> </font></span></div>
<span class="HOEnZb"><font color="#888888"> </font></span></blockquote>
<span class="HOEnZb"><font color="#888888"> <br>
<pre class="m_2390314032224398252moz-signature" cols="72">--
valentina pellizzer
President
One World Platform
<a moz-do-not-send="true" class="m_2390314032224398252moz-txt-link-freetext" href="https://oneworldplatform.net/" 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>
</font></span></div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature">
<table border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td
style="line-height:0;vertical-align:bottom;padding-right:10px;padding-top:20px;padding-bottom:20px"
align="left" valign="bottom" width="107"> <a
moz-do-not-send="true"
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
moz-do-not-send="true"
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" height="70" width="105"> </a> </td>
<td
style="line-height:1.1;vertical-align:bottom;padding-top:20px;padding-bottom:20px"
align="left" valign="bottom"> <img
moz-do-not-send="true"
src="https://about.me/t/sig?u=pinodefrancesco"
style="border:0;margin:0;padding:0;width:1;height:1;overflow:hidden"
height="1" width="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 moz-do-not-send="true"
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>
</blockquote>
<br>
</body>
</html>