--- 1/draft-ietf-netmod-yang-versioning-reqs-00.txt	2019-07-03 10:13:05.240884439 -0700
+++ 2/draft-ietf-netmod-yang-versioning-reqs-01.txt	2019-07-03 10:13:05.268885149 -0700
@@ -1,18 +1,18 @@
 
 Network Working Group                                     J. Clarke, Ed.
 Internet-Draft                                       Cisco Systems, Inc.
-Intended status: Informational                            March 26, 2019
-Expires: September 27, 2019
+Intended status: Informational                              July 3, 2019
+Expires: January 4, 2020
 
                   YANG Module Versioning Requirements
-               draft-ietf-netmod-yang-versioning-reqs-00
+               draft-ietf-netmod-yang-versioning-reqs-01
 
 Abstract
 
    This document describes the problems that can arise because of the
    YANG language module update rules, that require all updates to YANG
    module preserve strict backwards compatibility.  It also defines the
    requirements on any solution designed to solve the stated problems.
    This document does not consider possible solutions, nor endorse any
    particular solution.
 
@@ -24,21 +24,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 September 27, 2019.
+   This Internet-Draft will expire on January 4, 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
@@ -405,23 +405,23 @@
             either not been updated or have been updated in backwards-
             compatible ways.
 
        1.3  A refined form of YANG's 'import' statement MUST be provided
             that is more restrictive than "import any revision" and less
             restrictive than "import a specific revision".  Once non-
             backwards-compatible changes to modules are allowed, the
             refined import statement is used to express the correct
             dependency between modules.
 
-       1.4  The solution MUST allow for backwards-compatible
-            enhancements and bug fixes, as well as non-backwards-
-            compatible bug fixes in non-latest-release modules.
+       1.4  The solution MUST be able to express when non-backwards-
+            compatible changes have occurred between two revisions of a
+            given YANG module.
 
    2.  Requirements related to identifying changes between different
        module revisions:
 
        2.1  Readers of modules, and tools that use modules, MUST be able
             to determine whether changes between two revisions of a
             module constitute a backwards-compatible or non-backwards-
             compatible version change.  In addition, it MAY be helpful
             to identify whether changes represent bug fixes, new
             functionality, or both.