3 ms·
I don't think I came to the same conclusion you did after reading those 2 articles. While you say the lawsuit "isn't exactly hostile", I think it isn't exactly
by hn_throwaway_99 8y ago
I don't think I came to the same conclusion you did after reading those 2 articles. While you say the lawsuit "isn't exactly hostile", I think it isn't exactly "friendly" either, and it's not like ICANN is neutral and just looking to the courts for guidance. I don't think ICANN is pleased with this ruling, at all.
ICANN clearly wants to preserve the requirement around personal details in Whois data, while Tucows pretty much thinks that requirement goes against the spirit of GDPR. From your second link:
> ICANN’s goal, since discussions about the impact of the GDPR on domain registration began, has been to preserve as much of the status quo as possible. This has led ICANN to attempt to achieve GDPR-compliant domain registration via ‘process reduction’, as opposed to Tucows’ approach of starting with the GDPR and rebuilding from the ground up.
- JumpCrisscross 8y ago> ICANN clearly wants to preserve the requirement around personal details in Whois data They may just not want to get sued by the MPAA et al over facilitating copyright infringement. Without WHOIS, pursuing rogue domains gets harder.
- guitarbill 8y agoWe're not talking about no WHOIS, we're talking about reducing the number of WHOIS contacts, and not publishing WHOIS information for everybody to see it. Which yes, would means now you need e.g. a court order first before you'd get that information. So I guess "pursuing rogue domains gets harder" is one way to put it, or more legally correct another. For law enforcement this isn't a problem. For scummy copyright lawyers looking to make a quick buck, maybe it is. Guess which of those funds ICANN? And how exactly would not making WHOIS info public "facilitat[e] copyright infringement"? Nobody is buying it.