#ICANN62 @ICANN Board #netgov session: @icann_president visited UN, NY, 4-5 June, to meet with Secretary-General, Under-SG, Chair of G77, ambassadors & diplomats. Tarek Kamel tells Board the UN SG is very interested in netgov issues & his interest predates being the UN SG.— Samantha Dickinson (@sgdickinson) June 23, 2018
#ICANN62 @ICANN Board #netgov session: Tarek Kamel tells Board that ICANN is applying for @UNECOSOC accreditation. Not likely that accreditation will take affect until 2019.— Samantha Dickinson (@sgdickinson) June 23, 2018
#ICANN62 Community Input to the Charter Development of the GNSO Expedited PDP (EPDP): Heather Forrest presents draft timeline for the EPDP. Time for substantive work by the WG is only 4 months due to need to still do public comments processes within 12-month timeframe.#GDPR pic.twitter.com/Wdn4Qo6XFv— Samantha Dickinson (@sgdickinson) June 25, 2018
#ICANN62 Post #GDPR Whois/RDS Policy, @enoss: re GDPR’s benefits, the 7 million or so registrants of domain names since GDPR became active will not receive spam, not be inundated— Samantha Dickinson (@sgdickinson) June 26, 2018
by phone renewal requests, not be subjects to scams that pre-GDPR registrants have been targets of.
#ICANN62 Post #GDPR Whois/RDS Policy, @enoss: without any timely standard from the EU or from #ICANN, registrars had to obtain their own legal advice, in many cases at least 6 months before the 25 May deadline, on how to be in compliance.— Samantha Dickinson (@sgdickinson) June 26, 2018
#ICANN62 Post #GDPR Whois/RDS Policy, @how5: there’s very little new in terms of data protection requirements in the GDPR. #ICANN has not been in compliance with data protection law for the last 20 years.— Samantha Dickinson (@sgdickinson) June 26, 2018
#ICANN62 Post #GDPR Whois/RDS Policy, @enoss: users have been anonymous in their use of Whois since its onset. Post-GDPR, there's no way to determine “legitimate interest” without identifying who u are. Whois is an anachronistic set of data that’s public only because of history.— Samantha Dickinson (@sgdickinson) June 26, 2018
#ICANN62 Post #GDPR Whois/RDS Policy, @how5: to attempt to develop policy to replace the Temporary Specification in 4 months is heroic… and possibly stupid. We need to set ourselves up for success by limiting the amount we attempt to achieve in the EPDP.— Samantha Dickinson (@sgdickinson) June 26, 2018
#ICANN62 Post #GDPR Whois/RDS Policy, @enoss: if #ICANN issues Temp Spec on access, but if our legal advisors tell us it’s not in compliance with GDPR, then we won’t implement it. If we have to choose between litigating with ICANN or EU, reluctantly choose litigating with ICANN.— Samantha Dickinson (@sgdickinson) June 26, 2018
#ICANN62 Accreditation & Access to Non-Public Whois Data Post-#GDPR, @how5: That, or cast the net wider, & ask all DPAs globally, because data protection laws exist in more countries than just European ones. https://t.co/sbpFJTu7Xw— Samantha Dickinson (@sgdickinson) June 26, 2018
#ICANN62 Accreditation & Access to Non-Public Whois Data Post-#GDPR, Michael Palage: It’s been over a decade since @ICANN_GNSO has been able to complete a PDP in 1 year. It’s time to think outside the box. Encourages registrars to come forward with pilots, as @tucows has done.— Samantha Dickinson (@sgdickinson) June 26, 2018
Personal observation: the prevalence of handwringing, “what we really need to do is” & alarmed, angsty tone of speakers in #ICANN62 #GDPR sessions reminds me of the 1st ICANN meeting to discuss #IANAsteward transition… Only difference is this GDPR thing has truncated timeframe.— Samantha Dickinson (@sgdickinson) June 26, 2018
"For years people and organisations have had access to a LOT of data. They had unrestricted and complete access to everything. And in some respects they got addicted to that data" https://t.co/XrZgYIpuF3 #icann #gdpr #whois #panama— Blacknight Solutions (@blacknight) June 27, 2018
Despite reporting to GNSO otherwise, it is clear that ICANN org, as it told GAC today, is going to unilaterally come up with Access model in consultation with the European Data Protection Board and along with its friends in GAC. Clearly community won't be involved. #icann62— IGP Alert (@IGPAlert) June 27, 2018
#ICANN62 GAC/Board mtg, Russia: supports Brazil’s intervention. If possible, would be useful to begin discussions on how to move jurisdiction issue forward post-WS2 of CCWG-Accountability during #ICANN63 in Barcelona. https://t.co/I1qO12fBYr— Samantha Dickinson (@sgdickinson) June 27, 2018
ICANN62 GAC Communique ((pdf) embed below:#ICANN62 GAC Communique drafting: Panama Communique is adopted at 8:35 pm, Panama time! The Communique will be published tomorrow.— Samantha Dickinson (@sgdickinson) June 28, 2018
Editor's note: more on ICANN62 here and in this coming weekend's News Review on Domain Mondo.
