[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] UTF-8 as the long-term IDN solution
- To: idn working group <idn@ops.ietf.org>
- Subject: Re: [idn] UTF-8 as the long-term IDN solution
- From: "Adam M. Costello" <amc@cs.berkeley.edu>
- Date: Fri, 1 Jun 2001 22:46:06 +0000
- Delivery-date: Fri, 01 Jun 2001 15:46:53 -0700
- Envelope-to: idn-data@psg.com
- User-Agent: Mutt/1.3.17i
"Eric A. Hall" <ehall@ehsco.com> wrote:
> Applications store/display names that they are given by DNS, so DNS
> must provide them with the data in the appropriate format. Although
> the on-the-wire protocol can be ACE as you suggest, the resolver still
> needs a way to remember the desired disposition format of the query
> results.
Agreed.
> I suppose that it's technically feasible to ask resolvers to maintain
> state,
They already do. gethostbyname() blocks and retransmits the query until
the response comes back or the time limit is exceeded. That's quite
stateful.
> > and creating a new query format just for UTF-8 is certainly more
> > trouble than it's worth.
>
> No. The EDNS message is already defined and is required/used for
> things like A6 and DNAME already. This would just be another usage of
> that message. It also allows us to resolve the sizing problems.
Okay, creating a new query format just for UTF-8 would be more trouble
than it's worth, but it's not necessary, because the new format already
exists for other reasons, and we might as well specify that it uses
UTF-8.
Whether A6 and DNAME are useful enough to motivate wide deployment of
EDNS remains to be seen.
Marc Blanchet <Marc.Blanchet@viagenie.qc.ca> wrote:
> fyi, there is a draft for idn over edns (draft-ietf-idn-idne-xx.txt)
That looks good (after a cursory reading).
AMC