< draft-ietf-netmod-yang-versioning-reqs-00.txt   draft-ietf-netmod-yang-versioning-reqs-01.txt >
Network Working Group J. Clarke, Ed. Network Working Group J. Clarke, Ed.
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended status: Informational March 26, 2019 Intended status: Informational July 3, 2019
Expires: September 27, 2019 Expires: January 4, 2020
YANG Module Versioning Requirements YANG Module Versioning Requirements
draft-ietf-netmod-yang-versioning-reqs-00 draft-ietf-netmod-yang-versioning-reqs-01
Abstract Abstract
This document describes the problems that can arise because of the This document describes the problems that can arise because of the
YANG language module update rules, that require all updates to YANG YANG language module update rules, that require all updates to YANG
module preserve strict backwards compatibility. It also defines the module preserve strict backwards compatibility. It also defines the
requirements on any solution designed to solve the stated problems. requirements on any solution designed to solve the stated problems.
This document does not consider possible solutions, nor endorse any This document does not consider possible solutions, nor endorse any
particular solution. particular solution.
skipping to change at page 1, line 35 skipping to change at page 1, line 35
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." 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 Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 9, line 39 skipping to change at page 9, line 39
either not been updated or have been updated in backwards- either not been updated or have been updated in backwards-
compatible ways. compatible ways.
1.3 A refined form of YANG's 'import' statement MUST be provided 1.3 A refined form of YANG's 'import' statement MUST be provided
that is more restrictive than "import any revision" and less that is more restrictive than "import any revision" and less
restrictive than "import a specific revision". Once non- restrictive than "import a specific revision". Once non-
backwards-compatible changes to modules are allowed, the backwards-compatible changes to modules are allowed, the
refined import statement is used to express the correct refined import statement is used to express the correct
dependency between modules. dependency between modules.
1.4 The solution MUST allow for backwards-compatible 1.4 The solution MUST be able to express when non-backwards-
enhancements and bug fixes, as well as non-backwards- compatible changes have occurred between two revisions of a
compatible bug fixes in non-latest-release modules. given YANG module.
2. Requirements related to identifying changes between different 2. Requirements related to identifying changes between different
module revisions: module revisions:
2.1 Readers of modules, and tools that use modules, MUST be able 2.1 Readers of modules, and tools that use modules, MUST be able
to determine whether changes between two revisions of a to determine whether changes between two revisions of a
module constitute a backwards-compatible or non-backwards- module constitute a backwards-compatible or non-backwards-
compatible version change. In addition, it MAY be helpful compatible version change. In addition, it MAY be helpful
to identify whether changes represent bug fixes, new to identify whether changes represent bug fixes, new
functionality, or both. functionality, or both.
 End of changes. 4 change blocks. 
7 lines changed or deleted 7 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/