<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Times New Roman \(Body CS\)";
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Arial",sans-serif;
color:windowtext;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
.MsoChpDefault
{mso-style-type:export-only;
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:784926987;
mso-list-template-ids:308989282;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:1528523475;
mso-list-template-ids:-245722084;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
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">
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Hi All,<o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Please find below the notes and action items from last Thursday’s (Feb 8, 2024)<span class="apple-converted-space"> </span><a href="https://community.icann.org/x/d4D6EQ">IDN EPDP Meeting
#105</a><o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"> <o:p></o:p></span></p>
<div style="mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal" style="border:none;padding:0in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Thanks!<br>
Ariel, Steve, Saewon, and Dan<o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">ACTION ITEMS</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Leadership and the registries will review the D8 Team Response comments and get back to the team.<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Staff will update D8 EPDP Team response to clarify #3 to “3) The source domain name used to calculate the variant set that the queried domain name is a part of, if applicable"<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Staff will look at PR 6 to incorporate “there is some view” instead of “some members<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The team will review the glossary before the next call and update the document accordingly<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Staff will revise text in Rec 13 to remove the clause about the accuracy between the HTML and TXT versions of the Root Zone Database<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Staff will remove IG 9 in response to ICANN org comments. <o:p></o:p></span></li></ul>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">NOTES</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Roll call and SOI updates (2 min)<o:p></o:p></span></li></ul>
<ul type="disc">
<ul type="circle">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">There was an SOI update from Anil Kumar Jain.<o:p></o:p></span></li></ul>
</ul>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Welcome and chair updates (5 min)<o:p></o:p></span></li></ul>
<ul type="disc">
<ul type="circle">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The chair welcomed everyone to the call and noted the greater than usual amount of apologies due to the lunar new year.<o:p></o:p></span></li></ul>
</ul>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Second reading of draft recommendation text & glossary – review of input received (60 min)<o:p></o:p></span></li></ul>
<ul type="disc">
<ul type="circle">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Leadership and staff are still waiting on Team feedback on harmonization tables<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Comments were received for the D8 EPDP Team Response<o:p></o:p></span></li></ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level3 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Does the team want to make any rules regarding querying a domain that is not registered / allocated, but has allocated variants?<o:p></o:p></span></li></ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level4 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">This may depend on how registry systems work and it also might already be accounted for.<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level4 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">If non registered domain names should be included, there should be further explanation. When talking about RDAP in other areas it is not explicitly stated that it means <o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level5 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">If the team wants to include all allocated variant domain names, then they should include them all and not just a subset of the listing, per a participant and later echoed by another.<o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level4 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Since we are talking about the variant set, then all variants under variant TLDs should be included. The source domain name under the TLD should be included at a minimum, variant TLDs should be included
in RDAP. <o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level4 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">If RDAP requests are per TLD, what kind of complexities are being added? <o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level4 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">This could potentially be too heavy of a lift for registries?<o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level5 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">From chat: ”without response to domains that are un"registered" but actually in an existing domain registration set of variants would add a huge burden on registrar systems actually”<o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level4 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Potentially a minimal recommendation that says something along the lines of “it would be good to encapsulate the variant domain set” but the team will not be sure if this is necessary until a better
understanding of the concept is achieved.<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level4 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Does the team have an agreement on a preliminary recommendation? Initial thoughts include potentially keeping the text as is and leadership will discuss a path forward.<o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level5 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Does the context for “domain name” need to change in the first line of the D8 Team Response?<o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level4 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">ACTION ITEM: Leadership and the registries will review the D8 Team Response comments and get back to the team.<o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level3 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Comments were also received to improve on subsection 3 in the first bullet on calculating the variant domain set.<o:p></o:p></span></li></ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level4 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">"3) The source domain name used to calculate the variant set that the queried domain name is a part of, if applicable"<o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level5 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">This suggestion was Accepted by the team<o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<ul type="square">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level6 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">ACTION ITEM: Staff will update D8 EPDP Team response to clarify #3 to “3) The source domain name used to calculate the variant set that the queried domain name is a part of, if applicable"<o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">There was a question about the process about GNSO and ccNSO PDP mechanisms.<o:p></o:p></span></li></ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level3 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The GNSO PDP does not impact the ccNSO. The consequences are different and they do not have to abide by what is made in this group.<o:p></o:p></span></li></ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">There was an edit made to PR 5 during the call to reflect best practices in RFC 2119. <o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Under the Rationale for PR 5, there were discussions over redline text. There was agreement from the team to accept the redline text under this section.<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Under the Rationale for PR 6 there was a discussion about the use of “some members” in the text. This could be tweaked to sound a bit better. <o:p></o:p></span></li></ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level3 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">ACTION ITEM: Staff will look at PR 6 to incorporate “there is some view” instead of “some members”<o:p></o:p></span></li></ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">ACTION ITEM: The team will review the glossary before the next call and update the document accordingly. <o:p></o:p></span></li></ul>
</ul>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Review of ICANN org SMEs’ comments for draft recommendations (20 min)<o:p></o:p></span></li></ul>
<ul type="disc">
<ul type="circle">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">There was additional feedback from SMEs within ICANN that will be considered regarding the TMCH on charter question F1.<o:p></o:p></span></li></ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level3 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The registries that have established variant registration policies essentially concern both ROs that block variants and those that allow activation. There is the possibility that there could be allocation
without activation.<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level3 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Per Section 4.1.3 of the Trademark Clearinghouse Rights Protection Mechanism Requirements, the RO, in both situations (block variants vs. activate variants), needs to check all labels (i.e., allocatable
and blocked) in a variant label set against the Domain Name List recorded in the TMCH before any domain names from the set are registered.<o:p></o:p></span></li></ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level4 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">There was a question from a team member if this is just for registries that activate variants?<o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level5 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">No.<o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level4 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The suggested action for this recommendation is to not make any changes to the text. A footnote could be created for context but that is not necessary.<o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level5 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Agreement from the team was given for this recommendation of no action<o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Regarding Recommendations 12 and 13, IANA Staff members provided feedback<o:p></o:p></span></li></ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level3 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">On Rec 12: There are no plans to implement an RDAP server at the IANA level for variant TLDs. <o:p></o:p></span></li></ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level4 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">No concerns about the recommendations but wanted to clarify a comment <o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level4 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">From a team member, there are questions about implementation. Will the team have to go back and reinvent the wheel? Is it possible for the EPDP to develop technical standards? Based on the comments
from IANA there are different opinions on how to proceed.<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level4 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">From a leadership perspective, there is no action required. Potential benefit to make the recommendation clearer relating to the intent, but not necessary at this time.<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level4 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The Chair asked the team if somebody was to query a domain through RDAP and it turned out to be an unallocated variant, could someone attempt to register that domain?<o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level5 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The understanding is that the registrant would have to be the person for whom the variant is reserved. Due to the same entity principle, if there is an existing domain in the variant set, it would
be reserved for whoever owns the entity.<o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<ul type="square">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level6 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">By adding things onto RDAP that don’t create value, is the team spending its time wisely?<o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<ul type="square">
<ul type="square">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level7 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">It could add value if you could query non existing domain names. If a set exists, but a variant is unregistered, it would be beneficial to users for them to see that in a query of all of the variant
set. <o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
</ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<ul type="square">
<ul type="square">
<ul type="square">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level8 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Users can make any query, it's up to the registry / registrar on how to answer. Some TLDs answer that a string cannot be registered or reserved. Some do not because they do not have to. It is up
to the contracted party to give the level of detail requested by the Chair.<o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
</ul>
</ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level3 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">On Rec 13: There were concerns about a comment in the rationale for Recommendation 13. During the workshop it was discussed the accuracy between the HTML and TXT versions of the Root Zone Database.
IANA disagrees with this characterization. <o:p></o:p></span></li></ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level4 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Staff asked if the rationale should be modified in Rec 13 to account for IANA comments?<o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level5 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The chair is in favor of removing the rationale text in Rec 13 as it is not necessary for the text and the team agreed.<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level5 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">ACTION ITEM: Staff will revise text in Rec 13 to remove the part about the accuracy between the HTML and TXT versions of the Root Zone Database.<o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level3 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">On Rec 8 and IG 9, There were IANA staff comments that IG 9 would delay Rec 8. Staff asked the team if they would require IG 9?<o:p></o:p></span></li></ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level4 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Leadership is in favor of removing IG 9 as it is unclear if it's beneficial at this time. <o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level5 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The team agreed. Since it is already a “Should” clause and already weak<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level5 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">As it is already written, it can be interpreted that this should be delayed pending the URDP review, but that is not the intent of the team.<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level5 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">ACTION ITEM: Staff will remove IG 9 in response to ICANN org comments. <o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
</ul>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Update from ccPDP4 on Preliminary Recommendations 14 (10 min)<o:p></o:p></span></li></ul>
<ul type="disc">
<ul type="circle">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">ccPDP4 welcomed EPDP IDN policy staff to present to their group and provide an introduction to the preliminary recommendation. The ccPDP4 team will present to the ccNSO council and there should be
an update from the ccNSO and ccPDP4 team by Friday, 16 Feb. <o:p></o:p></span></li></ul>
</ul>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Draft section to address deferred guidelines from IDN Implementation Guidelines version 4.0 (20 min)<o:p></o:p></span></li></ul>
<ul type="disc">
<ul type="circle">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">For Implementation Guidance 15, There was a question if automatic activation should be allowed or be only considered for where generally the community agrees with the need?<o:p></o:p></span></li></ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level3 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">This was raised because automatic registration poses a challenge for registrants (Someone applies for 1 and gets 4, can be challenging to manage). SAC060 notes this challenge. <o:p></o:p></span></li></ul>
</ul>
</ul>
<ul type="disc">
<ul type="circle">
<ul type="square">
<ul type="square">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level4 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Some comments from the team said they could see the reasoning that some automatic activation could be sensible, but also that it should be restricted. <o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level4 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">May have an impact, for example, that a registrant applying for Simplified Chinese may want to automatically receive the Traditional Chinese variant automatically. In the IDNs guidelines, this was
only applicable to Chinese. <o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level4 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">There was a point that the team should not be overly prescriptive, specifically in implementation guidance. We could go further on IG 15.2, but also valid to not expand further.<o:p></o:p></span></li></ul>
</ul>
</ul>
</ul>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">AOB (3 min)<o:p></o:p></span></li></ul>
<ul type="disc">
<ul type="circle">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Next call will take place next week. Looking longer out, there will be two calls before ICANN79, with a meeting still planned for ICANN79. <o:p></o:p></span></li></ul>
</ul>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"></span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>
</div>
</div>
</body>
</html>