<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 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:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0in;
        margin-right:0in;
        margin-bottom:0in;
        margin-left:.5in;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:"Calibri",sans-serif;}
@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:1797872141;
        mso-list-type:hybrid;
        mso-list-template-ids:1531760118 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@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;}
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-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">This is the
<u>Ninth Topical E-mail</u> on outstanding questions being “put to the list.”  This covers a question stemming from the ICANN Board’s comment that applications for strings not integrated in the RZ-LGR should not be processed at all.  (Topic 25)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Remember:  We are down to the wire on this, so unless you have a VERY strong objection to these, we will put these into the document.  If you do have a big issue with the responses
 to these (all of which were previously discussed and in emails over the past 1.5 months), please let us know ASAP.  Only comments that provide the rationale for the objection with proposed replacement text to address the specific outstanding questions will
 now be considered.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Let’s not let the perfect be the enemy of the good.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><u><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;background:white">Language from Draft Final Report</span></u><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;background:white">: 
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Implementation Guidance 25.3: If a script is not yet integrated into the RZ-LGR, applicants should be able to apply for a string in that script, and it should be processed up to but not including
 contracting.<span style="color:black;background:white"><o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><u><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;background:white">Comment from the ICANN Board:</span></u><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;background:white"> 
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">The Board suggests that any applied-for string in a script not integrated in the RZ-LGR should not be processed until its validity and variant labels can be determined by RZ-LGR,
 following the Recommendation 5 of the RZ-LGR Study Group. <span style="background:white">
<o:p></o:p></span></span></p>
<p class="MsoNormal"><u><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;background:white"><o:p><span style="text-decoration:none"> </span></o:p></span></u></p>
<p class="MsoNormal"><u><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;background:white">Leadership Proposal</span></u><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;background:white">. Based on the discussions
 that took place on the call as well as in other discussions of similar topics, we would recommend:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;background:white"><o:p> </o:p></span></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo1">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;background:white">Leaving the language in the report as is with respect to the recommendation.  Rationale:  Although the Study Group recommended that the label should not “proceed through evaluation”,
 it did not offer any thoughts as to whether the other uniquely GNSO new gTLD processes should apply.  It did not discuss contention sets, public comments, objections, etc.  This is most likely because the group with comprised of ccNSO members (as well as GNSO)
 and the aforementioned processes are uniquely for new gTLDs and not for the ccTLD Fast Track.
<o:p></o:p></span></li></ol>
<p class="MsoListParagraph"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;background:white"> <o:p></o:p></span></p>
<ol style="margin-top:0in" start="2" type="1">
<li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo1">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;background:white">Include a warning for applicants that apply for scripts that have not been integrated into the RZ-LGR (one will be included in the next draft) that states that there is a chance
 that the application may not ever pass evaluation and that the applicant may be responsible for the costs of additional evaluations of that string.  This is mentioned in the Study Group Report as “Option B”.<o:p></o:p></span></li></ol>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;background:white"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Please have your comments (If any) by no later than 23:59:59 UTC on Wednesday, December 9, 2020.<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Sincerely,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Jeff & Cheryl<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">SubPro Co-Chairs<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>