- ripe-list - mailman.ripe.net

Last chance to enter: RIPE Labs competition RIPE 92
by Alun Davies 27 Mar '26

27 Mar '26

Dear colleagues, There's one week left to enter the RIPE Labs article competition for a chance to win free travel, tickets and accommodation for RIPE 92 in Edinburgh this May. You can find full details and see the current entries here: https://labs.ripe.net/competitions/ripe-labs-article-competition-ripe-92/ Looking forward to your submissions! Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

RIPE92 Second Call for Presentations
by Massimiliano Stucchi 26 Mar '26

26 Mar '26

Dear colleagues, The RIPE Programme Committee (PC) is now opening the second call for presentations seeking for content proposals from the RIPE community for the plenary sessions, lightning talks and BoFs. RIPE92 will be a hybrid meeting so both in-person and virtual presentations would be accepted and encouraged. The deadline to submit a presentation proposal is 9th of April 2026. Proposals submitted after this date will only be considered if there are still time slots available. Already submitted presentations which have not received an acceptance or rejection notification yet are still under consideration. You can read more about the CfP and submit your proposal at: https://pretalx.ripe.net/ripe-92/cfp More about the RIPE92 Meeting: https://ripe92.ripe.net/ Regards, Massimiliano Stucchi (On Behalf of the RIPE Programme Committee)

1 0

New on RIPE Labs: Make This One Change to Prevent Routing Loops in Your Network
by Alun Davies 26 Mar '26

26 Mar '26

Dear colleagues, In this new RIPE Labs article, Maynard Koch and colleagues talk about the trouble with routing loops, how often they occur, and how a simple change can help prevent them: https://labs.ripe.net/author/mkoch/make-this-one-change-to-prevent-routing-… Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

First RIPE Code of Conduct Survey
by Andrew McConachie 24 Mar '26

24 Mar '26

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 2

Call for Topics for RIPE 92 Community Plenary
by Mirjam Kuehne 20 Mar '26

20 Mar '26

Dear colleagues, The RIPE 92 Community Plenary will take place on Thursday, 21 May 2026 at 16:00 local Edinburgh 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

Selected Fellows Announced for RIPE 92 and RIPE 93
by Michela Galante 18 Mar '26

18 Mar '26

Dear all, The RIPE NCC is pleased to announce the selected fellows for RIPE 92 and RIPE 93: https://www.ripe.net/about-us/news/selected-fellows-announced-for-ripe-92-a… Congratulations to all the selected fellows! We would also like to thank the community volunteers who dedicated their time and expertise to reviewing applications, supporting the selection process, and are now coaching the fellows. This is the first time that we are running the new version of the RIPE Fellowship which introduces a structured learning approach that adapts to the fellows’ interests, including personalised coaching and full support to attend and engage in a RIPE Meeting. You can read more about the new RIPE Fellowship here: https://www.ripe.net/community/community-initiatives/ripe-fellowship/ If you have any questions, feel free to contact fellowship(a)ripe.net Best regards, Michela Galante on behalf of the RIPE Fellowship Team

1 0

Updated RIPE Programme Committee Charter published as ripe-853
by Mirjam Kuehne 13 Mar '26

13 Mar '26

Dear colleagues, The updated RIPE Programme Committee Charter is now published as ripe-853: https://www.ripe.net/publications/docs/ripe-853/ Kind regards, Mirjam Kühne

1 0

PI IPv4 and PI IPv6 IXP assignments
by info＠rudaki-ix.net 12 Mar '26

12 Mar '26

Comments on RIPE NCC new Payment Scheme. The Internet is a critical infrastructure on which life depends, especially during wartime. I personally had to make sure of this in Ukraine. Reliable operation of the network depends on many factors, it is not only the availability of power or fuel in generators, but also the accessibility of networks (providers and operators) to traffic exchange points, especially to independent traffic exchange networks. Most traffic exchange points (especially small regional ones) are critically important and greatly improve communication. But with a small number of participants (up to 100 exchange participants), the financial costs of maintaining the IXP are quite significant, most regional traffic exchange points in Ukraine have practically no profits, or their financial income is so low that the introduction of a new payment scheme for resources such as RI is a big problem. Especially when there is war in the country, and paying 1000 euros for PI IPv4 and IPv6 IXP assignments is a knife in the back. I am the founder of the traffic exchange point in Ukraine: RUDAKi-IX. The creation of IXP from the very beginning did not bring me significant profit, practically one of the lowest port prices is achieved by minimal infrastructure costs and support for the exchange. Most participants are in a state of war and do not have the means to pay membership fees, but now the burden of paying for PI objects must fall on their shoulders, for a moment these are two PI IPv4 + PI IPv6 objects. My personal opinion is negative towards such a significant increase in the cost of these resources. It is necessary to allocate IXP resources from other PI resources and prevent their increase in cost for end users of RIPE NCC. I propose to leave the cost for IXP at EUR 75. --------------------------------------------------------------------------------------------------- Зауваження до нової Схеми оплати RIPE NCC. Інтернет - це критична інфраструктура від роботи якої залежить життя, особливо під час війни. Мені особисто довелось в цьому впевнитися в Україні. Надійна робота мережі залежить від багатьох факторів, це не лише наявність живлення чи пального в генераторах а і доспутність мереж (провайдерів та оперторів) до точок обміну трафіку, особливо до незалежних мереж обміну трафіку. Більшість точок обміну трафіку (особливо невеликі регіональні) є критично важливими і дуже покращують зв'язок. Але з невеликою кількістю учасників (до 100 учасників біржі) фінансові витрати на підтримання роботи ІХР є досить значними, більшість регіональних точок обміну трафіку в Україні практично не мають прибутків, або їх фінансові надходження наскільки низьке що запровадження новой схеми оплати за ресурси типу РІ - це велика проблема. Особливо коли в країні війна, а сплата 1000 євро за PI IPv4 and IPv6 IXP assignments - це ніж в спину. Я засновник точки обміну трафіком в Україні: RUDAKi-IX. Створення ІХР із самого початку не мало на мені отримання значного прибутку, практично одна з найменшої ціни порту досягається мінимальними витрати на інфраструктуру і підтримку роботи біржи. Більшість учасників перебувають вкладній війській ситуації і не мають коштів сплачквати членські внески, але тепер на їх плечі має лягти тягар із сплати за обєкти РІ, на хвилинку це два об'єкти PI IPv4 + PI IPv6. Моя особиста думка має негатив до такої значного підвищення вартості за дані ресурси. Потрібно розподіляти ресурси ІХР від інших ресурсів РІ і не допустити їх збільшення вартості для кінцевих користуваців RIPE NCC. Я пропоную залишити для ІХР вартість на рівні EUR 75. -- Best regards, . Rudakov Igor mailto:info@rudaki-ix.net

4 3

Discussion about Charging Scheme to RIPE NCC Members List
by Mirjam Kuehne 12 Mar '26

12 Mar '26

Dear colleagues, Please note that conversations related to the RIPE NCC budget and charging scheme should take place on the RIPE NCC members list and not on the RIPE community list: https://www.ripe.net/membership/mail/ripe-ncc-mailing-lists/members-discuss/ Kind regards, Mirjam Kühne (RIPE Chair and List Moderator)

1 0

Concerns Regarding Proposed Increased Fees for PI Resources
by Viktoriia Opanasiuk 12 Mar '26

12 Mar '26

Dear Members of the Working group, I am writing to express my concern regarding the proposals under consideration for the future RIPE NCC charging scheme, specifically the potential increase in fees for PI Assignment. Any changes to the charging scheme should take regional characteristics into account. Different countries within the RIPE service region have diverse network structures, operator sizes, and resource usage patterns. In Ukraine, PI resources are widely used to ensure network resilience and independence, and the number of organizations using PI blocks significantly exceeds the number of LIRs. This widespread use of PI addressing contributes to a decentralized, robust, and distributed Internet infrastructure. A disproportionate increase in fees for PI blocks, as currently proposed in the consultations, would place a significant financial burden on small ISPs, regional networks, and other infrastructure organizations, many of which are already operating under serious economic pressure during long-term war. This could have several unintended consequences: - Higher fees may discourage the use of PI addressing for multihoming, potentially affecting network resilience and independence. - Additional costs may strain budgets, limiting the ability to maintain robust network architectures. - PI resources are essential for redundancy and rapid traffic rerouting in the event of failures; increasing their cost could unintentionally reduce the adoption of these practices. I therefore urge the Task Force to maintain annual fees for PI resources at the current level, avoiding disproportionate financial burden on operators that rely on these resources for critical connectivity. I appreciate the efforts of the Task Force and the transparency of the ongoing consultation process, and hope that the regional specifics of Ukraine will be duly considered. -- Kind regards, Regional Director Viner Telecom ISP

2 1