<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)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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>well I am with you in this part there will be problems in
some cases but this isn't weird because as we know that <br>
the protocol is using the current bidi algorithm which it doesn't identify
domains and render them as they. so this<br>
kind of problems are excepted to happen. and I still think leaving this
problem to registry might give us a better<br>
chance in solving it in future rather than just disallowing it in the protocol
level.<br>
<br>
and the draft did mention this:<br>
<br>
"Another set of issues concerns the proper display of IDNs with a<br>
mixture of LTR and RTL labels, or only RTL labels.<br>
<br>
It is unrealistic to expect that applications will display domain<br>
names using embedded formatting codes between their labels (for
one<br>
thing, no reliable algorithms for identifying domain names in
running<br>
text exist); thus, the display order will be determined by the
BIDI<br>
algorithm. Thus, a sequence (in network order) of R1.R2.ltr
will be<br>
displayed in the order 2R.1R.ltr in an LTR context, which might<br>
surprise someone expecting to see labels displayed in hierarchical<br>
order. People used to working with text that mixes LTR and
RTL<br>
strings might not be so surprised by this. Again, this memo
does not<br>
attempt to suggest a solution to this problem."<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Thank you,<span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Matitiahu Allouche
[mailto:matial@il.ibm.com] <br>
<b>Sent:</b> 13/Oct/2009 3:29 PM<br>
<b>To:</b> Abdulrahman I. ALGhadir<br>
<b>Cc:</b> idna-update@alvestrand.no; idna-update-bounces@alvestrand.no<br>
<b>Subject:</b> Re: RTL labels and numbers?<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Abdulrahman I.
ALGhadir wrote:</span> <br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><quote></span>
<br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Why
permitting done on the protocol level ? shouldn’t this be done at registry
level?</span> <br>
<span style='font-size:10.0pt;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.</span> <br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>At least this
will give users the choice for picking not forcing them on one type?</span> <br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><end of
quote></span> <br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>There is
another problem with "3COM" (where COM are RTL letters): if preceded
by a LTR label and displayed in an RTL context, the result will be very
confusing. For instance, the string (in network order) </span><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>
support.3COM.net</span> <br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>will be
displayed as</span> <br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>
net.MOCsupport.3<br>
<br>
<br>
Shalom (Regards), Mati<br>
Bidi Architect<br>
Globalization Center Of Competency -
Bidirectional Scripts<br>
IBM Israel<br>
Phone: +972 2 5888802 Fax: +972
2 5870333 Mobile: +972 52 2554160<br>
</span><br>
<br>
<o:p></o:p></p>
<table class=MsoNormalTable border=0 cellpadding=0 width="100%"
style='width:100.0%'>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:#5F5F5F'>From:</span> <o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>"Abdulrahman
I. ALGhadir" <aghadir@citc.gov.sa></span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:#5F5F5F'>To:</span> <o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'><idna-update@alvestrand.no></span>
<o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:#5F5F5F'>Date:</span> <o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>13/10/2009
10:16</span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:#5F5F5F'>Subject:</span> <o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>RTL
labels and numbers?</span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:#5F5F5F'>Sent by:</span> <o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>idna-update-bounces@alvestrand.no</span><o:p></o:p></p>
</td>
</tr>
</table>
<p class=MsoNormal><o:p> </o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" noshade style='color:#9D9DA1' align=center>
</div>
<p class=MsoNormal><br>
<br>
<br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Hello,</span>
<br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Well while I
was reading draft-ietf-idnabis-bidi-06.txt I found this:</span> <br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> </span>
<br>
<span style='font-size:10.0pt;font-family:"Courier New"'>“4.3. Strings
with numbers</span> <br>
<span style='font-size:10.0pt;font-family:"Courier New"'> </span> <br>
<span style='font-size:10.0pt;font-family:"Courier New"'> By
requiring that the first or last character of a string be category</span> <br>
<span style='font-size:10.0pt;font-family:"Courier New"'> R or AL,
RFC 3454 prohibited a string containing right-to-left</span> <br>
<span style='font-size:10.0pt;font-family:"Courier New"'>
characters from ending with a number.</span> <br>
<span style='font-size:10.0pt;font-family:"Courier New"'> </span> <br>
<span style='font-size:10.0pt;font-family:"Courier New"'> Consider
the strings ALEF 5 (HEBREW LETTER ALEF + DIGIT FIVE) and 5</span> <br>
<span style='font-size:10.0pt;font-family:"Courier New"'> ALEF.
Displayed in an LTR context, the first one will be displayed</span> <br>
<span style='font-size:10.0pt;font-family:"Courier New"'> from left
to right as 5 ALEF (with the 5 being considered right-to-</span> <br>
<span style='font-size:10.0pt;font-family:"Courier New"'> left
because of the leading ALEF), while 5 ALEF will be displayed in</span> <br>
<span style='font-size:10.0pt;font-family:"Courier New"'> exactly
the same order (5 taking the direction from context).</span> <br>
<span style='font-size:10.0pt;font-family:"Courier New"'> Clearly,
only one of those should be permitted as a registered label,</span> <br>
<span style='font-size:10.0pt;font-family:"Courier New"'> but
barring them both seems unnecessary.”</span> <br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> </span>
<br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Why
permitting done on the protocol level ? shouldn’t this be done at registry
level?</span> <br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> </span>
<br>
<span style='font-size:10.0pt;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.</span> <br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>At least this
will give users the choice for picking not forcing them on one type?</span> <br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> </span>
<br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Thank you,</span>
<br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> </span>
<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>