|Internationalized Domain Names
Study Group 17 (Security, languages and telecommunication software) has been instructed by Resolution 48 of the World Telecommunication Standardization
Assembly (Florianópolis, 2004) to study Internationalized Domain Names (IDN). It
is considered that implementation of IDN will contribute to easier and greater
use of the Internet in those countries where the native or official languages
are not represented in IRA (International Reference Alphabet) characters.|
To meet this obligation, Study Group 17 developed new Question 16,
Internationalized Domain Names tasked in particular to investigate specific and
issues in the field of IDN. The mandate for Question 16 is available on the
Study Group 17 website.
Question 16 was approved at the April 2006 Study Group 17 meeting in Jeju,
Korea. At this meeting Question 16 drafted a questionnaire for a Circular to
Member States, requesting information on their experiences in the use of IDN.
TSB Circular 96 was issued on 31 May 2006.
The purpose of this page is to share information on work progress, achievements
and acquired knowledge in the field of IDN.
Introduction to Internationalized Domain Names (IDN)
The abbreviation IDN stands for Internationalized Domain Name, also called a
multilingual domain name. Normal (traditional) domain names are limited to the
character set consisting of Latin letters (A-Z case ignored so includes a-z),
digits (0-9) and the hyphen (-), called LDH (Latin, Digits, Hyphen) characters
below. An IDN is a domain name that contains characters from the Unicode
repertoire, and therefore may contain letters with diacritics, as required by many European languages, or characters drawn from
non-Latin scripts such as Arabic or Chinese.
Though there are many concepts for implementing IDNs, the only recognized (standard) mechanism is called IDNA (Internationalized Domain Names in
Applications), and was agreed by the IETF’s IDN Working Group.
It was announced by IETF as a proposed standard in March 2003. The proposed standard encompasses the following IETF RFCs: RFC 3490, RFC 3491,
RFC 3492. (...more)
- Other Resources
- Results of the questionnaire
[01 December 2006: Replies received from Korea, Japan, Singapore,
Finland, Suriname, Armenia, Canada, United Arab Emirates, Lithuania,
Poland, Sweden, Denmark, Austria, Seychelles, Ukraine, Afghanistan,
Germany, Hong Kong (China), Switzerland, Liechtenstein, Kuwait, Venezuela,
Turkey, Vatican, France, Qatar, China]
- AfTLD members meeting, Cape Town, South Africa, 7 – 11 April 2008
- 18th CENTR Technical Workshop, Berlin, Germany, 4 May 2008
56th RIPE Meeting, Berlin, Germany, 5 -9 May 2008
- APTLD Meeting, Kuala Lumpur, Malaysia, 22 - 23 May 2008
- 13th CENTR Administrative Workshop, Crete, Grece, 4 June 2008
- 72nd IETF Meeting, Dublin, Ireland, 27 July – 1 August 2008
- 19th CENTR Technical Workshop, Dubai, United Arabic Emirates, 25 October 2008
- 57th RIPE meeting, Dubai, United Arabic Emiratem, 26 – 30 October 2008
- ICANN Meeting, Africa, 2 – 7 November 2008
- 73rd IETF, Minneapolis, USA, 16 – 21 November 2008
- Third Internet Governance Forum, Hyderabad, India, 3 – 6 December 2008