- ripe-list - mailman.ripe.net

Notice to the ASO Community on Rejection Action Petition Period for ICANN/IANA FY26 Operating Plan and Budget and ICANN FY26-30 Operating and Financial Plan
by Ulka Athale 09 May '25

09 May '25

This message is sent on behalf of the NRO Secretariat. ----------- Summary ----------- The ICANN Empowered Community is the mechanism through which ICANN’s Supporting Organizations (SOs) and Advisory Committees (ACs) can organise, under California law, to legally enforce their community powers and hold ICANN accountable for its actions. The Address Supporting Organization (ASO) is the Decisional Participant in the Empowered Committee. The ICANN Board has approved the operating plans and budgets for IANA and ICANN for 2026, as well as the ICANN Operating and Financial Plan from 2026-2030. Should anyone wish to object to the ICANN Board's approval of these plans and budgets, they may send a Rejection Action Petition to the ASO Secretariat by 30 May 2025. The announcement is available at: https://www.nro.net/notice-to-the-aso-community-on-rejection-action-petitio… ----------- Notice to the ASO Community on Rejection Action Petition Period for ICANN/IANA FY26 Operating Plan and Budget and ICANN FY26-30 Operating and Financial Plan ----------- 9 MAY 2025 Dear RIR Community As a Decisional Participant, the Address Supporting Organization received a notification from the ICANN Secretary requiring Decisional Participants to inform their constituents of the delivery of: - IANA FY26 Operating Plan and Budget - ICANN FY26 Operating Plan and Budget - ICANN FY26-30 Operating and Financial Plan Pursuant to Section 22.4(b)(v) of the ICANN Bylaws (at https://www.icann.org/resources/pages/governance/bylaws-en/#article22), this serves as notice to the EC Administration and Decisional Participants in the Empowered Community that on 3 May 2025 the ICANN Board approved the above mentioned Plans and Budgets. The resolutions approving the Operating Plans and Budgets are available at https://www.icann.org/en/board-activities-and-meetings/materials/approved-r… ----------- IANA FY26 Operating Plan and Budget ----------- The IANA FY26 Operating Plan and Budget as approved reflects updates made after the public comment proceeding closed. The IANA FY26 Operating Plan and Budget is available at:https://www.icann.org/en/system/files/files/adopted-iana-op-plan-budget-… ----------- ICANN FY26 Operating Plan and Budget ----------- The ICANN FY26 Operating Plan as approved reflects updates made after the public comment proceeding closed. The ICANN FY26 Operating Plan is available at pages 122-227 of the following document: https://www.icann.org/en/system/files/files/adopted-icann-op-financial-plan… ICANN FY26 Budget is available at: https://www.icann.org/en/system/files/files/adopted-icann-budget-fy2026-pub… ----------- ICANN FY26-30 Operating and Financial Plan ----------- The ICANN FY26-30 Operating and Financial Plan as approved reflects updates made after the public comment proceeding closed. The ICANN FY26-30 Operating and Financial Plan is available at pages 1-121 of the following document: https://www.icann.org/en/system/files/files/adopted-icann-op-financial-plan… ----------- Under the ICANN Bylaws, the Empowered Community now has the opportunity to consider whether it will reject the Board’s approval. During Rejection Action Petition Periods any individual may submit a petition to any Decisional Participant, seeking to reject the Board action. This petition period will end on 30 May 2025 at 06:59 UTC Please refer to Article 2, Annex D of the ICANN Bylaws for additional details on the Rejection Process, including all pertinent deadlines and requirements for Rejection Action Petitions: https://www.icann.org/resources/pages/governance/bylaws-en/#annexD Any Rejection Action Petition should be sent to the ASO Secretariat ( secretariat [at] aso.icann.org) before the deadline. Regards ASO Secretariat -- Kind regards, Ulka Athale RIPE NCC www.ripe.net

1 0

ICP-2 Discussions at RIPE 90
by herve.clement＠orange.com 09 May '25

09 May '25

Dear all, The consultation to get feedback on the draft "RIR Governance Document" intended to replace ICP-2 was launched on 14 April and closes on 27 May 2025: https://www.nro.net/policy/internet-coordination-policy-2/rir-governance-do… RIPE 90 gives us a valuable opportunity to hear your thoughts on this topic. The RIPE NRO NC representatives - Andrei Robachevsky, Constanze Bürger and I will be available during RIPE 90 during the following sessions: ------------------------------ BoF Keeping Up With the Times: Updating ICP-2 | Monday, 12 May at 18:00 UTC+1 ------------------------------ There will be a BoF on ICP-2 on Monday. We encourage you to please read the draft document in advance so that we use this slot to discuss the document as far as possible. We held a RIPE NCC Open House on 29 April, and the slides and recording are available here: https://www.ripe.net/meetings/open-house/updating-icp-2/ ------------------------------ Updates during the Address Policy Working Group Sessions | Wednesday, 09:00-10:30 UTC+1 ------------------------------ We will provide a regular update on the activities of the NRO NC (which serves as the ASO AC) during the Address Policy Working Group session, as well as share an overview of the work done to update ICP-2. ------------------------------ RIPE Community Plenary Session | Thursday, 16:00 - 17:30 UTC+1 ------------------------------ We will provide an overview of key takeaways and outcomes from the BoF. ------------------------------ NRO NC Office Hours: Daily during RIPE 90 from 13:30-14:00 ------------------------------ We will be available for informal chats to hear your input and answer your questions every day during RIPE 90. Note also that we recently published a RIPE Labs article providing more information on the background and scope of the ICP-2 review process: https://labs.ripe.net/author/nick-nugent/revising-icp-2-scope-expectations-… We look forward to seeing you at RIPE 90 and continuing the discussions. Regards, Constanze Bürger, Andrei Robachevsky and Hervé Clément (ASO AC chair) ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 0

RIPE NCC Trust Portal Launched
by Eleonora Petridou 08 May '25

08 May '25

Dear colleagues, We have launched a new Trust Portal to provide greater transparency into our operations and to help members and stakeholders better understand how we manage our security, compliance, and governance: https://trust.ripe.net/ The portal provides a comprehensive overview of how we protect the confidentiality, integrity, and availability of our services. It includes key policies and processes covering information security, data protection, vulnerability management, and incident response. It also highlights our compliance with frameworks like SOC 2 for RPKI services, our progress toward ISO 27001 certification, and adherence to GDPR and other relevant EU regulations. For law enforcement and other competent authorities, the Trust Portal also provides guidance on how to request information from the RIPE NCC, and links to other useful supporting information. We invite you to explore the Trust Portal, and welcome any feedback as we continue improving our transparency. Email security(a)ripe.net if you would like to know more. Kind regards, Eleonora Petridou Chief Information Security Officer RIPE NCC

1 0

Welcome Vasja Križmančič to the RIPE NomCom 2025
by RIPE NomCom Chair 06 May '25

06 May '25

Dear RIPE community, The RIPE NomCom has just passed the following resolution unanimously: Considering that Randy Bush has resigned from the committee and that Vasja Križmančič is the first person on the reserve list, the committee resolves to add Vasja Križmančič as a voting member to the committee effective immediately. We thank Randy for his contributions. Best, Jan Žorž Chair RIPE NomCom 2025

1 0

The RIPE Chair Team Reports - May 2025
by Mirjam Kuehne 06 May '25

06 May '25

Dear colleagues, With less than a week to go until RIPE 90 kicks off in Lisbon, here are some highlights and topics you can expect to be discussed at the meeting. https://labs.ripe.net/author/mirjam_kuhne/the-ripe-chair-team-reports-may-2… Kind regards, Mirjam Kühne RIPE Chair

1 0

RIPE 90 Programme Committee Elections
by Brian Nisbet 06 May '25

06 May '25

Colleagues, The RIPE Programme Committee is responsible for recruiting and selecting presentations for the RIPE Meeting Plenary sessions. As the term of two RIPE PC members end, we are looking for new members in Spring 2025 who will be elected by the RIPE community at RIPE 90. There are currently two seats up for election to the RIPE PC and nominations open today! Please send nominations, with a biography, statement of interest and photograph, to pc(a)ripe.net. RIPE Meeting Programme Committee: Appointment, Roles and Responsibilities - https://www.ripe.net/publications/docs/ripe-pc-appointment-roles-responsibi… - provides more information about the composition and roles of the RIPE PC. Nominations for the RIPE 90 PC elections can be sent in from Tuesday, 6 May, until Tuesday, 13 May, 15:30 (WEST/UTC+1). Please include a recent picture and short biography with your nomination. We will announce the PC elections at the RIPE meeting opening sessions, but interested parties can already nominate themselves. If you are nominating someone else, please ensure that the person concerned is willing to be nominated and is copied on emails sent to the PC. The PC will attempt to confirm that nomination with the nominee before proceeding. We will close candidate nominations on Tuesday, 13 May at 15:30 (WEST/UTC+1) and publish the biographies on the RIPE Meeting web site. The RIPE PC online voting system will be open from Tuesday, 13 May, 16:00 (WEST/UTC+1) until Thursday, 15 May, 17:00 (WEST/UTC+1), for community members to cast their votes. The total voting numbers may be public. The official announcement of the elected RIPE PC members will be on the morning of Friday, 16 May, during the closing plenary session. Important Dates and Deadlines Nominations Open: Tuesday, 6 May Nominations Close: Tuesday, 13 May, 15:30 (WEST/UTC+1) Voting Begins: Tuesday, 13 May, 16:00 (WEST/UTC+1) Voting Closes: Thursday, 15 May, 17:00 (WEST/UTC+1) Results Announced: Friday, 16 May, during the Closing Plenary session If you have any questions, please don't hesitate to email pc(a)ripe.net Regards, Brian On Behalf of the RIPE PC Brian Nisbet (he/him) Head of Service Operations HEAnet CLG, Ireland's National Education and Research Network North Dock Two, 93-94 North Wall Quay, Dublin 1, D01 V8Y6 +35316609040 brian.nisbet(a)heanet.ie www.heanet.ie Registered in Ireland, No. 275301. CRA No. 20036270

1 0

Join the RIPE NCC User Research Pool
by Fallon Albrecht 06 May '25

06 May '25

Dear colleagues, We are currently looking for community members and users who are willing to take part in user research. This research helps us understand how people use our platforms and where we can make improvements to make them more intuitive, accessible, and user-friendly. If you choose to participate, you might be invited to join short interviews, usability tests, or other research activities. Your input will help us improve how our platforms and tools work. You can sign up at: https://www.ripe.net/about-us/what-we-do/user-research/ Attending RIPE 90 in Lisbon? We’ll also be conducting live user research sessions during RIPE 90 in Lisbon. We invite you to test our new navigation prototype. We will also show you a quick demo of our OAuth 2.0 authorisation solution. If you’re attending, this is a great opportunity to provide your feedback in person and share your experience directly with our team. You can book your slot at: https://nccsurvey.ripe.net/m6Nk6P <https://nccsurvey.ripe.net/m6Nk6P> Thanks in advance for your time and feedback. Kind regards, Fallon Albrecht and Antonella De Bellis User Research team RIPE NCC

1 0

Consultation on Draft “Governance Document for the Recognition, Maintenance, and Derecognition of Regional Internet Registries”
by Ulka Athale 06 May '25

06 May '25

Dear colleagues, This message is sent on behalf of the Number Resource Organization Number Council (NRO NC) The announcement can be viewed at: https://www.nro.net/consultation-on-draft-governance-document-for-the-recog… ----------------------------------------- The NRO NC has published a draft version of a document that aims to update ICP-2: Criteria for Establishment of New Regional Internet Registries. This updated document is titled “Governance Document for the Recognition, Maintenance, and Derecognition of Regional Internet Registries” (RIR Governance Document) and can be viewed here: https://www.nro.net/policy/internet-coordination-policy-2/rir-governance-do… We now invite your input on this draft. Please make sure to share your feedback by Tuesday, 27 May 2025 on your regional consultation list. ----------------------------------------- Background Information ----------------------------------------- In October 2023, the Number Resource Organization Executive Council (NRO EC) asked the NRO Number Council (NRO NC), that fulfils the role of the Address Supporting Organization Address Council (ASO AC), to establish and manage a process to update the Internet Coordination Policy (ICP-2): Criteria for Establishment of New Regional Internet Registries document [1]. Modification of ICP-2 requires an open and transparent process to allow participation from across the global RIR and ICANN communities. As part of this process, the NRO NC invited the global Regional Internet Registry (RIR) communities to provide feedback on each principle via a questionnaire, which was open from 8 October until 6 December 2024 [2]. On 24 February 2025, the NRO published a qualitative analysis and summary of the community responses received on the proposed principles to update ICP-2 [3]. The updated criteria will continue to reflect the fundamental principles required for recognizing and evaluating new RIRs in keeping with the Internet landscape of today. There is no intention to fundamentally change or redesign the existing RIR system. The focus of the review and revision process is to identify existing gaps and areas of improvement to support the continued stability and self-governance of the Internet Numbers Registry System. This includes expanding or adding details related to governance, ecosystem, life cycle, recognition and operation of RIRs. It also outlines principles for the potential ‘derecognition’ of an RIR if it fails to adhere to the established criteria. ----------------------------------------- Share Your Input ----------------------------------------- The NRO NC is now seeking community input on the new draft text of the proposed “RIR Governance Document”. This feedback will be reviewed by the NRO NC during their workshop scheduled during ICANN 83 in June. We ask you to please keep the following in mind while preparing your comments: - Please share feedback that is specific to this draft - We are particularly interested in hearing your views on the new requirements in the draft - Whether the draft provides sufficient clarity regarding the ongoing obligations of an RIR and the remediation steps if the obligations are not met - This document does not address the implementation of the RIR criteria; comments on implementation will be considered out of scope - Constructive comments are highly appreciated To participate, please follow the consultations in your region listed on the Community Engagements web page: https://www.nro.net/policy/internet-coordination-policy-2/community-engagem… ----------------------------------------- Join a Session ----------------------------------------- All the planned sessions during which we will share information on the draft “RIR Governance Document” and the process to update ICP-2 will be listed on the NRO website. The sessions will also be recorded and archived, links to the recordings will also be listed on the same webpage: https://www.nro.net/policy/internet-coordination-policy-2/community-engagem… Regards, The NRO Secretariat [1] https://www.icann.org/resources/pages/new-rirs-criteria-2012-02-25-en [2] https://www.nro.net/the-nro-invites-internet-community-to-participate-in-ic… [3] https://www.nro.net/policy/internet-coordination-policy-2/icp-2-principles-… ----------------------------------------- For further reference, the timeline and process to review ICP-2 is available here: https://www.nro.net/policy/internet-coordination-policy-2/process-for-the-r… Kind regards, Ulka Athale RIPE NCC www.ripe.net

7 7

nomcom withdrawal
by Randy Bush 04 May '25

04 May '25

jan, tl;dr: i wish to withdraw from the nomcom -- as i decided to run for the eb long after the nomcom process started, the letter of 788 would let me stay on both. but that would not be the spirit of 788. withdrawing is just the right thing to do. my apologies for this taking so long. among other things, i was considering doing the reverse, withdrawing from the eb election as i consider the ripe chair to be a critical spof. but friends convinced me to trust the system, the nomcom will do the right thing without me. of course i would have withdrawn from nomcom if elected to the eb. an eb member really really should not wear two hats. analogously, if elected to the eb, i would withdraw from the coc team. apologies for chaos creation, and thanks for understanding. randy

2 1

Feedback on the Draft Governance Document for RIR Recognition and Derecognition
by Abdulrahman Almousa 29 Apr '25

29 Apr '25

Dears, After a review of the “Governance Document for the Recognition, Maintenance, and Derecognition of Regional Internet Registries” draft, I would like to submit the following feedback: *1. Insufficient Clarity Regarding Regional Continuity After Derecognition* *Observation:* The draft outlines the procedures for derecognizing an RIR but *does not provide clarity* on how continuity of Internet number resource management will be maintained in the affected region after derecognition. *Impact:* The absence of a predefined transitional or fallback mechanism poses operational risks for resource holders in the affected region and may jeopardize Internet infrastructure stability at a regional level. *Recommendation:* Including a clear provision specifying: - An obligation to guarantee service continuity for affected resource holders, - A framework for temporary stewardship or reassignment of responsibilities to an interim or existing RIR, - A stakeholder consultation process to guide regional transition planning. This addition would align with the draft's stated goal of safeguarding the reliability and neutrality of the Internet number registry system. *2. Concerns About the Requirement for Unanimous RIR Support for New RIR Recognition* *Observation:* Section 2.3(c) implies that *unanimous support* from all existing RIRs is necessary before forwarding a Candidate RIR proposal to ICANN for final approval. *Impact:* Requiring unanimous agreement effectively grants any single RIR the power to veto the recognition of a new RIR, regardless of demonstrated regional need or readiness. This could inhibit the natural evolution of the registry system, particularly in underserved or emerging regions that meet the technical and governance standards. *Recommendation:* Revising the requirement to allow for a *qualified majority* (e.g., three out of five RIRs) within the NRO Executive Council for forwarding a recognition proposal to ICANN. This change would uphold the principles of collaborative governance without unduly blocking legitimate initiatives. BR, Abdulrahman

1 0