I agree; I think changing the prefix would be a horrible mess. I'd rather not see that as a possibility in the charter.<br><br>Mark<br><br><div class="gmail_quote">On Thu, Mar 20, 2008 at 11:18 AM, Shawn Steele <<a href="mailto:Shawn.Steele@microsoft.com">Shawn.Steele@microsoft.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I think that changing the prefix would be a really bad idea:<br>
<br>
* Changing the domain name would break existing comparisons that rely on the punycode. (domain name xn--A wouldn't necessarily equal domain name xx--A)<br>
<br>
* names wouldn't match in the registry either. The browser would have to try the new prefix name, then if that failed, it'd have to try the xn-- name for back compat.<br>
<br>
* What happens when the xn-- and the new prefix names for the same machine/Unicode name point to different servers? This could happen either because the registrars messed up or they are on a subnet that didn't know better?<br>
<br>
* Developers would have to consider 2 versions for even simple applications.<br>
<br>
I think that these are much more serious that changing behavior for anything that is considered "bad" (for security) today. If a "bad" domain stops working we probably want it to stop working.<br>
<br>
Our intent is to replace the IDN resolution mechanism for IE/Windows/.Net with updated tables when they become available. We would oppose anything that causes us to have multiple revisions or complex code paths for edge cases.<br>
<font color="#888888"><br>
- Shawn<br>
</font><div><div></div><div class="Wj3C7c"><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>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Mark