>Alternately, one could add a "Document-Name: " header. Same difference,
>but maybe an extra header is more MIMEish.
Since the name="" is already used with MIME Content-type: headers, there's
no sense in inventing a new metainformation field. Also, I don't think the
extra metainformation field would work with a multipart MIME message, but I
do know that Content-type: is always going to be there for each piece of a
multipart MIME message, so the name="" method works regardless.
I would also expect that if you were to mail an HTML document to me from
your browser, the browser would put name="" info. on the Content-type:
header so my mail program would have a clue. When your browser mailed a
multipart MIME message with an TEXT, HTML, and PostScript version of the
document, each Content-type: would be labeled appropriately.