Re: [idn] pool deadline imminent

[Keith Moore <moore@cs.utk.edu>]

> I'm working on such a solution; for lack of a better name I'll call it
> IDN-8. It is ACE + UTF-8, but with ACE restricted to only the places
> where it is needed: RFC 2822 headers and SMTP commands/responses.

which is out of scope for this working group.

> UTF-8 is used almost everywhere else, including on the wire for DNS
> queries. The most important changes that need to be made are to resolvers,
> although applications can link with a compatibility library so that they
> work even if the resolver hasn't been changed.

for your  proposal to be credible you need to explain how (for instance)
how a legacy email client talking to a legacy resolver can lookup an ACEd
IDN if the on-the-wire protocol uses raw UTF-8.

and for that matter, you should explain why using UTF-8 on the wire in
the DNS query provides any significant benefit over more compact encodings
such as DUDE.  nobody has explained this yet, beyond some vague appeals 
to idealism.

Keith