--- 1/draft-ietf-mpls-tp-oam-id-mib-09.txt	2015-09-08 09:15:30.179352438 -0700
+++ 2/draft-ietf-mpls-tp-oam-id-mib-10.txt	2015-09-08 09:15:30.287355069 -0700
@@ -1,26 +1,26 @@
 
 Network Working Group
 INTERNET-DRAFT                                                Sam Aldrin
 Intended Status: Standards Track                            Google, Inc.
-Expires: March 1, 2016                                      M.Venkatesan
+Expires: March 11, 2016                                     M.Venkatesan
                                                               Dell, Inc.
                                                        Kannan KV Sampath
                                                                   Redeem
                                                         Thomas D. Nadeau
                                                                  Brocade
 
-                                                       September 1, 2015
+                                                       September 8, 2015
 
  MPLS-TP Operations, Administration, and Management (OAM) Identifiers
                    Management Information Base (MIB)
-                    draft-ietf-mpls-tp-oam-id-mib-09
+                    draft-ietf-mpls-tp-oam-id-mib-10
 
 Abstract
 
    This memo defines a portion of the Management Information Base (MIB)
    for use with network management protocols in the Internet community.
    In particular, it describes managed objects to configure the
    Operations, Administration, and Management (OAM) identifiers for
    Multiprotocol Label Switching (MPLS) and MPLS-based Transport Profile
    (TP).
 
@@ -38,21 +38,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 March 4, 2016.
+   This Internet-Draft will expire on March 11, 2016.
 
 Copyright and License Notice
 
    Copyright (c) 2015 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
@@ -1102,30 +1102,20 @@
          OBJECT      mplsOamIdMegServicePointerType
          MIN-ACCESS  read-only
          DESCRIPTION
                "Write access is not required."
 
          OBJECT      mplsOamIdMegMpLocation
          MIN-ACCESS  read-only
          DESCRIPTION
                "Write access is not required."
 
-         OBJECT      mplsOamIdMegOperStatus
-         MIN-ACCESS  read-only
-         DESCRIPTION
-               "Write access is not required."
-
-         OBJECT      mplsOamIdMegSubOperStatus
-         MIN-ACCESS  read-only
-         DESCRIPTION
-               "Write access is not required."
-
          OBJECT      mplsOamIdMegPathFlow
          MIN-ACCESS  read-only
          DESCRIPTION
                "Write access is not required."
 
          OBJECT      mplsOamIdMegRowStatus
          SYNTAX      RowStatus { active(1) }
          MIN-ACCESS  read-only
          DESCRIPTION
                "Write access is not required."
@@ -1256,22 +1245,21 @@
 
    This MIB relates to a system that will provide network connectivity
    and packet forwarding services. As such, improper manipulation of the
    objects represented by this MIB may result in denial of service to a
    large number of end-users.
 
    There are number of management objects defined in this MIB module
    with a MAX-ACCESS clause of read-create. Such objects may be
    considered sensitive or vulnerable in some network environments.
    The support for SET operations in a non-secure environment
-   without proper protection can have negative effect on network
-   operations.
+   without proper protection opens devices to attack.
 
    Some of the readable objects in this MIB module (i.e., objects
    with a MAX-ACCESS other than not-accessible) may be considered
    sensitive or vulnerable in some network environments.
    It is thus important to control even GET and/or NOTIFY access
    to these objects and possibly to even encrypt the values of these
    objects when sending them over the network via SNMP.  These are
    the tables and objects and their sensitivity/vulnerability:
 
    - mplsOamIdMegTable and mplsOamIdMeTable collectively show