The MIME Message/i18n Media Type
draft-klensin-email-i18n-message-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dr. John C. Klensin | ||
| Last updated | 2004-02-03 | ||
| 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
Efforts to design an internationalization model for electronic mail frequently encounter situations in which an internationalized message -- perhaps one containing some headers with characters coded in UTF-8 -- must be converted and transported over a traditional, 7-bit infrastructure. This document provides a specification, building on the design of message/rfc822, for encapsulating messages with internationalized headers and/or body part content types. This specification is one of a group intended to provide a modified and extended email environment for fully internationalized email. If approved, it is expected to update the discussion of 'message/' content types in RFC 2046.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)