Operations and Management (OAM) Requirements for Point-to-Multipoint MPLS Networks

Abstract

Operations and Management (OAM) Requirements for Point-to-Multipoint MPLS Networks Status of This Memo This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.

Requirements for Point-to-Multipoint Extensions to the Label Distribution Protocol

“…Further and precise requirements and mechanisms for P2MP MPLS Operations, Administration, and Maintenance (OAM) purposes are out of the scope of this document and are addressed in [RFC4687]. …”

Detecting Data-Plane Failures in Point-to-Multipoint MPLS - Extensions to LSP Ping

“…As stated in [RFC4687], MPLS has been extended to encompass P2MP LSPs. As with P2P MPLS LSPs, the requirement to detect, handle, and diagnose control-and data-plane defects is critical.…”

“…P2MP MPLS LSPs are at least as vulnerable to data-plane faults or to discrepancies between the control and data planes as their P2P counterparts. Therefore, mechanisms are needed to detect such data plane faults in P2MP MPLS LSPs as described in [RFC4687].…”

Requirements for Multicast in Layer 3 Provider-Provisioned Virtual Private Networks (PPVPNs)

“…Providing operators with means to check the proper setup and operation of MDTunnels MAY also be provided (e.g., when P2MP MPLS is used for MDTunnels, troubleshooting functionalities SHOULD integrate mechanisms compliant with [RFC4687], such as LSP Ping [RFC4379][LSP-PING]). Depending on the implementation, such verification could be initiated by a source-PE or a receiver-PE.…”