<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
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:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:858200342;
mso-list-type:hybrid;
mso-list-template-ids:1197368592 134807553 134807555 134807557 134807553 134807555 134807557 134807553 134807555 134807557;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:18.0pt;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:54.0pt;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:90.0pt;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:126.0pt;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:162.0pt;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:198.0pt;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:234.0pt;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:270.0pt;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:306.0pt;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:1273319496;
mso-list-type:hybrid;
mso-list-template-ids:-1785017668 134807567 134807577 134807579 134807567 134807577 134807579 134807567 134807577 134807579;}
@list l1:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:18.0pt;
text-indent:-18.0pt;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:54.0pt;
text-indent:-18.0pt;}
@list l1:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:90.0pt;
text-indent:-9.0pt;}
@list l1:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:126.0pt;
text-indent:-18.0pt;}
@list l1:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:162.0pt;
text-indent:-18.0pt;}
@list l1:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:198.0pt;
text-indent:-9.0pt;}
@list l1:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:234.0pt;
text-indent:-18.0pt;}
@list l1:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:270.0pt;
text-indent:-18.0pt;}
@list l1:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:306.0pt;
text-indent:-9.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style>
</head>
<body lang="en-BE" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">Dear all, <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">Please find below the notes and action items from today’s meeting on </span><span lang="EN-US" style="color:black;mso-fareast-language:EN-GB">Thursday 9 September</span><span style="color:black;mso-fareast-language:EN-GB"> 2021
at </span><span lang="EN-US" style="color:black;mso-fareast-language:EN-GB">13:00</span><span style="color:black;mso-fareast-language:EN-GB"> UTC.</span><span style="mso-fareast-language:EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Emily, Steve and Marika<o:p></o:p></span></p>
<div style="mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.5pt;padding:0cm 0cm 1.0pt 0cm">
<p class="MsoNormal" style="border:none;padding:0cm"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US">Action item</span></b><span lang="EN-US">
<b>#1</b>: RySG and ccNSO members on the IDN EPDP to check with their Stakeholder Group to see if there are any concerns about using the RZ-LGR for existing gTLDs (charter questions a1 and a2).
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US">Action item #2</span></b><span lang="EN-US">: Team to review Data and Metrics requirements in the charter and indicate whether any of the items identified are NOT necessary and/or which items are missing.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US">Action item #3</span></b><span lang="EN-US">: In advance of the next meeting, in preparation for further review of A3, please review the SubPro Limited Challenge / Appeal Mechanism as well as the appealing via the
integration panel in the context of the RZ-LGR. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US">Action item #4</span></b><span lang="EN-US">: For those that have not done so yet, please review all the introductory materials and sign off via the google sheet (see
<a href="https://docs.google.com/forms/d/e/1FAIpQLSfbXhd2L4oAb_Cn22FnjkSoDSj0K-HNcijDZDW_zpvseqXH8A/viewform">
https://docs.google.com/forms/d/e/1FAIpQLSfbXhd2L4oAb_Cn22FnjkSoDSj0K-HNcijDZDW_zpvseqXH8A/viewform</a>).
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><u><span lang="EN-US">Notes – IDNs EPDP Call – 9 September 2021<o:p></o:p></span></u></b></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US">Welcome & Chair Updates<o:p></o:p></span></b></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<ol style="margin-top:0cm" start="1" type="1">
<li class="MsoListParagraphCxSpFirst" style="margin-left:-18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo1">
<span lang="EN-US" style="font-size:11.0pt">Workplan is under development, informed by the survey taken during the last meetings. Leadership and staff support team expect to be able to circulate proposed work plan before the next meeting and will set aside
time next week for review and discussion.<o:p></o:p></span></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:-18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo1">
<span lang="EN-US" style="font-size:11.0pt">EoI for Chair is still open until September 15. For those interested, please make sure to submit your application.
<o:p></o:p></span></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:-18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo1">
<span lang="EN-US" style="font-size:11.0pt">As the team goes through the topics there may be need to collect data and metrics, to inform team’s deliberations/decisions. This could result in having to park certain items until that data is obtained. Team may
need to review / discuss what further data may be necessary. ICANN org has agreed to collect any necessary data.
<o:p></o:p></span></li><li class="MsoListParagraphCxSpLast" style="margin-left:-18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo1">
<span lang="EN-US" style="font-size:11.0pt">Edmon has spoken to ICANN legal and BGC chair who did not express any concern about his chairing this group until taking up his position. Furthermore, if the group is interested, Edmon could be invited back as a Board
liaison to this EPDP team. EPDP Team to indicate if there is support and/or concerns about this option.
<o:p></o:p></span></li></ol>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US">Begin deliberations on Topic A: Consistent definition and technical utilization of RZ-LGR<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span lang="EN-US"><o:p> </o:p></span></b></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraphCxSpFirst" style="margin-left:-18.0pt;mso-add-space:auto;mso-list:l0 level1 lfo2">
<span lang="EN-US" style="font-size:11.0pt">See charter<o:p></o:p></span></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:-18.0pt;mso-add-space:auto;mso-list:l0 level1 lfo2">
<span lang="EN-US" style="font-size:11.0pt">First question is whether EPDP Team is willing to accept RZ-LGR as the authoritative source to ensure a consistent approach for reviewing current and future TLDs. For existing delegated gTLD labels, does the Team
recommend using the RZ-LGR as the sole source to calculate the variant labels and disposition values? This may require some research to determine whether this would cause any potential issues for existing gTLDs.
<o:p></o:p></span></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:-18.0pt;mso-add-space:auto;mso-list:l0 level1 lfo2">
<span lang="EN-US" style="font-size:11.0pt">Maybe the question should be the other way around – is there any reason NOT to use it?
<o:p></o:p></span></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:-18.0pt;mso-add-space:auto;mso-list:l0 level1 lfo2">
<span lang="EN-US" style="font-size:11.0pt">See also the mapping document – SubPro and the TSG recommendations are consistent in exclusively using the RZ-LGR.
<o:p></o:p></span></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:-18.0pt;mso-add-space:auto;mso-list:l0 level1 lfo2">
<span lang="EN-US" style="font-size:11.0pt">Important to consult technical teams of registries and back-end providers. Suggestion to request the opinion of registries (both gTLD and ccTLD) as previous studies were conducted by technical experts, not registries.
<o:p></o:p></span></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:-18.0pt;mso-add-space:auto;mso-list:l0 level1 lfo2">
<span lang="EN-US" style="font-size:11.0pt">Note that early request for input will take place, which will focus on general questions. Need to consider whether separate targeted outreach is needed, also factoring in that registries are represented in that effort.
Those members may be able to bring back any relevant perspectives or input to the group as well.
<o:p></o:p></span></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:-18.0pt;mso-add-space:auto;mso-list:l0 level1 lfo2">
<span lang="EN-US" style="font-size:11.0pt">Is it worth for the staff support team to undertake a bit of data gathering to see which, if any, gTLDs would be affected?<o:p></o:p></span></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:-18.0pt;mso-add-space:auto;mso-list:l0 level1 lfo2">
<span lang="EN-US" style="font-size:11.0pt">May need to continue with a2 until data has been gathered to respond to question a1? May need further info on potential inconsistencies as the questions in the charter question are hypothetical at the moment?
<o:p></o:p></span></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:-18.0pt;mso-add-space:auto;mso-list:l0 level1 lfo2">
<span lang="EN-US" style="font-size:11.0pt">Probably three data points that would need to be gathered: 1) Are existing top-level domains valid based on the RZ-LGR? 2) Are variants that are identified determined via RZ-LGR and if not how are they different,
3) When variants are allocated to the rootzone LGR, were the self-identified variant labels taken into account?
<o:p></o:p></span></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:-18.0pt;mso-add-space:auto;mso-list:l0 level1 lfo2">
<span lang="EN-US" style="font-size:11.0pt">What is the process for requesting staff to gather this data? Note that the charter already identified data that might be helpful, but also noted that if additional data was needed, the group should request this.
There is a form that would need to be completed to request ICANN org to gather this data, outlining what data is needed and why. If an external vendor is required, budget approval may be involved. If the data needed was already identified in the charter, Team
can just confirm the data would be helpful and staff support team would action it.
<o:p></o:p></span></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:-18.0pt;mso-add-space:auto;mso-list:l0 level1 lfo2">
<span lang="EN-US" style="font-size:11.0pt">Would it be helpful to identify the overall data needs, or better / easier to do this as the group goes through the charter questions? Might be better to batch them, but helpful for members and participants to go
through the charter and identify any required data in advance. <o:p></o:p></span></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:-18.0pt;mso-add-space:auto;mso-list:l0 level1 lfo2">
<span lang="EN-US" style="font-size:11.0pt">Reminder, homework assignment was for members and participants to identify whether anything was omitted in the Data and Metrics requirements in the charter. Team may want to consider looking at what is in there and
sign off on it so that the staff support team can go ahead with collecting the data? Preferred approach is to keep on going through the charter so that the context is clear and specific data needed can be identified and linked to specific questions, but a
batch approach may be used so that the data gathering process can already start and doesn’t have to wait until all charter questions have been reviewed.
<o:p></o:p></span></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:-18.0pt;mso-add-space:auto;mso-list:l0 level1 lfo2">
<span lang="EN-US" style="font-size:11.0pt">What if there are inconsistencies with existing gTLDs? Either they have to fix it or team decides that use of RZ-LGR is not required in certain circumstances. May need to look at language on self-identified variants
in the applicant guidebook (see (<a href="https://newgtlds.icann.org/en/applicants/agb" target="_blank"><span style="color:windowtext;text-decoration:none">https://newgtlds.icann.org/en/applicants/agb</span></a>) (pg 1-36).
</span><span style="font-size:11.0pt;font-family:"Times New Roman",serif;mso-fareast-language:EN-GB"><o:p></o:p></span></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:-18.0pt;mso-add-space:auto;mso-list:l0 level1 lfo2">
<span lang="EN-US" style="font-size:11.0pt">May need to consider what harm would be caused by a potential inconsistencies.
<o:p></o:p></span></li><li class="MsoListParagraphCxSpLast" style="margin-left:-18.0pt;mso-add-space:auto;mso-list:l0 level1 lfo2">
<span lang="EN-US" style="font-size:11.0pt">A3 – Should the appeal process that was developed by SubPro be expanded to existing TLDs (Limited Challenge / Appeal Mechanism – see chart included in the SubPro Final Report on page 329)? On what grounds would the
challenge be accepted or would the applicant succeed. Reminder for Team to review the SubPro recommendations on this topic (see also mapping document). Note also process build into RZ-LGR (see
<a href="https://www.icann.org/en/system/files/files/lgr-procedure-20mar13-en.pdf">
https://www.icann.org/en/system/files/files/lgr-procedure-20mar13-en.pdf</a>). Team to consider if, when and how to call upon these existing mechanisms and how these would interact.
<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</body>
</html>