Hi Lars, Appreciate your response, and the update looks good! Best and tx, Kathy On 2/11/2025 1:19 PM, Lars Hoffmann via SubPro-IRT wrote:
Hi Kathy,
Thanks for reaching out. Elisa is ooo until tomorrow, so I hope it’s ok if I respond.
Since not all changes are subject to a comment period, we suggest will add the following language to the first paragraph:
“It should be noted that certain ACRs will be published for a 30-day comment period, as described in [Application Change Request Types and Required Processes], giving the general public the opportunity to provide their input.”
Best. Lars
PS: we will share an updated document asap.
*From: *Kathy Kleiman via SubPro-IRT <subpro-irt@icann.org> *Reply to: *Kathy Kleiman <Kathy@KathyKleiman.com> *Date: *Friday, 7 February 2025 at 11:30 *To: *"subpro-irt@icann.org" <subpro-irt@icann.org> *Subject: *[SubPro-IRT] Re: Application Change Requests
Hi Elisa,
Sorry to miss the discussion on this yesterday, but could we make a small change to the opening paragraph (and the doc is locked to I share the edit here)? Proposed change (two possibilities offered) in CAPS for readability below:
"The
Application Change Requests (ACR) process permits applicants to request changes to applications, which are reviewed by ICANN AND THE PUBLIC against the change request determination criteria (described in
Section<https://urldefense.com/v3/__https:/docs.google.com/document/d/1xn8_wTInFG3n-...>
2[docs.google.com] <https://urldefense.com/v3/__https:/docs.google.com/document/d/1xn8_wTInFG3n-...>)
and subject to (/alternatively, /PUBLIC REVIEW AND COMMENT AND) approval by ICANN.
With this added wording to the introductory section, we provide notice to the public to read farther and learn more about their ability to provide input about changes (details not discussed until close to the end of the doc and after a big table\).
Best, tx and have a good weekend,
Kathy
On 2/5/2025 10:55 AM, Elisa Busetto via SubPro-IRT wrote:
Dear IRT members,
Please find here [docs.google.com] <https://urldefense.com/v3/__https:/docs.google.com/document/d/1xn8_wTInFG3n-...> the updated Application Change Requests (ACRs) language, which we will discuss during meeting #112 <https://community.icann.org/x/AQAvH>, on 6 February at 19:00 UTC.
We have made some changes since we last discussed the topic with the objective to streamline the process and provide as much information as possible to applicants regarding the different scenarios. We hope that these updates are helpful.
What proved most difficult was finding ways to make sure that the community has the opportunity to provide their *input on RVCs and community registration policies* at the right time without delaying the processing of applications, which is why we developed a separate workflow for such changes.
In summary, we propose that the ACRs that include RVCs and community registration policies will be published for application comments *after* the Registry Commitment Evaluation (RCE) is concluded. This proposed approach allows the community to provide their input on the ‘near final’ version of RVC/community registration policy that reflects the agreed to changes following negotiations between the applicant and ICANN during the RCE, and not just on the originally submitted version by the applicant that might not be approved by ICANN and have to undergo substantive changes. Nevertheless, for transparency and to ensure that community views are informed by any changes that occurred during the RCEn, ICANN will also publish the originally submitted RVC/ community registration policy for the community to review and provide comments.
While we considered implementing this process like other types of ACRs (i.e., open a comment period before the RCE), we believe that the proposed approach is the most efficient path forward that will avoid the expenditure of community attention and resources to /_only_/ review and comment on originally submitted commitments/policies that may not meet the criteria and, as such, would not be approved for inclusion in the applicable Registry Agreement if the application proceeds to delegation.
ICANN will review the comments on both the ‘near final’ and originally submitted versions of commitments/policies and may re-initiate negotiations with the applicant based on input received during the comment period.
However, if an RVC or community registration policy is submitted as part of the initial application, we propose to open the comment period *before* the RCE. This is to ensure transparency by publishing all relevant materials submitted during the initial application on the reveal day (e..g, RVC/community registration policy may only be a small part of the initial application). If the applicant and ICANN agree to certain changes to the commitment/policy during the RCE, the applicant will have to submit an ACR to reflect those agreed to changes. If the changes are material, another comment period will be opened, giving the chance to the community to provide their input on the ‘near final’ version of policy/commitment.
Looking forward to going through the document tomorrow!
Best,
Ariel and Elisa
_______________________________________________
SubPro-IRT mailing list --subpro-irt@icann.org
To unsubscribe send an email tosubpro-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.
_______________________________________________ SubPro-IRT mailing list --subpro-irt@icann.org To unsubscribe send an email tosubpro-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.