2822upd-04 body content restrictions

On Sunday 27 January 2008 10:47:17 Frank Ellermann wrote:
> 
> Bruce Lilly wrote:
>  
> > 2822upd-04 section 2.3 reads in part:
> >    o  CR and LF MUST only occur together as CRLF; they MUST NOT
> >       appear independently in the body.
> 
> > This makes me uneasy for several reasons:
> > 1. it bucks the trend at liberalizing body content (e.g. 8BITMIME
> > and BINARY SMTP extensions).
> 
> IMO 2822upd is about message/rfc822 with transmission as SMTP DATA
> in mind.  It's not about an UTF8SMTP message/global, it's also not
> about BINARYMIME BDAT, NNTP message/news, or (arguably) SMTP SEND.
[...]

You seem to have missed the point.  Let me try to explain again.
The MIME RFCs work harmoniously with RFC 822 as every MIME message
is a valid RFC 822 message and every component of MIME header fields
is a valid component of an RFC 822 field (and can be specified
without having to disambiguate ambiguities in 822 -- about which
more in a separate message).  Per contra, the referenced 2822upd-04
sections state that a significant subset of valid RFC 822/MIME
messages are no longer valid Internet Message Format messages -- not
only for generation (which would itself be a giant step backward),
but for parsing as well (section 2 is claimed to be "general", i.e.
not restricted to generation).

> > 0x00-0x7f (with no CRLF restriction), but not 0x80-0xff.
> 
> Where have you found the US-ASCII restriction ?  Excluding half of
> the octets would be odd for the purpose of a *binary* transport. 

Please read the original, where the specific ABNF and the reference
to the section where is is located can be found.