- Gnso-scci - lists.icann.org

Is it time for a bit of text cleanup yet? Here's hoping!
by John McCabe Aug. 5, 2026

Aug. 5, 2026

> > Hi Manju, Ajith & SCCI Team, > > Not long ago I put in a good deal of time to go through the discussion document and suggest spelling, word usage and other tweaks that I believe enhanced/clarified, rather than changed the intended meanings in the rough drafts. > > I was advised at the time that I was ahead of the curve, and that the task-at-hand took precedence. Now that this seems to have come to completion, I would like to check the team's interest in revisiting my suggestions. > > Or perhaps staff has reviewed my recommendations and taken actioned on them already (one way or another). > > Thank you all for your consideration! > > John > P.S. My interest has its roots in high school, where I was the News Editor of our school newspaper back in the 20th century. I see a document such as that, and I’m afraid, it’s simply hard-wired into me ;) > > P.P.S. Here’s the link to the hopefully-soon-to-be-streamlined document: https://lists.icann.org/hyperkitty/list/gnso-scci@icann.org/message/NISE47C… Cheers! > >> Jul 31, 2026, at 6:18 AM, Ajith Francis via Gnso-scci <gnso-scci(a)icann.org <mailto:gnso-scci@icann.org>> wrote: >> >> Dear SCCI Members, >> >> With the deadline for feedback on the Assessment Plan having passed, I’d like to thank the SCCI for its review and feedback provided. >> >> We appreciate the feedback from Gaurav in particular, which we believe to be fair input, but maybe more appropriate for when the data gathering is taking place and not necessarily for the Assessment Plan. What we mean by that is, as data is gathered, that is the stage at which we will better understand whether there are limitations or impediments to getting the requirement information (Gaurav’s first point). And as data is gathered, the data sources will be included (Gaurav’s third point). For point two, consistent with how this group has operated to date, it’s envisioned that SCCI Support Staff will make the initial attempt and then collaborate with the SCCI to refine. With that in mind, it is probably fair to update the text to the SCCI more generally rather than just staff. >> >> Unless there are objections to leadership’s interpretation, we believe we can cancel the call on 5 August and SCCI Support Staff has what it needs to begin the Initial data gathering exercise. >> >> Best regards, >> Ajith >> SCCI Vice Chair >> _______________________________________________ >> Gnso-scci mailing list -- gnso-scci(a)icann.org <mailto:gnso-scci@icann.org> >> To unsubscribe send an email to gnso-scci-leave(a)icann.org <mailto:gnso-scci-leave@icann.org>

2 2

CANCELLED - Meeting Invitation | GNSO SCCI Call | Wednesday, 05 August 2026
by Julie Bisland July 31, 2026

July 31, 2026

THIS CALL HAS BEEN CANCELLED. PLEASE REMOVE IT FROM YOUR CALENDAR. ************** Dear all, The next meeting of the GNSO Standing Committee on Continuous Improvement (SCCI) will take place on Wednesday, 05 August 2026 at 12:00 UTC for 1 hour. Zoom Webinar link: : https://icann.zoom.us/j/96269931065?pwd=c0VKWkpMZHdNSlNSQkYrSG5MZmxQUT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/96269931065?pwd=c0VKWkpM…> Meeting ID: 962 6993 1065 Passcode: .&@z^zfSL1 Audio: Webinar ID: 962 6993 1065 Passcode: 0702315261 International numbers available: https://icann.zoom.us/u/ad6GAsKCUM [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/ad6GAsKCUM__;!!PtGJab4!6…> ALL: Before joining the call: * Please send apologies to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…>, the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…>, and the ICANN Community Participant Code of Conduct<https://www.icann.org/en/system/files/files/adopted-icann-community-partici…>. * Visit the 2026 Wiki Agenda pages: https://icann-community.atlassian.net/wiki/x/AQCPKQ [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/AQC…> Thank you, Kind regards, Terri Policy Team Supporting the GNSO

1 0

SCCI Assessment Plan Feedback Update and Next Steps
by Ajith Francis July 31, 2026

July 31, 2026

Dear SCCI Members, With the deadline for feedback on the Assessment Plan having passed, I’d like to thank the SCCI for its review and feedback provided. We appreciate the feedback from Gaurav in particular, which we believe to be fair input, but maybe more appropriate for when the data gathering is taking place and not necessarily for the Assessment Plan. What we mean by that is, as data is gathered, that is the stage at which we will better understand whether there are limitations or impediments to getting the requirement information (Gaurav’s first point). And as data is gathered, the data sources will be included (Gaurav’s third point). For point two, consistent with how this group has operated to date, it’s envisioned that SCCI Support Staff will make the initial attempt and then collaborate with the SCCI to refine. With that in mind, it is probably fair to update the text to the SCCI more generally rather than just staff. Unless there are objections to leadership’s interpretation, we believe we can cancel the call on 5 August and SCCI Support Staff has what it needs to begin the Initial data gathering exercise. Best regards, Ajith SCCI Vice Chair

2 1

Reminder: Request for Review and Feedback on CIP Assessment Plan by 29 July 2026
by Saewon Lee July 17, 2026

July 17, 2026

***REMINDER: Please provide your feedback by Wednesday, 29 July 2026 at 23:59 UTC*** Dear SCCI, As a follow-up to the request below to review the Assessment Plan<https://docs.google.com/spreadsheets/d/1xJGebCzGi5WJhnG8Dhg4s5smj4HZp9pE/ed…>, please share any substantive feedback or comments by Wednesday, 29 July 2026, at 23:59 UTC so that they can be incorporated into the next step. A tentative meeting will be scheduled on Wednesday, 5 August 2026, at our usual time (12:00 UTC) to discuss the feedback. If no substantive input is received by the deadline, the meeting will be canceled. Should you have any questions or concerns, please don’t hesitate to reach out. Much appreciated, Saewon From: Manju via Gnso-scci <gnso-scci(a)icann.org> Reply-To: Manju <manju4icann(a)gmail.com> Date: Tuesday, June 30, 2026 at 9:27 PM To: John McCabe <rysg.whoswho(a)gmail.com> Cc: "gnso-scci(a)icann.org" <gnso-scci(a)icann.org> Subject: [Gnso-scci] Re: ! Hi John, Thank you for the feedback. That said, I'd like to flag that we'd previously agreed to hold off on further wordsmithing of the criteria or indicators aside from the action items from ICANN86. I'd like to use this as another opportunity to remind the team that, absent any further feedback or comments on these specific 2 indicators: Criteria 4: The GNSO actively combats domain name security threats. * Indicator 1: The GNSO has demonstrated meaningful activity towards mitigating DNS Abuse and security threats relating to domain names that are in scope for the GNSO domain name security threats. * Indicator 2: 66% of surveyed respondents agree that the GNSO has demonstrated meaningful activityely towards mitigating DNS Abuse and security threats relating to domain names that are in scope for the GNSOcombats domain name security threats. We will take it as a consensus on the new wording and proceed to cancel the call tomorrow. In the meantime, please review the Assessment Plan: https://docs.google.com/spreadsheets/d/1xJGebCzGi5WJhnG8Dhg4s5smj4HZp9pE/ed… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1xJGebCzG…> Thank you and have an awesome July! Best, Manju On Sun, Jun 28, 2026 at 1:49 AM John McCabe via Gnso-scci <gnso-scci(a)icann.org<mailto:gnso-scci@icann.org>> wrote: Hi all, I jumped on this early this morning, and here’s what I’ve come up with in terms of my comments below. Some of what I’ve got repeats in different iterations, and others took some thinking, and maybe others will concur or have better ideas. Other than that, I’ve reviewed Steve's email and have nothing to add. If having this as a “crib sheet” will save you some time, I’m happy to be of service with what I hope is a solid contribution.. Enjoy your weekend! Cheers, John McCabe .whoswho ======================= I'm neither an English major nor a lawyer, but I checked with the best lawyer I know who confirms that "one or more" takes the singular (with exceptions, see At 9A/etc. below): At 4 A / P1. C1. Indic. 1: @ "one or more existing bodies" >>> "body" (singular) At 5 A / P1. C1. Indic. 2: @ "one or more mechanisms" >>> mechanism (singular) At 8 A / P1. C2. Indic. 1: @ "one or more existing bodies" >>> "body" (singular) At 9 A / P1. C2. Indic. 2: @ "one or more sections that demonstrate" >>> "section that demonstrates" (singular + agreement with verb) At 11 A / P1. Criterion 3: suggest replace "relevant" with "pertinent" as it speaks to Strategic Plan objectives (See AI guidance below) AI: While both words mean related to the topic, relevant describes a broad, logical connection, whereas pertinentmeans the information is on-point, decisive, and directly touches the core of the issue. [1 [ontariotraining.net]<https://urldefense.com/v3/__https:/ontariotraining.net/word-choice-pertinen…>, 2 [english.stackexchange.com]<https://urldefense.com/v3/__https:/english.stackexchange.com/questions/2117…>, 3 [dictionary.com]<https://urldefense.com/v3/__https:/www.dictionary.com/browse/pertinent__;!!…>] At 15 A / P1. C3. Indic. 4: Criterion 3: In the case of survey opinions, "relevant" seem like correct usage [No change proposed.] At 19 A/P1. Criterion 5: "The GNSO actively works to build and expand a multilingual Internet." [Propose a change of word order.] At 20 A/P1 C5 Indic. 1: @ "expanding and building" >>> "building and expanding" At 21 A/P1. C5 Indic. 2: @ "expanding and building" >>> "building and expanding" At 23 A/P2. Criterion 1: The GNSO’s working group(s) and/or process(es) address their goals and priorities and are in line with their purpose(s). [Delete "to", add "and".] At 24 A / P1. C1. Indic. 1: @ "one or more mechanisms" >>> "mechanism" (singular) AND should cell A24 start with P2. ? [It currently starts with P1.] At 25 A / P2. C1. Indic. 2: @ "one or more mechanisms" >>> "mechanism" (singular) At 26 A / P1. C1. Indic. 2: @ "in place that governs" >>> "in place to govern" (improper usage) At 27 A / P2. Criterion 2: Structure(s) in place is/(are) accessible and clearly communicated. (awkward, we may assume that there will be more than one ...) "Structures in place are accessible at locations clearly communicated." At 29 A / P3. C.2. Indic . 2: @ "media, on at least" >>> "media, at least on an annual basis..." (word order) At 30 A / P2. C.2. Indic . 3: @ "in place that govern the GNSO's processes" >>> "in place to govern..." (usage) At 31 A / P2. Criterion 3: "Output(s) produced have the desired outcome, are implementable, and implementation of such outputs is monitored." >>> "Outputs realized have the desired outcomes, are implementable, and implementation of such outputs is monitored." (clarity) At 32 A / P2. C.3 Indic 1: "The GNSO Council has one or more mechanisms to evaluate its implemented policy recommendations and determine whether >>> "to" > "and" they are achieving their desired/expected outcomes." >>> <"they" takes plural> At 35 A / P2. C.3 Indic 4: "At least 66% of the surveyed respondents agree that the output(s) that the GNSO produces have the desired outcome and are implementable, and the implementation of such outputs is monitored. (run-on sentence, insert comma after "implementable," as indicated) At 37 A / P3. Criterion 1: @ "... issues to focus upon within established timeframes." >>> "issues upon which to focuswithin established timeframes." (phrasing) At 38 A / P3. C1. Indic. 1: @ "one or more mechanisms" >>> mechanism (singular) At 39 A / P3. C1. Indic. 2: @ "one or more mechanisms" >>> mechanism (singular) At 40 A / P3. C1. Indic. 3: @ "priorities, and identifying and scoping relevant emerging issues to focus upon within established timeframes." "... priorities, **as well as to identify and scope** relevant emerging issues upon which to focus within established timeframes." At 42 A / P.3. C2 Indic. 1: "including a way to ensure" >>> "including procedures"/ "including processes" At 44 A / P3. C2. Indic. 3: "inputs related" >>> "inputs relating" At 45 A / P3. Criterion 3: "outputs relevant to its purpose" >>> "outputs pertinent to its purpose" See also: At 11 A / P1. Criterion 3: suggest replace "relevant" with "pertinent" At 60 A / P.3 C6. Indicator 3: "in respect of agreed-upon work plans." >>> "of" > "to" At 62 A / P3. C7. Indicator 1: "adequate staff support to support its activities" >>> "to fulfill its commitments" "At least 66% of the GNSO Council agrees " >>> agree At 63 A / P3. C7. Indicator 1: "adequate staff support to support its activities" >>> "to fulfill its commitments" "At least 66% of the GNSO SG/Cs agrees" >>> agree At 74 A / P4. C2. Indic. 4: @ "one or more mechanisms" >>> "mechanism" (singular) At 77 A / P4. C3. Indic. 1: @ "one or more mechanisms" >>> "mechanism" (singular) At 78 A / P4. C3. Indic. 2: @ "one or more mechanisms" >>> "mechanism" (singular) At 82 A / P4. C4. Indic. 2: @ "one or more mechanisms" >>> "mechanism" (singular) At 88 A / P4. C6. Indic. 1: @ "one or more mechanisms" >>> "mechanism" (singular) At 92 A / P5. C1. Indic. 2: @ "one or more mechanisms" >>> "mechanism" (singular) ======================= On Jun 26, 2026, at 5:08 PM, Steve Chan via Gnso-scci <gnso-scci(a)icann.org<mailto:gnso-scci@icann.org>> wrote: Dear SCCI Members, I would like to follow up on a couple of action items from ICANN86. You will have seen the text updated at ICANN86, circulated by Saewon, which is reproduced below. We have not seen any input to date. If no substantive feedback is received ahead of our next meeting on Wednesday, 1 July 2026, we will cancel the call. Criteria 4: The GNSO actively combats domain name security threats. * Indicator 1: The GNSO has demonstrated meaningful activity towards mitigating DNS Abuse and security threats relating to domain names that are in scope for the GNSO domain name security threats. * Indicator 2: 66% of surveyed respondents agree that the GNSO has demonstrated meaningful activityely towards mitigating DNS Abuse and security threats relating to domain names that are in scope for the GNSOcombats domain name security threats. Second, leadership and staff have completed another action item from ICANN86, which was to prepare a draft Assessment Plan. If you will recall at ICANN86, we reviewed a couple of examples that were captured on slides. What we have since done is to complete the Assessment Plan for all of the Indicators. From our perspective, we believe the Assessment Plan is quite straight forward, but we want to ensure you all have adequate time to review. In the event we cancel the 1 July meeting, you can instead take the time to review the Assessment Plan! Please find the Assessment Plan on the third tab in this document: https://docs.google.com/spreadsheets/d/1xJGebCzGi5WJhnG8Dhg4s5smj4HZp9pE/ed… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1xJGebCzG…> If you have any questions or concerns, please let us know. Best, Steve Steven Chan  VP, Policy Development Support & GNSO Relations Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org<mailto:steve.chan@icann.org> Mobile: +1.310.339.4410 _______________________________________________ Gnso-scci mailing list -- gnso-scci(a)icann.org<mailto:gnso-scci@icann.org> To unsubscribe send an email to gnso-scci-leave(a)icann.org<mailto:gnso-scci-leave@icann.org> _______________________________________________ Gnso-scci mailing list -- gnso-scci(a)icann.org<mailto:gnso-scci@icann.org> To unsubscribe send an email to gnso-scci-leave(a)icann.org<mailto:gnso-scci-leave@icann.org>

4 3

Meeting Invitation | GNSO SCCI Call | Wednesday, 05 August 2026
by Terri Agnew July 16, 2026

July 16, 2026

Dear all, The next meeting of the GNSO Standing Committee on Continuous Improvement (SCCI) will take place on Wednesday, 05 August 2026 at 12:00 UTC for 1 hour. Zoom Webinar link: : https://icann.zoom.us/j/96269931065?pwd=c0VKWkpMZHdNSlNSQkYrSG5MZmxQUT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/96269931065?pwd=c0VKWkpM…> Meeting ID: 962 6993 1065 Passcode: .&@z^zfSL1 Audio: Webinar ID: 962 6993 1065 Passcode: 0702315261 International numbers available: https://icann.zoom.us/u/ad6GAsKCUM ALL: Before joining the call: * Please send apologies to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…>, the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…>, and the ICANN Community Participant Code of Conduct<https://www.icann.org/en/system/files/files/adopted-icann-community-partici…>. * Visit the 2026 Wiki Agenda pages: https://icann-community.atlassian.net/wiki/x/AQCPKQ Thank you, Kind regards, Terri Policy Team Supporting the GNSO

1 0

CANCELLED | Meeting Invitation | GNSO SCCI Call | Wednesday, 01 July 2026
by Terri Agnew June 30, 2026

June 30, 2026

**This meeting has been cancelled. Please remove it from your calendars. Dear all, The next meeting of the GNSO Standing Committee on Continuous Improvement (SCCI) will take place on Wednesday, 01 July 2026 at 12:00 UTC for 1 hour. Zoom Webinar link: : https://icann.zoom.us/j/96269931065?pwd=c0VKWkpMZHdNSlNSQkYrSG5MZmxQUT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/96269931065?pwd=c0VKWkpM…> Meeting ID: 962 6993 1065 Passcode: .&@z^zfSL1 Audio: Webinar ID: 962 6993 1065 Passcode: 0702315261 International numbers available: https://icann.zoom.us/u/ad6GAsKCUM ALL: Before joining the call: * Please send apologies to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…>, the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…>, and the ICANN Community Participant Code of Conduct<https://www.icann.org/en/system/files/files/adopted-icann-community-partici…>. * Visit the 2026 Wiki Agenda pages: https://icann-community.atlassian.net/wiki/x/AQCPKQ Thank you, Kind regards, Julie Policy Team Supporting the GNSO

1 0

Follow-up: Action Items from SCCI Work Session at ICANN86
by Steve Chan June 30, 2026

June 30, 2026

Dear SCCI Members, I would like to follow up on a couple of action items from ICANN86. You will have seen the text updated at ICANN86, circulated by Saewon, which is reproduced below. We have not seen any input to date. If no substantive feedback is received ahead of our next meeting on Wednesday, 1 July 2026, we will cancel the call. Criteria 4: The GNSO actively combats domain name security threats. * Indicator 1: The GNSO has demonstrated meaningful activity towards mitigating DNS Abuse and security threats relating to domain names that are in scope for the GNSO domain name security threats. * Indicator 2: 66% of surveyed respondents agree that the GNSO has demonstrated meaningful activityely towards mitigating DNS Abuse and security threats relating to domain names that are in scope for the GNSOcombats domain name security threats. Second, leadership and staff have completed another action item from ICANN86, which was to prepare a draft Assessment Plan. If you will recall at ICANN86, we reviewed a couple of examples that were captured on slides. What we have since done is to complete the Assessment Plan for all of the Indicators. From our perspective, we believe the Assessment Plan is quite straight forward, but we want to ensure you all have adequate time to review. In the event we cancel the 1 July meeting, you can instead take the time to review the Assessment Plan! Please find the Assessment Plan on the third tab in this document: https://docs.google.com/spreadsheets/d/1xJGebCzGi5WJhnG8Dhg4s5smj4HZp9pE/ed… If you have any questions or concerns, please let us know. Best, Steve Steven Chan  VP, Policy Development Support & GNSO Relations Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org<mailto:steve.chan@icann.org> Mobile: +1.310.339.4410

3 4

REMINDER | Meeting Invitation | GNSO SCCI Call | Wednesday, 01 July 2026
by Terri Agnew June 30, 2026

June 30, 2026

Dear all, The next meeting of the GNSO Standing Committee on Continuous Improvement (SCCI) will take place on Wednesday, 01 July 2026 at 12:00 UTC for 1 hour. Zoom Webinar link: : https://icann.zoom.us/j/96269931065?pwd=c0VKWkpMZHdNSlNSQkYrSG5MZmxQUT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/96269931065?pwd=c0VKWkpM…> Meeting ID: 962 6993 1065 Passcode: .&@z^zfSL1 Audio: Webinar ID: 962 6993 1065 Passcode: 0702315261 International numbers available: https://icann.zoom.us/u/ad6GAsKCUM ALL: Before joining the call: * Please send apologies to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…>, the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…>, and the ICANN Community Participant Code of Conduct<https://www.icann.org/en/system/files/files/adopted-icann-community-partici…>. * Visit the 2026 Wiki Agenda pages: https://icann-community.atlassian.net/wiki/x/AQCPKQ Thank you, Kind regards, Julie Policy Team Supporting the GNSO

1 0

Re: Proposed Agenda for SCCI Work Session at ICANN86
by Saewon Lee June 11, 2026

June 11, 2026

Dear SCCI, Kindly note that the SCCI Work Session is scheduled for Monday, 8 June 2026, at 4:30pm CEST. My sincere apologies for any confusion caused below. I have now corrected the lower portion to 4:30pm (in red). See you all in Seville! Best regards, Saewon From: Saewon Lee via Gnso-scci <gnso-scci(a)icann.org> Reply-To: Saewon Lee <saewon.lee(a)icann.org> Date: Wednesday, June 3, 2026 at 12:51 PM To: "gnso-scci(a)icann.org" <gnso-scci(a)icann.org> Subject: [Gnso-scci] Proposed Agenda for SCCI Work Session at ICANN86 Dear SCCI, This is to inform you that a SCCI meeting has been scheduled during ICANN86 in Seville on Monday, 8 June 2026, at 4:30pm CEST. We look forward to seeing you there to tackle the next step of the CIP implementation work in Phase 1. The proposed agenda for the SCCI Work Session [icann86.sched.com]<https://urldefense.com/v3/__https:/icann86.sched.com/event/2NQMw/gnso-scci-…> during ICANN86 on Monday, 8 June 2026, at 4:30pm4pm CEST, is as follows: 1. Welcome and SOI Updates 2. Progress Update 3. Review of SG/Cs Feedback on the CIP Assessment Framework 4. Proposed CIP Assessment Plan 5. Next Steps 6. AOB Looking forward to seeing you in person or online soon! Kind regards, Saewon Saewon Lee Policy Development Support Manager for GNSO Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 (310) 463-5541 Email: saewon.lee(a)icann.org<mailto:saewon.lee@icann.org> Skype: saewon.lee.icann Website: www.icann.org<http://www.icann.org>

1 1

Meeting Invitation | GNSO SCCI Call | Wednesday, 01 July 2026
by Julie Bisland June 8, 2026

June 8, 2026

Dear all, The next meeting of the GNSO Standing Committee on Continuous Improvement (SCCI) will take place on Wednesday, 01 July 2026 at 12:00 UTC for 1 hour. Zoom Webinar link: : https://icann.zoom.us/j/96269931065?pwd=c0VKWkpMZHdNSlNSQkYrSG5MZmxQUT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/96269931065?pwd=c0VKWkpM…> Meeting ID: 962 6993 1065 Passcode: .&@z^zfSL1 Audio: Webinar ID: 962 6993 1065 Passcode: 0702315261 International numbers available: https://icann.zoom.us/u/ad6GAsKCUM ALL: Before joining the call: * Please send apologies to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…>, the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…>, and the ICANN Community Participant Code of Conduct<https://www.icann.org/en/system/files/files/adopted-icann-community-partici…>. * Visit the 2026 Wiki Agenda pages: https://icann-community.atlassian.net/wiki/x/AQCPKQ Thank you, Kind regards, Julie Policy Team Supporting the GNSO

1 0