Maintaining Presentation Guidelines on MIME Messages
draft-pritchett-mime-guidelines-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dan Pritchett | ||
| Last updated | 1994-04-05 | ||
| 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 introduction of MIME brings the standards required to construct robust mail user agents. These agents will quite often have presentation semantics. In many cases, the way to present a multipart message is clear based on the message, but there are times when this is not true. This document proposes a mechanism for dealing with those cases.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)