On Wed, Aug 23, 2017 at 09:32:22PM -0400, John R Levine wrote:
> We already have a perfectly good mail encoding, the one defined in
> RFC 5322 and its predecessors. (Recall that MIME is entirely hidden
> inside the 5322 message structure.) I suppose you could come up
> with a convention for filenames, but it hardly matters since
> anything interesting about the message is within the message itself.
Great.
> >Might also be nice to have some well-known-filename with metadata
> >about the archive content, eg: self-URL, previous, next URL, contact
> >URL (if any), archive owner signed checksums of files. Template
> >spec of filenames (%YYYY-%MM.mail),...
>
> URL? This is mail, not a web site. In any event, if you want to
> make indexes and such on top of an archive, go ahead but it's not
> part of the archive.
>
> >See above: metadata that would help you figure out if you have a
> >complete set of archive files.
>
> A file listing the other files with hashes or checksums is all you
> need for that.
Are there any RFCs specifying how mirrors can point to each others so
folks retrieving the information can load-balance/failover etc.. That ws
pretty much the level i was suggesting, and its certainly an orthogonal
problem.
Cheers
Toerless
> R's,
> John
--
---
tte@xxxxxxxxx