[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
A little document editing nit....
I've been informed by a little bird that a certain member on the IESG
(not our esteemed Security AD) has a habit of voting Discuss on
documents who contain definitions of MUST, SHOULD, MAY, etc. instead of
referencing RFC 2119. The stated rationale that is given is that IETF
standards ought to be using a consistent meaning for these words, and
the best way to do this is to define them by reference instead of
having each document define them explicitly.
Personally, I think this is a little bit silly (as long as the
definitions are consistent, who cares whether they are incorporated by
value or by reference), but in the interests of avoiding some last
minute frustration and delay, document editors of all IPSEC documents
are hereby strongly encouraged to replace definitions of MUST, SHOULD,
MAY, etc. with text that reads something like this:
NB: The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this
document, are to be interpreted as described in [RFC 2119].
Many, but not all of the ipsec drafts already reference RFC-2119. If
you are a document editor, please check your documents and make sure
that if your document uses MUST, SHOULD, MAY, etc. that you reference
RFC-2119. Thanks!!
- Ted