February 2024 - Subpro-irt-asp

ASP Handbook: remaining sections & today's changes
by Kristy Buckley Feb. 6, 2024

Feb. 6, 2024

Dear ASP-IRT members, We appreciate you all taking the time to join today's session and for your thoughtful comments. We have worked to clean up the ASP Handbook<https://docs.google.com/document/d/1w3_kYNYcEjXin5D1O9x4hxcpYJr7JqlY/edit?u…> as much as possible and have color-coded the bracketed sections that are still in development. As promised, this note is intended to summarize remaining sections we did not have time to cover today and proposed changes based upon today's ASP IRT feedback. See below outline of those sections and changes. 1. Remaining ASP Handbook sections we did not have time to cover-- please let us know if there are any concerns or objections to those by 1800 UTC Thursday, 1 February. * Section 6: ASP Application Process: * Updated Figure 3 to show numbered steps * Updated narrative steps to correspond to Figure 3. * Org is working on language re: ASP Application System confidentiality and will share on-list via the Handbook once available. * 6.1 Changes to ASP Applications: updated the text to address comment<https://docs.google.com/document/d/1w3_kYNYcEjXin5D1O9x4hxcpYJr7JqlY/edit?d…>; still working to confirm bracketed text re: application change requests]; added text on no resubmission. Added placeholder for withdrawals language once available. Note that withdrawal and fresh application would constitute a resubmission and we are working on this language to update the bracketed placeholder. Added in bracketed text that "timely manner" needs to be defined; resolved related comment. * Added bracketed text that "material changes" needs to be defined and to articulate what changes can/cannot be made once an application is submitted; resolved related comment. * Accepted formatting edits and resolved addressed comments where placeholder text has been added to the Handbook. * Added text to 3. Submit Application on p. 29 that ASP applicants are advised not to submit information about their intended string. This language is repeated elsewhere in the Handbook and is added to the Process Steps as a reminder to the applicants. * Accepted suggested edits ASP IRT participants proposed on 22 January ASP IRT meeting. * Section 7: org is working on updated language re: ASP system security, vendor COIs, and confidentiality, and will share once available, hopefully before end of this week. * Section 7.2: accepted suggested subheader name change to "Assessment" * Section 7.3: added bracketed language re: application change requests here to match section 6.1. Org will provide updated proposed language as soon as possible. * Section 7.5: updated subheader to "Support Allocation" per IRT feedback; the full portfolio of support has been re-ordered chronologically per IRT feedback. * Please see remaining comment from Tijani <https://docs.google.com/document/d/1w3_kYNYcEjXin5D1O9x4hxcpYJr7JqlY/edit?d…> * Retained remaining suggested edits to this section from 22 Jan meeting. * Minimum and maximum fee reductions still has bracketed text re: how ICANN Org would handle ASP applications in the "pipeline" and how support will be allocated. Org working on language for this and will share once available. * Section 9: Added 2012 AGB Eligibility Criteria (Section 1.2.1) as an additional resource, per the IRT's guidance. This language will be updated to reflect the Next Round AGB once available. * Noted that the ASP Funding Plan will be appended to the Handbook once available. 2. Proposed changes based on today’s ASP IRT feedback-- please let us know if there are any concerns or objections to those by 1800 UTC Thursday, 1 February. * org has added color coding to the ASP Handbook on the top of p.2 to help readers understand the remaining bracketed text. * Added bracketed text to p.9 to indicate every effort will be made to complete ASP application evaluations prior to the gTLD application submission period and that ASP applicants that qualify for support post-gTLD application submission may qualify for a refund. This language was based upon the ASP-IRT's suggestion and ICANN org is working to confirm final proposed language here based upon IRT input. * Section 5.5.5: * Added brackets and highlights for micro or small sized business from a less-developed economy to reflect ASP IRT meeting #13 discussion and noted that ICANN org will propose indicator language for ASP IRT consideration. * Per ASP IRT discussion and agreement, updated principal place of business definition to where a "supermajority (80%+) of the corporations top executives" and noted org will propose a definition for "top executives" * Responded to a previous comment from Rubens re: executives place of birth. Org's response: "Note that the indicator does not require executives to be born in the country, just that the executives are also located in the principal place of business." Resolved this comment. * Cleaned up comments on Section 5.5.5 and translated into bracketed text to be developed by ICANN org and proposed to the ASP IRT once available. * Section 5.6: added bracketed text that ICANN org will develop language to clarify whether it would allow supported applicants to apply for more than one gTLD string in the gTLD Program. Resolved related comment. * Accepted previously proposed suggested edits from the 22 Jan 2024 ASP IRT meeting (e.g., "allocatable TLD variants" ; "using the RZ-LGR tool (added link)"; and adding an example for traditional vs. simplified Chinese; and the added footnote placeholder) As noted during the meeting, we’ll try to get you additional proposed updates by the end of this week. For tomorrow's full IRT session, ICANN org will present a slide deck overview of the ASP Handbook, rather than go into the Handbook itself. We kindly invite ASP IRT members to join in as you see fit to help brief the full IRT on this collective effort. Many thanks for the hours you have all spent with us on this Handbook. It's been a pleasure to work with you all. And, we still have more work ahead of us (!) so we will be in touch about future ASP IRT meetings as well. Kind regards, Kristy, on behalf of the ASP Project Team

4 8

Follow-up Q for Anne
by Kristy Buckley Feb. 1, 2024

Feb. 1, 2024

Dear Anne, There was a section in the Handbook where you had suggested we add some examples of eligible entities that might wear multiple hats and that the Handbook should be clear that the applicant could submit documentation pertaining to multiple entity types. The updated language is below along with the proposed examples. As this was your suggestion, the IRT advised that we reach out to confirm this updated text adequately addresses your comment. The text is pasted below or you can go directly to Section 5.5 via this link: https://docs.google.com/document/d/1w3_kYNYcEjXin5D1O9x4hxcpYJr7JqlY/edit#h… 5.5 Eligible Entities Note that the categories for eligible entities identified below are not mutually exclusive. Should the ASP applicant fit into multiple eligible categories, the applicant is encouraged to submit required documentation for all applicable eligibility categories, so they may be evaluated accordingly. Note however, ASP applicants are only required to meet the eligibility criteria and indicators for one of the eligible entity categories listed to qualify under this criteria category (Eligible Entities). Submitting documentation for multiple entity types does not negatively impact the applicant’s eligibility (i.e., if an applicant submits documentation for two entity categories and qualifies for one but does not qualify for another, the applicant still passes the “Eligible Entity” evaluation category). See additional examples below. Applicant Example 1: if the applicant is a nonprofit/charitable organization and an Indigenous/Tribal Peoples organization, it may submit documentation to demonstrate eligibility for either entity or for both entities. The applicant only needs to meet the criteria and indicators for one entity type to pass the “Eligible Entity” evaluation category. Applicant Example 2: if the applicant is a small business social enterprise and is principally located in a developing economy, it may submit documentation to demonstrate eligibility for either entity or for both entities. The applicant only needs to meet the criteria and indicators for one entity type to pass the “Eligible Entity” evaluation category. Kind regards, Kristy

2 1

Post-call | SubPro IRT ASP Sub-Track #13 | 31 January 2024
by Next Round Policy Implementation Feb. 1, 2024

Feb. 1, 2024

Dear All, The recordings for Meeting #13 of the SubPro IRT ASP Sub-Track held on Wednesday, 31 January 2024 at 21:00-22:30 UTC are published on the meeting wiki page<https://community.icann.org/x/BIDCEQ>. 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, Leon

1 0

Apologies for the ASP Meeting on Wednesday
by Anne ICANN Feb. 1, 2024

Feb. 1, 2024

Kristy et al, Please accept my apologies for the ASP meeting on Wednesday. Unfortunately I have a late-breaking unavoidable conflict only 30 minutes into the Wednesday meeting. Will try to chime in for the first 30 minutes. Should be in the clear for Thursday's IRT meeting however. Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso(a)gmail.com

2 1