<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:"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:DengXian;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@DengXian";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 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;}
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.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:227686761;
mso-list-template-ids:-2036410106;}
@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-start-at:0;
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-start-at:0;
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-start-at:0;
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-start-at:0;
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-start-at:0;
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-start-at:0;
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-start-at:0;
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-start-at:0;
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:1468164470;
mso-list-template-ids:-2036410106;}
@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-start-at:0;
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-start-at:0;
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-start-at:0;
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-start-at:0;
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-start-at:0;
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-start-at:0;
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-start-at:0;
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-start-at:0;
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 l2
{mso-list-id:1468427564;
mso-list-type:hybrid;
mso-list-template-ids:-158678830 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l2:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l2:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l3
{mso-list-id:1482044957;
mso-list-template-ids:-2006421694;}
@list l3: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 l3:level2
{mso-level-start-at:0;
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 l3:level3
{mso-level-start-at:0;
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 l3:level4
{mso-level-start-at:0;
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 l3:level5
{mso-level-start-at:0;
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 l3:level6
{mso-level-start-at:0;
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 l3:level7
{mso-level-start-at:0;
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 l3:level8
{mso-level-start-at:0;
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 l3:level9
{mso-level-start-at:0;
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 l4
{mso-list-id:1853301295;
mso-list-template-ids:1620576282;}
@list l4: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 l4:level2
{mso-level-start-at:0;
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 l4:level3
{mso-level-start-at:0;
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 l4:level4
{mso-level-start-at:0;
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 l4:level5
{mso-level-start-at:0;
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 l4:level6
{mso-level-start-at:0;
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 l4:level7
{mso-level-start-at:0;
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 l4:level8
{mso-level-start-at:0;
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 l4:level9
{mso-level-start-at:0;
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 l5
{mso-list-id:1981302145;
mso-list-template-ids:1994534266;}
@list l5: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 l5:level2
{mso-level-start-at:0;
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 l5:level3
{mso-level-start-at:0;
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 l5:level4
{mso-level-start-at:0;
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 l5:level5
{mso-level-start-at:0;
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 l5:level6
{mso-level-start-at:0;
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 l5:level7
{mso-level-start-at:0;
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 l5:level8
{mso-level-start-at:0;
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 l5:level9
{mso-level-start-at:0;
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 l6
{mso-list-id:2055696565;
mso-list-template-ids:832337978;}
@list l6: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 l6:level2
{mso-level-start-at:0;
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 l6:level3
{mso-level-start-at:0;
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 l6:level4
{mso-level-start-at:0;
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 l6:level5
{mso-level-start-at:0;
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 l6:level6
{mso-level-start-at:0;
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 l6:level7
{mso-level-start-at:0;
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 l6:level8
{mso-level-start-at:0;
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 l6:level9
{mso-level-start-at:0;
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;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<div style="border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal"><span style="color:black">Dear all, <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Please find below the notes from today’s meeting on Thursday, 19 May 2022 at 13:30 UTC.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Kind regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Ariel, Steve, Emily<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><b><u>Action Items:</u></b><o:p></o:p></p>
<p class="MsoNormal"><b> </b><o:p></o:p></p>
<p class="MsoNormal"><b>ACTION ITEM: Leadership and staff to develop a proposal to scope further outreach to the three GPs with respect to additional work.</b><o:p></o:p></p>
<p class="MsoNormal"><b> </b><o:p></o:p></p>
<p class="MsoNormal"><b><u>Notes – IDNs EPDP Call – 5 May 2022</u></b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">1. Roll Call & SOI (2 minutes)<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">2. Welcome & Chair Updates (5 minutes)<o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo1">Have received feedback from Chinese, Japanese, and Korean Generation Panels - A7 Part 2. Will cover that if there is time.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo1">Last call for feedback for the draft text for charter questions A7 part 1, A9 and A10. Deadline is tomorrow at the close of business. Will look at feedback and decide if there is
anything to bring back to the WG if there are suggestions for amendments to the draft text.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo1">Attendance at ICANN74: Remind WG members that there are requests for responses to a survey to indicate if they will be attending the EPDP calls in person. Even if remotely please
still fill in the form answering “no”.<o:p></o:p></li></ul>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">3. Continue discussion of charter question D2 (40 minutes)<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Slide 4:</b><o:p></o:p></p>
<p class="MsoNormal"><b> </b><o:p></o:p></p>
<p class="MsoNormal"><b>Charter Question</b> <b>D2:</b> In order to ensure that the
<b>same entity principle</b> is maintained for <b>a gTLD and its allocated variant TLD labels</b>, what are the operational and legal impacts to the: <o:p></o:p></p>
<p class="MsoNormal">● Registry Transition Process or Change of Control in the Registry Agreement;<o:p></o:p></p>
<p class="MsoNormal">● Emergency Back-End Registry Operator (EBERO) provisions; and <o:p></o:p></p>
<p class="MsoNormal">● Reassignment of the TLD as a result of the Trademark Post-Delegation Dispute Resolution Procedure (TM-PDDRP)?<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b><i>Implicit Dependency with D1a: </i></b><i>“Should each TLD label be the subject of a separate Registry Agreement with ICANN? If not, should each TLD label along with its variant labels be subject to one Registry Agreement with the
same entity?” </i><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Slide 10:</b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>SubPro Context</b><o:p></o:p></p>
<p class="MsoNormal">To the extent that the TLD were to change hands at any point after delegation,<b> the variant TLDs must remain linked contractually,</b> which should be considered a persistent requirement (e.g.,
<b>this would impact gTLD registry transition procedures, including EBERO</b>).<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Staff Paper Context</b><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="mso-list:l4 level1 lfo2">Each of the registry agreements must contain provisions requiring
<b>all variant labels in the IDL set to follow the same process</b> in the event of any registry transition via a Registry Transition Process or Change of Control. <o:p></o:p></li><li class="MsoNormal" style="mso-list:l4 level1 lfo2">In no event, should the composition of the allocated and delegated set of variant TLDs be allowed to change at the same time as the change of the Registry Operator.<o:p></o:p></li><li class="MsoNormal" style="mso-list:l4 level1 lfo2">Emergency transition of a TLD to an EBERO
<b>must trigger an emergency transition of all variant TLDs to the EBERO</b>. <o:p></o:p></li></ul>
<p class="MsoNormal">In the case where a <b>Registry Agreement is terminated as a result of a TM-PDDRP</b> determination, the same entity rule would continue to apply so that the allocated and delegated variant TLD labels in the set would be
<b>assigned to the same entity togethe</b>r. <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Slide 11:</b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Questions for Discussion </b><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="mso-list:l6 level1 lfo3">How to maintain the “same entity” principle in the event of a registry transition process, with respect to each of the three types? <o:p></o:p></li><li class="MsoNormal" style="mso-list:l6 level1 lfo3">Are there any additional consideration related to the registry transition process involving variant gTLD labels?
<o:p></o:p></li></ul>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><u>Discussion</u>:<o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo1">Continuation of the discussion from the last meeting.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo1">Implicit dependency with D1a.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo1">EBERO process vs. planned retirement of a variant:
<o:p></o:p>
<ul style="margin-top:0in" type="circle">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level2 lfo1">Subpro recommended that the variants should be linked contractually, and should go along with the TLD.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level2 lfo1">Question: How to maintain this “same entity” principle in the event of a registry transition process?<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level2 lfo1">Question: Should the EBERO process would be triggered for a TLD variant that was intentionally retired? Answer: Procedurally it is not triggered. The EBERO would not be triggered
in a single case; it would be via a different process to ensure that it is done in a controlled manner.
<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level2 lfo1">One additional Subpro requirement: if you have a second-level name variant under a TLD it must be linked with the same entity. Would need a mechanism to make sure that it stays registered
to the same entity.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level2 lfo1">Principle: How to maintain the same-entity rule.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level2 lfo1">The purpose of the EBERO is to maintain the critical functions of the DNS.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level2 lfo1">Maybe focus on what is expected for the controlled (intentional) retirement and EBERO. May not need to consider the edge case of a forced retirement.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level2 lfo1">Remember that EBERO is an emergency operator.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level2 lfo1">Need to separate the retirement of a variant from the EBERO process. Variants that operate under one registry agreement, if you look at the .wed case the primary reason was financial.
Couldn’t image one variant triggering EBERO it would have to be the TLD and its variants. We shouldn’t confuse the retirement of a TLD and its variants with a TLD triggers the EBERO process.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level2 lfo1">If you want to retire a variant TLD there is no reason to go into EBERO. If you do go into EBERO then all of the variant TLDs should go into EBERO (if one goes, all should go).<o:p></o:p></li></ul>
</li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo1">Seems that there is an agreement to maintain the same entity principle: if one variant goes into EBERO then all variants go.<o:p></o:p></li></ul>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">4. Introduction to charter question D3 (30 minutes):<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Slide 13:</b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Charter Question</b> <b>D3:</b> In order to ensure that the same entity principle is maintained, what are the operational and legal impacts to the
<b>data escrow policies</b>, if any.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Slide 15:</b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Question for Discussion </b><o:p></o:p></p>
<p class="MsoNormal"><b>Registry Data Escrow</b>: The <i>EPDP recommends that each gTLD and its variant labels (if any) are to be subject to one Registry Agreement with the same registry operator. Given this preliminary recommendation, do the technical specifications
and legal requirements of the data escrow policy for gTLDs need to be adjusted in order to account for the possibility of having more than one label under one registry agreement?
</i><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><u>Discussion</u>:<o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo1">Assumption: Data escrow requirements apply to each TLD variant.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo1">This is about ensuring that the data is available in circumstances where something goes astray. The registry operator can decide who their escrow provider is and this should be the
same for the TLD and its variants, but we may need to make the explicit.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo1">Having one escrow for the provider and its variants makes it easier from a tech perspective.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo1">Current design is that each TLD has to have a separate escrow contract. But, we shouldn’t try to require that all of the data of all the variants must be squeezed into the same file.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo1">In the escrow definition there is a field for variants.
<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo1">Wonder if we should provide implementation guidance about keeping the current practice of separate files for each TLD.
<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo1">Suggestion: Don’t see changes to the current practice of each TLD having its own data escrow provider, just that it must be the same provider for the variant subset under a TLD.<o:p></o:p></li></ul>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">5. Feedback from Chinese, Japanese, and Korean Generation Panels - A7 Part 2 (10 mins)<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Slide 17:</b><o:p></o:p></p>
<p class="MsoNormal"><b> </b><o:p></o:p></p>
<p class="MsoNormal"><b>Charter Question A7:</b> What mechanism or criteria should be used to identify the scripts/languages appropriate for single-character TLDs? Once those scripts/languages are identified, what mechanism or criteria should be used to identify
a specific list of allowable characters which can be used as a single-character TLD within such scripts/languages? Should any specific implementation guidance be provided? Furthermore, should the relevant GP tag these code points in the RZ-LGR for a consistent
analysis and to ease their identification and algorithmic calculation?<o:p></o:p></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><b>Slide 18:</b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><b> </b><o:p></o:p></p>
<p class="MsoNormal"><b>Q1. What is the definition of ideograph or ideogram? </b><o:p></o:p></p>
<p class="MsoNormal"><b>1a. Based on this definition, are all Han characters considered ideograph or ideogram? </b><o:p></o:p></p>
<p class="MsoNormal"><b>1b. If not, does the definition clearly provide a way to identify which Han characters are ideograph or ideogram?</b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Chinese (Chair response)</b>: All Han characters are ideographs
<o:p></o:p></p>
<p class="MsoNormal"><b>Japanese (GP response)</b>: <b>Except for “</b><b><span lang="ZH-CN" style="font-family:"MS Gothic"">々</span>” (U+3005)</b>, all Han (Kanji) characters are ideographs<o:p></o:p></p>
<p class="MsoNormal"><b>Korean (GP response)</b>: All Han (Hanja) characters are ideographs
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Slide 19:</b><o:p></o:p></p>
<p class="MsoNormal"><b> </b><o:p></o:p></p>
<p class="MsoNormal"><b>GP Outreach: Questions 2 & 3: </b><o:p></o:p></p>
<p class="MsoNormal"><b> </b><o:p></o:p></p>
<p class="MsoNormal"><b>Q2. Is it possible for the three GPs to coordinate and develop criteria by which to identify a subset of the Han script allowed for single-character gTLDs that present no risk of user confusion? Alternatively, is it possible to develop
criteria by which to identify a list of Han characters that may introduce confusion risks that rise above commonplace similarities and should NOT be allowed for single-character gTLDs? </b><o:p></o:p></p>
<p class="MsoNormal"><b>Q3. Is it possible for the three GPs to coordinate and develop criteria for the evaluation of future single-character gTLD applications in Han script, particularly in the context of string confusion, to ensure they are introduced to
the root-zone in a conservative manner? </b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Chinese (Chair response)</b>: <o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="mso-list:l5 level1 lfo4">Difficult for three GPs to coordinate but may not be necessary as applications need to follow language rules not script rules <o:p></o:p></li><li class="MsoNormal" style="mso-list:l5 level1 lfo4">Chinese-GP variant rules have eliminated the possibility of confusion risk to the maximum extent<o:p></o:p></li><li class="MsoNormal" style="mso-list:l5 level1 lfo4"><b>Family name characters </b>
and <b>geo-location name characters</b> are most liked be applied as single character TLD<o:p></o:p></li></ul>
<p class="MsoNormal">Not all Han characters are suitable to be applied as a single character TLD. E.g.,
<span lang="ZH-CN" style="font-family:"MS Gothic"">丿</span> (U+4E3F), <span lang="ZH-CN" style="font-family:"MS Gothic"">
乀</span> (U+4E40), <span lang="ZH-CN" style="font-family:"MS Gothic"">乁</span> (U+4E41) are used as
<b>basic radicals rather than full characters with semantic meaning</b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Japanese (GP response)</b>:<o:p></o:p></p>
<p class="MsoNormal">It may be safer to <b>disallow Han characters that are defined as visually identical to Kana characters</b> in Japanese RZ-LGR (see
<a href="https://www.icann.org/en/system/files/files/proposal-japanese-lgr-20dec21-en.pdf#page=14">
Section 7</a>), but it is up to Integration Panel and ICANN to decide <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Korean (GP response)</b>: <o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="mso-list:l3 level1 lfo5">Several Hanja characters have the
<b>same pronunciation</b>, and there may be risk to cause confusion <o:p></o:p></li><li class="MsoNormal" style="mso-list:l3 level1 lfo5">Korean GP is willing to participate in further discussion about these criteria
<o:p></o:p></li></ul>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Slide 20: </b><o:p></o:p></p>
<p class="MsoNormal"><b> </b><o:p></o:p></p>
<p class="MsoNormal"><b>GP Outreach: Question 4:</b><o:p></o:p></p>
<p class="MsoNormal"><b> </b><o:p></o:p></p>
<p class="MsoNormal"><b>Q4. Is it feasible for the three GPs to reconvene to conduct the above mentioned work, and if so, what is the estimated level of effort and time required.
</b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Chinese (Chair response)</b>: A six-month period may be needed to generate a limited allowable list from the most conservative perspective<o:p></o:p></p>
<p class="MsoNormal"><b>Japanese (GP response)</b>: No answer <o:p></o:p></p>
<p class="MsoNormal"><b>Korean (GP response)</b>: Not sure how long it will take<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Reminder that these are preliminary responses with the with an eye towards future coordination work to develop more full answers, but these are just the preliminary responses from the GP chairs.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Observations from Sarmad Hussain, Staff:<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo6">Some general principles: For example, one principle is that if there is a character in Han script which may actually look similar to another character in another script example being
Han or Congee character looking the same in as Congee characters in Japanese there may be a motivation to not include those characters in a single-character TLDs because, since there is no context available there is a possibility that that single character
can be interpreted as the character in the other script, which means that we are possibly at least visually allowing a TLD which is probably a visual point of view – from a technical point of view. So that’s one.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo6">A principle in the Japanese case was one more point, which is not included here, that's kind of a second principle which is also common with Chinese that there are some other characters
which may not qualify for single character for various reasons. One reason provided by Chinese cases that there are some basic radicals, which don't have a semantic meaning so they're not really into graphic in that sense.
<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo6">The other example which is not here, but shared by Japanese was the iteration mark where iteration mark means, of course, that it says that the character, before it is should be repeated,
so it has to come after a character, it cannot come by itself. Because, then you don't really know what is being iterated so you shouldn't really make a single-character TLD with an iteration mark so that's another kind of principle which is coming out.
<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo6">Korean case is a little more challenging because in in addition to visual sort of similarity you know string similarity is largely motivated by visual sort of analysis, but they are
now going into pronunciation which is not entirely visual so that's sort of a discussion which we need to have, and also the need to have that whether such a criteria should be eligible for string similarity cases or not and so those are some of the points
looking at it from a big picture point of view – what this also means is that there is really work which needs to be done by the GPs by these communities as well as perhaps the PDP working group to either document the principles or document the data or a combination
of both to guide the strings similarity review process.<o:p></o:p></li></ul>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><u>Discussion</u>:<o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo7">Wondering whether we can consider having implementation guidance, or even a recommendation, in principle, to say that support the efforts of the C, J, K GPs to develop the criteria
in order for the evaluation to be done, prior to the next round, so that there's a mechanism by which the evaluators can rely on to evaluate whether particular application for a single character TLDs is allowable or not.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo7">Another way to look or approach this is that the PDP now has these preliminary responses from the three GPs and there's an indication at least that they seem to be willing to work
on the topic and willing to work together, even if it might be a little bit difficult so one of the plenary outcomes of this discussion could be that the PDP wants to request the GPs to undergo the more detailed work rather than just these preliminary responses
and then you know with the knowledge that again it's going to take a little bit of time, but basically the conclusion could be that the PDP team likes the direction of the analysis and but is now requesting the three GPs to undertake a more rigorous analysis
will work together to develop for answers and possibly the criteria.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo7">A possible way ahead is to actually go back to the GPs and request them to conduct that extra work, but when reaching out, I think it may be useful to make it clear what it is, I think
what is needed is the scope of the work. So, pronunciation, for example, a factor in determining confusability between 200 characters, that's something that the PDP working group should decide, or would decide that something which should be left to the generation
panel so some of this discussion I guess also would be helpful here, so that when we reach out to GPs, we reach out with a clear scope of work.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo7">Leadership could take the action to develop something to progress the outreach to the three GPs. Leadership can have a look at what's been provided in terms of input today and to see
how we want to scope the further outreach to the GPs to elaborate on what we think they need to do.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo7">Question re: the difference between Question 2 and 3: the difference between 2 and 3, is that 2 is looking at specific lists from two angles so 2 is a specific list of allowable or
potentially a list of not allowed, whereas 3 is more about general criteria that would allow for single character on script strings to be accepted and delegated -- so question 2 is about specific lists of strings either allowable or dis-allowable whereas
3 is more about general criteria<o:p></o:p></li></ul>
<p class="MsoListParagraph"> <o:p></o:p></p>
<p class="MsoNormal"><b>ACTION ITEM: Leadership and staff to develop a proposal to scope further outreach to the three GPs with respect to additional work.</b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">6. AOB (3 minutes): None.<o:p></o:p></p>
</div>
</body>
</html>