IANA Charset Registration Procedures
draft-iana-charset-reg-procedure-00
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
---|---|---|---|
Authors | Mark McFadden , Alexey Melnikov | ||
Last updated | 2015-04-24 (Latest revision 2014-10-21) | ||
RFC stream | (None) | ||
Formats | |||
Additional resources | |||
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
Multipurpose Internet Mail Extensions (MIME) (RFC-2045, RFC-2046, RFC-2047, RFC-2231) and various other Internet protocols are capable of using many different charsets. This in turn means that the ability to label different charsets is essential. This draft updates the IANA Charset Registration Procedures originally defined in [RFC2978]. Specifically, this document completely revises the registration procedures and the charset registries. The charset registry is now divided into three parts with separate registration procedures for each. Note: The charset registration procedure exists solely to associate a specific name or names with a given charset and to give an indication of whether or not a given charset can be used in MIME text objects. In particular, the general applicability and appropriateness of a given registered charset to a particular application is a protocol issue, not a registration issue, and is not dealt with by this registration procedure.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)