<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">for the most part, the IDNA2008 specification does place a great deal of responsibility on<div>the registry but for some cases, it was considered important to bar particularly confusing</div><div>situations at the protocol level. This was debated substantially during the course of the</div><div>development of IDNA2008.</div><div><br></div><div><br></div><div><div><div>On Oct 13, 2009, at 4:15 AM, Abdulrahman I. ALGhadir wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; 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: 0px; "><div lang="EN-US" link="blue" vlink="purple"><div class="Section1"><div style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 11pt; font-family: Calibri, sans-serif; ">Hello,<o:p></o:p></div><div style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 11pt; font-family: Calibri, sans-serif; ">Well while I was reading draft-ietf-idnabis-bidi-06.txt I found this:<o:p></o:p></div><div style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><pre style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 10pt; font-family: 'Courier New'; ">“4.3. Strings with numbers<o:p></o:p></pre><pre style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 10pt; font-family: 'Courier New'; "><o:p> </o:p></pre><pre style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 10pt; font-family: 'Courier New'; "> By requiring that the first or last character of a string be category<o:p></o:p></pre><pre style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 10pt; font-family: 'Courier New'; "> R or AL, RFC 3454 prohibited a string containing right-to-left<o:p></o:p></pre><pre style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 10pt; font-family: 'Courier New'; "> characters from ending with a number.<o:p></o:p></pre><pre style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 10pt; font-family: 'Courier New'; "><o:p> </o:p></pre><pre style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 10pt; font-family: 'Courier New'; "> Consider the strings ALEF 5 (HEBREW LETTER ALEF + DIGIT FIVE) and 5<o:p></o:p></pre><pre style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 10pt; font-family: 'Courier New'; "> ALEF. Displayed in an LTR context, the first one will be displayed<o:p></o:p></pre><pre style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 10pt; font-family: 'Courier New'; "> from left to right as 5 ALEF (with the 5 being considered right-to-<o:p></o:p></pre><pre style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 10pt; font-family: 'Courier New'; "> left because of the leading ALEF), while 5 ALEF will be displayed in<o:p></o:p></pre><pre style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 10pt; font-family: 'Courier New'; "> exactly the same order (5 taking the direction from context).<o:p></o:p></pre><pre style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 10pt; font-family: 'Courier New'; "> Clearly, only one of those should be permitted as a registered label,<o:p></o:p></pre><pre style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 10pt; font-family: 'Courier New'; "> but barring them both seems unnecessary.”<o:p></o:p></pre><div style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 11pt; font-family: Calibri, sans-serif; ">Why permitting done on the protocol level ? shouldn’t this be done at registry level?<o:p></o:p></div><div style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 11pt; font-family: Calibri, sans-serif; ">Ex. If someone wants to register 3COM (COM is a RTL word) registry will register 3COM for him/her and will lock COM3.<o:p></o:p></div><div style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 11pt; font-family: Calibri, sans-serif; ">At least this will give users the choice for picking not forcing them on one type?<o:p></o:p></div><div style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 11pt; font-family: Calibri, sans-serif; ">Thank you,<o:p></o:p></div><div style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div></div><pre style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 10pt; font-family: 'Courier New'; ">-----------------------------------------------------------------------------------
Disclaimer:
This message and its attachment, if any, are confidential and may contain legally
privileged information. If you are not the intended recipient, please contact the
sender immediately and delete this message and its attachment, if any, from your
system. You should not copy this message or disclose its contents to any other
person or use it for any purpose. Statements and opinions expressed in this e-mail
are those of the sender, and do not necessarily reflect those of the Communications
and Information Technology Commission (CITC). CITC accepts no liability for damage
caused by this email.
</pre>_______________________________________________<br>Idna-update mailing list<br><a href="mailto:Idna-update@alvestrand.no" style="color: blue; text-decoration: underline; ">Idna-update@alvestrand.no</a><br><a href="http://www.alvestrand.no/mailman/listinfo/idna-update" style="color: blue; text-decoration: underline; ">http://www.alvestrand.no/mailman/listinfo/idna-update</a><br></div></span></blockquote></div><br></div></body></html>