API Build-data JSON Resources
Theme

Choose how MSRBot.io looks on this device.

Preference is stored in this browser only.

IETF RFC 4687
[ACTIVE]

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

Metadata

Publisher
IETF
Doc Type
Informational
Pages
14
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.
Publication Date
2006-09-01
Status Note
Informational
DOI
10.17487/RFC4687
Link
https://doi.org/10.17487/RFC4687
Author(s)
Seisho Yasukawa
Adrian Farrel
Daniel King
Thomas Nadeau
Keyword(s)
MPLS, LSP, P2MP
Latest version of IETF RFC 4687

Document Versions — IETF RFC 4687

  • ▶ IETF RFC 4687 (2006-09-01)
    THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

Bibliographic Reference(s)

  • Minei, I., Ed., Kompella, K., Wijnands, I., Ed., and B. Thomas, "Label Distribution Protocol Extensions for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths", Work in Progress, June 2006. EXTERNAL
  • Aggarwal, R., Papadimitriou, D., and S. Yasukawa, "Extensions to RSVP-TE for Point to Multipoint TE LSPs", Work in Progress, July 2006. EXTERNAL
  • Yasukawa, S., Farrel, A., Ali, Z., and B. Fenner, "Detecting Data Plane Failures in Point-to- Multipoint MPLS Traffic Engineering - Extensions to LSP Ping", Work in Progress, April 2006. EXTERNAL
  • IETF RFC 3812 [Active*]
  • IETF RFC 3813 [Active*]
  • IETF RFC 3814 [Active*]
  • IETF RFC 3815 [Active*]
  • IETF RFC 4378 [Active*]
  • IETF RFC 4379 [Superseded*]
  • IETF RFC 4461 [Active*]
Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC4687.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 4687, Operations and Management (OAM) Requirements for Point-to-Multipoint MPLS Networks. Available at https://doi.org/10.17487/RFC4687
Snippet:
IETF RFC 4687, Operations and Management (OAM) Requirements  for Point-to-Multipoint MPLS Networks. Available at https://doi.org/10.17487/RFC4687

HTML (ISO 690 compliant)

Preview:
IETF RFC 4687, Operations and Management (OAM) Requirements for Point-to-Multipoint MPLS Networks. Available at https://doi.org/10.17487/RFC4687
Snippet:
<span class="citation"><cite>IETF RFC 4687</cite>, Operations and Management (OAM) Requirements  for Point-to-Multipoint MPLS Networks. Available at <a href="https://doi.org/10.17487/RFC4687" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4687</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 4687, Operations and Management (OAM) Requirements for Point-to-Multipoint MPLS Networks
doi: 10.17487/RFC4687
url: https://doi.org/10.17487/RFC4687
Snippet:
<li>
<cite id="bib-rfc4687">IETF RFC 4687</cite>, Operations and Management (OAM) Requirements  for Point-to-Multipoint MPLS Networks
<span class="doi">10.17487/RFC4687</span>
</li>

Referenced By