Re: [idn] SLC minutes

["Edmon" <edmon@neteka.com>]

Clarification on:
> Edmon Chung: <Some comment I did not quite get the point of about how
> TC/SC does not actually prohibit mixing the way Tashiro-san suggested.>
>

What I meant is that one of the misconceptions about TC/SC mapping is that
it prohibits the use of one of the mapped character, but that thinking is
not true.  For example, if a TC or SC character is mapped to T/S', a
registrant or a user can still use a domain that is in the form:

<TC><SC><TC>.example

It simply means that during matching within the DNS,

<T/S'><T/S'><T/S'>.example

will be used. So, even if a person typed in <TC><TC><TC>.example, it will
still match with <T/S'><T/S'><T/S'>.example.

This is the same as my thinking about LGC (Latin/Greek/Cyrillic) mapping,
that is

<ALPHA><a><A><alpha>.example

will be matched as

<a'><a'><a'><a'>.example

So, we can really fulfil the spirit of Nameprep that: "The user should not
be limited to only entering exactly the characters that might have been
used, but to instead be able to enter characters that unambiguously
[represents] the characters in the [perceived] host name.

Perhaps this issue (what I call, Character Equivalence Mapping) will be
discussed in other wgs but I just want to clarify what I meant during the
SLC-IDN meeting and that I think it is important for the usability of
multilingual domain names when they are deployed.

Edmon