ICANN has appointed a Chief Data Protection Officer

[David Cake]

I admit I find this development disappointing.
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:
 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; 
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);
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;
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. . 

David



> On 29 Jul 2017, at 3:32 am, Ayden Férdeline <icann at ferdeline.com> wrote:
> 
> ICANN has now appointed someone <https://www.icann.org/news/blog/introducing-icann-s-chief-data-protection-officer-cdpo> 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...
> 
> Best wishes, Ayden Férdeline 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20170731/94565c16/attachment.htm>