<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:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:238558681;
mso-list-type:hybrid;
mso-list-template-ids:1978433018 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0: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 l0: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 l0: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 l0: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 l0: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 l0: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 l0: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 l0: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 l0: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 l1
{mso-list-id:901795831;
mso-list-type:hybrid;
mso-list-template-ids:-15058300 134807553 134807555 134807557 134807553 134807555 134807557 134807553 134807555 134807557;}
@list l1: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 l1: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 l1: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 l1: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 l1: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 l1: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 l1: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 l1: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 l1: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 l2
{mso-list-id:1254243026;
mso-list-type:hybrid;
mso-list-template-ids:-695286916 134807553 134807555 134807557 134807553 134807555 134807557 134807553 134807555 134807557;}
@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:1310983456;
mso-list-type:hybrid;
mso-list-template-ids:-1855399306 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l3: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 l3: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 l3: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 l3: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 l3: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 l3: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 l3: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 l3: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 l3: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 l4
{mso-list-id:2088262450;
mso-list-type:hybrid;
mso-list-template-ids:-1505182386 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l4: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 l4: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 l4: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 l4: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 l4: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 l4: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 l4: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 l4: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 l4: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 l5
{mso-list-id:2110462501;
mso-list-type:hybrid;
mso-list-template-ids:212477144 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l5: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 l5: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 l5: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 l5: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 l5: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 l5: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 l5: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 l5: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 l5: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;}
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="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">With apologies for the late delivery, please find below the notes and action items from Thursday’s meeting on 25 May 2023 at 12:00 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, Emily, and Steve<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="color:black"> </span></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><u><span style="color:black">Notes and Action Items - IDNs EPDP Call – 25 May 2023</span></u></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="color:black">Action Items<o:p></o:p></span></b></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo1">
None<o:p></o:p></li></ul>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="color:black">Notes<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><u><span style="color:black;mso-fareast-language:EN-GB">Roll Call and SOI Updates<o:p></o:p></span></u></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l5 level1 lfo2">
<span style="mso-fareast-language:EN-GB">None<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><u><span style="color:black;mso-fareast-language:EN-GB">Welcome and Chair Updates<o:p></o:p></span></u></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l5 level1 lfo2">
<span style="mso-fareast-language:EN-GB">Reminder that the Phase 1 Initial Report is out for public comment and there have been a couple of requests to extend the public comment period. Leadership is willing to extend to 19 June. No concerns expressed.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l5 level1 lfo2">
<span style="mso-fareast-language:EN-GB">Update from GNSO Council meeting – presented timeline for Phase 2 work which shows this team concluding in Oct 2025. No concerns expressed from Council. Noted that Phase 2 work has already started and making significant
progress, which was not planned to start until the end of 2023.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l5 level1 lfo2">
<span style="mso-fareast-language:EN-GB">However, unknown what the comments will look like for Phase 1. Depending on the comments received, it could impact timelines for delivering the Phase 1 Final Report by Nov 2023.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l5 level1 lfo2">
<span style="mso-fareast-language:EN-GB">Also requested Council consider a F2F meeting for this EPDP Team, which requires a 6-month lead time. Looking at Nov-Dec timeframe.<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><u><span style="color:black;mso-fareast-language:EN-GB">Same-entity charter questions (C1, C2, C3, C3a)<o:p></o:p></span></u></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB"><o:p> </o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l3 level1 lfo3">
<span style="mso-fareast-language:EN-GB">Slide 3: Reminder of what the charter questions are about.<o:p></o:p></span>
<ul style="margin-top:0in" type="circle">
<li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l3 level2 lfo3">
<span style="mso-fareast-language:EN-GB">C1 – extending the same entity principle to existing second-level labels.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l3 level2 lfo3">
<span style="mso-fareast-language:EN-GB">C2 – Consider what the definition should be for same-entity (e.g., registrant). Also asks what the impact might be for ROs that already have a contractual provision that allows them to allocate second-level variants.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l3 level2 lfo3">
<span style="mso-fareast-language:EN-GB">C3 – Assumes that the answers to C1 and C2 are yes, what object should be used to identify entities as being the same?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l3 level2 lfo3">
<span style="mso-fareast-language:EN-GB">There is also C3a, but that is dependent upon the group agreeing that ROID is the right mechanism.<o:p></o:p></span></li></ul>
</li></ul>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">C1<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l5 level1 lfo2">
<span style="mso-fareast-language:EN-GB">Slide 4: There are existing recommendations from SubPro that require second-level labels, in their various permutations (s1.t1, s1.t1v1 & s1, s1v1, … under t1, t1v1, …) must all be allocated only to the same entity.
These two recommendations have already been adopted by the ICANN Board and are currently in implementation. The question is essentially, should these recommendations be extended to existing second-level labels that already exist in the DNS?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l5 level1 lfo2">
<span style="mso-fareast-language:EN-GB">What might be helpful is to understand if registry/registrar colleagues can share their experiences. How easy is it to identify when there are variants and set them aside?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l5 level1 lfo2">
<span style="mso-fareast-language:EN-GB">Clarification that for this question, we only need to consider variants at the second-level, since top-level variants do not exist. So, we only need to consider example.tld, examplev1.tld, …<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l5 level1 lfo2">
<span style="mso-fareast-language:EN-GB">For the instances where example.tld, examplev1.tld are both already registered but to different registrants, suggestion that these should be grandfathered and not be forced to take one of them away from one of the entities.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l5 level1 lfo2">
<span style="mso-fareast-language:EN-GB">However, if only one of them is registered, do not see an issue with enforcing the same entity requirement going forward.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l5 level1 lfo2">
<span style="mso-fareast-language:EN-GB">Question about how difficult it is to set aside variants for second-level domains. Response is that it should not be difficult and that currently, many registries are likely already withholding variants.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l5 level1 lfo2">
<span style="mso-fareast-language:EN-GB">Support for grandfathering as removing rights from an existing registrant in favor of another may lead to legal issues. Not sure how easy it will be to identify all existing variants and maintain a database.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l5 level1 lfo2">
<span style="mso-fareast-language:EN-GB">Question about further actions registrars could take where second-level variants are registered by different registrants. One response is that registrars often just follow policies and the law, and would not do anything
additional.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l5 level1 lfo2">
<span style="mso-fareast-language:EN-GB">Another question about grandfathering instances where there are two or more registrants for variants of each other. What happens on an ongoing basis?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l5 level1 lfo2">
<span style="mso-fareast-language:EN-GB">Suggestion that grandfathering should be a temporary situation that should be rectified as soon as possible. And that for any other allocatable variants, they should remain withheld so as to avoid making the grandfathering
issue worse. Some others agree with this approach as allowing additional variants to be registered will perpetuate the conflict with the policy.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l5 level1 lfo2">
<span style="mso-fareast-language:EN-GB">Only when the grandfathering situation is removed should the variants become available again.<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">C2<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l1 level1 lfo4">
<span style="mso-fareast-language:EN-GB">Slide 6 – reviewed existing contractual language that allows for the activation of variants. These requirements state that it must be the sponsoring registrar of the canonical name requesting activation and they must
have the same NS resource records, but do not require the same entity.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l1 level1 lfo4">
<span style="mso-fareast-language:EN-GB">The question here is whether the same entity principle should apply to existing second-level domains where variants are held by more than one registrant. The question is directly related to much of the EPDP Team’s discussions
so far in this meeting. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l1 level1 lfo4">
<span style="mso-fareast-language:EN-GB">Suggestion that allowing additional variants to continue to be registered doesn’t make the problem worse (where there are two or more registrants for variants of each other). Concerns about to withhold until the issue
is resolved creates uncertainty. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l1 level1 lfo4">
<span style="mso-fareast-language:EN-GB">Noted that allowing additional variants makes resolving the grandfathering issue more difficult to resolve.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l1 level1 lfo4">
<span style="mso-fareast-language:EN-GB">There is no data available about how many instances there are of variants being held my 2 or more registrants.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l1 level1 lfo4">
<span style="mso-fareast-language:EN-GB">Registrants are potentially being disadvantaged by not being allowed to register additional variants. The grandfathering can still be unwound if the set of variants is reduced to a single registrant.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l1 level1 lfo4">
<span style="mso-fareast-language:EN-GB">Example shared for clarification: There are 4 labels that are variants of each other with two of them registered to two separate registrants. The suggestion from some is that the two unregistered variants should remain
unregistered until the grandfathering need is removed.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l1 level1 lfo4">
<span style="mso-fareast-language:EN-GB">Allowing variants in this situation doesn’t change the scenario, there are 2 or more registrants for variants of each other.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l1 level1 lfo4">
<span style="mso-fareast-language:EN-GB">Grandfathering is to take account of the existing state. It should not be considered forward looking to create more grandfathering complexities. It also seems to allow for the violation of the same-entity principles.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l1 level1 lfo4">
<span style="mso-fareast-language:EN-GB">Not sure the same entity principle is broken by allowing additional variants to be registered in a grandfathering situation.<br>
Summary of discussions to date: it seems like agreement that the same entity principle should be extended to existing registrations. And it seems like agreement that there should be grandfathering. The remaining questions are around the grandfathering rules.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l1 level1 lfo4">
<span style="mso-fareast-language:EN-GB">Good stopping point for this first discussion and pursue next meeting.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l1 level1 lfo4">
<span style="mso-fareast-language:EN-GB">There is a second piece of C2 to consider which is the impact of the same entity requirement for existing registries that already have the contractual allowance to activate variants. That contractual allowance is different
than the same entity requirement.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l1 level1 lfo4">
<span style="mso-fareast-language:EN-GB">Initial thought is that since this consensus policy, ROs will need to comply with it. The existing requirements and new consensus policy will need to be consistent.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l1 level1 lfo4">
<span style="mso-fareast-language:EN-GB">Further, there is a feeling that the existing requirements are compatible – could therefore add an additional provision that requires the same registrant.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l1 level1 lfo4">
<span style="mso-fareast-language:EN-GB">Discussion whether it should be registrant or legal entity, or both. Comes back to what is commonly understood as what is a registrant. Same entity is same registrant, is the same applicant. Need to define what we mean
by same registrant or same entity. Details that need to be included. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l1 level1 lfo4">
<span style="mso-fareast-language:EN-GB">A registrant (contact) can also represent a legal body or person or both.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l1 level1 lfo4">
<span style="mso-fareast-language:EN-GB">The requirement could be for the same entity, but do not specify the method to ensure the same entity.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l1 level1 lfo4">
<span style="mso-fareast-language:EN-GB">Should existing Ros that already have this contractual amendment be required to rely on the same entity principle to allocate or withhold for allocation second-level variants int the future? – answer is yes. Will discuss
during leadership team where to go next.<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><u><span style="color:black;mso-fareast-language:EN-GB">Dialogue with SSAC SMEs<o:p></o:p></span></u></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB"><o:p> </o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l2 level1 lfo5">
<span style="mso-fareast-language:EN-GB">Lyman Chapin, John Levine, Jim Galvin, Jiankang Yao and Jaap Akkerhuis from SSAC joined the conversation<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l2 level1 lfo5">
<span style="mso-fareast-language:EN-GB">Purpose of reaching out to SSAC is following publication of the Initial Report to see if there are any security and stability concerns. Getting a heads up may facilitate reconciling public comment input.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l2 level1 lfo5">
<span style="mso-fareast-language:EN-GB">General feedback from SSAC SMEs: Although as individuals have strongly held opinions on some of these topics, as variants do not exist at the DNS level, it is not likely one where SSAC will have specific comments on
many of the recommendations as these are mainly focused on the user experience and not the technical level.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l2 level1 lfo5">
<span style="mso-fareast-language:EN-GB">SSAC SME feedback: Re. Preliminary Recommendation 8.1 - SSAC60 and the follow up comments is to advocate the conservatism approach because there may be permutation effects at the top level and then the second and third
level. Understanding from the GNSO deliberation where that conservatism will be achieved will be what the SSAC would be interested in seeing. Need to assess whether the measures in place will result in conservative activation of variants. Economic factor may
determine number of variants that will allocated. For second level they could be sold as a package? Maybe for this a ceiling value should be considered to ensure conservatism?
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l2 level1 lfo5">
<span style="mso-fareast-language:EN-GB">Chair confirmed that the IDN EPDP team has taken a conservative approach recognizing that variants have not been introduced before. Anticipate that reality will be fairly conservative as only Arabic doesn’t have a limit
on the variant labels that can be available at the top-level. Have reached out to the Arabic script level to see if they could assist with what would be a reasonable ceiling.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l2 level1 lfo5">
<span style="mso-fareast-language:EN-GB">SSAC SME feedback re. Preliminary recommendation 3.7: In relation to 3.7, the SSAC comments on SubPro essentially said the same as preliminary rec 3.7 so there does seem to be consistency.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l2 level1 lfo5">
<span style="mso-fareast-language:EN-GB">Response: no upper bound on total number of TLDs is in line with the variant approach. If someone wants to pay for 1,000 variant TLDs they can do so similar to how someone can apply for 1,000 TLDs that are not variants.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l2 level1 lfo5">
<span style="mso-fareast-language:EN-GB">SSAC SME feedback re. preliminary recommendation 8.7: there needs to be a transparent process to update the LZ-LGR.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l2 level1 lfo5">
<span style="mso-fareast-language:EN-GB">SSAC will take question about providing feedback back. SSAC 60 and SAC120 did already provide input, but review if further input is deemed necessary. Domain name itself consists of top level and second level so permutations
are a potential concern for SSAC. Appreciate that the GNSO has reached out in good faith to engage with SSAC on this topic.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l2 level1 lfo5">
<span style="mso-fareast-language:EN-GB">Reminder that public comment period is still open – if SSAC has further input, will try to submit by the deadline.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l2 level1 lfo5">
<span style="mso-fareast-language:EN-GB">SAC120 highlights importance of ensuring usage of variants. Preliminary recommendation 3.5 provides for explanation for why variants are needed. Others may come into play as well, for example delegation within a certain
period of time. <o:p></o:p></span></li></ul>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><u><span style="color:black;mso-fareast-language:EN-GB">AOB<o:p></o:p></span></u></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-left:0in;mso-add-space:auto;mso-list:l4 level1 lfo6">
<span style="mso-fareast-language:EN-GB">None<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="color:black"> </span></b><span style="color:black"><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>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;color:black">Steven Chan</span></b><b><span style="font-size:10.0pt;font-family:"MS Gothic";color:black">
</span></b><span style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:black">Senior Director, Policy Development Support & GNSO Relations<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:black">Internet Corporation for Assigned Names and Numbers (ICANN) <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:black">12025 Waterfront Drive, Suite 300<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:black">Los Angeles, CA 90094-2536</span><span style="font-size:10.0pt;font-family:"MS Gothic";color:black">
</span><span style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:black">Email: <a href="mailto:steve.chan@icann.org" title="mailto:steve.chan@icann.org"><span style="color:#0563C1">steve.chan@icann.org</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:black">Skype: steve.chan55<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:black">Mobile: +1.310.339.4410<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:black">Find out more about the GNSO by visiting: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=o7Auz997kA-HPv9PHJCjFVZw7Pgo8krw4MxfqCwBrIU&e=" title="https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=o7Auz997kA-HPv9PHJCjFVZw7Pgo8krw4Mxf"><span style="color:#0563C1">https://learn.icann.org/</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:black">Follow @GNSO on Twitter: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNSO&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=kWw4fQPNjw2lVKy1UjTxS2F0BmjEAzaDFWNmsYywbmE&e=" title="https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNSO&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=kWw4fQPNjw2lVKy1UjTxS2F0BmjE"><span style="color:#0563C1">https://twitter.com/ICANN_GNSO</span></a><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;color:black">Transcripts and recordings of GNSO Working Group and Council events are located on the <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_group-2Dactivities_calendar&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=-L6chFfv0OperrXHHpTF722WnH3FZIutn4cS16IvpOg&e=" title="https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_group-2Dactivities_calendar&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=-L6chFf"><span style="color:#0563C1">GNSO
Master Calendar</span><span style="color:#954F72"> </span></a></span><o:p></o:p></p>
</div>
</body>
</html>