IETF director blocks STAMP over Pseudowires draft citing technical flaws

The blocking of the STAMP over Pseudowires draft prevents the formalization of performance monitoring tools essential for maintaining quality of service in complex streaming delivery networks. By flagging inconsistencies with RFC 8762 and RFC 9780, Fairhurst is enforcing strict interoperability and security standards that prevent fragmented implementations of network telemetry. For the streaming ecosystem, these technical hurdles delay the adoption of standardized latency and loss measurement across multi-protocol label switching environments. Watch for a revised Internet-Draft that addresses the specific UDP checksum and congestion control requirements to clear the IESG ballot.

STAMP (Simple Two-way Active Measurement Protocol) has become a foundational tool for network operators seeking standardized latency and packet-loss measurement across heterogeneous transport paths. The IETF's MPLS Working Group has advanced several STAMP-related drafts in parallel, including extensions for Segment Routing and MPLS-TP environments, reflecting broad operator demand for unified telemetry that spans pseudowire and label-switched-path architectures. The IETF datatracker shows the STAMP over PW draft entered IESG review in mid-2026 after years of working-group iteration, with the document referencing both RFC 8762 (STAMP base protocol) and RFC 9780 (STAMP extensions for Segment Routing) as normative dependencies. The blocking DISCUSS ballot from Gorry Fairhurst, who serves as Area Director for the Transport Area, signals that cross-area coordination on UDP transport semantics remains a gating issue for MPLS-layer telemetry standards. The ETSI updates statutes to formalize ICT and broadcasting standards coordination reflect a broader industry trend toward aligning these complex technical frameworks.

The congestion-control concern Fairhurst raised touches a long-standing IETF policy position on UDP-based protocols. RFC 8085, "UDP Usage Guidelines," which Fairhurst co-authored, establishes that UDP senders must implement congestion control or demonstrate that their traffic is congestion-safe, a requirement that has historically slowed approval of UDP-based measurement protocols. STAMP's base specification (RFC 8762) addressed this by recommending that reflectors and session-senders operate within controlled domains, but extending STAMP over pseudowires introduces new encapsulation scenarios where the original congestion-control assumptions may not hold. This tension between measurement utility and transport safety has been a recurring theme in IETF Transport Area reviews, and Fairhurst's ballot applies that framework consistently to the MPLS telemetry stack.

For streaming delivery networks, the practical stakes are significant. Content delivery operators and ISPs increasingly rely on active measurement to detect path degradation before it impacts viewer quality of experience. RFC 9780, published in early 2025, extended STAMP with optional TLVs for Segment Routing path identification, enabling operators to correlate measurement results with specific SR policies. Until the pseudowire extension clears IESG review, operators running MPLS-based backbones with pseudowire segments lack a standardized method to inject STAMP test packets across those tunnels, forcing reliance on proprietary or vendor-specific monitoring tools. The delay also affects interoperability testing between equipment vendors who have already implemented RFC 8762 and RFC 9780 support in their network operating systems.