October 2024 - SubPro-IRT - lists.icann.org

Evaluation Challenges
by Elisa Busetto Oct. 29, 2024

Oct. 29, 2024

Dear IRT members, Please find the Evaluation Challenges proposed language: drive<https://docs.google.com/document/d/1qMl_AyyEaPHqfK1CKT7CEpm6zCVjl6Q-ppiJrh9…>, pdf<https://community.icann.org/download/attachments/315490346/EXT_Topic%2032_E…>. Best regards, Elisa

1 1

SubPro-IRT invitation to GDS reception in Istanbul | 11 November 2024, 17:30-19:00 IST
by Next Round Policy Implementation Oct. 29, 2024

Oct. 29, 2024

Dear IRT members, As we are preparing for the ICANN81 public meeting in Istanbul, we are conscious of the large amount of work ICANN collectively is handling. We’d like to express our continued appreciation for the support you provide in particular to the policy implementation work underway with the Global Domains & Strategy (GDS) function. Your work is enabling several key achievements, including the rollout of the Registration Data Policy, the coming opening of Applicant Support and Registry Service Provider evaluation aspects of the New gTLD Program: Next Round, and others. The GDS team invites you to join us for a small reception on Monday, 11 November from 17:30 to 19:00 local time at the conference venue in Istanbul. For reference, travel time from the venue to the host reception scheduled from 18:30 to 21:00 at the Atatürk Cultural Centre is a 15-minute walk. GDS and other team members who are supporting the meeting on the ground in Istanbul will be pleased to see you there. We’ll have some light food and drinks available, and will especially value the time to catch up and to thank the many Implementation Review Team (IRT) members for their continued support this year on a number of complex and important issues. Sincerely, Theresa Swinehart ICANN SVP, Global Domains & Strategy

1 0

Responses to Questions re: Community Commitments vs. RVCs vs. CPE
by Jared Erwin Oct. 28, 2024

Oct. 28, 2024

Dear IRT members, In follow-up to our discussion last week and in preparation for further discussion in a few hours, I have prepared some responses to the questions that came up last week regarding community commitments as it relates to CPE. I’d like to propose that we spend maybe only the first 10 minutes of our discussion on this and then move to a review of the criteria. Thank you, Jared Question(s) from IRT: What is the difference between an RVC and a Community Commitment? Do an applicant's Community Commitments have to be an RVC? Are all Community Commitments evaluated in the same way as RVCs? What are examples of Community Commitments? As set out by the SubPro Final Report, there are different types of gTLDs. A “community” gTLD string is a specific type of application, and, if delegated, the gTLD is differentiated from a generic gTLD by having a Specification 12. Community commitments are required by every community applicant (regardless of contention status), which are enshrined in Spec 12. It is not necessarily true that they would be part of Spec 11 (for RVCs) but could be depending on the applicant's choice and/or any objections/GAC advice. The draft AGB text on PICs/RVCs notes that the community registration policies must be evaluated and meet the same criteria as those that will be applied to the evaluation of RVCs. However, there are some key distinctions between “community commitments”, RVCs, and the Community Priority Evaluation (CPE) criteria. When an applicant designates its application as “community” the applicant will be asked to answer a series of additional questions that are specific to community gTLD applications and will be used to evaluate the application against the CPE criteria. These questions will cover the following areas: · Criterion 1: Community Establishment · Criterion 2: Nexus · Criterion 3: Registration Policies · Criterion 4: Community Endorsement The “community commitments” that will be evaluated using the “RVC evaluation criteria” are the “community registration policies” that are called for in Criterion 3 above. The current draft AGB PICs/RVCs text is proposing to evaluate these registrations policies related to Criterion 3 against the RVC criteria and NOT the information provided for Criteria 1, 2, and 4, because registration policies are the only “commitments” that will result in binding additional commitments in the applicable RA. The other criteria require the applicant to demonstrate, at the time of application, the existence of a community, the string’s nexus to the community, and endorsement of the community, but this type of information would not be expected to result in ongoing, enforceable commitments in the applicable RA. To summarize, registration policies proposed by applicants for community gTLDs will be evaluated using the criteria developed for the evaluation of registry voluntary commitments. These community registration policies could look very similar to commitments proposed as RVCs by non-community applicants, but they will live in Specification 12 because the applied-for gTLD is a community gTLD. ICANN is preparing guidelines and questions to assist applicants in their preparation of RVCs. -- Jared Erwin 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>

5 4

REMINDER | SubPro IRT Meeting #83 | 29 October 2024, 12:00-14:00 UTC
by Next Round Policy Implementation Oct. 28, 2024

Oct. 28, 2024

Dear All, Meeting #83 of the SubPro IRT will be held on 29 October 2024 at 12:00-14:00 UTC [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/yc8mvhfs__;!!PtGJab4!4R9S5Ht…>]. The agenda can be consulted here<https://community.icann.org/x/JIAUFg>. We will be covering: Material Types & 4. Different TLD Types 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>. 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

SubPro IRT Meeting #83a | 30 October 2024, 21:00-22:00 UTC
by Next Round Policy Implementation Oct. 28, 2024

Oct. 28, 2024

Dear All, Meeting #83a of the SubPro IRT will be held on 30 October 2024 at 21:00-22:00 UTC [local time<https://tinyurl.com/3y4zzeu3>]. The agenda can be consulted here<https://community.icann.org/x/EoATFw>. 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>. 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

IRT meeting on 30 October 2024 at 21:00 UTC
by Elisa Busetto Oct. 25, 2024

Oct. 25, 2024

Dear IRT members, We would like to inform you that we will hold an additional IRT meeting on 30 October 2024 at 21:00 UTC to continue the discussions on CPE. The calendar invite will go out on Monday. Best regards, Elisa

1 0

Post call | SubPro IRT Meeting #82 | 24 October 2024
by Next Round Policy Implementation Oct. 25, 2024

Oct. 25, 2024

Dear All, The recordings for Meeting #82 of the SubPro IRT held on Thursday, 24 October 2024 at 19:00-20:30 UTC are published on the meeting wiki page<https://community.icann.org/x/BoAUFg> These include: * Attendance * Audio recording * Zoom recording (including audio, visual, rough transcript, chat) 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 #82 | 24 October 2024, 19:00-20:30 UTC
by Next Round Policy Implementation Oct. 24, 2024

Oct. 24, 2024

Dear All, Meeting #82 of the SubPro IRT will be held in one hour on 24 October 2024 at 19:00-20:30 UTC [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/bxu87zfu__;!!PtGJab4!4SY9TG5…>]. The agenda can be consulted here<https://community.icann.org/x/BoAUFg>. 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>. 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 #82 | 24 October 2024, 19:00-20:30 UTC
by Next Round Policy Implementation Oct. 23, 2024

Oct. 23, 2024

Dear All, Meeting #82 of the SubPro IRT will be held on 24 October 2024 at 19:00-20:30 UTC [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/bxu87zfu__;!!PtGJab4!4SY9TG5…>]. The agenda can be consulted here<https://community.icann.org/x/BoAUFg>. 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>. 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

[For Review] ASP T&Cs Updates
by Kristy Buckley Oct. 22, 2024

Oct. 22, 2024

Greetings IRT colleagues, Further to our discussions during IRT meeting #78<https://community.icann.org/pages/viewpage.action?pageId=365592854> and based upon the input so far on the ASP Terms & Conditions (T&Cs), it seems we may be grappling with some more fundamental questions. Before diving into wordsmithing the T&Cs, we thought it might be helpful to tee up some “food-for-thought” IRT discussion questions and scenarios, outlined below. Discussion Questions: 1. In relation to Public Responsibility Due Diligence: * Can the applicant become affiliated with an existing RO/gTLD applicant after qualifying? * Can the supported applicant act counter to international law? 2. In relation to Financial Need: * Does a supported applicant have to be financially needy to receive each subsequent financial support? 3. In relation to Financial Viability: * This is covered by deposit and paying discounted gTLD eval fee; then by the gTLD Financial Evaluation. 4. In relation to Eligible Entities: * Can a supported applicant change their entity type after qualifying? * If we allow the supported applicant to change control as a prospective or actual gTLD applicant, how do we harmonize this with ASP Handbook<https://newgtldprogram.icann.org/sites/default/files/documents/next-round-a…> Restriction 4.6.6 that does not allow change of control for the first three years as an RO? * [Note: ASP Handbook Restriction 4.6.6 indicates that supported applicants that progress to delegation will be restricted from assigning the Registry Agreement or change of control for a period of three years unless for necessary reasons, in-line with a modified approach to SubPro IG 17.17 discussed with the ASP-IRT]. In relation to each of these questions, we’ve also developed an attached infographic to help share our thinking on the T&Cs (and in particular, T&Cs Section 4) in relation to the ASP evaluation criteria. The orange bars in the graphic illustrate our proposal for the period of time the applicant is expected to adhere with each of the ASP evaluation criteria categories. The yellow diamonds indicate potential checkpoints, where ICANN may, at its discretion, request documentation or information from the supported applicant/RO before it receives the next financial support. This approach is in alignment with ICANN’s mission as a nonprofit public-benefit corporation. Scenarios As you’re reviewing the ASP T&Cs, it may be helpful to consider some potential scenarios we may encounter with supported applicants: * Scenario 1: a small non-profit organization qualifies for support and receives the gTLD evaluation fee discount. It then receives a US $500K grant to support their future efforts as a Registry Operator. No other material changes are made on the supported applicant side. * If ICANN were to check/reaffirm eligibility prior to the applicant receiving a discount on a conditional evaluation fee, the supported applicant would still be eligible to receive the discount. * Scenario 2: a small social enterprise business qualifies for support. Prior to applying for a gTLD, the supported applicant sells a controlling share to an existing Registry Operator in return for a US $8M investment. * If ICANN were to check/reaffirm eligibility prior to the applicant receiving a discount on the gTLD evaluation fee, the supported applicant would no longer be eligible to receive a discount because they are affiliated with another Registry Operator (Public Responsibility Due Diligence) and they no longer meet the Financial Need nor Small Business requirements (<$5M USD in revenue, sales, cash and cash equivalents). * Scenario 3: a non-governmental organization qualifies for support and receives gTLD evaluation and conditional fee discounts. After passing the gTLD evaluation, prior to delegation, the applicant converts its status to a for-profit entity and auctions off the business. A Fortune 500 company buys the business. * If ICANN were to check/reaffirm eligibility prior to the Registry Operator (RO) receiving reduced base Registry Agreement fees, the RO would no longer be eligible for the discount. * [Note: ASP Handbook Restriction 4.6.6 indicates that supported applicants that progress to delegation will be restricted from assigning the Registry Agreement or change of control for a period of three years unless for necessary reasons, in-line with a modified approach to SubPro IG 17.17 discussed with the ASP-IRT. If the eligibility entity status is not required post-qualification per the T&Cs, the supported applicant can sell their business to another RO or gTLD applicant, increasing the risk of gaming and abuse.] I realize this is a lot of information to digest via email. As such, we will also prepare this information into slides but we wanted to share our thinking in advance of IRT meeting #81 on Tuesday to help inform our discussions. We have also attached the latest redline of the ASP Terms & Conditions (T&Cs) for your review. We will post a comparative redline to the 30 Sept version to the EXT Drive on Monday. Of course, please feel free to share your views on-list in advance of the meeting. Many thanks for your thinking on this and we look forward to meeting next week. Kind regards, Kristy, on behalf of the ASP Project Team

2 2