From: linuxa linux (firstname.lastname@example.org)
Date: Sun Nov 09 2008 - 13:56:42 CST
Please read response below.
I am not a technical expert, thus my understanding
could be flawed, thus I would like to say sorry for any
errors throughout this.
--- On Tue, 4/11/08, Ruszlan Gaszanov <email@example.com> wrote:
> From: Ruszlan Gaszanov <firstname.lastname@example.org>
> Subject: RE: Solutions to the IDN Problems Discussed
> To: email@example.com
> Cc: firstname.lastname@example.org
> Date: Tuesday, 4 November, 2008, 11:34 AM
> > There is a problem with solution #1 - it already
> > exists :) though for semi-ASCII language and
> > Internationalised domain names it does not work :(
> > because I visited this website
> > http://www.nameisp.com/puny.asp and did an
> > with total-ASCII language domain names and the
> > punycode representation was the same as the domain
> > name. Thus there is a problem with punycode machine
> > code presently, as it "cheats" and does not
> "code" the
> > total-ASCII language domain names like it does with
> > semi-ASCII language and Internationalised domain
> > names.
> Any other implementation would be incompatible with
> existing DNS
> infrastructure and requires developing a completely new
> name-lookup protocol
> as well as setting up a parallel server infrastructure.
Punycode exists at the Whois for Internationalised Domain Names and you could easily put a Y2K project management with a timeline for ending old type ASCII registrations and where new type Punycode registrations would commence at ASCII names. ASCII names would get processed via the Punycode field like you have with IDN and your previous ASCII field shuts, that's all. Both systems could exist simultaneously, the new process open and the previous closed yet continuing then later when there's learning curve development you could consider correcting the old type closed ASCII system. This system would allow registrations that are (1) IDN (Internationalised Domain Name) and also those that are (2) MDN (Multilingual Domain Names).
> Since such protocol
> would be fundamentally incompatible with any existing
> internet applications,
> new software will have to be developed. This would
> practically mean
> creating a second Internet.
Software applications would catch-up to this via the Y2K sort project management and also via market. Unicode got accepted then Punycode at ASCII registrations compatibility should also get accepted.
> Considering the cost and time requirements of such a
> project, as well as all
> the confusion and inconveniences the transition would
> cause, I do not really
> believe the user community would benefit from it. In any
> case this kind of
> project is quite beyond the mandates of either ICANN or
> Unicode Consortium.
You have Punycode existing at IDN then you can also use same at ASCII. Only the registration window get's changed and you have an extended Punycode that also changes ASCII registration into Punycode. The user community would really become happy because you would get quicker IDN implementation and a new type registration that are Multilingual. Software application integration would happen early. This would help those people that speak / write more than one language. People could then interact better and with virtue atmosphere than before they were able to with only their single language domains and software applications. You find that there are countries where the railway stations are using their traditional languages as well as the english language. The world has become more cosmopolitan and thus you need this to happen very urgently.
This archive was generated by hypermail 2.1.5 : Sun Nov 09 2008 - 14:24:41 CST