[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] opting out of SC/TC equivalence
At 1:41 AM +0800 9/2/01, tsenglm@????.??.tw wrote:
>I just enhansize the issuse can not be neglected.
It is not being neglected. It has been addressed repeatedly here.
Because there cannot be a universally-deployed technical solution in
IDN, it must be deployed as rule that zone administrators know that
they should follow.
> 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.
VeriSign GRS is a zone administrator like all other zone
administrators. If they mess up, the folks controlling them (in this
case, ICANN) should tell them to fix the problem.
> 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.
For *all* users, we need it to work properly. Please remember that
most people in the world will find interface problems with IDN, just
the way they find them with the current DNS. (Said a different way,
we will probably manage to offend almost everyone with whatever we do
here.) If we can make sound technical decisions to reduce the
problems, fine; if not, we should finish and let the most-qualified
people work on the non-technical solutions.
It is clear that we cannot find sound technical solutions to the
simplified-traditional problem. So, we should move on, making sure
that whatever technical solution we create doesn't *prevent* a later
non-technical solution.
If you can show where the current IDNA/ACE/nameprep solutions prevent
an eventual traditional-simplified solution, please speak up.
Otherwise, it is probably better to spend your time starting to work
on the non-technical solution, such as suggestions to zone
administrators. The sooner that happens, the sooner that the users
will get what they want.
These statements may sound harsh to the people who have never
participated in the IETF before now, but they are the way that every
protocol is made. For every protocol, problems that could not be
solved technically in the protocol get solved in the marketplace.
This is true for HTTP, SMTP, Internet telephony, and on and on. IDN
will be no different.
--Paul Hoffman, Director
--Internet Mail Consortium