Re: [idn] IN-ADDR.ARPA

[Dirk-Willem van Gulik <dirkx@xxxxxxxxxxxxxx>]

On Thu, 25 Nov 1999, Harald Tveit Alvestrand wrote:

> At 12:27 25.11.99 +0800, Tan Tin Wee wrote:

> >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.

> Rob Austein's tagged name components proposal will also make this possible, 
> in that you can have 2 PTR records, one in ASCII and one in "charset+"; a 
> non-i18n resolver will get only one of these returned.

Let's also note that if you limit your scope to just being able to enter
things like

	telnet	Myi18nhost....
	ftp	Myi18nhost...

and URI's, all you need is a CNAME. A reverse lookup of the A record would
just give a PTR to something understandable with old fashioned tools.

I.e. IMHO 95% of the problem can be solved with very little effords. And
is the main thing to solve:

	entering a domain name your own way, in your own language

and having it telnet, ftp or web-browse to the 'right' place.

Dw.