Operations and Management (OAM) Requirements for Multi-Protocol Label Switched (MPLS) Networks

Abstract

Operations and Management (OAM) Requirements for Multi-Protocol Label Switched (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 Operations, Administration, and Maintenance (OAM) in MPLS Transport Networks

“…By covering transport specificities, these requirements complement those identified in RFC 4377 [11]; yet, some requirements may be similar.…”

GMPLS RSVP-TE Extensions for Operations, Administration, and Maintenance (OAM) Configuration

“…MPLS OAM requirements are described in [RFC4377], which provides requirements to create consistent OAM functionality for MPLS networks. The following list is an excerpt of MPLS OAM requirements documented in [RFC4377] that bear direct relevance to the discussion set forth in this document: o It MUST be possible to explicitly request the setup of OAM entities for the signaled LSP and provide specific information for the setup if this is required by the technology.…”

Bidirectional Forwarding Detection (BFD) for MPLS Label Switched Paths (LSPs)

“…For instance, the control plane of the MPLS LSP may be functional while the data plane may be mis-forwarding or dropping data. Hence, there is a need for a mechanism to detect a data plane failure in the MPLS LSP path [RFC4377].…”