May 2024 - Subpro-irt-asp - lists.icann.org

v2 Draft ASP Handbook
by Kristy Buckley June 6, 2024

June 6, 2024

Greetings ASP-IRT colleagues, Thanks to all of you for taking the time to join our three ASP-IRT sessions this week, Meetings #17-19<https://community.icann.org/pages/viewpage.action?pageId=322994328> to review the public comments received on the draft ASP Handbook<https://www.icann.org/en/public-comment/proceeding/review-of-the-draft-appl…> and proposed changes to the draft Handbook. You may recall that the draft ASP Handbook that went out for public comment included a number of areas with bracketed text, including placeholders for additional details previously requested by the ASP-IRT. Wherever possible, ICANN org has added additional information suggested by the IRT and updated/removed bracketed text. Per the public comments received, staff moved important text to colored text boxes. As indicated in our sessions this week, we are sharing: 1) an updated "clean" version 2 of the draft ASP Handbook<https://docs.google.com/document/d/1_ReePYbw2WJEEwvoAnGqsrASfkzWc_Ui/edit?u…>; 2) an attached redline version 2 of the draft ASP Handbook (it looks scary because of all the structural changes; substantive changes were discussed this week and any further ones are noted with comments to the IRT; the redline version is attached because it would not load properly on Drive); and 3) the version of the draft ASP Handbook<https://docs.google.com/document/d/1w3_kYNYcEjXin5D1O9x4hxcpYJr7JqlY/edit?u…> that went out for public comment. *Due to timing constraints, we have provided the Handbook as view-only and we're asking that any further feedback be provided on-list. As discussed, the redline will show a number of editorial and structural changes to the draft Handbook, per the comments and letters received. As we noted during our meetings this week--improving the readability of the ASP Handbook is still a work in progress. For example, the current criteria and indicator tables in the Handbook were updated to reflect how information is organized in the ASP Application System. Though there are few substantive changes to the criteria and indicators other than those relating to public comments or those discussed with the ASP-IRT (e.g., updating Financial Need to align with other criteria). However, in considering how to improve readability, we realize that tables are not easy to follow. So, in the next iteration we will remove the tables and just list the ASP criteria and indicators in an outline format. We will also include an appendix of the criteria, application questions, and required documentation. As you review the clean version 2 of the draft ASP Handbook, please keep an eye out for "Comments to the IRT" -- these are explanatory notations of substantive changes made and in some cases, rationale as to why those changes were proposed. In terms of next steps, we kindly ask the ASP-IRT to review the clean version 2 of the draft ASP Handbook and to share any additional questions or comments on-list by 17:00 UTC on Friday, 31 May. Following this, ICANN org will finalize version 2 of the draft ASP Handbook then post to the wiki and website once ready. As always, please let us know if you have any questions. Many thanks to this group for its continued dedication and thoughtful contributions. We are getting there and we appreciate your involvement. Kind regards, Kristy, on behalf of the ASP Project Team

5 8

GAC comments on ASP Handbook revision
by Kennybirch, Rosalind (DSIT) May 31, 2024

May 31, 2024

Hi Kristy, Sam, Thanks so much for giving us until today to consult on the ASP Handbook with our constituencies. All - it has been a pleasure to work with you throughout this process - we are almost there! I have attached a few comments based on consulting with GAC members. These include small changes for clarity and high-level points (eg that ICANN should look to make more funding available if there are many successful applicants). However, there are also a few suggestions for direct changes to the handbook. I wanted to highlight the key recommended changes from the GAC below: * A need to identify which groups the program is aimed at up top, in the objectives (section 1.3) and the overview (section 2, first two paragraphs) sections respectively, including that the program has a global focus. * This theme, of clearly highlighting who this program is aimed at, also resonates in some of the comments the GAC has suggested later down in the document. GAC members who are looking to encourage groups in their countries to apply fed back that it would make much more sense to see information on eligible entities first, before reading through public responsibility, etc. sections - to be able to check whether they are eligible in the first place. This would also be a more efficient use of their time (eg saving themselves time reading through all of that detail in the first instance, only to find they aren't an eligible entity of the program). * On the current section 2.3, GAC members wondered if it could be clarified, and emphasized, that the expectation is that much of the work through both processes (the ASP application process and the new gTLD application process) will be transferable/replicable? It may deter an entity from applying if they get the impression that they will need to do double the work. * Finally, and this is a query from me - I thought we had agreed to remove the laundry list of example localized data, such as under five mortality (health), etc.? My understanding was that we had agreed to take out the list for the 'micro or small sized business from a less developed economy' section as the examples of localized data were causing confusion and made almost any group eligible to apply, when the focus of this category is supposed to be on lesser developed economies, from a global perspective? I recall that we also said that if an example of localized data was to be left in, it should focus on Internet connectivity itself (eg the Internet penetration example). I also really appreciated ICANN's publication of the primer document on the ASP, which I read with interest this week. There could be great merit in adding that primer (attached) as an annex, or at least an accompanying document to go with the handbook. Best wishes, Roz

5 6

Post-call | SubPro IRT ASP Sub-Track #19 | 23 May 2024
by Next Round Policy Implementation May 24, 2024

May 24, 2024

Dear All, The recordings for Meeting #19 of the SubPro IRT ASP Sub-Track held on Thursday, 23 May 2024 at 15:00-16:30 UTC are published on the meeting wiki page<https://community.icann.org/x/r4BAEw>. 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

Link to Deck - SubPro IRT ASP Sub-Track Meetings #17, 18 and 19
by Samantha Mancia May 23, 2024

May 23, 2024

Dear ASP IRT Sub-Track, Thanks again for your participation over the last few days. Please find as promised the deck<https://community.icann.org/pages/viewpage.action?pageId=322994328&preview=…> we reviewed, which has now been added to the wiki. 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

REMINDER | SubPro IRT ASP Sub-Track Meeting #19 | 23 May 2024, 15:00-16:30 UTC
by Next Round Policy Implementation May 23, 2024

May 23, 2024

Dear All, Meeting #19 of the SubPro IRT ASP Sub-Track will be held in one hour on 23 May 2024 at 15:00-16:30 UTC [local time<https://tinyurl.com/5fey8efh>] – it will be a 90-minute call The agenda can be consulted here<https://community.icann.org/x/r4BAEw>. 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

Post-call | SubPro IRT ASP Sub-Track #18 | 22 May 2024
by Next Round Policy Implementation May 23, 2024

May 23, 2024

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

REMINDER | SubPro IRT ASP Sub-Track Meeting #19 | 23 May 2024, 15:00-16:30 UTC
by Next Round Policy Implementation May 22, 2024

May 22, 2024

Dear All, Meeting #19 of the SubPro IRT ASP Sub-Track will be held on 23 May 2024 at 15:00-16:30 UTC [local time<https://tinyurl.com/5fey8efh>] – it will be a 90-minute call The agenda can be consulted here<https://community.icann.org/x/r4BAEw>. 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

ASP IRT Sub-Track - Correct Link for Today's Call
by Samantha Mancia May 22, 2024

May 22, 2024

Hello ASP IRT Sub-Track, It seems there may have been different links in the invites. Please use this link for todays IRT call: Join Zoom Meeting 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) Meeting ID: 930 7529 0767 Passcode: 4781543838 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

REMINDER | SubPro IRT ASP Sub-Track Meeting #18 | 22 May 2024, 14:00-15:30 UTC
by Next Round Policy Implementation May 22, 2024

May 22, 2024

Dear All, Meeting #18 of the SubPro IRT ASP Sub-Track will be held in one hour on 22 May 2024 at 14:00-15:30 UTC [local time<https://tinyurl.com/ycyrpest>] – it will be a 90-minute call. The agenda can be consulted here<https://community.icann.org/x/pIBAEw>. 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

Post-call | SubPro IRT ASP Sub-Track #17 | 21 May 2024
by Next Round Policy Implementation May 22, 2024

May 22, 2024

Dear All, The recordings for Meeting #17 of the SubPro IRT ASP Sub-Track held on Tuesday, 21 May 2024 at 18:30-20:00 UTC are published on the meeting wiki page<https://community.icann.org/x/mIBAEw>. 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