- ripe-list - mailman.ripe.net

New on RIPE Labs: RootViz - New Root DNS Reachability Dashboard
by Alun Davies 11 Mar '26

11 Mar '26

Dear colleagues, In this new guest post from the team at SIDN Labs on RIPE Labs, Gioavane Moura presents RootViz - a new dashboard built on RIPE Atlas data that lets the community visualise real-time measurement results and explore how probes reach the Internet’s root DNS servers: https://labs.ripe.net/author/giovane_moura/rootviz-new-root-dns-reachabilit… Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

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

10 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

2 1

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

10 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

1 0

The RIPE Chair Team Reports - March 2026
by Mirjam Kuehne 10 Mar '26

10 Mar '26

Dear colleagues, In this new update on RIPE Labs, we report on preparations for RIPE 92, including programme planning, a new training course on public speaking, new opportunities to engage with the research community and more. We also list some recent and upcoming industry events we are participating in. https://labs.ripe.net/author/mirjam_kuhne/the-ripe-chair-team-reports-march… Kind regards, Mirjam Kühne and Anna Wilson RIPE Chair Team

1 0

Update on RIPE Meeting Childcare Service
by Meeting Mailbox 10 Mar '26

10 Mar '26

Dear all, In early January, we circulated a questionnaire to help us assess whether to continue offering childcare service at RIPE Meetings. While we appreciate those who took the time to respond, the number of responses was relatively low and did not clearly indicate strong or consistent demand across the wider meeting community. This reflects a broader trend we have observed over the past two years, where uptake of the childcare service has remained very low. Given the significant costs involved in providing the service, the current level of participation makes it difficult to sustain in its present format. At the same time, we recognise the importance of making RIPE Meetings accessible to participants with families. Rather than withdrawing support entirely, we will look into alternative ways to assist parents. For the upcoming meeting in Edinburgh, we will share a list of local childcare providers that families can contact and arrange directly, according to their individual needs and preferences. We will continue to review this topic and explore whether a different model or revised criteria could make an organised service viable in the future. Thank you to everyone who took the time to provide feedback. If you have further input you would like us to consider, please feel free to get in touch. Kind regards, The RIPE Meeting Organisation Team

1 0

ICANN 85 and NRO NC
by constanze buerger 09 Mar '26

09 Mar '26

Dear colleagues, ICANN 85 is currently taking place in Mumbai. At ICANN 85, Hervé Clément, Andrei Robachevsky and I are bringing feedback from the RIPE community to review of ICP-2 as members of the NRO Number Council. The NRO NC has been presenting its work to various ICANN constituencies, and many of the sessions allow for hybrid participation. Our focus is simple: making sure the framework for the Regional Internet Registries remains technically robust, operationally resilient, and fit for the needs of the Internet community. We’ll share more updates and discuss progress with the community at RIPE 92. Best regards Constanze

1 0

Solidarity with Members and Network Operators
by Hans Petter Holen 05 Mar '26

05 Mar '26

Dear colleagues, We would like to express our solidarity with the network operators who are currently working hard to maintain Internet access despite the effects of escalating violence in the Middle East. We recognise that many RIPE NCC members and colleagues are directly affected by the situation, and our thoughts are with those experiencing uncertainty, loss and disruption as events continue to unfold. We remain committed to keeping our members operational and continue to provide undisrupted registry services to all those affected. For RIPE NCC members who may be experiencing difficulties as a result of the conflict, we would like to remind you that the payment extension form is available to you. Members who anticipate challenges meeting the payment deadlines for this year’s invoices can request additional time through the form: https://www.ripe.net/participate/forms/apply/payment-extension-form/ As a membership organisation, we have close ties with many network operators in our Middle East service region. We also recognise that members of our own staff and RIPE community are affected by the situation, and we stand with everyone facing hardship during this time. We will continue to focus on supporting our members, community and maintaining the services that underpin the operation of the Internet. Kind regards, Hans Petter Holen Managing Director and CEO RIPE NCC

1 0

New on RIPE Labs: A Day in the Life of RIPE Atlas
by Alun Davies 03 Mar '26

03 Mar '26

Dear colleagues, What does a typical day on RIPE Atlas look like? In this new article, researchers from across the community analyse a 24-hour snapshot - nearly 200,000 measurements generating billions of results - to show how RIPE Atlas works in practice: https://labs.ripe.net/author/yevheniya-nosyk/a-day-in-the-life-of-ripe-atla… Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

New on RIPE Labs: Ukraine as a Laboratory of Internet Resilience
by Alun Davies 25 Feb '26

25 Feb '26

Dear colleagues, On the fourth anniversary of the full-scale invasion of Ukraine, Eliza Rohotska and Solomiia Yaremenko reflect on what Internet resilience means in practice and what it takes to keep networks running under sustained damage to infrastructure. You can read their article now on RIPE Labs: https://labs.ripe.net/author/eliza-rohotska/ukraine-as-a-laboratory-of-inte… Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

SR-MPLS traffic engineering Survey
by Dekinder Florian 24 Feb '26

24 Feb '26

Hello community, I’m Ph. D. Student at University de Liège, Belgium, and I’m conducting a survey as part of my researches on Segment Routing (SR) traffic engineering practices among network operators. We have a technique, called ArEST, allowing us to discriminate SR-MPLS and regular MPLS traffic. See https://orbi.uliege.be/bitstream/2268/337150/1/paper.pdf and our Git https://gitlab.uliege.be/segment-routing. If you are involved in the management of SR in your network, I would greatly appreciate your input. The survey should take no more than 5 minutes to complete. Link to the survey<https://docs.google.com/forms/d/e/1FAIpQLSc0vz9hX5VF_Ii2bprgC1neZwVnaA5tGS3…> Best regards, Florian Dekinder Université de Liège

1 0