Re: [idn] I-D ACTION:draft-ietf-idn-idna-08.txt

["Eric A. Hall" <ehall@ehsco.com>]

"Adam M. Costello" wrote:

> So you're saying that a label containing some octets in the range 0..7F
> and some in the range 80..FF is neither text nor binary, but actually
> a mixture of the two.

That's one way to read it. Another way to read it is that all of the
codepoints are opaque, except that ASCII ranges A-Z and a-z are to be
treated as case-neutral for the purposes of comparison ONLY. Which is, in
fact, exactly what RFC 1035 says.

> I assume it's the ASCII --> non-ASCII conversion that worries you, but
> that happens only when displaying names to users (the ASCII form would
> be user-hostile)

The results are identical to what would happen if we reinvented the
existing RRs. There is no practical difference to the user community. The
only safe way to handle either of these ridiculous scenarios is to let the
governing bodies decide how the data should be handled.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/