RFC 6426: MPLS On-Demand Connectivity Verification and Route Tracing
In plain English — editorial summary, not part of the RFC
Label Switched Path Ping (LSP ping) is an existing and widely deployed Operations, Administration, and Maintenance (OAM) mechanism for Multi-Protocol Label Switching (MPLS) Label Switched Paths (LSPs). This document describes extensions to LSP ping so that LSP ping can be used for on-demand connectivity verification of MPLS Transport Profile (MPLS-TP) LSPs and pseudowires. This document also clarifies procedures to be used for processing the related OAM packets. Further, it describes procedures for using LSP ping to perform connectivity verification and route tracing functions in MPLS-TP networks. Finally, this document updates RFC 4379 by adding a new address type and creating an IANA registry. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6426
- Published
- November 2011
- Authors
- E. Gray; N. Bahadur; S. Boutros; R. Aggarwal
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 22
- Also known as
- —
- Updates:
- RFC 4379
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6428Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport ProfileUpdated
November 2011
- RFC 6424Mechanism for Performing Label Switched Path Ping (LSP Ping) over MPLS TunnelsObsoleted
November 2011
- RFC 5994Application of Ethernet Pseudowires to MPLS Transport NetworksCurrent
October 2010
- RFC 5960MPLS Transport Profile Data Plane ArchitectureUpdated
August 2010
- RFC 5951Network Management Requirements for MPLS-based Transport NetworksCurrent
September 2010
- RFC 5950Network Management Framework for MPLS-based Transport NetworksCurrent
September 2010
- RFC 5921A Framework for MPLS in Transport NetworksUpdated
July 2010
- RFC 5884Bidirectional Forwarding Detection (BFD) for MPLS Label Switched Paths (LSPs)Updated
June 2010
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?