<div class="gmail_quote">2010/10/24 Mark Davis ☕ <span dir="ltr"><<a href="mailto:mark@macchiato.com">mark@macchiato.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"><div><font face="georgia,serif">> </font><span style="font-family: arial,sans-serif; font-size: 13px; border-collapse: collapse;">These A-label having been initially registered as IDNA2003, IDNA2008 or xn-ascii does not make any difference.</span></div>
<div><font face="georgia,serif"><br></font></div></div><div><span style="font-family: arial,sans-serif; font-size: 13px; border-collapse: collapse;"></span><font face="georgia,serif">There is a bit of a problem in terminology. I used the term "punycode label" to include labels of the form "xn--...", where the ... is valid Punycode representations (in ASCII) of a Unicode string (with non-ASCII characters).</font></div>
</blockquote><div><br>This seems to be an IDNA2003 and IDNA2008 well acceptable definition?<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><font face="georgia,serif">If we are speaking precisely, the</font><span style="font-family: georgia,serif;"> term "A-Label" is defined in IDNA2008, and is more restrictive. It does not include all the punycode labels that are valid in IDNA2003. So "<a href="http://xn--1-wpn.blogspot.com/" target="_blank">http://xn--1-wpn.blogspot.com/</a>" (= http://€<a href="http://1.blogspot.com/" target="_blank">1.blogspot.com/</a>) does not have an A-Label in it, but is a punycode label, and is valid in IDNA2003.</span></div>
</blockquote><div> </div><div>This is also my understanding. But I understand it is only more restrictive because the IDNA2008 conversion terms are more restrictive.<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><span style="font-family: georgia,serif;"><br></span></div><div><font face="georgia, serif">Because A-Label is defined in IDNA2008 (not in IDNA2003), we should follow the IDNA2008 definition precisely. Otherwise communication becomes difficult -- two people think they are in agreement about a point involving A-Labels, when they mean different things, and are thus not in agreement.</font></div>
</blockquote><div><br>Agreement. IDNA2003 stated (RFC 3490) : "While all ACE labels begin with the ACE prefix, not all labels beginning with the ACE prefix are necessarily ACE labels." How should I call non-ACE/non-A-label "xn--" ASCII domain names? Such domain names exist and therefore can be used by Cookies. <br>
<br>However, the problem I raised was that for the network DNS A-labels are the reference, while U-labels are the IUser's reference, and that no concept has been suggested (*) (on the IETF side) and no mechanism has been defined (*) on the IUse Architecture side to make sure they strictly correspond throughout applications. (*): I am aware of except the IDNApplication concept (i.e. to centralise punycoding on each machine/network) and the ML-DNS JFC is working on a running test.<br>
<br>Frankly, my understanding is that IDNA2008 is a vertical begining and real IETF horizontal work is to come, as per <a href="http://www.iab.org/documents/iabmins/iabmins.2010-04-07.txt">http://www.iab.org/documents/iabmins/iabmins.2010-04-07.txt</a> and their <a href="http://www.iab.org/appeals/2010-08-20-morfin-response.pdf">http://www.iab.org/appeals/2010-08-20-morfin-response.pdf</a> committed reponse .<br>
<br>Portzamparc<br><br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><font face="georgia, serif"><br></font></div><div><div><div><div class="im"><font face="georgia, serif">Mark<br><br><i>— Il meglio è l’inimico del bene —</i></font><br>
<br><br></div><div><div></div><div class="h5"><div class="gmail_quote">On Sat, Oct 23, 2010 at 19:05, jean-michel bernier de portzamparc <span dir="ltr"><<a href="mailto:jmabdp@gmail.com" target="_blank">jmabdp@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="gmail_quote">2010/10/24 Mark Davis ☕ <span dir="ltr"><<a href="mailto:mark@macchiato.com" target="_blank">mark@macchiato.com</a>></span><div><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<font face="georgia,serif">I'm in agreement about the usefulness of storing the punycode form. As to what you would like to see, Patrik, I'm in agreement there as well; that the goal is IDNA2008. And I think we'll get there eventually, when the major registries disallow the registrations of non-IDNA2008 names. </font></blockquote>
</div><div><br>Dear Mark,<br><br>whatever the policy of the "registries", their transitions, their interest in Unicode, their commercial, cultural or political strategies, etc. they only use A-labels as far as the Internet and the Internet DNS are concerned (them having "xn--" headers or not - remember that until IDNA2003 every cooky was A-label only). These A-label having been initially registered as IDNA2003, IDNA2008 or xn-ascii does not make any difference. Cookies are not interested in the origin of the domain name, but in the value of the domain names. Every IDN has one and only one lowercase A-label value. And this value is here to stay.<br>
<br>Considering anything else for cookies, is to reintroduce the confusion that IDNA2008 clarified. <br>Remember the sensible ".su" position: they will not register U-labels, but only A-label whatever the reverse punycodability.<br>
<br>The problem for implementers is not there. The problem is to obtain a local user authoritative A-label, something the AD was told not to ask but IAB will have to document.<br><br>Portzamparc<br></div></div><div style="display: inline;">
</div>
</blockquote></div><br></div></div></div></div></div>
</blockquote></div><br><div style="visibility: hidden; display: inline;" id="avg_ls_inline_popup"></div><style type="text/css">#avg_ls_inline_popup { position:absolute; z-index:9999; padding: 0px 0px; margin-left: 0px; margin-top: 0px; width: 240px; overflow: hidden; word-wrap: break-word; color: black; font-size: 10px; text-align: left; line-height: 13px;}</style>