Internationalized Domain Name: Difference between revisions
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
According to ICANN,Internationalized Domain Names (IDNs) are domain names represented by local language characters. <ref>[http://www.icann.org/en/topics/idn/ IDN according to ICANN]</ref> These types of domain names could either contain non-ASCII scripts characters or letters. | According to ICANN,Internationalized Domain Names (IDNs) are domain names represented by local language characters. <ref>[http://www.icann.org/en/topics/idn/ IDN according to ICANN]</ref> These types of domain names could either contain non-ASCII scripts characters or letters. | ||
An important milestone in the development of IDN [[TLD]]s 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 domain names with non-Latin characters.<ref>[http://www.icann.org/en/topics/idn/ IDN ccTLD Fast Track Process according to ICANN]</ref> | An important milestone in the development of IDN [[TLD]]s 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 domain names with non-Latin characters.On October, 2009, [[ICANN]] accepted the development of IDN ccTLDs on the Internet using IDNA standards. <ref>[http://www.icann.org/en/topics/idn/ IDN ccTLD Fast Track Process according to ICANN]</ref> | ||
==ICANN Approves Delegation of IDN ccTLDs== | |||
The first IDN ccTLDs were successfully installed in the [[DNS]] root zone in May, 2010, which include Russia (.рф), Egypt (صر.), Saudi Arabia (السعودية.) and United Arab Emirates (امارات.). <ref>[http://blog.icann.org/2010/05/idn-cctlds-%E2%80%93-the-first-four/ IDN ccTLDs – The First Four]</ref> | |||
On August 2010, ICANN approved the delegation of the Arabic scripts for Palestine (فلسطين), Tunisia (تونس) Jordan (الاردن), Thailand (.ไทย) and the two IDN ccTLD for Sri Lanka (.ලංකා) and (.இலங்கை).<ref>[http://domainincite.com/palestine-gets-its-own-arabic-domain-names/ Palestine gets its own Arabic domain names]</ref> | |||
As of September, 2011, 16 countries have IDNs, and there are another 33 requests for IDNs in 22 different languages still pending with ICANN.<ref>[http://mobile.ictqatar.qa/sites/default/files/documents/IDN_IGF_2011.pdf IDN IGF 2011, ictqatar.qa]</ref> | As of September, 2011, 16 countries have IDNs, and there are another 33 requests for IDNs in 22 different languages still pending with ICANN.<ref>[http://mobile.ictqatar.qa/sites/default/files/documents/IDN_IGF_2011.pdf IDN IGF 2011, ictqatar.qa]</ref> | ||
==Rejected IDN ccTLD== | |||
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.<ref>[http://domainincite.com/icann-says-no-to-bulgarian-cctld/ ICANN says no to Bulgarian ccTLD]</ref> | |||
==Logistics== | ==Logistics== | ||
Revision as of 06:12, 2 April 2012
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 essentially 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 now 60% of users access the Internet in their native, non-English language.[1]
Overview[edit | edit source]
The IDN can also be perceived as the label displayed in a software application, in an alphabet or language-specific script. The 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. Based on these facts, the IDNs ensure the names written by means of native-language scripts are translated into ASCII text compatible with the DNS.
IDN History[edit | edit source]
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.
ICANN and IDN[edit | edit source]
According to ICANN,Internationalized Domain Names (IDNs) are domain names represented by local language characters. [2] These types of domain names could either contain non-ASCII scripts 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 domain names with non-Latin characters.On October, 2009, ICANN accepted the development of IDN ccTLDs on the Internet using IDNA standards. [3]
ICANN Approves Delegation of IDN ccTLDs[edit | edit source]
The first IDN ccTLDs were successfully installed in the DNS root zone in May, 2010, which include Russia (.рф), Egypt (صر.), Saudi Arabia (السعودية.) and United Arab Emirates (امارات.). [4] On August 2010, ICANN approved the delegation of the Arabic scripts for Palestine (فلسطين), Tunisia (تونس) Jordan (الاردن), Thailand (.ไทย) and the two IDN ccTLD for Sri Lanka (.ලංකා) and (.இலங்கை).[5]
As of September, 2011, 16 countries have IDNs, and there are another 33 requests for IDNs in 22 different languages still pending with ICANN.[6]
Rejected IDN ccTLD[edit | edit source]
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.[7]
Logistics[edit | edit source]
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. [8]
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.