Network Working Group T. Nadeau
Request for Comments: 4377 M. Morrow
Category: Informational G. Swallow
Cisco Systems, Inc.
D. Allan
Nortel Networks
S. Matsushima
Japan Telecom
February 2006
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.
Copyright Notice
Copyright (C) The Internet Society (2006).
Abstract
This document specifies Operations and Management (OAM) requirements
for Multi-Protocol Label Switching (MPLS), as well as for
applications of MPLS, such as pseudo-wire voice and virtual private
network services. These requirements have been gathered from network
operators who have extensive experience deploying MPLS networks.
Table of Contents
1. Introduction ....................................................2
2. Document Conventions ............................................2
3. Motivations .....................................................4
4. Requirements ....................................................4
5. Security Considerations ........................................11
6. References .....................................................12
7. Acknowledgements ...............................................13
Nadeau, et al. Informational [Page 1]
RFC 4377 OAM Requirements for MPLS Networks February 2006
1. Introduction
This document describes requirements for user and data plane
Operations and Management (OAM) for Multi-Protocol Label Switching
(MPLS). These requirements have been gathered from network operators
who have extensive experience deploying MPLS networks. This document
specifies OAM requirements for MPLS, as well as for applications of
MPLS.
Currently, there are no specific mechanisms proposed to address these
requirements. The goal of this document is to identify a commonly
applicable set of requirements for MPLS OAM at this time.
Specifically, a set of requirements that apply to the most common set
of MPLS networks deployed by service provider organizations at the
time this document was written. These requirements can then be used
as a base for network management tool development and to guide the
evolution of currently specified tools, as well as the specification
of OAM functions that are intrinsic to protocols used in MPLS
networks.
2. Document Conventions
2.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Queuing/buffering Latency: The delay caused by packet queuing (value
is variable since it is dependent on the
packet arrival rate, the packet length,
and the link throughput).
Probe-based-detection: Active measurement tool that can measure
the consistency of an LSP [RFC4379].
Defect: Any error condition that prevents a Label
Switched Path (LSP) from functioning
correctly. For example, loss of an
Interior Gateway Protocol (IGP) path will
most likely result in an LSP not being
able to deliver traffic to its
destination. Another example is the
interruption of the path for a TE tunnel.
These may be due to physical circuit
failures or failure of switching nodes to
operate as expected.
Nadeau, et al. Informational [Page 2]
RFC 4377 OAM Requirements for MPLS Networks February 2006
datatracker.ietf.org