Hi Justine, Thank you very much for your kind words and for reviewing the language. Please see below our responses to your comments. *** Community Input Window The ALAC requests consideration for extending this time period to 135 days. The ALAC believes 135 days is a more reasonable time period for purposes of application comments and/or objections given the time needed to review the anticipated high number of applications (which org have factored into its calculation of fees), while still meeting the rigorous stipulations for its process for objections -- i.e. requiring bottom-up development of potential objections, discussion and approval of objections at the RALO level, and followed by a process for ALAC's consideration and approval of the objection. The ALAC raises a valid point, but we would like to note that this issue was not raised previously as part of IRT discussions or public comments and is not based on any specific policy recommendations. In this context, we would like to invite the ALAC to submit their request as a public comment in the upcoming proceeding, so it can be reviewed by/with the group as part of the discussions on the final updates to the language. We would need some time to assess the exact impact of such a change on processing times, vendor costs, and any other aspects of the Program but would like to provide our initial thoughts below. Firstly, it should be noted that the community may begin reviewing applications and strings on Reveal Day, approximately 16-17 days prior to the comment and the objection periods opening on String Confirmation Day. In other words, the community will have approximately 106-107 days to review applications and strings. In addition, it is expected that such a change will extend the overall Program timeline by at least 45 days (the additional time requested by the ALAC) or possibly more. Among others, application comments will be provided to the relevant panels after the comment period closes, which will have an impact on the timeline of the String Evaluation Reports publication. *** Independent Objector I vaguely recall the IRT discussing the possibility of granting the IO a short extension of time beyond the set period to file objections but I don't recall if there was strong support either ways. I'd like to bring up this suggestion again given that the IO's ability to file an objection is dependent on the availability of a comment in opposition having been submitted. Such a comment could foreseeably be submitted at the end of the set period which does not give the IO reasonable time to react to it. We suggested having a separate window for Independent Objectors during meeting #63<https://community.icann.org/x/UgDyF>, and the group seemed to favor having them file objections at the same time as everybody else. Also in this case, we would like to invite the ALAC to submit a public comment so this potential amendment can be discussed with the IRT after the proceeding. *** We welcome any reactions from IRT members on these matters already at this stage but will most likely not be able to make substantive changes to the language before the closing of the final public comment. Best regards, Elisa From: Justine Chew via SubPro-IRT <subpro-irt@icann.org> Reply to: Justine Chew <justine.chew.icann@gmail.com> Date: Tuesday, 6 May 2025 at 12:34 To: Lars Hoffmann <lars.hoffmann@icann.org> Cc: "subpro-irt@icann.org" <subpro-irt@icann.org> Subject: [SubPro-IRT] Re: Community Input & Dispute Resolution Dear Lars, You and your team have been excellent in making sure new comments are noted and reviewed. I would just like to mention that I have made two new comments for this topics(s), one on behalf of the ALAC and the other in my own capacity. Thanks. Kind regards, Justine --------- On Tue, 29 Apr 2025, 18:58 Lars Hoffmann via SubPro-IRT, <subpro-irt@icann.org<mailto:subpro-irt@icann.org>> wrote: Dear IRT members, Please see here the redline for the Community Input and Dispute Resolution language: https://docs.google.com/document/d/16HK37AMl3VtfmhzPSoiidyqMYRrKzNRCYArbp7Az... [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/16HK37AMl3Vtfm...> Please note, this topic includes language on: * Application Comments * GAC early warning * GAC advice * Singular/Plural notification * Objections * Standing * Filing and Processing * Appeals If you’d like to provide further input, please use the comment function on the google document. At this time, we have not more discussion on this topic scheduled. Very best. Lars _______________________________________________ SubPro-IRT mailing list -- subpro-irt@icann.org<mailto:subpro-irt@icann.org> To unsubscribe send an email to subpro-irt-leave@icann.org<mailto:subpro-irt-leave@icann.org> _______________________________________________ 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.