IDN TLDs

IDN ccTLDs:

The allocation of the TLD names has been very restricted, so the demands of more TLDs also started the debate on new requirements of non-English TLDs.

The combination of exposed domain names with internationalization requirements led rapidly to demands to permit domain names in applications that used characters other than those of the very restrictive, ASCII-subset, “hostname” (or “letter-digit-hyphen” (“LDH”)) conventions recommended in the DNS specifications [RFC1035]. The effort to do this soon became known as “multilingual domain names”. That was actually a misnomer, since the DNS deals only with characters and identifier strings, and not, except by accident or local registration conventions, with what people usually think of as “names”. There has also been little interest in what would actually be a “multilingual name”, i.e., a name that contains components from more than one language. Instead, interest has focused on the use, in the context of the DNS, of strings that conform to specific individual languages.

Many working groups worked for Internationalized Domain Names (IDNs) and ICANN launched a Fast Track Program for IDN ccTLDs. Since 16th Nov 09 Applications Processing for IDN ccTLDs Fast Track has been started.

The countries and territories who are using non-English Language (nationwide) for official documentation or for community, are eligible to apply for a new country code top level domain name (ccTLD) in their own Native Language through a designated manager. First four pioneers, the lucky-ones were Russian FederationThe United Arab EmiratesEgypt, and Saudi Arabia.

1. Russian Federation – .рф (meaning .rf in Cyrillic)
2. United Arab Emirates – .امارات (meaning .Emarat in Arabic)
3. Egypt – .مصر (meaning .Egypt in Arabic)
4. Saudi Arabia – .السعودية (meaning .AlSaudiah in Arabic, including desired variants السعودیة , لسعوديه ,السعودیۃ )

About 30 TLDs has been allocated to different countries in their own local official language scripts.