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.<br><br>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"?<br>
<br>Doncha love slippery slopes :)<br><br>Lisa<br><br><div class="gmail_quote">On Wed, Dec 2, 2009 at 11:26 AM, Andrew Sullivan <span dir="ltr"><<a href="mailto:ajs@shinkuro.com">ajs@shinkuro.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On Wed, Dec 02, 2009 at 07:17:41PM +0000, Shawn Steele wrote:<br>
<br>
> So if that's how the problem will be solved, is there a better way<br>
> to state it? Or should bundling in these cases just be a BCP?<br>
<br>
</div>We couldn't offer anything other than BCP or even Informational,<br>
because zone operators are quite correct in asserting that the<br>
contents of their zone are entirely within the purview of local<br>
policy: this is not something one can require as a matter of protocol.<br>
<br>
A<br>
<font color="#888888"><br>
--<br>
Andrew Sullivan<br>
<a href="mailto:ajs@shinkuro.com">ajs@shinkuro.com</a><br>
Shinkuro, Inc.<br>
_______________________________________________<br>
Idna-update mailing list<br>
<a href="mailto:Idna-update@alvestrand.no">Idna-update@alvestrand.no</a><br>
<a href="http://www.alvestrand.no/mailman/listinfo/idna-update" target="_blank">http://www.alvestrand.no/mailman/listinfo/idna-update</a><br>
</font></blockquote></div><br>