
Published:Thu, 04 Aug 2011 13:31:48 -0700
NEW HOSTEL... SINGAPORE: Foreign students of MDIS need not have to look far for accommodation -- its new S$80 million student hostel has opened its doors within the integrated cam......
Published:Fri, 19 Aug 2011 12:50:10 -0700
“Accountable care organizations” is the health wonk phrase du jour. Obamacare’s advocates point to its support for ACOs as one of the important cost-control initiatives in t......
Published:Tue, 23 Aug 2011 07:19:39 -0700
Shortly after the vote, Peter Dengate Thrush joined a New gTLD Group which stands to greatly benefit directly from this vote on the program he led on for nearly 3 years.......
Published:Mon, 08 Aug 2011 07:00:00 -0700
BOSTON, MASSACHUSETTS-- - AHRMM11 Annual Conference & Exhibition - TECSYS Inc. , an industry-leading supply chain management software company, announced today TECSYS Supply Manage......
Published:Sun, 07 Aug 2011 12:42:07 -0700
After a touching keynote address by ICANNs Kurt Pritz, industry leaders shared viewpoints and predictions at Master of Your Domain? New TLD Conference for the first time since his......
Internationalizing Domain Names in Applications (IDNA) is a mechanism defined in 2003 for handling internationalised domain names containing non-ASCII characters. These names are typically written in languages or scripts which do not use the Latin alphabet: Arabic,Hangul, Hiragana and Kanji for instance. Although the Domain Name System supports non-ASCII characters, applications such as e-mail and web browsers restrict the characters which can be used as domain names for purposes such as a hostname. Strictly speaking it is the network protocols these applications use that have restrictions on the characters which can be used in domain names, not the applications that have these limitations or the DNS itself. To retain backwards compatibility with the installed base the IETF IDNA Working Group decided that internationalised domain names should be converted to a suitable ASCII-based form that could be handled by web browsers and other user applications. IDNA specifies how this conversion between names written in non-ASCII characters and their ASCII-based representation is performed.
An IDNA-enabled application is able to convert between the internationalised and ASCII representations of a domain name. It uses the ASCII form for DNS lookups but can present the internationalised form to users who presumably prefer to read and write domain names in non-ASCII scripts such as Arabic or Hiragana. Applications that do not support IDNA will not be able to handle domain names with non-ASCII characters, but will still be able to access such domains if given the (usually rather cryptic) ASCII equivalent.
ICANN issued guidelines for the use of IDNA in June 2003, and it was already possible to register .jp domains using this system in July 2003 and .info domains in March 2004. Several other top-level domain registries started accepting registrations in 2004 and 2005. IDN Guidelines were first created in June 2003, and have been updated to respond to phishing concerns in November 2005. An ICANN working group focused on country code domain names at the top level was formed in November 2007 and promoted jointly by the country code supporting organization and the Governmental Advisory Committee.
Mozilla 1.4, Netscape 7.1, Opera 7.11 were among the first applications to support IDNA. A browser plugin is available for Internet Explorer 6 to provide IDN support. Internet Explorer 7.0 and Windows Vista's URL APIs provide native support for IDN.

Digg
|
Reddit
|
Mixx
|
del.icio.us
|
Stumble it! |