Re: [idn] IN-ADDR.ARPA

[Tan Tin Wee <tinwee@xxxxxxxxxxxx>]

This is what the UTF5 encoding provides,
an ability for those who still insist on 
using ASCII to read multilingual double byte
characters. Unfortunately, UTF5 transformation
may not lead to a meaningful or even semi-meaningful ASCII host name
but at least, you can key in the character string in ASCII.

bilingual in the sense that
a. it's got an ASCII UTF5 equivalent
b. it's got an double byte code that can be displayed through the
   appropriate viewer in the characters recognisable by the 
   native speaker of the language.

In this sense, the iDNS does fulfill this proposed requirement
of the Internationalisation of domain names

bestrgds

Tin Wee


Shane Kerr wrote:
> 
> Here's a concern about international DNS from an
> administrator point of view.  Currently, a lot of
> boxes have logs with the host names of other machines,
> derived from IN-ADDR.ARPA queries based on the IP of
> the TCP or UDP originator.  I would like to see the
> ability to have semi-meaningful host names preserved
> in the future while still being able to use a stinky
> old ASCII editor to review this information.
> 
> The iDNS proposal would allow this, but the names
> would be basically machine-parsable only.
> Additionally, some MOSTLY meaningful names, like say
> www.Gießen.de (also expressible as www.Giessen.de),
> would be expressed as a string of encoded values.
> 
> I'm not really married to the idea, but I think a
> bilingual international DNS system may be the right
> thing to do.  That is, hosts would specify both an
> old-fashioned alphanumeric plus dash host name, as
> well as a new-fangled iDNS name.  Just a thought.
> 
> Shane Kerr
> __________________________________________________
> Do You Yahoo!?
> Thousands of Stores.  Millions of Products.  All in one place.
> Yahoo! Shopping: http://shopping.yahoo.com