14. Informative References
[CESU-8]
Phipps, T., "Unicode Technical Report #26: Compatibility Encoding Scheme for UTF-16: 8-Bit (CESU-8)", UTR 26, April 2002, \http://www.unicode.org/unicode/reports/tr26/\``.
Description: CESU-8 is a UTF-8-like encoding that encodes UTF-16 code values instead of Unicode code points. It is not valid UTF-8 and is not intended for Internet use.
[FSS_UTF]
X/Open Company Ltd., "X/Open Preliminary Specification -- File System Safe UCS Transformation Format (FSS-UTF)", May 1993, \http://wwwold.dkuug.dk/jtc1/sc22/wg20/docs/N193-FSS-UTF.pdf\``.
Description: An early precursor to UTF-8, FSS-UTF was part of the standardization process that led to the current UTF-8 specification.
[RFC2045]
Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, November 1996.
Description: Defines the MIME framework for email message bodies, including character set labeling.
[RFC2234]
Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, November 1997.
Description: Defines the ABNF notation used to specify the UTF-8 byte sequence syntax in Section 4 of this document.
[RFC2978]
Freed, N. and J. Postel, "IANA Charset Registration Procedures", BCP 19, RFC 2978, October 2000.
Description: Specifies the procedures for registering character set names with IANA, which this RFC follows for the UTF-8 charset.
[UAX15]
Davis, M. and M. Duerst, "Unicode Standard Annex #15: Unicode Normalization Forms", An integral part of The Unicode Standard, Version 4.0.0, April 2003, \http://www.unicode.org/unicode/reports/tr15\``.
Description: Describes Unicode Normalization Forms (NFC, NFD, NFKC, NFKD) which provide solutions to canonical equivalence issues discussed in the Security Considerations section.
[US-ASCII]
American National Standards Institute, "Coded Character Set - 7-bit American Standard Code for Information Interchange", ANSI X3.4, 1986.
Description: The ASCII character set, which is fully compatible with and preserved in UTF-8 encoding.
Related Links
- Previous: 13. Normative References
- Return to RFC 3629 Home