SiteLibrary

Link Collectors Community

 



Internationalized Domain Names (IDN)
Published on 02/24/05 at 07:14:02 GMT by Norbert
 
ProgrammingAn issue we will have to deal with in the near future in our Web directory: IDN. A simple example, in a language that even in some parts of the south of the United States is the primary language: the English sentence "Why don't we simply talk in Spanish" translates as "Porqué no pueden simplemente hablar en Español". A Web site http://PorqueNoPuedenSimplementeHablarEnEspanol.org/ is WRONG: spelling is never a question of style, it's like spelling libary or morgage. Once we look at languages that do not use a latin script the problems multiply.

I put together a few links about IDN:

VeriSign IDN
United States Home > Products & Services > Naming and Directory Services > Domain Name Registry Services > IDNs  
Internationalized Domain Names    
"IDNs are domain names represented by local language characters. They  transform the Internet into a multilingual tool by enabling users to navigate  in their preferred script. VeriSign helps global organizations protect and secure their brands."
 -  Internet Users: i-Nav plug-in to navigate email using IDNs.
 -  Companies: IDNs helps to reach audiences in their local language, to strengthen brand recognition, and to improve user experience.
 -  IDN Standards: IDN Testbed to test the proposed IDN standards.

http://www.verisign.com/static/012758.pdf
Adoption of Internationalized Domain  Names (IDNs) in Applications: a White  Paper  DRAFT  IDN Software Developer Consortium
"... In May 2004, there were an estimated 945 million Internet users worldwide, with 81% living outside of the United States. ... Sixty-six per cent of the Internet online population does not speak English as a primary language, while greater than two-thirds of that does not speak any English at all."

http://www.ietf.org/rfc/rfc3490.txt.
IDN in Applications (IDNA) RFC 3490 (March 2003)
defines the handling of IDNs within client applications

http://www.ietf.org/rfc/rfc3491.txt
Name Preparation (nameprep) RFC 3491 (March 2003)
a method to ensure domain name uniqueness that makes sense to users

http://www.ietf.org/rfc/rfc3492.txt
Encoding Scheme (punycode) RFC 3492 (March 2003)
algorithm to turn a Unicode code point into an ASCII compatible string for DNS

http://idn.isc.org/
a blog about IDN OSS development and IDN related news, also a wiki.

http://www.icann.org/general/idn-guidelines-20jun03.htm
Guidelines for the Implementation of Internationalized Domain Names
Version 1.0 20 June 2003

http://www.ietf.org/rfc/rfc3492.txt
A. Costello: RFC 3492 (March 2003)
Punycode: A Bootstring encoding of Unicode for Internationalized Domain Names in Applications (IDNA)
... uniquely and reversibly transforms a Unicode string into an ASCII string.  ASCII characters in the Unicode string are represented literally, and non-ASCII characters are represented by ASCII characters that are allowed in host name labels (letters, digits, and hyphens). ... defines a general algorithm called Bootstring ... Punycode is an instance of Bootstring that uses particular parameter ... appropriate for IDNA.
!! RFC 1034 [RFC1034] restricts the length of a domain label to 63 characters.

From their examples:
  -  (D) Czech: Pro(ccaron)prost(ecaron)nemluv(iacute)(ccaron)esky
      Punycode: Proprostnemluvesky-uyb24dma41a
  -  (J) Spanish: Porqu(eacute)nopuedensimplementehablarenEspa(ntilde)ol
      Punycode: PorqunopuedensimplementehablarenEspaol-fmd56a
...
8. Security Considerations
"  ... there can still be multiple Unicode representations of the "same" text, for various definitions of "same".  This problem is addressed to some extent by the Unicode standard under the topic of  canonicalization, and this work is leveraged for domain names by Nameprep ..."
Appendix A. Mixed-case annotation ...
Author: Adam M. Costello, University of California, Berkeley  http://www.nicemice.net/amc/

http://www.ietf.org/rfc/rfc3491.txt
P. Hoffman IMC & VPNC, M. Blanchet Viagenie: RFC 3491 (March 2003)
Nameprep: A Stringprep Profile for Internationalized Domain Names (IDN)
describes how to prepare internationalized domain name (IDN) labels to increase the likelihood that name input and comparison work in ways that make sense for typical users throughout the world.  
Hoffman, P. and M. Blanchet, "Preparation of Internationalized Strings ("stringprep")", RFC 3454, December 2002.
9. Security Considerations
  ... users of security protocols might do visual matching ... stringprep does nothing to map similar-looking characters together ...

 Printer Friendly Version - Internationalized Domain Names (IDN)  Log in to use this feature   931 reads
All Articles by Norbert

  Comments on this article:
 Internationalized Domain Names (IDN) | 0 comments | Sign Up

The comments are owned by the poster. We aren't responsible for the content.
Only registered members may comment on articles.
 
No comments so far.
 


Who's On


EST Nov. 2002 ~ Copyright © 2002-2008 ~ SiteLibrary


Member's Banner Ad
Member's Banner Ad - Got a Banner? Enter it Here!
View All Banners



This site was made with WebAPP Web Automated Perl Portal system v0.9.9.9 RC4 , a web portal system written in Perl.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the Poster.

XML v1.0