Hello Soobok, Here are my comments on reordering. Apologies if they are too clear.
The additional complexity introduced by reordering is a very serious problem. It is true that this complexity is somewhat similar to the complexity of e.g. nameprep or conversion from a legacy encoding. However, on many platforms, both conversion from a legacy encoding as well as many aspects of nameprep are available as libraries, and are used for other purposes. In particular on constrained devices (mobile phones,...), most of nameprep can be simplified a lot if one knows what kinds of characters can be input. On the other hand, the benefits for the users are actually very small. Nobody wants to input domain names with 15 or more Hanzi or Hangul. Nobody will be able to remember them. Writing them down on a napkin will take a long time. Every company or organization that has such a long label in their domain name, and no shorter alternative, will simply not get any contacts directly to their web site. If they have a short alternative, why do they need a long version? (please note that there is no danger of spoofing by somebody else getting the long version :-). So this is a solution in search of a real problem, not worth bothering the whole world with additional complexity. Regards, Martin. At 13:11 01/10/10 +0900, Soobok Lee wrote: >Hi, all > >I am ready to receive any criticisms on REORDERING. >Any suggestions of improvements or downsides of REORDERING are all welcome. > >I expect many feedbacks from non-US and non-European participants and >observers. > >Thanks. > >Soobok Lee
