-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
John Bambenek
wrote:
>
> But is the risk to self-identification as present when
> role-based accounts could be used as opposed to PII? I guess
> I'm not understanding the risks of people accidentally
> disclosing what they don't intend to.
The ris
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello,
John Bambenek
wrote:
> > All whois data is PII, in the case where people register
> > individual details, as opposed to organizational roles. I think
> > you may need to do a bit more research on this topic, you seem to
> > have misunderstoo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi :-)
John Bambenek wrote:
> > That said, I agree it cannot solve GDPR or other policy concerns.
>
> Why? GDPR applies to IP addresses, that doesn't impact DNS yet.
You appear to have confused IP with P(I)I: personally identifying
information.
A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello everyone,
Jim Reid wrote:
>
> BTW, whois was originally intended to provide a way to publish
> out-of-band contact data so the domain holder could be
> contacted whenever their DNS or email was broken. Putting this
> info in the DNS would de
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Nick, everyone,
Nick Johnson wrote:
> I'm working on a system that needs to authenticate a TLD
> owner/operator in order to take specific actions. We had
> intended to handle this by requiring them to publish a token in
> a TXT record under a su
