[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
ICANN GDPR lawsuit
Peering DB is also a directory service.
The only 'service' they provide is to distribute contact information.
Therefor maintaining and distributing information is in fact 'essential'.
Further, Peering DB make it easy to remove contact information.
The difference in legal systems makes Peering DB a very low risk in the EU.
Whois is more 'at risk' because it doesn't require individual information to maintain a net block.
BUT, most whois can be handled by role accounts and privacy guard services.
Best practice is to use role accounts.
Privacy guard deals with the now rare condition where a net block is owned by an individual.
Most domain name services have provided a privacy guard option for years.
Most network providers simply want an email address that works.
I don't really care if it is joe or the purple people eater as long as it gets
a response from an intelligent entity that can fix a routing issue.
For this purpose a level 1 tech capable of escalating an issue counts as
an intelligent entity.
From: NANOG [mailto:nanog-bounces at nanog.org] On Behalf Of Owen DeLong
Sent: Monday, June 04, 2018 12:58 PM
To: Baldur Norddahl <baldur.norddahl at gmail.com>
Cc: nanog at nanog.org
Subject: Re: ICANN GDPR lawsuit
> On Jun 3, 2018, at 22:44 , Baldur Norddahl <baldur.norddahl at gmail.com> wrote:
>> Yeah, what Niels is really leaving out here is the open question of
>> whether or not GDPR will eventually lead to the destruction of Peering DB.
> Of course it will not. We just need to accept that only roles not
> people are published. Those people will change job anyway and nobody updates whois.
> GDPR does not apply to companies, so you can still publish the owner
> of domains and IP prefixes as company names with contact information.
Much of the information in Peering DB is people. In fact, IIRC, peering DB doesnâ??t really have â??roleâ?? accounts.
Peering DB is unrelated to whois.
E-MAIL CONFIDENTIALITY NOTICE:
The contents of this e-mail message and any attachments are intended solely for the addressee(s) and may contain confidential and/or legally privileged information. If you are not the intended recipient of this message or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and any attachments. If you are not the intended recipient, you are notified that any use, dissemination, distribution, copying, or storage of this message or any attachment is strictly prohibited.