rfc2278.txt

著名的RFC文档,其中有一些文档是已经翻译成中文的的.


RFC 2278                  Charset Registration              January 1998


   reviewer may also recommend standards track processing (before or
   after registration) when that appears appropriate and the level of
   specification of the charset is adequate.

   Decisions made by the reviewer must be posted to the ietf-charsets
   mailing list within 14 days. Decisions made by the reviewer may be
   appealed to the IESG.

4.3.  IANA Registration

   Provided that the charset registration has either passed review or
   has been successfully appealed to the IESG, the IANA will register
   the charset, assign a MIBenum value, and make its registration
   available to the community.

5.  Location of Registered Charset List

   Charset registrations will be posted in the anonymous FTP file
   "ftp://ftp.isi.edu/in-notes/iana/assignments/character-sets" and all
   registered charsets will be listed in the periodically issued
   "Assigned Numbers" RFC [currently RFC-1700].  The description of the
   charset may also be published as an Informational RFC by sending it
   to "[e-mail]" (please follow the instructions to RFC
   authors [RFC-2223]).

6.  Registration Template

   To: [e-mail]
   Subject: Registration of new charset

   Charset name(s):

   (All names must be suitable for use as the value of a MIME content-
   type parameter.)

   Published specification(s):

   (A specification for the charset must be openly available that
   accurately describes what is being registered. If a charset is
   defined as a composition of a CCS and a CES then these defintions
   must either be included or referenced.)

   Person & email address to contact for further information:








Freed & Postel           Best Current Practice                  [Page 6]

RFC 2278                  Charset Registration              January 1998


7.  Security Considerations

   This registration procedure is not known to raise any sort of
   security considerations that are appreciably different from those
   already existing in the protocols that employ registered charsets.

8.  References

   [ISO-2022]
        International Standard -- Information Processing -- Character
        Code Structure and Extension Techniques, ISO/IEC 2022:1994, 4th
        ed.

   [ISO-8859]
        International Standard -- Information Processing -- 8-bit
        Single-Byte Coded Graphic Character Sets
        - Part 1: Latin Alphabet No. 1, ISO 8859-1:1987, 1st ed.
        - Part 2: Latin Alphabet No. 2, ISO 8859-2:1987, 1st ed.
        - Part 3: Latin Alphabet No. 3, ISO 8859-3:1988, 1st ed.
        - Part 4: Latin Alphabet No. 4, ISO 8859-4:1988, 1st ed.
        - Part 5: Latin/Cyrillic Alphabet, ISO 8859-5:1988, 1st
        ed.
        - Part 6: Latin/Arabic Alphabet, ISO 8859-6:1987, 1st ed.
        - Part 7: Latin/Greek Alphabet, ISO 8859-7:1987, 1st ed.
        - Part 8: Latin/Hebrew Alphabet, ISO 8859-8:1988, 1st ed.
        - Part 9: Latin Alphabet No. 5, ISO/IEC 8859-9:1989, 1st
        ed.
        International Standard -- Information Technology -- 8-bit
        Single-Byte Coded Graphic Character Sets
        - Part 10: Latin Alphabet No. 6, ISO/IEC 8859-10:1992,
        1st ed.

   [ISO-10646]
        ISO/IEC 10646-1:1993(E),  "Information technology --
        Universal Multiple-Octet Coded Character Set (UCS) --
        Part 1: Architecture and Basic Multilingual Plane",
        JTC1/SC2, 1993.

   [RFC-2048]
        Freed, N., Klensin, J., and J. Postel, "Multipurpose Internet
        Mail Extensions (MIME) Part Four: Registration Procedures", RFC
        2048, November 1996.

   [RFC-1700]
        Reynolds, J., and J. Postel, "Assigned Numbers", STD 2, RFC
        1700, October 1994.





Freed & Postel           Best Current Practice                  [Page 7]

RFC 2278                  Charset Registration              January 1998


   [RFC-1759]
        Smith, R., Wright, F., Hastings, T., Zilles, S., and J.
        Gyllenskog, "Printer MIB", RFC 1759, March 1995.

   [RFC-2045]
        Freed, N., and N. Borenstein, "Multipurpose Internet Mail
        Extensions (MIME) Part One: Format of Internet Message Bodies",
        RFC 2045, November 1996.

   [RFC-2046]
        Freed, N., and N. Borenstein, "Multipurpose Internet Mail
        Extensions (MIME) Part Two: Media Types", RFC 2046, November
        1996.

   [RFC-2047]
        Moore, K., "Multipurpose Internet Mail Extensions (MIME) Part
        Three: Representation of Non-Ascii Text in Internet Message
        Headers", RFC 2047, November 1996.

   [RFC-2119]
        Bradner, S., "Key words for use in RFCs to Indicate Requirement
        Levels", BCP 14, RFC 2119, March 1997.

   [RFC-2130]
        Weider, C., Preston, C., Simonsen, K., Alvestrand, H., Atkinson,
        R., Crispin, M., and P. Svanberg, "Report from the IAB Character
        Set Workshop", RFC 2130, April 1997.

   [RFC-2184]
        Freed, N., and K. Moore, "MIME Parameter Value and Encoded Word
        Extensions: Character Sets, Languages, and Continuations", RFC
        2184, August 1997.

   [US-ASCII]
        Coded Character Set -- 7-Bit American Standard Code for
        Information Interchange, ANSI X3.4-1986.















Freed & Postel           Best Current Practice                  [Page 8]

RFC 2278                  Charset Registration              January 1998


9.  Authors' Addresses

   Ned Freed
   Innosoft International, Inc.
   1050 Lakes Drive
   West Covina, CA 91790
   USA

   Phone: [phone]
   Fax:   [phone]
   EMail: [e-mail]


   Jon Postel
   USC/Information Sciences Institute
   4676 Admiralty Way
   Marina del Rey, CA  90292
   USA

   Phone: [phone]
   Fax:   [phone]
   EMail: [e-mail]





























Freed & Postel           Best Current Practice                  [Page 9]

RFC 2278                  Charset Registration              January 1998


Full Copyright Statement

   Copyright (C) The Internet Society (1998).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
























Freed & Postel           Best Current Practice                 [Page 10]