RFC 5892: The Unicode Code Points and Internationalized Domain Names for Applications (IDNA)
In plain English — editorial summary, not part of the RFC
This document specifies rules for deciding whether a code point, considered in isolation or in context, is a candidate for inclusion in an Internationalized Domain Name (IDN). It is part of the specification of Internationalizing Domain Names in Applications 2008 (IDNA2008). [STANDARDS-TRACK]
Document record
- Document ID
- RFC5892
- Published
- August 2010
- Authors
- P. Faltstrom
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 70
- Also known as
- —
- Updated by:
- RFC 8753
Topics
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 9233Internationalized Domain Names for Applications 2008 (IDNA2008) and Unicode 12.0.0Current
March 2022
- RFC 5891Internationalized Domain Names in Applications (IDNA): ProtocolCurrent
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 5890Internationalized Domain Names for Applications (IDNA): Definitions and Document FrameworkCurrent
August 2010
- RFC 6452The Unicode Code Points and Internationalized Domain Names for Applications (IDNA) - Unicode 6.0Current
November 2011
- RFC 9224Finding the Authoritative Registration Data Access Protocol (RDAP) ServiceCurrent
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?