<html 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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
@font-face
{font-family:"Times New Roman \(Body CS\)";
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Arial",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@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:145704726;
mso-list-template-ids:-1797650852;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:457528334;
mso-list-template-ids:-616123856;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level4 lfo3
{mso-level-start-at:0;
mso-level-numbering:continue;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level4 lfo4
{mso-level-start-at:0;
mso-level-numbering:continue;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level5 lfo4
{mso-level-start-at:0;
mso-level-numbering:continue;
mso-level-text:o;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Hi All,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><br>
Please find below the notes and action items from the <a href="https://community.icann.org/x/yoyZDg">
31 August 2023 IDNs EPDP meeting #94</a> at 12:00 UTC.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Ariel, Steve, and Dan<o:p></o:p></span></p>
<div style="mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal" style="border:none;padding:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">ACTION ITEMS</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo1;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Leadership will look to set an agenda for the F2F in October as to allow representative groups time to discuss and strategize for the meeting <o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo1;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Leadership will reconsider Recommendation 3.xx for further clarification<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo1;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Leadership will work to re-write Rec. 3.5.4. to better address the responsibilities of the registry operator in relation to the end-user.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo1;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Leadership will discuss the wording of 3.5.1 and determine if the second part of the statement is redundant due to the definition of variant.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo1;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The ALAC will review the updated language in Rec 3.5 and IG 3.6<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo1;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The team will deliberate on IG 3.9 and how to proceed with the specifics of the application process<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">NOTES</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo2;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Roll Call and SOI Updates<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo2;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Welcome and Chair Updates<o:p></o:p></span>
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The chair welcomed everyone to the call <o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Updates were provided on the upcoming Face to Face Workshop (F2F)<o:p></o:p></span>
<ul style="margin-top:0in" type="square">
<li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo2;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The dates will be between 6 December to 8 December <o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo2;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Details were provided for Travel Support for those who meet the requirements to receive funding <o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo2;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Most of the content for this meeting will be focused on Phase 2 of the EPDP<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo2;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">ACTION ITEM: Leadership will look to set an agenda for the F2F in October as to allow representative groups time to discuss and strategize for the meeting <o:p></o:p></span></li></ul>
</li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo2;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Review of Proposed Updates of Phase 1 Final Recommendations<o:p></o:p></span>
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The Chair provided a background for the Final Recommendations for Phase 1 of the EPDP<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Staff then provided more detailed information and walked the team through the document<o:p></o:p></span>
<ul style="margin-top:0in" type="square">
<li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo2;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Redline was used to denote changes from the initial report<o:p></o:p></span></li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2;vertical-align:baseline">
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Rec 1.1</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif"> contains a minor verbiage change and the rationale was also updated<o:p></o:p></span>
<ul style="margin-top:0in" type="square">
<li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo2;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">This received unanimous support from the team.<o:p></o:p></span></li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2;vertical-align:baseline">
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Rec 2.1 </span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">contains changes to avoid being repetitive in the text and future-proofed (removed “IDN”) and updates to the rationale
to expand on the removal of the asterisk <o:p></o:p></span>
<ul style="margin-top:0in" type="square">
<li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo2;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">This update is part of the global change for futureproofing<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo2;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">There was a question from a team member regarding the grammar of “only” to refer to a specific registry operator, which was discussed by Leadership<o:p></o:p></span></li></ul>
</li></ul>
</li></ul>
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<ul style="margin-top:0in" type="square">
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l1 level4 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">This was deliberately included and meant to emphasize the point and was agreed to by the team member<o:p></o:p></span></li></ul>
<li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">This recommendation was agreed to by the team<o:p></o:p></span></li></ul>
<li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo3;vertical-align:baseline">
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Rec 3.1</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif"> contains the global change and
<b>Rec 3.2</b> changes “delegated” to “existing” for clarity, including rationale for the decisions<o:p></o:p></span>
<ul style="margin-top:0in" type="square">
<li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">This was agreed to by the team<o:p></o:p></span></li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo3;vertical-align:baseline">
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Rec 3.3 </span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">contains similar edits for the future-proofing global change<b><o:p></o:p></b></span>
<ul style="margin-top:0in" type="square">
<li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">There was a discussion from the team over possibly removing reference to the 2012 round, but this was not needed due to the differentiation between TLD and SLD<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The recommendation was agreed to by the team<o:p></o:p></span></li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo3;vertical-align:baseline">
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Rec 3.4 </span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">received a slightly more detailed change due to verbiage being updated to comply with comments received<b><o:p></o:p></b></span>
<ul style="margin-top:0in" type="square">
<li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">This was approved by the team as it addresses ICANN Org’s concerns about the original wording<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">This recommendation was agreed to by the team<o:p></o:p></span></li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo3;vertical-align:baseline">
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Rec 3.xx</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif"> is a new recommendation from leadership to capture a request for clarification on Rec 3.4 and clarifies that there
are no swapping of variant labels with the exception of Brand TLD variant labels due to the existing recommendation from SubPro which explicitly states this<b><o:p></o:p></b></span>
<ul style="margin-top:0in" type="square">
<li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">A member of team requested more clarification to be made in the wording <o:p></o:p></span>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l1 level4 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">ACTION ITEM: Leadership will reconsider Recommendation 3.xx for further clarification<o:p></o:p></span></li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">A team member asked if there would be future public comment due to the new recommendations, but the chair explained there would not be. The venue for stakeholder comment is through the team members
of the EPDP. There will be an opportunity for the team to provide their thoughts on the updates at a future meeting<o:p></o:p></span></li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo3;vertical-align:baseline">
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Rec 3.5</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif"> contains revised and additional language for the explanation of the mission and purpose of the primary gTLD string
from applicants <b><o:p></o:p></b></span>
<ul style="margin-top:0in" type="square">
<li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">This received a comment from a team member in the document regarding clarity of a specific wording choice and this rolled up into discussion of I.G 3.6<o:p></o:p></span>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l1 level4 lfo3;vertical-align:baseline">
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">I.G. 3.6 </span>
</b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">is written in support of the goal to prevent frivolous applications for allocatable variant labels<b><o:p></o:p></b></span></li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">There was discussion on the team of the value of a scoring system against just having pass/fail<o:p></o:p></span>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l1 level4 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The chair described a scenario where there could be overall scores for the entirety of a gTLD registration or just the IDN part of the registration. The implementation guidance should allow evaluators
to make that distinction if that is how the SubPro implementation guidance gets delivered<o:p></o:p></span></li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">A team member asked what type of information the registry would have to provide for 3.5.4 that would satisfy the evaluators.<o:p></o:p></span>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l1 level4 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The nuance, said the team member, is in the relationship between the end user and the registrant. The team member proposed potentially rewriting this part of the recommendation as it will be difficult
for the registry operator to enforce policies with all the intermediaries between the end-user and the registry operator (registrar, resellers, etc.). They would prefer the language be tightened up to become answerable by the registry operator<o:p></o:p></span></li></ul>
</li></ul>
</li></ul>
</ul>
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<ul style="margin-top:0in" type="square">
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="color:black;mso-list:l1 level5 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">This was agreed to by the chair<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level5 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">ACTION ITEM: Leadership will work to re-write Rec. 3.5.4. to better address the responsibilities of the registry operator in relation to the end-user.<o:p></o:p></span></li></ul>
</ul>
<li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">A comment on 3.5.1 asked about potentially confusing language <o:p></o:p></span>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l1 level4 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The second part of 3.5.1 may be redundant due to the word “meaning”. The variant should already be equivalent to the primary string, per the team member, and therefore may be able to be shortened
and merged with 3.5.2.<o:p></o:p></span>
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="color:black;mso-list:l1 level5 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">ACTION ITEM: Leadership will discuss the wording of 3.5.1 and determine if the second part of the statement is redundant due to the definition of variant.<o:p></o:p></span></li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l1 level4 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Another participant in the chat wrote: “My quick comment focuses on ‘how it is the same as the applied-for primary gTLD string or existing gTLD’. The meaning of the primary gTLD is de facto the same
with that of its variants. They are only different in written form but have the same meaning. So, applicants do not need to answer this question.”<o:p></o:p></span>
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="color:black;mso-list:l1 level5 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Leadership followed up to ask if this is the case with scripts other than Chinese.<o:p></o:p></span></li></ul>
</li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">There was also a comment about the subjective nature of the language and criteria in 3.5.3 and 3.5.4<o:p></o:p></span>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l1 level4 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">A comment suggested 3.5.4 may not be needed due to the same-entity principle<o:p></o:p></span>
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="color:black;mso-list:l1 level5 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">This is in light of the registry operator or registrar not having much control over who is going to register a name at a second level. Unless the list of strings registered at the second level are
predetermined, it would be impossible to regulate this.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level5 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The Chair asked if the team believes 3.5.4 is necessary to be included.<o:p></o:p></span></li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l1 level4 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Another comment suggested that much of the application process is subjective and potentially challenging for the evaluators<o:p></o:p></span>
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="color:black;mso-list:l1 level5 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">A comment from staff mentioned “much of the new gTLD program is based on subjective criteria so in that sense, this is not a new problem. The evaluators need to be able come up with consistent results,
even in cases where there are multiple firms performing the evaluation. And for context, the SubPro PDP made Rec 27.2 (“Evaluation scores on all questions should be limited to a pass/fail<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level5 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">scale (0-1 points only)” to not only simplify the process, but to also reduce the level of subjectivity in evaluation.”<o:p></o:p></span></li></ul>
</li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">There was a discussion on the “general standard of reasonableness” and the consistency from evaluators <o:p></o:p></span>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l1 level4 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">One participant in chat summed up their thoughts by posing the question of “how to [ensure] that evaluators use the same rule to measure all applications”<o:p></o:p></span>
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="color:black;mso-list:l1 level5 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">They then followed up with “I think we cannot evaluate these detailed questions/requests for information without knowing how it will be evaluated. As the example I used, if the applicant fills out
an answer, would that be considered a PASS? Or are we expecting that the applicant’s answer provides specific details, operational or communications, etc.”<o:p></o:p></span>
<ul style="margin-top:0in" type="square">
<li class="MsoNormal" style="color:black;mso-list:l1 level6 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Leadership replied that “If it is generally reasonable then it would pass. Recall we are attempting to weed out frivolous applications for variant label(s). So something senseless would fail.” <o:p></o:p></span></li></ul>
</li></ul>
</li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The ALAC representative to the team volunteered to have the ALAC review the updated text for 3.5 and 3.6 as the original language was generated by them. <o:p></o:p></span>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l1 level4 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The chair discussed the leadership changes in the text of 3.6 to allow evaluators to be reasonable in their scoring. In the estimation of the chair, it will be highly unlikely that an application
would fail. <o:p></o:p></span>
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="color:black;mso-list:l1 level5 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">ACTION ITEM: The ALAC will review the updated language in Rec 3.5 and IG 3.6<o:p></o:p></span></li></ul>
</li></ul>
</li></ul>
<li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo4;vertical-align:baseline">
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Rec 3.7 </span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">was described, along with pointed discussion on the updated language for IG 3.9<o:p></o:p></span>
<ul style="margin-top:0in" type="square">
<li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">One team member asked about the impact on Registry Service Provider, including current RSPs?<o:p></o:p></span>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l1 level4 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The chair shared that the intent is that there will be no impact on current RSPs as the tests are not retroactive and will only impact new applicants.<o:p></o:p></span>
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="color:black;mso-list:l1 level5 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The team member asked about in the future if there are three tests that will have to apply for a new applicant. If an existing gTLD does not comply because the RSP does not have the requirements
on new RSPs implemented, why would they be allowed to continue to offer their services? <o:p></o:p></span></li></ul>
</li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Another team member asked about the impact on registry service operators managing multiple different gTLD backends. <o:p></o:p></span>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l1 level4 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">For example, if an RSP manages five different TLDs and one of them is a new operator that is transitioning in, that requires compliance with the new tests, how are they going to manage the split
between the new and old requirements?<o:p></o:p></span>
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="color:black;mso-list:l1 level5 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">They suggested decoupling the capture of learnings and what needs to be done, as to not talk about implementation. Changes could be applied in the future such that operators will have ample time
to reflect changes and gain compliance. <o:p></o:p></span></li></ul>
</li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">A member of the team had considered this language as meaning ICANN would develop and require the specific clauses, but there is a challenge that there is no one standard <o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The intent of the guidance is to complete research into the implementation of this round of the gTLD program to inform best practices for future rounds.<o:p></o:p></span>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l1 level4 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">ACTION ITEM: The team will deliberate on IG 3.9 and how to proceed with the specifics of the application process<o:p></o:p></span></li></ul>
</li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo4;vertical-align:baseline">
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Rec 3.10 </span>
</b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">was described, and the team detailed the global change and editorial changes made to the wording.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo4;vertical-align:baseline">
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Rec 3.11 </span>
</b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">was described, including the global change and a discussion on the four allocatable variant labels, with no substantive changes.<b><o:p></o:p></b></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo4;vertical-align:baseline">
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Rec 3.12 </span>
</b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">follows the global change. <b><o:p></o:p></b></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo4;vertical-align:baseline">
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Rec 3.13</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif"> covers the potential discount for registry operators and the discretion given to ICANN org to decide on individual
cases and the grammatical change to the recommendation to clarify this point. <b><o:p></o:p></b></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo4;vertical-align:baseline">
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Rec 3.14 </span>
</b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">contains minor wording changes and
<b>Rec 3.15 </b>there are no edits. In these two recommendations 2012 and IDN remain, not following the global change, as they contain specific carve outs for these cases, nullifying the global change.<b><o:p></o:p></b></span>
<ul style="margin-top:0in" type="square">
<li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">There were no objections from the team from 3.10-15<o:p></o:p></span></li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The vice-chair implored the team to review the document before meeting #95 next week <o:p></o:p></span></li></ul>
<li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">AOB<o:p></o:p></span>
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The chair ended the call<o:p></o:p></span></li></ul>
</li></ul>
<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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Dan Gluck
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>
</div>
</body>
</html>