<br><br><div class="gmail_quote">On Mon, Aug 31, 2009 at 4:32 AM, John C Klensin <span dir="ltr"><<a href="mailto:klensin@jck.com">klensin@jck.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
<br>
--On Monday, August 31, 2009 4:22 AM +1000 Wil Tan <<a href="mailto:wil@cloudregistry.net" target="_blank">wil@cloudregistry.net</a>> wrote:<br>
<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
On Sat, Aug 29, 2009 at 5:17 PM, John C Klensin<br>
<<a href="mailto:klensin@jck.com" target="_blank">klensin@jck.com</a>> wrote:<br>
<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
--On Monday, August 24, 2009 23:24 -0400 Andrew Sullivan<br>
<<a href="mailto:ajs@shinkuro.com" target="_blank">ajs@shinkuro.com</a>> wrote:<br>
<br>
><br>
> In a previous comment (see<br>
> <a href="http://www.alvestrand.no/pipermail/idna-update/2009-July/00" target="_blank">http://www.alvestrand.no/pipermail/idna-update/2009-July/00</a><br></div>
> 497 0.html), I made a vague remark about something I find<div class="im"><br>
> worrisome in this text in §<a href="http://2.3.2.1" target="_blank">2.3.2.1</a>:<br>
> ...<br>
<br>
These changes, with Paul's suggested modifications, have been<br>
tentatively accepted and incorporated in the document. Anyone<br>
who objects should say so quickly.<br>
<br>
<br>
</div></blockquote><div class="im">
I posted a comment related to the definition of A-label some<br>
time ago, but the thread was digressed:<br>
<a href="http://www.alvestrand.no/pipermail/idna-update/2009-June/00455" target="_blank">http://www.alvestrand.no/pipermail/idna-update/2009-June/00455</a><br>
8.html<br>
<br>
The issue is with case variants of A-labels. By DNS rules, as<br>
mentioned in several places in the idnabis-defs draft,<br>
A-labels are to be compared in a case independent manner.<br>
However, if certain characters in an A-label have been<br>
uppercased, the Punycode decoding algorithm (due to its<br>
mixed-case annotation feature) may produce invalid U-label<br>
because the ASCII characters will be in capital letter form.<br>
</div></blockquote>
<br>
Suggested fix? Do I need to put a "force lower case for undecorated Latin (ASCII) characters" into the conversation step from A-labels to U-labels?<br>
<br>
</blockquote><div><br></div><div>Essentially yes, I'm suggesting that as a fix but am not certain how to go about updating the documents to reflect it.</div><div><br></div><div>One way would be to update -protocol-14, section 5.3, A-label Input section to add the lowercasing step prior to using the Punycode decoding algorithm. The section on symmetry constraint (-defs-10, section 2.3.2.1) should also have similar wordings.</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Suggested wording would be appreciated if so.<br><font color="#888888">
<br>
</font></blockquote><div> </div><div><div>If the WG agrees that this is a valid issue, and that it is the right way to fix it, I will work on wording.</div><div><br></div><div>=wil</div></div></div>