"Internationalized Domain Names for Applications (IDNA): Background, Explanation, and Rationale", John Klensin, 18-Jun-09. ( bytes)

Several years have passed since the original protocol for Internationalized Domain Names (IDNs) was completed and deployed. During that time, a number of issues have arisen, including the need to update the system to deal with newer versions of Unicode. Some of these issues require tuning of the existing protocols and the tables on which they depend. This document provides an overview of a revised system and provides explanatory material for its components.

"Internationalized Domain Names in Applications (IDNA): Protocol", John Klensin, 13-Jul-09. ( bytes)

This document is the revised protocol definition for internationalized domain names (IDNs). The rationale for changes, the relationship to the older specification, and important

"An updated IDNA criterion for right-to-left scripts", Harald Alvestrand, Cary Karp, 7-Aug-09. ( bytes)

The use of right-to-left scripts in internationalized domain names has presented several challenges. This memo discusses some problems with these scripts, and some shortcomings in the 2003 IDNA BIDI criterion. Based on this discussion, it proposes a new BIDI rule for IDNA labels.

"Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework", John Klensin, 22-Jun-09. ( bytes)

This document is one of a collection that, together, describe the protocol and usage context for a revision of Internationalized Domain Names for Applications (IDNA), superseding the earlier version. It describes the document collection and provides definitions and other material that are common to the set.

"Mapping Characters in IDNA", Pete Resnick, Paul Hoffman, 3-Jul-09. ( bytes)

In the original version of the Internationalized Domain Names in Applications (IDNA) protocol, any Unicode code points taken from user input were mapped into a set of Unicode code points that "make sense", which were then encoded and passed to the domain name system (DNS). The current version of IDNA presumes that the input to the protocol comes from a set of "permitted" code points, which it then encodes and passes to the DNS, but does not specify what to do with the result of user input. This document describes the actions taken by an implementation between user input and passing permitted code points to the new IDNA protocol.

Return to Internet-Draft directory.

Return to IETF home page.