IETF 125: Inter-Domain Routing (IDR) 2026-03-20 01:00

IETF
IETFMar 20, 2026

Why It Matters

These decisions affect operator deployments and interoperability by shaping how SR policies are encoded and allocated in production, and improved cross-group coordination should reduce deployment delays and prevent inconsistent early-use of registry values.

Summary

At IETF 125’s Inter-Domain Routing session, chairs reviewed working-group status and flagged problems with early allocations and coordination that delayed several drafts, notably NRP and SRv6-related work. They emphasized that experimental or early allocation values must only be used with IANA-assigned or draft-specific registries and urged authors to include cross-working-group sections to align with SPRING and other efforts. The meeting proceeded to technical presentations, including a BGP-SR policy metric extension draft that proposes reusing existing metric code points, adds a segment-list sub-TLV registry, and clarifies metric semantics and usage based on reviewer feedback. Several drafts are near adoption but timing depends on shepherd reviews, registry decisions, and better linkage to related workstreams.

Original Description

Inter-Domain Routing (IDR) meeting session at IETF 125
2026-03-20 01:00

Comments

Want to join the conversation?

Loading comments...