RFC 4687: Operations and Management (OAM) Requirements for Point-to-Multipoint MPLS Networks
In plain English — editorial summary, not part of the RFC
Multi-Protocol Label Switching (MPLS) has been extended to encompass point-to-multipoint (P2MP) Label Switched Paths (LSPs). As with point-to-point MPLS LSPs, the requirement to detect, handle, and diagnose control and data plane defects is critical. For operators deploying services based on P2MP MPLS LSPs, the detection and specification of how to handle those defects are important because such defects not only may affect the fundamentals of an MPLS network, but also may impact service level specification commitments for customers of their network. This document describes requirements for data plane operations and management for P2MP MPLS LSPs. These requirements apply to all forms of P2MP MPLS LSPs, and include P2MP Traffic Engineered (TE) LSPs and multicast LSPs. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4687
- Published
- September 2006
- Authors
- S. Yasukawa; A. Farrel; D. King; T. Nadeau
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4920Crankback Signaling Extensions for MPLS and GMPLS RSVP-TECurrent
July 2007
- RFC 4201Link Bundling in MPLS Traffic Engineering (TE)Current
October 2005
- RFC 5439An Analysis of Scaling Issues in MPLS-TE Core NetworksCurrent
February 2009
- RFC 4659BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPNCurrent
September 2006
- RFC 4717Encapsulation Methods for Transport of Asynchronous Transfer Mode (ATM) over MPLS NetworksCurrent
December 2006
- RFC 4726A Framework for Inter-Domain Multiprotocol Label Switching Traffic EngineeringCurrent
November 2006
- RFC 4781Graceful Restart Mechanism for BGP with MPLSCurrent
January 2007
- RFC 4577OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)Current
June 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?