[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [idn] Reality Check



From: "Adam M. Costello" <amc@cs.berkeley.edu>
> Edmon <edmon@neteka.com> wrote:
>
> > 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?
>
> I don't follow.  The application gets the domain name from the user or
> an href attribute or wherever (not from DNS).  The application hands
> the domain name to the resolver, and gets back an IP address.  The
> application then opens a TCP connection to that IP address and sends the
> HTTP request, which includes the original domain name but not anything
> that came back from DNS.
>

Yes, I meant that when a dns application connects to the destination server,
it includes the "original domain name".  Do you at this point use ACE or
UTF8 or some other encoding?  IDNA mandates the use of ACE.  I think we
should have an "option" where if the destination HTTP server is IDN/UTF8
aware, then the UTF8 could be used.  This would give the incentive for
related servers and protocols such as HTTP servers to update to IDN/UTF8
extension.

Edmon