Unregistered code points and new prefixes (was: Re: sharp s(Eszett))

Cary Karp ck at nic.museum
Sun Mar 9 10:47:11 CET 2008

Quoting Erik:

> Martin said it the way I would have, roughly, "Who are you trying to
> protect, and from what?" It does not make much sense to disallow the
> lookup of an invalid A-label by an IDNA-aware application, let alone
> an IDNA-unaware application.
> However, if the consensus of the group is to disallow invalid A-label
> lookups, then I will reluctantly go along with it. It does make
> migration to future versions of Unicode a bit harder than it needs to
> be. Michel said it quite well too, something like "I'm not very
> excited about it."

The gTLD registries are forbidden by the terms of their contracts with
ICANN from accepting the registration of any labels with hyphens in the
third and fourth positions unless an explicit further agreement has
been signed in which the registry binds itself to follow the ICANN IDN


which do not permit prefixing random strings with xn--.

The ccTLD registries are not subject to the same across the board
constraint. The resulting user confusion is significant and the
retroactive imposition of remedial policies is not a viable means for
addressing this problem (nor is simply dismissing or tolerating it).

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.alvestrand.no/pipermail/idna-update/attachments/20080309/3ba6fcec/signature.bin

More information about the Idna-update mailing list