[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] IDN WG Last Call: draft-ietf-idn-punycode-00.txt
At 01:42 PM 2002-01-30, Adam M. Costello wrote:
>Erik Nordmark <Erik.Nordmark@eng.sun.com> wrote:
>> I think the RFC 2119 upper case terms are more exact and allows
>> distinguishing between regular english use of these terms, such as "an
>> implementor should consider the performance ...", and rather exact
>> statements about the requirement levels in the specification.
>That's one of the reasons I don't like capitalizing those words. What
>if I'm reading a spec in which "must" is usually capitalized, but in one
>sentence it is lowercase. Am I required to obey that sentence or not?
>At that point I think we're making distinctions that don't exist.
Yes. "MUST" and "must" are equivalent. Where one intends
another meaning than that defined by RFC 2119, one should
use a different word.
IMO, it's good to uppercase these imperatives so that
cases where an imperative was used unintentionally are easily
noticed and corrected during the editing and review process.