[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
ICANN GDPR lawsuit
The whois guard solution seems workable where the registrar just forwards information.
It would be nice if there were corporate phone numbers as GDPR doesn't apply to corporations.
For routing whois information there aren't going to be many individuals and it would seem
that the corporations who employee individuals should be the ones protecting those individuals
work emails by providing a generic contact email forward. Which is good practice anyway
since people leave and go on vacation and problems still happen.
And the routing whois information is a lot more relevant to most of us here.
Of course anyone posting to a public list should be aware that their email address is
part of that information. Which is particularly relevant to this list.
From: NANOG [mailto:nanog-bounces at nanog.org] On Behalf Of William Herrin
Sent: Friday, June 01, 2018 9:24 AM
To: list at satchell.net
Cc: nanog at nanog.org
Subject: Re: ICANN GDPR lawsuit
On Fri, Jun 1, 2018 at 8:47 AM, Stephen Satchell <list at satchell.net> wrote:
> In other words, how do you do your job in light of the GDPR
> restrictions on accessing contact information for other network operators?
> Please be specific. A lot of NOC policies and procedures will need to
> be updated.
Publish role accounts in whois instead of personal information?
Sorry, I don't mean to break up an energetic tirade but a phone number is not PII when it's attached to "hostmaster" instead of "John Doe".
You and I like knowing that there's a specific person there and it certainly helps when auditing public policy compliance but as a technical matter contact doesn't have to work that way.
I noticed that Namecheap solved their GDPR problem by simply making their "WhoisGuard" product free.
William Herrin ................ herrin at dirtside.com bill at herrin.us Dirtside Systems ......... Web: <http://www.dirtside.com/>
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.