>>>>> "Adrian" == Adrian Farrel <adrian@xxxxxxxxxxxx> writes:
Adrian> How about... The key words "MUST", "MUST NOT", "REQUIRED",
Adrian> "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",
Adrian> "MAY", and "OPTIONAL" in this document are to be interpreted
Adrian> as described in [RFC2119] when they appear in ALL CAPS.
Adrian> These words may also appear in this document in lower case
Adrian> as plain English words, absent their normative
Adrian> meanings. Other words found in this document MAY also have
Adrian> their expected meanings. The term TROLL-BAIT is to be
Adrian> interpreted as described in [1].
I like this a lot with no sarcasm intended.
I'll note that in my normal reading mode I do not distinguish case,
but even so I find the ability to use may and should in RFC text without
the 2119 implications valuable.
Yes, you need to be careful. Yes, you should consider how your reader
might or might not notice the difference. Consider though if you're
saying something like "an octet may contain a value between 0 and 255."
It's not really normative; it's a statement of fact. However, the world
will not really be made worse if someone checks the range of their octet
values.