Plenary - Main Room (Mon, 16:00)

The NETCONF API has been specified for 20 years and it's time to look at all the zoo of protocols, formats and schemas available for use. Is it mature? Can we rely on it? Is it efficient? Have you read the fine print?

Large R&E networks are full of partial signals: traceroutes show path changes, OWAMP tests show delay and loss, iperf3 shows throughput - each running at its own cadence, inspected with its own tool. When a data transfer slows down, the real question is simple but hard to answer fast: did the path change, and does that explain it?

We built a routing-aware incident triage tool on top of perfSONAR data from the WLCG/OSG mesh (170+ sites, ~4M tests/day). For each monitored corridor (source-destin…

In the past few months, we have built a successor to the classic RISwhois service. In this talk, I briefly discuss the history of RISwhois, and then detail the improvements we have made in RISwhois-rs, and end by looking to the potential future improvements to RISwhois-rs.

RIPE RIS has been collecting BGP data for more than 25 years. We maintain a
long-term archive, and that comes with its own challenges: the volume only grows,
and noisy or low-value data stays with us forever. In recent years, we have
therefore been quite selective about accepting new peering sessions. We now want
to reconsider that approach: collecting data from more peers, while keeping the
long-term volume manageable.

In this talk, I will recap the data RIS has been collecting and show some…

Traceroute is an important Internet measurement tool used to infer the Internet’s topology and to identify middleboxes. It relies on network devices decrementing the Time to Live (TTL) in IP packet headers by one at each hop and sending Internet Control Message Protocol (ICMP) Time Exceeded error messages if the TTL reaches zero. However, we show that TTL jumps exist on the Internet: some devices rewrite the TTL, often to larger value of up to 255. These rewrites hide the remaining path from tr…