Operations and Management Requirements for Point-to- Multipoint MPLS Networks
RFC 4687, “Operations and Management Requirements for Point-to- Multipoint MPLS Networks”, is an Informational document published in September 2006 by S. Yasukawa, A. Farrel, D. King, T. Nadeau. The canonical text is published by the RFC Editor.
Abstract
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 4687 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4686 Analysis of Threats Motivating DomainKeys Identified Mail
- RFC 4688 A Uniform Resource Name Namespace for Aerospace and Defence Industries Association of Europe Specification 1000D
- RFC 4685 Atom Threading Extensions
- RFC 4689 Terminology for Benchmarking Network-layer Traffic Control Mechanisms
- RFC 4684 Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching Internet Protocol Virtual Private Networks
- RFC 4690 Review and Recommendations for Internationalized Domain Names
- RFC 4683 Internet X.509 Public Key Infrastructure Subject Identification Method
- RFC 4691 Guidelines for Acting as an IETF Liaison to Another Organization