<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div><br></div>I believe the situation when this IG was drafted was different. We had much less scripts than what RZ-LGR currently features and there was a concern of some communities not being able to apply. <div><br></div><div>So both on a personal basis and trying to summon the Work Track 4 collective thinking, I am supportive. </div><div><br></div><div><br></div><div>Rubens</div><div><br id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>Em 2 de mar. de 2024, à(s) 09:41, Jeff Neuman <jeff@jjnsolutions.com> escreveu:</div><br class="Apple-interchange-newline"><div>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<div>
<div dir="ltr">
<div dir="ltr">Thank you for providing this rationale. As one of the former co-chairs of the SubPro PDP Working Group, I believe the rationale here is sound and makes sense especially in light of the IDN ePDP Phase 1 Recommendation. Though I am not sure
there are any rules or procedures necessarily governing this situation, I am of the view that because (i) the IDN ePDP was a “Recommendation” as opposed to the SubPro’s “Implementation Guidance” and (ii) the IDN ePDP Phase 1 occurred more recently, that the
IDN ePDP Phase 1 recommendation should be followed where, like here, there is a possible conflict.</div>
<div dir="ltr"><br>
</div>
<div id="ms-outlook-mobile-signature">
<div><br>
</div>
<div dir="ltr">
<div dir="ltr">Sincerely,</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">Jeffrey J. Neuman</div>
<div dir="ltr">Founder & CEO</div>
<div dir="ltr">JJN Solutions, LLC</div>
<div dir="ltr">+1.202.549.5079</div>
<div dir="ltr">Jeff@jjnsolutions.com</div>
</div>
</div>
<div id="mail-editor-reference-message-container" class="ms-outlook-mobile-reference-message">
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif"><b>From:</b> SubPro-IRT <subpro-irt-bounces@icann.org> on behalf of Next Round Policy Implementation <NextRound_PolicyImplementation@icann.org><br>
<b>Sent:</b> Friday, March 1, 2024 10:55 AM<br>
<b>To:</b> subpro-irt@icann.org <subpro-irt@icann.org><br>
<b>Subject:</b> [SubPro-IRT] Rationale for Not Implementing Implementation Guidance 25.3
<div> </div>
</font></div>
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<div class="WordSection1"><div style="margin: 0cm; font-size: 11pt; font-family: Aptos, sans-serif;">
Dear IRT members, </div><p class="MsoNormal" style="margin: 0cm; font-size: 11pt; font-family: Aptos, sans-serif;">
</p><div style="margin: 0cm; font-size: 11pt; font-family: Aptos, sans-serif;">
We are please to inform you that the <a href="https://community.icann.org/download/attachments/238617525/Rationale%20for%20Not%20Implementing%20IG25.3.pdf?version=1&modificationDate=1709242109840&api=v2">
Rationale for Not Implementing Implementation Guidance 25.3 of SubPro</a> is published on the
<a href="https://community.icann.org/x/ZYAvEQ">Meeting #30 wiki page</a>. We will discuss it during the meeting tomorrow.
</div><p class="MsoNormal" style="margin: 0cm; font-size: 11pt; font-family: Aptos, sans-serif;">
</p><div style="margin: 0cm; font-size: 11pt; font-family: Aptos, sans-serif;">
Best regards,</div><div style="margin: 0cm; font-size: 11pt; font-family: Aptos, sans-serif;">
Elisa</div><p class="MsoNormal" style="margin: 0cm; font-size: 11pt; font-family: Aptos, sans-serif;">
</p>
</div>
</div>
</div>
</div>
_______________________________________________<br>SubPro-IRT mailing list<br>SubPro-IRT@icann.org<br>https://mm.icann.org/mailman/listinfo/subpro-irt<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 (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). 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.</div></blockquote></div><br></div></body></html>