Re: [idn] new I-D: Safely Encoding of likeness information into ACE label version 0.2

["Soobok Lee" <lsb@postel.co.kr>]

----- Original Message ----- 
From: "James Seng/Personal" <James@Seng.cc>
To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>
 > Now to make it more interesting, lets take this Chinese ideograph
> 
> U+65E5 in UTF-8 ??
> U+66F0 in UTF-8 ??
> 
 > Or make how about U+6046 and U+6052? Different? Well, they are used
> similarly at least when we refer to hang shang bank of HK. (Depending
> what IME you use, they produce U+6046 or U+6052).
> 

Even If we normalize U+6046 into U+6052 ( or U+30AB -> U+529B ),
my I-D's likeness encoding will allow recover U+6046 (or U+30AB) 
as long as applications do not casefold the produced ACE label.

Likeness encoding prohibits  look-alike domains to be registered automatically
, while it allows  multiple representations of an IDN to be typed in and 
interchanged and displayed. 

With likeness encoding, look-alike normalization is not so expensive.
 
> 
> Bottomline: This is not an easy task. We need to ask ourselves in IDN WG
> if we have the right expertise to do this.   

I agree it will take much time.  
But I oppose to give birth to "immuno-deficient" premature IDN standard.
We or other relevant organizations should hurry up for it. 

Soobok Lee


> -James Seng