Re: [idn] Reality Check

["Edmon" <edmon@neteka.com>]

From: "Adam M. Costello" <amc@cs.berkeley.edu>
> The application does not talk to the DNS server.  The application talks
> to the resolver, and the resolver talks to the DNS server.  The DNS
> protocol matters to servers and resolvers, but not applications.  (Am I
> wrong about this?

What I meant was the application using the DNS information then
communicating to a destination server such as an http server.  That is,
after they obtain an RR from the DNS, how they use the information to then
connect with the destination.  Should we not allow this to be in UTF8 in the
future?

> > This ensures that once the other components or protocols become UTF8
> > compliant, the DNS will not be stuck with ACE.
>
> I have no objection to defining a UTF-8 extension for DNS, but I don't
> see how it will have much impact on applications, and I certainly
> don't see any urgency.  IDN deployment can commence as soon as IDNA is
> finalized and approved, while the DNS extension can be rolled out soon
> after, or much later, with the same chance of success either way.

I think it is important that a UTF-8 extension is available either in
parallel or soon after, or there is a greater risk that we wont see an
upgrade anytime soon.

> Perhaps the people focused on the DNS protocol should redirect their
> attention to the resolver API, because that's where you can help
> applications.  This API is already being changed to support IPv6 (see
> RFC 2553), so I'd suggest coordinating with that effort.

Are you suggesting then that the discussion on using a UTF8 extension for
IDN in the DNS would be outside the scope of the IDN wg?

Edmon