Communicating Information for External Program Use in Internet Messages: The Process Content-Disposition Type
draft-rfced-exp-whalen-00

Document Type Expired Internet-Draft (individual)
Author Curtis Whalen 
Last updated 1997-09-22
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-rfced-exp-whalen-00.txt

Abstract

This memo provides a mechanism whereby messages conforming to the MIME specifications [RFC 2045, RFC 2046, RFC 2047, RFC 2048, RFC 2049] can convey information not intended for display by the Mail User Agent (UA), but for processing (as opposed to display) by an external program. It specifies a new type of 'Content-Disposition' (defined by [RFC 2183]), which is valid for any MIME entity ('message' or 'body part). When 'body part' is referred to in this memo, it is referring to any MIME entity, except in section 2.4. This memo is the definition of this type, as specified by Section 9 of [RFC 2183]. This document is intended as an extension to MIME. As such, the reader is assumed to be familiar with the MIME specifications, [RFC 822], and [RFC 2183]. The information presented herein supplements but does not replace that found in those documents.

Authors

Curtis Whalen (diamondplus@iname.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)