Of course he will. ICANN has been acting ill-advised from the start. Instead of embracing GDPR and its impact and taking the essence of the regulation at heart and building upon that basis, ICANN ORG (and parts of the community) has been shirking its responsibilites until this day and continued to search for loopholes, excemptions and ways around it.

The law suit is just the latest example of this painful process, where ICANN now is specifically expanding its mandate to define a purpose for the collection of certain data.

Some excellent reading material on this issue can be found here:
https://www.internetgovernance.org/2018/05/28/the-injunction-icanns-lame-attempt-to-turn-dns-into-a-trademark-registry/

Best,
Volker



I have a feeling Schrems will likely triumph before ICANN.

-Carlton


==============================
Carlton A Samuels
Mobile: 876-818-1799
Strategy, Process, Governance, Assessment & Turnaround
=============================

On Sun, May 27, 2018 at 11:05 PM, Alan Greenberg <alan.greenberg@mcgill.ca> wrote:
https://www.icann.org/news/announcement-2018-05-25-en

For those who might not have noticed, on Friday, ICANN announced that it has filed injunction proceedings against a German registrar (associated with TUCOWS) that had informed ICANN that under the GDPR, it would no longer be collecting certain data (Admin and Technical contact info).

Collection is a critical step, in that if data is not collected, it cannot be released to accredited parties, no matter how good their justification is.

As I understand it (and that could be wrong), this is an interesting step, in that it takes the issue out of the hands of data commissioners and into the courts, where presumably ICANN will be given an opportunity to explain why it believes that such collection is important. Although data commissioners have been reported to say that they have no legal basis to grant a delay, this is something that the courts can do pending resolution.

Alan

_______________________________________________
RDS-WHOIS2-RT mailing list
RDS-WHOIS2-RT@icann.org
https://mm.icann.org/mailman/listinfo/rds-whois2-rt



_______________________________________________
RDS-WHOIS2-RT mailing list
RDS-WHOIS2-RT@icann.org
https://mm.icann.org/mailman/listinfo/rds-whois2-rt


-- 
Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.

Mit freundlichen Grüßen,

Volker A. Greimann
- Rechtsabteilung -

Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: vgreimann@key-systems.net

Web: www.key-systems.net / www.RRPproxy.net
www.domaindiscount24.com / www.BrandShelter.com

Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
www.facebook.com/KeySystems
www.twitter.com/key_systems

Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken 
Umsatzsteuer ID.: DE211006534

Member of the KEYDRIVE GROUP
www.keydrive.lu 

Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen.

--------------------------------------------

Should you have any further questions, please do not hesitate to contact us.

Best regards,

Volker A. Greimann
- legal department -

Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: vgreimann@key-systems.net

Web: www.key-systems.net / www.RRPproxy.net
www.domaindiscount24.com / www.BrandShelter.com

Follow us on Twitter or join our fan community on Facebook and stay updated:
www.facebook.com/KeySystems
www.twitter.com/key_systems

CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken 
V.A.T. ID.: DE211006534

Member of the KEYDRIVE GROUP
www.keydrive.lu 

This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.