Re: [idn] draft about <draft-ietf-idn-uname-01.txt>

["Adam M. Costello" <amc@cs.berkeley.edu>]

tsenglm <tsenglm@cc.ncu.edu.tw> wrote:

> Based on the DNS tree server, www.foo2.net www.foo-two.net will
> be "replaced " by the same ACE unique-name/identifier in resoving
> processing if they are mapped to the same ACE identifier.

You mean replaced in the application layer, so that, for example, the
browser knows that foo2.net and foo-two.net are the same?  For that to
happen, the resolver interface must be changed.  Right now, even if
foo.com and bar.com are both CNAME records for webhost.com, the browser
will not treat foo.com and bar.com as the same, which is good, because
webhost.com is probably using virtual hosting, so that foo.com and
bar.com really are logically separate sites.  If you want foo2.com and
foo-two.com to be considered the same by the browser, you need some
other relationship connecting them, not the alias (CNAME) relationship.
Even if you introduce a new resource record type (UNAME), the existing
resolver interface has no way of expressing any connection between
names other than the alias relationship, so you'd need a new resolver
interface.  Or you could inform the browser of the name equivalence at a
higher layer, for example using HTTP redirects.

AMC