<div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div style="word-wrap:break-word"><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 Call Tranche 8 (character adjustments)</font></div></div></blockquote><div><br></div><div>NO. </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word"><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></blockquote><div>
<br></div><div>A YES vote would represent a significant security problem, and slow the development of IDNA2008 significantly. There are two distinct issues wrapped up in this tranche.</div><div><br></div><div><br></div><div>
1. As for the conjoining Hangul characters, these are used in representing non-modern Hangul characters. The committee has had a long-standing consensus for *not* going character by character through each script to determine which are the modern-use characters and which are not. We do not need to reopen this issue.</div>
<div><br></div><div>If this change is made, then that would force us to rethink that policy, potentially bogging us down in protracted analyses of the different scripts to exclude non-modern use characters, such as </div>
<div><span class="Apple-style-span" style="font-family: Times; "><code><a target="c" href="http://unicode.org/cldr/utility/character.jsp?a=01BF"><span class="Apple-style-span" style="font-size: small;">U+01BF</span></a></code><span class="Apple-style-span" style="font-size: small;"> ( ƿ ) LATIN LETTER WYNN<br>
</span><code><a target="c" href="http://unicode.org/cldr/utility/character.jsp?a=16B9"><span class="Apple-style-span" style="font-size: small;">U+16B9</span></a></code><span class="Apple-style-span" style="font-size: small;"> ( ᚹ ) RUNIC LETTER WUNJO WYNN W</span></span><span class="Apple-style-span" style="font-size: small;"><br>
</span></div>and many, many others.</div><div class="gmail_quote"><br><div><br></div><div>2. While the desire for ß and ς characters is understandable, there are problems with compatibility. Until they are upgraded, which will require some period of time, implementations will be supporting IDNA2003 and not IDNA2008. And for compatibility, for the foreseeable future, even implementations that support IDNA2008 will need to also support IDNA2003. </div>
<div><br></div><div>In most cases the differences between these are tractable, for companies like my own. URL X may be valid in IDNA2003 and not IDNA2008 or vice versa, but it never goes to two different locations. These two characters would break that. URL X could go to two *different* locations, depending which standard is being supported.</div>
<div><br></div>If I send someone <span class="Apple-style-span" style="font-family: -webkit-sans-serif; line-height: 19px; "><a href="http://grosse.com">große.com</a> in an email, then depending on what tools the user uses to read that email, it could end up at <a href="http://grosse.com">grosse.com</a> (a legitimate site) or </span><span class="Apple-style-span" style="font-family: -webkit-sans-serif; line-height: 19px; "><a href="http://grosse.com">große.com</a> (a spoof site). (Or, of course, <a href="http://grosse.com">große.com</a> could be the legitimate site and <a href="http://grosse.com">grosse.com</a> the spoof site.) This represents a significant security problem.</span></div>
<div class="gmail_quote"><span class="Apple-style-span" style="font-family: -webkit-sans-serif; line-height: 19px;"><br></span></div><div class="gmail_quote"><span class="Apple-style-span" style="font-family: -webkit-sans-serif; line-height: 19px;">Sigma is fundamentally a presentation issue: it should be displayed as <span class="Apple-style-span" style="font-family: arial; line-height: normal; ">ς if it is final. An alternative approach would be to add a SHOULD that it be so displayed.</span></span></div>
<div class="gmail_quote"><br></div><div class="gmail_quote">Eszett is slightly trickier. Yet its use in German orthography is not fundamentally required, as evidenced by the fact that it is not used in High German within in Switzerland, with no apparent ill effects on the population (see, for example, <a href="http://www.nzz.ch/">http://www.nzz.ch/</a>). And the recommended usage of ss vs ß changed substantially in the latest, not-wholly successful, German spelling reforms. As a percentage of words in use, especially when weighted by usage, the number that are distinguished by ss vs ß are vanishingly small.</div>
<div class="gmail_quote"><br></div><div class="gmail_quote">As stated in rationale-03:</div><div class="gmail_quote"><span class="Apple-style-span" style="font-family: Times; font-size: 16px; "><pre class="newpage" style="margin-top: 0px; margin-bottom: 0px; page-break-before: always; ">
<span class="Apple-style-span" style="font-size: small;"> They [DNS 'names']are typically derived from, or rooted in, some
language because most people think in language-based ways. But,
because they are mnemonics, they need not obey the orthographic
conventions of any language: it is not a requirement that it be
possible for them to be "words".
This distinction is important because the reasonable goal of an IDN
effort is not to be able to write the great Klingon (or language of
one's choice) novel in DNS labels but to be able to form a usefully
broad range of mnemonics in ways that are as natural as possible in a</span></pre><pre class="newpage" style="margin-top: 0px; margin-bottom: 0px; page-break-before: always; "><span class="Apple-style-span" style="font-size: small;"> very broad range of scripts.</span></pre>
</span></div><div class="gmail_quote"><br></div><div class="gmail_quote">Thus while recognizing the legitimate desire of people to use ß and ς characters, the cost in terms of compatibility and security does not appear to be worth the gain. It is thus too early for consensus on these.<br>
</div><div class="gmail_quote"><br></div><div class="gmail_quote">Instead, those wanting to make this change should propose some mechanisms for avoiding the security problems -- only if those can be overcome in a reasonable fashion could we incorporate this change, allowing ß and ς.</div>
<div class="gmail_quote"><br></div><div class="gmail_quote"><br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div style="word-wrap:break-word">
<div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px"><font face="Helvetica" size="3" style="font:12.0px Helvetica"></font></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;min-height:14px">
<br></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;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">Procedure:</font></div>
<div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;min-height:14px"><br></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;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">There are several decisions that the working group will need to make to confirm consensus. I will send a series of proposals over the next two weeks requesting YES or NO positions on each within a 4 day window. If NO is the response, a reason for that position needs to be stated. If there is a clear consensus based on responses or in the absence of a consensus against each proposal, it will be assumed that the proposal is acceptable to the Working Group.</font></div>
<div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;min-height:14px"><br></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;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">Parenthesized symbols (e.g., "(R.1)") after the items are references to the issues lists where additional explanations can be found, as sent by John Klensin as body parts "idnabis-protocol-issues-rev3" and "idnabis-rationale-issues-03" on a message titled 'Issues lists and the "preprocessing" topic' to the working group on 18 August (<a href="http://www.alvestrand.no/pipermail/idna-update/2008-August/002537.html" target="_blank">http://www.alvestrand.no/pipermail/idna-update/2008-August/002537.html</a>)</font></div>
<div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;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">This group needs to get its documents out; it is behind its original schedule. It should be noted that the IDN ccTLD and gTLD selection initiatives at ICANN have already begun so that delay may weaken the IETF's ability to assist in a rational deployment of IDNA.</font></div>
<div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;min-height:14px"><br></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;min-height:14px"><br></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;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">(8) Specific character adjustments for IDNA2003 -> IDNA2008</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">differences.</font></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;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">(8.a) Make Eszett Protocol-Valid per list discussion.</font></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;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">(8.b) Make Greek final sigma Protocol-Valid per list</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">discussion.</font></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;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">(8.c) Disallow conjoining Hangul jamo per recommendation from</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">KRNIC and others, permitting only precomposed syllables.</font></div>
<div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;min-height:14px"><br></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;min-height:14px"><br></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;min-height:14px">
<br></div><br><div> <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;text-align:auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><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;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><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;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><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;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><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;text-indent:0px;text-transform:none;white-space:normal;word-spacing: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" target="_blank">vint@google.com</a></div>
<div><br></div></div></span><br></span><br></span></span></span> </div><br></div><br>_______________________________________________<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>
<br></blockquote></div><br></div>