November 2025 - Ccnso-leadership

Re: [EXTERNAL] - [SOAC-Leaders-ICANNMeeting-Planning] Reminder by Friday 21st Nov: Feedback needed: SOAC Leaders ICANN84 Feedback & ICANN85 Kick off call
by Jordan Carter Nov. 21, 2025

Nov. 21, 2025

Hi folks Personally I'm happy with a reviews session. Will we need two? If not, I wonder if a session about 'after the WSIS' might be useful. The framework will be known, and so situating ICANN in the post-WSIS world would have value? The geopol update, which is dry and info rich, could definitely remain in prep week. Thoughts? J Get Outlook for iOS<https://aka.ms/o0ukef> ________________________________ From: Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning <soac-leaders-icannmeeting-planning(a)icann.org> Sent: Thursday, November 20, 2025 10:24:16 PM To: soac-leaders-icannmeeting-planning(a)icann.org <soac-leaders-icannmeeting-planning(a)icann.org> Subject: [EXTERNAL] - [SOAC-Leaders-ICANNMeeting-Planning] Reminder by Friday 21st Nov: Feedback needed: SOAC Leaders ICANN84 Feedback & ICANN85 Kick off call Dear all, A reminder that your feedback is required on the below points stemming from the first ICANN85 Kick off call last week, copied here from the email below for your convenience: REQUEST: We seek your feedback and suggestions on the following questions: * Community Sessions 1 & 2: Do you support scheduling a session on the Review of Reviews for Community Session 1? What other topics would you like to see discussion at the second Community Session, or would you rather see just the one Community Session on the schedule? * Do you support holding the Geopolitical Forum virtually as part of Prep Week for ICANN85? BLOCK SCHEDULE: The block schedule, updated version is attached to this email, has seen a few changes, coordinated by your SOAC Support staff, focusing only on the time and date of the bilateral sessions with the Board as follows: * Monday, 09 March 16:30 – 17:30: Change from Joint ICANN Board & GNSO Council to Joint ICANN Board and RSSAC * Wednesday, 11 March 10:30 – 11:30: Change from Joint ICANN Board & ASO to Joint ICANN Board & GNSO Council * Wednesday, 11 March 16:30 – 17:30: Change from Joint ICANN Board and RSSAC to Joint ICANN Board and ASO NEXT PRODUCTION CALL: Has been scheduled for Tuesday 25th November 2025 at 16:00 UTC. Please let us know if you have not received the calendar invitation. Thank you! Nathalie From: Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Monday, November 17, 2025 at 8:44 PM To: "soac-leaders-icannmeeting-planning(a)icann.org" <soac-leaders-icannmeeting-planning(a)icann.org> Subject: SOAC Leaders ICANN84 Feedback & ICANN85 Kick off call Dear all, Thank you to those who joined the ICANN84 Feedback & ICANN85 Kick Off call held earlier today. For those who could not make it, please find the recording here<https://icann.zoom.us/rec/play/_md_DoewpJ-dqSNoAEWZZxzNP5Xmy1b0YiQ0eCxbnBcu…> and the Block Schedule and Production timeline attached to this email. A second Production call will be scheduled very shortly. Please find here below a summary of what was said during the call, followed by action items for SOAC leadership: Feedback on ICANN84: * A scheduling conflict with a key ICANN org session of direct interest to ccTLD managers was raised by the ccNSO. Further communication and collaboration will be put in place to minimize the risk of this happening again. * A lack of coffee being served was noted for the last coffee break of the last day of the meeting, this will be relayed to our staff supporting catering. * A screen in one of the meeting rooms was too small for participants to read in the room, this has been noted by the Production team. * Appreciation was shared by those on the call for Meetings team and Travel for their efforts to procuring a venue at late notice and making the meeting a success * Support was shown for the ICANN85 Welcome Reception (gala) and for these taking place offsite when possible. Review of the proposed draft ICANN85 Block Schedule: * The new addition of a pilot for a ICANN Board & Community Discussion to the block schedule (as a concrete outcome of the How We Meet project) saw a discussion on its structure and purpose. Several participants were in favour of it being topic-based, rather than open questions to the Board. It was understood that this session will not replace the current joint SOAC meetings with the Board. There was a suggestion to hold this new session at the Policy Forum when there are no bilateral meetings with the Board. * The addition of a series of 2026 Next Round Info sessions, based on the anticipated timing of the launch of the next round of new gTLDs, was noted without objection. * The ccNSO raised the issue of set time blocks for Tech Day (Monday), this will be discussed with the ccNSO directly. * The option of having the Geopolitical Forum take place during Prep Week with a focus on interactive exchanges for the onsite meeting was also discussed. * Little time was left for the discussion on the Community Sessions (topics and whether to hold one or two) but the suggestion was made to have at least one of the sessions focus on the Review of Reviews. REQUEST: We seek your feedback and suggestions on the following questions: * Community Sessions 1 & 2: Do you support scheduling a session on the Review of Reviews for Community Session 1? What other topics would you like to see discussion at the second Community Session, or would you rather see just the one Community Session on the schedule? * Do you support holding the Geopolitical Forum virtually as part of Prep Week for ICANN85? We will greatly appreciate your feedback on these questions by Friday 21 November if possible. In addition, if you have suggestions for how we can plan and structure the new Board-Community Discussion session, we will be grateful to receive those as well. Thank you! Kind regards, Nathalie, on behalf of the Schedule team

2 1

Fwd: [soac-chairs] Draft Bylaw Change Playbook
by Alejandra Reynoso Barral Nov. 21, 2025

Nov. 21, 2025

FYI ******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. ******************************************* ---------- Forwarded message --------- From: Alejandra Reynoso Barral <alejandra.reynoso(a)gmail.com> Date: Fri, Nov 21, 2025 at 2:59 PM Subject: Re: [soac-chairs] Draft Bylaw Change Playbook To: Russ Weinstein <russ.weinstein(a)icann.org> Cc: Soac-chairs(a)icann.org <Soac-chairs(a)icann.org>, Policy Team Leaders < policy-team-leaders(a)icann.org>, Kurtis Lindqvist <kurtis.lindqvist(a)icann.org>, John Jeffrey <john.jeffrey(a)icann.org>, Sam Eisner <Samantha.Eisner(a)icann.org > Dear Russ After having a conversation with the ccNSO Council I want to express my appreciation for the proposed playbook, and I believe it is a sound basis to understand the complexities inherent in ICANN Bylaw changes. From reading the Playbook, it is our understanding that the Bylaw amendment process can be divided in two phases: - Phase one: The procedures to develop a proposed Bylaw change, starting with a request for a Bylaw change and ending with the Initiation of the Bylaw amendment process by the Board (directing a public comment) - Phase two: The procedures and actions as defined in the ICANN Bylaw amendment procedures starting with the public comment period and ending a Board decision to stop the process or ending with EC rejection or approval action process. After an initial evaluation of the playbook, we believe that focusing on the mapping and documenting of the first phase is most helpful to explain how a Bylaw amendment should be proposed by (a part of) the community, and to understand what to expect after an amendment is proposed. Since 2016, when the Empowered Community was established, various Bylaw amendments have been initiated and concluded, and the community has gained an understanding of its role and the procedures. Looking at the Bylaw Change Playbook we have identified the following basic flow for phase one (see overview below). 1. Originating Request. 2. Addressee. 3. Assessment of need and scope of the requested Bylaw amendment. 4. Coordination and detailing of proposals with requesting entities. 5. Consistency Check. 6. Board Initiation (Milestone): End of Phase 1 and Start of Phase 2. Assuming this flow is correct, we have the following questions and observations: - Does it make a difference how a Bylaw proposal originates? For example, through a PDP, a Bylaw mandated review, or a community working group? If so, what is the impact? - Are there Bylaw change requests that by definition can not result in an amendment, for example if a Bylaw amendment is only suggested as part of comment in a public comment procedure and this suggestion is not accepted? In the past the ccNSO Council suggested a Bylaw change through a public comment. This part of the public comments was not accepted by the relevant committee, i.e not included as recommendation by the review team. Does a request for a Bylaw change need to meet any formalities and/or format? - Who is the addressee of a Bylaw amendment? Board, CEO & President, other (for example both)? - Once a request is received, it is unclear from the Playbook, who from staff will be designated to assess the need and scope, who will be informed about the outcome, what is a reasonable timeline, and how to escalate matters if needed. We believe that providing clarity will add significantly to the predictability of the amendment process and cooperation of entities involved in the process. To date the ccNSO had varying experiences with respect to this and the next steps of Phase 1 ( Coordination with requester and Consistency check) . Finally, the Council would like to understand when a request fails? Who decides? Will the requesting party be informed and by whom? Kind regards, Alejandra Reynoso Overview of Phase 1 - Requesting a Bylaw amendment [image: image.jpeg] ******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. ******************************************* On Thu, Oct 23, 2025 at 4:25 PM Russ Weinstein via soac-chairs < soac-chairs(a)icann.org> wrote: > Dear SO AC Leaders, > > > > I hope your travel has gone smoothly (or is going smoothly). The team and > I am looking forward to seeing you soon here in Dublin! > > > > Based on a previous request for information on how the community can raise > the need for Bylaws amendments and the expected processes from start to > finish for such amendment processes, attached please find a discussion > draft of a Bylaws Playbook. We have been working on a draft that shares > meaningful information, with the hope that it is useful to the community. > While the procedural requirements from the ICANN Bylaws Article 25, > Sections 25.1 and 25.2 are defined, those procedural requirements only > start once there is language upon which the Bylaws amendment processes can > be formally initiated. As documented in the Playbook, there are a variety > of situations from which community could identify the possible need for a > Bylaws amendment. The Bylaws Playbook therefore is more example-based than > forward looking, exploring how Bylaws amendments have been raised in the > past. The Playbook then discusses how, once there is appropriate language > for consideration, the formal Section 25.1 or 25.2 processes move forward. > > > > We are looking for your feedback on the utility of this document and > whether there are modifications or enhancements that might serve the > community’s needs. If it would be helpful, we would be happy to schedule > some time next month to hear your initial thoughts. > > > > Thanks, > > Russ > > > > Russ Weinstein > > Senior Vice President, Policy Development Support > > Internet Corporation for Assigned Names and Numbers (ICANN) > _______________________________________________ > soac-chairs mailing list -- soac-chairs(a)icann.org > To unsubscribe send an email to soac-chairs-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. >

1 0

Fwd: DNS Abuse PDP Cooperation
by Alejandra Reynoso Barral Nov. 12, 2025

Nov. 12, 2025

FYI ******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. ******************************************* ---------- Forwarded message --------- From: Elizabeth Bacon <bbacon(a)pir.org> Date: Wed, Nov 12, 2025 at 6:03 PM Subject: DNS Abuse PDP Cooperation To: alejandra.reynoso(a)gmail.com <alejandra.reynoso(a)gmail.com>, Dennis Tan Tanaka <dtantanaka(a)verisign.com>, Chris Disspain <chris.disspain(a)identity.digital> Cc: Sue Schuler <secretariat(a)rysg.info>, Nikki Schuler <datasec(a)rysg.info> Hello, I hope your travel home from ICANN was smooth. After our discussions at ICANN, I wanted to follow up to try to establish a plan for collaboration between our groups on the DNS Abuse PDPs. Soon Council will have an updated Issues Report and Charter that reflects the Public Comments. It would be great to have some collaboration set up as those discussions get started. We are happy to set up a dedicated email list as well as meetings with our RySG DNS Abuse Working Group (and hopefully the joint CPH DNS Abuse Group) and your dedicated DNS Abuse Working Groups or teams. Please let us know what will work best for you and your group and we’ll get started! Looking forward to working together throughout the PDP processes. Best, Beth *Elizabeth Bacon* *| Chair, RySG* [image: Logo] <https://www.thenew.org/> *Senior Director, Policy and Privacy, CIPP/E, CIPM* beth <beth(a)pir.org>@pir.org <beth(a)pir.org> | +1 484.354.1936 | www.thenew.org | *Power your inspiration. Connect your world.*

1 0