RFC 4379: Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8029.
Current document in this lineage: RFC 8029 — Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures
In plain English — editorial summary, not part of the RFC
This document describes a simple and efficient mechanism that can be used to detect data plane failures in Multi-Protocol Label Switching (MPLS) Label Switched Paths (LSPs). There are two parts to this document: information carried in an MPLS "echo request" and "echo reply" for the purposes of fault detection and isolation, and mechanisms for reliably sending the echo reply. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4379
- Published
- February 2006
- Authors
- K. Kompella; G. Swallow
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 50
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.
Read the full history of Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures →
Referenced by
9 later RFCs formally update or obsolete part of this document.
- RFC 5462Multiprotocol Label Switching (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic Class" FieldCurrent
February 2009
- RFC 6424Mechanism for Performing Label Switched Path Ping (LSP Ping) over MPLS TunnelsObsoleted
November 2011
- RFC 6425Detecting Data-Plane Failures in Point-to-Multipoint MPLS - Extensions to LSP PingCurrent
November 2011
- RFC 6426MPLS On-Demand Connectivity Verification and Route TracingCurrent
November 2011
- RFC 6829Label Switched Path (LSP) Ping for Pseudowire Forwarding Equivalence Classes (FECs) Advertised over IPv6Obsoleted
January 2013
- RFC 7506IPv6 Router Alert Option for MPLS Operations, Administration, and Maintenance (OAM)Current
April 2015
- RFC 7537IANA Registries for LSP Ping Code PointsObsoleted
May 2015
- RFC 7743Relayed Echo Reply Mechanism for Label Switched Path (LSP) PingCurrent
January 2016
- RFC 8029Detecting Multiprotocol Label Switched (MPLS) Data-Plane FailuresUpdated
March 2017
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4378A Framework for Multi-Protocol Label Switching (MPLS) Operations and Management (OAM)Current
February 2006
- RFC 6383Advice on When It Is Safe to Start Sending Data on Label Switched Paths Established Using RSVP-TECurrent
September 2011
- RFC 4377Operations and Management (OAM) Requirements for Multi-Protocol Label Switched (MPLS) NetworksCurrent
February 2006
- RFC 4382MPLS/BGP Layer 3 Virtual Private Network (VPN) Management Information BaseCurrent
February 2006
- RFC 4385Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for Use over an MPLS PSNUpdated
February 2006
- RFC 4368Multiprotocol Label Switching (MPLS) Label-Controlled Asynchronous Transfer Mode (ATM) and Frame-Relay Management Interface DefinitionCurrent
January 2006
- RFC 4365Applicability Statement for BGP/MPLS IP Virtual Private Networks (VPNs)Current
February 2006
- RFC 4364BGP/MPLS IP Virtual Private Networks (VPNs)Updated
February 2006
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?