- SubPro-IRT - lists.icann.org

Post call | SubPro IRT Meeting #153 | 19 August 2025
by Next Round Policy Implementation Aug. 19, 2025

Aug. 19, 2025

Dear All, The recordings for Meeting #153 of the SubPro IRT held on Tuesday, 19 August 2025 are published on the meeting wiki page<https://icann-community.atlassian.net/wiki/x/KYCNEw>. These include: * Audio recording * Zoom recording (including audio, visual, rough transcript, chat) * Attendance * Deck For additional information, you may consult the mailing list archives<https://mm.icann.org/pipermail/subpro-irt/> and the main wiki page<https://community.icann.org/x/pQM5Dg>. Best regards, Renate

1 0

CPE
by Anne ICANN Aug. 19, 2025

Aug. 19, 2025

Jared, Thanks for your patience with all of us as we discussed the parameters of the CPE Evaluator's limits on independent research. I do agree that it can be made clearer that such necessary research extends to public comment, letters of support, letters of opposition, and other issues reasonably raised in the mind of the evaluator regarding the community status of the applicant. I do *not* agree, as someone remarked (maybe Kathy?) in today's session, that there is a problem with the "weighting" in the CPE scoring process. The scoring was thoroughly discussed in the IRT. Just by way of example using the hypothetical raised in an ALAC meeting in Prague and again in some negative public comment, the fact that a larger community may exist, should not disqualify an applicant from establishing community status in its own self-identified community. For example, the Eastern Band of Cherokee Indians that governs the town of Cherokee, North Carolina, is a smaller community group than the Cherokee Nation but that does not mean the the Cherokee Nation would automatically object to the Eastern Band application for .cherokee. In fact, it might be supported. The real issue is what type of application is competing for the same string with that smaller community application - is it community based or not? If it's not, the community that qualifies prevails and does not have to bid at auction (e.g. against Jeep). If both qualify as communities, then they have to compete in an auction. Further, the CPE Panel is clearly not required to go "fishing" for communities that have not applied for the string but which are entitled to file objections and letters of opposition. The Community Objection process is established to maintain the balance. Letters of opposition are also relevant and that is why the panel must be free to conduct independent research re same. Bottom line the IRT cannot substitute its judgment for that of an expert CPE Evaluator, which is also empowered under the RFP to retain experts on the particular community under consideration. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso(a)gmail.com

2 1

Re: [Ext] Re: Re: Draft CPE Vendor Selection Criteria
by Jared Erwin Aug. 18, 2025

Aug. 18, 2025

Dear Juan and IRT members, Please see my responses in red below. ICANN has taken this feedback into account and made updates to this portion of the RFP, where relevant/appropriate. ICANN expects now to publish the RFP by mid-week. We will notify the IRT once it is published. As we are on a time crunch and have already delayed publication, we will not be able to make any further updates to the RFP, but as noted below, many of the issues can be discussed with providers in the RFP process and/or during contract negotiation. Thank you again for the input. Best, Jared From: Juan Manuel Rojas <jumaropi(a)yahoo.com> Reply-To: Juan Manuel Rojas <jumaropi(a)yahoo.com> Date: Sunday, August 17, 2025 at 17:14 To: Jared Erwin <jared.erwin(a)icann.org>, Justine Chew <justine.chew.icann(a)gmail.com> Cc: "subpro-irt(a)icann.org" <subpro-irt(a)icann.org> Subject: [Ext] Re: [SubPro-IRT] Re: Draft CPE Vendor Selection Criteria Hi Jared, Thanks for the update. Regarding to this topic we are proposing the following additions: 1. To 1A, adding the bullet point: “The provider must also ensure that its evaluation methodology and clarifying questions are documented in clear, non-technical language to facilitate transparency and public accountability.” ICANN has added “The provider must also ensure that its evaluation methodology and clarifying questions are documented in plain language” to 3b. However, ICANN notes that clarifying questions are not public so the reference to transparency and public accountability do not seem relevant. 2A. To 2A, adding the bullet points: “- include vulnerable communities such as indigenous peoples, linguistic minorities, marginalized populations, or communities with limited digital infrastructure; Added “- represent non-commercial organizations including non-governmental organizations (NGOs), community-based organizations, civil society groups, and grassroots movements that may have different organizational structures and documentation practices than commercial entities.” Added 2B. To 2B, replacing newly-deleted sentence with: "Panels must include members with demonstrated experience in community-focused work across sectors, such as community development, community organization, engagement, or community studies. At least one panelist should have specific experience working with vulnerable communities, non-commercial organizations, or marginalized populations." As discussed, ICANN believes this is potentially too limiting to include in the RFP, such that the number and quality of responses could be hindered. ICANN will take this into consideration as it reviews bidder responses and conducts bidder interviews and ultimately as it selects a provider. To 2B, New addition: “The provider must demonstrate capability to identify when applications involve vulnerable communities or non-commercial organizations that may require specialized evaluation approaches, including: · Understanding of different organizational structures and governance models used by non-commercial entities · Recognition of potential barriers faced by vulnerable communities in documentation or application processes · Ability to assess community support and legitimacy using culturally appropriate methods” ICANN believes this is covered by the following language in the RFP: * “Provider and Panelists will need to determine when the Panel requires supplemental experience and/or expertise in a specific community to appropriately validate the application information and/or comments or letters received related to the application. The Panel may need to perform other limited validating research as required. Any research must be disclosed to the applicant. · The Provider should demonstrate what processes and mechanisms they’ve developed for identifying such situations and for acquiring required expertise. “ To 3A or B add: “Panels must reflect geographic, cultural, and stakeholder diversity to ensure balanced evaluation of applications from different regions and community types.” ICANN has added some language to this effect based on similar comments from the ALAC. To the bullets of 4A, we seek the important additions of - recognizing and accommodating different communication styles, organizational structures, and documentation practices that may be used by vulnerable communities and non-commercial organizations, and -applying cultural competency when evaluating applications from indigenous peoples, linguistic minorities, or other marginalized communities ICANN has added the following: Panel should be able to recognize through its own expertise or through consultation with supplemental non-evaluators the different types and needs of communities, such as communication styles, organizational structures, and documentation practices, especially when evaluating applications from indigenous peoples, linguistic minorities, or other marginalized communities To 6A, should be expanded based on 4.4.5.1 CPE Clarifying Questions to include those who submit letters of opposition, to read: “To avoid the appearance of any conflict of interest, all questions for the applicant OR THE PERSON OR ENTITY THAT SUBMITTEDA LETTER OF OPPOSITION TO A CPE applicant….” [caps for easy reading only] Updated To 6B, adding the sentence: “The provider must ensure that conflict of interest assessments consider potential biases or conflicts that may arise when evaluating applications from vulnerable communities or non-commercial organizations, including any unconscious bias that may affect fair evaluation of non-traditional applicants.“ ICANN believes this is covered by the existing conflict of interest language. Further, The Provider should make available to ICANN, and ICANN should publish, summary information regarding conflict-of-interest recusals to promote transparency while maintaining individual privacy.” ICANN will consider this further as it reviews bidder responses and moves to selection and contracting of a vendor. ---- We note that the edits above raise similar concerns to those raised Justine in her email, and provide detail and elaboration that her comment seeks and that we strongly agree is necessary. e.g., Justine’s 2A request to: “Consider elaborating on what ‘diverse panel’ means. We also fully agree that 2B is a “must” not a “should have.” This comment, in the tight timeframe, has the input and support of two active representatives of NPOC and NCSG. Best, Juan JUAN MANUEL ROJAS, M.Sc. Director - MINKA DIGITAL Colombia NPOC Chair - NCSG/GNSO M.Sc. Information Technology Registered Linux User No.533108. http://www.jmanurojas.com [jmanurojas.com]<https://urldefense.com/v3/__http:/www.jmanurojas.com__;!!PtGJab4!71OBdgYtHX…> -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GIT d- s: a+ C+++ UL P+ L+++ !E !W+++ !N !o K+++ w-- !O M- V PS+ PE-- Y+ PGP+ t+ 5 X++ R tv+ b+ DI D G e+++(+++)>+++ h+ r++ y+ ------END GEEK CODE BLOCK------ El sábado, 16 de agosto de 2025, 06:39:59 a.m. GMT-5, Justine Chew via SubPro-IRT <subpro-irt(a)icann.org> escribió: Dear Jared, Given the extremely short turnaround time, I was only able to work with 2 ALAC colleagues to review the earlier version of the Draft Selection Criteria. I also subsequently reviewed the updated version and offer our aggregated feedback on the updated version for consideration. Kind regards, Justine **** Feedback on Updated Version 1A * (per Anne's comment) It is unclear what "evaluation projects" means so we suggest stipulating that provider must have significant demonstrated expertise in projects which call for evaluating applications against a defined set of criteria. * Agree with deletion of "train" as provider should be expected to have or engage employees and/or subcontractors who already possess relevant expertise * If feasible, consider specifying in the RFP how each type of experience - relevant project management and community application evaluation - will be assessed (see also 2A below) * Would the RFP also address how provider should handle publication of the status of each evaluation, up to conclusion and including evaluation challenges? 1B * Consider including emphasizing timelines - we suggest that provider must demonstrate the ability to develop efficient work methods, evaluation/assessment approaches .... 2A * Consider elaborating on what "diverse panel" means. * Consider strengthening reliance on supplemental non-evaluator expertise as mandatory or at the very least, a strongly advisable action, rather than leaving that to the panel's discretion, assuming assessment of expertise in evaluating community applications may not be strictly measurable or determinable without clear and specific metrics * Consider suggesting that a panel has the option to draw on ICANN community volunteers as supplemental non-evaluators 2B * Panelist must have the necessary capabilities and/or experience to evaluate applications etc rather than just "should have" * Unless panelists possess the requisite experience in community-focused work across sectors, such as community development, community organization, engagement, management and/or community studies, then provider and panelists will need to rely on supplemental experience and/or expertise in a specific community - we should as far as possible avoid having provider and panelists insisting that supplemental non-evaluators are not needed when they should * Panel may need to perform other limited validating research as required 3A * Please include the element of "fair and consistent outcomes" in the demonstration required 3B and 6B * Processes governing changes in panel composition under circumstances such as conflict of interest or clear biasness, should reflect short timelines for the same, and at no cost to applicant. 10 * Provider must provide reference checks of relevant prior on evaluation services. Separately, how would ICANN org establish whether selected provider is carrying out its contracted services satisfactorily during the contracted period? On Sat, 16 Aug 2025 at 01:25, Jared Erwin via SubPro-IRT <subpro-irt(a)icann.org<mailto:subpro-irt@icann.org>> wrote: Dear IRT Members, As discussed, please see here the updated version of the Draft Selection Criteria [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/space…> (please give the link a moment to load to the relevant spot on the page). This includes redlines based on IRT feedback from our call on 12 August 2025 [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/space…>. I would kindly request any other feedback ASAP so that we can incorporate that by our publication date of Monday, 18 August 2025. Should you have trouble with the link above, the document is on the working documents page [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/space…>, under Topic 34. Thank you Jared From: Jared Erwin <jared.erwin(a)icann.org<mailto:jared.erwin@icann.org>> Date: Saturday, August 9, 2025 at 10:00 To: "subpro-irt(a)icann.org<mailto:subpro-irt@icann.org>" <subpro-irt(a)icann.org<mailto:subpro-irt@icann.org>> Subject: Draft CPE Vendor Selection Criteria Dear IRT Members, As discussed on Thursday, 7 August, I’m sharing here the draft CPE vendor selection criteria, which we will review in our call on Tuesday, 12 August at 12:00 UTC. The document can be found on the respective meeting page here: https://icann-community.atlassian.net/wiki/spaces/SPIR/pages/328105985/2025… [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/space…>. Thank you, Jared -- Jared Erwin Senior Director, New gTLD Program Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) jared.erwin(a)icann.org<mailto:jared.erwin@icann.org> _______________________________________________ SubPro-IRT mailing list -- subpro-irt(a)icann.org<mailto:subpro-irt@icann.org> To unsubscribe send an email to subpro-irt-leave(a)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. _______________________________________________ SubPro-IRT mailing list -- subpro-irt(a)icann.org<mailto:subpro-irt@icann.org> To unsubscribe send an email to subpro-irt-leave(a)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.

1 0

Re: [Ext] Re: Re: Draft CPE Vendor Selection Criteria
by Jared Erwin Aug. 18, 2025

Aug. 18, 2025

Dear Justine and IRT members, Please see my responses in red below. ICANN has taken this feedback into account and made updates to this portion of the RFP, where relevant/appropriate. ICANN expects now to publish the RFP by mid-week. We will notify the IRT once it is published. As we are on a time crunch and have already delayed publication, we will not be able to make any further updates to the RFP, but as noted below, many of the issues can be discussed with providers in the RFP process and/or during contract negotiation. Thank you again for the input. Best, Jared From: Justine Chew <justine.chew.icann(a)gmail.com> Date: Saturday, August 16, 2025 at 04:39 To: Jared Erwin <jared.erwin(a)icann.org> Cc: "subpro-irt(a)icann.org" <subpro-irt(a)icann.org> Subject: [Ext] Re: [SubPro-IRT] Re: Draft CPE Vendor Selection Criteria Dear Jared, Given the extremely short turnaround time, I was only able to work with 2 ALAC colleagues to review the earlier version of the Draft Selection Criteria. I also subsequently reviewed the updated version and offer our aggregated feedback on the updated version for consideration. Kind regards, Justine **** Feedback on Updated Version 1A * (per Anne's comment) It is unclear what "evaluation projects" means so we suggest stipulating that provider must have significant demonstrated expertise in projects which call for evaluating applications against a defined set of criteria. Updated * Agree with deletion of "train" as provider should be expected to have or engage employees and/or subcontractors who already possess relevant expertise Ok * If feasible, consider specifying in the RFP how each type of experience - relevant project management and community application evaluation - will be assessed (see also 2A below) ICANN has a scoring rubric that it uses internally to make such assessments. * Would the RFP also address how provider should handle publication of the status of each evaluation, up to conclusion and including evaluation challenges? Yes, this is covered in other areas of the RFP 1B * Consider including emphasizing timelines - we suggest that provider must demonstrate the ability to develop efficient work methods, evaluation/assessment approaches .... We note elsewhere in the RFP that “Completing individual evaluations within a 3-6 month timeframe. ICANN expects that there may be multiple evaluations occurring simultaneously and notes that the volume of evaluations could impact the time to completion. The provider should be prepared to complete a smaller batch of evaluations in 3-4 months, while a larger batch may take 4-6 months.” We will also emphasize this in any bidder interviews. 2A * Consider elaborating on what "diverse panel" means. We will attempt to elaborate on how a potential provider could understand “diverse” * Consider strengthening reliance on supplemental non-evaluator expertise as mandatory or at the very least, a strongly advisable action, rather than leaving that to the panel's discretion, assuming assessment of expertise in evaluating community applications may not be strictly measurable or determinable without clear and specific metrics. We will take this into consideration as we review bidder responses and conduct bidder interviews and ultimately work with a chosen vendor. ICANN believes it may be limiting in terms of bidder responses if we require this. * Consider suggesting that a panel has the option to draw on ICANN community volunteers as supplemental non-evaluators. We will take this into consideration as we review bidder responses and conduct bidder interviews and ultimately work with a chosen vendor. 2B * Panelist must have the necessary capabilities and/or experience to evaluate applications etc rather than just "should have" Updated * Unless panelists possess the requisite experience in community-focused work across sectors, such as community development, community organization, engagement, management and/or community studies, then provider and panelists will need to rely on supplemental experience and/or expertise in a specific community - we should as far as possible avoid having provider and panelists insisting that supplemental non-evaluators are not needed when they should We will take this into consideration as we review bidder responses and conduct bidder interviews and ultimately work with a chosen vendor. ICANN believes it may be limiting in terms of bidder responses if we require this. * Panel may need to perform other limited validating research as required Updated 3A * Please include the element of "fair and consistent outcomes" in the demonstration required This particular bullet has been removed but consistency is addressed later in the document. 3B and 6B * Processes governing changes in panel composition under circumstances such as conflict of interest or clear biasness, should reflect short timelines for the same, and at no cost to applicant. We have added the point about “reflecting short timelines”; the cost will be covered elsewhere in the RFP and in discussions with the potential bidders. However, it is ICANN’s presumption that there will only be a flat fee for the applicant, as described in the AGB. 10 * Provider must provide reference checks of relevant prior on evaluation services. Updated Separately, how would ICANN org establish whether selected provider is carrying out its contracted services satisfactorily during the contracted period? This is covered in other areas of the RFP which provides more details on scope of work/deliverables/timeframes. Such details would also be established during the contracting process/negotiation. On Sat, 16 Aug 2025 at 01:25, Jared Erwin via SubPro-IRT <subpro-irt(a)icann.org<mailto:subpro-irt@icann.org>> wrote: Dear IRT Members, As discussed, please see here the updated version of the Draft Selection Criteria [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/space…> (please give the link a moment to load to the relevant spot on the page). This includes redlines based on IRT feedback from our call on 12 August 2025 [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/space…>. I would kindly request any other feedback ASAP so that we can incorporate that by our publication date of Monday, 18 August 2025. Should you have trouble with the link above, the document is on the working documents page [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/space…>, under Topic 34. Thank you Jared From: Jared Erwin <jared.erwin(a)icann.org<mailto:jared.erwin@icann.org>> Date: Saturday, August 9, 2025 at 10:00 To: "subpro-irt(a)icann.org<mailto:subpro-irt@icann.org>" <subpro-irt(a)icann.org<mailto:subpro-irt@icann.org>> Subject: Draft CPE Vendor Selection Criteria Dear IRT Members, As discussed on Thursday, 7 August, I’m sharing here the draft CPE vendor selection criteria, which we will review in our call on Tuesday, 12 August at 12:00 UTC. The document can be found on the respective meeting page here: https://icann-community.atlassian.net/wiki/spaces/SPIR/pages/328105985/2025… [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/space…>. Thank you, Jared -- Jared Erwin Senior Director, New gTLD Program Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) jared.erwin(a)icann.org<mailto:jared.erwin@icann.org> _______________________________________________ SubPro-IRT mailing list -- subpro-irt(a)icann.org<mailto:subpro-irt@icann.org> To unsubscribe send an email to subpro-irt-leave(a)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.

1 0

NEW MEETING | SubPro IRT Meeting #155a | 27 August 2025, 12:00-14:00 UTC
by Next Round Policy Implementation Aug. 18, 2025

Aug. 18, 2025

Dear All, Meeting #155a of the SubPro IRT will be held on 27 August 2025 at 12:00-14:00 UTC [local time<https://tinyurl.com/ychykyje>]. Planned topics: TBA The final agenda can be consulted here<https://icann-community.atlassian.net/wiki/x/AYDIGQ>. Before the meeting, please be sure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/en/governance/documents/icann-community-anti-harassme…>. We would like to remind participants that to ensure transparency of participation in ICANN's multistakeholder model, we ask that you sign in to Zoom sessions using your full name. For example, First Name and Last Name or Surname. You may be removed from the session if you do not sign in using your full name. Zoom information: Join the Zoom Webinar directly (recommended): https://icann.zoom.us/j/97063459905?pwd=VUVsd0J0RnNtRXkyNXJFZW9vdTEzZz09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/97063459905?pwd=VUVsd0J0…> Meeting ID: 970 6345 9905 Passcode: DQ#0L.9x5e Zoom Audio only: One tap mobile +13462487799,,97063459905#,,,,*5806401747# US (Houston) +16699006833,,97063459905#,,,,*5806401747# US (San Jose) Meeting ID: 970 6345 9905 Passcode: 5806401747 Should you be unable to attend the meeting, please let us know in advance. A recording will be made available. Please do not hesitate to contact us should you have any questions. Best regards, Renate

1 0

CHANGE OF TIME | SubPro IRT Meeting #156 | 28 August 2025, 18:00-20:00 UTC
by Next Round Policy Implementation Aug. 18, 2025

Aug. 18, 2025

PLEASE NOTE THE CHANGE OF TIME – THIS CALL WILL NOW BE FROM 18:00 TO 20:00 UTC DO NOT FORGET TO UPDATE YOUR CALENDAR Dear All, Meeting #156 of the SubPro IRT will be held on 28 August 2025 at 18:00-20:00 UTC [local time<https://tinyurl.com/mrexfxpw>]. Planned topics: Data Privacy; String Similarity The final agenda can be consulted here<https://icann-community.atlassian.net/wiki/x/UYCOEw>. Before the meeting, please be sure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/en/governance/documents/icann-community-anti-harassme…>. We would like to remind participants that to ensure transparency of participation in ICANN's multistakeholder model, we ask that you sign in to Zoom sessions using your full name. For example, First Name and Last Name or Surname. You may be removed from the session if you do not sign in using your full name. Zoom information: Join the Zoom Webinar directly (recommended): https://icann.zoom.us/j/97063459905?pwd=VUVsd0J0RnNtRXkyNXJFZW9vdTEzZz09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/97063459905?pwd=VUVsd0J0…> Meeting ID: 970 6345 9905 Passcode: DQ#0L.9x5e Zoom Audio only: One tap mobile +13462487799,,97063459905#,,,,*5806401747# US (Houston) +16699006833,,97063459905#,,,,*5806401747# US (San Jose) Meeting ID: 970 6345 9905 Passcode: 5806401747 Should you be unable to attend the meeting, please let us know in advance. A recording will be made available. Please do not hesitate to contact us should you have any questions. Best regards, Renate

1 0

CHANGE OF TIME - EARLIER CALL | SubPro IRT Meeting #155 | 26 August 2025, 04:00-06:00 UTC
by Next Round Policy Implementation Aug. 18, 2025

Aug. 18, 2025

PLEASE NOTE THE CHANGE OF TIME – THIS CALL WILL NOW BE FROM 04:00 TO 06:00 UTC DO NOT FORGET TO ADJUST YOUR CALENDAR Dear All, Meeting #155 of the SubPro IRT will be held on 26 August 2025 at 04:00-06:00 UTC [local time<https://tinyurl.com/3f8hnrh5>]. Planned topics: Community Input The final agenda can be consulted here<https://icann-community.atlassian.net/wiki/x/KQCOEw>. Before the meeting, please be sure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/en/governance/documents/icann-community-anti-harassme…>. We would like to remind participants that to ensure transparency of participation in ICANN's multistakeholder model, we ask that you sign in to Zoom sessions using your full name. For example, First Name and Last Name or Surname. You may be removed from the session if you do not sign in using your full name. Zoom information: Join the Zoom Webinar directly (recommended): https://icann.zoom.us/j/97063459905?pwd=VUVsd0J0RnNtRXkyNXJFZW9vdTEzZz09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/97063459905?pwd=VUVsd0J0…> Meeting ID: 970 6345 9905 Passcode: DQ#0L.9x5e Zoom Audio only: One tap mobile +13462487799,,97063459905#,,,,*5806401747# US (Houston) +16699006833,,97063459905#,,,,*5806401747# US (San Jose) Meeting ID: 970 6345 9905 Passcode: 5806401747 Should you be unable to attend the meeting, please let us know in advance. A recording will be made available. Please do not hesitate to contact us should you have any questions. Best regards, Renate

1 0

Post call | SubPro IRT Meeting #151 | 12 August 2025
by Next Round Policy Implementation Aug. 18, 2025

Aug. 18, 2025

Dear All, The recordings for Meeting #152 of the SubPro IRT held on Thursday, 14 August 2025 are published on the meeting wiki page<https://icann-community.atlassian.net/wiki/x/KYCOEw>. These include: * Audio recording * Zoom recording (including audio, visual, rough transcript, chat) * Attendance * Deck For additional information, you may consult the mailing list archives<https://mm.icann.org/pipermail/subpro-irt/> and the main wiki page<https://community.icann.org/x/pQM5Dg>. Best regards, Renate

1 0

REMINDER | SubPro IRT Meeting #153 | 19 August 2025, 04:00-06:00 UTC
by Next Round Policy Implementation Aug. 18, 2025

Aug. 18, 2025

Dear All, Meeting #153 of the SubPro IRT will be held on one hour on 19 August 2025 at 04:00-06:00 UTC [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/smbdf7uc__;!!PtGJab4!5ryk1zJ…>]. Planned topics: Appendix 6: Predictability; Module 2: Order of Application Processing and Prioritization Draw; Module 3: Community Input, Objections, and Appeals The final agenda can be consulted here [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/KYC…>. Before the meeting, please be sure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/en/governance/documents/icann-community-anti-harassme…>. We would like to remind participants that to ensure transparency of participation in ICANN's multistakeholder model, we ask that you sign in to Zoom sessions using your full name. For example, First Name and Last Name or Surname. You may be removed from the session if you do not sign in using your full name. Zoom information: Join the Zoom Webinar directly (recommended): https://icann.zoom.us/j/97063459905?pwd=VUVsd0J0RnNtRXkyNXJFZW9vdTEzZz09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/97063459905?pwd=VUVsd0J0…> Meeting ID: 970 6345 9905 Passcode: DQ#0L.9x5e Zoom Audio only: One tap mobile +13462487799,,97063459905#,,,,*5806401747# US (Houston) +16699006833,,97063459905#,,,,*5806401747# US (San Jose) Meeting ID: 970 6345 9905 Passcode: 5806401747 Should you be unable to attend the meeting, please let us know in advance. A recording will be made available. Please do not hesitate to contact us should you have any questions. Best regards, Renate

1 0

REMINDER | SubPro IRT Meeting #153 | 19 August 2025, 04:00-06:00 UTC
by Next Round Policy Implementation Aug. 18, 2025

Aug. 18, 2025

Dear All, Meeting #153 of the SubPro IRT will be held on 19 August 2025 at 04:00-06:00 UTC [local time<https://tinyurl.com/smbdf7uc>]. Planned topics: Appendix 6: Predictability; Module 2: Order of Application Processing and Prioritization Draw; Module 3: Community Input, Objections, and Appeals The final agenda can be consulted here<https://icann-community.atlassian.net/wiki/x/KYCNEw>. Before the meeting, please be sure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/en/governance/documents/icann-community-anti-harassme…>. We would like to remind participants that to ensure transparency of participation in ICANN's multistakeholder model, we ask that you sign in to Zoom sessions using your full name. For example, First Name and Last Name or Surname. You may be removed from the session if you do not sign in using your full name. Zoom information: Join the Zoom Webinar directly (recommended): https://icann.zoom.us/j/97063459905?pwd=VUVsd0J0RnNtRXkyNXJFZW9vdTEzZz09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/97063459905?pwd=VUVsd0J0…> Meeting ID: 970 6345 9905 Passcode: DQ#0L.9x5e Zoom Audio only: One tap mobile +13462487799,,97063459905#,,,,*5806401747# US (Houston) +16699006833,,97063459905#,,,,*5806401747# US (San Jose) Meeting ID: 970 6345 9905 Passcode: 5806401747 Should you be unable to attend the meeting, please let us know in advance. A recording will be made available. Please do not hesitate to contact us should you have any questions. Best regards, Renate

1 0