- ripe-list - mailman.ripe.net

Constanze
by constanze buerger 20 May '26

20 May '26

Good morning everyone, Unfortunately, I won’t be able to attend RIPE 92, as I started a new position in April. I’m still continuing my work in the NRO Number Council / ASO AC with pleasure, and Andrei Robachevsky and Hervé Clément will support you on site on behalf of the NRO NC. Wishing you all a great and successful meeting — I’ll miss you. See you soon, Constanze

1 0

Working group chair (s)election process (11 of them)
by Sasha Romijn 18 May '26

18 May '26

Hi all, I'd like to start a discussion on the way we select working group chairs. I brought this up on the wg-chairs list some time ago, and saw dns-wg is discussing it[1] as well, so I thought I'd bring it to the wider list. The latest wg chair job description draft[2] says: > Each WG selects their chairs with a clearly defined process on a regular basis. The process should be announced in advance and clearly described to the WG members in advance in order to avoid surprise and to encourage as many volunteers as possible. > ... > - A selection process that also allows for online participation My initial questions to the community, with elaboration below: 1. Who should be eligible to participate in a chair selection, either by vote or sharing views? Mailing list subscribers? People who have actively contributed in the past N months? Anyone present at the session (in person? also remote?)? Anyone signed up to the mailing list before a certain time? Checked in for a certain number of RIPE meetings? Something else? I've seen no objections to my quote from the new draft job description, that online participation needs to be possible. (Explicitly not talking about who is eligible to be a chair candidate here, that's out of scope for now, I'm only talking about who should have a voice in the decision.) 2. Should "selection" and "election" be more clearly distinguished? What distinguishes contributing to the consensus from a vote? If we're effectively running an election, should we design it properly rather than calling it something else? Should there be a minimum length for something to be "a statement of support", vs e.g. 15x "+1 for Sasha"? To be clear, I am not in favour of electing chairs, but even less in favour of pretending we do one thing while doing another. 3. Do we actually need 11 slightly different processes to select a chair, one for each working group? I am aware there have historically been some strong opinions on having individual processes, but I'm not convinced this serves our community. We could also still distinguish "special interest groups" from "deciding what the RIPE NCC should do" and have two, depending on the harm a "malicious" chair could do. Though I don't feel that latter factor is reflected in current complexity. I bring this up, because over the years I've been involved in chair selection from several angles: as a candidate, as someone trying to encourage others to put themselves forward, seeing it in other working groups. I've had a look at all the existing WG chair selection procedures, details below. They vary quite a bit: in-person vs. remote participation, mailing list vs. meeting session, explicit ballots vs. consensus. They share a common structure: candidates are presented, WG members express views, chairs declare a consensus, kind of. With some exceptions: open source currently claims to do voting, but we have not actually done that. What "expressing views" and "WG members" mean is vague. One way this is visible: some selections I've watched start to look more like an election, on the mailing list. The chairs will ask for "send your statements of support to the list", and then the mailing list fills with "+1 to <name>". In more than one case, candidates saw the +1's on the list, got their (otherwise not RIPE involved) personal network to sign up to the list, and send +1's too. That creates an awkward situation for the chairs, and I can say from personal experience it is also awkward as a candidate. Some of the current procedures explicitly tie participation to physical presence at a RIPE meeting. DNS explicitly says "mailing list". Most leave it vague. The process for disputes varies wildly too: delegate to RIPE chair, have some voting process run by the RIPE NCC, or undocumented. Many selections are reasonably smooth, I feel we struggle more with finding candidates to begin with, which means some of our "consenus" has an element of "well, glad someone volunteered, sounds fine" (without me meaning to downplay the qualities of all those volunteers). But vague processes certainly can hurt signups for chair position too. Comparison: RIPE PC selection is a straightforward election, open to in-person and remote meeting attendees. I am not advocating we do this for chairs. More similar is the RIPE chair selection, but that process is far too heavy for WGs. I do think it is a good example of a process with similar underlying goals though. I am interested to hear what the community thinks. Is there a real problem to solve? And if so, how should we move towards a solution? I think Mirjam was planning to bring this up in the RIPE community plenary as well. Sasha (without my hat as opensource wg co-chair, but fully acknowledging we are part of this problem, though we hope to bring an improved version to the list soon) [1] https://mailman.ripe.net/archives/list/dns-wg@ripe.net/thread/B4WK4MHXJVCLB… [2] https://www.ripe.net/publications/docs/ripe-documents/other-documents/draft… Thanks to Raymond Jetten, Brian Nisbet, Leo Vegoda, and our RIPE chairs for their input in earlier threads. == Current policies: Connect and Database say: > WG members express their approval or otherwise of the presented candidates … the Chair(s) declare a decision MAT (the shortest process of all) and RIPE NCC services are similar but not identical to Connect and Database. IOT says: > The incoming co-chair will be chosen by the WG using consensus and the remaining co-chair will make the consensus determination. IPv6 and Security say: > WG Chairs are elected at WG sessions at RIPE meetings. Anyone physically present at the WG session is eligible to participate in the selection process. The candidate does not need to be physically present at the WG session. > If possible the Chair should be elected by acclamation by the WG or by consensus after discussion. If the result is unclear, then a secret ballot should be held. In the case of a ballot, votes will be counted by RIPE NCC Staff and/or Chairs of other WGs. The result will be determined by simple majority. Address policy is similar to IPv6, except with slightly different in-person/remote requirements: > The working group will select new chair(s) at the RIPE Address Policy Working Group session. Those present at the session, either in person or remotely, will determine by consensus among themselves who takes the available position(s). The remaining chair will determine whether consensus has been reached. If the working group finds itself without a chair the RIPE chair will determine consensus. > If no consensus can be reached then a secret ballot to elect the new chair(s) will be held at the working group session. Everyone physically present at the session can participate in the secret ballot. Votes will be counted by RIPE NCC Staff, and the result will be determined using proportional representation through the single transferable vote, otherwise known as PR-STV. The winner(s) of the secret ballot will become the new chair(s). DNS, where consensus can explicitly also be a tie: > At the end of a co-chair's term, the WG will decide by consensus who is appointed to the available co-chair position. In the event of a tie, the consensus tied candidates will draw lots. Consensus will be determined on the DNS WG mailing list Routing: > these are generally appointed by consensus of those present at a Working Group meeting. Open source: > If there is one (or more) application, the current co-chair and the new candidate start to discuss about among themselves who will be serving next terms. If no consensus is reached until 14 days before RIPE, then we'll have a voting at the RIPE meeting.

3 2

RIPE 92 Starts Today
by Meeting Mailbox 18 May '26

18 May '26

Dear colleagues, RIPE Chair Mirjam Kühne will open the RIPE 92 meeting in Edinburgh today at 14:00 local time (UTC+1). You can follow the meeting online via the live webcast: https://ripe92.ripe.net/live/ If you would like to chat with other RIPE community members at the meeting and ask questions, you need to register as an online participant. Registration for online participation is free, and you will receive a link to Meetecho, our online platform. Register at: https://ripe92.ripe.net/register/participate-online/ Track #RIPE92 on X (Twitter), Mastodon, Instagram, Facebook and LinkedIn to stay up to date with all RIPE Meeting updates. Best regards, The RIPE Meeting Team

1 0

New on RIPE Labs: Legacy Out of Contract
by Alun Davies 15 May '26

15 May '26

Dear colleagues, Following on from our 2024 look back at 10 years of legacy policy, we’ve been taking a deeper dive into out-of-contract legacy address space managed by the RIPE NCC. Qasim Lone and colleagues provide a detailed breakdown of the numbers and explore the behaviours that emerge from this region of IPv4. Read more on RIPE Labs: https://labs.ripe.net/author/qasim-lone/legacy-out-of-contract/ Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

Notice to the ASO Community: ICANN Approval Action Community Forum and Rejection Action Petition Period
by Ulka Athale 13 May '26

13 May '26

This message is sent on behalf of the Number Resource Organization (NRO) --------- The original announcements are available on the NRO website: Approval Action Community Forum on Board Approval of Fundamental Bylaws: https://www.nro.net/notice-to-the-aso-community-on-approval-action-communit… Rejection Action Petition Period for Standard Bylaws Amendments, IANA and and ICANN FY27 Operating Plan and Budget, ICANN FY27-31 Operating and Financial Plan: https://www.nro.net/notice-to-the-aso-community-on-rejection-action-petitio… --------- Summary These notices announce: 1. The ICANN Board's approval of Fundamental Bylaws Amendments on 3 May 2026, which triggers a notice period for an Approval Action Community Forum. Any comments on these ICANN Bylaws changes should be sent to the ASO Secretariat at secretariat [at] aso.icann.org no later than 9 June 2026 at 11:59 pm PDT. 2. The ICANN Board's approval of Standard Bylaws Amendments, the IANA and ICANN FY27 Operating Plan and Budget and the ICANN FY27-31 Operating and Financial Plan, triggering the Rejection Action Petition Period ending on 1 June 2026 at 06:59 UTC. Any Rejection Action Petition to the ASO should be sent to the ASO Secretariat at secretariat [at] aso.icann.org before the deadline. --------- Background Information The NRO serves as the Address Supporting Organization (ASO) which is a Supporting Organization under ICANN's structure. The Empowered Community is the mechanism through which ICANN's Supporting Organizations (SOs) and Advisory Committees (ACs) can organize under California law to legally enforce community powers. The Community has nine powers to ensure the ICANN Board and Organization are accountable: - Reject ICANN and IANA budgets, and ICANN operating and strategic plans - Reject standard Bylaw amendments - Reject PTI governance actions - Approve fundamental Bylaw and Articles amendments, and asset sales - Recall the entire ICANN Board - Appoint and remove individual ICANN Board directors (other than the President)- Require the ICANN Board to review its rejection of IANA Function Review (IFR),special IFR, Separation Cross-Community Working Group (SCWG) creation,and SCWG recommendation decisions - Initiate community reconsideration request, mediation, or Independent Review Process (IRP) - The rights of inspection and investigation Read more about the Empowered Community here: https://www.icann.org/ec ------------------------------ Approval Action Community Forum on Board Approval of Fundamental Bylaws: ------------------------------ Dear RIR Community, As a Decisional Participant in the ICANN Empowered Community, the Address Supporting Organization has received a notification from the ICANN Secretary concerning the ICANN Board’s approval of Fundamental Bylaws Amendments to Articles 17 and 18 of the ICANN Bylaws. In accordance with the ICANN Bylaws, Decisional Participants are required to promptly inform their constituents of the delivery of the ICANN Board decisions relating to these Fundamental Bylaws Amendments. The ICANN Board approved the Fundamental Bylaws Amendments on 3 May 2026. The Board resolutions, including the discussion and rationale, are available here: Bylaws Amendment – IANA Naming Function Review https://www.icann.org/en/board-activities-and-meetings/materials/approved-r… Bylaws Amendment – Customer Standing Committee Composition and Review, and CSC Charter https://www.icann.org/en/board-activities-and-meetings/materials/approved-r… The text of the Fundamental Bylaws Amendments is available here: Article 17 – Customer Standing Committee https://itp.cdn.icann.org/en/files/governance/proposed-updates-to-article-1… Article 18 – IANA Naming Function Reviews https://itp.cdn.icann.org/en/files/governance/proposed-updates-to-article-1… Under the ICANN Bylaws, delivery of the Secretary’s Notice triggers an Approval Action Community Forum. The Forum must be convened and concluded during the period beginning on the Approval Action Board Notification Date, 11 May 2026, and ending at 11:59 pm PDT on the 30th day after that date, 9 June 2026, or during the next scheduled ICANN Public Meeting, ICANN86, which will take place from 8–11 June 2026. Further details on the Approval Action process are available in Article 1.2 of Annex D of the ICANN Bylaws: https://www.icann.org/resources/pages/governance/bylaws-en/#annexD Please note that the Approval Action Community Forum is convened at the direction of the Empowered Community Administration. Any comments on these ICANN Bylaws changes should be sent to the ASO Secretariat at secretariat [at] aso.icann.org no later than 9 June 2026 at 11:59 pm PDT. Regards, ASO Secretariat ------------------------------ Notice to the ASO Community on Rejection Action Petition Period for Standard Bylaws Amendments, IANA and ICANN FY27 Operating Plan and Budget, ICANN FY27-31 Operating and Financial Plan ------------------------------ Dear RIR Community, As a Decisional Participant in the ICANN Empowered Community, the Address Supporting Organization has received a notification from the ICANN Secretary concerning the ICANN Board’s approval of the following items: Standard Bylaws Amendment to Article 27 of the ICANN Bylaws IANA FY27 Operating Plan and Budget ICANN FY27 Operating Plan and Budget ICANN FY27–31 Operating and Financial Plan In accordance with the ICANN Bylaws, Decisional Participants are required to promptly inform their constituents of the delivery of these ICANN Board decisions. Pursuant to Section 25.1 of the ICANN Bylaws, this serves as notice to the Empowered Community Administration and the Decisional Participants that, on 3 May 2026, the ICANN Board approved a Standard Bylaws Amendment to Article 27 of the ICANN Bylaws. The Board resolution approving the Standard Bylaws Amendment is available here: https://www.icann.org/en/board-activities-and-meetings/materials/approved-r… The text of the approved Standard Bylaws Amendment is available here: https://www.icann.org/en/system/files/files/transition-article-to-address-s… The purpose of this amendment is to create a temporary pause and reset mechanism for ICANN’s Specific Reviews. Pursuant to Section 22.4(b)(v) of the ICANN Bylaws, this also serves as notice to the Empowered Community Administration and the Decisional Participants that, on 3 May 2026, the ICANN Board approved the following plans and budgets: IANA FY27 Operating Plan and Budget ICANN FY27 Operating Plan and Budget ICANN FY27–31 Operating and Financial Plan The Board resolution approving these plans and budgets is available here: https://www.icann.org/en/board-activities-and-meetings/materials/approved-r… The approved documents are available as follows: IANA FY27 Operating Plan and Budget https://www.icann.org/en/system/files/files/adopted-iana-op-plan-budget-fy2… ICANN FY27 Operating Plan Pages 117–215 of the following document: https://www.icann.org/en/system/files/files/adopted-icann-op-financial-plan… ICANN FY27 Budget https://www.icann.org/en/system/files/files/adopted-icann-budget-fy2027-pub… ICANN FY27–31 Operating and Financial Plan Pages 1–116 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 to reject the Board’s approval of these actions. During the applicable Rejection Action Petition Period, any individual may submit a petition to any Decisional Participant seeking to reject the Board action. The Rejection Action Petition Period will end on 1 June 2026 at 06:59 UTC. Further details on the Rejection Process, including the relevant deadlines and requirements for Rejection Action Petitions, are available in Article 2 of Annex D of the ICANN Bylaws: https://www.icann.org/resources/pages/governance/bylaws-en/#annexD Any Rejection Action Petition to the ASO should be sent to the ASO Secretariat at secretariat [at] aso.icann.org before the deadline. Regards, ASO Secretariat -- Kind regards, Ulka Athale Community Development Manager RIPE NCC www.ripe.net

1 0

PC Elections @ RIPE 92
by Brian Nisbet 12 May '26

12 May '26

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 2026 who will be elected by the RIPE community at RIPE 92. There are currently two seats up for election to the RIPE PC. 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 91 PC elections can be sent in from Tuesday, 12 May, until Tuesday, 19 May, 15:30 (BST/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, 19 May at 15:30 (BST/UTC+1) and publish the biographies on the RIPE Meeting web site. The RIPE PC online voting system will be open from Tuesday, 19 May, 16:00 (BST/UTC+1) until Thursday, 21 May, 17:00 (BST/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, 22 May, during the closing plenary session. Important Dates and Deadlines Nominations Open: Tuesday, 12 May Nominations Close: Tuesday, 19 May, 15:30 (BST/UTC+1) Voting Begins: Tuesday, 19 May, 16:00 (BST/UTC+1) Voting Closes: Thursday, 21 May, 17:00 (BST/UTC+1) Results Announced: Friday, 22 May, during the Closing Plenary session Questions about the RIPE PC can be sent to pc(a)ripe.net. Brian On Behalf of the RIPE PC Brian Nisbet (he/him) Head of Service Operations Asiera (formerly HEAnet), Ireland's National Research and Education Network North Dock Two, 93-94 North Wall Quay, Dublin 1, D01 V8Y6 +35316609040 brian.nisbet(a)asiera.ie www.heanet.ie<http://www.heanet.ie> www.asiera.ie<https://www.asiera.ie/> Registered in Ireland, No. 275301. CRA No. 20036270

1 0

The RIPE Chair Team Reports - May 2026
by Mirjam Kuehne 11 May '26

11 May '26

Dear colleagues, In this new article on RIPE Labs, we report on what to expect at RIPE 92, including the main programme and parallel events, WG chair selections and support for newcomers, as well as highlights from recent industry events. We hope to see you all next week in Edinburgh either in person or online. Kind regards, Mirjam Kühne & Anna Wilson RIPE Chair Team

1 1

RIR Governance Document Version 2: Status Report May 2026 now available
by Ulka Athale 08 May '26

08 May '26

This message is sent on behalf of the Number Resource Organization (NRO) ----------------- This announcement provides an update on the ongoing work to update ICP-2 by the RIR Governance Document. The announcement is available at: https://www.nro.net/rir-governance-document-version-2-status-report-may-202… ----------------- RIR Governance Document Version 2: Status Report May 2026 now available ----------------- The Number Resource Organization Number Council (NRO NC) has updated the Q1 Status Report based on discussions held during the in‑person meetings at ICANN 85 [1] [2]. The Q1 Status Report built on the outcomes of the NRO NC workshop held from 12 to 14 November 2025 in Montevideo. That workshop reviewed feedback received across the five RIR mailing lists, as well as input submitted through webinars and online sessions, RIR meetings, community fora, engagement with ICANN communities, and the ICANN Public Comment process. The Status Report identifies open issues, highlights topics that attracted significant comment, and records decisions made by the NRO NC in response to community input. ----------------- Status Report May 2026 ----------------- The Status Report May 2026 is now available. This version continues to track progress on updating the RIR Governance Document, providing transparency on issues under discussion, areas where drafting is underway, and topics that remain in progress as the NRO NC works towards the final draft of the document. https://www.nro.net/policy/internet-coordination-policy-2/rir-governance-do… We encourage interested parties to review the Status Report and continue to monitor progress ahead of the publication of the final draft, which will advance to the RIRs and ICANN for approval and adoption. We sincerely thank everyone who has shared their insights and appreciate the time, thought, and effort contributed by participants. On behalf of the NRO NC The Number Resource Organization Number Council (NRO NC) is also known as the Address Supporting Organization Address Council (ASO AC) within ICANN, where it serves as the body responsible for overseeing global policy development related to Internet number resources. [1] Q1 Status Report: https://www.nro.net/wp-content/uploads/RIR-Governance-Document-Version-2-St… [2] ASO AC Participation in ICANN 85: https://www.nro.net/aso-ac-participation-in-icann-85/ -- Kind regards, Ulka Athale Community Development Manager RIPE NCC www.ripe.net

1 0

Draft RIPE Working Group Chair Job Description and Procedures v2 - Last Call
by Mirjam Kuehne 06 May '26

06 May '26

Dear colleagues, We did not receive any additional comments after publishing v2 of the Draft RIPE Working Group Chair Job Description and Procedures: https://www.ripe.net/publications/docs/ripe-documents/other-documents/draft… This is a Last Call for comments. It will end on 20 May at 06:00 UTC. Kind regards, Mirjam Kühne RIPE Chair

1 0

New on RIPE Labs: Routing, QUIC, and More
by Alun Davies 05 May '26

05 May '26

Dear colleagues, Here’s a quick round-up of what we’ve been publishing on RIPE Labs over the past couple of weeks: - Questioning the IPv8 Proposal A critical look at the IPv8 proposal and why trying to solve everything all at once might not be the answer. - Making Resource Holders Easier to Identify: Introducing reg-nr in the RIPE Database A simple change that makes it much easier to identify who is actually behind Internet resources. - From BGP Data to Insight: Simplifying Real-Time Routing Analysis On making real-time BGP data easier to explore, understand, and act on. - The Internet’s New Builders On how the companies driving Internet traffic are increasingly the ones building the infrastructure behind it. - ADoX Deployment in the Wild Even with QUIC’s privacy features, passive measurements can still reveal how large networks are built. - Understanding DDoS Scrubbing in BGP: Five Leading Scrubbers Using BGP data to identify how five major providers handle DDoS mitigation in practice. - Using QUIC Backscatter to Infer Hypergiant Deployment Configurations On how backscatter data can uncover how hypergiants deploy QUIC in the real world. - Towards Understanding City-Level Routing Using BGP Location Communities On what BGP communities can tell us about routing behaviour at the city level. You can find them all here: https://labs.ripe.net/ Happy reading, and as always, all comments and contributions are very welcome! Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0