- ripe-list - mailman.ripe.net

The RIPE Chair Team Reports - October 2025
by Mirjam Kuehne 10 Oct '25

10 Oct '25

Dear colleagues, With RIPE 91 around the corner, we flag some tweaks to the schedule, a new submission system, some interesting BoF sessions, and more. We also present our revamped fellowship programme, policy updates, and highlights from recent and upcoming industry events. You can find more details in our new RIPE Labs article: https://labs.ripe.net/author/mirjam_kuhne/the-ripe-chair-team-reports-octob… Kind regards, Mirjam Kühne RIPE Chair

1 0

New on the RIPE Labs Podcast: Andrei Robachevsky on ICP-2 in Review
by Alun Davies 09 Oct '25

09 Oct '25

Dear colleagues, Ahead of a BoF session dedicated to this topic coming up at RIPE 91, Andrei Robachevsky joins us on the RIPE Labs podcast to talk about the ICP-2 review process. Whether this is a new topic to you, or you just want to hear Andrei's take on the principles and priorities driving the review of this foundational Internet governance document, you can see the full episode on RIPE Labs: https://labs.ripe.net/author/alun_davies/andrei-robachevsky-icp-2-in-review… Or jump right into the video on YouTube: https://www.youtube.com/watch?v=htcdXvkrVXo Best regards, Alun Davies RIPE Labs Editor

1 0

Applications for the RIPE Fellowship Are Now Open (RIPE 92 and RIPE 93)
by Laura Lorenzo de Gracia 09 Oct '25

09 Oct '25

Dear all, *Applications are now open for the RIPE Fellowship for RIPE 92 (Edinburgh, 18–22 May 2026) and RIPE 93 (Sofia, 26–30 October 2026).* The RIPE Fellowship helps new voices from across the RIPE NCC service region take part in the RIPE community. *This is the first time we are running the new version of the RIPE Fellowship*. The updated RIPE Fellowship introduces a structured learning approach and personalised coaching. Fellows receive coaching, training and full support to attend and engage in a RIPE Meeting. *Who Can Apply and How: * 1. You can apply if you are 18 or older, live in the RIPE NCC service region, and study or work in a field related to Internet coordination and operations (such as networking, routing, measurements, or governance). 2. You must also complete the RIPE 101 course and pass the RIPE Fellowship quiz. Returning Fellows are welcome to apply if they meet the criteria. After passing the quiz, you’ll receive an invitation to submit your application, just choose your preferred meeting (RIPE 92 or 93), select your learning track, and apply before 10 December 2025, 12:00 CET. Please spread the word in your networks and if this is for you, of course, apply!. Learn more and start your application at: https://www.ripe.net/fellowship If you have any questions, feel free to contact fellowship(a)ripe.net We look forward to welcoming new Fellows to RIPE 92 and RIPE 93! Kind regards, Laura Lorenzo on behalf of the RIPE Fellowship Team

1 0

beIN && RIPE NCC && Notorious Markets
by Alex de Joode 09 Oct '25

09 Oct '25

https://torrentfreak.com/bein-says-issues-at-ripe-ncc-help-piracy-as-a-serv… https://torrentfreak.com/images/USTR-2025-0018-0029-beIN_Miramax_2025-Notor… We had a nice presentation from beIN (rightsholder) at the Lisbon RIPE meeting, unfortunately it seems they are not very happy with the KYC procedure that RIPE NCC applies to their customers (I believe they mean the subsequent KYC for letting/renting (sub)resources). (from the article) “Poor governance and a non-existent know your customer” In the case of off-shore/bulletproof providers, beIN says that identifying the owner of an ASN using information held by RIPE NCC can prove impossible. “RIPE NCC requests its members or those who use RIPE NCC resources to provide accurate contact information. Some rogue providers abuse this system by posting false or incomplete information. This prevents rights owners and authorities from reaching them or successfully sending takedown notices,” beIN explains. Inaccurate information can include fake or unmonitored email addresses, false business addresses or shared locations with many tenants. This ultimately makes it impossible for beIN to identify the owners of off-shore hosting companies. If it’s unable to do that, targeting the operators of the PaaS platforms becomes impossible too. “In other words, the very concept of an offshore or bulletproof hosting provider seeks to rely on the ease by which this registration system can be misused through the provision of false or incomplete information,” the company adds. If RIPE NCC gets added to the Notorious Markets list, their Public Affairs and Regulatory team will be busy and as RIPE NCC is a Dutch and European association pressure from those directions cannot be ruled out (then change will happen whether or not the members agree (even as membership organisation the RIPE policies must be inline with the law)). The above statement of beIN does signal a important issue that not only facilitates copyright infringement but a larger enablement of criminal internet infrastructure, that can and is used for support for various nefarious activities. Renting ASN, IP blocks and not chancing to registration to the correct user makes it difficult to find the bad apples. Now the RIPE members can change the policies that deal with this themselves (I would guess this should be started in Bucarest) otherwise the likelyhood of RIPE NCC receiving a 'gatekeeper' assignment (as banks have in the financial industry) and the need for extra (expensive !) lawyers by the NCC will increase the membership contribution. (In NL Dutch banks have approx. 25% of their employees commited to this gatekeeper role) Cheers, Alex -- IDGARA | Alex de Joode | alex(a)idgara.nl | +31651108221

9 8

about poorly monitored contact addresses...
by Michael Richardson 08 Oct '25

08 Oct '25

Got this in reply to my email. I imagine many others are getting the same. Does this mean they are monitoring things better, or... worse? :-) NOC Belcenter <noc(a)belcenter.be> wrote: > [https://belcenter.biz/Mail/Production/top_freshdesk.png] > Dear Michael Richardson, > Thank you for contacting our services > We confirm that ticket #1000023585 has been opened. > You will be contacted as soon as possible by one of our agents. -- Michael Richardson <mcr+IETF(a)sandelman.ca> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide

1 0

Re: ripe-list Digest, Vol 168, Issue 2
by Petra.Zeidler＠dlr.de 08 Oct '25

08 Oct '25

Hi, Andrew Campling <andrew.campling(a)419.consulting> writes: > Irrespective of any view regarding rights holders, the lack of effective KYC procedures is also a problem in combating both malicious and illegal content Know Your Customer does require that someone IS their customer, right? Which in very many cases will not be the case for resource users and RIPE. In cases of someone using "fallow" resources without authorization by the formal resource holder, would you also blame the RIPE database for having incorrect info? Let me point out that even a "bulletproof" hoster will not beam their packets onto the Internet but will be connected to an uplink or uplinks, which ought to be readily traceable with a plain traceroute until you find the closest-to-them entity you can identify and that picks up their phones, which likely have a contract either with the hoster or their provider (and maybe even an acceptable use policy). Following that scavenger-hunt wise is sure more work than just looking it up in a phone book (RIR database), but the likelihood of finding entities whose customers the sought-after parties are is distinctly better. Kind regards, Petra Zeidler —————————————————————————— Deutsches Zentrum für Luft- und Raumfahrt e.V. (DLR) Deutsches Fernerkundungsdatenzentrum | DFD-INF | Oberpfaffenhofen, Münchener Str. 20 | 82234 Weßling Petra Zeidler Telefon +49 8153 28 4295 | Telefax +49 8153 28 1448 | petra.zeidler(a)dlr.de | http://www.dlr.de/eoc ----------------------------------------------------------------------

2 3

First RIPE Code of Conduct Survey
by Andrew McConachie 06 Oct '25

06 Oct '25

Dear all, The RIPE Code of Conduct Team has launched its first Code of Conduct survey to understand how safe people feel at RIPE meetings and how likely they are to report concerns. If you have a moment to answer five quick, anonymous questions - your input will shape what we improve next. We have more details on the background to this work in the RIPE Labs article: https://labs.ripe.net/author/amcconachie/announcing-the-first-ripe-code-of-… But if you want to dive straight into the survey, it's available at: https://forms.gle/fyp9eCzy7jLzdh2m9 Best regards, Andrew McConachie - on behalf of the RIPE Code of Conduct Team

1 0

NRO NC Election at RIPE 91
by Boris Duval 03 Oct '25

03 Oct '25

Dear colleagues, We would like to share some information ahead of the upcoming NRO NC election taking place during RIPE 91. The election will fill one seat for a three-year term starting in January 2026 and ending in December 2028. --------------- Nominees --------------- There are three nominees on the ballot: - Constanze Bürger - Alexander Timokhin - Tiago Felipe Goncalves You can view more information about the nominees at: https://www.ripe.net/community/nro-nc/nro-nc-nominations-october-2025/nomin… You can submit expressions of support for the nominees to nominations(a)ripe.net. These expressions of support will be published on the website. Details are available at: https://www.ripe.net/community/nro-nc/nro-nc-nominations-october-2025/expre… --------------- Voting --------------- The following criteria are applicable in order to vote in the NRO NC election: - You must have registered for RIPE 91 and to vote in the NRO NC election - You must check-in ahead of the voting registration deadline: 14:00 (UTC+3) on Tuesday, 21 October - You must have attended at least one of the previous eight RIPE Meetings You can read more about the NRO NC election process in ripe-813: https://www.ripe.net/publications/docs/ripe-813/ Please note that you must also check in (even if you are participating online) in order to receive an electronic ballot. Our system will automatically exclude all those who have not checked in for RIPE 91. We will inform those registered who are ineligible to vote. If you believe you are eligible to vote, you will be able to ask for a review and be able to provide relevant information. All eligible voters will receive a link to the online voting platform via email. Voting information is available at: https://www.ripe.net/community/nro-nc/nro-nc-nominations-october-2025/elect… --------------- Important Dates and Deadlines --------------- Registration to vote in the NRO NC election closes: 14:00 (UTC+3) on Tuesday, 21 October Deadline to check-in for RIPE 91 (online or onsite): 14:00 (UTC+3) on Tuesday, 21 October Voting opens: 17:00 (UTC+3) on Tuesday, 21 October Voting closes: 09:00 (UTC+3) on Friday, 24 October Results announced: During the Closing Plenary session of RIPE 91 on Friday, 24 October If you have any questions about the NRO NC election, please contact nominations(a)ripe.net. Kind regards, Boris Duval RIPE NCC

1 0

RIPE Labs Article Competition for RIPE 91 - Results
by Alun Davies 03 Oct '25

03 Oct '25

Dear colleagues, I'm pleased to announce that Yuriy Vykhnevych has been selected as winner of our latest competition for his article 'Keeping Network Sites Online During Blackouts' in which he provides important power management advice for network operators working under adverse conditions. Second prize this time went to Fredrik Lindeberg for his excellent article, 'End-to-End Encryption: Architecturally Necessary'. Our congratulations to both authors! We are very glad to be able to share their work on RIPE Labs and we look forward to seeing them in person at upcoming RIPE Meetings. You can find both articles and other competition entries here: https://labs.ripe.net/competitions/ripe-labs-article-competition-ripe-91/ Also, note that articles published after the close of our latest competition can already be marked for entry in our next one - so feel free to start writing for a chance to come join us in Edinburgh for RIPE 92. Kind regards, Alun Davies RIPE Labs Editor

1 0

Loss of RIPE Community Member Fearghas McKay
by Mirjam Kuehne 02 Oct '25

02 Oct '25

Dear colleagues, We were all very saddened yesterday to learn that Fearghas McKay had passed away while attending a conference. No doubt this will come as a shock to his family and those of us who knew him from his work in the community. Fearghas has been an active participant in the RIPE community for many years. He served as Chair of the EIX Working Group from 1998-2013, and has been a part of programme committees and steering groups for a number of Network Operator Groups and peering forums, including AfPIF, CAPIF and UKNOF, often taking the role of co-chair within these groups. He was also a RIPE Atlas Ambassador for several years, helping to introduce Internet measurements to network operators around the world. His contributions have helped shape the RIPE community and the interconnection world more broadly. We will miss his energy, his humour, and his friendship. On behalf of the RIPE community we wish to extend our condolences to Fearghas’s family and friends. Kind regards, Mirjam Kühne RIPE Chair

1 0