IETF 125: Source Packet Routing in Networking (SPRING) 2026-03-20 06:00

Why It Matters

Decisions and community engagement here determine the security posture and operational interoperability of SRv6 deployments; timely feedback is needed to finalize specs that carriers will rely on. Low participation risks delaying standards that have cross-WG dependencies and real-world deployment impact.

Summary

At IETF 125 the SPRING working group reviewed document progress, noting two drafts (circuit-style SR policy and distributed SRv6 locator by DHCP) moved to the RFC editor and another on resource awareness submitted to the ISG. Chairs emphasized a lagging level of mailing-list participation—especially on a long-running SRv6 security draft that has seen minimal review—and urged members to contribute comments or risk reassigning authors. The meeting also featured a technical proposal from Huawei on a unified 128-bit SRv6 path-segment identifier and three flag-signalling options (dedicated P-flag, generic flag, and no-flag), with discussion of trade-offs around implementation simplicity, bit-space consumption, and extensibility. Next steps include soliciting more WG feedback, updating the security draft, and continuing design debate on the SRv6 PSID flag mechanism.

Original Description

Source Packet Routing in Networking (SPRING) meeting session at IETF 125

2026-03-20 06:00

https://datatracker.ietf.org/group/spring/about/