<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;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
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:1022586513;
mso-list-template-ids:-370220986;}
@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:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@list l1
{mso-list-id:1073350972;
mso-list-type:hybrid;
mso-list-template-ids:-638177064 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:38.25pt;
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;
margin-left:74.25pt;
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;
margin-left:110.25pt;
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;
margin-left:146.25pt;
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;
margin-left:182.25pt;
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;
margin-left:218.25pt;
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;
margin-left:254.25pt;
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;
margin-left:290.25pt;
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;
margin-left:326.25pt;
text-indent:-.25in;
font-family:Wingdings;}
@list l2
{mso-list-id:1351223919;
mso-list-type:hybrid;
mso-list-template-ids:-230758966 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:1626693067;
mso-list-type:hybrid;
mso-list-template-ids:-60935458 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:1664814404;
mso-list-type:hybrid;
mso-list-template-ids:-2139077852 134807553 134807555 134807557 134807553 134807555 134807557 134807553 134807555 134807557;}
@list l4:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.25in;
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;
margin-left:.75in;
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;
margin-left:1.25in;
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;
margin-left:1.75in;
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;
margin-left:2.25in;
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;
margin-left:2.75in;
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;
margin-left:3.25in;
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;
margin-left:3.75in;
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;
margin-left:4.25in;
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">Please find below the notes and action items from today’s meeting on Thursday, 02 February 2023 at 13: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 (and for this week, a huge note of thanks to Marika for capturing notes!)<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 – 02 February 2023</span></u></b><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">Action Items</span></u></b><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><span style="color:black;mso-fareast-language:EN-GB">Action item #1</span></b><span style="color:black;mso-fareast-language:EN-GB">: ICANN org to share scenarios in which a primary label may become undelegated so that this can be included
in the rationale. <o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="color:black;mso-fareast-language:EN-GB">Action item #2:
</span></b><span style="color:black;mso-fareast-language:EN-GB">Staff support team to circulate definition of critical function (see section six in in Specification 10 here:
<a href="https://newgtlds.icann.org/sites/default/files/agreements/agreement-approved-31jul17-en.html#specification10">
https://newgtlds.icann.org/sites/default/files/agreements/agreement-approved-31jul17-en.html#specification10</a></span><span style="mso-fareast-language:EN-GB">). The Critical Functions include: DNS Service; DNSSEC proper resolution; EPP; RDDS; Data Escrow.
[COMPLETE]<span style="color:black"><o:p></o:p></span></span></p>
<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"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><u><span style="color:black">Notes</span></u></b><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">Notes – IDN EPDP – 02 February 2023<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><u><span style="color:black">Roll Call and SOI Updates / Welcome and Chair Updates</span></u><span style="color:black"><o:p></o:p></span></p>
<ul type="disc">
<li class="MsoListParagraph" style="color:black;margin-left:2.25pt;mso-list:l1 level1 lfo2">
Reminder, staff sent around text for review two weeks ago with a deadline of today (Thursday 2 Feb). If additional time is needed, please indicate this as soon as possible so that there is an indication of when input is expected to be received.
<o:p></o:p></li><li class="MsoListParagraph" style="color:black;margin-left:2.25pt;mso-list:l1 level1 lfo2">
No meeting next week due to ICANN org all hands meeting. <o:p></o:p></li><li class="MsoListParagraph" style="color:black;margin-left:2.25pt;mso-list:l1 level1 lfo2">
A webinar has been scheduled with the GAC on 15 February at 11.00 UTC. This will allow the group to provide an update on the work and progress to date. Further info will be circulated closer to the date. All are welcome to join.<o:p></o:p></li></ul>
<p class="MsoNormal"><u><span style="color:black;mso-fareast-language:EN-GB">Continued review of ICANN org input<o:p></o:p></span></u></p>
<p class="MsoNormal"><u><span style="color:black;mso-fareast-language:EN-GB"><o:p><span style="text-decoration:none"> </span></o:p></span></u></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-top:5.0pt;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level1 lfo3">
<span style="mso-fareast-language:EN-GB">Take stock of where we are at this point.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level1 lfo3">
<span style="mso-fareast-language:EN-GB">Commenced with non-substantive input that can be applied with no issues (slide 4 – 5) – those updates are in the progress of being made. Everyone will have a change to review these.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level1 lfo3">
<b><span style="mso-fareast-language:EN-GB">Input for A5 – Rec 1.5 (slide 6)</span></b><span style="mso-fareast-language:EN-GB"> – Best practices may not be ready from a practical perspective before round launches. May only be known after the next round. Were
envisioned to help applicants to better prepare. There is also a recommendation in relation to development of criteria – purpose is to sure that applicants are capable to operate the TLD and variants. Observation from the staff side: this element to demonstrate
need and capability for variants should go to the same purpose of best practice guideline. The intent of this recommendation may be covered elsewhere, so maybe this recommendation is not as useful at this time. No agreement on how to proceed during the last
call, although there was agreement to take this to the list, no discussion to date.
<o:p></o:p></span>
<ul style="margin-top:0in" type="circle">
<li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Leadership suggestion: consider recasting this recommendation. Rather than best practice guidelines, consider recommending that the IRT develops a framework for best practices for the operation of IDN gTLDs and variant
labels for registries and registrars.<o:p></o:p></span></li></ul>
</li></ul>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;mso-add-space:auto">
<i><span style="color:black;mso-fareast-language:EN-GB">Team input</span></i><span style="color:black;mso-fareast-language:EN-GB">:
<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Best practice should be established by registrars and/or registries – others do not participate in the operation of gTLDs. It is a top down manner of operation.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Original recommendation foresaw relevant stakeholders participating in development of guidelines (“such as registries, registrars, and registrants who have experience or interest in IDNs in the scripts with allocatable
variant labels”). <o:p></o:p></span></li></ul>
<li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level1 lfo3">
<b><span style="mso-fareast-language:EN-GB">Input for A9 – Rec 1.12 (Slide 7) </span>
</b><span style="mso-fareast-language:EN-GB">– Agreement on the last call that label states need to be tracked by ICANN and ideally this list is made available for all to see. Rationale may need to be provided for why this would be public as resources would
be involved for doing so. <b><o:p></o:p></b></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level1 lfo3">
<b><span style="mso-fareast-language:EN-GB">Input for A10 – Rec 1.13 (Slide 8) </span>
</b><span style="mso-fareast-language:EN-GB">– Question is about states and transitions that labels would go through in their lifecycle. What happens if primary label gets revoked, would ICANN org still need to track the IDN variant states? A better word for
revoked would be ‘un-delegated’. There is a presumption that the Registry operator would not be able to continue operating the TLD if the primary label is undelegated, would it still be necessary to continue tracking the labels and transitions of the variants
in this scenario? <b><o:p></o:p></b></span></li></ul>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;mso-add-space:auto">
<i><span style="color:black;mso-fareast-language:EN-GB">Team input</span></i><span style="color:black;mso-fareast-language:EN-GB">:<b><o:p></o:p></b></span></p>
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">If primary label is not used, it should return to the withheld-same-entity. The set of variants is still the set of variants.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">If the primary is revoked, should the whole set be revoked. This should open a broader discussion as this is almost like a redelegation. Need to think about what would trigger such a situation, for example, update to
the RZ-LGR? This would be very different from registry trying to change the primary string. May need to run through some scenarios to better understand.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Question arises, can you apply for a set, where you never intended to use the primary label?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Let’s take the question out of the current context and think about the sanctity of the set. In the case of a breach of contract, it would seem that it would disqualify the variants as well. It is a single contract that
happens to cover various strings. If there is a breach of contract for one string, doesn’t that automatically affect the others?
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Is it decided yet that it would be one contract? Could also consider multiple contracts.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Need to distinguish why the primary label is revoked – if it is a contractual issue, then it affects all variants and all should be revoked, but if on the other hand the registry decides that they don’t want the primary
label, there should be an opportunity to modify the contract that one of the variants would become the primary label. This could result in changes to other variants if the relationship changes.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">There would be a period of time for the registry to delegate all the strings in the contract. Have not included option of switching out the primary label. Order in which labels are delegated does not matter, but all
need to be delegated in a certain period of time. Not sure if we should go down the path of allowing a registry operator to switch out their primary label or any label once they are contracted. Not sure if that is within scope for this group – may be a conversation
for registry and ICANN legal. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Primary label affects allocatable and blocked variants so it may require a recalculation of string similarity and also other parts of the process?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Logically they are still a set, just because the primary label is revoked that doesn’t change the set. If primary goes out, all should be taken out.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">See slide 8 and 7 – possible to move from delegated to allocated which implies un-delegation. Question is when can that be invoked for primary labels as well as variants. If it cannot be invoked, then #7 may need to
be excluded. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Group seems to agree that it is an all or nothing – if you break the set, you break the sanctity of it.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Now about the circumstances in which cases it can go from delegated to undelegated. There seem to be two options: 1) Breach of contract, 2) registry operator voluntarily decides no longer to operate the string. If the
primary is undelegated, it follows that the variants are undelegated as well. <o:p>
</o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">There are technical and policy considerations – technically there is not necessarily an issue if a primary label is undelegated, but the policy consideration is what matters here. Need to protect the integrity of the
set. Need to be clear about the scenarios, and need to be clear to applicants at the outset.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">If the un-delegation results from action caused by RO then the full set should go out with the primary; if un-delegation is not due to an action caused by the RO, then grandfathering might apply.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Grandfathering would only apply where there is a change to the RZ-LGR (see A10).<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Is it possible for a registry to request withdrawal of a variant label (only one, not others). If that is possible, is it also possible to request withdrawal of a primary label.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Variants are not determined by the registry operator, but the RZ-LGR.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">How strongly do we hold the sanctity of the set? Do we allow a variant to be withdrawn if the primary label is still in place? That should be allowed and the variant becomes un-delegated. However, if the primary label
is un-delegated, it does affect the set, as the set is determined by the primary label. Need to look at the cause of the un-delegation. If it is a breach of contract, shouldn’t be allowed to keep the variants. But if it is due to something that is not caused
by the Registry operator, for example, country language changes result in primary label no longer being valid, or changes to RZ-LGR, there should be exceptions.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Proposal: for simplicity, allocatable variant labels can be subject to delegation, un delegation provided registry operator justifies and have a transitional plan for existing registration, etc. The primary label is
not subject to voluntary un-delegation. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">If the primary goes, the set goes, so the variant label status would no longer need to be tracked either.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Consider asking how many Registry Operators would apply for IDNs variants sets if it is known that the loss of primary destroys the whole set and all TLDs from it.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">May not be necessary to ask this as loss of a primary label is likely an edge case.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:5.0pt;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Would need to keep data for a period of time to be able to track after withdrawal.
<o:p></o:p></span></li></ul>
</ul>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black;mso-fareast-language:EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="color:black;mso-fareast-language:EN-GB">Action item #1</span></b><span style="color:black;mso-fareast-language:EN-GB">: ICANN org to share scenarios in which a primary label may become undelegated so that this can be included
in the rationale. <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><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-top:0in;margin-bottom:0in;margin-top:5.0pt;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level1 lfo3">
<b><span style="mso-fareast-language:EN-GB">Input for B1 – Rec 2.1 (slide 11) </span>
</b><span style="mso-fareast-language:EN-GB">–<b> </b>general concern not specifically about the text in the recommendation but about if an existing registry is granted a variant TLD it would be on an older existing version of the Registry agreement. There
is currently no process for moving from on older version to a newer version of the Registry Agreement. May need to provide for a process to be able to do so.<b><o:p></o:p></b></span></li></ul>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;mso-add-space:auto">
<i><span style="color:black;mso-fareast-language:EN-GB">Team input</span></i><span style="color:black;mso-fareast-language:EN-GB">:<b><o:p></o:p></b></span></p>
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Consider having unified registry agreements but having variety may not be desirable.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Not considered the option that a Ry may already have an agreement and if it would apply for variants it would be under a new agreement. Need to consider Registry agreement. May be difficult to meld two. Should this be
pushed off to the IRT to see how to make this happen, or is this something for the group to address?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Needs to be clear path for how to deal with this, including specification 14. Having various agreements will be confusing and may cause enforcement issues.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">No change needed to this recommendation. Group to review recommendations in general and rationale to see if there is a way to have the IRT consider the best path forward for this scenario. Note, same would apply for
SubPro.<o:p></o:p></span></li></ul>
<li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level1 lfo3">
<b><span style="mso-fareast-language:EN-GB">Input for B2 – Rec 2.2 & Rec 2.3 (slide 12)
</span></b><span style="mso-fareast-language:EN-GB">– originally labelled as non-substantive, but as it is not only about a tweak it would be substitution of language to provide a more precise assessment of what is being recommended.
<b><o:p></o:p></b></span></li></ul>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;mso-add-space:auto">
<i><span style="color:black;mso-fareast-language:EN-GB">Team input</span></i><span style="color:black;mso-fareast-language:EN-GB">:<b><o:p></o:p></b></span></p>
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:5.0pt;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">No concerns, but review if suggestion is consistent with definition of critical function (see
</span><span style="color:windowtext"><a href="https://newgtlds.icann.org/sites/default/files/agreements/agreement-approved-31jul17-en.html#specification10"><span style="mso-fareast-language:EN-GB">https://newgtlds.icann.org/sites/default/files/agreements/agreement-approved-31jul17-en.html#specification10</span></a></span><span style="mso-fareast-language:EN-GB">).
<o:p></o:p></span></li></ul>
</ul>
<p class="MsoNormal"><b><span style="color:black;mso-fareast-language:EN-GB"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="color:black;mso-fareast-language:EN-GB">Action item #2:
</span></b><span style="color:black;mso-fareast-language:EN-GB">Staff support team to circulate definition of critical function.
<o:p></o:p></span></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-top:0in;margin-bottom:0in;margin-top:5.0pt;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level1 lfo3">
<b><span style="mso-fareast-language:EN-GB">Input for D1b – Rec 2.6 </span></b><span style="mso-fareast-language:EN-GB">– suggestion to separate recommendation into two parts, one for need and one for capability, as well as guidance on criteria that can be
used to assess need and capability. If the expertise does not reside within this group to determine criteria, it could also be recommended that an external party develops these criteria for the application process.
<b><o:p></o:p></b></span></li></ul>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;mso-add-space:auto">
<i><span style="color:black;mso-fareast-language:EN-GB">Team input</span></i><span style="color:black;mso-fareast-language:EN-GB">:<b><o:p></o:p></b></span></p>
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">No concerns about splitting recommendation into two.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Not sure what research would be helpful in this regard.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Is related to evaluation of overall application and technical capability, so may need to be brought into the implementation part as it is interrelated with SubPro on the overall evaluation. May make more sense to link
it to that implementation work?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">If this group would not develop the criteria itself, and would ask for research to be done in the future, it would not come back to this group but if adopted would inform implementation and development of application
criteria. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Concerned that this could turn into a substantive effort where it doesn’t need to be. Shouldn’t it be similar to what a ‘normal’ gTLD operator needs to demonstrate? How would it differ from an application for an IDN
and/or variants?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Even if that is the case, may still be necessary to confirm this through research. This shouldn’t be a huge effort. It should be studied alongside the capabilities for any TLD operator.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Suggestion: demonstrate operational capability to perform the critical functions with respect to second level registration in the Variant TLD set. Stay within what we can measure, but the specific details of what can
be measured in terms of variants may need to be deferred to implementation or additional research.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Consider qualifying the research, if the group decides to go down this path.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Group to break recommendation in two and expand on implementation guidance 2.7.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Need question is reasonably subjective. Will be difficult to have set of criteria against which to measure. Primary need would be related to a language community. In 2012 round there was a question about purpose, but
it was an unscored question. Maybe that is another way of dealing with it – having it as an unscored question?
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Have not considered yet who would do the evaluation.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">The evaluation piece shouldn’t stray too far from what was in the RZ-LGR. That may be something evaluations could point to. If there is a big deviation, evaluators could ask why this deviation exists.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">Group to further consider the scoring / non-scoring option and see if there is a way to point out what is really important in this recommendation.
<o:p></o:p></span></li></ul>
<li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:0in;margin-top:0in;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level1 lfo3">
<b><span style="mso-fareast-language:EN-GB">Input for B5-Rec 2.8 (side 14)</span></b><span style="mso-fareast-language:EN-GB"> – in principle non substantive, but given the changes to the text, wanted to check with the group. Org is suggesting to be more precise
in what the restrictions may be, and list out in implementation guidance what the specific restrictions would be. This could potentially be pulled out from the SubPro report.
<o:p></o:p></span></li></ul>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;mso-add-space:auto">
<i><span style="color:black;mso-fareast-language:EN-GB">Team input</span></i><span style="color:black;mso-fareast-language:EN-GB">:<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-bottom:5.0pt;mso-margin-bottom-alt:5.0pt;mso-margin-top-alt:5.0pt;mso-add-space:auto;mso-list:l2 level2 lfo3">
<span style="mso-fareast-language:EN-GB">To further consider during the next call, but in general, whatever can be done to clarify language should be considered.
<o:p></o:p></span></li></ul>
</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 type="disc">
<li class="MsoListParagraph" style="color:black;mso-list:l3 level1 lfo5"><span style="mso-fareast-language:EN-GB">None<o:p></o:p></span></li></ul>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></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>