Paul,<br>I am afraid we all have difficulties with Elisabeth's elliptic mind, because she don't use to consider the technical/individual details (there can be many of them), but the implied architectural/strategic whole. I think I would support your proposition, but I am not sure I understand "A pair of A-labels MUST be compared using a case-preserving comparison.". Moreover, the way you phrase it seems to integrate the case-preservation in the protocol, i.e. in the ACE and not to keep it as a part of its use? <br>
<br>The rule proposed by Andrew Sullivan seems quite systematic and clear?<br><br>1. The encoding of A-label1 according to [RFC3492] results in U-label1.<br>2. The decoding of U-label2 according to [RFC3492] results in A-label2.<br>
3. A-label1 is equivalent to A-label2 according to DNS matching rules for labels.<br>4. U-label1 is bistring equivalent to U-label2.<br><br>We felt it addressed our point "References to the lower/uppercase image can be understood by DNS
old-timers, but is confusing to newcomers, as it does not reflect the
same functionality and because U-label/A-label lower/uppercase
treatment is not the same." since everyone knows that punycode is case preserving. <br><br>Best<br>Portzamparc<br>an IETF user<br><br><br><div class="gmail_quote">2009/8/31 Paul Hoffman <span dir="ltr"><<a href="mailto:phoffman@imc.org">phoffman@imc.org</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;"><div class="im">At 12:35 AM +0200 8/31/09, Elisabeth Blanconil wrote:<br>
>"(i) A change to the "punycode" algorithm or to the ACE approach to<br>
>encoding names in the DNS."<br>
>-> this is now what you propose.<br>
<br>
</div>Wrong: no one other than you has proposed any change to either.<br>
<div class="im"><br>
>"(ii) A change to the ACE prefix from "xn--"<br>
>-> you now propose a change from "xn--" to "$$--"<br>
<br>
</div>You have both misattributed Vint's statement to Wil and completely misunderstood Vint's statement. The string "$$" does not appear in any of the WG documents.<br>
<div class="im"><br>
>"(iii) A change to the basic approach taken in the design team<br>
>documents (Namely: independence from Unicode version and elimination<br>
>of character mapping in the protocol)"<br>
>-> Vint already proposed the change of the last sub-point.<br>
<br>
</div>Correct. That is a proposed charter change that is being considered by the IETF. So far, we have heard no objections.<br>
<div><div></div><div class="h5">_______________________________________________<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>