<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">To the point….but i guess since the CDPO has been appointed he would need to look and be able to advise on public view of data in the whois for example. I am sure we need the correct and validated details of anyone who registers to have them on Data base but some information coming from special request like authorities needs a different access. Based on who and what the subject of the issue comes to be.</div><div class=""><br class=""></div><div class="">You have valid points which everyone must come to a middle ground to succeed Privacy laws and certainly GDPR is going to affect many dealings with EU be it online or cloud.The challenges are gona need to happen not only within the groups but affects ICANN directly. </div><div class=""><br class=""></div><div class="">But looks like stephanie has provided some more background. The bigger question is that whatever happens we all need to tie down to GDPR else no business at all and no safe harbor. </div><div class=""><br class=""></div><div class="">My acid test here is to see what the new Chief brings in. He should be able to look at everything and have guidelines for all groups and for ICANN as well. </div><div class=""><br class=""></div><div class="">Kris</div><br class=""><div><blockquote type="cite" class=""><div class="">On Jul 31, 2017, at 4:24 PM, Ade Bo <<a href="mailto:adebodea@GMAIL.COM" class="">adebodea@GMAIL.COM</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hello everyone, <div class=""><br class=""></div><div class="">Has anyone thought how are these changes going to influence cybercrime? </div><div class="">How much harder is it going to be to find information necessary to prosecute someone?</div><div class="">We are thinking of protecting privacy but isn’t there nothing contradicting that ?</div><div class="">I believe these matter should be looked at from all the stakeholders perspective.</div><div class=""><br class=""></div><div class=""><div class="">
<div style="font-family: Helvetica; font-style: normal; font-variant-ligatures: normal; font-variant-position: normal; font-variant-caps: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">With kind regards<br class=""><br class="">Adela Bodea</div><div style="font-family: Helvetica; font-style: normal; font-variant-ligatures: normal; font-variant-position: normal; font-variant-caps: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""></div><div style="font-family: Helvetica; font-style: normal; font-variant-ligatures: normal; font-variant-position: normal; font-variant-caps: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">"The true sign of intelligence is not knowledge but imagination”</div><div style="font-family: Helvetica; font-style: normal; font-variant-ligatures: normal; font-variant-position: normal; font-variant-caps: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""> Albert Einstein </div>
</div>
<br class=""><div class=""><blockquote type="cite" class=""><div class="">On 31 Jul 2017, at 14:06, Michael Oghia <<a href="mailto:mike.oghia@gmail.com" class="">mike.oghia@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">I agree too Stephanie, excellent points David. <div class=""><br class=""></div><div class="">Would anyone support us as the NCSG requesting a formal response to David's points (and a formal explanation as to the motivation behind Mr. Halloran's appointment)?</div><div class=""><div class="gmail_extra"><br clear="all" class=""><div class=""><div class="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class=""><font face="arial, helvetica, sans-serif" size="2" class="">Best,</font></div><div class=""><font size="2" face="arial, helvetica, sans-serif" class="">-Michael<br class=""></font></div><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><br class=""></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div><div class="gmail_quote">On Mon, Jul 31, 2017 at 1:51 PM, Stephanie Perrin <span dir="ltr" class=""><<a href="mailto:stephanie.perrin@mail.utoronto.ca" target="_blank" class="">stephanie.perrin@mail.utoronto.ca</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" class=""><p class=""><font size="+1" class=""><font face="Lucida Grande" class="">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><span class="gmail-HOEnZb"><font color="#888888" class=""><p class=""><font size="+1" class=""><font face="Lucida Grande" class="">Stephanie Perrin</font></font><br class="">
</p></font></span><div class=""><div class="gmail-h5">
<br class="">
<div class="gmail-m_-4063821553450781781moz-cite-prefix">On 2017-07-31 03:33, David Cake wrote:<br class="">
</div>
<blockquote type="cite" class="">
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 class="">
<blockquote type="cite" class="">
<div class="">On 29 Jul 2017, at 3:32 am, Ayden Férdeline
<<a href="mailto:icann@ferdeline.com" target="_blank" class="">icann@ferdeline.com</a>>
wrote:</div>
<br class="gmail-m_-4063821553450781781Apple-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" target="_blank" class="">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="gmail-m_-4063821553450781781protonmail_signature_block">
<div class="gmail-m_-4063821553450781781protonmail_signature_block-user">
<div class="">Best wishes, Ayden Férdeline <br class="">
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</blockquote>
<br class="">
</div></div></div>
</blockquote></div><br class=""></div></div></div>
</div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Kris Seeburn</div><div class=""><a href="mailto:seeburn.k@gmail.com" class="">seeburn.k@gmail.com</a></div><div class=""><ul style="margin: 0px; padding: 0px 0px 8px; border: 0px; outline: 0px; font-family: Helvetica, Arial, sans-serif; vertical-align: baseline; list-style: none; line-height: 17px; display: table-cell; width: 504px; color: rgb(51, 51, 51);" class=""><li style="margin: 0px; padding: 8px 12px 2px 0px; border: 0px; outline: 0px; font-style: inherit; font-size: 11px; font-family: inherit; vertical-align: baseline; font-variant: inherit; line-height: 1.2em;" class=""><dl class="public-profile" style="margin: 0px; padding: 0px; border: 0px; outline: 0px; font-style: inherit; font-family: inherit; vertical-align: baseline; font-variant: inherit; line-height: inherit; word-wrap: break-word;"><dd style="margin: 0px; padding: 2px 9px 1px 0px; border: 0px; outline: 0px; font-style: inherit; font-family: inherit; vertical-align: top; font-variant: inherit; line-height: inherit; display: inline-block; zoom: 1;" class=""><a href="http://www.linkedin.com/in/kseeburn/" title="View public profile" name="webProfileURL" style="margin: 0px 10px 0px 0px; padding: 0px 0px 0px 19px; border: 0px; outline: 0px; font-style: inherit; font-family: inherit; vertical-align: middle; text-decoration: none; color: rgb(102, 102, 102); font-variant: inherit; line-height: inherit; display: inline-block; zoom: 1; background-image: url(http://s.c.lnkd.licdn.com/scds/common/u/images/apps/profile/sprite/sprite_profile_top_card_v8.png); background-position: 0px -249px; background-repeat: no-repeat no-repeat;" class="">www.linkedin.com/in/kseeburn/</a></dd></dl></li></ul></div><div class=""><br class=""></div></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br class=""></body></html>