Oops, used wrong from address
----- Original Message -----
From: "Bert Wijnen" <hfam.wijnen@xxxxx>
To: "Pete Resnick" <presnick@xxxxxxxxxxxx>; <ietf@xxxxxxxx>
Cc: <iesg@xxxxxxxx>
Sent: Saturday, August 09, 2008 9:29 PM
Subject: Re: Call for review of proposed update to ID-Checklist
Pete....
Again, this was included in the ID-Checklist, because many many
documents did use ABNF without a citation/reference.
As stated before: the ID-Checklist does not (intend) to introduce
any new requirements that were/are not documented elsewhere in our
approved procedures/documents. So in that light, the ID-Checklist
might as well be abolished. Practice/experience has however shown
that many authors/editors of I-Ds do not follow our procedures very
well (not a big surprise, it is not easy to find them all) and so the
ID-Checklist tries to help them have the pointers in one place.
Bert
Editor of the ID-Checklist
----- Original Message -----
From: "Pete Resnick" <presnick@xxxxxxxxxxxx>
To: <ietf@xxxxxxxx>
Cc: "IETF Chair" <chair@xxxxxxxx>; <iesg@xxxxxxxx>
Sent: Tuesday, July 08, 2008 9:27 PM
Subject: Re: Call for review of proposed update to ID-Checklist
Re: Call for review of proposed update to ID-ChecklistThe 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@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf