Internet Corporation for Assigned Names and Numbers

RFCs Related to IDN

The revised IDNABIS specification (aka IDNA2008):

RFC 5890 [TXT, 53 KB] Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework

RFC 5891 [TXT, 38 KB] Internationalized Domain Names in Applications (IDNA): Protocol

RFC 5892 [TXT, 183 KB] The Unicode Code Points and Internationalized Domain Names for Applications (IDNA)

RFC 5893 [TXT, 38 KB] Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA)

RFC 5894 [TXT, 113 KB] Internationalized Domain Names for Applications (IDNA): Background, Explanation, and Rationale

The initial IDNA RFCs (aka IDNA2003):

RFC 3454 [TXT, 136 KB] Preparation of Internationalized Strings ("stringprep")

RFC 3490 [TXT, 52 KB] Internationalizing Domain Names in Applications

RFC 3491 [TXT, 12 KB] Nameprep: A Stringprep Profile for Internationalized Domain Names

RFC 3492 [TXT, 68 KB] Punycode: A Bootstring encoding of Unicode for Internationalized Domain Names in Applications

Informational texts:

RFC 3743 [TXT, 76 KB] Joint Engineering Team (JET) Guidelines for IDN Registration and Administration for Chinese, Japanese, and Korean

RFC 4185 [TXT, 52 KB] National and Local Characters for DNS Top Level Domain (TLD) Names

RFC 4690 [TXT, 100 KB] Review and Recommendations for Internationalized Domain Names (IDNs)

The development of IDNABIS:

A revised version of the IDNA protocol – IDNABIS – was recently approved by the IESG. The resulting RFC's are listed above. This action was initiated by an informal design team that evaluated experience gained in the implementation of IDNA since its introduction in 2003 and identified several key areas that would benefit from modification. These were described in RFC4690, and on its basis, a formal IETF working group was chartered with the preparation of IDNABIS. Core issues addressed by that group included: need for an unambiguous one-to-one relationship between the Unicode ("U-label") and the ASCII-encoded ("A-label") form of every IDN label; determining valid code points solely by their Unicode character properties, thereby removing the dependency on a specific version of Unicode; reducing problems with scripts written from right to left.

An additional non-normative document about mapping Mapping Characters in IDNA was produced by the IDNABIS working group but has not yet been moved into the RFC-Editor queue. This is due to an on-going discussion of compatibility details between the two versions of the protocol, and the extent to which latitude should be provided for addressing this matter locally.

All versions of the IDNABIS documents together with relevant associated material are available through the IETF or at Patrik Fältström's site:

Stay Connected

  • News Alerts:
  • Newsletter:
  • Compliance Newsletter:
  • Policy Update: