--- 1/draft-ietf-isis-yang-isis-cfg-39.txt	2019-09-28 12:13:11.801092152 -0700
+++ 2/draft-ietf-isis-yang-isis-cfg-40.txt	2019-09-28 12:13:12.001097195 -0700
@@ -1,25 +1,25 @@
 
 IS-IS Working Group                                         S. Litkowski
 Internet-Draft                                             Cisco Systems
 Intended status: Standards Track                                D. Yeung
-Expires: March 29, 2020                                      Arrcus, Inc
+Expires: March 31, 2020                                      Arrcus, Inc
                                                                A. Lindem
                                                            Cisco Systems
                                                                 J. Zhang
                                                         Juniper Networks
                                                                L. Lhotka
                                                                   CZ.NIC
-                                                      September 26, 2019
+                                                      September 28, 2019
 
                    YANG Data Model for IS-IS Protocol
-                    draft-ietf-isis-yang-isis-cfg-39
+                    draft-ietf-isis-yang-isis-cfg-40
 
 Abstract
 
    This document defines a YANG data model that can be used to configure
    and manage the IS-IS protocol on network elements.
 
 Requirements Language
 
    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
    "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
@@ -35,21 +35,21 @@
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF).  Note that other groups may also distribute
    working documents as Internet-Drafts.  The list of current Internet-
    Drafts is at https://datatracker.ietf.org/drafts/current/.
 
    Internet-Drafts are draft documents valid for a maximum of six months
    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."
 
-   This Internet-Draft will expire on March 29, 2020.
+   This Internet-Draft will expire on March 31, 2020.
 
 Copyright Notice
 
    Copyright (c) 2019 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
    (https://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
@@ -495,25 +495,25 @@
            }
            container level-2 {
              uses isis:overload-global-cfg;
              description
                "Level 2 configuration.";
            }
    }
 
    If an implementation does not support per-level configuration for a
    parameter modeled with per-level configuration, the implementation
-   SHOULD advertise a deviation to announce the non-support of the
+   should advertise a deviation to announce the non-support of the
    level-1 and level-2 containers.
 
    Finally, if an implementation supports per-level configuration but
-   does not support the level-1-2 configuration, it SHOULD also
+   does not support the level-1-2 configuration, it should also
    advertise a deviation.
 
 2.4.  Per-Interface Parameters
 
    The per-interface section of the IS-IS instance describes the
    interface-specific parameters.
 
    The interface is modeled as a reference to an existing interface
    defined in the "ietf-interfaces" YANG model ([RFC8343].
 
@@ -1852,21 +1852,21 @@
                    "Unknown alternate type.";
                }
              }
              description
                "Type of alternate.";
            }
            leaf best {
              type boolean;
              description
                "Is set when the alternate is the preferred one,
-                is unset otherwise.";
+                is clear otherwise.";
            }
            leaf non-best-reason {
              type string {
                length "1..255";
              }
              description
                "Information field to describe why the alternate
                 is not best. The length should be limited to 255
                 unicode characters. The expected format is a single
                 line text.";
@@ -5040,21 +5040,21 @@
    Denial-of-Service (DoS) attack.  For example, adding IS-IS on any
    unprotected interface could allow an IS-IS adjacency to be formed
    with an unauthorized and malicious neighbor.  Once an adjacency is
    formed, traffic could be hijacked.  As a simpler example, a Denial-
    of-Service attack could be mounted by changing the cost of an IS-IS
    interface to be asymmetric such that a hard routing loop ensues.  In
    general, unauthorized modification of most IS-IS features will pose
    their own set of security risks and the "Security Considerations" in
    the respective reference RFCs should be consulted.
 
-   Some of the readable data nodes in the ietf-isi.yang module may be
+   Some of the readable data nodes in the ietf-isis.yang module may be
    considered sensitive or vulnerable in some network environments.  It
    is thus important to control read access (e.g., via get, get-config,
    or notification) to these data nodes.  The exposure of the Link State
    Database (LSDB) will expose the detailed topology of the network.
    The Link State Database (LSDB) is represented by the following schema
    node:
 
       /isis/database
 
    Exposure of the Link State Database includes information beyond the