2. But in fact, if you look at the headers we have defined so far, you
will see that the only places 8bit freedom is allowed is in comments,
phrases, parameters and newsgroup-names.
you obviously don't get it. the definition of message/rfc822 is for
the content-type, not for the use of that content-type in email.
content-type definitions are independent of where they are used.
(the only exception is text/plain where the default charset is
"iso-8859-1" in http and "us-ascii" in email - but this was only a
hack for backward compatibility with pre-standards http.)
it's absolutely unacceptable for usefor to redefine the meaning
of message/rfc822 - even if they only pretend to do so for usenet.