> -----Original Message----- > From: regext <[email protected]> On Behalf Of James Galvin > Sent: Friday, June 08, 2018 9:33 AM > To: Registration Protocols Extensions <[email protected]> > Subject: [EXTERNAL] [regext] WGLC: draft-ietf-regext-bundling- > registration-03 > > The document editors have indicated that the following document is ready > for submission to the IESG to be considered for publication as an > Informational Document: > > Extensible Provisioning Protocol (EPP) Domain Name Mapping Extension for > Strict Bundling Registration https://datatracker.ietf.org/doc/draft-ietf- > regext-bundling-registration/ > > Please indicate your support or no objection for the publication of this > document.
I support publication as long there are still operators willing to implement and use this extension. I have not attempted to validate the schema or examples (more on that below), but I do have a few comments on the document itself. In no particular order: Several of the transform command descriptions say that they do not add any elements to the structures described in RFC 5731, but they do on to say "When the command has been processed successfully, the EPP <resData> element MUST contain child elements as described in the EPP domain mapping [RFC5731]. This EPP <extension> element SHOULD contain the <b-dn:upData> which contains <b-dn:bundle> element". It would be good to include examples of these modified response elements. Security Considerations: the document says (in so many words) that there's nothing here beyond the basic EPP considerations. I don't think I agree with that. For example, isn't there a risk of unintended consequences if transferring, modifying, or deleting one name affects an entire bundle of names? It might be a good idea to say something in this section to note that the client SHOULD know that a transform command can affect multiple domain names and not just the one passed as a command argument. Schema and examples: have these been confirmed to work? Scott _______________________________________________ regext mailing list [email protected] https://www.ietf.org/mailman/listinfo/regext
