<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Jefsey, it is not up to you to specify how the IDNABIS working group does its work. Moreover, the working group has the option to consult with language experts and, in fact, is listening to the Arabic Language working group for input; it is also listening to the Korean language experts, the CJK JET group and others. It is unfair for you to characterize IDNABIS as purely engineering. We have the head of the Unicode consortium actively involve in the working and he has access to a significant range of experts.<div><br></div><div>Vint</div><div><br></div><div><br><div apple-content-edited="true"> <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; "><div><div><br class="Apple-interchange-newline">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> </div><br><div><div>On Mar 27, 2009, at 9:57 AM, JFC Morfin wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">2009/3/27 Roozbeh Pournader <span dir="ltr"><<a href="mailto:roozbeh@gmail.com">roozbeh@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> Let's face it: this thread is not about Tatweel. It's about the decision process in the group.<br> <font color="#888888"> Roozbeh</font></blockquote><div><br></div><div>Dear Roozbeh,</div><div>To be precise, the thread is about the area of responsibility of IETF through the decision process that must apply on a small question. IDNA is to support languages through the Internet. This group is competent about internet support. It is not about languages. </div> <div><br></div><div>- languages requires linguistics experts and MUST decide by consensus.</div><div>- internet technological support requires engineers and MAY decide by rough consensus.</div><div><br></div><div>This WG is established to support non-LDH in domain names. All it can say is either:</div> <div>- this codepoint is an exception which hurts the network stability, here is why, here is what we did to try to minimize the number of exceptions.<br></div><div>- the IDNA architecture does not permit to support the following linguistic requirements (such as French majuscules).</div> <div><br></div><div>But it cannot say: we engineers decide not to support this codepoint for linguistic reasons. The same linguists cannot say: we linguists decide that the DNS will support UTF8.</div><div><br></div><div> <br></div><div>So, may be can we rephrase the questions as follows:</div><div><br></div><div>- Do you think that disallowing code points at protocol level is a vital necessity for the Internet Y/N ?<br></div><div>- Why ?</div> <div>- Is TATWEEL such a code point Y/N ?</div><div>- Why (not considering graphic confusability which is outside the scope of this WG)?</div><div>- if you answered Yes to one of the question above, this means that you consider the IETF as a multilinguist authority. </div> <div><br></div><div>Rough consensus on this non-linguistic IETF question will decide of the technical infeasibility of the TATWEEL support.<br></div><div>Would this be acceptable to you?</div><div>jfc</div><div><br></div> <div><br></div><div><br></div></div> _______________________________________________<br>Idna-update mailing list<br><a href="mailto:Idna-update@alvestrand.no">Idna-update@alvestrand.no</a><br>http://www.alvestrand.no/mailman/listinfo/idna-update<br></blockquote></div><br></div></body></html>