> If the set of characters contains pairs of homographic<br>
> characters, the policy must specify a method to prevent two homographic<br>
> domains being registered to different entities.<br><br>Because that policy does not actually appear to be feasible. How does TLD XX determine whether 2 strings are homographs or not? Is it up to them? Is there is some specification they need to reference? Otherwise, how would anyone know whether such a statement were true or not? Or does Firefox take the TLD's word for it? If you try to register ball.XX and ba11.XX is one of them blocked (for the "Firefox-blessed" TLD XX)?<br>
<br>Mark<br><br><div class="gmail_quote">On Sun, Mar 9, 2008 at 3:22 PM, Gervase Markham <<a href="mailto:gerv@mozilla.org">gerv@mozilla.org</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;">
<div class="Ih2E3d">Stephane Bortzmeyer wrote:<br>
> I thought that such decisions were the responsability of the TLD. Now,<br>
> do you mean that a browser's vendor decision (and a bad one)<br>
> constrains TLD policy decisions?<br>
<br>
</div>TLDs have complete freedom about how they implement IDN. Firefox and<br>
other browsers have complete freedom about how and whether they present<br>
fully-rendered IDN domains to the user.<br>
<div class="Ih2E3d"><br>
> Side note: how many TLD have a consistent policy about homographs? Not<br>
> just an anti-Unicode policy but a policy to prevent the registration<br>
> of bankofthewest.example and bankofthevvest.example to different<br>
> entities?<br>
<br>
</div>I believe policy in that specific area varies. However, more generally,<br>
there are now 30+ TLDs who have policies which comply with our IDN<br>
guidelines and so have been whitelisted:<br>
<a href="http://www.mozilla.org/projects/security/tld-idn-policy-list.html" target="_blank">http://www.mozilla.org/projects/security/tld-idn-policy-list.html</a><br>
That page also has a rather good summary of why we do things this way.<br>
<br>
The guidelines are not exactly complex; I can quote them in their entirety:<br>
<br>
> In order for us to display IDNs in a particular TLD, that registry<br>
> concerned must have and keep a published policy stating which characters<br>
> are permitted. If the set of characters contains pairs of homographic<br>
> characters, the policy must specify a method to prevent two homographic<br>
> domains being registered to different entities.<br>
<br>
I would have thought any TLD which is issuing IDNs without going even<br>
that far would be doing its customers a great disservice.<br>
<br>
Gerv<br>
<div><div></div><div class="Wj3C7c">_______________________________________________<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