Post call | SubPro IRT Meeting #76 | 3 October 2024

Dear All, The recordings for Meeting #76 of the SubPro IRT held on Thursday, 3 October 2024 at 19:00-20:00 UTC are published on the meeting wiki page<https://community.icann.org/x/CIHKFQ>. 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

Dear Kristy and Sam, Firstly, my apologies for not being able to join the discussion during the 3rd Oct call. I have just listened to the recording and would like to take the opportunity to share some input. I will, however, at this point, limit my input to a single issue regarding the terms and conditions for ASP. *1. Change in financial conditions* I concur with Jeff Neuman in that there should *not* be gap the applicability of terms and conditions for an ASP applicant such that any terms and conditions should apply at the point of application for ASP and continue to apply until the applicant enters into an RA (assuming it's successful all the way through). The earlier text on clause 4 that went out for public comment *did* reflect such a gap which the ALAC's comment then sought to close. However, in agreeing with Anne Aikman-Scalese's point that we should not penalize an applicant's change in financial means at the point of application for a gTLD string (which we had also expressed support for earlier), *it is now clear that the relevant portion of the text in clause 4 should perhaps be separated* to address both concerns. For this, please see suggested changes for consideration / further fine-tuning: "4. While there is no fee to apply to the Applicant Support Program,
Applicant acknowledges that the intent of the Applicant Support Program is to make the New gTLD Program evaluation fees and processes accessible to entities that would like to operate a gTLD but would otherwise be unable to apply to the New gTLD Program because of financial and resource constraints.
The Applicant Support Program is not intended to provide support to
applying entities that (a) were created by, are affiliated with existing gTLD Registry Operators or prospective applicants to the New gTLD Program that would not meet the certain criteria of the Applicant Support Program up to when ICANN proposes to delegate the new gTLD and enters into a Registry Agreement with the Applicant or (b) have sufficient ongoing funding or investment from other sources at the time this Application is submitted or when ICANN proposes to delegate the new gTLD. If Applicant is found to have abused the intent of the ASP Program, Applicant may be excluded from participation in the New gTLD Program entirely.
Before submitting this Application to participate in the ASP Program,
Applicant should carefully review the eligibility requirements for the ASP Program set forth in the Handbook to determine whether Applicant meets such criteria. If prior to the delegation of a new gTLD ICANN determines, in its sole discretion, that majority control and/or “Eligible Entity” type of the Applicant’s financial conditions has/have changed and the Applicant would not have been eligible or qualified for the financial support under the Applicant Support Program, then (a) at ICANN’s request the Applicant will pay ICANN the full gTLD evaluation fee promptly upon request, or (b) ICANN may reject the Application without any liability or recourse to the Applicant."
And we should not conflate the above guardrails against change in eligibility with the "paying it forward" idea. I look forward to discussing this and other issues on ASP terms and conditions in an upcoming call. Kind regards, Justine On Fri, 4 Oct 2024 at 16:04, Next Round Policy Implementation via SubPro-IRT <subpro-irt@icann.org> wrote:
Dear All,
The recordings for Meeting #76 of the SubPro IRT held on Thursday, 3 October 2024 at 19:00-20:00 UTC are published on the meeting wiki page <https://community.icann.org/x/CIHKFQ>.
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
_______________________________________________ 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.

Dear Justine, We were sorry to miss you but many thanks for sharing this additional input. Let us take these thoughtful comments back to discuss and we’ll come back on list (or via another meeting) as needed. We may come back with some questions on-list to inform additional changes. Thanks again and hope to catch you on the next meeting! Kind regards, Kristy On Oct 6, 2024, at 00:48, Justine Chew <justine.chew.icann@gmail.com> wrote: Dear Kristy and Sam, Firstly, my apologies for not being able to join the discussion during the 3rd Oct call. I have just listened to the recording and would like to take the opportunity to share some input. I will, however, at this point, limit my input to a single issue regarding the terms and conditions for ASP. 1. Change in financial conditions I concur with Jeff Neuman in that there should not be gap the applicability of terms and conditions for an ASP applicant such that any terms and conditions should apply at the point of application for ASP and continue to apply until the applicant enters into an RA (assuming it's successful all the way through). The earlier text on clause 4 that went out for public comment did reflect such a gap which the ALAC's comment then sought to close. However, in agreeing with Anne Aikman-Scalese's point that we should not penalize an applicant's change in financial means at the point of application for a gTLD string (which we had also expressed support for earlier), it is now clear that the relevant portion of the text in clause 4 should perhaps be separated to address both concerns. For this, please see suggested changes for consideration / further fine-tuning: "4. While there is no fee to apply to the Applicant Support Program, Applicant acknowledges that the intent of the Applicant Support Program is to make the New gTLD Program evaluation fees and processes accessible to entities that would like to operate a gTLD but would otherwise be unable to apply to the New gTLD Program because of financial and resource constraints. The Applicant Support Program is not intended to provide support to applying entities that (a) were created by, are affiliated with existing gTLD Registry Operators or prospective applicants to the New gTLD Program that would not meet the certain criteria of the Applicant Support Program up to when ICANN proposes to delegate the new gTLD and enters into a Registry Agreement with the Applicant or (b) have sufficient ongoing funding or investment from other sources at the time this Application is submitted or when ICANN proposes to delegate the new gTLD. If Applicant is found to have abused the intent of the ASP Program, Applicant may be excluded from participation in the New gTLD Program entirely. Before submitting this Application to participate in the ASP Program, Applicant should carefully review the eligibility requirements for the ASP Program set forth in the Handbook to determine whether Applicant meets such criteria. If prior to the delegation of a new gTLD ICANN determines, in its sole discretion, that majority control and/or “Eligible Entity” type of the Applicant’s financial conditions has/have changed and the Applicant would not have been eligible or qualified for the financial support under the Applicant Support Program, then (a) at ICANN’s request the Applicant will pay ICANN the full gTLD evaluation fee promptly upon request, or (b) ICANN may reject the Application without any liability or recourse to the Applicant." And we should not conflate the above guardrails against change in eligibility with the "paying it forward" idea. I look forward to discussing this and other issues on ASP terms and conditions in an upcoming call. Kind regards, Justine On Fri, 4 Oct 2024 at 16:04, Next Round Policy Implementation via SubPro-IRT <subpro-irt@icann.org<mailto:subpro-irt@icann.org>> wrote: Dear All, The recordings for Meeting #76 of the SubPro IRT held on Thursday, 3 October 2024 at 19:00-20:00 UTC are published on the meeting wiki page<https://community.icann.org/x/CIHKFQ>. 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 _______________________________________________ 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.
participants (3)
-
Justine Chew
-
Kristy Buckley
-
Next Round Policy Implementation