Re: [idn] opting out of SC/TC equivalence

["James Seng/Personal" <James@Seng.cc>]

Dear Prof Tseng,

While using "TLD" to determine language or charset is one possible
*policy* solution, unfortunately, DNS is an resolution infrastructure
which should be independent of "TLD". It is by historical co-incident
that most TLDs are given to each country.

Suppose I have a .sg domain names, why *must* it be in Chinese? Why not
in Tamil or European? If I am a french company having an office in
Taiwan with a .tw domain names, why cant I use french names for my own
machine? Perhaps it *must* because it is of some policy set by SGNIC or
TWNIC but that is a policy by respective NICs, and should not come from
IETF. We engineers needs to design our protocol to be as flexible as
possible.

And when we say IDN, we are not even talking about 2LD..it could be 3LD,
4LD or even TLD itself. And in DNS infrastructure, it is not only used
for domain names as we know it. Many other research are using DNS in
some other ways which both you and me have no idea (I know of one
research which is trying to do biochemical naming using DNS).

Therefore, it is important that technical solution should be as
independent of any policy and not biased against any TLD, 2LD etc in
particular.

-James Seng

>           By this principle,  why partial set of CJK characters that
are
> partial setted by local language tag can be used with different TLD
> (cn,jp,tw..). Because the TLD implied the language tag and will let
them
> differentiable from other TLD .  The problems com from these
contraints:
>           1. Big table of UNICODE let domain name can be mixing
registed but
> viewed in part now.
>           2. Many duplicate, easy-to-confuse and
> un-normalied/non-canonicalied scripts in UNICODE.
>           3. No one can change the coding at one night , you can only
> transit step by step.
>           4. ML.com try to use all code point withou considering the
> troubles come from mixing.
>
> L.M.Tseng
>
>