Mmm... as editor of the document, maybe I should explain how this document
came into existence several years ago. It was back then that the IESG got
many many documents that had a lot of these simple (and easy to fix)
issues. Some look like showstoppers, others are not so much showstoppers,
but they do take extra time (of many people) if they need to be fixed
once the document goes into IETF Last Call. So in order to try and make
doument authors/editors and also WG chairs aware of what the many
little errors were that we as IESG often saw, we composed this document.
Hope this helps,
Bert Wijnen
-----Oorspronkelijk bericht-----
Van: ietf-bounces(_at_)ietf(_dot_)org
[mailto:ietf-bounces(_at_)ietf(_dot_)org]Namens Pete
Resnick
Verzonden: dinsdag 8 juli 2008 21:28
Aan: ietf(_at_)ietf(_dot_)org
CC: IETF Chair; iesg(_at_)ietf(_dot_)org
Onderwerp: Re: Call for review of proposed update to ID-Checklist
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.
pr
--
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf