--- 1/draft-ietf-mpls-tp-mib-management-overview-07.txt	2012-04-15 21:14:00.742671852 +0200
+++ 2/draft-ietf-mpls-tp-mib-management-overview-08.txt	2012-04-15 21:14:00.786671191 +0200
@@ -1,19 +1,19 @@
 Network Working Group                                   D. King (Editor)
 Internet-Draft                                        Old Dog Consulting
 Intended status: Informational                    M. Venkatesan (Editor)
-Expires: August 8, 2012                                          Aricent
-                                                           March 8, 2012
+Expires: Secptember 13, 2012                                     Aricent
+                                                          April 13, 2012
 
         Multiprotocol Label Switching Transport Profile (MPLS-TP)
                        MIB-based Management Overview
-             draft-ietf-mpls-tp-mib-management-overview-07.txt
+             draft-ietf-mpls-tp-mib-management-overview-08.txt
 
 Abstract
 
    A range of Management Information Base (MIB) modules has been
    developed to help model and manage the various aspects of
    Multiprotocol Label Switching (MPLS) networks.  These MIB modules are
    defined in separate documents that focus on the specific areas of
    responsibility of the modules that they describe.
 
    The MPLS Transport Profile (MPLS-TP) is a profile of MPLS
@@ -39,21 +39,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 August 8, 2012.
+   This Internet-Draft will expire on September 13, 2012.
 
 Copyright Notice
 
    Copyright (c) 2012 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
@@ -436,22 +436,22 @@
    The purpose of MPLS resiliency is to ensure minimal interruption to
    traffic when the failure occurs within the system or network.
 
    Various components of MPLS resiliency solutions are;
    1) Graceful restart in LDP and RSVP-TE modules,
    2) Make Before Break,
    3) Protection Switching for LSPs,
    4) Fast ReRoute for LSPs,
    5) PW redundancy.
 
-   The below modules only support the SNMP based MIB management
-   for MPLS resiliency.
+   The MIB modules below only support MIB based management for MPLS
+   resiliency.
 
    MPLS Fast Reroute (FRR) is a restoration network resiliency mechanism
    used in MPLS TE to redirect the traffic onto the backup LSP's in 10s
    of milliseconds in case of link or node failure across the LSP.
 
    MPLS-FRR-GENERAL-STD-MIB [draft-ietf-mpls-fastreroute-mib-14]
    contains objects that apply to any MPLS LSR implementing MPLS TE fast
    reroute functionality.
 
    MPLS-FRR-ONE2ONE-STD-MIB [draft-ietf-mpls-fastreroute-mib-14]
@@ -561,21 +561,21 @@
    |         |                    |      |       |    |                |
    |         |                    +<--- GMPLS-TE-STD-MIB ------------->+
    |         |                    ^                                    ^
    +<--- PW-STD-MIB <------+      |                                    |
    ^                       ^      |                                    |
    |                       |      |                                    |
    +<--- PW-ENET-STD-MIB ->+      |                                    |
    ^                       ^      |                                    |
    |                       |      |                                    |
    |                       |      |                                    |
-   +<---------------- PW-MPLS-STD-MIB-------------PAC-MAN------------->+
+   +<---------------- PW-MPLS-STD-MIB--------------------------------->+
 
    Thus:
 
    -  All the MPLS MIB modules depend on MPLS-TC-STD-MIB.
 
    -  All the GMPLS MIB modules depend on GMPLS-TC-STD-MIB.
 
    -  All the PW MIB modules depend on PW-TC-STD-MIB.
 
    -  MPLS-LDP-STD-MIB, MPLS-TE-STD-MIB, MPLS-FTN-STD-MIB,
@@ -721,24 +721,24 @@
 
 5.2.2 Recommendations
 
    - PW-MPLS-STD-MIB [RFC5602] can be enhanced to operate over
      co-routed/associated bi-directional tunnel.
 
 5.3 MPLS-TP Sections
 
 5.3.1 Gap Analysis
 
-   The existing MPLS MIB modules does not support MPLS-TP sections.
+   The existing MPLS MIB modules do not support MPLS-TP sections.
 
 5.3.2 Recommendations
-   Link specific and/or path/segment specific sections can be achieved
+   Link specific and/or path/segment specific sections can be supported
    by enhancing the IF-MIB [RFC2863], MPLS-TE-STD-MIB [RFC3812] and
    PW-STD-MIB [RFC5601] MIB modules.
 
 5.4 MPLS-TP OAM
 
 5.4.1 Gap Analysis
 
    MPLS manages the LSP and pseudowire faults through LSP ping
    [RFC4379], VCCV [RFC5085], BFD for LSPs [RFC5884] and BFD for VCCV
    [RFC5885] tools.