- ripe-list - mailman.ripe.net

Call for Topics for RIPE 93 Community Plenary
by Mirjam Kuehne 21 Aug '26

21 Aug '26

Dear colleagues, The RIPE 93 Community Plenary will take place on Thursday, 29 October 2026 at 16:00 local Sofia time. If there are any specific topics you would like to discuss during this session, please let us know. You can find more about the RIPE Community Plenary and minutes of previous sessions here: https://www.ripe.net/participate/ripe/ripe-community-plenary Kind regards, Mirjam Kühne & Anna Wilson RIPE Chair Team

1 0

research survey on Segment Routing (SR-MPLS) traffic engineering practices
by Dekinder Florian 19 Aug '26

19 Aug '26

Dear colleagues, I am conducting a research survey on Segment Routing (SR-MPLS) traffic engineering practices in operational networks, as part of an ongoing measurement study at the University of Liège (Belgium). Our work builds on AReST, a methodology we developed to detect and characterize SR-MPLS tunnels from external traceroute measurements (paper: https://orbi.uliege.be/bitstream/2268/337150/1/paper.pdf — code: https://gitlab.uliege.be/segment-routing) The goal of this survey is to complement our external measurements with first-hand operational insight from network engineers and architects. If you are involved in the design, deployment, or operation of SR-MPLS in your network, I would greatly appreciate your input. The survey takes approximately 5 minutes and all responses will be kept strictly anonymized in any publication. Thank you for your time — every response helps, even if your deployment is limited or in early stages. Best regards, Florian Dekinder Contact: florian.dekinder(a)uliege.be<mailto:florian.dekinder@uliege.be> Link: https://forms.gle/2zPxABc2ZwL4Uxmn9

1 0

research survey on Segment Routing (SR-MPLS) traffic engineering practices
by Dekinder Florian 18 Aug '26

18 Aug '26

Dear colleagues, I am conducting a research survey on Segment Routing (SR-MPLS) traffic engineering practices in operational networks, as part of an ongoing measurement study at the University of Liège (Belgium). Our work builds on AReST, a methodology we developed to detect and characterize SR-MPLS tunnels from external traceroute measurements (paper: https://orbi.uliege.be/bitstream/2268/337150/1/paper.pdf — code: https://gitlab.uliege.be/segment-routing) The goal of this survey is to complement our external measurements with first-hand operational insight from network engineers and architects. If you are involved in the design, deployment, or operation of SR-MPLS in your network, I would greatly appreciate your input. The survey takes approximately 5 minutes and all responses will be kept strictly anonymized in any publication. Thank you for your time — every response helps, even if your deployment is limited or in early stages. Best regards, Florian Dekinder Contact: florian.dekinder(a)uliege.be<mailto:florian.dekinder@uliege.be>

1 0

Sjoerd Wolthers appointed Chief Technology Officer
by Hans Petter Holen 11 Aug '26

11 Aug '26

Dear all, After an intensive recruitment process, I am happy to announce that as of 1 September 2026 Sjoerd Wolthers will be the new Chief Technology Officer of the RIPE NCC. In the last several months, we executed an intense and thorough process to find our new CTO. We screened around 270 applicants through different selection rounds, including multiple interviews, a leadership and capability assessment, and a written assignment. During the process, we interviewed some really strong candidates and concluded after the final interviews that Sjoerd is the best match for the RIPE NCC. Sjoerd started his leadership career in 2004 at KPN, and he has fulfilled the CTO role at XS4ALL and FD Mediagroup. Over the last year, Sjoerd worked as interim Head of IT and interim CTO for the RIPE NCC, so his onboarding is mostly done and he knows what is expected from the RIPE NCC CTO. We are happy that Sjoerd will continue to work for us, leading the Technology division in such a way that our challenging objectives will be achieved. Sjoerd will be introduced to the RIPE community during the upcoming RIPE Meeting. We wish Sjoerd lots of success in his new position. Hans Petter Holen Chief Executive Officer RIPE NCC

1 0

ASO AC delivers Recommended Draft RIR Governance Document to NRO EC
by Ulka Athale 28 Jul '26

28 Jul '26

This message is sent on behalf of the Number Resource Organization (NRO) ------------------ The announcement is available at: https://www.nro.net/aso-ac-delivers-recommended-draft-rir-governance-docume… ------------------ ASO AC delivers Recommended Draft RIR Governance Document to NRO EC The Number Resource Organization Executive Council (NRO EC) is pleased to announce that the Number Resource Organization Number Council (NRO NC), which fulfils the role of the Address Supporting Organization Address Council (ASO AC), has completed its work on version 3 of the RIR Governance Document. This work was undertaken by the ASO AC in response to the NRO EC’s request to review and update Internet Coordination Policy-2 (ICP-2): Criteria for Establishment of New Regional Internet Registries, and to support a strengthened governance framework for the Regional Internet Registry (RIR) system [1]. The resulting document, titled the ASO AC Recommended Draft RIR Governance Document, represents the outcome of the ASO AC’s work under this mandate. The ASO AC has now formally delivered this draft to the NRO EC for its consideration and responsibility for the document has now transitioned to the NRO EC. ---------------- Background ---------------- The review of ICP-2 has followed a staged and iterative process, with opportunities for participation from across the RIR and ICANN communities. The process began with a review of the existing ICP-2 document and the development of proposed principles to guide the updated governance framework. Community input was then sought on those principles through a questionnaire, with an ICANN Public Comment process conducted in parallel [2]. Feedback from the principles phase informed the first draft of the RIR Governance Document, which was published for consultation in Apr-May 2025 [3]. That consultation included engagement through RIR community mailing lists, webinars and online sessions, RIR meetings, ICANN community engagement, and an ICANN Public Comment process. The feedback received informed the development of version 2 of the document, which was published with supporting materials, including a redline and summary rationale of changes. A second consultation on version 2 in Aug-Nov 2025 provided a further opportunity for the RIR and ICANN communities to review the revised draft and provide input [4]. Following the second consultation, the ASO AC continued engagement with RIR and ICANN communities, including at ICANN 85 in Mar 2026 [5]. Feedback from these consultations and engagement activities, together with subsequent review and drafting work by the ASO AC, informed the ASO AC Recommended Draft now delivered to the NRO EC. ---------------- Next steps ---------------- The NRO EC will now review the ASO AC Recommended Draft RIR Governance Document and progress the next stages of the process, including coordination with ICANN and the RIRs, and the pathway toward a final version. An updated timeline will be published soon to guide these final stages. The ASO AC Recommended Draft RIR Governance Document and supporting materials — including a rationale document summarizing key changes from version 2, and a comparison/redline document showing changes from version 2 — will be published separately in accordance with this timeline. Any future opportunities for community input will be communicated by the NRO EC. Further information on the next stages, including relevant timelines and processes, will be shared in due course. ---------------- Acknowledgement ---------------- The NRO EC thanks the ASO AC, including its Drafting Team, for its work in completing the ASO AC Recommended Draft RIR Governance Document. The NRO EC also thanks the RIR and ICANN communities for their participation throughout the ICP-2 review process. Contributions through the principles questionnaire, community consultations, RIR and ICANN engagement sessions, mailing lists, webinars, and ICANN Public Comment processes have been important to the development of the document. NRO Executive Council ---------------- [1] https://www.icann.org/resources/pages/new-rirs-criteria-2012-02-25-en [2] https://www.nro.net/policy/internet-coordination-policy-2/icp-2-principles-… [3] https://www.nro.net/consultation-on-draft-governance-document-for-the-recog… [4] https://www.nro.net/consultation-on-the-second-draft-of-the-governance-docu… [5] https://www.nro.net/aso-ac-participation-in-icann-85/ -- Kind regards, Ulka Athale Community Development Manager RIPE NCC www.ripe.net

1 0

The RIPE Labs article competition for RIPE 93 is open
by Alun Davies 23 Jul '26

23 Jul '26

Dear colleagues, The RIPE Labs article competition is back! Every RIPE Meeting introduces the community to new voices and fresh faces, and the article competition is one of the ways we help make this happen. If you have an idea for an article that would be of value to the community, we want to hear from you. The winning author will receive free tickets, travel and accommodation for the upcoming meeting in Sofia, Bulgaria this October Entries close on 2 September, and you can find everything else you need to know, including the submission guidelines, here: https://labs.ripe.net/competitions/ripe-labs-article-competition-ripe-93/ We look forward to reading your submissions. Good luck! Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

New on RIPE Labs: What's ARP Got to Do with It?
by Alun Davies 23 Jul '26

23 Jul '26

Dear colleagues, Following up on his recent RIPE Labs article, A Farewell to ARPs, Remco van Mook takes a closer look at the role ARP plays in today's IPv4 Internet, and why it has become such a central part of the discussion around IPv6-only networks: https://labs.ripe.net/author/remco-van-mook/whats-arp-got-to-do-with-it/ Comments and feedback are very welcome as always! Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

New on RIPE Labs: Beyond Origin Validation - Four Classes of Routing Attack Nobody Is Validating
by Alun Davies 21 Jul '26

21 Jul '26

Dear colleagues, Antonio Prado and colleagues revisit fifteen years of routing security research and argue that, while origin validation has made real progress, four major classes of routing attack remain outside the scope of cryptographic validation: https://labs.ripe.net/author/antonio-prado/beyond-origin-validation-four-cl… Comments and feedback are very welcome as always! Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

RIPE NCC Strategy 2027-31 Published
by Hans Petter Holen 13 Jul '26

13 Jul '26

Dear colleagues, The RIPE NCC Strategy 2027-31 is now available. The document has been approved by the RIPE NCC Executive Board with input from our membership and the community. This is the second five-year strategy that the RIPE NCC has published, with our previous strategy covering the years 2022-26. This strategy builds upon our existing vision, mission and values and sets the long-term direction for the organisation. The document explains RIPE NCC’s role in the Internet ecosystem, sets out six strategic focus areas for the coming five-year period and the external factors that influence our operating environment. It also covers objectives at the service-level that will guide the development of our services and operations. The plans for each year will be available in detail in the Activity Plan and Budget. The document is available at: https://www.ripe.net/publications/docs/ripe-862/ Kind regards, Hans Petter Holen CEO and Managing Director RIPE NCC

1 0

New on RIPE Labs: A Farewell to ARPs: IPv4 Service on IPv6-Only Networks
by Alun Davies 13 Jul '26

13 Jul '26

Dear colleagues, This new article from Remco van Mook explores an IETF proposal that would allow IPv4 to operate over IPv6-only infrastructure without ARP, IPv4 subnets, tunnelling or translation: https://labs.ripe.net/author/remco-van-mook/a-farewell-to-arps-ipv4-service… Comments and feedback are very welcome as always! Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0