RFC 9571: Extension of RFC 6374-Based Performance Measurement Using Synonymous Flow Labels
In plain English — editorial summary, not part of the RFC
RFC 6374 describes methods of making loss and delay measurements on Label Switched Paths (LSPs) primarily as they are used in MPLS Transport Profile (MPLS-TP) networks. This document describes a method of extending the performance measurements (specified in RFC 6374) from flows carried over MPLS-TP to flows carried over generic MPLS LSPs. In particular, it extends the technique to allow loss and delay measurements to be made on multipoint-to-point LSPs and introduces some additional techniques to allow more sophisticated measurements to be made in both MPLS-TP and generic MPLS networks.
Document record
- Document ID
- RFC9571
- Published
- May 2024
- Authors
- S. Bryant; G. Swallow; M. Chen; G. Fioccola; G. Mirsky
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 18
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9570Deprecating the Use of Router Alert in LSP PingCurrent
May 2024
- RFC 9572Updates to EVPN Broadcast, Unknown Unicast, or Multicast (BUM) ProceduresCurrent
May 2024
- RFC 9573MVPN/EVPN Tunnel Aggregation with Common LabelsCurrent
May 2024
- RFC 9568Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6Current
April 2024
- RFC 9574Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs)Current
May 2024
- RFC 9566Deterministic Networking (DetNet) Packet Replication, Elimination, and Ordering Functions (PREOF) via MPLS over UDP/IPCurrent
April 2024
- RFC 9587YANG Data Model for OSPFv3 Extended Link State Advertisements (LSAs)Current
June 2024
- RFC 9552Distribution of Link-State and Traffic Engineering Information Using BGPCurrent
December 2023
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?