RE: BCP 19, RFC 2978 on IANA Charset Registration Procedures

From: Hart, Edwin F. (
Date: Thu Oct 19 2000 - 15:00:21 EDT

Please update the reference to ISO/IEC 10646-1: 2000, which ISO has recently
published and made available. It includes 31 amendments and 3 corrigenda to
the first (1993) edition.

Adding an optional mapping to 10646 is a good idea. FYI, ISO is in the
process of revising ISO 2375 (coded character set registration according to
ISO/IEC 2022) to add the option of a 10646 mapping. However, the draft
revision to 2375 specifies that the mapping is subject to a review process
because we expect that implementers may be depending on such mappings.

Ed Hart

Edwin F. Hart
The Johns Hopkins University Applied Physics Laboratory
11100 Johns Hopkins Road
Laurel, MD 20723-6099
+1-443-778-6926 (Baltimore area)
+1-240-228-6926 (Washington, DC area)
+1-443-778-1093 (fax)
+1-240-228-1093 (fax)

-----Original Message-----
From: Misha Wolf []
Sent: Thursday, October 19, 2000 13:53
To: Unicode List
Subject: Re: BCP 19, RFC 2978 on IANA Charset Registration Procedures

A new Request for Comments is now available in online RFC libraries.

        BCP 19
        RFC 2978

        Title: IANA Charset Registration Procedures
        Author(s): N. Freed, J. Postel
        Status: Best Current Practice
        Date: October 2000
        Pages: 11
        Characters: 21615
        Obsoletes: 2278
        I-D Tag: draft-freed-charset-regist-03.txt


Multipurpose Internet Mail Extensions (MIME) (RFC-2045, RFC-2046,
RFC-2047, RFC-2184) 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.
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.

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.

        Visit our Internet site at

Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be
the views of Reuters Ltd.

This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:21:14 EDT