<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font size="+1"><font face="Lucida Grande">I totally agree David,
and as someone who last worked in risk management, if I were
the CEO looking at this mess right now I would be asking hard
questions of the people who have advised the Board to just
ignore the data protection commissioners for the past 17 years.
First position paper on WHOIS being illegal was in 2000.
Makes a heck of an easy case to take to Court....</font></font></p>
<p><font size="+1"><font face="Lucida Grande">Stephanie Perrin</font></font><br>
</p>
<br>
<div class="moz-cite-prefix">On 2017-07-31 03:33, David Cake wrote:<br>
</div>
<blockquote type="cite"
cite="mid:4DE65D16-BB9B-4A18-A040-189090FA9494@davecake.net">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
I admit I find this development disappointing.
<div class="">While it is a sign (along with the GDPR task force
established at the last meeting) that ICANN has finally
understood the significance of its downplaying and avoidance of
the GDPR and other international data protection law over the
last few years, it is disappointing that:</div>
<div class=""> a) ICANN is still not taking the issue that
seriously, as it is in addition to existing Deputy General
Counsel duties, so represents a limited allocation of resources
to the issue; </div>
<div class="">b) is a missed opportunity to bring additional
experience and expertise into the organisation, expertise ICANN
desperately needs (and is currently relying on its volunteers to
provide);</div>
<div class="">c) is continuing to the have the issue managed by
the same team whose denial and obstinate avoidance of the issue
has led to the organisation now facing a crisis;</div>
<div class="">d) continues a pattern of having ICANN legal be put
in charge of areas where it is largely responsible for continued
organisation dysfunction, so effectively being given the
opportunity to manage criticism but not given any strong
inventive to admit to past mistakes. . </div>
<div class=""><br class="">
</div>
<div class="">David</div>
<div class=""><br class="">
<div class=""><br class="">
</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 29 Jul 2017, at 3:32 am, Ayden Férdeline
<<a href="mailto:icann@ferdeline.com" class=""
moz-do-not-send="true">icann@ferdeline.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">ICANN has now <a
href="https://www.icann.org/news/blog/introducing-icann-s-chief-data-protection-officer-cdpo"
title="appointed someone" rel="nofollow" class=""
moz-do-not-send="true">appointed someone</a> to the
role of "Chief Data Protection Officer". Daniel
Halloran, who in his bio is described as "one of
ICANN's longest-serving employees" and reports
directly to John Jeffrey, does not list his experience
in establishing privacy frameworks nor their
associated compliance structures in his bio. That
said, I wish him all the best in this new role and
look forward to seeing how ICANN's understanding of
data protection law evolves over the coming months now
that this position has been created...<br class="">
</div>
<div class=""><br class="">
</div>
<div class=" protonmail_signature_block">
<div class="protonmail_signature_block-user ">
<div class="">Best wishes, Ayden Férdeline <br
class="">
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</blockquote>
<br>
</body>
</html>