Re: [Ltru] Re: Informative (was: Extended language tags)

Doug Ewell scripsit:

> I must not be a good enough RFC 2119 language lawyer to understand this. 
> I thought MUST was normative, and SHOULD and MAY were non-normative. 

I think that's a misunderstanding of "normative".  MUST, SHOULD, and
MAY all represent norms, they are just different kinds of norms, about
required, recommended, and optional behavior respectively.  A statement
in an RFC such as "A client MAY provide a CRC-32 checksum" means that it
is conformant either to provide the checksum or to omit it; no server
may complain in either case of a violation of the protocol.  This is
normatively defined behavior (or lack of behavior) on the server's part.

Informative content, on the other hand, is historical, exemplary,
explanatory, or the like.

By this standard, the Type, Subtag, Tag, Prefix, Preferred-Value,
and Suppress-Script fields are normative; the Description, Added,
Deprecated, Comments, and File-Date fields are informative.

-- 
Where the wombat has walked,            John Cowan <cowan@ccil.org>
it will inevitably walk again.          http://www.ccil.org/~cowan

_______________________________________________
Ltru mailing list
Ltru@ietf.org
https://www1.ietf.org/mailman/listinfo/ltru