<html><head>
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style type="text/css"><!--#x3172c9b0ebde4c6 p.MsoNormal
{margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;}
#x3172c9b0ebde4c6 a:link
{color: blue; text-decoration: underline;}
#x3172c9b0ebde4c6 li.m4268253947299239722msolistparagraph
{margin-right: 0cm; margin-left: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;}
#x3172c9b0ebde4c6 div.WordSection1
{page: WordSection1;}
#x3172c9b0ebde4c6 ul
{margin-bottom: 0cm;}
--></style><style id="css_styles" type="text/css"><!--blockquote.cite { margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:0px; border-left: 1px solid #cccccc }
blockquote.cite2 {margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:0px; border-left: 1px solid #cccccc; margin-top: 3px; padding-top: 0px; }
a img { border: 0px; }
li[style='text-align: center;'], li[style='text-align: center; '], li[style='text-align: right;'], li[style='text-align: right; '] { list-style-position: inside;}
body { font-family: 'Segoe UI'; font-size: 12pt; }
.quote { margin-left: 1em; margin-right: 1em; border-left: 5px #ebebeb solid; padding-left: 0.3em; }
--></style>
</head>
<body><div>The other issue is that somewhere along the line a decision was made that "compliance with the LGR" would be part of the DNS Stability check. By making it part of the DNS Stability check, if you are not compliant with the RZ-LGR, then you fail that test and your application does not even make it to the next step. Therefore, by making it part of the DNS Stability review, you cannot implement the SubPro Recommendation that it can proceed to everything up until contracting.</div><div><span><br /></span></div><div><span>So the real question is whether "compliance with the RZ-LGR" should be a separate test from the DNS Stability review. </span></div>
<div><br /></div><div id="signature_old" style="clear:both"><div><br /></div><img src="cid:em6425389b-5a48-45c2-87a9-c7cdbc270cbe@4affc605.com" border="0" /></div><div style="clear:both"><br /></div>
<div><br /></div>
<div>
<div>------ Original Message ------</div>
<div>From "Susan Payne" <<a href="mailto:susan.payne@comlaude.com">susan.payne@comlaude.com</a>></div>
<div>To "Anne ICANN" <<a href="mailto:anneicanngnso@gmail.com">anneicanngnso@gmail.com</a>>; "Next Round Policy Implementation" <<a href="mailto:NextRound_PolicyImplementation@icann.org">NextRound_PolicyImplementation@icann.org</a>>; "<a href="mailto:subpro-irt@icann.org">subpro-irt@icann.org</a>" <<a href="mailto:subpro-irt@icann.org">subpro-irt@icann.org</a>></div>
<div>Date 1/30/2024 8:17:03 AM</div>
<div>Subject [SubPro-IRT] RZ-LGR Draft Text</div></div><div><br /></div>
<div id="x3172c9b0ebde4c6" style="word-wrap:break-word"><blockquote cite="LO3P123MB322757DC5665E6CCFB33660E9A7D2@LO3P123MB3227.GBRP123.PROD.OUTLOOK.COM" type="cite" class="cite2">
<div class="WordSection1">
<p class="MsoNormal">Thanks Anne.<o:p xmlns:o="#unknown"></o:p></p>
<p class="MsoNormal">I would add that the SubPro Final Report itself gives a clear explanation of the intentions behind Implementation Guidance, which can be found in the Preamble, page 3:<o:p xmlns:o="#unknown"></o:p></p>
<p class="MsoNormal"><o:p xmlns:o="#unknown"> </o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt;line-height:12.9pt;mso-line-height-rule:exactly;punctuation-wrap:simple;text-autospace:none">
<u><span style="font-size:12.0pt;font-family:"Times New Roman",serif;mso-fareast-language:EN-US">Implementation Guidance</span></u><span style="font-size:12.0pt;font-family:"Times New Roman",serif;mso-fareast-language:EN-US">: The Working Group strongly recommends
the stated action, with a strong
presumption
that it
will be
implemented, but
recognizes that there may
exist valid
reasons in particular
circumstances to not
take the recommended
action exactly as described.
However, the
party to
whom the
action is directed
must make
all efforts to
achieve the
purpose behind
the recommended
action (as expressed
in the
rationale and
the recommendation
to which
the implementation guidance is linked,
if applicable)
even if
done through
a different
course. In
all cases,
the full
implications must be
understood and
carefully weighed
before choosing
a different
course. Implementation
guidance commonly
refers to <b>how
</b>a recommendation
should be implemented.
Implementation guidance typically
uses the term
“should” indicating
that the
Working Group
expects the action to
take place,
noting the caveats above.<o:p xmlns:o="#unknown"></o:p></span></p>
<p class="MsoNormal"><o:p xmlns:o="#unknown"> </o:p></p>
<p class="MsoNormal">This is of course relevant to our upcoming discussion of the section on the
Root Zone Label Generation Rules, specifically paragraph 2.1 which proposes that applicants will not be permitted to submit an application for a string if its script has not yet been integrated in the RZ-LGR, and which diverges from SubPro Implementation
Guidance 25.3, and its accompanying rationale:
<o:p xmlns:o="#unknown"></o:p></p>
<p class="MsoNormal"><o:p xmlns:o="#unknown"> </o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt;line-height:12.9pt;mso-line-height-rule:exactly;punctuation-wrap:simple;text-autospace:none">
<a name="a. Recommendations and/or implementation"></a><a name="_bookmark0"></a><u><span style="font-size:12.0pt;font-family:"Times New Roman",serif;mso-fareast-language:EN-US">Implementation Guidance 25.3</span></u><span style="font-size:12.0pt;font-family:"Times New Roman",serif;mso-fareast-language:EN-US">:
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 up to but not including contracting. Applicants under such circumstances should be
warned of the possibility that
the applied-for string may
never be delegated and they will
be responsible
for any additional evaluation costs.<o:p xmlns:o="#unknown"></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;line-height:12.9pt;mso-line-height-rule:exactly;punctuation-wrap:simple;text-autospace:none">
<span style="font-size:12.0pt;font-family:"Times New Roman",serif;letter-spacing:-.1pt;mso-fareast-language:EN-US"><o:p xmlns:o="#unknown"> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;line-height:12.9pt;mso-line-height-rule:exactly;punctuation-wrap:simple;text-autospace:none">
<a name="b. Deliberations and rationale for recom"></a><u><span style="font-size:12.0pt;font-family:"Times New Roman",serif;mso-fareast-language:EN-US">Rationale</span></u><span style="font-size:12.0pt;font-family:"Times New Roman",serif;mso-fareast-language:EN-US">:
…While the Working Group is fully supportive of requiring IDN TLDs to comply with RZ-LGR, it’s cognizant
that this may impact
potential applicants who want to apply for
an application in a
script that
is not yet
integrated into the
RZ-LGR. The Working Group believes that applicants should be
provided the opportunity to
apply for a string in a
script that is not
yet integrated into the
RZ-LGR, and it should be
processed up to but not including
contracting. It should of course
not be
delegated until it
is compliant. The Working Group believes the
burden in this case
is on the
applicant, who may have to wait for an indeterminate amount of time but is not aware of any other serious concerns.<o:p xmlns:o="#unknown"></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;line-height:12.9pt;mso-line-height-rule:exactly;punctuation-wrap:simple;text-autospace:none">
<span style="font-size:12.0pt;font-family:"Times New Roman",serif;letter-spacing:-.1pt;mso-fareast-language:EN-US"><o:p xmlns:o="#unknown"> </o:p></span></p>
<p class="MsoNormal">It is difficult to see, without further explanation from the staff team, how paragraph 2.1 achieves the purpose behind the recommended action in SubPro 25.3, bearing in mind that the SubPro WG had
clearly considered that this would mean an applicant might apply for a string in an unintegrated script without any guarantee of delegation. Hopefully this is what we will discuss shortly.
<o:p xmlns:o="#unknown"></o:p></p>
<p class="MsoNormal"><o:p xmlns:o="#unknown"> </o:p></p>
<div>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td style="padding:0cm 0cm 0cm 0cm">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Poppins SemiBold"">Susan Payne
<br />
</span><span style="font-size:9.0pt;font-family:"Poppins Light";color:#950734">Head of Legal Policy
</span><span style="font-size:9.0pt;font-family:"Poppins SemiBold""><br />
Com Laude<br />
</span><strong><span style="font-size:9.0pt;font-family:"Poppins Light";color:#950734">T</span></strong><span style="font-size:9.0pt;font-family:"Poppins Light""> +44 (0) 20 7421 8250<br />
<strong><span style="color: rgb(149, 7, 52);">Ext</span></strong> 255</span><o:p xmlns:o="#unknown"></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><o:p xmlns:o="#unknown"> </o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td style="padding:7.5pt 0cm 0cm 0cm">
<p class="MsoNormal"><em>Follow us on
<a href="https://t-uk.xink.io/Tracking/Index/pRkAAGVfAADw_RQA0">Linkedin</a> and <a href="https://t-uk.xink.io/Tracking/Index/bhkAAGVfAADw_RQA0">
YouTube</a></em><o:p xmlns:o="#unknown"></o:p></p>
</td>
</tr>
</tbody>
</table>
</div>
<p class="MsoNormal"><img border="0" width="1" height="1" style="width:.0069in;height:.0069in" id="_x0000_i1025" src="https://t-uk.xink.io/Tracking/Impression/UxsAAGVfAADw_RQA0" /><o:p xmlns:o="#unknown"></o:p></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> SubPro-IRT <<a href="mailto:subpro-irt-bounces@icann.org">subpro-irt-bounces@icann.org</a>>
<b>On Behalf Of </b>Anne ICANN<br />
<b>Sent:</b> Thursday, January 25, 2024 11:00 PM<br />
<b>To:</b> Next Round Policy Implementation <<a href="mailto:NextRound_PolicyImplementation@icann.org">NextRound_PolicyImplementation@icann.org</a>><br />
<b>Cc:</b> <a href="mailto:subpro-irt@icann.org">subpro-irt@icann.org</a><br />
<b>Subject:</b> Re: [SubPro-IRT] Post call | SubPro IRT Meeting #25 | 23 January 2024<o:p xmlns:o="#unknown"></o:p></span></p>
</div>
<p class="MsoNormal"><o:p xmlns:o="#unknown"> </o:p></p>
<div>
<div>
<p class="MsoNormal">Hi Lars and all IRT Team Members,<o:p xmlns:o="#unknown"></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p xmlns:o="#unknown"> </o:p></p>
</div>
<div>
<p class="MsoNormal">Further to our discussion this past Tuesday, I am pasting below the language from Council's Response to the ICANN Staff Sub Pro ODP team in relation to the effect of Implementation Guidance. This is from the GNSO Council Response to Question
Set #6 (not #4 as I had thought.) Hopefully this Response from Council is helpful generally on the topic of variation from Implementation Guidance.
<o:p xmlns:o="#unknown"></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p xmlns:o="#unknown"> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:blue">"In short, implementation guidance remains a strong recommendation as opposed to a<br />
requirement. As referenced in the Preamble to the Sub Pro Final Report, ICANN should<br />
specify any “circumstances where there may be valid reasons not to take such guidance exactly<br />
as described…” In such circumstances, Council believes that consultation with the IRT, the<br />
Guidance Process Team, or the Council itself (e.g. via a request for GNSO Input) is in order<br />
prior to the adoption of alternatives to the specified Implementation Guidance. In all cases, the<br />
implementation should be accomplished in a manner that achieves the objectives laid out in the<br />
implementation guidance even if the mechanism of implementation differs slightly from that<br />
contained in the final report."</span><o:p xmlns:o="#unknown"></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p xmlns:o="#unknown"> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thank you,<o:p xmlns:o="#unknown"></o:p></p>
</div>
<div>
<p class="MsoNormal">Anne<o:p xmlns:o="#unknown"></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p xmlns:o="#unknown"> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p xmlns:o="#unknown"> </o:p></p>
</div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Anne Aikman-Scalese<o:p xmlns:o="#unknown"></o:p></p>
</div>
<p class="MsoNormal">GNSO Councilor<o:p xmlns:o="#unknown"></o:p></p>
<div>
<p class="MsoNormal">NomCom Non-Voting 2022-2024<o:p xmlns:o="#unknown"></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="mailto:anneicanngnso@gmail.com">anneicanngnso@gmail.com</a><o:p xmlns:o="#unknown"></o:p></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p xmlns:o="#unknown"> </o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p xmlns:o="#unknown"> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Wed, Jan 24, 2024 at 7:15 AM Next Round Policy Implementation <<a href="mailto:NextRound_PolicyImplementation@icann.org">NextRound_PolicyImplementation@icann.org</a>> wrote:<o:p xmlns:o="#unknown"></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Dear All, <o:p xmlns:o="#unknown"></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;font-variant-caps:normal;text-align:start;word-spacing:0px">
<o:p xmlns:o="#unknown"></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;font-variant-caps:normal;text-align:start;word-spacing:0px">
The<span class="m4268253947299239722apple-converted-space"> </span>recordings for<span class="m4268253947299239722apple-converted-space"> </span>Meeting
#25
<span class="m4268253947299239722apple-converted-space"> </span>of the SubPro IRT held on<span class="m4268253947299239722apple-converted-space"> </span>Tuesday,
23 January 2024
at<span class="m4268253947299239722apple-converted-space"> </span>13:00-14:00<span class="m4268253947299239722apple-converted-space"> </span>UTC<span class="m4268253947299239722apple-converted-space"> </span>are
published
<span class="m4268253947299239722apple-converted-space"> </span>on the<span class="m4268253947299239722apple-converted-space"> </span><a href="https://community.icann.org/x/WYPxDg" title="https://community.icann.org/x/bpOZDg">meeting
wiki page
</a>.<o:p xmlns:o="#unknown"></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;font-variant-caps:normal;text-align:start;word-spacing:0px">
<o:p xmlns:o="#unknown"></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;font-variant-caps:normal;text-align:start;word-spacing:0px">
These include:<o:p xmlns:o="#unknown"></o:p></p>
<ul style="margin-top:0cm;font-variant-caps:normal;text-align:start;word-spacing:0px" type="disc">
<li class="m4268253947299239722msolistparagraph" style="color:black;margin-top:0cm;margin-bottom:0cm;mso-list:l0 level1 lfo1">
Attendance<span class="m4268253947299239722apple-converted-space"> </span><o:p xmlns:o="#unknown"></o:p></li><li class="m4268253947299239722msolistparagraph" style="color:black;margin-top:0cm;margin-bottom:0cm;mso-list:l0 level1 lfo1">
Audio recording<o:p xmlns:o="#unknown"></o:p></li><li class="m4268253947299239722msolistparagraph" style="color:black;margin-top:0cm;margin-bottom:0cm;mso-list:l0 level1 lfo1">
Zoom recording (including audio, visual, rough transcript, chat)<o:p xmlns:o="#unknown"></o:p></li></ul>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;font-variant-caps:normal;text-align:start;word-spacing:0px">
<o:p xmlns:o="#unknown"></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;font-variant-caps:normal;text-align:start;word-spacing:0px">
For additional information, you may consult the<span class="m4268253947299239722apple-converted-space"> </span><a href="https://mm.icann.org/pipermail/subpro-irt/" title="https://mm.icann.org/pipermail/subpro-irt/">mailing
list archives
</a><span class="m4268253947299239722apple-converted-space"> </span>and the<span class="m4268253947299239722apple-converted-space"> </span><a href="https://community.icann.org/x/pQM5Dg" title="https://community.icann.org/x/pQM5Dg">main
wiki page
</a>.<o:p xmlns:o="#unknown"></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;font-variant-caps:normal;text-align:start;word-spacing:0px">
<o:p xmlns:o="#unknown"></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;font-variant-caps:normal;text-align:start;word-spacing:0px">
Best regards,<o:p xmlns:o="#unknown"></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;font-variant-caps:normal;text-align:start;word-spacing:0px">
Elisa<o:p xmlns:o="#unknown"></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p xmlns:o="#unknown"></o:p></p>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br />
SubPro-IRT mailing list<br />
<a href="mailto:SubPro-IRT@icann.org">SubPro-IRT@icann.org</a><br />
<a href="https://mm.icann.org/mailman/listinfo/subpro-irt">https://mm.icann.org/mailman/listinfo/subpro-irt</a><br />
<br />
_______________________________________________<br />
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (
<a href="https://www.icann.org/privacy/tos">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style
delivery or disabling delivery altogether (e.g., for a vacation), and so on.
<o:p xmlns:o="#unknown"></o:p></p>
</div>
</blockquote>
</div>
</div>
<hr />
The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the
sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to
scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company
registered in England and Wales with company number 10689074 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number
5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England;
Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State
of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku,
Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see
<a href="https://comlaude.com/">www.comlaude.com</a>
</blockquote></div>
</body></html>