RFC 3492: Punycode: A Bootstring encoding of Unicode for Internationalized Domain Names in Applications (IDNA)
In plain English — editorial summary, not part of the RFC
Punycode is a simple and efficient transfer encoding syntax designed for use with Internationalized Domain Names in Applications (IDNA). It uniquely and reversibly transforms a Unicode string into an ASCII string. ASCII characters in the Unicode string are represented literally, and non-ASCII characters are represented by ASCII characters that are allowed in host name labels (letters, digits, and hyphens). This document defines a general algorithm called Bootstring that allows a string of basic code points to uniquely represent any string of code points drawn from a larger set. Punycode is an instance of Bootstring that uses particular parameter values specified by this document, appropriate for IDNA. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3492
- Published
- March 2003
- Authors
- A. Costello
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 35
- Also known as
- —
- Updated by:
- RFC 5891
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 3731Extensible Provisioning Protocol (EPP) Domain Name MappingObsoleted
March 2004
- RFC 3732Extensible Provisioning Protocol (EPP) Host MappingObsoleted
March 2004
- RFC 3733Extensible Provisioning Protocol (EPP) Contact MappingObsoleted
March 2004
- RFC 2718Guidelines for new URL SchemesObsoleted
November 1999
- RFC 2717Registration Procedures for URL Scheme NamesObsoleted
November 1999
- RFC 2703Protocol-independent Content Negotiation FrameworkCurrent
September 1999
- RFC 2611URN Namespace Definition MechanismsObsoleted
June 1999
- RFC 4510Lightweight Directory Access Protocol (LDAP): Technical Specification Road MapCurrent
June 2006
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?