On Tue, Jul 08, 2008 at 02:27:41PM -0500, Pete Resnick wrote: > The document says: > > "If ABNF is used, you MUST include a normative reference to RFC 4234." > > To quote two fine radio personalities here in the states, this one seems > "boooooooooogus". Yes, any I-D that uses ABNF must include a normative > reference to RFC 4234, but for the IESG to not engage in review until it > is in there is silly beyond belief. Make a note to the author that they > need the reference and continue consideration.
Stupid question ---- isn't this specific thing something we should allow the secretariat to fix as part of the RFC publishing process, and in fact give them instructions to add the reference if they find it missing? They do things like fix/update references IIRC, and this is only a minor step beyond that, and should be well within their capabilities, I would think. Sure, we can ask document editors to add the reference to RFC 4234, and maybe we can even do things like include a reference to RFC 4234 in an RFC template file with a note to remove if the standard ends up not using ABNF, but there must be a class of things which could be streamlined to save time on both the document editors, reviewers, and AD's time. Regards, - Ted _______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf