Lisa Dusseault lisa.dusseault at gmail.com
Wed Dec 2 20:35:21 CET 2009

I don't see where that principle begins and ends.  If it were entirely true,
zone operators would be entirely free to register xn--garbage as a domain,
entirely free to register DISALLOWED characters.

Since it is in the purview of IDNA designers to make a character valid or
disallowed,  wouldn't also be in the purview of IDNA designers to say
something like "This character becomes valid on date 01/01/2020", right?  So
why wouldn't it be in the purview of IDNA designers to also say something
like "This character becomes fully valid on date 01/01/2020, but until then,
may be registered if it is bundled with another sequence"?

Doncha love slippery slopes :)


On Wed, Dec 2, 2009 at 11:26 AM, Andrew Sullivan <ajs at shinkuro.com> wrote:

> On Wed, Dec 02, 2009 at 07:17:41PM +0000, Shawn Steele wrote:
> > So if that's how the problem will be solved, is there a better way
> > to state it?  Or should bundling in these cases just be a BCP?
> We couldn't offer anything other than BCP or even Informational,
> because zone operators are quite correct in asserting that the
> contents of their zone are entirely within the purview of local
> policy: this is not something one can require as a matter of protocol.
> A
> --
> Andrew Sullivan
> ajs at shinkuro.com
> Shinkuro, Inc.
> _______________________________________________
> Idna-update mailing list
> Idna-update at alvestrand.no
> http://www.alvestrand.no/mailman/listinfo/idna-update
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.alvestrand.no/pipermail/idna-update/attachments/20091202/a2455c43/attachment-0001.htm 

More information about the Idna-update mailing list