The multipart/choices Content-Type
draft-palme-multipart-choices-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Jacob Palme | ||
Last updated | 2001-01-02 | ||
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 memo specifies that the existing MIME content-type 'multipart/alternative' should be restricted to cases where the alternatives differ in their content-type. When the alternatives differ in other properties than content-type, a new 'multipart/choices' content-type is to be used instead. This is necessary, because the present specification gives extremely bad downgrading for mailers not supporting use of 'multipart/alternative' for other differences than content-type. This memo also specifies a mandatory parameter to multipart/choices. This mandatory parameter will hopefully avoid the same problem occuring again in the future.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)