RFC 7759: Configuration of Proactive Operations, Administration, and Maintenance (OAM) Functions for MPLS-Based Transport Networks Using Label Switched Path (LSP) Ping
In plain English — editorial summary, not part of the RFC
This specification describes the configuration of proactive MPLS-TP Operations, Administration, and Maintenance (OAM) functions for a given Label Switched Path (LSP) using a set of TLVs that are carried by the LSP Ping protocol.
Document record
- Document ID
- RFC7759
- Published
- February 2016
- Authors
- E. Bellagamba; G. Mirsky; L. Andersson; P. Skoldstrom; D. Ward; J. Drake
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 29
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7487Configuration of Proactive Operations, Administration, and Maintenance (OAM) Functions for MPLS-Based Transport Networks Using RSVP-TECurrent
March 2015
- RFC 8256Requirements for Hitless MPLS Path Segment MonitoringCurrent
October 2017
- RFC 8184Dual-Homing Protection for MPLS and the MPLS Transport Profile (MPLS-TP) PseudowiresCurrent
June 2017
- RFC 8185Dual-Homing Coordination for MPLS Transport Profile (MPLS-TP) Pseudowires ProtectionCurrent
June 2017
- RFC 7325MPLS Forwarding Compliance and Performance RequirementsCurrent
August 2014
- RFC 7190Use of Multipath with MPLS and MPLS Transport Profile (MPLS-TP)Current
March 2014
- RFC 7167A Framework for Point-to-Multipoint MPLS in Transport NetworksCurrent
April 2014
- RFC 6428Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport ProfileUpdated
November 2011
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?