Re: [idn] Re: dichotomies

[Erik van der Poel <[e-mail]>]

JFC (Jefsey) Morfin wrote:
> (I will correct Erik's "xn--s" proposed notation into "xs--" not to 
> create havoc in punycode)

You are right, of course. What was I thinking? Duh. Well, how about 
"xs--n", to differentiate it from "xn--", and to still have the 
advantage of a non-delimiter-like character before the rest of the string?

> One of the reason why I disagreed with IDNA is it creates a possibly 
> conflicting left-to-right hierarchy while the DNS hierarchy is 
> right-to-left.

I'm afraid I don't understand this.

> This does not simplify understanding, management, security. Why not to 
> just use DNS zones? I have not yet understood why it was opposed. IMHO 
> the future of ML.ML names are in the form "name2.name.xx--chicom.com" 
> where "xx-nn.com" will print as ".com" in Chinese and name, name2 etc. 
> will all have to use codes from the Chinese Table of ".com".

I think your proposal makes some sense. It is similar to my proposal in 
a way -- recall my .jp example, with the rule that *all* labels would 
have to use the same ACE prefix or pure ASCII.

There isn't really any way to force the TLDs or zone administrators to 
follow any rules that we might come up with. The best we can do is write 
down some guidelines that are well thought out. And write them clearly.

If registries and zone administrators fail to follow the guidelines, the 
applications may have to display their domain names differently, to 
indicate some level of risk.

Also, we can't just suddenly switch a TLD from one encoding to another 
and then expect all the subdomains to follow suit the same night. 
Instead, we might have a rule specifying that all labels under the first 
new ACE prefix must use the same prefix. For example, suppose we have a 
new domain with the new prefix, called "xs--nfoo-abc.jp". Since the 2LD 
uses the new prefix, any 3LDs, 4LDs and so on would also have to use the 
new prefix. Does this make sense?

Finally, regarding displaying ".com" in Chinese, there is currently no 
reason to display ".com" in ASCII. This could easily be displayed in 
Chinese if the application developers were only willing to modify their 
programs to be more user-friendly. Of course, this brings up all sorts 
of issues like what to do with copy and paste, educating users about the 
new kind of display, being able to type ".com" in Chinese in one 
application while being required to type it in ASCII in another, and so 
on. There are some issues, but theoretically, you *can* already display 
".com" in Chinese.

This is not so different from Punycode itself, which you wouldn't 
normally display as is. You first decode it and then show the Unicode to 
the user.

Erik