[TSG-Access-RD] For consideration: Proposal to hash PoC in Public Domain Name Whois

[Hollenbeck, Scott]

(Trimming recipients)

> -----Original Message-----
> From: TSG-Access-RD <tsg-access-rd-bounces at icann.org> On Behalf Of Ram
> Mohan
> Sent: Tuesday, February 5, 2019 1:02 PM
> To: Adiel Akplogan <adiel.akplogan at icann.org>
> Cc: MAEMURA Akinori <akinori.maemura at board.icann.org>; tsg-access-
> rd at icann.org; David Conrad <david.conrad at icann.org>; John Crain
> <crain at icann.org>
> Subject: [EXTERNAL] Re: [TSG-Access-RD] For consideration: Proposal to hash
> PoC in Public Domain Name Whois
>
> Dear Akinori, Adiel,
> The TSG will consider this proposal and will revert to the BTC on the
> questions posed below in the next few weeks, certainly prior to the Kobe
> meeting.

Thanks for passing this on, Ram. At first glance I see potential for conflict with RFCs 6350/7095 (vCard/jCard)  and  7483 (RDAP responses). For example, the proposal suggests that an email address (which is returned as part of a jCard structure by RDAP) could be replaced with a hash value. RFC 6350 says this about vCard email address values: "Even though the value is free-form UTF-8 text, it is likely to be interpreted by a Mail User Agent (MUA) as an "addr-spec", as defined in [RFC5322]". So, we don't know how downstream consumers (such as vCard parsers) of these hash values will deal with them when they're expecting structured email addresses, telephone numbers, etc.

What part of this is actually in our remit? It doesn't have anything to do with authentication or authorization.

Scott