draft-ietf-opsawg-oam-overview-13.txt | draft-ietf-opsawg-oam-overview-14.txt | |||
---|---|---|---|---|
Operations and Management Area Working Group T. Mizrahi | Operations and Management Area Working Group T. Mizrahi | |||
Internet Draft Marvell | Internet Draft Marvell | |||
Intended status: Informational N. Sprecher | Intended status: Informational N. Sprecher | |||
Expires: July 2014 Nokia Solutions and Networks | Expires: August 2014 Nokia Solutions and Networks | |||
E. Bellagamba | E. Bellagamba | |||
Ericsson | Ericsson | |||
Y. Weingarten | Y. Weingarten | |||
January 28, 2014 | February 18, 2014 | |||
An Overview of | An Overview of | |||
Operations, Administration, and Maintenance (OAM) Tools | Operations, Administration, and Maintenance (OAM) Tools | |||
draft-ietf-opsawg-oam-overview-13.txt | draft-ietf-opsawg-oam-overview-14.txt | |||
Abstract | Abstract | |||
Operations, Administration, and Maintenance (OAM) is a general term | Operations, Administration, and Maintenance (OAM) is a general term | |||
that refers to a toolset for fault detection and isolation, and for | that refers to a toolset for fault detection and isolation, and for | |||
performance measurement. Over the years various OAM tools have been | performance measurement. Over the years various OAM tools have been | |||
defined for various layers in the protocol stack. | defined for various layers in the protocol stack. | |||
This document summarizes some of the OAM tools defined in the IETF in | This document summarizes some of the OAM tools defined in the IETF in | |||
the context of IP unicast, MPLS, MPLS for the transport profile | the context of IP unicast, MPLS, MPLS for the transport profile | |||
skipping to change at page 2, line 16 | skipping to change at page 2, line 16 | |||
and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
The list of current Internet-Drafts can be accessed at | The list of current Internet-Drafts can be accessed at | |||
http://www.ietf.org/ietf/1id-abstracts.txt. | http://www.ietf.org/ietf/1id-abstracts.txt. | |||
The list of Internet-Draft Shadow Directories can be accessed at | The list of Internet-Draft Shadow Directories can be accessed at | |||
http://www.ietf.org/shadow.html. | http://www.ietf.org/shadow.html. | |||
This Internet-Draft will expire on July 28, 2014. | This Internet-Draft will expire on August 18, 2014. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2014 IETF Trust and the persons identified as the | Copyright (c) 2014 IETF Trust and the persons identified as the | |||
document authors. All rights reserved. | document authors. All rights reserved. | |||
This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
(http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
publication of this document. Please review these documents | publication of this document. Please review these documents | |||
skipping to change at page 20, line 47 | skipping to change at page 20, line 47 | |||
BFD [BFD-LSP] can be used to detect MPLS LSP data plane failures. | BFD [BFD-LSP] can be used to detect MPLS LSP data plane failures. | |||
A BFD session is established for each MPLS LSP that is being | A BFD session is established for each MPLS LSP that is being | |||
monitored. BFD Control packets must be sent along the same path as | monitored. BFD Control packets must be sent along the same path as | |||
the monitored LSP. If the LSP is associated with multiple FECs, a BFD | the monitored LSP. If the LSP is associated with multiple FECs, a BFD | |||
session is established for each FEC. | session is established for each FEC. | |||
While LSP Ping can be used for detecting MPLS data plane failures and | While LSP Ping can be used for detecting MPLS data plane failures and | |||
for verifying the MPLS LSP data plane against the control plane, BFD | for verifying the MPLS LSP data plane against the control plane, BFD | |||
can only be used for the former. The advantage of BFD is that it can | can only be used for the former. BFD can be used in conjunction with | |||
provide faster failure detection, and scales better to a large number | LSP Ping, as is the case in MPLS-TP (see Section 4.5.4.). | |||
of LSPs. Thus, a combination of LSP Ping and BFD can provide the | ||||
advantages of BFD, as well as allow to verify the data plane against | ||||
the control plane. | ||||
4.4.3. OAM for Virtual Private Networks (VPN) over MPLS | 4.4.3. OAM for Virtual Private Networks (VPN) over MPLS | |||
The IETF has defined two classes of VPNs, Layer 2 VPNs (L2VPN) and | The IETF has defined two classes of VPNs, Layer 2 VPNs (L2VPN) and | |||
Layer 3 VPNs (L3VPN). [L2VPN-OAM] provides the requirements and | Layer 3 VPNs (L3VPN). [L2VPN-OAM] provides the requirements and | |||
framework for OAM in the context of Layer 2 Virtual Private Networks | framework for OAM in the context of Layer 2 Virtual Private Networks | |||
(L2VPN), and specifically it also defines the OAM layering of L2VPNs | (L2VPN), and specifically it also defines the OAM layering of L2VPNs | |||
over MPLS. [L3VPN-OAM] provides a framework for the operation and | over MPLS. [L3VPN-OAM] provides a framework for the operation and | |||
management of Layer 3 Virtual Private Networks (L3VPNs). | management of Layer 3 Virtual Private Networks (L3VPNs). | |||
End of changes. 5 change blocks. | ||||
9 lines changed or deleted | 6 lines changed or added | |||
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |