I have been trying to search about multilingual domains fortnight. The Technology is impressive but at a very nascent stage right now, the biggest hurdle is that still users are required to type .com after the domain , Confused ?
Well let me explain somethings ,
What is a multilingual domain ?
A domain name that is not in default ASCII interface, The English words like google.com are all transmitted in ASCII format. While गाैरव.com is a Hindi(multilingual) domain which i can register and use as a domain name, remember it is written in Unicode which is a NON-ASCII character.
So how it works ?
Let me try to make a rough Sketch how it works
1. A Registrar receives an IDN within an ASCII TLD (.com or .net) from the registrant.
2.The Registrar prepares the ISO 10646 character sequence as described in the Preparation of Internationalized Host Names Internet Draft5.
3.the Registrar transforms the ISO 10646 sequence into an ASCII PunyCode string.
4.The Registrar registers the domain
5.The Registry converts the Punycode domain to the ISO 10646 character sequence and prepares the sequence
6.The Registry transforms the prepared ISO 10646 character sequence into an ASCII Punycode string if it is matches with the original string passed by the Registrar, then the registration is permitted. If the strings do not match, then the domain was not prepared properly and the registration attempt is denied.
PS: I may be wrong and these are not the standards.
Isn`t there any inconsistency ?
Yes there is when the ASCII code is changed into the punycode small phonetic characters like halant in hindi can change the punycode with a larger difference, that`s why if punycode find a similar domain registered it denies the domain registration, But this not always works.
Still i am looking for more information , so this is surely going to be topic for next couple of days
Notice: All the work is under GFDL licence and copyright of Gaurav Mishra
Subscribe to:
Post Comments (Atom)
2 comments:
Well, Punycode seems to be a hack, as domain names are not stored in the Unicode character set (ISO-10646), instead application needs to convert domain names into Punycode equivalent before resolving it. So, it will be cool, if DNS RFC is revised for Unicode encoded domain names. Or at least Punycode conversion should be in DNS resolution libraries.
This conversion overhead is already being heavily talked as it will definately slow down the DNS servers.
If punycode conversion is done while DNS resolution it can slow down the nw a lot, Views ??
And is it possible to revise DNS non-ascii characters, or i must ask is it feasible ?
Views ??
Post a Comment