RE: [idn] Should we add U+FF0E FULLWIDTH FULL STOP to section 5.10 of Nameprep?

[Yves Arrouye <yves@realnames.com>]

> FULLWIDTH FULLSTOP(U+FF0E) is already compatibility 
> decomposed into Latin FULLSTOP (U+002E)  in KC Normalization 
> step in NAMEPREP. You can confirm that in page 4 of 
> http://www.unicode.org/charts/PDF/UFF00.pdf .
> 
> If any label contains U+ff0e to be mapped into u+002e in kc 
> norm in nameprep, it will be treated as error  in the 
> following prohibition stage in nameprep , since
> u+002E. is prohibited.

But that is exactly the problem I want to address: if you type:

	SOMETHING<U+FF0E>JP

For example, it will not be seen as a domain name in the .JP domain, even
though this was the intent (let's say also that JP can be in full-width
ASCII, which makes the U+FF0E very plausible). Just like typing:

	SOMETHING<U+3002>JP

won't. This is the exact same thing. So I think we need to handle it just
like U+3002 is handled.

YA