[149712] in North American Network Operators' Group
Re: Dear RIPE: Please don't encourage phishing
daemon@ATHENA.MIT.EDU (Jimmy Hess)
Sun Feb 12 22:53:14 2012
In-Reply-To: <4F3877E7.2010904@necom830.hpcl.titech.ac.jp>
Date: Sun, 12 Feb 2012 21:52:16 -0600
From: Jimmy Hess <mysidia@gmail.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
2012/2/12 Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>:
> Valdis.Kletnieks@vt.edu wrote:
[snip]
> So, I can understand your attempt to insist on lowercase,
> but it does not work because DNS does not allow it.
[snip]
Not exactly... DNS is case-insensitive when you are talking about
7-bit ASCII; the set of alphabetic characters that can appear in a
DNS label; with no punycode.
IDN means that non-ASCII characters are represented using punycode.
As soon as you have a browser parsing punycode stuff, any string
containing unicode characters has a unique punycode encoding / RFC
3491 / RFC 3492.
The symbols represented in the punycode encodings are not case sensitive.
Uppercase A-Z vs Lowercase a-z in the generalized variable-length
integers are not distinct,
the punycode representation itself cannot really be case sensitive,
but the codepoint represented by the encoding, the result of decoding
the punycode is case-preserving.
--
-JH
