I like this boiler plate wording a little bit better than what is in
draft-leiba-rfc2119-update.
I think it will better end the ambiguity as to whether lowercase is intended to
be normative within the document.
However, I’m not convinced it will reduce the amount of discussion as to
whether a particular use of one of these words in a document should have been
written in ALL CAPS.
Tony Hansen
On 8/10/16, 9:51 PM, "ietf on behalf of Randy Bush"
<ietf-bounces(_at_)ietf(_dot_)org on behalf of randy(_at_)psg(_dot_)com> wrote:
fwiw, i have been using the following for some years
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to
be interpreted as described in RFC 2119 [RFC2119] only when they
appear in all upper case. They may also appear in lower or mixed
case as English words, without normative meaning.
randy