Changes

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 navigate 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.<ref>[http://mobile.ictqatar.qa/sites/default/files/documents/IDN_IGF_2011.pdf IDN IGF, ictqatar.qa]</ref>

|note  = This article is neutral, but is [[Sponsorship|sponsored]] by [[Verisign]],<br> the registry for [[.com]], [[.net]], & other [[TLD]]s.<br>You can learn more about their services [http://www.verisigninc.com/?loc=en_US here].

|logo    = verisignlogo.png

|platsponsor = ICANNWiki [[Sponsorship|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 [[Root Zone|the root]] in April, 2010; it is estimated that 60% of users now access the Internet in their native, non-English language.<ref>[http://mobile.ictqatar.qa/sites/default/files/documents/IDN_IGF_2011.pdf IDN IGF, ictqatar.qa]</ref>

The syntax designed for the use of the IDN 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. <ref>[http://www.quackit.com/domain-names/internationalized_domain_names.cfm Registering IDNs]</ref>

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.

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 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.<ref>[http://zodiacregistry.com/about.php About, ZodiacRegistry.com]</ref>  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.

==History==

 

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.<ref>[http://zodiacregistry.com/about.php About, ZodiacRegistry.com]</ref>  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. In India [http://thetechportal.com/2016/08/18/xgenplus-supports-idn-domain-names-in-india/ XgenPlus] Email software has successfully started offering email services in all Indian languages on IDN domain names.  

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 script 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 national domain names with non-Latin characters. At that time, [[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>  

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. <ref>[http://www.icann.org/en/topics/idn/ IDN ccTLD Fast Track Process according to ICANN]</ref>  

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,<ref>[http://idntraffic.com/?p=193 IDNtraffic.com]</ref> while the other was too similar to Estonia's [[.ee]].<ref>[http://domainincite.com/9667-gac-demands-appeal-of-idn-cctld-bans GAC Demands APpeal of IDN ccTLD Bans]</ref>

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,<ref>[http://idntraffic.com/?p=193 IDNtraffic.com]</ref> while the other was too similar to Estonia's [[.ee]].<ref>[http://domainincite.com/9667-gac-demands-appeal-of-idn-cctld-bans GAC Demands APpeal of IDN ccTLD Bans]</ref>

==Logistics==

===IDN New gTLDs===

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. <ref>[http://www.quackit.com/domain-names/internationalized_domain_names.cfm Registering IDNs]</ref>

: ''See a list of all IDN New gTLD applications [[New gTLD IDN Applications|here]].''

 

It was revealed in June 2012 that 116 IDN [[New gTLD Program]] 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).<ref>[http://www.circleid.com/posts/20120614_analysis_of_the_idn_new_gtld_applications/ Analysis of the IDN New gTLD Applications, circleid.com]</ref>

 

Likely as part of new ICANN CEO's [[Fadi Chehadé]]'s internationalization of the organization, [[IDN]] gTLD applications were given priority in the [[batching|batching process]]. Batching is a term used to describe the prioritization of applications in such a way that ICANN staff can deal with them in an organized and efficient manner. The final process used to batch was a lottery, where applications were pulled at random. IDN applications were given the option to go first in this system.<ref>[http://domainnamewire.com/2012/12/05/confirmed-idns-will-be-prioritized-in-new-tld-queue/ Confirmed IDNs Will be Prioritized in New TLD Queue, DomainNameWire.com]Published Dec 5 2012, Retrieved Jan 18 2013</ref>

 

In 2013 Government of India started domain name registry of .bharat (in Hindi) IDN for multiple regional languages. In support of that [https://www.xgenplus.com/idn-email-web-hosting/ XgenPlus] - an Indian email solutions company started to offer [http://thetechportal.com/2016/08/18/xgenplus-supports-idn-domain-names-in-india/ IDN compliant email server] and hosted email services much before Gmail / Office365 ana yahoo.

 

In 2013 the ccTLD registry, [[IRNIC]], transitioned existing IDN registrations at the second level under .ir to full IDNs under .ایران.<ref name="study">[https://www.icann.org/en/system/files/files/eurid-middle-east-dns-study-initial-13oct15-en.pdf MEAC DNS Study], ICANN.org. Published 2015 October 13. Retrieved 2015 November 12.</ref>

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.

Beginning in July 11th, 2012, all .it domain names began allowing [[IDN|Internationalized Domain Names]] (IDN), allowing them to support Italian, French, and German accents and characters. In five minutes, 1,737 new IDNs were registered; in thirty, 2,620; in four hours, eight thousand.<ref name="idn">[http://centr.org/news/07-16-2012/2191/idn-success-italy IDN Success in Italy], Centr.org. Published 16 July 2012. Retrieved 29 November 2012.</ref> The first .it IDN name, registered in three seconds, was perché.it, followed by perchè.it, a misspelling of the former. Common words were registered in the first hours, along with accented words that are usually devoid of accents, such as "agentì", "pizzà", and "ìtalià". Non-Italian proper nouns were also registered in their native tongue, in the case of IDNs related to Austria -- österreich.it -- and the German city Cologne -- köln.it.<ref name="idn"></ref>

 

With 10,000 IDNs, Turkey has half the IDNs in the MEAC (Middle East and Adjoining Countries) region, at the second level, under [[.tr]].<ref name="study"></ref>

 

As of December 2014, 2̬% of the existing 91,000 full IDNs were in Arabic script, and the leading ones were [[.موقع]] (.mawqe, aka "site") and [[.شبكة]] (.shabaka, aka "web"). The strong performers in the region are United Arab Emirates, Saudi Arabia, Egypt, and Islamic Republic of Iran.<ref name="study"></ref>

 

[[Image:MiddleEastRegion.png|IDNS by Country (2009-2014)|400px]]

==References==

==References==

[[Category: Glossary]]

[[Category: Glossary]]