Re: [idn] compatibility chars in draft-ietf-idn-nameprep

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

>         While it might be reasonable to suggest this behaviour,
> it is outside the IETF's scope to require this of an API
> that *by its very definition* is NOT an IETF standard.

IETF does sometimes define APIs, even if they're not standardized.

regardless of whether IETF tries to define an API for IDN queries,
if it's important that character substitution be communicated to 
the application (and I think it is, if only for security purposes),
we need to find a way to say this.

> >That way it as at least possible to write applications which
> >handle these things reasonably.
> >
> >(applications used to do this with domain names- if you typed in
> >a name which mapped to a CNAME the app would then display the
> >name indicated by the CNAME record) 
> 
>         Many modern applications do not do this.  While some
> might consider this a bug, it is commonly not done today.
 
right.  but it worked well in the past and is worth considering again.

Keith