[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[idn] nameprep failures
- To: idn@ops.ietf.org
- Subject: [idn] nameprep failures
- From: "D. J. Bernstein" <djb@cr.yp.to>
- Date: 19 Jul 2001 01:35:39 -0000
- Automatic-Legal-Notices: Copyright 2001, D. J. Bernstein. My transmission of this message to you does not constitute a copyright waiver or any other limitation of my rights, even if you have told me otherwise.
- Mail-Followup-To: idn@ops.ietf.org
Mark Davis writes:
> I think the whole notion of trying to prevent cross-script confusions in
> domain names is a morass. It would invariably result in complicated rules
I see a domain name on a business card. I type it in. I'll be unhappy if
I don't get the right name. Isn't that the whole point of nameprep?
If I see WWW.AOL.COM, where the first dot is actually U+3002, then I'm
sure I'll type it incorrectly. Isn't this why nameprep prohibits U+3002?
If I see WWW.AOL.COM, where the A is actually a capital Alpha, then I'm
sure I'll type it incorrectly. So why doesn't nameprep prohibit Alpha?
It seems safe to allow lowercase Greek alpha (and not the other alphas)
as long as users _don't_ think they can type it in uppercase. We really
should deprecate the use of uppercase characters in domain names.
---Dan