Ancillary Content-Disposition Type
draft-newman-mime-cdisp-metadata-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Chris Newman | ||
| Last updated | 1999-03-24 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Content-Disposition [CDISP] header defines two disposition types: ``inline'' and ``attachment'' which can affect presentation of a MIME [MIME-IMB] body part. There have been a number of cases where one MIME body part is ancillary or contains meta-data for another MIME body part and is neither suitable for inline display by itself, nor is it useful if treated as an independent attachment and saved to a file by itself. If the recipient UA is not familiar with the specific media type, the user often is presented with a useless unrecognizable attachment. This memo proposes a third disposition type, ``ancillary'', to address this situation.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)