Excerpts from ext.ietf-822: 25-Oct-91 Re: transport-related issue.. John
Noerenberg(_at_)qualcomm (1193)
But since RFC-XXXX offers both subset compliance and full compliance, a UA
should be able to distinguish compliance with the RFC from this field.
Nathaniel, how about adding a RFC-XXXXs (for subset) token for this
purpose?
Isn't this confusing messages and UA's? Surely a message with
"Body-Version: RFC-XXXX" will have to be RFC-XXXX *compliant*; that is,
everything in it will have to conform to the RFC -- I can't whimsically
rules on how Quoted-Printable is defined, for instance. A UA, on the
other hand, only has to be RFC-XXXX *conformant*; that is, it must
satisfy the description in the minimal-conformance appendix. Anything
above that is "features". But a UA that is conformant should be able to
"handle" (if only by dropping on the floor) any RFC-XXXX-compliant
message.
Bill