<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:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:1631595941;
mso-list-type:hybrid;
mso-list-template-ids:-717870586 -1842982136 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:12.0pt;
font-family:"Times New Roman","serif";
mso-fareast-font-family:"Times New Roman";
color:windowtext;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
-->
</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 style='word-wrap: break-word;
-webkit-nbsp-mode: space;-webkit-line-break: after-white-space'>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Well yes it is </span>confusing and yes there are other confusing
problems which the protocol simply assign it to registry what I say it is
unfair to prevent all domains <o:p></o:p></p>
<p class=MsoNormal>Which they start with digits to be as choice for user if
this problem moved to registry level a registry can simply do:<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='mso-list:Ignore'>1)<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]><span dir=LTR></span>Act same as what the protocol do
now (preventing all domains which start with digits).<span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='mso-list:Ignore'>2)<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]><span dir=LTR></span> <span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:black'>Register domains which start
with digits and lock the same domain which end with digits and the opposite.</span><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'>And any further problems which may result from using 2) can be
solved as the registry wants.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Plus if the protocol allowed this maybe bidi algorithm will
support domains who knows.<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>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thank you,<o:p></o:p></span></p>
<div>
<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"'> Vint Cerf
[mailto:vint@google.com] <br>
<b>Sent:</b> 13/Oct/2009 4:06 PM<br>
<b>To:</b> Abdulrahman I. ALGhadir<br>
<b>Cc:</b> idna-update@alvestrand.no<br>
<b>Subject:</b> Re: RTL labels and numbers?<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>for the most part, the IDNA2008 specification does place a
great deal of responsibility on<o:p></o:p></p>
<div>
<p class=MsoNormal>the registry but for some cases, it was considered important
to bar particularly confusing<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>situations at the protocol level. This was debated
substantially during the course of the<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>development of IDNA2008.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal>On Oct 13, 2009, at 4:15 AM, Abdulrahman I. ALGhadir wrote:<o:p></o:p></p>
</div>
<p class=MsoNormal><br>
<br>
<o:p></o:p></p>
<div>
<div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'>Hello,<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'>Well while I was reading draft-ietf-idnabis-bidi-06.txt I found
this:<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'> <o:p></o:p></span></p>
</div>
<pre><span style='color:black'>“4.3. Strings with numbers<o:p></o:p></span></pre><pre><span
style='color:black'> <o:p></o:p></span></pre><pre><span style='color:black'> By requiring that the first or last character of a string be category<o:p></o:p></span></pre><pre><span
style='color:black'> R or AL, RFC 3454 prohibited a string containing right-to-left<o:p></o:p></span></pre><pre><span
style='color:black'> characters from ending with a number.<o:p></o:p></span></pre><pre><span
style='color:black'> <o:p></o:p></span></pre><pre><span style='color:black'> Consider the strings ALEF 5 (HEBREW LETTER ALEF + DIGIT FIVE) and 5<o:p></o:p></span></pre><pre><span
style='color:black'> ALEF. Displayed in an LTR context, the first one will be displayed<o:p></o:p></span></pre><pre><span
style='color:black'> from left to right as 5 ALEF (with the 5 being considered right-to-<o:p></o:p></span></pre><pre><span
style='color:black'> left because of the leading ALEF), while 5 ALEF will be displayed in<o:p></o:p></span></pre><pre><span
style='color:black'> exactly the same order (5 taking the direction from context).<o:p></o:p></span></pre><pre><span
style='color:black'> Clearly, only one of those should be permitted as a registered label,<o:p></o:p></span></pre><pre><span
style='color:black'> but barring them both seems unnecessary.”<o:p></o:p></span></pre>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'>Why permitting done on the protocol level ? shouldn’t this
be done at registry level?<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'>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></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'>At least this will give users the choice for picking not forcing
them on one type?<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'>Thank you,<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'> <o:p></o:p></span></p>
</div>
</div>
<pre><span style='color:black'>-----------------------------------------------------------------------------------<o:p></o:p></span></pre><pre><span
style='color:black'>Disclaimer:<o:p></o:p></span></pre><pre><span
style='color:black'>This message and its attachment, if any, are confidential and may contain legally<o:p></o:p></span></pre><pre><span
style='color:black'>privileged information. If you are not the intended recipient, please contact the<o:p></o:p></span></pre><pre><span
style='color:black'>sender immediately and delete this message and its attachment, if any, from your<o:p></o:p></span></pre><pre><span
style='color:black'>system. You should not copy this message or disclose its contents to any other<o:p></o:p></span></pre><pre><span
style='color:black'>person or use it for any purpose. Statements and opinions expressed in this e-mail<o:p></o:p></span></pre><pre><span
style='color:black'>are those of the sender, and do not necessarily reflect those of the Communications<o:p></o:p></span></pre><pre><span
style='color:black'>and Information Technology Commission (CITC). CITC accepts no liability for damage<o:p></o:p></span></pre><pre><span
style='color:black'>caused by this email.<o:p></o:p></span></pre>
<p class=MsoNormal><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif";
color:black'>_______________________________________________<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">http://www.alvestrand.no/mailman/listinfo/idna-update</a><o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</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>