RFC 2279: UTF-8, a transformation format of ISO 10646
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3629.
Current document in this lineage: RFC 3629 — UTF-8, a transformation format of ISO 10646
In plain English — editorial summary, not part of the RFC
UTF-8, the object of this memo, has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values. This memo updates and replaces RFC 2044, in particular addressing the question of versions of the relevant standards. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2279
- Published
- January 1998
- Authors
- F. Yergeau
- Status
- DRAFT STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 10
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2044 (1996)
- RFC 2279 (1998)
- RFC 3629 (2003) ✓
Read the full history of UTF-8, a transformation format of ISO 10646 →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4042UTF-9 and UTF-18 Efficient Transformation Formats of UnicodeCurrent
April 2005
- RFC 7997The Use of Non-ASCII Characters in RFCsUpdated
December 2016
- RFC 2346Making Postscript and PDF InternationalCurrent
May 1998
- RFC 2083PNG (Portable Network Graphics) Specification Version 1.0Current
March 1997
- RFC 1952GZIP file format specification version 4.3Current
May 1996
- RFC 1951DEFLATE Compressed Data Format Specification version 1.3Current
May 1996
- RFC 1950ZLIB Compressed Data Format Specification version 3.3Current
May 1996
- RFC 3423XACCT's Common Reliable Accounting for Network Element (CRANE) Protocol Specification Version 1.0Current
November 2002
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?