RFC 6055: IAB Thoughts on Encodings for Internationalized Domain Names
In plain English — editorial summary, not part of the RFC
This document explores issues with Internationalized Domain Names (IDNs) that result from the use of various encoding schemes such as UTF-8 and the ASCII-Compatible Encoding produced by the Punycode algorithm. It focuses on the importance of agreeing on a single encoding and how complicated the state of affairs ends up being as a result of using different encodings today.
Document record
- Document ID
- RFC6055
- Published
- February 2011
- Authors
- D. Thaler; J. Klensin; S. Cheshire
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 24
- Also known as
- —
- Updates:
- RFC 2130
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6409Message Submission for MailUpdated
November 2011
- RFC 5335Internationalized Email HeadersObsoleted
September 2008
- RFC 5137ASCII Escaping of Unicode CharactersCurrent
February 2008
- RFC 4042UTF-9 and UTF-18 Efficient Transformation Formats of UnicodeCurrent
April 2005
- RFC 9839Unicode Character Repertoire SubsetsCurrent
August 2025
- RFC 7997The Use of Non-ASCII Characters in RFCsUpdated
December 2016
- RFC 5895Mapping Characters for Internationalized Domain Names in Applications (IDNA) 2008Current
September 2010
- RFC 5892The Unicode Code Points and Internationalized Domain Names for Applications (IDNA)Updated
August 2010
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?