RFC 6374: Packet Loss and Delay Measurement for MPLS Networks
Many service provider service level agreements (SLAs) depend on the ability to measure and monitor performance metrics for packet loss and one-way and two-way…
Read RFC 6374 on the RFC Editor
Outgoing relationships (24 related RFCs)
Incoming relationships (24 related RFCs)
- Updated by — RFC 7214: Moving Generic Associated Channel (G-ACh) IANA Registries to a New Registry
- Normatively referenced by — RFC 6375: A Packet Loss and Delay Measurement Profile for MPLS-Based Transport Networks
- Normatively referenced by — RFC 6669: An Overview of the Operations, Administration, and Maintenance (OAM) Toolset for MPLS-Based Transport Networks
- Normatively referenced by — RFC 7487: Configuration of Proactive Operations, Administration, and Maintenance (OAM) Functions for MPLS-Based Transport Networks Using RSVP-TE
- Normatively referenced by — RFC 7190: Use of Multipath with MPLS and MPLS Transport Profile (MPLS-TP)
- Normatively referenced by — RFC 9779: Performance Measurement for Segment Routing Networks with the MPLS Data Plane
- Normatively referenced by — RFC 9974: Operations, Administration, and Maintenance (OAM) Requirements for the Bit Index Explicit Replication (BIER) Layer
- Informatively referenced by — RFC 7799: Active and Passive Metrics and Methods (with Hybrid Types In-Between)
- Informatively referenced by — RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions
- Informatively referenced by — RFC 7276: An Overview of Operations, Administration, and Maintenance (OAM) Tools
- Informatively referenced by — RFC 9522: Overview and Principles of Internet Traffic Engineering
- Informatively referenced by — RFC 9551: Framework of Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet)
- Informatively referenced by — RFC 7456: Loss and Delay Measurement in Transparent Interconnection of Lots of Links (TRILL)
- Informatively referenced by — RFC 7810: IS-IS Traffic Engineering (TE) Metric Extensions
- Informatively referenced by — RFC 8877: Guidelines for Defining Packet Timestamps
- Informatively referenced by — RFC 6812: Cisco Service-Level Assurance Protocol
- Informatively referenced by — RFC 7212: MPLS Generic Associated Channel (G-ACh) Advertisement Protocol
- Informatively referenced by — RFC 8233: Extensions to the Path Computation Element Communication Protocol (PCEP) to Compute Service-Aware Label Switched Paths (LSPs)
- Informatively referenced by — RFC 8372: MPLS Flow Identification Considerations
- Informatively referenced by — RFC 8924: Service Function Chaining (SFC) Operations, Administration, and Maintenance (OAM) Framework
- Informatively referenced by — RFC 8957: Synonymous Flow Label Framework
- Informatively referenced by — RFC 8169: Residence Time Measurement in MPLS Networks
- Informatively referenced by — RFC 9978: Bidirectional Forwarding Detection (BFD) Stability
- Informatively referenced by — RFC 10014: Guidelines for Characterizing the Term "OAM"