icannwiki

Internationalized Domain Name

Revision as of 17:24, 16 September 2012 by Andrew (talk | contribs) (→ICANN and IDN)
This article is neutral, but is sponsored by Verisign,
the registry for .com, .net, & other TLDs.
You can learn more about their services here.
link={{{link}}}
link={{{link}}}
ICANNWiki Platinum Sponsor


An IDN (Internationalized Domain Name) is an Internet domain name that uses the latest ICANN protocols and standards to support domain names written in multiple scripts and languages (non-ASCII characters). They allow users to use the Internet without using English, which was long considered the default Internet language despite the Internet's growing base of international users. The first IDNs were implemented into the root in April, 2010; it is estimated that 60% of users now access the Internet in their native, non-English language.[1]

Overview edit

The IDN can also be perceived as the label displayed in a software application, in an alphabet or language-specific script. IDNs are stored in the DNS as ASCII strings. The DNS performs look-up services to ensure the translation of user-friendly names to locate the Internet resources, and it is restricted to using ASCII characters for acceptable domains. IDNs ensure the names written by means of non-ASCII scripts are translated into ASCII text compatible with the DNS.

IDN History edit

The IDN was proposed by Martin Dürst in 1996 and implemented in 1998 by Tan Juay Kwang and Leong Kok Yong. Later on, the IDNA system (Internationalizing Domain Names in Applications) was adopted and implemented in some top-level domain names. According to the IDNA system, an "internationalized domain name" signifies any domain name which contains labels on which the IDNA ASCII algorithm could be applied. James Seng (ChingHong Seng) has been credited as a primary inventor of IDNs.[2] In the early stages of his career, James Seng's mentor Dr. Tan Tin Wee inspired him to work on IDNs to curb the digital divide in Asia. With $24 million in investment from Venture Capital firms General Atlantic Partners and Network Solutions/Verisign, James went on become the founder and CTO of i-DNS.net. During this time, he was working on the standardization of IDNs as the Co-Chair of the IDN Working Group at the IETF. He also stressed the need for IDNs at various forums such as ICANN, ITU and IGF and his efforts have helped make IDN an Internet standard.

ICANN and IDN edit

According to ICANN, Internationalized Domain Names (IDNs) are domain names represented by local language characters. [3] These types of domain names could either contain non-ASCII script characters or letters.

An important milestone in the development of IDN TLDs was the October, 2009, ICANN meeting in Korea. At the meeting the ICANN Board approved the IDN ccTLD Fast Track Process that enabled countries to offer national domain names with non-Latin characters. At that time, ICANN accepted the development of IDN ccTLDs on the Internet using IDNA standards. [4]

ICANN Approves Delegation of IDN ccTLDs edit

The first IDN ccTLDs were successfully implemented into the DNS root zone in May, 2010, these included Russia (.рф), Egypt (صر.), Saudi Arabia السعودية.) and United Arab Emirates (امارات.).[5] In August 2010, ICANN approved the delegation of the Arabic script TLDs for Palestine (فلسطين.), Tunisia (تونس.) Jordan (الاردن.), Thailand (.ไทย) and the two IDN ccTLDs for Sri Lanka (.ලංකා) and (.இலங்கை.[6] ICANN also approved the Arabic script ccTLD for Iran, India, Qatar, Singapore, Syria and Taiwan.[7]

ICANN received 36 IDN ccTLD applications in 22 languages. Thirty IDN ccTLDs are currently delegated in the root zone.[8]

Rejected IDN ccTLDs edit

The internet governing body rejected the IDN application of the Bulgarian government for .6r, the Cyrillic translation of .bg due to its close similarity with the .br, ccTLD for Brazil.[9] In an interview, Bulgaria's Technology Minister Alexander Tsvetkov said that his government will appeal to ICANN to reconsider its decision. [10] In addition, Bulgaria's Deputy Transport Minister stated the government might modify its application or wait for the launching of an appeals procedure. He hoped that ICANN will accept their proposal by the end of 2011. Meanwhile, the Brazilian government supported ICANN's decision in rejecting the .6r citing that "any graphic confusion migh facilitate phishing practices" and other related problems.[11]

At ICANN 44 in Prague, the GAC addressed rejected IDN ccTLDs. Their communique asked ICANN to "urgently reconsider" its ruling, as they saw the move as having "erred on the too-conservative side, in effect applying a more stringent test of confusability between Latin and non-Latin scripts than when undertaking a side by side comparison of Latin strings." While not all of the rejected strings were addressed directly, the communique was understood to address ICANN's rejection of the aforementioned .6r from Bulgaria, Greek's .ελ (short for Ελλας, or Hellas), and a Greek transliteration of .eu). .ελ was rejected because of its similarity of .EA, which is a reserved 2 character ccTLD on the ISO-3166 list,[12] while the other was too similar to Estonia's .ee.[13]

Logistics edit

The syntax designed for the used of IDNA is known as "Punycode". The non-ASCII characters are transformed into a specific format containing only ASCII characters and then a unique identification is processed for the domain name. [14]

In order to see and use the characters found in IDNs various changes and specific settings may need to be manipulated within the Web browser, or the installation of foreign language packs may be required.

References edit

Retrieved from "https://icannwiki.org/index.php?title=Internationalized_Domain_Name&oldid=65854"