← Older revision
Revision as of 02:48, 21 September 2012
(One intermediate revision by one user not shown)
Line 7:
Line 7:
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 [[Root Zone|the root]] in April, 2010; it is estimated that 60% of users now access the Internet in their native, non-English language.
[http://mobile.ictqatar.qa/sites/default/files/documents/IDN_IGF_2011.pdf IDN IGF, ictqatar.qa]
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 [[Root Zone|the root]] in April, 2010; it is estimated that 60% of users now access the Internet in their native, non-English language.
[http://mobile.ictqatar.qa/sites/default/files/documents/IDN_IGF_2011.pdf IDN IGF, ictqatar.qa]
−
===Overview===
+
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]].
−
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===
+
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.
[http://www.quackit.com/domain-names/internationalized_domain_names.cfm Registering IDNs]
−
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.
[http://zodiacregistry.com/about.php About, ZodiacRegistry.com]
In the early stages of his career, James Seng's mentor Dr. Tan Tin Wee inspired him to work on [[IDN]]s 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.
+
−
+
−
===Logistics===
+
−
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.
[http://www.quackit.com/domain-names/internationalized_domain_names.cfm Registering IDNs]
+
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.
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.
−
==
ICANN and IDN
==
+
==
History
==
−
According to ICANN
,
Internationalized
Domain Names
(IDNs
)
are
domain names
represented by local language characters
.
[http://
www
.
icann.org
/
en/topics/idn/ IDN according to ICANN
]
These types
of
domain names could either contain non
-
ASCII script characters or letters
.
+
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
.
[http://
zodiacregistry
.
com
/
about.php About, ZodiacRegistry.com
]
In the early stages
of
his career, James Seng's mentor Dr. Tan Tin Wee inspired him to work on [[IDN]]s 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
.
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 national domain names with non-Latin characters. At that time, [[ICANN]] accepted the development of IDN ccTLDs on the Internet using IDNA standards.
[http://www.icann.org/en/topics/idn/ IDN ccTLD Fast Track Process according to ICANN]
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 national domain names with non-Latin characters. At that time, [[ICANN]] accepted the development of IDN ccTLDs on the Internet using IDNA standards.
[http://www.icann.org/en/topics/idn/ IDN ccTLD Fast Track Process according to ICANN]
Line 33:
Line 28:
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 to .EA, which is a reserved 2 character [[ccTLD]] on the [[ISO-3166]] list,
[http://idntraffic.com/?p=193 IDNtraffic.com]
while the other was too similar to Estonia's [[.ee]].
[http://domainincite.com/9667-gac-demands-appeal-of-idn-cctld-bans GAC Demands APpeal of IDN ccTLD Bans]
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 to .EA, which is a reserved 2 character [[ccTLD]] on the [[ISO-3166]] list,
[http://idntraffic.com/?p=193 IDNtraffic.com]
while the other was too similar to Estonia's [[.ee]].
[http://domainincite.com/9667-gac-demands-appeal-of-idn-cctld-bans GAC Demands APpeal of IDN ccTLD Bans]
+
+
===IDN New gTLDs===
+
: ''See a list of all IDN New gTLDs [[New gTLD IDN Applications|here]].''
+
+
It was revealed in June 2012 that 116 IDN [[New gTLDs]] had been applied for, 73 of them being Chinese language. Approximately half of these Chines TLDs come from mainland China, but a significant number of them were applied for by non-Chinese companies. Because of the restriction against single-character TLDs, many companies who would have applied for "网" (web) and "店" (shop), instead were forced to apply for "网站" (website) and "网店" (web-shop). The biggest IDN applicant was [[Zodiac]], which applied for 15 Chinese TLDs. [[Verisign]] applied for 12 foreign language transliterations of [[.com]] and [[.net]]. The languages with the second highest number of applications were Arabic (15) and Japanese (9).
[http://www.circleid.com/posts/20120614_analysis_of_the_idn_new_gtld_applications/ Analysis of the IDN New gTLD Applications, circleid.com]
==References==
==References==
Line 38:
Line 38:
[[Category: Glossary]]
[[Category: Glossary]]
+
__NOTOC__