Skip to main content

You're viewing an archived page. It is no longer being updated.

RIPE 80

Date: 14 May 2020, 11:00 - 11:45 (UTC+2)
Chairs: Job Snijders and Paul Hoogsteder
Scribe: Suzanne Taylor
Status: Approved

Opening / Welcome / Agenda

Working Group Chairs Job Snijders and Paul Hoogsteder opened the meeting and welcomed everyone to the online session.

Job noted that the presentations were pre-recorded to ensure they could stick to the tight agenda, as they had less time than usual for the session.

Job presented a poll question (using the Zoom interface) to seek consensus for approval of the working group’s draft minutes from RIPE 79.

DBTF Requests Input from Routing WG on what to do with RPSL

Nick Hilliard

The presentation is available online:
https://ripe80.ripe.net/presentations/43-inex-ripe-routing-wg-online-2020-05-14.pdf

George Michaelson, APNIC, said that the stats on “objects used” were fascinating and that, given ROA, it was hard to believe that a route object was needed. Nick responded that this would possibly need to be resolved in the future, when it might be possible to move away from using route objects, but that currently it would be inadvisable to do so as so many route objects were being used.     

Kostas Zorbadelos, CANAL+ Telecom, asked whether there was a proposal to remove the unused parts. Nick responded that there was no proposal yet and that this was a call for discussion for the time being.

Job added that, as a network operator, he recognised that there were object types used every day and others that weren’t used as much, and it was worth having a community discussion about what was being used and what could be improved.

There were no further questions or comments.

Update on Policy Proposal 2019-08 "RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space"

Massimiliano Stucchi, Melchior Aelmans, Martijn Schmidt

The presentation is available online:
https://ripe80.ripe.net/presentations/18-RIPE80-2019-08.pdf

A participant suggested the need for a signed assert for this kind of publication.

Randy Bush, IIJ and Arrcus, asked how to cryptographically validate the Slurm file. Massimiliano responded that so far there was no mechanism, but they could consider working on that in parallel at the IETF.

Kurt Kayser, German Federal Ministry of the Interior, asked whether the Slurm file was similar to handling Martians. Massimiliano answered that it contained them as well and that he could point Kurt to the proof-of-concept that they wrote so he could see how it produced the Slurm file, and that any request would be gladly received.

Job added that the proposal followed the RIPE Policy Development Process, which meant that the best way to provide feedback would be to join the Routing Working Group mailing list and contributing comments there.

There were no further questions or comments.

PeeringDB 'never_via_routeservers' Option

Johannes Moos

The presentation is available online:
https://ripe80.ripe.net/presentations/37-e-jmo-RIPE80_Never_via_route_servers_handout.pdf

Rüdiger Volk (no affiliation) said that it was useful to publish constraints for autonomous systems and that using such information (e.g. for suppressing routes) required that authorisation could be verified (ex. ASPA).

Simon Lockhart, Bogons Ltd, asked whether this would not be better placed as an attribute on an object in the RIPE Database. Johannes responded that you could put it there but putting it in PeeringDB would likely be a quicker option.

There were no further questions or comments.

RPKI Deployment Update

Ben Cox

The presentation is available online:
https://ripe80.ripe.net/presentations/36-Ben_Cox.pdf

Randy Bush, IIJ and Arrcus, commented that the number Ben used for “validating ASes” includes those getting it for free from upstreams, and asked what the real number of validating ASes was. Ben replied that he suspected that the real number was around 1,000.

Gordon Gidofalvy, KTH Royal Institute of Technology, asked whether Ben had taken a look at stub AS/transit AS non-validating/validating ratios and which was more common. Ben replied that he thought it was mostly stub networks doing origin validation.

There were no further questions or comments.

AOB

Job said he hoped that there would be more time for discussion at the next working group session, whatever form that would take. He thanked everyone for attending and concluded the session.