- ripe-list - mailman.ripe.net

Meet the NRO NC at RIPE 91
by herve.clement＠orange.com 17 Oct '25

17 Oct '25

Dear all, The RIPE NRO NC representatives (Andrei Robachevsky, Constanze Bürger and I) will be attending RIPE 91 in Bucharest next week. We would like to hear your feedback on the second version of the draft "RIR Governance Document" intended. The consultation on the document is open until 7 November 2025. We will present at the following sessions: Monday, 20 October, 18:00 EEST (UTC+3): BoF on ICP-2 https://ripe91.ripe.net/programme/meeting-plan/sessions/57/ Thursday, 23 October, 14:00 EEST (UTC+3): NRO NC Update in the Address Policy Working Group https://ripe91.ripe.net/programme/meeting-plan/sessions/43/ Thursday, 23 October, 16:00 EEST (UTC+3): Reporting back on the ICP-2 BoF in the RIPE Community Plenary https://ripe91.ripe.net/programme/meeting-plan/sessions/46/ Hallway chats: We will be available near the Meet & Greet desk from Tuesday, 21 October until Thursday, 23 October everyday during the lunch break from 13:30 - 14:00 EEST/UTC+3. Looking forward to seeing you in Bucharest! Constanze, Andrei and Hervé ____________________________________________________________________________________________________________ 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 Response on KYC challenges and beIN article
by Gabor de Wit 14 Oct '25

14 Oct '25

Dear colleagues, Apologies for the delayed response concerning the RIPE NCC's KYC processes referenced in the mail thread around a beIN article and references to Notorious Markets here <https://mailman.ripe.net/archives/list/ripe-list@ripe.net/thread/AR54WJAJNM…> – RIPE 91 preparations have been keeping us busy! In answer to Michele: our first impression is largely in line with what Nick and others have already said in the thread – the report seems to mix up the RIPE NCC’s due diligence processes and responsibilities with entities that are either involved on the user or content layer of the Internet (e.g. ISPs)[1] or are sponsoring End Users, in which case the RIPE NCC only has a contractual agreement with the sponsoring organization. It’s understandable that people use ‘KYC’ as shorthand for making sure bad actors can’t hide. However, the Internet registry system is substantively different from (e.g.) the financial services industry where this term originates. The RIPE Database does not hold information about individual users or website content. It holds information about who is responsible for IP addresses and AS Numbers, and parts of this information is curated by the holders of these resources themselves. Our job is to ensure that the RIPE NCC-curated part of this data is correct and that the right people can be contacted if needed (e.g. abuse-c contacts). Of course, this is a complex issue and we invite all stakeholders with concerns to raise them within the RIPE community, both on the appropriate WG mailing lists and at the RIPE Meeting next week. For our part, I will see to it that we prepare some material that clearly outlines what we currently do in terms of due diligence checks and where responsibility for maintaining data rests under the existing framework. This can form the basis for any constructive discussions stakeholders wish to have on this topic moving forward. We will therefore aim to publish something on RIPE Labs after RIPE 91, which can be informed by any discussions we have at the meeting. Radu, I've also asked someone from my team to contact you as I would like to understand what went wrong with your referenced tickets. -- Gabor de Wit Chief Registry Officer | RIPE NCC ---------------------------------------------- [1] For more information on the differences between the various responsibilities in Internet governance, have a look at an excellent RIPE Labs article here: https://labs.ripe.net/author/anastasiya-pak/hisham-ibrahim-the-internet-is-…

1 0

Programme Committee Elections @ RIPE 91
by Brian Nisbet 14 Oct '25

14 Oct '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 Autumn 2025 who will be elected by the RIPE community at RIPE 91. 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 today, Tuesday, 14 October, until Tuesday, 21 October, 15:30 (EEST/UTC+3). 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, 21 October at 15:30 (EEST/UTC+3) and publish the biographies on the RIPE Meeting web site. The RIPE PC online voting system will be open from Tuesday, 21 October, 16:00 (EEST/UTC+3) until Thursday, 23 October, 17:00 (EEST/UTC+3), 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, 24 October, during the closing plenary session. Important Dates and Deadlines ----------------------------- Nominations Open: Tuesday, 14 October Nominations Close: Tuesday, 21 October, 15:30 (EEST/UTC+3) Voting Begins: Tuesday, 21 October, 16:00 (EEST/UTC+3) Voting Closes: Thursday, 23 October, 17:00 (EEST/UTC+3) Results Announced: Friday, 24 October, 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 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

Elections at MANRS
by Alejandro Fernández-Cernuda 13 Oct '25

13 Oct '25

Dear members of the RIPE mailing list, *MANRS* is about to hold elections for the renewal of the three seats of the Steering Committee that will become vacant at the end of this year. If you are planning to run for election, *you can submit your nomination until next Friday, 17 October 2025, at 23:59 UTC*. We have four candidates so far. The higher the number of nominations, the better chances we will have to have a more diverse Steering Committee, which will benefit us all. *Remember that everyone is eligible to serve on the Steering Committee— MANRS participation is not required.* Once the nomination process is complete, we will move to the next step: voting. *MANRS participants will vote online from 28 – 30 October 2025*. For further information, please refer to this post: *https://manrs.org/2025/09/nominations-open-for-manrs-steering-committee-3/ <https://manrs.org/2025/09/nominations-open-for-manrs-steering-committee-3/>* If you are interested in meeting us, you will have a large MANRS delegation attending the RIPE 91 meeting in Bucharest next week. Thank you and see you very soon! • • • • Alejandro Fernández-Cernuda Díaz Director of Engagement, Internet Integrity Program Global Cyber Alliance afcernuda(a)globalcyberalliance.org +32 28823050 GCA Brussels Rond Point Schuman 6 1040 Brussels Belgium [image: GCA Website] <https://csvv404.na1.hs-sales-engage.com/Ctc/WZ+23284/csVV404/JkM2-6qcW6N1vH…> [image: GCA Twitter] <https://csvv404.na1.hs-sales-engage.com/Ctc/WZ+23284/csVV404/JkM2-6qcW6N1vH…> [image: GCA Facebook] <https://www.facebook.com/GlobalCyberAlliance/> [image: GCA LinkedIn] <https://csvv404.na1.hs-sales-engage.com/Ctc/WZ+23284/csVV404/Jl22-6qcW7lCdL…> [image: GCA YouTube] <https://csvv404.na1.hs-sales-engage.com/Ctc/WZ+23284/csVV404/Jl22-6qcW7lCdL…> [image: GCA GitHub] <https://csvv404.na1.hs-sales-engage.com/Ctc/WZ+23284/csVV404/JkM2-6qcW6N1vH…> [image: GCA Email Signup] <https://csvv404.na1.hs-sales-engage.com/Ctc/WZ+23284/csVV404/JkM2-6qcW6N1vH…> [image: GCA Instagram] <https://csvv404.na1.hs-sales-engage.com/Ctc/WZ+23284/csVV404/JkM2-6qcW6N1vH…> [image: GCA Forums] <https://csvv404.na1.hs-sales-engage.com/Ctc/WZ+23284/csVV404/JkM2-6qcW6N1vH…> GCA takes your privacy seriously. To review our privacy policy, please click here <https://www.globalcyberalliance.org/privacy-policy/>.

1 0

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