RFC 5894: Internationalized Domain Names for Applications (IDNA): Background, Explanation, and Rationale
In plain English — editorial summary, not part of the RFC
Several years have passed since the original protocol for Internationalized Domain Names (IDNs) was completed and deployed. During that time, a number of issues have arisen, including the need to update the system to deal with newer versions of Unicode. Some of these issues require tuning of the existing protocols and the tables on which they depend. This document provides an overview of a revised system and provides explanatory material for its components. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5894
- Published
- August 2010
- Authors
- J. Klensin
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 43
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5893Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA)Current
August 2010
- RFC 5891Internationalized Domain Names in Applications (IDNA): ProtocolCurrent
August 2010
- RFC 5890Internationalized Domain Names for Applications (IDNA): Definitions and Document FrameworkCurrent
August 2010
- RFC 5892The Unicode Code Points and Internationalized Domain Names for Applications (IDNA)Updated
August 2010
- RFC 3490Internationalizing Domain Names in Applications (IDNA)Obsoleted
March 2003
- RFC 6082Deprecating Unicode Language Tag Characters: RFC 2482 is HistoricCurrent
November 2010
- RFC 8753Internationalized Domain Names for Applications (IDNA) Review for New Unicode VersionsCurrent
April 2020
- RFC 9233Internationalized Domain Names for Applications 2008 (IDNA2008) and Unicode 12.0.0Current
March 2022
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?