<br>This is why the metainformation concerning which mapping solution has been/is to be used is to be passed, so the resolution stays certain.<div><div>jfc<br><div><br></div><div><br><div class="gmail_quote">2009/2/20 Andrew Sullivan <span dir="ltr"><<a href="mailto:ajs@shinkuro.com">ajs@shinkuro.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="Ih2E3d"><br></div>
Today, if someone "registers" fußbal.tld, what gets registered is<br>
fussbal.tld. But if someone types fußbal.tld into a "resolution<br>
context", it _also_ gets mapped, so that they get to fussbal.tld.<br>
<br>
After IDNA2008, that will not be true, and the typer of fußbal.tld<br>
will either get no resolution at all, or else will go to some other<br>
site, or (if they're lucky) will be redirected to the same fussbal.tld<br>
site.<br>
<br>
That is certainly a change in behaviour, and one that opens the<br>
possibility for abuse in a way that the other examples didn't (because<br>
those other characters were not mapped to something else by protocol).</blockquote><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
<div class="Ih2E3d"><br>
A<br>
<br>
--<br>
Andrew Sullivan<br>
<a href="mailto:ajs@shinkuro.com">ajs@shinkuro.com</a><br>
Shinkuro, Inc.<br>
_______________________________________________<br>
</div><div><div></div><div class="Wj3C7c">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></div></div></div>