Dear Tijani, Many thanks for your careful review and thoughtful comments, much appreciated. Please see our responses in-line below. Kind regards, Kristy, on behalf of the ASP Project Team ==== 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). Thank you for this comment. We looked at the public comment version of the Handbook and saw that it seemed to be a copy/paste error on this indicator. We’ve updated the indicator to reflect what we had in the public comment version<https://community.icann.org/display/SPIR/ASP+%7C+Applicant+Support+Program?p...>. We’ve also updated the flow chart to reflect this. Link to comment and suggested edits. <https://docs.google.com/document/d/18aQYgEs-sTNmsCpggazQWREWI12f5t_z/edit?di...> 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. For indigenous / tribal peoples, we have two pathways to qualify as an eligible entity: 1) as an indigenous organization; and 2) as an indigenous micro or small business from a less-developed economy. The instructions and indicators for each of these are different. If an indigenous organization applies as an indigenous/tribal peoples’ organization, they do not need to submit documentation related to the small business entity. The ASP-IRT suggested adding indigenous or tribal as a less-developed economy under the micro or small business category. Here are a few examples of potential applicant scenarios related to these pathways: 1) An indigenous organization working on food security issues in the Canadian Arctic could apply under the indigenous organization category. 2) A small business ice cream shop that is indigenous owned could apply under micro or small business from a less-developed economy category. 3) A small business general store, not owned by an indigenous person but that is operating on indigenous lands could apply as a micro or small business from a less-developed economy category. 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. After consulting with indigenous community experts, the guidance was to avoid being overly prescriptive about what defines indigenous-owned because it can vary by region, country, and territory. Here is an example of how it is defined in Canada: https://nacca.ca/wp-content/uploads/2024/04/IBD-Placemat_EN-March-12-2024.pd... but I think we want to be careful about creating a one-size-fits-all approach to the indicator since it may be defined differently in other places. My understanding is that in Brazil, for instance, there is not a single national standard definition of indigenous owned business. This is where the expertise of the SARP evaluators will be important. ________________________________ From: Tijani <tijani.benjemaa@topnet.tn> Sent: Friday, August 2, 2024 1:10 To: Kristy Buckley; SubPro-IRT-asp@icann.org Cc: Tijani Subject: [Ext] Re: [Subpro-irt-asp] Follow-up Items | ASP Handbook 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@icann.org> Répondre à : Kristy Buckley <kristy.buckley@icann.org> Date : jeudi 1 août 2024 à 21:51 À : "SubPro-IRT-asp@icann.org" <SubPro-IRT-asp@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 [newgtldprogram.icann.org]<https://urldefense.com/v3/__https://newgtldprogram.icann.org/en/application-...> 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 [docs.google.com]<https://urldefense.com/v3/__https://docs.google.com/document/d/18aQYgEs-sTNm...>). * 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 [docs.google.com]<https://urldefense.com/v3/__https://docs.google.com/document/d/18aQYgEs-sTNm...>) 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 [docs.google.com]<https://urldefense.com/v3/__https://docs.google.com/document/d/18aQYgEs-sTNm...>) 3. In Section 4.6: Restrictions: Addition of cross reference to change requests section to 4.6.1 (link to comment [docs.google.com]<https://urldefense.com/v3/__https://docs.google.com/document/d/18aQYgEs-sTNm...>). Handbook text pasted below: For information on restrictions related to application change requests, please see Section 5.1: Changes to ASP Applications [docs.google.com]<https://urldefense.com/v3/__https://docs.google.com/document/d/18aQYgEs-sTNm...>. 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 [docs.google.com]<https://urldefense.com/v3/__https://docs.google.com/document/d/18aQYgEs-sTNm...>). 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>. 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 [docs.google.com]<https://urldefense.com/v3/__https://docs.google.com/document/d/18aQYgEs-sTNm...>). 7. In Section 6.5 Extended Evaluation: Minor wording updates for clarity (link to comment [docs.google.com]<https://urldefense.com/v3/__https://docs.google.com/document/d/18aQYgEs-sTNm...>). 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 [docs.google.com]<https://urldefense.com/v3/__https://docs.google.com/document/d/18aQYgEs-sTNm...>). _______________________________________________ Subpro-irt-asp mailing list -- subpro-irt-asp@icann.org To unsubscribe send an email to subpro-irt-asp-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.