The IESG wrote: > > The IESG has received a request from an individual submitter to consider > the > following document: > > - 'The APPLICATION/MBOX Media-Type ' > <draft-hall-mime-app-mbox-02.txt> as a Proposed Standard > > The IESG plans to make a decision in the next few weeks, and solicits > final comments on this action. Please send any comments to the > iesg@xxxxxxxx or ietf@xxxxxxxx mailing lists by 2004-09-06. > > The file can be obtained via > http://www.ietf.org/internet-drafts/draft-hall-mime-app-mbox-02.txt > > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@xxxxxxxx > https://www1.ietf.org/mailman/listinfo/ietf-announce The draft mentions that "some form of external negotiation or prior agreement is often necessary in order to ensure that the contents of the database are accurately read by messaging systems on other hosts". MIME provides for such mechanisms via the Content-Type field parameters. It would appear to be desirable to define at least two parameter attributes for use with this media type, viz. one defining the separator between messages (perhaps as a regular expression), and another defining the line-ending sequence in use (defaulting to CRLF). Note that RFC 2231 provides mechanisms for quoting and encoding parameter content, so that for example a lone LF line-ending sequence could be encoded in the parameter value as "%0A". _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf