<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;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
.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:1471480234;
mso-list-template-ids:423535492;}
@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:1498495798;
mso-list-template-ids:-2050580512;}
@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" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><br>
Please find below the notes and action items from the<span class="apple-converted-space"> </span><a href="https://community.icann.org/x/zIyZDg" title="https://community.icann.org/x/yoyZDg"><span style="color:#0563C1">7 September 2023 IDNs EPDP meeting #95</span></a><span class="apple-converted-space"> </span>at
12:00 UTC.<o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<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" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<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;color:black"><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>
<div>
<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">Staff will review Recommendation 4.4 and draft potential language for priority for past applications in the string similarity review process.<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 chair asked the team to consider approaches for the string similarity review process, also in Recommendation 4.4, to clear up confusion in the event that an in-process ccTLD string is found confusingly
similar to an in-process gTLD string<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">Staff will look into the best wording for Rec 6.2 based on RFC 2119. <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">Staff will review Final Recommendations 7.8 and 7.11 and provide language to reflect the request from the public comments about not conforming to the language in recognized data protection principles.<b><o:p></o:p></b></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 review the proposed changes for Rec 3.5 and IG 3.6.<b><o:p></o:p></b></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><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></b></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 (2min)<o:p></o:p></span></li></ul>
<ul style="margin-top:0in" type="disc">
<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">No Updates<o:p></o:p></span></li></ul>
</ul>
<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">Welcome and Chair Updates (5min)<o:p></o:p></span></li></ul>
<ul style="margin-top:0in" type="disc">
<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 and detailed the email that went out to the GNSO council from IDNs EPDP Staff Support regarding .Quebec. The council will have one week to review and provide
feedback.<o:p></o:p></span></li></ul>
</ul>
<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">Continue Review of Proposed Updates of Phase 1 Final Recommendations (Starting at 3.16) (110 min)<o:p></o:p></span></li></ul>
<ul style="margin-top:0in" type="disc">
<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">Starting with Recommendation 3.16, the global change was made for this recommendation and sub recommendations (3.16.1, 3.16.2, 3.16.3) were added to remain consistent with formatting. A footnote
was also added to reflect comments received. This received unanimous approval from the team.<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">Rec 3.17 received an update from a team member on the new guidance from the Chinese, Japanese, and Korean Generation Panels on the status of single-character gTLDs and expect formal communications
to be sent from the group on the second part of Rec 3.17. Regardless, it did receive support in chat from the team. <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">A smaller global change was made to clarify that Reserve Names are New gTLD Program Reserved Names was made and was agreed to by the team. This was the major change reflected in 3.18-3.21. <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">Rec 3.22 contained larger changes that are part of a pending resolution in front of the ICANN Board. Staff support will keep an ear out for any updates and provide them to the team if available.<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">Rec 4.1 is a larger recommendation with many sub recommendations included to maintain common formatting. It also contained the smaller global change regarding Reserve Names above and removed text
in 4.1.6 and 4.1.12 to give flexibility to the string similarity review panel to review applied-for strings in any number of characters against two-character ASCII combinations. It was asked from a team member if an applied-for string in the next round is
found confusingly similar to a 2012 round string that is still in process and hasn't been delegated, should priority be given to the 2012 round string? <o:p></o:p></span></li></ul>
</ul>
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<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 chair agreed it would be helpful to call out in a recommendation about the priority given to past rounds of gTLDs to account for the possibility posed by the team member that without an explicit
recommendation that a prior application from 2012 for this round (or potentially this round for future rounds) would be skipped over by the string similarity review. It is possible that this fits around Recommendation 4.4 as it is the outcome for string similarity
review. <o:p></o:p></span></li></ul>
</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">
<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: Staff will review Recommendation 4.4 and draft potential language for priority for past applications in the string similarity review process.<o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Recs 4.2 and 4.3 were discussed without objection.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Rec 4.4 was discussed regarding the changes made and a team member brought up the potential for in process ccTLD and gTLD requests where the in process ccTLD could take precedence over the gTLD,
as this is in the 2012 Applicant Guidebook. <o:p></o:p></span></li></ul>
</ul>
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<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">The chair asked how to account for the difference in timing between requests and what is currently in use is if the applied gTLD has completed its application process (ready to be delegated) and
then the ccTLD request comes in, it is too late. If the ccTLD request comes in as the gTLD application is under consideration, then the ccTLD wins out.<o:p></o:p></span></li></ul>
</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">
<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">Another team member asked about what happens if the gTLD passes the string similarity test but the process is not finished and the ccTLD request comes across the wire? <o:p></o:p></span></li></ul>
</ul>
</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">The ccTLD would proceed as the only way the ccTLD application stops is if the gTLD is completely finished and is ready to be contracted. <o:p></o:p></span></li></ul>
</ul>
</ul>
</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">
<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">ACTION ITEM: The chair asked the team to consider approaches for the string similarity review process in Recommendation 4.4 to clear up confusion in the event that an in-process ccTLD string is found
confusingly similar to an in-process gTLD string<o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
</ul>
</ul>
<ul style="margin-top:0in" type="disc">
<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">There was language with regard to the limited challenge mechanism in the rationale for Rec 4.4 that may need rewording in the future, but not at this moment<o:p></o:p></span></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">Rec 5.1 has no changes, while 5.2-5.5 contain edits to incorporate numbered sub recommendations instead of bulleted lists and in 5.3 there are edits to language to clarify and remain consistent throughout
the report. This received unanimous approval from the team.<o:p></o:p></span></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">No changes were made to Rec 6.1<o:p></o:p></span></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">Minor changes were made to Recommendation 6.2 in meaning, but the recommendation was rewritten to better reflect this. There was discussion over the use of “must” instead of “will” in the text, with
“must” preferred by the team. “Must” was added to the text during the call, but for consistency “shall” might also be used. <o:p></o:p></span></li></ul>
</ul>
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<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">ACTION ITEM: Staff will look into the best wording for Rec 6.2 based on RFC 2119. <o:p></o:p></span></li></ul>
</ul>
</ul>
<ul style="margin-top:0in" type="disc">
<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">Rec 7.1 contained some revised text from staff and leadership and a team member provided context for registries not wanting different SLAs for different TLDs, as there is value in consistency. <o:p></o:p></span></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">A minor change was made for 7.2 without any disagreement. <o:p></o:p></span></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">A substantial change was made for 7.3 with the vice chair responding that the “Amendment to Rec 7.3 is to reflect an agreed change in position requiring a new RA for existing ROs to require the same
RA but adding a specification to achieve the same goal.”<o:p></o:p></span></li></ul>
</ul>
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<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">This was agreed to by the team.<o:p></o:p></span></li></ul>
</ul>
</ul>
<ul style="margin-top:0in" type="disc">
<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">Rec 7.4 was removed due to it no longer being necessary and the following numbers were changed. Below this bullet, the new numbers are referred to.<o:p></o:p></span></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">There were no major changes to 7.5 and 7,6<o:p></o:p></span></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">Rec 7.7 received some revisions that were not objected to by the team.<o:p></o:p></span></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">Rec 7.8’s revisions were exclusively the global change.<o:p></o:p></span></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">Rec 7.9 was revised to reflect proposed edits from the public comment proceeding. <o:p></o:p></span></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 Public Comment review for Final Recommendations 7.8 and 7.11 should add the language regarding contracted parties. (Contracted parties must abide by all applicable laws and regulations…)<o:p></o:p></span></li></ul>
</ul>
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<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">ACTION ITEM: Staff will add draft text in the “Public Comment Review” section of Final Recommendations 7.8 and 7.11 to reflect the request from the public comments about not conforming to the language
in recognized data protection principles. <o:p></o:p></span></li></ul>
</ul>
</ul>
<ul style="margin-top:0in" type="disc">
<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">Rec 7.12-7.14 received minor changes without objection<o:p></o:p></span></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">Rec 8.1 received no changes<o:p></o:p></span></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">Rec 8.2 was discussed for the changes made based on prior comments, including that guidelines would be non-binding. There was discussion about the timeline (before or during implementation) and lack
of precedence in this area. It was suggested that guidelines could evolve, but the chair answered the framework would be developed during implementation not the specific guidelines.<o:p></o:p></span></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">A global change was made in Rec 8.4 and a minor wording change was made in Rec 8.5 without objection.<o:p></o:p></span></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">No changes were made in Rec 8.6. In Rec 8.7 there was a minor change made to discuss the stability principle in the LGR procedure. There was also a discussion for changing “must” to “should” in the
text, which is reflected in the current document. <o:p></o:p></span></li></ul>
</ul>
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<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">The second instance must remain ”must”<o:p></o:p></span></li></ul>
</ul>
</ul>
<ul style="margin-top:0in" type="disc">
<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">No change was made in Rec 8.8.<o:p></o:p></span></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 global change was made in Recs 8.10 and 8.11. Implementation Guidance was added for 8.11 in IG 8.12 to address ICANN Org’s concern from the public comment period. The implementation guidance
shifted the recommendation numbers and the numbers below this bullet are the new numbers. <o:p></o:p></span></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">Rec 8.13 contained a minor wording change without objection.<o:p></o:p></span></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">Rec 9.1 and IG 9.2 did not receive comments and do not contain any changes. It was noted in the rationale that some text was removed to reflect best practices.<o:p></o:p></span></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">No changes were made in Rec 9.3.<o:p></o:p></span></li></ul>
</ul>
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<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 was a discussion about the label state transition from “rejected” to “withheld-same-entity” in IG 9.4 but the chair determined that at this time it is not necessary to change this transition
path or delete the “rejected” label state. <o:p></o:p></span></li></ul>
</ul>
</ul>
<ul style="margin-top:0in" type="disc">
<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">Review of proposed text for Rec 3.5 and I.G. 3.6 (Time Permitting)<o:p></o:p></span></li></ul>
<ul style="margin-top:0in" type="disc">
<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 discussed proposed revisions from leadership to Rec 3.5 and IG 3.6<o:p></o:p></span></li></ul>
</ul>
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<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">Possible outcomes were presented to the team for the implementation guidance, with the chair asking the team to consider the proposal.
<o:p></o:p></span></li></ul>
</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">
<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 review the proposed changes for Rec 3.5 and IG 3.6.<o:p></o:p></span></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">The chair announced that this will be discussed next week and then closed the meeting. <o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
</div>
</div>
</body>
</html>