Connect Working Group Minutes RIPE 91

Date: Wednesday, 22 October 2025, 09:00 - 10:30 (UTC+3)
Chairs: Paul Hoogsteder, Stavros Konstantaras, Will van Gulik
Scribe: Jelena Ćosić
Status: Draft

1. Opening & Housekeeping

WG Chairs

Quick welcome by the co-chairs, since they had a packed agenda ahead.

2. PeeringDB Update

Leo Vegoda

The presentation is available at: https://ripe91.ripe.net/programme/meeting-plan/sessions/27/GJ98YB/

There were no questions or comments.

Stefano Servillo

The presentation is available at: https://ripe91.ripe.net/programme/meeting-plan/sessions/27/C3ZSGJ/

Radu-Adrian Feurdean (France IX) doesn’t agree that the best way to validate is using IRR data due to authenticity issues. He pointed out that for him RPKI is the most important one and that he doesn’t even check IRR data if origin is valid. He is still using IRR for AS path, hoping that ASPA will soon solve this as well.

Stefano replied that the issues of outdated and bloated AS-SETs will be solved once RPKI adoption reaches 100%, in the meantime the blindspots can be solved by doing the proposed validation.

Will van Gulik (RomandIX) suggested doing tests with smaller IXPs and he volunteered to be the first one.

Ben Cartwright-Cox shared an update that Cogent signed ARIN agreement, which means their space is RPKI capable. The news was well received in the room.

Mick O'Donovan (HEAnet) had a question on how network operators can be encouraged or persuaded to properly maintain their AS-SETs, given that they often become unwieldy and hard to manage. He asked if RIPE NCC could prod members on it, like they did in the past, while acknowledging that the community itself has to be better at managing AS-SETs.

To which Stavros and Stefano responded by adding that that’s still not enough.

Dave Phelan (APNIC) commented that most IXs at least use prefix count limits (often based on PeeringDB) to prevent issues from overly broad AS-SETs, and since the IRRd 4 update, RADb now rejects third-party entries that conflict with valid ROAs, helping keep data cleaner.

The last comment came from Rudiger Volk who mentioned that he had developed tools to help analyse and manage customer routing data quality, and he is considering reviving the project, potentially with IXP support. Stavros asked him to share the tool URLs on the mailing list, and Rudiger replied that they are not yet public but should become available once he sorts out access and hosting details.

4. European Interconnection Regulation - Proposals and Impacts

Mike Blanche

The presentation is available at: https://ripe91.ripe.net/programme/meeting-plan/sessions/27/FSUDM8/

First comment came from Alex de Joode (AMS-IX) who cited a recent US–EU trade agreement stating that the EU will not adopt or maintain network users fees, suggesting that this resolves the issue.

Tom Strickx (Cloudflare) suggested promoting awareness of the DNA and network usage fees at RIPE meetings, similar to efforts around RPKI. They emphasised that Korea’s regulation originally targeted ISP to ISP interconnections but has been misused to charge CAPs as well, creating a harmful regulatory environment that Europe should avoid.

Fredy Kuenzler (Init 7) clarified that their legal case with Swisscom is still ongoing at the federal administrative court and may conclude this year or next. A positive outcome was that it prompted a network upgrade from another operator, resolving packet loss issues. Once the current case is finished, they plan to address issues with another operator.

The last question came from Danko Jevtović (RNIDS) who asked how the EU Commission believes this regulation will actually benefit innovation, which is their main concern.

5. How far can you get with IX Route Servers?

Ben Cartwright-Cox

The presentation is available at: https://ripe91.ripe.net/programme/meeting-plan/sessions/27/ZRGKVK/#ben-cartwright-cox

Tom Strickx (Cloudflare) pointed to a large difference between the import and export sides and asked for an explanation of why this is happening, noting that it seems unusual. Ben replied that the discrepancy may be due to operators exporting but not importing routes, or simply poor configuration. Message to the IXPs in the room: check your RS config, pay attention to how your RS filter policy is generated.

6. The role of IXPs in South East Europe

Jelena Ćosić