<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<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 name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 5 4 2 2 2 3 2 4;}
@font-face
{font-family:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:"Arial Unicode MS";
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:"\@Arial Unicode MS";
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:"MS PGothic";
panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
{font-family:"\@MS PGothic";
panose-1:2 11 6 0 7 2 5 8 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"MS PGothic",sans-serif;
color:black;
mso-fareast-language:JA;}
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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"MS PGothic",sans-serif;
mso-fareast-language:JA;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"MS Gothic";
color:black;
mso-fareast-language:JA;}
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:"MS PGothic",sans-serif;
color:black;
mso-fareast-language:JA;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;
mso-fareast-language:JA;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"MS PGothic",sans-serif;
color:black;
mso-fareast-language:JA;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle26
{mso-style-type:personal-reply;
font-family:"Arial Unicode MS",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:461462565;
mso-list-type:hybrid;
mso-list-template-ids:-928478698 737987050 960928754 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:18.0pt;
text-indent:-18.0pt;
mso-ansi-font-size:12.0pt;
mso-bidi-font-size:12.0pt;
color:windowtext;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-text:"\(%2\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:54.0pt;
text-indent:-18.0pt;
mso-ascii-font-family:"Times New Roman";
mso-fareast-font-family:Calibri;
mso-hansi-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:90.0pt;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:126.0pt;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:162.0pt;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:198.0pt;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:234.0pt;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:270.0pt;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:306.0pt;
text-indent:-9.0pt;}
@list l1
{mso-list-id:910850194;
mso-list-template-ids:2130992238;}
@list l1:level1
{mso-level-start-at:2;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l2
{mso-list-id:1023870005;
mso-list-template-ids:985297612;}
@list l3
{mso-list-id:1073435736;
mso-list-template-ids:-643941240;}
@list l4
{mso-list-id:1196770016;
mso-list-type:hybrid;
mso-list-template-ids:2119188920 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l4:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l4:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l4:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l4:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l4:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l4:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l4:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l4:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l4:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l5
{mso-list-id:2030909453;
mso-list-template-ids:-119606748;}
@list l5:level1
{mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l5:level2
{mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l5:level3
{mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l5:level4
{mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l5:level5
{mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l5:level6
{mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l5:level7
{mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l5:level8
{mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l5:level9
{mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
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 bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-CA style='font-size:11.0pt;font-family:"Arial Unicode MS",sans-serif;color:windowtext;mso-fareast-language:ZH-TW'>I think we should communicate to Yoshitaka what you have outlined, especially letting him know that we did take the suggestion into consideration. And get from him, with the explanation, whether he still has a concern with the existing language.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:11.0pt;font-family:"Arial Unicode MS",sans-serif;color:windowtext;mso-fareast-language:ZH-TW'>Edmon<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:11.0pt;font-family:"Arial Unicode MS",sans-serif;color:windowtext;mso-fareast-language:ZH-TW'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:11.0pt;font-family:"Arial Unicode MS",sans-serif;color:windowtext;mso-fareast-language:ZH-TW'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext'> Idngwg [mailto:idngwg-bounces@icann.org] <b>On Behalf Of </b>Sarmad Hussain<br><b>Sent:</b> Sunday, May 13, 2018 2:25 AM<br><b>To:</b> Kal Feher <icann@feherfamily.org>; idngwg@icann.org<br><b>Subject:</b> Re: [Idngwg] FW: [Ext] haven't received any response from you<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'>Dear All,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'>Kindly also note that Guideline 16 is part of the existing implemented “version 3.0” of the guidelines. The existing guideline says:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:11.25pt;margin-left:51.0pt;text-indent:-18.0pt;mso-list:l5 level1 lfo2;background:white'><![if !supportLists]><span style='font-family:"Helvetica",sans-serif;color:#333333;mso-fareast-language:EN-US'><span style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'>“</span><span style='font-family:"Helvetica",sans-serif;color:#333333;mso-fareast-language:EN-US'>All code points in a single label will be taken from the same script as determined by the Unicode Standard Annex #24: Script Names <<a href="http://www.unicode.org/reports/tr24"><span style='color:#0098D5'>http://www.unicode.org/reports/tr24</span></a>>. Exceptions to this guideline are permissible for languages with established orthographies and conventions that require the commingled use of multiple scripts. <span style='background:yellow;mso-highlight:yellow'>Even in the case of this exception, visually confusable characters from different scripts will not be allowed to co-exist in a single set of permissible code points unless a corresponding policy and character table is clearly defined.</span><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'>In the proposed version 4.0 this guideline has been divided into two parts. Guideline 15 addresses the first (unhighlighted) part. Guideline 16 covers the highlighted part. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'>We now have:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormalCxSpLast style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:18.0pt;mso-add-space:auto;text-indent:-18.0pt;line-height:105%;mso-list:l0 level1 lfo5'><![if !supportLists]><span lang=EN-CA style='font-family:"Times New Roman",serif;color:windowtext;mso-fareast-language:EN-US'><span style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span lang=EN-CA style='font-family:"Times New Roman",serif'>All code points in a single IDN label must be taken from the same Unicode script as determined by the Unicode Standard Annex #24: Unicode Script Property (</span><a href="http://www.unicode.org/reports/tr24"><span lang=EN-CA style='font-family:"Times New Roman",serif'>http://www.unicode.org/reports/tr24</span></a><span class=MsoHyperlink><span lang=EN-CA style='font-family:"Times New Roman",serif'>)</span></span><span lang=EN-CA style='font-family:"Times New Roman",serif'>. Exceptions to this guideline are permissible for languages with established orthographies and conventions that require the commingled use of multiple Unicode scripts. Also see Additional Notes V and VI.</span><span lang=EN-CA style='font-family:"Times New Roman",serif;color:windowtext;mso-fareast-language:EN-US'><o:p></o:p></span></p><p class=MsoListParagraph><span lang=EN-CA style='font-family:"Times New Roman",serif'><o:p> </o:p></span></p><p class=MsoNormalCxSpFirst style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:18.0pt;mso-add-space:auto;text-indent:-18.0pt;line-height:105%;mso-list:l0 level1 lfo5'><![if !supportLists]><span style='font-family:"Times New Roman",serif;color:windowtext'><span style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-family:"Times New Roman",serif'>In the case of any exceptions made allowing mixing of Unicode scripts, visually confusable characters from different scripts must not be allowed to co-exist in a single set of permissible code points unless a corresponding IDN policy and IDN Table is clearly defined to minimize confusion between domain names. Also see Additional Note IV.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'>Regards,<br>Sarmad <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:ZH-TW'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:ZH-TW'> Idngwg [<a href="mailto:idngwg-bounces@icann.org">mailto:idngwg-bounces@icann.org</a>] <b>On Behalf Of </b>Sarmad Hussain<br><b>Sent:</b> Saturday, May 12, 2018 11:11 AM<br><b>To:</b> Kal Feher <<a href="mailto:icann@feherfamily.org">icann@feherfamily.org</a>>; <a href="mailto:idngwg@icann.org">idngwg@icann.org</a><br><b>Subject:</b> Re: [Idngwg] FW: [Ext] haven't received any response from you<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'>Dear Kal, All,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'>The communication was forwarded to IDN Guidelines WG when it was received (see attached email). This comment is in continuation of the <a href="https://mm.icann.org/pipermail/comments-idn-guidelines-19oct17/2017q4/000003.html">comment submitted by JPRS</a> during the public comment. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'>The WG had a discussion around the input received by JPRS at multiple meetings. The final discussion took place on 19 April and the changes proposed were reviewed and agreed on 26 April (see notes at <a href="https://community.icann.org/display/IDN/IDN+Implementation+Guidelines">https://community.icann.org/display/IDN/IDN+Implementation+Guidelines</a>). The summary of the discussion and changes to incorporate the JPRS feedback is as follows:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'><o:p> </o:p></span></p><ol style='margin-top:0cm' start=1 type=1><li class=MsoNormal style='color:windowtext;mso-list:l4 level1 lfo9'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>The WG discussed that changes should be made in Guideline 15 and not 16. <o:p></o:p></span></li><li class=MsoNormal style='color:windowtext;mso-list:l4 level1 lfo9'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>The WG considered that the use of “script” is ambiguous and so changed the text to refer to “Unicode script” as defined in the Unicode script property. <o:p></o:p></span></li><li class=MsoNormal style='color:windowtext;mso-list:l4 level1 lfo9'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>In the context of “unicode script”, Japanese writing system uses Hiragana, Katakana and Han. Therefore, the WG agreed to qualify Japanese case as a known exception of script mixing. However, it was agreed that this be done as an Additional Note and not in the text of the guideline (latter to remain generic).<o:p></o:p></span></li><li class=MsoNormal style='color:windowtext;mso-list:l4 level1 lfo9'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>Additional Note V was added and says that Japanese is a known case where Hiragana, Katakana and Han scripts are mixed. It also notes that Chinese, Japanese and Korean IDN tables also mix “a-z” ASCII. <o:p></o:p></span></li><li class=MsoNormal style='color:windowtext;mso-list:l4 level1 lfo9'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>Additional Note VII allows additional letters like digits and hyphen to be mixed in scripts, where relevant.<o:p></o:p></span></li></ol><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'>The Additional Notes V and VII added are covering the concerns raised by JPRS to pre-qualify script-mixing in Japanese writing system. It still puts the Japanese case in the “exception” category because the point of reference is the “Unicode script”, which the JPRS had suggested be reviewed. The WG considered it and decided to use the “Unicode script” so that part of the comment was perhaps not addressed per the expectation of the JPRS. Also, there are two separate guidelines – no. 14 for within-script cases and no. 16 for cross-script cases. Therefore, no. 16 was not altered.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'>Please let me know how you would like to proceed.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'>Regards,<br>Sarmad<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext'> Idngwg [<a href="mailto:idngwg-bounces@icann.org">mailto:idngwg-bounces@icann.org</a>] <b>On Behalf Of </b>Kal Feher<br><b>Sent:</b> Friday, May 11, 2018 9:50 PM<br><b>To:</b> <a href="mailto:idngwg@icann.org">idngwg@icann.org</a><br><b>Subject:</b> Re: [Idngwg] FW: [Ext] haven't received any response from you<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p>Hello Sarmad,<o:p></o:p></p><p>I don't recall the communication. Was it discussed in one of our meetings and were there any action points from that discussion that we have failed to take?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On 11/5/18 10:37 pm, Sarmad Hussain wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>Dear All,<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>We received the following communication from JPRS today. Please let us know<o:p></o:p></pre><pre>how you would want to respond to it.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Regards,<o:p></o:p></pre><pre>Sarmad<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>-----Original Message-----<o:p></o:p></pre><pre>From: <a href="mailto:yoshitaka@jprs.co.jp">yoshitaka@jprs.co.jp</a> [<a href="mailto:yoshitaka@jprs.co.jp">mailto:yoshitaka@jprs.co.jp</a>] <o:p></o:p></pre><pre>Sent: Friday, May 11, 2018 2:49 AM<o:p></o:p></pre><pre>To: Mats Dufberg <a href="mailto:mats.dufberg@iis.se"><mats.dufberg@iis.se></a><o:p></o:p></pre><pre>Cc: Sarmad Hussain <a href="mailto:sarmad.hussain@icann.org"><sarmad.hussain@icann.org></a>; Pitinan Kooarmornpatana<o:p></o:p></pre><pre><a href="mailto:pitinan.koo@icann.org"><pitinan.koo@icann.org></a><o:p></o:p></pre><pre>Subject: [Ext] haven't received any response from you<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Dear IDN guidelines WG Chair,<o:p></o:p></pre><pre>(CC: Sarmad<span lang=JA>、</span>Pitinan)<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>On 30 March, I sent you our proposed change on the IDN implementation<o:p></o:p></pre><pre>guidelines document, following the suggestion made in the WG public meeting<o:p></o:p></pre><pre>in San Juan on 12 March (pasted below). For these one and half months, I<o:p></o:p></pre><pre>have not received any response to that from you.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Today, I happened to find that "Final Proposed Draft v. 4.0 of the IDN<o:p></o:p></pre><pre>Guidelines"<o:p></o:p></pre><pre><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_anno">https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_anno</a><o:p></o:p></pre><pre>uncement-2D2018-2D05-2D10-2Den&d=DwICJg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms<o:p></o:p></pre><pre>7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=zptC-TxcZW1PmY1jJ5<o:p></o:p></pre><pre>LzXVqPvD3ZlsiKvb4agfECycQ&s=wxk9m-mdZnan6Q2PmV36GLfLEXk6eKFuZRXMIFdZLeg&e=<o:p></o:p></pre><pre>was published. <o:p></o:p></pre><pre><o:p> </o:p></pre><pre>It was a surprise and disappointing for us to find it without prior<o:p></o:p></pre><pre>correspondence regarding our proposal sent to you on 30 March.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Yoshitaka Okuno<o:p></o:p></pre><pre>Manager, Services Development Department Japan Registry Services Co., Ltd.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>On Fri, 30 Mar 2018 17:40:59 +0900<o:p></o:p></pre><pre><a href="mailto:yoshitaka@jprs.co.jp">yoshitaka@jprs.co.jp</a> wrote:<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>Dear IDN guidelines working group,<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Please refer to the following comments and proposal.<o:p></o:p></pre><pre>The comments and proposal are being sent to you, following your <o:p></o:p></pre><pre>suggestion made in IDN Guidelines Working Group meeting in San Juan.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>In the working group meeting, the essence was orally stated by Hiro <o:p></o:p></pre><pre>Hotta, JPRS in the meeting room.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>I hope this may be of help to you.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>[Summary]<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>1. As described in current guidelines, the issues of visually confusable<o:p></o:p></pre><pre> characters are not specific to the cases with commingled use of <o:p></o:p></pre><pre> multiple scripts.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> We believe Japanese domain labels fall on the exceptional cases <o:p></o:p></pre><pre> stated in Guideline#15.<o:p></o:p></pre><pre> Kanji, Hiragana, and Katakana scrips are daily used in a <o:p></o:p></pre><pre> commingled manner based on established orthographies and <o:p></o:p></pre><pre> conventions in Japan. Such comingled use is allowed even in <o:p></o:p></pre><pre> single words. This means Japanese people consider the collective <o:p></o:p></pre><pre> set of Kanji, Hiragana, and Katakana characters to belong to ONE <o:p></o:p></pre><pre> script in constituting Japanese words, just as native English <o:p></o:p></pre><pre> writers/readers consider English characters to belong to ONE <o:p></o:p></pre><pre> script.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> Therefore, in the case where comingled use of UNICODE scripts is <o:p></o:p></pre><pre> allowed by Guideline#15, restrictions (if any) should be the same <o:p></o:p></pre><pre> as in the case of one UNICODE script in constituting domain <o:p></o:p></pre><pre> labels.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>2. In Additional Note IV, the guidelines of visually confusable<o:p></o:p></pre><pre> characters are described. We think they are the good notes because<o:p></o:p></pre><pre> the issues of visually confusable characters are clearly pointed.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> Taking into account the fact that issues of visually confusable <o:p></o:p></pre><pre> characters reside both in the case of a single UNICODE script and <o:p></o:p></pre><pre> in the case where comingled UNICODE scripts are allowed, we think <o:p></o:p></pre><pre> the sentence "must not be allowed to" is overdescribed in <o:p></o:p></pre><pre> guideline#16.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>[Suggestion]<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> We would like to propose as follows.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> - The guideline#16 is removed from section 2.5.2 and is moved to <o:p></o:p></pre><pre> a newly created section between 2.5.2 and 2.5.3. The new section <o:p></o:p></pre><pre> is headlined as "2.5.X Visually confusable characters".<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> - The guideline#16 will be modified as follows.<o:p></o:p></pre><pre> -------------------------------------------------------------------<o:p></o:p></pre><pre> 16. <o:p></o:p></pre><pre> Visually confusable characters had better not co-exist in a single<o:p></o:p></pre><pre> set of permissible code points. TLD registries should clearly <o:p></o:p></pre><pre> define a corresponding policy and IDN Table to minimize confusion <o:p></o:p></pre><pre> between domain names. Also see Additional Note IV.<o:p></o:p></pre><pre> <o:p></o:p></pre><pre>-------------------------------------------------------------------<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Thanks for your consideration.<o:p></o:p></pre><pre>----<o:p></o:p></pre><pre>Yoshitaka Okuno<o:p></o:p></pre><pre>Manager, Services Development Department Japan Registry Services Co., <o:p></o:p></pre><pre>Ltd.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre></blockquote><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><pre>_______________________________________________<o:p></o:p></pre><pre>Idngwg mailing list<o:p></o:p></pre><pre><a href="mailto:Idngwg@icann.org">Idngwg@icann.org</a><o:p></o:p></pre><pre><a href="https://mm.icann.org/mailman/listinfo/idngwg">https://mm.icann.org/mailman/listinfo/idngwg</a><o:p></o:p></pre></blockquote><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><pre>-- <o:p></o:p></pre><pre>Kal Feher<o:p></o:p></pre><pre>@kalfeher<o:p></o:p></pre></div></body></html>