> -----Original Message----- > From: regext [mailto:regext-boun...@ietf.org] On Behalf Of Hollenbeck, > Scott > Sent: Friday, April 13, 2018 9:48 AM > To: 'gal...@elistx.com' <gal...@elistx.com>; 'email@example.com' > <firstname.lastname@example.org> > Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-org-02 > > > -----Original Message----- > > From: regext [mailto:regext-boun...@ietf.org] On Behalf Of James > > Galvin > > Sent: Friday, April 13, 2018 9:22 AM > > To: Registration Protocols Extensions <email@example.com> > > Subject: [EXTERNAL] [regext] WGLC: draft-ietf-regext-org-02 > > > > The document editors have indicated that the following document is > > ready for submission to the IESG to be considered for publication as a > > Proposed > > Standard: > > > > Extensible Provisioning Protocol (EPP) Organization Mapping > > https://datatracker.ietf.org/doc/draft-ietf-regext-org/ > > > > Please indicate your support for the publication of this document. > > I support publication of this document in concept, but I just noticed some > significant omissions that need to be addressed before it can move > forward. > > There is text missing to describe how the Role Values Registry described > in Section 7.3 should be created and managed by IANA. The authors might > want to look at Section 2 of RFC 8126 for a description of the kind of > information that's needed. > > In Section 7.1, text needs to be added to include registration of the > schema from Section 5. Section 6 of RFC 5731 can be used as an example of > the instructions for registering both the XML namespace and the XML > schema. Note that there is no XML included with registration of the > namespace.
Sorry, missed one: In Section 7.2, the IESG should be named as the registrant for a standards track extension. Scott _______________________________________________ regext mailing list firstname.lastname@example.org https://www.ietf.org/mailman/listinfo/regext