RFC 8029: Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures
This document describes a simple and efficient mechanism to detect data-plane failures in Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs). It…
Read RFC 8029 on the RFC Editor
Outgoing relationships (31 related RFCs)
Incoming relationships (25 related RFCs)
- Updated by, Normatively referenced by — RFC 9041: Updating the MPLS Label Switched Paths (LSPs) Ping Parameters IANA Registry
- Updated by — RFC 8611: Label Switched Path (LSP) Ping and Traceroute Multipath Support for Link Aggregation Group (LAG) Interfaces
- Updated by, Normatively referenced by — RFC 9570: Deprecating the Use of Router Alert in LSP Ping
- Normatively referenced by — RFC 8287: Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data Planes
- Normatively referenced by — RFC 9780: Bidirectional Forwarding Detection (BFD) for Multipoint Networks over Point-to-Multipoint MPLS Label Switched Paths (LSPs)
- Normatively referenced by — RFC 8690: Clarification of Segment ID Sub-TLV Length for RFC 8287
- Normatively referenced by — RFC 9703: Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data Plane
- Normatively referenced by — RFC 9961: MPLS Segment Routing Point-to-Multipoint (P2MP) Policy Ping
- Normatively referenced by — RFC 9062: Framework and Requirements for Ethernet VPN (EVPN) Operations, Administration, and Maintenance (OAM)
- Normatively referenced by — RFC 9214: OSPFv3 Code Point for MPLS LSP Ping
- Normatively referenced by — RFC 9489: Label Switched Path (LSP) Ping Mechanisms for EVPN and Provider Backbone Bridging EVPN (PBB-EVPN)
- Normatively referenced by — RFC 9612: Bidirectional Forwarding Detection (BFD) Reverse Path for MPLS Label Switched Paths (LSPs)
- Normatively referenced by — RFC 9655: Egress Validation in Label Switched Path Ping and Traceroute Mechanisms
- Normatively referenced by — RFC 9658: Multipoint LDP Extensions for Multi-Topology Routing
- Normatively referenced by — RFC 9716: Mechanisms for MPLS Ping and Traceroute Procedures in Inter-Domain Segment Routing Networks
- Normatively referenced by — RFC 9832: BGP Classful Transport Planes
- Normatively referenced by — RFC 9884: Label Switched Path Ping for Segment Routing Path Segment Identifier with MPLS Data Plane
- Informatively referenced by — RFC 8403: A Scalable and Topology-Aware MPLS Data-Plane Monitoring System
- Informatively referenced by — RFC 8924: Service Function Chaining (SFC) Operations, Administration, and Maintenance (OAM) Framework
- Informatively referenced by — RFC 9359: Echo Request/Reply for Enabled In Situ OAM (IOAM) Capabilities
- Informatively referenced by — RFC 9516: Active Operations, Administration, and Maintenance (OAM) for Service Function Chaining (SFC)
- Informatively referenced by — RFC 9772: Active Operations, Administration, and Maintenance (OAM) for Use in Generic Network Virtualization Encapsulation (Geneve)
- Informatively referenced by — RFC 9805: Deprecation of the IPv6 Router Alert Option for New Protocols
- Informatively referenced by — RFC 9974: Operations, Administration, and Maintenance (OAM) Requirements for the Bit Index Explicit Replication (BIER) Layer
- Informatively referenced by — RFC 10014: Guidelines for Characterizing the Term "OAM"