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


        BCP 19:
        RFC 2278:

        Title:      IANA Charset Registration Procedures
	Author(s):  N. Freed, J. Postel
        Status:     Best Current Practice
	Date:       January 1998
        Mailbox:    ned.freed@innosoft.com, Postel@ISI.EDU
	Pages:      10
        Characters: 18881
        Updates/Obsoletes:  None

        URL:        ftp://ds.internic.net/rfc/rfc2278.txt


MIME [RFC-2045, RFC-2046, RFC-2047, RFC-2184] and various other modern
Internet protocols are capable of using many different charsets. This
in turn means that the ability to label different charsets is
essential. This 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 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
be sent to RFC-DIST-REQUEST@ISI.EDU.

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

        To: rfc-info@ISI.EDU
        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 admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute