<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:973683585;
mso-list-type:hybrid;
mso-list-template-ids:1712230774 -26165822 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:2;
mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;
mso-fareast-font-family:"Times New Roman";
mso-bidi-font-family:Calibri;}
@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;
mso-bidi-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;
mso-bidi-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;
mso-bidi-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;
mso-bidi-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;
mso-bidi-font-family:Wingdings;}
@list l1
{mso-list-id:1418598713;
mso-list-template-ids:-1972586618;}
@list l1:level1
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level4
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level7
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2
{mso-list-id:1451127387;
mso-list-template-ids:-703695628;}
@list l2: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 l2: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 l2: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 l2: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 l2: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 l2: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 l2: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 l2: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 l2: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="purple">
<div class="WordSection1">
<p class="MsoNormal">Dear Working Group members,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Please see below the notes from the meeting on 28 April at 0300 UTC.
<b><i>These high-level notes are designed to help WG members navigate through the content of the call and are not a substitute for the recording, transcript, or the chat,</i></b> which will be posted at:
<a href="https://community.icann.org/display/NGSPP/2020-04-28+New+gTLD+Subsequent+Procedures+PDP">
https://community.icann.org/display/NGSPP/2020-04-28+New+gTLD+Subsequent+Procedures+PDP</a>.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Kind regards,<br>
Julie<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Notes and Action Items:</b><o:p></o:p></p>
<p class="MsoNormal"><b> </b><o:p></o:p></p>
<p class="MsoNormal"><b>Actions:</b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="color:black">2.7.5 Internationalized Domain Names:<o:p></o:p></span></p>
<p class="MsoNormal"><u><span style="color:black">Recommendation xx (rationale 2)</span></u><span style="color:black">:<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><u><span style="color:black">Implementation Guidance xx (Rationale 2)</span></u><span style="color:black">:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">ACTION ITEM: Revise the text to make the changes in brackets and strikeout: “If a script is not yet integrated into the RZ-LGR, applicants should be able to apply for a string in that script, [and it should be
processed] <s>but it should not be delegated</s> [and it should be processed up to but not including contracting].<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">Recommendation xx (Rationale 4)</span></u><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"><span style="color:black">ACTION ITEM: Remove the brackets and check if language is consistent with the recommendations in the IDN Variant TLD Recommendations Analysis Report for the requirement for the back-end registry service provider:
<a href="https://www.icann.org/en/system/files/files/idn-variant-tld-recommendations-analysis-25jan19-en.pdf">
https://www.icann.org/en/system/files/files/idn-variant-tld-recommendations-analysis-25jan19-en.pdf</a>.
<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:black">2.7.6 Security and Stability<o:p></o:p></span></p>
<p class="MsoNormal"><u>Recommendation xx (Rationale 1)</u>:<o:p></o:p></p>
<p class="MsoNormal">ACTION ITEM: ICANN Org will provide delegation statistics.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><u>Implementation Guidance xx (Rationale 1)</u>:<o:p></o:p></p>
<p class="MsoNormal">ACTION ITEM: Replace “Verisign” with “Root Zone Manager”.<o:p></o:p></p>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<p class="MsoNormal"><b>Notes:</b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">1. Updates to Statements of Interest: No updates provided.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">2. Discussion of Final Report Topics: <a href="https://docs.google.com/document/d/1kUlmZH8nxWTgfcRluA5FxLheMm4XhhOwkRt7om52aQU/edit?usp=sharing">
https://docs.google.com/document/d/1kUlmZH8nxWTgfcRluA5FxLheMm4XhhOwkRt7om52aQU/edit?usp=sharing</a><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">a. <span style="color:black">2.7.5 Internationalized Domain Names, page 77</span><span style="font-size:12.0pt;color:black"><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">Recommendation xx (rationale 2)</span></u><span style="color:black">: Compliance with Root Zone Label Generation Rules (RZ-LGR) must be required for the generation of IDN TLDs and variants labels, [including
the determination of whether the label is blocked or allocatable].<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">Discussion</span></u><span style="color:black">:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">-- Comment From Staff: There is a recommendation in Registry System Testing about whether IDN tables need to be tested during PDT. The relevant recommendation in this section was removed for the time being, so
as not to duplicate. The IG from Registry System Testing is: Implementation Guidance xx (rationale 3): The testing of Internationalized Domain Name (IDN) tables should be removed if the applicant is using tables that are pre-vetted by the community. To the
extent an applicant is proposing tables that are not pre-vetted by the community, the tables should be reviewed during the evaluation process and the evaluator should utilize IDN tools available at the time of review.<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 ITEM: Add the bracketed text and drop the brackets.<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">Implementation Guidance xx (Rationale 2)</span></u><span style="color:black">: If a script is not yet integrated into the RZ-LGR, applicants should be able to apply for a string in that script, [and it should
be processed] but it should not be delegated.<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">Discussion</span></u><span style="color:black">:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">-- Should not go to contracting until the RZ-LGR for that script are integrated.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">-- </span><span style="color:black">Are we giving applicants sufficient warning that contracting may be held up subject to RZ-LGR?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">-- Could take it all the way up until contracting.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">-- Make sure this is consistent with the Registry System Testing section.<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 ITEM: Revise the text to make the changes in brackets and strikeout: “If a script is not yet integrated into the RZ-LGR, applicants should be able to apply for a string in that script, [and it should
be processed] <s>but it should not be delegated</s> [and it should be processed up to but not including contracting].<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">Recommendation xx (Rationale 4)</span></u><span style="color:black">: IDN gTLDs deemed to be variants of already existing or applied for TLDs will be allowed provided they have the same registry operator [and
back-end registry service provider,] implementing by force of written agreement a policy of cross-variant TLD bundling.<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">Discussion</span></u><span style="color:black">:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">-- The same registry operator must be the same for variants of already existing or applied for TLDs.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">-- Registry SG suggested the bracketed language – requiring the same back-end operator.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">-- Do we need to be this prescriptive?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">-- In the recommendations on IDN Variant TLDs passed by the Board last year it does address this point – specifically the same back-end operator if applicable:
<a href="https://www.icann.org/en/system/files/files/idn-variant-tld-recommendations-analysis-25jan19-en.pdf">
https://www.icann.org/en/system/files/files/idn-variant-tld-recommendations-analysis-25jan19-en.pdf</a>
<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 ITEM: Remove the brackets and check if language is consistent with the recommendations in the IDN Variant TLD Recommendations Analysis Report for the requirement for the back-end registry service provider:
<a href="https://www.icann.org/en/system/files/files/idn-variant-tld-recommendations-analysis-25jan19-en.pdf">
https://www.icann.org/en/system/files/files/idn-variant-tld-recommendations-analysis-25jan19-en.pdf</a>.
<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">Recommendation xx (Rationale 5)</span></u><span style="color:black">: A given second-level label under any allocated IDN variant TLD must only be allocated to the same entity/registrant, or else withheld for
possible allocation only to that entity (e.g., s1 under {t1, t1v1, …}, e.g., s1.t1 and s1.t1v1). <o:p></o:p></span></p>
<p class="MsoNormal"><u><span style="color:black">Recommendation xx (Rationale 5)</span></u><span style="color:black">: For second-level IDN variant labels that arise from a registration based on a second-level IDN table, all allocatable IDN variant labels
in the set must only be allocated to the same entity or withheld for possible allocation only to that entity (e.g., all allocatable second-level labels {s1, s1v1, …} under all allocated variant TLD labels {t1, t1v1, …}). <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">Discussion</span></u><span style="color:black">:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">-- Question: Wonder how we link contractually two or three contracts are independent now. It might cause issues later, for example, there are three IDN variant TLDs and a registry decides to terminate one of those
because of no registration – is a registry not allowed to take down one of the variants? Contracts should be able to be separated. Answer: Don’t think it is an insurmountable problem. In the case of IDN variant TLDs there isn’t a reason that you could have
a new specification about how you handle multiple variant TLDs – you could have one contract but have provisions that would only relate to registry operators that operate multiple variant TLDs. Not sure we should be prescriptive for how they should do that.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">-- That's possibly something that the RO could specify in the RSEP request to stop variant X from being offered to new registrations.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">-- The variants do not all have to be active - however, if TLDs are delegated as variant labels based on the LGR, their status as variants would not change.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">-- Question: Might we need another Implementation Guidance regarding another RA Specification for IDNs? Answer: We don’t need to be so prescriptive here.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">-- In terms of the contract and retiring of variant TLDs – might need one contract for both or contracts tied together. If a registry wants to retire a variant TLD it won’t be possible for another registry to
pick it up.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">-- Since ICANN can’t look at content the registrant can – they could be in two completely different web sites (traditional and simplified Chinese for example). Out of our control.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">-- Question: Do we need a recommendation relating to URS and UDRP? Answer: Don’t know if we know enough about that issue to make any recommendations. Might refer to the RPMs PDP WG Phase 2.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">-- UDRP is meant to address a large share of trademark issues, but there is always the possibility of only a court being able to settle a dispute. As long as UDRP keeps working for a near totality, it doesn't have
to deal with all possible cases.<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">b. 2.7.6 Security and Stability, page 80</span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><u>Recommendation xx (Rationale 1)</u>: ICANN must honor and review the principle of conservatism when adding new gTLDs to the root zone. <br>
<u>Recommendation xx (Rationale 1)</u>: ICANN must focus on the rate of change for the root zone over smaller periods of time (e.g., monthly) rather than the total number of delegated strings for a given calendar year.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><u>Discussion</u>:<o:p></o:p></p>
<p class="MsoNormal">-- There was no basis for 1000 delegations.<o:p></o:p></p>
<p class="MsoNormal">-- the 1000 per year came from an ICANN operational assessment, which then served as the basis for security and stability considerations.<o:p></o:p></p>
<p class="MsoNormal">-- ICANN Org has presented the data on number and rate of delegations.<o:p></o:p></p>
<p class="MsoNormal">-- Looking at contracts only it looks like we had around 500 delegations per year.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>ACTION ITEM: ICANN Org will provide delegation statistics.<o:p></o:p></b></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><u>Implementation Guidance xx (Rationale 1)</u>: The Office of the Chief Technology Officer (OCTO) should consult with PTI, Verisign, the root operators via RSSAC, and the larger DNS technical community on the implementation of these recommendations.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><u>Discussion</u>:<o:p></o:p></p>
<p class="MsoNormal">-- In this one, we should replace Verisign with Root Zone Manager. It's currently Verisign, but we don't know whether this will change or not. Should be the role and not the organization.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>ACTION ITEM: Replace “Verisign” with “Root Zone Manager”.</b><o:p></o:p></p>
</div>
</body>
</html>