On 13 nov 2010, at 01.05, Masataka Ohta wrote:
> Some non-ASCII name wrote:
>
>>> 3. the general category of all code points, is one of { Ll, Lo, Lm,
>>> Mn }.
>
>> If you want more clarification than that (and the reference to
> > RFC5890 where it is discussed further), please send text.
>
> OK. Add the following:
>
> As the upper case character corresponding to 'y' with diaeresis
> is not uniquely defined, for example, localized domain names
> are unusable
>
> It should be noted that, extended case insensitivities beyond
> European characters, such as correspondence between Chinese
> ones, the problem is even more unsolvable.
>
> It should clarify how localized domain names are useless.
I have two problems with this text. First that I think it is wrong. Secondly
that the way IDN and other localization initiatives is by being a) backward
compatible [so that the matching algorithm can not be changed -- regardless of
what you want] b) because of [a] it pushes the "case insensitivity" matching by
asking applications to canonicalize in a way so that if canonicalize(a) ==
canonicalize(b), then a == b, i.e. not do the canonicalization in the DNS
protocol itself. Because the matching function can not be changed.
I therefore, as I think Paul said, suggest we should accept
draft-liman-tld-names-04 as it is now, and let the explanation on case
insensitivities (etc) are in the RFC589x IDNA2008 RFCs. I further think the
references are clear enough so that people that are interested find the sources
for the explanation.
Patrik
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
