Niels comment in Chicago was related to the reseller drafts. Neils, if you have proposed text to add to draft-ietf-regext-verificationcode, please share it publically or privately.
Thanks, — JG James Gould Distinguished Engineer jgo...@verisign.com 703-948-3271 12061 Bluemont Way Reston, VA 20190 VerisignInc.com <http://verisigninc.com/> On 4/18/17, 8:41 AM, "regext on behalf of Hollenbeck, Scott" <regext-boun...@ietf.org on behalf of shollenb...@verisign.com> wrote: > -----Original Message----- > From: regext [mailto:regext-boun...@ietf.org] On Behalf Of Niels ten Oever > Sent: Tuesday, April 18, 2017 8:31 AM > To: regext@ietf.org > Subject: [EXTERNAL] Re: [regext] I-D Action: draft-ietf-regext- > verificationcode-01.txt > > Hi all, > > I just found out that this draft standards is already being approved by > ICANN since February, which somehow seems a bit the wrong way around: > > https://www.icann.org/en/system/files/correspondence/papac-to-kane- > 27feb17-en.pdf > > I brought up on this list and in the past two sessions that this document > would really benefit from Privacy Considerations (RFC6973). > > Not only because it is a good thing to do, but also because if we want > these practices to exist for some time they will need to abide by privacy > regulations (such as the upcoming GODR [0]). Niels, if I remember correctly James Gould asked you at the Chicago meeting if you could help with proposed text to be added to the document, and I think you agreed. Have you had a chance to work with him to come up with that text? Scott _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
