Linlin, you might want to keep some text in the document so that the RFC Editor knows to change "XXXX" to the assigned RFC number and IANA knows to use that number.
Scott From: Linlin Zhou <zhoulin...@cnnic.cn> Sent: Monday, October 29, 2018 4:33 AM To: Hollenbeck, Scott <shollenb...@verisign.com>; regext <regext@ietf.org> Cc: iesg <i...@ietf.org> Subject: [EXTERNAL] Re: [regext] IANA Considerations for draft-ietf-regext-org and draft-ietf-regext-org-ext Thank you Scott. I checked the RFC7451, the registration should be updated like this, Name of Extension: Extensible Provisioning Protocol (EPP) Organization Mapping Document Status: Standards Track Reference: RFCXXXX Registrant Name and Email Address: IESG, i...@ietf.org<mailto:i...@ietf.org> TLDs: Any IPR Disclosure: None Status: Active Notes: None Regards, Linlin _____ Linlin Zhou From: Hollenbeck, Scott<mailto:shollenbeck=40verisign....@dmarc.ietf.org> Date: 2018-10-25 23:00 To: 'regext@ietf.org'<mailto:regext@ietf.org> CC: 'i...@ietf.org'<mailto:i...@ietf.org> Subject: [regext] IANA Considerations for draft-ietf-regext-org and draft-ietf-regext-org-ext Minor comments here that I just noticed while looking at a different document... The registration template for the EPP extensions registry is described in Sections 2.2.1 and 2.2.2 of RFC 7451. Both draft-ietf-regext-org and draft-ietf-regext-org-ext are missing the "Reference" information. It should be added, like this (or similar): Reference: RFC XXXX (please replace "XXXX" with the RFC number for this document after a number is assigned by the RFC Editor) Scott _______________________________________________ regext mailing list regext@ietf.org<mailto:regext@ietf.org> https://www.ietf.org/mailman/listinfo/regext
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
