August 2024 - Subpro-irt-asp

SubPro IRT ASP Sub-Track Meeting #25 | 19 September 2024, 18:00-19:00 UTC
by Next Round Policy Implementation Aug. 20, 2024

Aug. 20, 2024

Dear All, Meeting #25 of the SubPro IRT ASP Sub-Track will be held on 19 September 2024 at 18:00-19:00 UTC [local time<https://tinyurl.com/akp727u6>]. The agenda can be consulted here<https://community.icann.org/x/OoALFg>. 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/93075290767?pwd=MHl2YzBoc1Vyd2hkbC9xOTNwdlgvUT09 Meeting ID: 930 7529 0767 Passcode: 7Dg4fef%=2 Audio only One tap mobile +19294362866,,93075290767#,,,,*4781543838# US (New York) +12532158782,,93075290767#,,,,*4781543838# US (Tacoma) Find your local number: https://icann.zoom.us/u/aDZ2vqhHu Meeting ID: 930 7529 0767 Passcode: 4781543838 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

Re: Follow-up Items | ASP Handbook
by Samantha Mancia Aug. 12, 2024

Aug. 12, 2024

Hello ASP IRT Sub-Track, I hope you are well. As Kristy is out this week, I wanted to provide an update on the action item below: 1. Once available, Kristy to confirm on list that we’ve consulted internally on the latest financial need indicator (link to comment<https://docs.google.com/document/d/18aQYgEs-sTNmsCpggazQWREWI12f5t_z/edit?d…>). We have indeed consulted internally and confirmed the current language in the ASP Handbook that we discussed on call<https://community.icann.org/pages/viewpage.action?pageId=353173560> is ok to proceed. Thanks again to those of you who provided your feedback. At this stage we’re going to clean up the ASP Handbook and get it ready for publication, aiming for the end of this week on the ASP Website: https://newgtldprogram.icann.org/en/application-rounds/round2/asp/handbook As discussed, the Board-approved version of the ASP Handbook is pending the Board-GAC consultation in September, but in the meantime we are posting version 3 on the website to support communications and outreach efforts. In line with our project schedule and availability of translation services, we are proceeding with publication of the English version while the other five ICANN language versions are being developed. These will be posted as soon as they are available. Again, expressing our gratitude for all of your thoughtful input and contributions to the work we have done to get here! Kind Regards, Samantha Mancia Project Manager, New gTLD Program Team Internet Corporation for Assigned Names and Numbers (ICANN) Office Telephone: +1 310 301 5800 www.icann.org<http://www.icann.org> From: Kristy Buckley <kristy.buckley(a)icann.org> Date: Thursday, August 1, 2024 at 1:51 PM To: "SubPro-IRT-asp(a)icann.org" <SubPro-IRT-asp(a)icann.org> Cc: Samantha Mancia <samantha.mancia(a)icann.org> Subject: Follow-up Items | ASP Handbook Greetings ASP-IRT members, Many thanks for taking the time to join us again today. I know many of you were juggling other meetings simultaneously or back-to-back. Much appreciated. As promised, we are sharing additional comments on-list for your review. We kindly request any additional questions or comments on-list by 23:59 UTC Monday 5 August. This will allow us to finalize preparations for posting v3 of the Handbook on the ASP website<https://newgtldprogram.icann.org/en/application-rounds/round2/asp/handbook> and to ensure translation of the ASP Handbook into the ICANN languages in a timely fashion. Below please see the follow-up items from today as well as the remaining Handbook comments to review. Kind regards, Kristy, on behalf of the ASP Project Team ---- Follow up items from today's meeting: 1. Once available, Kristy to confirm on list that we’ve consulted internally on the latest financial need indicator (link to comment<https://docs.google.com/document/d/18aQYgEs-sTNmsCpggazQWREWI12f5t_z/edit?d…>). 2. Kristy and Sam to consult internally about the possibility of offering the fee discount to ASP applicants still awaiting ASP evaluation results by the time the gTLD application submission period begins (as opposed to offering a refund if they qualify). ICANN org will update on-list and/or bring this to the full IRT in relation topical discussions about the gTLD fee, withdrawals, refunds, etc. Remaining Handbook comments to review: 1. In Section 4.6: Restrictions: In light of Justine's question around distinguishing between Terms and Conditions (T&Cs) and Restrictions, and given that the T&Cs are currently out for public comment, what does the IRT think about keeping this language out of the ASP Handbook and instead leaving in Terms & Conditions and potentially the AGB? In the Handbook we are suggesting removal of text (4.6.4) because it is already in the ASP T&Cs (link to comment<https://docs.google.com/document/d/18aQYgEs-sTNmsCpggazQWREWI12f5t_z/edit?d…>) and subject to changes following public comment on the T&Cs. 1. In Section 4.6: Restrictions: following our discussion on 1 August, we propose keeping the restriction (4.6.7) related to the future Registry Agreement which is for ROs, not ASP applicants, but it seems important to flag to prospective ASP applicants. (link to comment<https://docs.google.com/document/d/18aQYgEs-sTNmsCpggazQWREWI12f5t_z/edit?d…>) 1. In Section 4.6: Restrictions: Addition of cross reference to change requests section to 4.6.1 (link to comment<https://docs.google.com/document/d/18aQYgEs-sTNmsCpggazQWREWI12f5t_z/edit?d…>). Handbook text pasted below: For information on restrictions related to application change requests, please see Section 5.1: Changes to ASP Applications<https://docs.google.com/document/d/18aQYgEs-sTNmsCpggazQWREWI12f5t_z/edit#h…>. 1. In Section 5: Applicant Support Program Application Process: Additional detail on privacy policies added in place of the link to the bylaws (link to comment<https://docs.google.com/document/d/18aQYgEs-sTNmsCpggazQWREWI12f5t_z/edit?d…>). Handbook text pasted below: Personal data processed for the New gTLD Program will be deleted when it is no longer needed for stated purposes, subject to legal requirements, while taking into account ICANN org’s overarching mandate to operate to the maximum extent feasible in an open and transparent manner consistent with procedures designed to ensure fairness. Any Personal Information (as defined in the ICANN Privacy Policy) collected, used, submitted or transmitted in connection with the ASP Evaluation will be processed only for lawful purposes and consistent with the purposes for which it was collected. Such Personal Information will be processed in accordance with the New gTLD Program Personal Data Privacy Statement<https://www.icann.org/privacy> and ICANN Privacy Policy<https://www.icann.org/privacy/policy>. 1. In Section 5: Applicant Support Program Application Process: Updates to steps 2 and 3 to reflect information learned as system development has progressed (link to comment<https://docs.google.com/document/d/18aQYgEs-sTNmsCpggazQWREWI12f5t_z/edit?d…>). 1. In Section 6.5 Extended Evaluation: Minor wording updates for clarity (link to comment<https://docs.google.com/document/d/18aQYgEs-sTNmsCpggazQWREWI12f5t_z/edit?d…>). Handbook text pasted below: ASP applicants that do not pass the Phase 2 evaluation may request an extended evaluation. During extended evaluation, the SARP may seek clarification or additional information from ASP applicants to determine final evaluation results. ASP applicants in extended evaluation may lose their place in the queue and will have 21 calendar days to provide the requested information respond. If those responses do not satisfy the Phase 2 eligibility requirements, the applicant will not qualify for support. 1. In Section 7.2: Additional Resources: updated to point to the New gTLD Program: Next Round website and the ASP website, as this will have information on the programs, trainings, resources, events, and more (link to comment<https://docs.google.com/document/d/18aQYgEs-sTNmsCpggazQWREWI12f5t_z/edit?d…>).

4 5

ASP Webinar Recordings
by Samantha Mancia Aug. 7, 2024

Aug. 7, 2024

Hello ASP IRT Sub-Track, Just sending a note to let you know the ASP Webinar recordings and presentations from 30 and 31 July have now been posted on the ASP website: https://newgtldprogram.icann.org/en/application-rounds/round2/asp/resources Kind Regards, Samantha Mancia Project Manager, New gTLD Program Team Internet Corporation for Assigned Names and Numbers (ICANN) Office Telephone: +1 310 301 5800 www.icann.org<http://www.icann.org>

1 0

Re: Follow-up Items | ASP Handbook
by Tijani Aug. 2, 2024

Aug. 2, 2024

Kristy and all, I went trough the clean version and found the following remarks: 4.5.3 Indigenous/Tribal Peoples’ Organizations (P 30 Clean) The instruction for question (a) is: Upload documentation demonstrating support from the Indigenous/Tribal Peoples' community represented by the applicant organization, exactly the same as the instruction for question (b). The instruction for question (a) should be: Upload documentation demonstrating proof of official recognition from a relevant authority. It should be corrected in the text (P 30) and the flow chart (P 31). 4.5.5. Micro- or Small-Sized Business from a Less-Developed Economy (P 37 Clean) The instruction for question (b) is: Upload documentation demonstrating that the applicant is an Indigenous/Tribal Peoples’-owned business, such as an Indigenous/Tribal Peoples’ Organization status, or a letter of support from the corresponding Indigenous/Tribal Peoples’ community. Indigenous/tribal people’ organization status is the requirement for 4.5.3 (P30) question (a), and letter of support from the corresponding indigenous/tribal peoples’ community is the requirement for 4.5.3 question (b) I told you on the call that it’s a duplication of 4.5.3 Indigenous/Tribal Peoples’ Organizations, especially because you don’t need to be a micro or small business to qualify for support if you are an Indigenous/Tribal Peoples' Organization or if you are located in an indigenous/tribal land that is normally an underserved territory/region. 4.5.5. Micro- or Small-Sized Business from a Less-Developed Economy (P 36 Clean) While for underserved economies, it’s required that the applicant’s principal place of business must be located in these countries/territories/regions and more than 50 percent of the company owned by residents from there, for the indigenous/tribal, no such condition applies: 80% of the company could be owned by non-resident of the indigenous/tribal land and it’s still eligible to be supported. I hope this is helpful. Tijani De : Kristy Buckley via Subpro-irt-asp <subpro-irt-asp(a)icann.org> Répondre à : Kristy Buckley <kristy.buckley(a)icann.org> Date : jeudi 1 août 2024 à 21:51 À : "SubPro-IRT-asp(a)icann.org" <SubPro-IRT-asp(a)icann.org> Objet : [Subpro-irt-asp] Follow-up Items | ASP Handbook Greetings ASP-IRT members, Many thanks for taking the time to join us again today. I know many of you were juggling other meetings simultaneously or back-to-back. Much appreciated. As promised, we are sharing additional comments on-list for your review. We kindly request any additional questions or comments on-list by 23:59 UTC Monday 5 August. This will allow us to finalize preparations for posting v3 of the Handbook on the ASP website and to ensure translation of the ASP Handbook into the ICANN languages in a timely fashion. Below please see the follow-up items from today as well as the remaining Handbook comments to review. Kind regards, Kristy, on behalf of the ASP Project Team ---- Follow up items from today's meeting: Once available, Kristy to confirm on list that we’ve consulted internally on the latest financial need indicator (link to comment). Kristy and Sam to consult internally about the possibility of offering the fee discount to ASP applicants still awaiting ASP evaluation results by the time the gTLD application submission period begins (as opposed to offering a refund if they qualify). ICANN org will update on-list and/or bring this to the full IRT in relation topical discussions about the gTLD fee, withdrawals, refunds, etc. Remaining Handbook comments to review: In Section 4.6: Restrictions: In light of Justine's question around distinguishing between Terms and Conditions (T&Cs) and Restrictions, and given that the T&Cs are currently out for public comment, what does the IRT think about keeping this language out of the ASP Handbook and instead leaving in Terms & Conditions and potentially the AGB? In the Handbook we are suggesting removal of text (4.6.4) because it is already in the ASP T&Cs (link to comment) and subject to changes following public comment on the T&Cs. 2. In Section 4.6: Restrictions: following our discussion on 1 August, we propose keeping the restriction (4.6.7) related to the future Registry Agreement which is for ROs, not ASP applicants, but it seems important to flag to prospective ASP applicants. (link to comment) 3. In Section 4.6: Restrictions: Addition of cross reference to change requests section to 4.6.1 (link to comment). Handbook text pasted below: For information on restrictions related to application change requests, please see Section 5.1: Changes to ASP Applications. 5. In Section 5: Applicant Support Program Application Process: Additional detail on privacy policies added in place of the link to the bylaws (link to comment). Handbook text pasted below: Personal data processed for the New gTLD Program will be deleted when it is no longer needed for stated purposes, subject to legal requirements, while taking into account ICANN org’s overarching mandate to operate to the maximum extent feasible in an open and transparent manner consistent with procedures designed to ensure fairness. Any Personal Information (as defined in the ICANN Privacy Policy) collected, used, submitted or transmitted in connection with the ASP Evaluation will be processed only for lawful purposes and consistent with the purposes for which it was collected. Such Personal Information will be processed in accordance with the New gTLD Program Personal Data Privacy Statement and ICANN Privacy Policy. 6. In Section 5: Applicant Support Program Application Process: Updates to steps 2 and 3 to reflect information learned as system development has progressed (link to comment). 7. In Section 6.5 Extended Evaluation: Minor wording updates for clarity (link to comment). Handbook text pasted below: ASP applicants that do not pass the Phase 2 evaluation may request an extended evaluation. During extended evaluation, the SARP may seek clarification or additional information from ASP applicants to determine final evaluation results. ASP applicants in extended evaluation may lose their place in the queue and will have 21 calendar days to provide the requested information respond. If those responses do not satisfy the Phase 2 eligibility requirements, the applicant will not qualify for support. 8. In Section 7.2: Additional Resources: updated to point to the New gTLD Program: Next Round website and the ASP website, as this will have information on the programs, trainings, resources, events, and more (link to comment). _______________________________________________ Subpro-irt-asp mailing list -- subpro-irt-asp(a)icann.org To unsubscribe send an email to subpro-irt-asp-leave(a)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.

2 1

Post-call | SubPro IRT ASP Sub-Track #24 | 1 August 2024
by Next Round Policy Implementation Aug. 2, 2024

Aug. 2, 2024

Dear All, The recordings for Meeting #24 of the SubPro IRT ASP Sub-Track held on Thursday, 1 August 2024 at 18:00-19:00 UTC are published on the meeting wiki page<https://community.icann.org/x/OAANFQ>. These include: * Attendance * Audio recording * Zoom recording (including audio, visual, rough transcript, chat) For additional information, you may consult the mailing list archive<https://mm.icann.org/pipermail/subpro-irt-asp/>. Best regards, Renate

1 0

Follow-up Items | ASP Handbook
by Kristy Buckley Aug. 1, 2024

Aug. 1, 2024

Greetings ASP-IRT members, Many thanks for taking the time to join us again today. I know many of you were juggling other meetings simultaneously or back-to-back. Much appreciated. As promised, we are sharing additional comments on-list for your review. We kindly request any additional questions or comments on-list by 23:59 UTC Monday 5 August. This will allow us to finalize preparations for posting v3 of the Handbook on the ASP website<https://newgtldprogram.icann.org/en/application-rounds/round2/asp/handbook> and to ensure translation of the ASP Handbook into the ICANN languages in a timely fashion. Below please see the follow-up items from today as well as the remaining Handbook comments to review. Kind regards, Kristy, on behalf of the ASP Project Team ---- Follow up items from today's meeting: * Once available, Kristy to confirm on list that we’ve consulted internally on the latest financial need indicator (link to comment<https://docs.google.com/document/d/18aQYgEs-sTNmsCpggazQWREWI12f5t_z/edit?d…>). * Kristy and Sam to consult internally about the possibility of offering the fee discount to ASP applicants still awaiting ASP evaluation results by the time the gTLD application submission period begins (as opposed to offering a refund if they qualify). ICANN org will update on-list and/or bring this to the full IRT in relation topical discussions about the gTLD fee, withdrawals, refunds, etc. Remaining Handbook comments to review: 1. In Section 4.6: Restrictions: In light of Justine's question around distinguishing between Terms and Conditions (T&Cs) and Restrictions, and given that the T&Cs are currently out for public comment, what does the IRT think about keeping this language out of the ASP Handbook and instead leaving in Terms & Conditions and potentially the AGB? In the Handbook we are suggesting removal of text (4.6.4) because it is already in the ASP T&Cs (link to comment<https://docs.google.com/document/d/18aQYgEs-sTNmsCpggazQWREWI12f5t_z/edit?d…>) and subject to changes following public comment on the T&Cs. 1. In Section 4.6: Restrictions: following our discussion on 1 August, we propose keeping the restriction (4.6.7) related to the future Registry Agreement which is for ROs, not ASP applicants, but it seems important to flag to prospective ASP applicants. (link to comment<https://docs.google.com/document/d/18aQYgEs-sTNmsCpggazQWREWI12f5t_z/edit?d…>) 1. In Section 4.6: Restrictions: Addition of cross reference to change requests section to 4.6.1 (link to comment<https://docs.google.com/document/d/18aQYgEs-sTNmsCpggazQWREWI12f5t_z/edit?d…>). Handbook text pasted below: For information on restrictions related to application change requests, please see Section 5.1: Changes to ASP Applications<https://docs.google.com/document/d/18aQYgEs-sTNmsCpggazQWREWI12f5t_z/edit#h…>. 1. In Section 5: Applicant Support Program Application Process: Additional detail on privacy policies added in place of the link to the bylaws (link to comment<https://docs.google.com/document/d/18aQYgEs-sTNmsCpggazQWREWI12f5t_z/edit?d…>). Handbook text pasted below: Personal data processed for the New gTLD Program will be deleted when it is no longer needed for stated purposes, subject to legal requirements, while taking into account ICANN org’s overarching mandate to operate to the maximum extent feasible in an open and transparent manner consistent with procedures designed to ensure fairness. Any Personal Information (as defined in the ICANN Privacy Policy) collected, used, submitted or transmitted in connection with the ASP Evaluation will be processed only for lawful purposes and consistent with the purposes for which it was collected. Such Personal Information will be processed in accordance with the New gTLD Program Personal Data Privacy Statement<https://www.icann.org/privacy> and ICANN Privacy Policy<https://www.icann.org/privacy/policy>. 1. In Section 5: Applicant Support Program Application Process: Updates to steps 2 and 3 to reflect information learned as system development has progressed (link to comment<https://docs.google.com/document/d/18aQYgEs-sTNmsCpggazQWREWI12f5t_z/edit?d…>). 1. In Section 6.5 Extended Evaluation: Minor wording updates for clarity (link to comment<https://docs.google.com/document/d/18aQYgEs-sTNmsCpggazQWREWI12f5t_z/edit?d…>). Handbook text pasted below: ASP applicants that do not pass the Phase 2 evaluation may request an extended evaluation. During extended evaluation, the SARP may seek clarification or additional information from ASP applicants to determine final evaluation results. ASP applicants in extended evaluation may lose their place in the queue and will have 21 calendar days to provide the requested information respond. If those responses do not satisfy the Phase 2 eligibility requirements, the applicant will not qualify for support. 1. In Section 7.2: Additional Resources: updated to point to the New gTLD Program: Next Round website and the ASP website, as this will have information on the programs, trainings, resources, events, and more (link to comment<https://docs.google.com/document/d/18aQYgEs-sTNmsCpggazQWREWI12f5t_z/edit?d…>).

1 0

REMINDER | SubPro IRT ASP Sub-Track Meeting #24 | 1 August 2024, 18:00-19:00 UTC
by Next Round Policy Implementation Aug. 1, 2024

Aug. 1, 2024

Dear All, Meeting #24 of the SubPro IRT ASP Sub-Track will be held in one hour on 1 August 2024 at 18:00-19:00 UTC [local time<https://tinyurl.com/bdp7u5cz>]. The agenda can be consulted here<https://community.icann.org/x/OAANFQ>. 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/93075290767?pwd=MHl2YzBoc1Vyd2hkbC9xOTNwdlgvUT09 Meeting ID: 930 7529 0767 Passcode: 7Dg4fef%=2 Audio only One tap mobile +19294362866,,93075290767#,,,,*4781543838# US (New York) +12532158782,,93075290767#,,,,*4781543838# US (Tacoma) Find your local number: https://icann.zoom.us/u/aDZ2vqhHu Meeting ID: 930 7529 0767 Passcode: 4781543838 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

Re: Follow-up | Financial Need indicator
by Tijani Aug. 1, 2024

Aug. 1, 2024

Hi Kristy, Don’t you feel that « may not” is very light since an applicant who is majority owned or controlled by an entity that does not meet the Financial Need criteria couldn’t be accepted for support. Can it be “must not” or “can’t” instead? Tijani De : Kristy Buckley via Subpro-irt-asp <subpro-irt-asp(a)icann.org> Répondre à : Kristy Buckley <kristy.buckley(a)icann.org> Date : jeudi 1 août 2024 à 01:53 À : "SubPro-IRT-asp(a)icann.org" <SubPro-IRT-asp(a)icann.org> Objet : [Subpro-irt-asp] Follow-up | Financial Need indicator Greetings ASP-IRT members, We look forward to continuing our review and discussion tomorrow/1 August. In the meantime, I'm sharing on-list the proposed draft edits to the Financial Need indicator that we've been discussing. If you would like to review it in the context of the ASP Handbook, here is the link to that comment, which we'll also discuss tomorrow during the meeting: https://docs.google.com/document/d/18aQYgEs-sTNmsCpggazQWREWI12f5t_z/edit?d… Also pasted below for easy reference, with suggested edits in bold and strikethrough: "The applying entity may not be majority (more than 50%) owned or controlled (defined in Section 4.2 Criterion 2 indicator) by an entity that does not meet the Financial Need above criteria." As noted in the comment linked above, we are proposing this draft language in light of recent discussions with the ASP-IRT. Though, we note that it will still need to be checked internally for consistency with other ICANN procedures. Since we already define "control" in Section 4.2 Public Responsibility it seems prudent to refer back to that same definition for Financial Need. In Public Responsibility we require that the applicant is not affiliated with or controlled by another RO, prospective gTLD applicant, or RSP that wouldn't meet the ASP criteria. In the Financial Need section, we are proposing that the applicant cannot be controlled by an entity (not just another RO/gTLD applicant) that does not meet the Financial Need criterion. We look forward to picking up where we left off. Please feel free to share your thoughts on-list or on the call, whichever is most convenient. Kind regards, Kristy, on behalf of the ASP Project Team _______________________________________________ Subpro-irt-asp mailing list -- subpro-irt-asp(a)icann.org To unsubscribe send an email to subpro-irt-asp-leave(a)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.

2 1

Follow-up | Financial Need indicator
by Kristy Buckley July 31, 2024

July 31, 2024

Greetings ASP-IRT members, We look forward to continuing our review and discussion tomorrow/1 August. In the meantime, I'm sharing on-list the proposed draft edits to the Financial Need indicator that we've been discussing. If you would like to review it in the context of the ASP Handbook, here is the link to that comment, which we'll also discuss tomorrow during the meeting: https://docs.google.com/document/d/18aQYgEs-sTNmsCpggazQWREWI12f5t_z/edit?d… Also pasted below for easy reference, with suggested edits in bold and strikethrough: "The applying entity may not be majority (more than 50%) owned or controlled (defined in Section 4.2 Criterion 2 indicator) by an entity that does not meet the Financial Need above criteria." As noted in the comment linked above, we are proposing this draft language in light of recent discussions with the ASP-IRT. Though, we note that it will still need to be checked internally for consistency with other ICANN procedures. Since we already define "control" in Section 4.2 Public Responsibility it seems prudent to refer back to that same definition for Financial Need. In Public Responsibility we require that the applicant is not affiliated with or controlled by another RO, prospective gTLD applicant, or RSP that wouldn't meet the ASP criteria. In the Financial Need section, we are proposing that the applicant cannot be controlled by an entity (not just another RO/gTLD applicant) that does not meet the Financial Need criterion. We look forward to picking up where we left off. Please feel free to share your thoughts on-list or on the call, whichever is most convenient. Kind regards, Kristy, on behalf of the ASP Project Team

1 0