Charles Lindsey wrote:
It should be noted that, despite the use of the numbers "822", a
"message/rfc822" entity isn't restricted to material in strict conformance
to RFC822, nor are the semantics of "message/rfc822" objects restricted to
the semantics defined in RFC822. More specifically, a "message/rfc822"
message could well be a News article or a MIME message.
Clearly, strict RFC [2]822 compliance is not a requirement, and use for
News articles is explicitly encouraged (which is why Usefor makes it the
official way to encapsulate News).
The reference in 2046 is to "News article" as defined at the time 2046
was written, viz. RFC 1036, which uses the 822 message format. message/rfc822
always means headers comply with the 822 header syntax, no matter how
the Usefor WG tries to finagle things.
The only requirement is that the syntax should agree with RFC [2]822, and
I have no problem with that since the proposed Usefor wording for gateways
that we are discussing explicitly requires that it should be so on the
Email side of the gateway, and tells you what transformations are
necessary to ensure it. So I still do not see what Larry's problem is.
The draft does not provide a mechanism to ensure compliance.