ICANN GDPR lawsuit

• Subject: ICANN GDPR lawsuit
• From: rubensk at gmail.com (Rubens Kuhl)
• Date: Mon, 4 Jun 2018 16:32:39 -0300
• In-reply-to: <[email protected]>
• References: <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]>

On Fri, Jun 1, 2018 at 1:56 AM, Hank Nussbacher <hank at efes.iucc.ac.il>
wrote:

> On 31/05/2018 21:44, John Peach wrote:
> > On 05/31/2018 02:37 PM, Dan Hollis wrote:
> >> On Thu, 31 May 2018, bzs at theworld.com wrote:
> >>> FWIW a German court has just ruled against ICANN's injunction and in
> >>> favor of Tucows/EPAG.
> >>>   https://www.icann.org/news/announcement-4-2018-05-30-en
> >>
> >> Welcome to contact-free whois?
> >>
> >> -Dan
> >
> >
> > Already been bitten by it and trying to get the contact info reinstated.
> >
> >
> >
> The entire whois debacle will only get resolved when some hackers attack
> www.eugdpr.org, ec.europa.eu and some other key .eu sites.  When the
> response they get will be "sorry, we can't determine who is attacking
> you since that contravenes GDPR", will the EU light bulb go on that
> something in GDPR needs to be tweaked.
>

Usually, identifying attackers at other online services is a duty on RIR
directories, and even the RIPE one is not suffering that many changes due
to GDPR.

Also, GDPR doesn't prevent law enforcement access.


Rubens

• Follow-Ups:
  • ICANN GDPR lawsuit
    • From: goemon at sasami.anime.net (Dan Hollis)

• References:
  • ICANN GDPR lawsuit
    • From: hank at efes.iucc.ac.il (Hank Nussbacher)

• Prev by Date: Broadcom vs Mellanox based platforms
• Next by Date: ICANN GDPR lawsuit
• Previous by thread: ICANN GDPR lawsuit
• Next by thread: ICANN GDPR lawsuit
• Index(es):
  • Date
  • Thread