draft-ietf-netconf-rfc7895bis-06.txt   draft-ietf-netconf-rfc7895bis-07.txt 
Network Working Group A. Bierman Network Working Group A. Bierman
Internet-Draft YumaWorks Internet-Draft YumaWorks
Obsoletes: 7895 (if approved) M. Bjorklund Obsoletes: 7895 (if approved) M. Bjorklund
Intended status: Standards Track Tail-f Systems Intended status: Standards Track Tail-f Systems
Expires: October 11, 2018 J. Schoenwaelder Expires: April 20, 2019 J. Schoenwaelder
Jacobs University Jacobs University
K. Watsen K. Watsen
Juniper Networks Juniper Networks
R. Wilton R. Wilton
Cisco Systems Cisco Systems
April 9, 2018 October 17, 2018
YANG Library YANG Library
draft-ietf-netconf-rfc7895bis-06 draft-ietf-netconf-rfc7895bis-07
Abstract Abstract
This document describes a YANG library that provides information This document describes a YANG library that provides information
about the YANG modules, datastores, and datastore schemas used by a about the YANG modules, datastores, and datastore schemas used by a
network management server. Simple caching mechanisms are provided to network management server. Simple caching mechanisms are provided to
allow clients to minimize retrieval of this information. This allow clients to minimize retrieval of this information. This
version of the YANG library supports the Network Management Datastore version of the YANG library supports the Network Management Datastore
Architecture by listing all datastores supported by a network Architecture by listing all datastores supported by a network
management server and the schema that is used by each of these management server and the schema that is used by each of these
skipping to change at page 1, line 46 skipping to change at page 1, line 46
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 October 11, 2018. This Internet-Draft will expire on April 20, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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 25 skipping to change at page 2, line 25
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
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
2. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. YANG Library Data Model . . . . . . . . . . . . . . . . . . . 6 3. YANG Library Data Model . . . . . . . . . . . . . . . . . . . 5
4. YANG Library YANG Module . . . . . . . . . . . . . . . . . . 8 4. YANG Library YANG Module . . . . . . . . . . . . . . . . . . 8
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
6. Security Considerations . . . . . . . . . . . . . . . . . . . 21 6. Security Considerations . . . . . . . . . . . . . . . . . . . 21
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 22
8.1. Normative References . . . . . . . . . . . . . . . . . . 22 8.1. Normative References . . . . . . . . . . . . . . . . . . 22
8.2. Informative References . . . . . . . . . . . . . . . . . 23 8.2. Informative References . . . . . . . . . . . . . . . . . 23
Appendix A. Summary of Changes from RFC 7895 . . . . . . . . . . 24 Appendix A. Summary of Changes from RFC 7895 . . . . . . . . . . 24
Appendix B. Example YANG Library Instance for a Basic Server . . 25 Appendix B. Example YANG Library Instance for a Basic Server . . 25
Appendix C. Example YANG Library Instance for an Advanced Server 27 Appendix C. Example YANG Library Instance for an Advanced Server 27
skipping to change at page 3, line 16 skipping to change at page 3, line 16
The old YANG library definitions have been retained (for backwards The old YANG library definitions have been retained (for backwards
compatibility reasons) but the definitions have been marked as compatibility reasons) but the definitions have been marked as
deprecated. For backwards compatibility, an NMDA-supporting server deprecated. For backwards compatibility, an NMDA-supporting server
SHOULD populate the deprecated "/modules-state" tree in a backwards- SHOULD populate the deprecated "/modules-state" tree in a backwards-
compatible manner. The new "/yang-library" tree would be ignored by compatible manner. The new "/yang-library" tree would be ignored by
legacy clients, while providing all the data needed for NMDA-aware legacy clients, while providing all the data needed for NMDA-aware
clients, which would themselves ignore the "/modules-state" tree. clients, which would themselves ignore the "/modules-state" tree.
The recommended approach to populate "/modules-state" is to report The recommended approach to populate "/modules-state" is to report
the schema for YANG modules that are configurable via conventional the schema for YANG modules that are configurable via conventional
datastores and for which config false data nodes are returned via a configuration datastores and for which config false data nodes are
NETCONF <get> operation, or equivalent. returned via a NETCONF <get> operation, or equivalent.
The YANG library information can be different on every server and it The YANG library information can be different on every server and it
can change at runtime or across a server reboot. If a server can change at runtime or across a server reboot. If a server
implements multiple network management protocols to access the implements multiple network management protocols to access the
server's datastores, then each such protocol may have its own server's datastores, then each such protocol may have its own
conceptual instantiation of the YANG library. conceptual instantiation of the YANG library.
If a large number of YANG modules are utilized by a server, then the If a large number of YANG modules are utilized by a server, then the
YANG library contents can be relatively large. Since the YANG YANG library contents can be relatively large. Since the YANG
library contents changes very infrequently, it is important that library contents changes very infrequently, it is important that
clients be able to cache the YANG library contents and easily clients be able to cache the YANG library contents and easily
identify whether their cache is out of date. identify whether their cache is out of date.
All NETCONF servers supporting YANG 1.1 [RFC7950] are required to
support YANG Library (see Section 5.6.4 of RFC 7950). NETCONF
servers implementing the NETCONF extensions to support the NMDA
[I-D.ietf-netconf-nmda-netconf] MUST implement at least the version
of the YANG library defined in this document. Similarly, all
RESTCONF servers are required to support YANG Library (see Section 10
of RFC 8040). RESTCONF servers implementing the RESTCONF extensions
to support the NMDA [I-D.ietf-netconf-nmda-restconf] MUST implement
at least the version of the YANG library defined in this document.
1.1. Terminology 1.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"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] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
The following terms are defined in [RFC7950]: The following terms are defined in [RFC7950]:
skipping to change at page 4, line 38 skipping to change at page 4, line 30
o dynamic configuration datastore o dynamic configuration datastore
o client and server o client and server
The following terms are used within this document: The following terms are used within this document:
o YANG library: A collection of YANG modules, submodules, o YANG library: A collection of YANG modules, submodules,
datastores, and datastore schemas used by a server. datastores, and datastore schemas used by a server.
o YANG library checksum: A server-generated checksum of the contents o YANG library content identifier: A server-generated identifier of
of the YANG library. the contents of the YANG library.
Tree diagrams used in this document use the notation defined in Tree diagrams used in this document use the notation defined in
[RFC8340]. [RFC8340].
2. Objectives 2. Objectives
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 SHOULD o revision: If defined in the YANG module or submodule, the revision
have a revision. This is derived from the most recent revision is derived from the most recent revision statement within the
statement within the module or submodule. module or submodule.
o submodule list: The name, and if defined, revision of each o submodule list: The name, and if defined, revision of each
submodule used by the module must be identified. submodule used by the module must be identified.
o feature list: The name of each YANG feature supported by the o feature list: The name of each YANG feature supported by the
server, in a given datastore schema, must be identified. server, in a given datastore schema, must be identified.
o deviation list: The name of each YANG module with deviation o deviation list: The name of each YANG module with deviation
statements affecting a given YANG module, in a given datastore statements affecting a given YANG module, in a given datastore
schema, must be identified. schema, must be identified.
skipping to change at page 5, line 30 skipping to change at page 5, line 20
application for each datastore supported by a server: application for each datastore supported by a server:
o identity: The YANG identity for the datastore. o identity: The YANG identity for the datastore.
o schema: The schema (i.e., the set of modules) implemented by the o schema: The schema (i.e., the set of modules) implemented by the
datastore. datastore.
In order to select one out of several possible data model designs, In order to select one out of several possible data model designs,
the following criteria were used: the following criteria were used:
1. Efficient for a client to consume. Since the size of the YANG 1. The information must be efficient for a client to consume. Since
library can be quite large, it should be possible for clients to the size of the YANG library can be quite large, it should be
cache the YANG library information. possible for clients to cache the YANG library information.
2. A dynamic configuration datastore must be able to implement a 2. A dynamic configuration datastore must be able to implement a
module or feature that is not implemented in the conventional module or feature that is not implemented in the conventional
configuration datastores. configuration datastores.
3. It must be possible to NOT implement a module or feature in 3. It must be possible to not implement a module or feature in
<operational>, even if it is implemented in some other datastore. <operational>, even if it is implemented in some other datastore.
This is required for transition purposes; a server that wants to This is required for transition purposes; a server that wants to
implement <operational> should not have to implement all modules implement <operational> should not have to implement all modules
at once. at once.
4. A given module can only be implemented in one revision in all 4. A given module can only be implemented in one revision in all
datastores. If a module is implemented in more than one datastores. If a module is implemented in more than one
datastores, the same revision is implemented in all these datastore, the same revision is implemented in all these
datastores. datastores.
5. Multiple revisions can be used for import, if import-by revision 5. Multiple revisions can be used for import, if import-by revision
is used. is used.
6. Make it possible to use the YANG library by schema mount 6. It must be possible to use the YANG library by schema mount
[I-D.ietf-netmod-schema-mount]. [I-D.ietf-netmod-schema-mount].
3. YANG Library Data Model 3. YANG Library Data Model
The "ietf-yang-library" YANG module provides information about the The "ietf-yang-library" YANG module provides information about the
modules, submodules, datastores, and datastore schemas supported by a modules, submodules, datastores, and datastore schemas supported by a
server. All data nodes in "ietf-yang-library" are "config false", server. All data nodes in "ietf-yang-library" are "config false",
and thus only accessible in the operational state datastore. and thus only accessible in the operational state datastore.
+-----------+ +-----------+
skipping to change at page 7, line 35 skipping to change at page 7, line 35
| +--ro submodule* [name] | +--ro submodule* [name]
| +--ro name yang:yang-identifier | +--ro name yang:yang-identifier
| +--ro revision? revision-identifier | +--ro revision? revision-identifier
| +--ro location* inet:uri | +--ro location* inet:uri
+--ro schema* [name] +--ro schema* [name]
| +--ro name string | +--ro name string
| +--ro module-set* -> ../../module-set/name | +--ro module-set* -> ../../module-set/name
+--ro datastore* [name] +--ro datastore* [name]
| +--ro name ds:datastore-ref | +--ro name ds:datastore-ref
| +--ro schema -> ../../schema/name | +--ro schema -> ../../schema/name
+--ro checksum string +--ro content-id string
notifications: notifications:
+---n yang-library-update +---n yang-library-update
+--ro checksum -> /yang-library/checksum +--ro content-id -> /yang-library/content-id
The "/yang-library" container holds the entire YANG library. The The "/yang-library" container holds the entire YANG library. The
container has the following child nodes: container has the following child nodes:
o The "/yang-library/module-set" contains entries representing o The "/yang-library/module-set" contains entries representing
module sets. The list "/yang-library/module-set/module" module sets. The list "/yang-library/module-set/module"
enumerates the modules that belong to the module set. A module is enumerates the modules that belong to the module set. A module is
listed together with its submodules (if any), a set of features, listed together with its submodules (if any), a set of features,
and any deviation modules. The list "/yang-library/module-set/ and any deviation modules. The list "/yang-library/module-set/
import-only-module" lists all modules (and their submodules) used import-only-module" lists all modules (and their submodules) used
only for imports. only for imports. The assignment of a module to a module-set is
at the server's discretion. This revision of the YANG library
attaches no semantics as to which module-set a module is listed
in.
o The "/yang-library/schema" list contains an entry for each o The "/yang-library/schema" list contains an entry for each
datastore schema supported by the server. All conventional datastore schema supported by the server. All conventional
configuration datastores use the same "schema" list entry. A configuration datastores use the same "schema" list entry. A
dynamic configuration datastore may use a different datastore dynamic configuration datastore may use a different datastore
schema from the conventional configuration datastores, and hence schema from the conventional configuration datastores, and hence
may require a separate "schema" entry. A "schema" entry has a may require a separate "schema" entry. A "schema" entry has a
leaf-list of references to entries in the "module-set" list. The leaf-list of references to entries in the "module-set" list. The
schema consists of the union of all modules in all referenced schema consists of the union of all modules in all referenced
module sets. module sets.
o The "/yang-library/datastore" list contains one entry for each o The "/yang-library/datastore" list contains one entry for each
datastore supported by the server, and it identifies the datastore datastore supported by the server, and it identifies the datastore
schema associated with a datastore via a reference to an entry in schema associated with a datastore via a reference to an entry in
the "schema" list. Each supported conventional configuration the "schema" list. Each supported conventional configuration
datastore has a separate entry, pointing to the same "schema" list datastore has a separate entry, pointing to the same "schema" list
element. element.
o The "/yang-library/checksum" leaf contains the YANG library o The "/yang-library/content-id" leaf contains the YANG library
checksum, which is a unique implementation-specific identifier content identifier, which is an implementation-specific identifier
representing the current information in the YANG library on a representing the current information in the YANG library on a
specific server. The value of this leaf MUST change whenever the specific server. The value of this leaf MUST change whenever the
information in the YANG library changes. There is no requirement information in the YANG library changes. There is no requirement
that the same information always results in the same "checksum" that the same information always results in the same "content-id"
value. This leaf allows a client to fetch all schema information value. This leaf allows a client to fetch all schema information
once, cache it, and only refetch it if the value of this leaf has once, cache it, and only refetch it if the value of this leaf has
been changed. If the value of this leaf changes, the server also been changed. If the value of this leaf changes, the server also
generates a "yang-library-update" notification. generates a "yang-library-update" notification.
Note that for a NETCONF server implementing the NETCONF extensions to Note that for a NETCONF server implementing the NETCONF extensions to
support the NMDA [I-D.ietf-netconf-nmda-netconf], a change of the support the NMDA [I-D.ietf-netconf-nmda-netconf], a change of the
YANG library checksum results in a new value for the :yang- YANG library content identifier results in a new value for the :yang-
library:1.1 capability defined in [I-D.ietf-netconf-nmda-netconf]. library:1.1 capability defined in [I-D.ietf-netconf-nmda-netconf].
Thus, if such a server implements NETCONF notifications [RFC5277], Thus, if such a server implements NETCONF notifications [RFC5277],
and the notification "netconf-capability-change" [RFC6470], a and the notification "netconf-capability-change" [RFC6470], a
"netconf-capability-change" notification is generated whenever the "netconf-capability-change" notification is generated whenever the
YANG library checksum changes. YANG library content identifier changes.
4. YANG Library YANG Module 4. YANG Library YANG Module
The "ietf-yang-library" YANG module imports definitions from The "ietf-yang-library" YANG module imports definitions from
"ietf-yang-types" and "ietf-inet-types" defined in [RFC6991] and from "ietf-yang-types" and "ietf-inet-types" defined in [RFC6991] and from
"ietf-datastores" defined in [RFC8342]. While the YANG module is "ietf-datastores" defined in [RFC8342]. While the YANG module is
defined using YANG version 1.1, the YANG library supports the YANG defined using YANG version 1.1, the YANG library supports the YANG
modules written in any version of YANG. modules written in any version of YANG.
RFC Ed.: update the date below with the date of RFC publication and RFC Ed.: update the date below with the date of RFC publication and
remove this note. remove this note.
<CODE BEGINS> file "ietf-yang-library@2018-02-21.yang" <CODE BEGINS> file "ietf-yang-library@2018-10-16.yang"
module ietf-yang-library { module ietf-yang-library {
yang-version 1.1; yang-version 1.1;
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;
reference "RFC 6991: Common YANG Data Types."; reference "RFC 6991: Common YANG Data Types.";
} }
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
reference "RFC 6991: Common YANG Data Types."; reference "RFC 6991: Common YANG Data Types.";
} }
import ietf-datastores { import ietf-datastores {
prefix ds; prefix ds;
// RFC Ed.: update the reference below with the actual RFC number reference "RFC 8342: Network Management Datastore Architecture.";
reference "RFC XXXX: Network Management Datastore Architecture.";
} }
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: <http://tools.ietf.org/wg/netconf/>
WG List: <mailto:netconf@ietf.org> WG List: <mailto:netconf@ietf.org>
Author: Andy Bierman Author: Andy Bierman
skipping to change at page 9, line 46 skipping to change at page 9, line 48
Author: Martin Bjorklund Author: Martin Bjorklund
<mailto:mbj@tail-f.com> <mailto:mbj@tail-f.com>
Author: Juergen Schoenwaelder Author: Juergen Schoenwaelder
<mailto:j.schoenwaelder@jacobs-university.de> <mailto:j.schoenwaelder@jacobs-university.de>
Author: Kent Watsen Author: Kent Watsen
<mailto:kwatsen@juniper.net> <mailto:kwatsen@juniper.net>
Author: Rob Wilton Author: Rob Wilton
<rwilton@cisco.com>"; <mailto:rwilton@cisco.com>";
description description
"This module provides information about the YANG modules, "This module provides information about the YANG modules,
datastores, and datastore schemas used by a network datastores, and datastore schemas used by a network
management server. management server.
Copyright (c) 2018 IETF Trust and the persons identified as Copyright (c) 2018 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
skipping to change at page 10, line 22 skipping to change at page 10, line 23
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 This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
// RFC Ed.: update the date below with the date of RFC publication // RFC Ed.: update the date below with the date of RFC publication
// and remove this note. // and remove this note.
// RFC Ed.: replace XXXX with actual RFC number and remove this // RFC Ed.: replace XXXX with actual RFC number and remove this
// note. // note.
revision 2018-02-21 { revision 2018-10-16 {
description description
"Added support for multiple datastores according to the "Added support for multiple datastores according to the
Network Management Datastore Architecture (NMDA)."; Network Management Datastore Architecture (NMDA).";
reference reference
"RFC XXXX: YANG Library."; "RFC XXXX: YANG Library.";
} }
revision 2016-04-09 { revision 2016-04-09 {
description description
"Initial revision."; "Initial revision.";
reference reference
skipping to change at page 11, line 38 skipping to change at page 11, line 40
type inet:uri; type inet:uri;
description description
"Contains a URL that represents the YANG schema "Contains a URL that represents the YANG schema
resource for this module or submodule. resource for this module or submodule.
This leaf will only be present if there is a URL This leaf will only be present if there is a URL
available for retrieval of the schema for this entry."; available for retrieval of the schema for this entry.";
} }
} }
grouping implementation-parameters { grouping module-implementation-parameters {
description description
"Parameters for describing the implementation of a module."; "Parameters for describing the implementation of a module.";
leaf-list feature { leaf-list feature {
type yang:yang-identifier; type yang:yang-identifier;
description description
"List of all YANG feature names from this module that are "List of all YANG feature names from this module that are
supported by the server, regardless whether they are defined supported by the server, regardless whether they are defined
in the module or any included submodule."; in the module or any included submodule.";
} }
skipping to change at page 13, line 11 skipping to change at page 13, line 12
list submodule { list submodule {
key "name"; key "name";
description description
"Each entry represents one submodule within the "Each entry represents one submodule within the
parent module."; parent module.";
uses module-identification-leafs; uses module-identification-leafs;
uses location-leaf-list; uses location-leaf-list;
} }
uses implementation-parameters; uses module-implementation-parameters;
} }
list import-only-module { list import-only-module {
key "name revision"; key "name revision";
description description
"An entry in this list indicates that the server imports "An entry in this list indicates that the server imports
reusable definitions from the specified revision of the reusable definitions from the specified revision of the
module, but does not implement any protocol accessible module, but does not implement any protocol accessible
objects from this revision. objects from this revision.
Multiple entries for the same module name MAY exist. This Multiple entries for the same module name MAY exist. This
skipping to change at page 16, line 7 skipping to change at page 16, line 7
* Top-level container * Top-level container
*/ */
container yang-library { container yang-library {
config false; config false;
description description
"Container holding the entire YANG library of this server."; "Container holding the entire YANG library of this server.";
uses yang-library-parameters; uses yang-library-parameters;
leaf checksum { leaf content-id {
type string; type string;
mandatory true; mandatory true;
description description
"A server-generated checksum of the contents of the "A server-generated identifier of the contents of the
'yang-library' tree. The server MUST change the value of 'yang-library' tree. The server MUST change the value of
this leaf if the information represented by the this leaf if the information represented by the
'yang-library' tree, except 'yang-library/checksum', has 'yang-library' tree, except 'yang-library/content-id', has
changed."; changed.";
} }
} }
/* /*
* Notifications * Notifications
*/ */
notification yang-library-update { notification yang-library-update {
description description
"Generated when any YANG library information on the "Generated when any YANG library information on the
server has changed."; server has changed.";
leaf checksum { leaf content-id {
type leafref { type leafref {
path "/yanglib:yang-library/yanglib:checksum"; path "/yanglib:yang-library/yanglib:content-id";
} }
mandatory true; mandatory true;
description description
"Contains the YANG library checksum for the updated YANG "Contains the YANG library content identifier for the updated
library at the time the notification is generated."; YANG library at the time the notification is generated.";
} }
} }
/* /*
* Legacy groupings * Legacy groupings
*/ */
grouping module-list { grouping module-list {
status deprecated; status deprecated;
description description
skipping to change at page 21, line 36 skipping to change at page 21, line 36
This document takes over this registration entry made by RFC 7895. This document takes over this registration entry made by RFC 7895.
6. Security Considerations 6. Security Considerations
The YANG module specified in this document defines a schema for data The YANG module specified in this document defines a schema for data
that is accessed by network management protocols such as NETCONF that is accessed by network management protocols such as NETCONF
[RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer is the [RFC6241] or RESTCONF [RFC8040]. 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 Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
is HTTPS, and the mandatory-to-implement secure transport is TLS is HTTPS, and the mandatory-to-implement secure transport is TLS
[RFC5246]. [RFC8446].
The NETCONF access control model [RFC6536] provides the means to The NETCONF access control model [RFC8341] provides the means to
restrict access for particular NETCONF or RESTCONF users to a restrict access for particular NETCONF or RESTCONF users to a
preconfigured subset of all available NETCONF or RESTCONF protocol preconfigured subset of all available NETCONF or RESTCONF protocol
operations and content. 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:
skipping to change at page 22, line 31 skipping to change at page 22, line 31
(S&TCD) under Contract No. W15P7T-13-C-A616. Any opinions, findings (S&TCD) under Contract No. W15P7T-13-C-A616. Any opinions, findings
and conclusions or recommendations expressed in this material are and conclusions or recommendations expressed in this material are
those of the author(s) and do not necessarily reflect the views of those of the author(s) and do not necessarily reflect the views of
The Space & Terrestrial Communications Directorate (S&TCD). The Space & Terrestrial Communications Directorate (S&TCD).
8. References 8. References
8.1. Normative References 8.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, <https://www.rfc-editor.org/info/ DOI 10.17487/RFC2119, March 1997, <https://www.rfc-
rfc2119>. 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, <https://www.rfc- DOI 10.17487/RFC3688, January 2004, <https://www.rfc-
editor.org/info/rfc3688>. editor.org/info/rfc3688>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, DOI 10.17487/
RFC5246, August 2008, <https://www.rfc-editor.org/info/
rfc5246>.
[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, <https://www.rfc- DOI 10.17487/RFC6020, October 2010, <https://www.rfc-
editor.org/info/rfc6020>. editor.org/info/rfc6020>.
[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,
<https://www.rfc-editor.org/info/rfc6241>. <https://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,
<https://www.rfc-editor.org/info/rfc6242>. <https://www.rfc-editor.org/info/rfc6242>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
Protocol (NETCONF) Access Control Model", RFC 6536, DOI RFC 6991, DOI 10.17487/RFC6991, July 2013,
10.17487/RFC6536, March 2012, <https://www.rfc- <https://www.rfc-editor.org/info/rfc6991>.
editor.org/info/rfc6536>.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC
6991, DOI 10.17487/RFC6991, July 2013, <https://www.rfc-
editor.org/info/rfc6991>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>. <https://www.rfc-editor.org/info/rfc8040>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018, <https://www.rfc-
editor.org/info/rfc8341>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>. <https://www.rfc-editor.org/info/rfc8342>.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>.
8.2. Informative References 8.2. Informative References
[I-D.ietf-netconf-nmda-netconf] [I-D.ietf-netconf-nmda-netconf]
Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "NETCONF Extensions to Support the Network and R. Wilton, "NETCONF Extensions to Support the Network
Management Datastore Architecture", draft-ietf-netconf- Management Datastore Architecture", draft-ietf-netconf-
nmda-netconf-04 (work in progress), March 2018. nmda-netconf-07 (work in progress), October 2018.
[I-D.ietf-netconf-nmda-restconf] [I-D.ietf-netconf-nmda-restconf]
Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "RESTCONF Extensions to Support the Network and R. Wilton, "RESTCONF Extensions to Support the Network
Management Datastore Architecture", draft-ietf-netconf- Management Datastore Architecture", draft-ietf-netconf-
nmda-restconf-03 (work in progress), March 2018. nmda-restconf-05 (work in progress), October 2018.
[I-D.ietf-netmod-schema-mount] [I-D.ietf-netmod-schema-mount]
Bjorklund, M. and L. Lhotka, "YANG Schema Mount", draft- Bjorklund, M. and L. Lhotka, "YANG Schema Mount", draft-
ietf-netmod-schema-mount-09 (work in progress), March ietf-netmod-schema-mount-11 (work in progress), August
2018. 2018.
[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,
<https://www.rfc-editor.org/info/rfc5277>. <https://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, <https://www.rfc-editor.org/info/rfc6470>. February 2012, <https://www.rfc-editor.org/info/rfc6470>.
skipping to change at page 24, line 25 skipping to change at page 24, line 25
<https://www.rfc-editor.org/info/rfc7895>. <https://www.rfc-editor.org/info/rfc7895>.
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>. <https://www.rfc-editor.org/info/rfc8340>.
[RFC8343] Bjorklund, M., "A YANG Data Model for Interface [RFC8343] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,
<https://www.rfc-editor.org/info/rfc8343>. <https://www.rfc-editor.org/info/rfc8343>.
[RFC8344] Bjorklund, M., "A YANG Data Model for IP Management", RFC [RFC8344] Bjorklund, M., "A YANG Data Model for IP Management",
8344, DOI 10.17487/RFC8344, March 2018, <https://www.rfc- RFC 8344, DOI 10.17487/RFC8344, March 2018,
editor.org/info/rfc8344>. <https://www.rfc-editor.org/info/rfc8344>.
[RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N., [RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N.,
Ananthakrishnan, H., and X. Liu, "A YANG Data Model for Ananthakrishnan, H., and X. Liu, "A YANG Data Model for
Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March
2018, <https://www.rfc-editor.org/info/rfc8345>. 2018, <https://www.rfc-editor.org/info/rfc8345>.
[RFC8348] Bierman, A., Bjorklund, M., Dong, J., and D. Romascanu, "A [RFC8348] Bierman, A., Bjorklund, M., Dong, J., and D. Romascanu, "A
YANG Data Model for Hardware Management", RFC 8348, DOI YANG Data Model for Hardware Management", RFC 8348,
10.17487/RFC8348, March 2018, <https://www.rfc- DOI 10.17487/RFC8348, March 2018, <https://www.rfc-
editor.org/info/rfc8348>. editor.org/info/rfc8348>.
[RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for
Routing Management (NMDA Version)", RFC 8349, DOI Routing Management (NMDA Version)", RFC 8349,
10.17487/RFC8349, March 2018, <https://www.rfc- DOI 10.17487/RFC8349, March 2018, <https://www.rfc-
editor.org/info/rfc8349>. editor.org/info/rfc8349>.
Appendix A. Summary of Changes from RFC 7895 Appendix A. Summary of Changes from RFC 7895
This document updates [RFC7895] in the following ways: This document updates [RFC7895] in the following ways:
o Renamed document title from "YANG Module Library" to "YANG o Renamed document title from "YANG Module Library" to "YANG
Library". Library".
o Added a new top-level "/yang-library" container to hold the entire o Added a new top-level "/yang-library" container to hold the entire
skipping to change at page 27, line 31 skipping to change at page 27, line 31
</datastore> </datastore>
<datastore> <datastore>
<name>ds:running</name> <name>ds:running</name>
<schema>config-schema</schema> <schema>config-schema</schema>
</datastore> </datastore>
<datastore> <datastore>
<name>ds:operational</name> <name>ds:operational</name>
<schema>state-schema</schema> <schema>state-schema</schema>
</datastore> </datastore>
<checksum>75a43df9bd56b92aacc156a2958fbe12312fb285</checksum> <content-id>75a43df9bd56b92aacc156a2958fbe12312fb285</content-id>
</yang-library> </yang-library>
Appendix C. Example YANG Library Instance for an Advanced Server Appendix C. Example YANG Library Instance for an Advanced Server
The following example extends the preceding Basic Server YANG Library The following example extends the preceding Basic Server YANG Library
example, by using modules from [RFC8345] and [RFC8349], to illustrate example, by using modules from [RFC8345] and [RFC8349], to illustrate
a slightly more advanced server that: a slightly more advanced server that:
o Has a module with features only enabled in <operational>; the o Has a module with features only enabled in <operational>; the
"ietf-routing module" is supported in <running>, <startup>, and "ietf-routing module" is supported in <running>, <startup>, and
skipping to change at page 31, line 28 skipping to change at page 31, line 28
</datastore> </datastore>
<datastore> <datastore>
<name>ex-ds-eph:ds-ephemeral</name> <name>ex-ds-eph:ds-ephemeral</name>
<schema>dynamic-config-schema</schema> <schema>dynamic-config-schema</schema>
</datastore> </datastore>
<datastore> <datastore>
<name>ds:operational</name> <name>ds:operational</name>
<schema>state-schema</schema> <schema>state-schema</schema>
</datastore> </datastore>
<checksum>14782ab9bd56b92aacc156a2958fbe12312fb285</checksum> <content-id>14782ab9bd56b92aacc156a2958fbe12312fb285</content-id>
</yang-library> </yang-library>
Authors' Addresses Authors' Addresses
Andy Bierman Andy Bierman
YumaWorks YumaWorks
Email: andy@yumaworks.com Email: andy@yumaworks.com
Martin Bjorklund Martin Bjorklund
 End of changes. 47 change blocks. 
80 lines changed or deleted 71 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/