--- 1/draft-ietf-opsawg-oam-overview-13.txt	2014-02-18 10:14:37.150730527 -0800
+++ 2/draft-ietf-opsawg-oam-overview-14.txt	2014-02-18 10:14:37.250732979 -0800
@@ -1,23 +1,23 @@
 Operations and Management Area Working Group                  T. Mizrahi
 Internet Draft                                                   Marvell
 Intended status: Informational                               N. Sprecher
-Expires: July 2014                          Nokia Solutions and Networks
+Expires: August 2014                        Nokia Solutions and Networks
                                                            E. Bellagamba
                                                                 Ericsson
                                                            Y. Weingarten
 
-                                                        January 28, 2014
+                                                       February 18, 2014
 
                               An Overview of
           Operations, Administration, and Maintenance (OAM) Tools
-                   draft-ietf-opsawg-oam-overview-13.txt
+                   draft-ietf-opsawg-oam-overview-14.txt
 
 Abstract
 
    Operations, Administration, and Maintenance (OAM) is a general term
    that refers to a toolset for fault detection and isolation, and for
    performance measurement. Over the years various OAM tools have been
    defined for various layers in the protocol stack.
 
    This document summarizes some of the OAM tools defined in the IETF in
    the context of IP unicast, MPLS, MPLS for the transport profile
@@ -49,21 +49,21 @@
    and may be updated, replaced, or obsoleted by other documents at any
    time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."
 
    The list of current Internet-Drafts can be accessed at
    http://www.ietf.org/ietf/1id-abstracts.txt.
 
    The list of Internet-Draft Shadow Directories can be accessed at
    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 (c) 2014 IETF Trust and the persons identified as the
    document authors. All rights reserved.
 
    This document is subject to BCP 78 and the IETF Trust's Legal
    Provisions Relating to IETF Documents
    (http://trustee.ietf.org/license-info) in effect on the date of
    publication of this document. Please review these documents
@@ -916,25 +916,22 @@
 
    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
    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
    session is established for each FEC.
 
    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
-   can only be used for the former. The advantage of BFD is that it can
-   provide faster failure detection, and scales better to a large number
-   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.
+   can only be used for the former. BFD can be used in conjunction with
+   LSP Ping, as is the case in MPLS-TP (see Section 4.5.4.).
 
 4.4.3. OAM for Virtual Private Networks (VPN) over MPLS
 
    The IETF has defined two classes of VPNs, Layer 2 VPNs (L2VPN) and
    Layer 3 VPNs (L3VPN). [L2VPN-OAM] provides the requirements and
    framework for OAM in the context of Layer 2 Virtual Private Networks
    (L2VPN), and specifically it also defines the OAM layering of L2VPNs
    over MPLS. [L3VPN-OAM] provides a framework for the operation and
    management of Layer 3 Virtual Private Networks (L3VPNs).