<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=windows-1256">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:"Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:555317403;
mso-list-type:hybrid;
mso-list-template-ids:255496254 1208549391 1208549401 1208549403 1208549391 1208549401 1208549403 1208549391 1208549401 1208549403;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1
{mso-list-id:1426730547;
mso-list-template-ids:1256340050;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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-SG" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:JA">Dear All,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:JA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:JA">In drafting the explanation for “uniform” in Guideline 13 in the Additional Note II, we should consider another scenario not yet captured but needed in the uniform treatment of variants across the IDN
Tables. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:JA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:JA">Thus, I have suggested additional text in the Additional Note II (ii) in the updated version 2.9-redline attached.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:JA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:JA">As an explanation, consider the scenario:
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:JA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:JA">Suppose a registry creates two IDN Tables, one exclusively for Traditional Chinese and other exclusively for Simplified Chinese. If the additional text is not there the registry could potentially allocate
the TC and SC versions of labels to different registrants. With the proposed text, the variant code points will need to be reviewed for both SC and TC together so even with such IDN Tables, the variant labels for SC and TC will go to the same registrant.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:JA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:JA">The same case can occur in Arabic script. If we have Arabic Kaf (‘k’
</span><span lang="AR-SA" dir="RTL" style="font-family:"Arial",sans-serif;mso-fareast-language:JA">ß</span><span dir="LTR"></span><span style="mso-fareast-language:JA"><span dir="LTR"></span> U+0643) in Arabic language table and Persian Kaf (‘k’
</span><span lang="ER" dir="RTL" style="font-family:"Arial",sans-serif;mso-fareast-language:JA">˜</span><span dir="LTR"></span><span lang="ER" style="mso-fareast-language:JA"><span dir="LTR"></span>
</span><span style="mso-fareast-language:JA">U+06A9) in Persian language table, then the identical labels
</span><span lang="ER" dir="RTL" style="font-family:"Arial",sans-serif;mso-fareast-language:JA">˜ÊÇÈ</span><span dir="LTR"></span><span lang="ER" style="mso-fareast-language:JA"><span dir="LTR"></span>
</span><span lang="EN-US" style="mso-fareast-language:JA">and</span><span dir="RTL"></span><span lang="EN-US" dir="RTL" style="font-family:"Arial",sans-serif;mso-fareast-language:JA"><span dir="RTL"></span>
</span><span lang="ER" dir="RTL" style="font-family:"Arial",sans-serif;mso-fareast-language:JA">ßÊÇÈ
</span><span dir="LTR"></span><span style="mso-fareast-language:JA"><span dir="LTR"></span>(kitab – book) could be allocated
</span><span lang="EN-US" style="mso-fareast-language:JA">to different registrants. If these are harmonized to be uniform, as described, such cases will be prevented.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:JA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:JA">This case does not seem to be captured elsewhere in the guidelines. I think this was originally intended, but when we specified the definition of “uniform”, we did not capture this part.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:JA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:JA">Kindly see if this version 2.9 is agreeable to proceed (with any further edits suggested) or should we take version 2.8 further.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:JA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:JA">Regards,<br>
Sarmad<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:JA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:JA"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span lang="EN-US" style="mso-fareast-language:JA">From:</span></b><span lang="EN-US" style="mso-fareast-language:JA"> idngwg-bounces@icann.org [mailto:idngwg-bounces@icann.org]
<b>On Behalf Of </b>Sarmad Hussain<br>
<b>Sent:</b> Sunday, October 15, 2017 1:11 PM<br>
<b>To:</b> idngwg@icann.org<br>
<b>Subject:</b> [Idngwg] Update draft + PC2 call + ICANN 60 presentations<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Dear All,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you for the amazing work all of you have done in finalizing the Guidelines document!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As discussed, we will conduct a second public comment on this document.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Following the IDNGWG meeting on 12 October, please find attached the following:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo3">Call for second public comment (PC2)<o:p></o:p></li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo3">Updated draft of the guidelines (updated redline version + PC2 clean version)<o:p></o:p></li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo3">Updated ICANN 60 presentations (detailed for 90 min session on 29 Oct. + short for 7 minute update on 1 Nov.)<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">(corresponding PDF versions also attached on request)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have added only two specific questions at the top of the guidelines document: one on scope and other on value of X. Kindly confirm that these are Ok, and please share if you would like to add any additional specific questions?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As discussed, second public comment call and corresponding document will be sent in for publication on 18 October, so please share any
<i><span style="color:red">feedback before 0500 UTC 18 Oct</span></i><span style="color:red"> (please make changes directly in the documents)</span>. It will be useful to get your confirmation even if you do not have any suggested changes.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As usual, the recording of the call is available at the wiki page
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_display_IDN_IDN-2BImplementation-2BGuidelines&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=psZrPi04OpZy2zYuUYGSomCxurkdBugJeqIN31z4UUc&s=SRrRz2lBwei_6_lLDzFWZdrAv06f9FrzPDZr-kbBOqg&e=">
https://community.icann.org/display/IDN/IDN+Implementation+Guidelines[community.icann.org]</a> and the notes will also be available there soon.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards,<br>
Sarmad<o:p></o:p></p>
</div>
</body>
</html>