draft-ietf-netconf-yang-library-06.txt   rfc7895.txt 
Network Working Group A. Bierman Internet Engineering Task Force (IETF) A. Bierman
Internet-Draft YumaWorks Request for Comments: 7895 YumaWorks
Intended status: Standards Track M. Bjorklund Category: Standards Track M. Bjorklund
Expires: October 29, 2016 Tail-f Systems ISSN: 2070-1721 Tail-f Systems
K. Watsen K. Watsen
Juniper Networks Juniper Networks
April 27, 2016 June 2016
YANG Module Library YANG Module Library
draft-ietf-netconf-yang-library-06
Abstract Abstract
This document describes a YANG library, which provides information This document describes a YANG library that provides information
about all the YANG modules used by a network management server (e.g., about all the YANG modules used by a network management server (e.g.,
a Network Configuration Protocol (NETCONF) server). Simple caching a Network Configuration Protocol (NETCONF) server). Simple caching
mechanisms are provided to allow clients to minimize retrieval of mechanisms are provided to allow clients to minimize retrieval of
this information. this information.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
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 This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on October 29, 2016. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7895.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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 2, line 15 skipping to change at page 2, line 12
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3
2. YANG Module Library . . . . . . . . . . . . . . . . . . . . . 4 2. YANG Module Library . . . . . . . . . . . . . . . . . . . . . 4
2.1. modules-state . . . . . . . . . . . . . . . . . . . . . . 4 2.1. modules-state . . . . . . . . . . . . . . . . . . . . . . 4
2.1.1. modules-state/module-set-id . . . . . . . . . . . . . 5 2.1.1. modules-state/module-set-id . . . . . . . . . . . . . 4
2.1.2. modules-state/module . . . . . . . . . . . . . . . . 5 2.1.2. modules-state/module . . . . . . . . . . . . . . . . 5
2.2. YANG Library Module . . . . . . . . . . . . . . . . . . . 5 2.2. YANG Library Module . . . . . . . . . . . . . . . . . . . 5
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
3.1. YANG Module Registry . . . . . . . . . . . . . . . . . . 11 3.1. YANG Module Registry . . . . . . . . . . . . . . . . . . 11
4. Security Considerations . . . . . . . . . . . . . . . . . . . 11 4. Security Considerations . . . . . . . . . . . . . . . . . . . 11
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 5.1. Normative References . . . . . . . . . . . . . . . . . . 12
6.1. Normative References . . . . . . . . . . . . . . . . . . 12 5.2. Informative References . . . . . . . . . . . . . . . . . 12
6.2. Informative References . . . . . . . . . . . . . . . . . 13 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 13
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
A.1. v05 to v06 . . . . . . . . . . . . . . . . . . . . . . . 13
A.2. v04 to v05 . . . . . . . . . . . . . . . . . . . . . . . 14
A.3. v03 to v04 . . . . . . . . . . . . . . . . . . . . . . . 14
A.4. v02 to v03 . . . . . . . . . . . . . . . . . . . . . . . 14
A.5. v01 to v02 . . . . . . . . . . . . . . . . . . . . . . . 14
A.6. v00 to v01 . . . . . . . . . . . . . . . . . . . . . . . 14
A.7. draft-ietf-netconf-restconf-03 to v00 . . . . . . . . . . 14
Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
There is a need for standard mechanisms to identify the YANG modules There is a need for standard mechanisms to identify the YANG modules
and submodules that are in use by a server that implements YANG data and submodules that are in use by a server that implements YANG data
models. If a large number of YANG modules are utilized by the models. If a large number of YANG modules are utilized by the
server, then the YANG library contents needed can be relatively server, then the YANG library contents needed can be relatively
large. This information changes very infrequently, so it is large. This information changes very infrequently, so it is
important that clients be able to cache the YANG library contents and important that clients be able to cache the YANG library contents and
easily identify whether their cache is out-of-date. easily identify whether their cache is out of date.
YANG library information can be different on every server, and can YANG library information can be different on every server and can
change at run-time or across a server reboot. change at runtime or across a server reboot.
If the server implements multiple protocols to access the YANG- If the server implements multiple protocols to access the YANG-
defined data, each such protocol has it's own conceptual defined data, each such protocol has its own conceptual instantiation
instantiation of the YANG library. of the YANG library.
The following information is needed by a client application (for each The following information is needed by a client application (for each
YANG module in the library) to fully utilize the YANG data modeling YANG module in the library) to fully utilize the YANG data modeling
language: language:
o name: The name of the YANG module. o name: The name of the YANG module.
o revision: Each YANG module and submodule within the library has a o revision: Each YANG module and submodule within the library has a
revision. This is derived from the most recent revision statement revision. This is derived from the most recent revision statement
within the module or submodule. If no such revision statement within the module or submodule. If no such revision statement
skipping to change at page 3, line 39 skipping to change at page 3, line 27
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14, [RFC2119]. 14, [RFC2119].
The following terms are defined in [RFC6241]: The following terms are defined in [RFC6241]:
o client o client
o server o server
The following terms are defined in [I-D.ietf-netmod-rfc6020bis]: The following terms are defined in [YANG1.1]:
o module o module
o submodule o submodule
The following terms are used within this document: The following terms are used within this document:
o YANG library: a collection of YANG modules and submodules used by o YANG library: A collection of YANG modules and submodules used by
a server a server.
1.2. Tree Diagrams 1.2. Tree Diagrams
A simplified graphical representation of the data model is used in A simplified graphical representation of the data model is used in
this document. The meaning of the symbols in these diagrams is as this document. The meaning of the symbols in these diagrams is as
follows: follows:
o Brackets "[" and "]" enclose list keys. o Brackets "[" and "]" enclose list keys.
o Abbreviations before data node names: "rw" means configuration o Abbreviations before data node names: "rw" means configuration
data (read-write) and "ro" state data (read-only). data (read-write) and "ro" state data (read-only).
o Symbols after data node names: "?" means an optional node, "!" o Symbols after data node names: "?" means an optional node, "!"
skipping to change at page 4, line 29 skipping to change at page 4, line 18
o Ellipsis ("...") stands for contents of subtrees that are not o Ellipsis ("...") stands for contents of subtrees that are not
shown. shown.
2. YANG Module Library 2. YANG Module Library
The "ietf-yang-library" module provides information about the YANG The "ietf-yang-library" module provides information about the YANG
library used by a server. This module is defined using YANG version library used by a server. This module is defined using YANG version
1, but it supports the description of YANG modules written in any 1, but it supports the description of YANG modules written in any
revision of YANG. revision of YANG.
YANG Tree Diagram for "ietf-yang-library" module: Following is the YANG Tree Diagram for the "ietf-yang-library"
module:
+--ro modules-state +--ro modules-state
+--ro module-set-id string +--ro module-set-id string
+--ro module* [name revision] +--ro module* [name revision]
+--ro name yang:yang-identifier +--ro name yang:yang-identifier
+--ro revision union +--ro revision union
+--ro schema? inet:uri +--ro schema? inet:uri
+--ro namespace inet:uri +--ro namespace inet:uri
+--ro feature* yang:yang-identifier +--ro feature* yang:yang-identifier
+--ro deviation* [name revision] +--ro deviation* [name revision]
| +--ro name yang:yang-identifier | +--ro name yang:yang-identifier
| +--ro revision union | +--ro revision union
+--ro conformance-type enumeration +--ro conformance-type enumeration
+--ro submodules
+--ro submodule* [name revision] +--ro submodule* [name revision]
+--ro name yang:yang-identifier +--ro name yang:yang-identifier
+--ro revision union +--ro revision union
+--ro schema? inet:uri +--ro schema? inet:uri
2.1. modules-state 2.1. modules-state
This mandatory container holds the identifiers for the YANG data This mandatory container holds the identifiers for the YANG data
model modules supported by the server. model modules supported by the server.
2.1.1. modules-state/module-set-id 2.1.1. modules-state/module-set-id
This mandatory leaf contains a unique implementation-specific This mandatory leaf contains a unique implementation-specific
identifier representing the current set of modules and submodules on identifier representing the current set of modules and submodules on
a specific server. The value of this leaf MUST change whenever the a specific server. The value of this leaf MUST change whenever the
set of modules and submodules in the YANG library changes. There is set of modules and submodules in the YANG library changes. There is
no requirement that the same set always results in the same module- no requirement that the same set always results in the same "module-
set-id value. set-id" value.
This leaf allows a client to fetch the module list once, cache it, This leaf allows a client to fetch the module list once, cache it,
and only re-fetch it if the value of this leaf has been changed. and only refetch it if the value of this leaf has been changed.
If the value of this leaf changes, the server also generates a If the value of this leaf changes, the server also generates a
"yang-library-change" notification, with the new value of "yang-library-change" notification, with the new value of
"module-set-id". "module-set-id".
Note that for a NETCONF server that implements YANG 1.1 Note that for a NETCONF server that implements YANG 1.1 [YANG1.1], a
[I-D.ietf-netmod-rfc6020bis], a change of the "module-set-id" value change of the "module-set-id" value results in a new value for the
results in a new value for the :yang-library capability defined in :yang-library capability defined in [YANG1.1]. Thus, if such a
[I-D.ietf-netmod-rfc6020bis]. Thus, if such a server implements server implements NETCONF notifications [RFC5277], and the
NETCONF notifications [RFC5277], and the notification notification "netconf-capability-change" [RFC6470], a
"netconf-capability-change" [RFC6470], a "netconf-capability-change" "netconf-capability-change" notification is generated whenever the
notification is generated whenever the "module-set-id" changes. "module-set-id" changes.
2.1.2. modules-state/module 2.1.2. modules-state/module
This mandatory list contains one entry for each YANG data model This mandatory list contains one entry for each YANG data model
module supported by the server. There MUST be an entry in this list module supported by the server. There MUST be an entry in this list
for each revision of each YANG module that is used by the server. It for each revision of each YANG module that is used by the server. It
is possible for multiple revisions of the same module to be imported, is possible for multiple revisions of the same module to be imported,
in addition to an entry for the revision that is implemented by the in addition to an entry for the revision that is implemented by the
server. server.
2.2. YANG Library Module 2.2. YANG Library Module
The "ietf-yang-library" module defines monitoring information for the The "ietf-yang-library" module defines monitoring information for the
YANG modules used by a server. YANG modules used by a server.
The "ietf-yang-types" and "ietf-inet-types" modules from [RFC6991] The "ietf-yang-types" and "ietf-inet-types" modules from [RFC6991]
are used by this module for some type definitions. are used by this module for some type definitions.
RFC Ed.: update the date below with the date of RFC publication and <CODE BEGINS> file "ietf-yang-library@2016-06-21.yang"
remove this note.
<CODE BEGINS> file "ietf-yang-library@2016-04-09.yang"
module ietf-yang-library { module ietf-yang-library {
namespace "urn:ietf:params:xml:ns:yang:ietf-yang-library"; namespace "urn:ietf:params:xml:ns:yang:ietf-yang-library";
prefix "yanglib"; prefix "yanglib";
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
} }
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
} }
skipping to change at page 6, line 14 skipping to change at page 6, line 4
module ietf-yang-library { module ietf-yang-library {
namespace "urn:ietf:params:xml:ns:yang:ietf-yang-library"; namespace "urn:ietf:params:xml:ns:yang:ietf-yang-library";
prefix "yanglib"; prefix "yanglib";
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
} }
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
} }
organization organization
"IETF NETCONF (Network Configuration) Working Group"; "IETF NETCONF (Network Configuration) Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/netconf/> "WG Web: <https://datatracker.ietf.org/wg/netconf/>
WG List: <mailto:netconf@ietf.org> WG List: <mailto:netconf@ietf.org>
WG Chair: Mehmet Ersue WG Chair: Mehmet Ersue
<mailto:mehmet.ersue@nsn.com> <mailto:mehmet.ersue@nsn.com>
WG Chair: Mahesh Jethanandani WG Chair: Mahesh Jethanandani
<mailto:mjethanandani@gmail.com> <mailto:mjethanandani@gmail.com>
Editor: Andy Bierman Editor: Andy Bierman
<mailto:andy@yumaworks.com> <mailto:andy@yumaworks.com>
skipping to change at page 7, line 4 skipping to change at page 6, line 40
Copyright (c) 2016 IETF Trust and the persons identified as Copyright (c) 2016 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.";
// RFC Ed.: replace XXXX with actual RFC number and remove this This version of this YANG module is part of RFC 7895; see
// note. the RFC itself for full legal notices.";
// RFC Ed.: remove this note
// Note: extracted from draft-ietf-netconf-yang-library-06.txt
// RFC Ed.: update the date below with the date of RFC publication revision 2016-06-21 {
// and remove this note.
revision 2016-04-09 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: YANG Module Library."; "RFC 7895: YANG Module Library.";
} }
/* /*
* Typedefs * Typedefs
*/ */
typedef revision-identifier { typedef revision-identifier {
type string { type string {
pattern '\d{4}-\d{2}-\d{2}'; pattern '\d{4}-\d{2}-\d{2}';
} }
description description
"Represents a specific date in YYYY-MM-DD format."; "Represents a specific date in YYYY-MM-DD format.";
skipping to change at page 8, line 52 skipping to change at page 8, line 35
leaf namespace { leaf namespace {
type inet:uri; type inet:uri;
mandatory true; mandatory true;
description description
"The XML namespace identifier for this module."; "The XML namespace identifier for this module.";
} }
leaf-list feature { leaf-list feature {
type yang:yang-identifier; type yang:yang-identifier;
description description
"List of YANG feature names from this module that are "List of YANG feature names from this module that are
supported by the server, regardless whether they are supported by the server, regardless of whether they are
defined in the module or any included submodule."; defined in the module or any included submodule.";
} }
list deviation { list deviation {
key "name revision"; key "name revision";
description description
"List of YANG deviation module names and revisions "List of YANG deviation module names and revisions
used by this server to modify the conformance of used by this server to modify the conformance of
the module associated with this entry. Note that the module associated with this entry. Note that
the same module can be used for deviations for the same module can be used for deviations for
multiple modules, so the same entry MAY appear multiple modules, so the same entry MAY appear
skipping to change at page 9, line 33 skipping to change at page 9, line 17
type enumeration { type enumeration {
enum implement { enum implement {
description description
"Indicates that the server implements one or more "Indicates that the server implements one or more
protocol-accessible objects defined in the YANG module protocol-accessible objects defined in the YANG module
identified in this entry. This includes deviation identified in this entry. This includes deviation
statements defined in the module. statements defined in the module.
For YANG version 1.1 modules, there is at most one For YANG version 1.1 modules, there is at most one
module entry with conformance type 'implement' for a module entry with conformance type 'implement' for a
particular module name, since YANG 1.1 requires that particular module name, since YANG 1.1 requires that,
at most one revision of a module is implemented. at most, one revision of a module is implemented.
For YANG version 1 modules, there SHOULD NOT be more For YANG version 1 modules, there SHOULD NOT be more
than one module entry for a particular module name."; than one module entry for a particular module name.";
} }
enum import { enum import {
description description
"Indicates that the server imports reusable definitions "Indicates that the server imports reusable definitions
from the specified revision of the module, but does from the specified revision of the module but does
not implement any protocol accessible objects from not implement any protocol-accessible objects from
this revision. this revision.
Multiple module entries for the same module name MAY Multiple module entries for the same module name MAY
exist. This can occur if multiple modules import the exist. This can occur if multiple modules import the
same module, but specify different revision-dates in same module but specify different revision dates in
the import statements."; the import statements.";
} }
} }
mandatory true; mandatory true;
description description
"Indicates the type of conformance the server is claiming "Indicates the type of conformance the server is claiming
for the YANG module identified by this entry."; for the YANG module identified by this entry.";
} }
container submodules { list submodule {
key "name revision";
description description
"Contains information about all the submodules used "Each entry represents one submodule within the
by the parent module entry"; parent module.";
uses common-leafs;
list submodule { uses schema-leaf;
key "name revision";
description
"Each entry represents one submodule within the
parent module.";
uses common-leafs;
uses schema-leaf;
}
} }
} }
} }
/* /*
* Operational state data nodes * Operational state data nodes
*/ */
container modules-state { container modules-state {
config false; config false;
description description
"Contains YANG module monitoring information."; "Contains YANG module monitoring information.";
leaf module-set-id { leaf module-set-id {
skipping to change at page 11, line 29 skipping to change at page 11, line 9
} }
} }
<CODE ENDS> <CODE ENDS>
3. IANA Considerations 3. IANA Considerations
3.1. YANG Module Registry 3.1. YANG Module Registry
This document registers one URI in the IETF XML registry [RFC3688]. This document registers one URI in the "IETF XML Registry" [RFC3688].
Following the format in RFC 3688, the following registration is Following the format in RFC 3688, the following registration has been
requested to be made. made.
URI: urn:ietf:params:xml:ns:yang:ietf-yang-library URI: urn:ietf:params:xml:ns:yang:ietf-yang-library
Registrant Contact: The NETCONF WG of the IETF. Registrant Contact: The NETCONF WG of the IETF.
XML: N/A, the requested URI is an XML namespace. XML: N/A, the requested URI is an XML namespace.
This document registers one YANG module in the YANG Module Names This document registers one YANG module in the "YANG Module Names"
registry [RFC6020]. registry [RFC6020].
name: ietf-yang-library name: ietf-yang-library
namespace: urn:ietf:params:xml:ns:yang:ietf-yang-library namespace: urn:ietf:params:xml:ns:yang:ietf-yang-library
prefix: yanglib prefix: yanglib
// RFC Ed.: replace XXXX with RFC number and remove this note reference: RFC 7895
reference: RFC XXXX
4. Security Considerations 4. Security Considerations
The YANG module defined in this memo is designed to be accessed via The YANG module defined in this memo is designed to be accessed via
the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the
secure transport layer and the mandatory-to-implement secure secure transport layer and the mandatory-to-implement secure
transport is SSH [RFC6242]. Authorization for access to specific transport is SSH [RFC6242]. The NETCONF access control model
portions of conceptual data and operations within this module is [RFC6536] provides the means to restrict access for particular
provided by the NETCONF access control model (NACM) [RFC6536]. NETCONF users to a pre-configured subset of all available NETCONF
protocol operations and content.
Some of the readable data nodes in this YANG module may be considered Some of the readable data nodes in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus sensitive or vulnerable in some network environments. It is thus
important to control read access (e.g., via get, get-config, or important to control read access (e.g., via get, get-config, or
notification) to these data nodes. These are the subtrees and data notification) to these data nodes. These are the subtrees and data
nodes and their sensitivity/vulnerability: nodes and their sensitivity/vulnerability:
o /modules-state/module: The module list used in a server o /modules-state/module: The module list used in a server
implementation may help an attacker identify the server implementation may help an attacker identify the server
capabilities and server implementations with known bugs. Although capabilities and server implementations with known bugs. Although
some of this information may be available to all users via the some of this information may be available to all users via the
NETCONF <hello> message (or similar messages in other management NETCONF <hello> message (or similar messages in other management
protocols), this YANG module potentially exposes additional protocols), this YANG module potentially exposes additional
details that could be of some assistance to an attacker. Server details that could be of some assistance to an attacker. Server
vulnerabilities may be specific to particular modules, module vulnerabilities may be specific to particular modules, module
revisions, module features, or even module deviations. This revisions, module features, or even module deviations. This
information is included in each module entry. For example, if a information is included in each module entry. For example, if a
particular operation on a particular data node is known to cause a particular operation on a particular data node is known to cause a
server to crash or significantly degrade device performance, then server to crash or significantly degrade device performance, then
the module list information will help an attacker identify server the module list information will help an attacker identify server
implementations with such a defect, in order to launch a denial of implementations with such a defect, in order to launch a denial-
service attack on the device. of-service attack on the device.
5. Acknowledgements
Contributions to this material by Andy Bierman are based upon work
supported by the The Space & Terrestrial Communications Directorate
(S&TCD) under Contract No. W15P7T-13-C-A616. Any opinions, findings
and conclusions or recommendations expressed in this material are
those of the author(s) and do not necessarily reflect the views of
The Space & Terrestrial Communications Directorate (S&TCD).
6. References 5. References
6.1. Normative References 5.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119,
RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<http://www.rfc-editor.org/info/rfc3688>. <http://www.rfc-editor.org/info/rfc3688>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, DOI 10.17487/RFC6020, October 2010,
<http://www.rfc-editor.org/info/rfc6020>. <http://www.rfc-editor.org/info/rfc6020>.
skipping to change at page 13, line 24 skipping to change at page 12, line 36
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<http://www.rfc-editor.org/info/rfc6241>. <http://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<http://www.rfc-editor.org/info/rfc6242>. <http://www.rfc-editor.org/info/rfc6242>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536, DOI Protocol (NETCONF) Access Control Model", RFC 6536,
10.17487/RFC6536, March 2012, DOI 10.17487/RFC6536, March 2012,
<http://www.rfc-editor.org/info/rfc6536>. <http://www.rfc-editor.org/info/rfc6536>.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
6991, DOI 10.17487/RFC6991, July 2013, RFC 6991, DOI 10.17487/RFC6991, July 2013,
<http://www.rfc-editor.org/info/rfc6991>. <http://www.rfc-editor.org/info/rfc6991>.
6.2. Informative References 5.2. Informative References
[I-D.ietf-netmod-rfc6020bis]
Bjorklund, M., "The YANG 1.1 Data Modeling Language",
draft-ietf-netmod-rfc6020bis-11 (work in progress),
February 2016.
[RFC5277] Chisholm, S. and H. Trevino, "NETCONF Event [RFC5277] Chisholm, S. and H. Trevino, "NETCONF Event
Notifications", RFC 5277, DOI 10.17487/RFC5277, July 2008, Notifications", RFC 5277, DOI 10.17487/RFC5277, July 2008,
<http://www.rfc-editor.org/info/rfc5277>. <http://www.rfc-editor.org/info/rfc5277>.
[RFC6470] Bierman, A., "Network Configuration Protocol (NETCONF) [RFC6470] Bierman, A., "Network Configuration Protocol (NETCONF)
Base Notifications", RFC 6470, DOI 10.17487/RFC6470, Base Notifications", RFC 6470, DOI 10.17487/RFC6470,
February 2012, <http://www.rfc-editor.org/info/rfc6470>. February 2012, <http://www.rfc-editor.org/info/rfc6470>.
Appendix A. Change Log [YANG1.1] Bjorklund, M., "The YANG 1.1 Data Modeling Language", Work
in Progress, draft-ietf-netmod-rfc6020bis-12, April 2016.
-- RFC Ed.: remove this section before publication.
A.1. v05 to v06
o correct IANA instructions for module
A.2. v04 to v05
o clarify security considerations per secdir review
o clarifications for AD review
A.3. v03 to v04
o editorial changes after WGLC
o one library instance per management protocol
o removed protocol definitions
o removed requirements on YANG 1.1 modules (text is moved to draft-
ietf-netmod-rfc6020bis)
o added notification yang-library-change
o changed top-level node name from "modules" to "modules-state"
o changed leaf "conformance" to "conformance-type"
A.4. v02 to v03
o added yang-protocol identity
o added identities for NETCONF and RESTCONF protocols
o added yang-protocol leaf-list to /modules
o added restricted-protocol leaf-list to /modules/module
A.5. v01 to v02
o clarify 'implement' conformance for YANG 1.1 modules
A.6. v00 to v01
o change conformance leaf to enumeration
o filled in security considerations section
A.7. draft-ietf-netconf-restconf-03 to v00
o moved ietf-yang-library from RESTCONF draft to new draft
Appendix B. Open Issues
-- RFC Ed.: remove this section before publication.
The YANG Library issue tracker can be found here: Acknowledgements
https://github.com/netconf-wg/yang-library/issues Contributions to this material by Andy Bierman are based upon work
supported by the Space & Terrestrial Communications Directorate
(S&TCD) under Contract No. W15P7T-13-C-A616. Any opinions, findings,
conclusions, or recommendations expressed in this material are those
of the author(s) and do not necessarily reflect the views of the
Space & Terrestrial Communications Directorate (S&TCD).
Authors' Addresses Authors' Addresses
Andy Bierman Andy Bierman
YumaWorks YumaWorks
Email: andy@yumaworks.com Email: andy@yumaworks.com
Martin Bjorklund Martin Bjorklund
Tail-f Systems Tail-f Systems
 End of changes. 52 change blocks. 
199 lines changed or deleted 107 lines changed or added

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