RFC 5860: Requirements for Operations, Administration, and Maintenance (OAM) in MPLS Transport Networks

This document lists architectural and functional requirements for the Operations, Administration, and Maintenance of MPLS Transport Profile. These…

Read RFC 5860 on the RFC Editor

Outgoing relationships (7 related RFCs)

Normative reference — RFC 4379: Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures
Normative reference — RFC 5085: Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires
Normative reference — RFC 5654: Requirements of an MPLS Transport Profile
Normative reference — RFC 2679: A One-way Delay Metric for IPPM
Normative reference — RFC 2680: A One-way Packet Loss Metric for IPPM
Normative reference — RFC 2681: A Round-trip Delay Metric for IPPM
Informative reference — RFC 4377: Operations and Management (OAM) Requirements for Multi-Protocol Label Switched (MPLS) Networks

Incoming relationships (18 related RFCs)

Normatively referenced by — RFC 6371: Operations, Administration, and Maintenance Framework for MPLS-Based Transport Networks
Normatively referenced by — RFC 6428: Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport Profile
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 6373: MPLS Transport Profile (MPLS-TP) Control Plane Framework
Normatively referenced by — RFC 6435: MPLS Transport Profile Lock Instruct and Loopback Functions
Normatively referenced by — RFC 6670: The Reasons for Selecting a Single Solution for MPLS Transport Profile (MPLS-TP) Operations, Administration, and Maintenance (OAM)
Normatively referenced by — RFC 6671: Allocation of a Generic Associated Channel Type for ITU-T MPLS Transport Profile Operation, Maintenance, and Administration (MPLS-TP OAM)
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 7571: GMPLS RSVP-TE Extensions for Lock Instruct and Loopback
Informatively referenced by — RFC 5921: A Framework for MPLS in Transport Networks
Informatively referenced by — RFC 7276: An Overview of Operations, Administration, and Maintenance (OAM) Tools
Informatively referenced by — RFC 6426: MPLS On-Demand Connectivity Verification and Route Tracing
Informatively referenced by — RFC 7260: GMPLS RSVP-TE Extensions for Operations, Administration, and Maintenance (OAM) Configuration
Informatively referenced by — RFC 6905: Requirements for Operations, Administration, and Maintenance (OAM) in Transparent Interconnection of Lots of Links (TRILL)
Informatively referenced by — RFC 7325: MPLS Forwarding Compliance and Performance Requirements
Informatively referenced by — RFC 7167: A Framework for Point-to-Multipoint MPLS in Transport Networks
Informatively referenced by — RFC 9974: Operations, Administration, and Maintenance (OAM) Requirements for the Bit Index Explicit Replication (BIER) Layer