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

["tsenglm@????.??.tw" <tsenglm@cc.ncu.edu.tw>]

Dear James:
                    I  am here are not to put ccTLD as the IDN TLD.  All the
thing I concerned is not to let SC/TC of CJK fall in a confusing & battle
status especially for users.                        We put SC/TC in tw and
cn and try to forget the trouble in plictical pressure , in this condition
why we against any language or scripts will used in tw ?
                    As a chinese language user , you must konw the  openness
characteristic in chinese characters.  You are younger so you can not
understand what happened in TC/SC
especially in PRC-SC.  But you must know the troubles in less normalization
and people can not easily communicated in Taiwan and China. You also know
that HK and MO are returned to China.  Mixing TC/SC will produce more
confusing in CJK area and that will produce more troubles in gTLD.
                    An Engineer will do right thing and try best not to do
something hurt others. No matter it is client solution or server based
solution , and what level domain that will be applied, the most basic issuse
is to reduce easy-to-confuse term .  You know the frequently used characters
are almost the same in Taiwan and China, most of them are different code
point in UNICODE and many of them are very similar especially in some small
difference in radical.  The most bad thing is people do not know the
confusing is existed in high probability.
                     Language tag is only a technique to reduce the
complexity in TC/SC ,  I do not expect programmer will like many special
case.   I  just enhansize the issuse can not be neglected.  We all know the
registration of ML.com will renew around November,  so there are time
schedule pressure ,  I  hope they can work in right way and produce less
confusings in using TC/SC.  Actually , I should not to worry them if I
assume they have troubles in it, but it is not so fair to users. For CJK
users , we need it work properly.

L.M.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
>