<div dir="ltr">Indeed, Kris, I agree with you on this point. You have just awakened my attention by this observation. At the local level, this could enable us to solve the problems of registrars not accredited and who abound in the country at the risk of deliveries the personal data to any person pretending to be of the intelligence service.<br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><b>SCHOMBE BAUDOUIN<br></b></div><div><b>SECRETAIRE EXECUTIF FGI-IGF RDC<br></b></div><div dir="ltr"><div><b style="color:rgb(0,0,0);font-family:'bookman old style','new york',times,serif">COORDINATION NATIONALE CAFEC<br>ICANN/AFRALO Member<br></b></div><div><b style="color:rgb(0,0,0);font-family:'bookman old style','new york',times,serif">ISOC Member</b><font color="#000000" face="bookman old style, new york, times, serif"><b><br></b></font>Téléphone mobile:+243998983491/+243813684512<br>email : <a href="mailto:b.schombe@gmail.com" target="_blank">b.schombe@gmail.com</a><br>skype : b.schombe<br>blog : <a href="http://akimambo.unblog.fr" target="_blank">http://akimambo.unblog.fr</a><br> <br> <br><br></div></div></div></div></div></div>
<br><div class="gmail_quote">2017-07-31 13:42 GMT+01:00 Kris Seeburn <span dir="ltr"><<a href="mailto:seeburn.k@gmail.com" target="_blank">seeburn.k@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>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><br></div><div>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><br></div><div>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><br></div><div>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><br></div><div>Kris</div><div><div class="h5"><br><div><blockquote type="cite"><div>On Jul 31, 2017, at 4:24 PM, Ade Bo <<a href="mailto:adebodea@GMAIL.COM" target="_blank">adebodea@GMAIL.COM</a>> wrote:</div><br class="m_-8135433649905264689Apple-interchange-newline"><div><div style="word-wrap:break-word">Hello everyone, <div><br></div><div>Has anyone thought how are these changes going to influence cybercrime? </div><div>How much harder is it going to be to find information necessary to prosecute someone?</div><div>We are thinking of protecting privacy but isn’t there nothing contradicting that ?</div><div>I believe these matter should be looked at from all the stakeholders perspective.</div><div><br></div><div><div>
<div style="font-family:Helvetica;font-style:normal;font-variant-ligatures: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;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">With kind regards<br><br>Adela Bodea</div><div style="font-family:Helvetica;font-style:normal;font-variant-ligatures: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;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><br></div><div style="font-family:Helvetica;font-style:normal;font-variant-ligatures: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;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">"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-caps:normal;font-variant-numeric:normal;font-variant-alternates:normal;font-variant-east-asian:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"> Albert Einstein </div>
</div>
<br><div><blockquote type="cite"><div>On 31 Jul 2017, at 14:06, Michael Oghia <<a href="mailto:mike.oghia@gmail.com" target="_blank">mike.oghia@gmail.com</a>> wrote:</div><br class="m_-8135433649905264689Apple-interchange-newline"><div><div dir="ltr">I agree too Stephanie, excellent points David. <div><br></div><div>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><div class="gmail_extra"><br clear="all"><div><div class="m_-8135433649905264689gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><font face="arial, helvetica, sans-serif" size="2">Best,</font></div><div><font size="2" face="arial, helvetica, sans-serif">-Michael<br></font></div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><br></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"><<a href="mailto:stephanie.perrin@mail.utoronto.ca" target="_blank">stephanie.perrin@mail.<wbr>utoronto.ca</a>></span> wrote:<br><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"><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><span class="m_-8135433649905264689gmail-HOEnZb"><font color="#888888"><p><font size="+1"><font face="Lucida Grande">Stephanie Perrin</font></font><br>
</p></font></span><div><div class="m_-8135433649905264689gmail-h5">
<br>
<div class="m_-8135433649905264689gmail-m_-4063821553450781781moz-cite-prefix">On 2017-07-31 03:33, David Cake wrote:<br>
</div>
<blockquote type="cite">
I admit I find this development disappointing.
<div>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> 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>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>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>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><br>
</div>
<div>David</div>
<div><br>
<div><br>
</div>
<div><br>
<div>
<blockquote type="cite">
<div>On 29 Jul 2017, at 3:32 am, Ayden Férdeline
<<a href="mailto:icann@ferdeline.com" target="_blank">icann@ferdeline.com</a>>
wrote:</div>
<br class="m_-8135433649905264689gmail-m_-4063821553450781781Apple-interchange-newline">
<div>
<div>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">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>
</div>
<div><br>
</div>
<div class="m_-8135433649905264689gmail-m_-4063821553450781781protonmail_signature_block">
<div class="m_-8135433649905264689gmail-m_-4063821553450781781protonmail_signature_block-user">
<div>Best wishes, Ayden Férdeline <br>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div></div></div>
</div></blockquote></div><br></div></div></div></blockquote></div><br></div></div><span class="HOEnZb"><font color="#888888"><div>
<div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div>Kris Seeburn</div><div><a href="mailto:seeburn.k@gmail.com" target="_blank">seeburn.k@gmail.com</a></div><div><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)"><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"><dl class="m_-8135433649905264689public-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"><a href="http://www.linkedin.com/in/kseeburn/" title="View public profile" name="m_-8135433649905264689_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" target="_blank">www.linkedin.com/in/kseeburn/</a></dd></dl></li></ul></div><div><br></div></div><br class="m_-8135433649905264689Apple-interchange-newline"><br class="m_-8135433649905264689Apple-interchange-newline">
</div>
<br></font></span></div></blockquote></div><br></div>