[93094] THU 01/29/98 15:24 FROM UNICORE@UNICODE.ORG: FW: RFC 2278 on Charset
        Registration; 142 LINES

Received: by rlg.org; Thu, 29 Jan 98 15:24:22 PST
Received: from unicode.org (unicode2.apple.com [17.254.3.212])
        by public.lists.apple.com (8.8.8/8.8.8) with SMTP id PAA41700
        ; Thu, 29 Jan 1998 15:16:43 -0800
Received: by unicode.org (NX5.67g/NX3.0S)
        id AA24330; Thu, 29 Jan 98 14:50:25 -0800
Message-Id: <9801292250.AA24330@unicode.org>
Errors-To: uni-bounce@unicode.org
Mime-Version: 1.0
Content-Type: multipart/mixed;
        boundary="---- =_NextPart_000_01BD2CDF.116D8040"
X-Uml-Sequence: 1621 (1998-01-29 22:50:22 GMT)
To: Multiple Recipients of Unicore <unicore@unicode.org>
Reply-To: unicore@unicode.org
From: "Winkler, Arnold F" <Arnold.Winkler@unisys.com>
Date: Thu, 29 Jan 1998 14:50:20 -0800 (PST)
Subject: FW: RFC 2278 on Charset Registration

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------ =_NextPart_000_01BD2CDF.116D8040
Content-Type: text/plain

Some more to look at
Arnold

> -----Original Message-----
> From: RFC Editor [SMTP:rfc-ed@ISI.EDU]
> Sent: Thursday, January 29, 1998 4:37 PM
> Cc:   rfc-ed@ISI.EDU
> Subject:      RFC 2278 on Charset Registration
>
>
> 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
>
> ...
>
> Below is the data which will enable a MIME compliant Mail Reader
> implementation to automatically retrieve the ASCII version
> of the RFCs.

------ =_NextPart_000_01BD2CDF.116D8040
Content-Type: message/rfc822

Subject:
Date: Thu, 29 Jan 1998 17:55:21 -0500
X-Priority: 3
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1458.49)
Content-Type: multipart/mixed;
        boundary="---- =_NextPart_002_01BD2CDF.116FF140"


------ =_NextPart_002_01BD2CDF.116FF140
Content-Type: text/plain


------ =_NextPart_002_01BD2CDF.116FF140
Content-Type: application/octet-stream;
        name="ATT51813.txt"
Content-Disposition: attachment;
        filename="ATT51813.txt"

Content-type: message/external-body;
        access-type="mail-server";
        server="mailserv@ds.internic.net"

Content-Type: text/plain
Content-ID: <980129123517.RFC@ISI.EDU>

SEND /rfc/rfc2278.txt

------ =_NextPart_002_01BD2CDF.116FF140
Content-Type: message/external-body;
        site="rfc";
        dir="rfc2278.txt";
        mode="ds.internic.net";
        access-type="anon-ftp"


------ =_NextPart_002_01BD2CDF.116FF140--

------ =_NextPart_000_01BD2CDF.116D8040--