IANA Registration of Content-Disposition Header Field value 'encapsulated'
draft-melnikov-iana-reg-cd-encapsulated-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Alexey Melnikov , Bernie Hoeneisen | ||
| Last updated | 2023-08-17 (Latest revision 2023-02-13) | ||
| Replaces | draft-melnikov-iana-reg-forwarded | ||
| 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
This document defines a new Content-Disposition header field value "encapsulated" to be used with "message/rfc822" and "message/global" media types. Content-Disposition "encapsulated" signals that enclosed message should be presented inline, instead of being presented as a forwarded message. One use case for this is for S/ MIME header protection.
Authors
Alexey Melnikov
Bernie Hoeneisen
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)