[rfc-dist] RFC 3718 on A Summary of Unicode Consortium Procedures, Policies, Stability, and Public Access

rfc-editor@rfc-editor.org rfc-editor@rfc-editor.org
Thu, 26 Feb 2004 18:06:07 -0800


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

        RFC 3718

        Title:      A Summary of Unicode Consortium Procedures,
                    Policies, Stability, and Public Access
        Author(s):  R. McGowan
        Status:     Informational
        Date:       February 2004
        Pages:      11
        Characters: 25865
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-rmcgowan-unicode-procs-03.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3718.txt

This memo describes various internal workings of the Unicode
Consortium for the benefit of participants in the IETF.  It is
intended solely for informational purposes.  Included are discussions
of how the decision-making bodies of the Consortium work and their
procedures, as well as information on public access to the
character encoding & standardization processes.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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.

Content-Type: Multipart/Alternative; Boundary="OtherAccess"

Content-Type:  Message/External-body;

Content-Type: text/plain
Content-ID: <040226180503.RFC@RFC-EDITOR.ORG>

DOC-ID: rfc3718

Content-Type:   Message/External-body;

Content-Type: text/plain
Content-ID: <040226180503.RFC@RFC-EDITOR.ORG>