--- 1/draft-ietf-netmod-rfc7277bis-02.txt	2018-01-11 08:15:35.352580790 -0800
+++ 2/draft-ietf-netmod-rfc7277bis-03.txt	2018-01-11 08:15:35.500584294 -0800
@@ -1,42 +1,47 @@
 
 Network Working Group                                       M. Bjorklund
 Internet-Draft                                            Tail-f Systems
-Obsoletes: rfc7277 (if approved)                         January 9, 2018
+Obsoletes: rfc7277 (if approved)                        January 11, 2018
 Intended status: Standards Track
-Expires: July 13, 2018
+Expires: July 15, 2018
 
                   A YANG Data Model for IP Management
-                    draft-ietf-netmod-rfc7277bis-02
+                    draft-ietf-netmod-rfc7277bis-03
 
 Abstract
 
    This document defines a YANG data model for management of IP
    implementations.  The data model includes configuration and system
-   state.  This document obsoletes RFC 7277.
+   state.
+
+   The YANG model in this document conforms to the Network Management
+   Datastore Architecture defined in I-D.ietf-netmod-revised-datastores.
+
+   This document obsoletes RFC 7277.
 
 Status of This Memo
 
    This Internet-Draft is submitted in full conformance with the
    provisions of BCP 78 and BCP 79.
 
    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 http://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 July 13, 2018.
+   This Internet-Draft will expire on July 15, 2018.
 
 Copyright Notice
 
    Copyright (c) 2018 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
@@ -1141,26 +1146,27 @@
    This document registers a YANG module in the "YANG Module Names"
    registry [RFC6020].
 
      Name:         ietf-ip
      Namespace:    urn:ietf:params:xml:ns:yang:ietf-ip
      Prefix:       ip
      Reference:    RFC 7277
 
 6.  Security Considerations
 
-   The YANG module defined in this document is designed to be accessed
-   via network management protocols such as NETCONF [RFC6241] or
-   RESTCONF [RFC8040].  The lowest NETCONF layer is the secure transport
-   layer, and the mandatory-to-implement secure transport is Secure
-   Shell (SSH) [RFC6242].  The lowest RESTCONF layer is HTTPS, and the
-   mandatory-to-implement secure transport is TLS [RFC5246].
+   The YANG module specified in this document defines a schema for data
+   that is designed to be accessed via network management protocols such
+   as NETCONF [RFC6241] or RESTCONF [RFC8040].  The lowest NETCONF layer
+   is the secure transport layer, and the mandatory-to-implement secure
+   transport is Secure Shell (SSH) [RFC6242].  The lowest RESTCONF layer
+   is HTTPS, and the mandatory-to-implement secure transport is TLS
+   [RFC5246].
 
    The NETCONF access control model [RFC6536] provides the means to
    restrict access for particular NETCONF or RESTCONF users to a
    preconfigured subset of all available NETCONF or RESTCONF protocol
    operations and content.
 
    There are a number of data nodes defined in the YANG module which are
    writable/creatable/deletable (i.e., config true, which is the
    default).  These data nodes may be considered sensitive or vulnerable
    in some network environments.  Write operations (e.g., edit-config)
@@ -1384,21 +1390,21 @@
              <forwarding or:origin="or:default">false</forwarding>
              <mtu or:origin="or:system">1500</mtu>
              <address>
                <ip>192.0.2.1</ip>
                <prefix-length>24</prefix-length>
                <origin>static</origin>
              </address>
              <neighbor or:origin="or:learned">
                <ip>192.0.2.2</ip>
                <link-layer-address>
-                 00:01:02:03:04:05
+                 00:00:5E:00:53:AB
                </link-layer-address>
              </neighbor>
            </ipv4>
            <ipv6 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip">
              <enabled or:origin="or:default">true</enabled>
              <forwarding or:origin="or:default">false</forwarding>
              <mtu>1280</mtu>
              <address>
                <ip>2001:db8::10</ip>
                <prefix-length>32</prefix-length>
@@ -1408,21 +1414,21 @@
              <address or:origin="or:learned">
                <ip>2001:db8::1:100</ip>
                <prefix-length>32</prefix-length>
                <origin>dhcp</origin>
                <status>preferred</status>
              </address>
              <dup-addr-detect-transmits>0</dup-addr-detect-transmits>
              <neighbor or:origin="or:learned">
                <ip>2001:db8::1</ip>
                <link-layer-address>
-                 00:01:02:03:04:05
+                 00:00:5E:00:53:AB
                </link-layer-address>
                <origin>dynamic</origin>
                <is-router/>
                <state>reachable</state>
              </neighbor>
              <neighbor or:origin="or:learned">
                <ip>2001:db8::4</ip>
                <origin>dynamic</origin>
                <state>incomplete</state>
              </neighbor>