Re: [Editorial Errata Reported] RFC5322 (3400)

Ned Freed <[email protected]> Wed, 28 Nov 2012 07:54:30 -0800 (PST)
Newsgroups gmane.ietf.rfc822
Message-ID <[email protected]>
> MIME describes CRLFs as line separators rather than line terminators which
> is consistent with 5322 (and necessary for correctly representing the
> encapsulated data) but unhelpful for resolving this niggle. RFC 3030
> (BINARYMIME / BDAT) assumes lines in textual bodies are terminated rather
> than separated which seems to be stricter than MIME specifies, but it
> does avoid Keith's worries.

Sorry, that's incorrect. The statements RFC 3030 makes are in the context of
converting to and from local storage formats. The intention is clearly to say
that line separators/terminator/delimiters/whatever have to be represented by a
canonical CRLF sequence.

At no time does RFC 3030 say that all lines in a text part have to be
terminated with a CRLF, only that when lines are terminated the terminator
has to be a CRLF. And as I pointed out previously: MIME explicitly allows
text parts that don't end in CRLF, and encoding is *not* required to
represent such parts inside of a multipart.

				Ned
_______________________________________________
ietf-822 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ietf-822