(Sorry, resending due to a corporate mailer encryption setting user error on my part).
> -----Original Message----- > From: Niels ten Oever [mailto:li...@digitaldissidents.org] > Sent: Tuesday, April 18, 2017 9:29 AM > To: Gould, James <jgo...@verisign.com>; Hollenbeck, Scott > <shollenb...@verisign.com>; 'regext@ietf.org' <regext@ietf.org> > Subject: [EXTERNAL] Re: [regext] I-D Action: draft-ietf-regext- > verificationcode-01.txt > > Hi James, > > You're right. In Berlin I mentioned it in relation to the verification > code draft (and brought up the statement about it [0]), but similar there > are definitely also considerations for the resellers draft. Could you elaborate on that, please? The reseller (soon to be generic organization, I believe) draft(s) describe a means of exchanging information to identify an organization. Which bits of information do you see having human rights considerations? > Question is: should we create privacy considerations per draft, or would > it make more sense to make a draft with Privacy Considerations for EPP > (similar to RFC7819 did for DHCP). I don't know that I can answer that question without a better explanation of the kinds of things to be considered. I *can* see issues associated with personal privacy and the publication of contact information in WHOIS and/or RDAP (which points towards considerations for a document like RFC 5733), but where do you see considerations for a document like RFC 5732 in which there is no exchange of information associated with humans? Scott _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
