RFC 5891: Internationalized Domain Names in Applications (IDNA): Protocol
In plain English — editorial summary, not part of the RFC
This document is the revised protocol definition for Internationalized Domain Names (IDNs). The rationale for changes, the relationship to the older specification, and important terminology are provided in other documents. This document specifies the protocol mechanism, called Internationalized Domain Names in Applications (IDNA), for registering and looking up IDNs in a way that does not require changes to the DNS itself. IDNA is only meant for processing domain names, not free text. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5891
- Published
- August 2010
- Authors
- J. Klensin
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 17
- Also known as
- —
- Updates:
- RFC 3492
Topics
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 3490 (2003)
- RFC 3491 (2003)
- RFC 5890 (2010)
- RFC 5891 (2010)
Read the full history of Internationalized Domain Names in Applications (IDNA): Protocol →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5890Internationalized Domain Names for Applications (IDNA): Definitions and Document FrameworkCurrent
August 2010
- RFC 5893Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA)Current
August 2010
- RFC 5894Internationalized Domain Names for Applications (IDNA): Background, Explanation, and RationaleCurrent
August 2010
- RFC 5892The Unicode Code Points and Internationalized Domain Names for Applications (IDNA)Updated
August 2010
- 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
- RFC 6409Message Submission for MailUpdated
November 2011
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?