Re: [idn] proposals and deadlines

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

"Eric A. Hall" <ehall@ehsco.com> wrote:

>  3) Resolvers present two separate APIs: one for legacy names, one for
>     IDNs.
>
>  5) The UTF8 IDN resolver calls would generate messages with an EDNS
>     extended label type.
>
>  7) In those cases where the extended lookup failed, the client would
>     have to convert the UTF8 IDN to ACE

It would not only ACE-encode IDNs in DNS queries, but also ACE-decode
IDNs in DNS responses (because the application is using the UTF-8 API
and expects a UTF-8 answer), right?

This looks like it would work, but if I'm writing a resolver, and I'm
supposed to implement ACE-encode, ACE-decode, and EDNS, I'm probably
going to think to myself, "Hmmm, if I just pretend that the EDNS lookup
always fails, then I won't have to bother implementing EDNS, and the
application will never know the difference."

AMC