<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>Hello,<o:p></o:p></p>
<p class=MsoNormal>Well while I was reading draft-ietf-idnabis-bidi-06.txt I found
this:<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<pre>“4.3. Strings with numbers<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> By requiring that the first or last character of a string be category<o:p></o:p></pre><pre> R or AL, RFC 3454 prohibited a string containing right-to-left<o:p></o:p></pre><pre> characters from ending with a number.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> Consider the strings ALEF 5 (HEBREW LETTER ALEF + DIGIT FIVE) and 5<o:p></o:p></pre><pre> ALEF. Displayed in an LTR context, the first one will be displayed<o:p></o:p></pre><pre> from left to right as 5 ALEF (with the 5 being considered right-to-<o:p></o:p></pre><pre> left because of the leading ALEF), while 5 ALEF will be displayed in<o:p></o:p></pre><pre> exactly the same order (5 taking the direction from context).<o:p></o:p></pre><pre> Clearly, only one of those should be permitted as a registered label,<o:p></o:p></pre><pre> but barring them both seems unnecessary.”<o:p></o:p></pre>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Why permitting done on the protocol level ? shouldn’t
this be done at registry level?<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>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></p>
<p class=MsoNormal>At least this will give users the choice for picking not
forcing them on one type?<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Thank you,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<pre>
-----------------------------------------------------------------------------------
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></body>
</html>