[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] I-D ACTION:draft-ietf-idn-uri-00.txt
- To: idn@ops.ietf.org
- Subject: Re: [idn] I-D ACTION:draft-ietf-idn-uri-00.txt
- From: "D. J. Bernstein" <djb@cr.yp.to>
- Date: 10 Jan 2001 03:06:34 -0000
- Delivery-date: Tue, 09 Jan 2001 19:07:42 -0800
- Envelope-to: idn-data@psg.com
- Mail-Followup-To: idn@ops.ietf.org
Adam M. Costello writes:
> There is a potential problem with host name comparisons.
All the problems you describe go away if nameprep is handled in the way
I've been suggesting: registries prohibit bad names, users have whatever
software is needed to type good names, and most programs are left alone.
> Software comparing IRIs presumably knows about case-equivalence among
> non-ASCII characters, but software comparing URIs might not.
Good names never include uppercase non-ASCII characters. Comparisons of
non-ASCII characters are bitwise comparisons.
> That means IRIs might use mixed-case host names, but when they are
> converted to URIs the non-ASCII characters must be forced to lower
> case (in the host part only, not the path).
All that complexity disappears. Converting IRI to URI is a simple matter
of converting Unicode to UTF-8.
---Dan