RFC 2781: UTF-16, an encoding of ISO 10646
In plain English — editorial summary, not part of the RFC
This document describes the UTF-16 encoding of Unicode/ISO-10646, addresses the issues of serializing UTF-16 as an octet stream for transmission over the Internet, discusses MIME charset naming as described in [CHARSET-REG], and contains the registration for three MIME charset parameter values: UTF-16BE (big-endian), UTF-16LE (little- endian), and UTF-16. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2781
- Published
- February 2000
- Authors
- P. Hoffman; F. Yergeau
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2756Hyper Text Caching Protocol (HTCP/0.0)Current
January 2000
- RFC 2952Telnet Encryption: DES 64 bit Cipher FeedbackCurrent
September 2000
- RFC 2953Telnet Encryption: DES 64 bit Output FeedbackCurrent
September 2000
- RFC 2967TISDAG - Technical Infrastructure for Swedish Directory Access GatewaysCurrent
October 2000
- RFC 2978IANA Charset Registration ProceduresCurrent
October 2000
- RFC 2986PKCS #10: Certification Request Syntax Specification Version 1.7Updated
November 2000
- RFC 2994A Description of the MISTY1 Encryption AlgorithmCurrent
November 2000
- RFC 3067TERENA'S Incident Object Description and Exchange Format RequirementsCurrent
February 2001
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?