Dear John,<br>there is seemingly a fundamental misunderstanding between multilinguists and you: we do _not_ care about natural languages. We are only interested in a complete support of Unicode that you did remove when lowercasing punycode entries, without providing a mechanism to restore the Unicode information on an end to end basis. <br>
<br>IDNA is now entropic, it was not before. This is not something we can live with. <br><br><div class="gmail_quote">2009/9/17 John C Klensin <span dir="ltr"><<a href="mailto:klensin@jck.com">klensin@jck.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The reality is that Jean-Michel's idea of appropriating a few<br>
DISALLOWED or contextually-prohibited Unicode characters</blockquote><div><br>Using DISALLOWED makes the IDNAPLUS more robust, if the IETF does not change their mind. Using UNASSIGNED is chancy if Unicode does not want to cooperate. Using contextually-prohibibited Unicode points looks more like a hack and plainly shows that IETF and Unicode not only did not care about the users demands, but opposed them. This is why I consider that this point is not off context.<br>
<br> But, unless someone comes up with a<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
way to look at, e.g.,<br>
<a href="http://p33.a22.example.net" target="_blank">p33.a22.example.net</a><br>
and know, definitively, whether the first two labels are<br>
"English", "French", "German", etc., it just isn't workable in<br>
practice.<br></blockquote><div><br>Who cares? <br><br>What is needed along with the Internet RFC 1958 end to end rule is that if <a href="http://p33.a22.example.net">p33.a22.example.net</a> and <a href="http://P33.A22.example.net">P33.A22.example.net</a> the receiving hosts receives the respectively as <a href="http://p33.a22.example.net">p33.a22.example.net</a> and <a href="http://P33.A22.example.net">P33.A22.example.net</a> (as they currently do) and can locally discrimiate, or better they can be resolved as <a href="http://p33.a22.example.net">p33.a22.example.net</a> and as <a href="http://xn--33-abc.xn--22.bcd.example.net">xn--33-abc.xn--22.bcd.example.net</a> because before lowercasing the entries punycode will change <a href="http://P33.a22.example.net">P33.a22.example.net</a> in ?p33.?<a href="http://a22.example.net">a22.example.net</a>.<br>
<br></div></div>Best.<br>Portzamparc<br>