[Fwd: I-D ACTION:draft-hall-mime-app-mbox-00.txt]

[Eric A. Hall]

Here's my thinking. Given the choice between breaking applications that
rely on different end-of-line sequences versus breaking one or more of the
specifications, I've got to favor breaking the apps. Besides which,
checking for end-of-line strings and adapting/converting isn't exactly
rocket science.

Therefore, the major media-type for mbox files should be application.

I'll clarify in the spec that the canonical end-of-line sequence is
UNIX-specific and that applications MUST only transfer mbox files in that
format, but SHOULD be prepared to receive files in other formats for the
sake of robustness, and that any local processing and/or conversion is up
to the application[s].

I'll also add a statement up front that message/digest is preferred since
it doesn't have problems with eol, charsets, etc.

Everybody okay with that?

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/