Home > Research > Publications & Outputs > RFC4687: Operations and Management (OAM) Requir...

Electronic data

  • rfc4687

    Submitted manuscript, 29.8 KB, text/plain

View graph of relations

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

Research output: Other contribution

Published

Standard

RFC4687: Operations and Management (OAM) Requirements for Point-to-Multipoint MPLS Networks. / King, Daniel; Yasukawa, Seisho; Farrel, Adrian et al.
14 p. 2006, Standards Organisation Output.

Research output: Other contribution

Harvard

APA

Vancouver

Author

Bibtex

@misc{eb0de09c2c034d2a9d2698d16ae60c30,
title = "RFC4687: Operations and Management (OAM) Requirements for Point-to-Multipoint MPLS Networks",
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.",
author = "Daniel King and Seisho Yasukawa and Adrian Farrel and Thomas Nadeau",
year = "2006",
month = sep,
language = "English",
type = "Other",

}

RIS

TY - GEN

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

AU - King, Daniel

AU - Yasukawa, Seisho

AU - Farrel, Adrian

AU - Nadeau, Thomas

PY - 2006/9

Y1 - 2006/9

N2 - 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.

AB - 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.

M3 - Other contribution

ER -