[IRT.RegDataPolicy] Rec14 IRT comments closing - privacy proxy
Anderson, Marc
mcanderson at verisign.com
Fri Oct 25 17:30:38 UTC 2019
Dennis, I support closing Rec #14. I agree that it makes sense to roll this recommendation into the section on publication of registration data. That will make the final policy language clearer and easier to implement. This is also the case in my proposed publication document.
I would like to suggest collapsing the 7.3 and 7.3.1 language. I’m not sure why the language was broken up in the first place, but it would be cleaner to read as a single section along the lines of the language in Rec #14:
7.3 In the case of a domain name registration where an "affiliated" privacy/proxy service is used, Registrar (and Registry where applicable) MUST include in the public RDDS and return in response to any domain name query full non-personal RDDS data of the privacy/proxy service, which MAY also include the existing privacy/proxy pseudonymized email
Best,
Marc
From: IRT.RegDataPolicy <irt.regdatapolicy-bounces at icann.org> On Behalf Of Dennis Chang
Sent: Thursday, October 24, 2019 6:08 PM
To: irt.regdatapolicy at icann.org
Subject: [EXTERNAL] [IRT.RegDataPolicy] Rec14 IRT comments closing - privacy proxy
Call to close IRT comments on recommendation #14 regarding privacy proxy.
60
IRT review closing Recommendation #14 Analysis - privacy proxy<https://docs.google.com/document/d/1LVRC3qDxbOCtKs5TupX-S7MIYeoXPplPpdMT44Kgqp0/edit>
20191030
--
Kind Regards,
Dennis S. Chang
GDD Programs Director
Phone: +1 213 293 7889
Sykpe: dennisSchang
www.icann.org<http://www.icann.org> One World – One Internet
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/irt.regdatapolicy/attachments/20191025/08dd5785/attachment.html>
More information about the IRT.RegDataPolicy
mailing list