<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
this call got only a few responses - mostly positive but with some observations in general that will need to be resolved in Minneapolis.<div><br></div><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: 12.0px Helvetica">YES: 4</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: 12.0px Helvetica">NO: 1</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: 12.0px Helvetica">however, see comments below of a more general nature.</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: 12.0px Helvetica">CONSENSUS STATEMENT:</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: 12.0px Helvetica">(6) Conversion, validation, and related issues.</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: 12.0px Helvetica">(6.a) The discussion of Unicode conversions in Section 5.2 of</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: 12.0px Helvetica">Protocol-05 is satisfactory. (P.7)</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: 12.0px Helvetica">(6.b) The discussion of A-label validation in Section 5.4 of</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: 12.0px Helvetica">Protocol is satisfactory, even though it leaves considerable</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: 12.0px Helvetica">flexibility to implementation decisions. (P.8)</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: 12.0px Helvetica">(6.c) Labels are not permitted to start with combining marks.</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: 12.0px Helvetica">(P.13)</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: 12.0px Helvetica">Comments:</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: 12.0px Helvetica">1. Section 4.2 of Protocol could be interpreted as only requiring Unicode Strings to be in NFC *if* they resulted from conversion from a legacy character encoding, rather than requiring it also of Unicode strings that did not result from such an encoding. The text needs to be fixed so that it is very clear that the NFC requirement is also true of strings that did not require conversion, as is the intent. I don't think this part is controversial -- it just makes it clearer and more consistent with 5.5.</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: 12.0px Helvetica">2. In terms of validation (the subject of this tranche), the second paragraph of 4.2 and the section 5.3 open up an unpleasant interoperability and security hole, since it places no limits on the mappings that can be applied to forbidden characters.</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: 12.0px Helvetica">Take the following 3 strings:</font></div> <ol> <li style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" color="#0018ea" style="font: 12.0px Helvetica; color: #0018ea"><a href="HTTP://SCHAFFER.DE/"><u>HTTP://SCHAFFER.DE</u><u></u></a></font></li> <li style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" color="#0018ea" style="font: 12.0px Helvetica; color: #0018ea"><a href="HTTP://xn--schffer-7wa.DE/"><u>HTTP://SCHÄFFER.DE</u><u></u></a></font></li> <li style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" color="#0018ea" style="font: 12.0px Helvetica; color: #0018ea"><a href="HTTP://xn--schffer-oxa.DE/"><u>HTTP://SCHÆFFER.DE</u><u></u></a></font></li> </ol><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: 12.0px Helvetica">This section allows any implementation to map *any* of these to *any* of the following:</font></div> <ol> <li style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" color="#0018ea" style="font: 12.0px Helvetica; color: #0018ea"><a href="http://schaeffer.de/"><u>http://schaeffer.de</u><u></u></a></font></li> <li style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" color="#0018ea" style="font: 12.0px Helvetica; color: #0018ea"><a href="http://xn--schffer-7wa.de/"><u>http://schäffer.de</u><u></u></a></font></li> <li style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" color="#0018ea" style="font: 12.0px Helvetica; color: #0018ea"><a href="http://schaffer.de/"><u>http://schaffer.de</u><u></u></a></font></li> </ol><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: 12.0px Helvetica">That is, one implementation could map #2 to #3, while another implementation could map #2 to #1. Or, for that matter, many other variants. It allows Y</font><font face="Arial" size="3" style="font: 12.0px Arial">ENİ<a href="http://KAPI.TR/"><font color="#0018ea" style="color: #0018ea"><u>KAPI.TR</u></font></a> to be mapped to any of yenikap<a href="http://xn--cfa.tr/"><font color="#0018ea" style="color: #0018ea"><u>ı.tr</u></font></a>, yenı<a href="http://kapi.tr/"><font color="#0018ea" style="color: #0018ea"><u>kapi.tr</u></font></a>, or other dotted vs dotless i variants. As a matter of fact, a conformant implementation could m</font><font face="Arial" size="4" style="font: 13.0px Arial">ap <a href="http://xn--h1acbxfam.RU/"><font color="#0018ea" style="color: #0018ea"><u>РУССКИЙ.RU</u></font></a> to <a href="http://sarapalin.ru/"><font color="#0018ea" style="color: #0018ea"><u>sarapalin.ru</u></font></a>, since no limits are placed on the kinds of mappings that can be done.</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 13px/normal Arial; min-height: 15px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Arial" size="4" style="font: 13.0px Arial">============</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: 12.0px Helvetica">Strictly speaking I am fine with the 3 questions asked (6.a, 6.b and 6.c). I share some of the issues mentioned by Mark, but could live with the current text. So, if this is strictly the question, this would be a YES.</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: 12.0px Helvetica">If the consensus call also concerns 5.3 "Character Changes in Preprocessing or the User Interface", then I have a more serious issue that would require a fix imo (thus a NO position). At this point clause 5.3 contains a 'MUST NOT' declaration in its 3rd paragraph while saying in its 4th paragraph "This step is not standardized as part of IDNA, and is not further specified here". I see this as contradictory, because I don't see how you can impose a requirement on a step that you are explicitly not 'specifying'. In other words, the 'MUST NOT' statement must be removed and replaced by a statement saying that the pre-processing should not (lower case intended) map PROTOCOL-VALID characters. Again it is up to the pre-processing spec to mandate that, not the protocol spec.</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; min-height: 14px; "><br></div><br><div> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div><div>NOTE NEW BUSINESS ADDRESS AND PHONE</div><div>Vint Cerf</div><div>Google</div><div>1818 Library Street, Suite 400</div><div>Reston, VA 20190</div><div>202-370-5637</div><div><a href="mailto:vint@google.com">vint@google.com</a></div><div><br></div></div></span><br class="Apple-interchange-newline"></span><br class="Apple-interchange-newline"></span></span></span> </div><br></div></body></html>