Dear Jared, Would you mind sharing again the latest (draft) CPE Evaluation Guide that is proposed to be put out for public comment? Would that be the same draft that, as you mentioned, would be published prior to the opening of the round? Thanks, Justine On Sat, 21 Mar 2026 at 02:36, Jared Erwin via SubPro-IRT < subpro-irt@icann.org> wrote:
Dear IRT Members,
Following up on my email below, does the IRT have any input? If no concerns or further input, ICANN proposes moving forward with Option 2 (regular public comment period, which would close after 30 April).
Thank you
Jared
*From: *Jared Erwin <jared.erwin@icann.org> *Date: *Wednesday, March 18, 2026 at 15:22 *To: *"subpro-irt@icann.org" <subpro-irt@icann.org> *Subject: *Public Comment on Draft CPE Evaluation Guide
Dear IRT Members,
Following on the announcement <https://www.icann.org/en/announcements/details/icann-announces-community-pri...> of the CPE vendor, I am writing regarding next steps for the public comment on the CPE Evaluation Guide. Relevant here are two SubPro Recs: 34.12 and 34.16 (for your reference, I have copied these into the bottom of this email).
Specifically, I would appreciate the IRT’s input on the timing and length of the public comment. We are hopeful that we can open the public comment early next week. However, the RFP and contracting process took more time than expected, which means that we have less time before the opening of the round to both conduct the public comment and finalize the Evaluation Guide.
We believe there are two options:
1. A shortened public comment period (30 days, closing the week of 20 April). This would allow us to complete the public comment and attempt to have a final draft before 30 April. The downside is that there is less time for community groups to develop their comments and for ICANN to consider those comments. 2. ICANN could conduct the public comment for the standard time (40 days), which would mean that the period closes after 30 April (likely week of 4 May), and the report and updated draft would be published after the round opens (likely week of 18 May).
ICANN believes that the second option would ensure that community groups have sufficient time to develop comments and for ICANN and the CPE vendor to consider any feedback while still meeting the spirit of recommendations 34.12 and 34.16—the guide will be published (in draft form) prior to the opening of the round. ICANN anticipates that any changes to the document following the public comment would be minor. Additionally, the finalized guide would be available well before the closing of the application submission period.
Given these options, does the IRT have any input? I would appreciate any feedback as soon as possible.
Thank you very much!
Best,
Jared
*Relevant SubPro Recs*
*Recommendation 34.12**: The process to develop evaluation and selection criteria that will be used to choose a Community Priority Evaluation Provider (CPE Provider) must include mechanisms to ensure appropriate feedback from the ICANN community. In addition, any terms included in the contract between ICANN org and the CPE Provider regarding the CPE process must be subject to public comment.*
*Recommendation 34.16**: All Community Priority Evaluation procedures (including any supplemental dispute provider rules) must be developed and published before the opening of the application submission period and must be readily and publicly available.*
_______________________________________________ SubPro-IRT mailing list -- subpro-irt@icann.org To unsubscribe send an email to 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.