[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] Internationalized PTR draft submitted
- To: James Seng <James@Seng.cc>
- Subject: Re: [idn] Internationalized PTR draft submitted
- From: Rick H Wesson <firstname.lastname@example.org>
- Date: Mon, 18 Sep 2000 10:43:56 -0700 (PDT)
- cc: Randy Bush <email@example.com>, firstname.lastname@example.org
- Delivery-date: Mon, 18 Sep 2000 10:44:14 -0700
- Envelope-to: email@example.com
why are you on this language bent? If we have UTF-16 which represents
*all* languages why do we need a "tag" which can't be enforced to let us
know what language the name is in. In fact the name could be in many
Lets banish the term language in this group, you obviously mean charset and
thinking that I only want the Japanese IDN for an Arabic name is useless.
Lets just understand that localization of PTR records isn't going to happn
with i18n names.
On Tue, 19 Sep 2000, James Seng wrote:
> PTR has a failing which IPTR attempts to address, ie, locale info (language
> So a Japanese application may choose the Japanese IDN for the IP and the
> Korean application may choose the Korean IDN for the IP. How useful it is
> subjected to debate of cos.
> -James Seng
> Randy Bush wrote:
> > multiple names for one ip is a red herring (idiom for something which
> > distracts one from the proper path).
> > 6126.96.36.199.in-addr.arpa. PTR my.dom.ain.
> > PTR another.dom.ain.
> > PTR yet.another.name.
> > is perfectly legal and in common use.
> > randy