draft-ietf-netconf-rfc7895bis-05.txt   draft-ietf-netconf-rfc7895bis-06.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: August 31, 2018 J. Schoenwaelder Expires: October 11, 2018 J. Schoenwaelder
Jacobs University Jacobs University
K. Watsen K. Watsen
Juniper Networks Juniper Networks
R. Wilton R. Wilton
Cisco Systems Cisco Systems
February 27, 2018 April 9, 2018
YANG Library YANG Library
draft-ietf-netconf-rfc7895bis-05 draft-ietf-netconf-rfc7895bis-06
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 August 31, 2018. This Internet-Draft will expire on October 11, 2018.
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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
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
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
3. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. YANG Library Data Model . . . . . . . . . . . . . . . . . . . 6 3. YANG Library Data Model . . . . . . . . . . . . . . . . . . . 6
5. YANG Library YANG Module . . . . . . . . . . . . . . . . . . 8 4. YANG Library YANG Module . . . . . . . . . . . . . . . . . . 8
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
7. Security Considerations . . . . . . . . . . . . . . . . . . . 21 6. Security Considerations . . . . . . . . . . . . . . . . . . . 21
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 22
9.1. Normative References . . . . . . . . . . . . . . . . . . 22 8.1. Normative References . . . . . . . . . . . . . . . . . . 22
9.2. Informative References . . . . . . . . . . . . . . . . . 23 8.2. Informative References . . . . . . . . . . . . . . . . . 23
Appendix A. Summary of Changes from RFC 7895 . . . . . . . . . . 25 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
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 31 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 31
1. Introduction 1. Introduction
There is a need for a standard mechanism to expose which YANG modules There is a need for a standard mechanism to expose which YANG modules
[RFC7950], datastores and datastore schemas [RFC7950], datastores and datastore schemas [RFC8342] are in use by a
[I-D.ietf-netmod-revised-datastores] are in use by a network network management server.
management server.
This document defines the YANG module "ietf-yang-library" that This document defines the YANG module "ietf-yang-library" that
provides this information. This version of the YANG library is provides this information. This version of the YANG library is
compatible with the Network Management Datastore Architecture (NMDA) compatible with the Network Management Datastore Architecture (NMDA)
[I-D.ietf-netmod-revised-datastores]. The previous version of the [RFC8342]. The previous version of the YANG library, defined in
YANG library, defined in [RFC7895], is not compatible with the NMDA [RFC7895], is not compatible with the NMDA since it assumes that all
since it assumes that all datastores have exactly the same schema. datastores have exactly the same schema. This is not necessarily
This is not necessarily true in the NMDA since dynamic configuration true in the NMDA since dynamic configuration datastores may have
datastores may have their own datastore schema. Furthermore, the their own datastore schema. Furthermore, the operational state
operational state datastore may support non-configurable YANG modules datastore may support non-configurable YANG modules in addition to
in addition to the YANG modules supported by conventional the YANG modules supported by conventional configuration datastores.
configuration datastores.
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
skipping to change at page 3, line 35 skipping to change at page 3, line 34
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 All NETCONF servers supporting YANG 1.1 [RFC7950] are required to
support YANG Library (see Section 5.6.4 of RFC 7950). NETCONF support YANG Library (see Section 5.6.4 of RFC 7950). NETCONF
servers implementing the NETCONF extensions to support the NMDA servers implementing the NETCONF extensions to support the NMDA
[I-D.ietf-netconf-nmda-netconf] must implement at least the version [I-D.ietf-netconf-nmda-netconf] MUST implement at least the version
of the YANG library defined in this document. Similarly, all of the YANG library defined in this document. Similarly, all
RESTCONF servers are required to support YANG Library (see Section 10 RESTCONF servers are required to support YANG Library (see Section 10
of RFC 8040). RESTCONF servers implementing the RESTCONF extensions of RFC 8040). RESTCONF servers implementing the RESTCONF extensions
to support the NMDA [I-D.ietf-netconf-nmda-restconf] must implement to support the NMDA [I-D.ietf-netconf-nmda-restconf] MUST implement
at least the version of the YANG library defined in this document. at least the version of the YANG library defined in this document.
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 1.1. Terminology
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]. 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
2. Terminology
The following terms are defined in [RFC7950]: The following terms are defined in [RFC7950]:
o module o module
o submodule o submodule
o data node o data node
This document uses the phrase "implementing a module" as defined in This document uses the phrase "implementing a module" as defined in
[RFC7950] Section 5.6.5. [RFC7950] Section 5.6.5.
The following terms are defined in The following terms are defined in [RFC8342]:
[I-D.ietf-netmod-revised-datastores]:
o datastore o datastore
o datastore schema o datastore schema
o configuration o configuration
o configuration datastore o configuration datastore
o conventional configuration o conventional configuration
skipping to change at page 4, line 43 skipping to change at page 4, line 42
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 checksum: A server-generated checksum of the contents
of the YANG library. 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
[I-D.ietf-netmod-yang-tree-diagrams]. [RFC8340].
3. 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: Each YANG module and submodule within the library SHOULD
have a revision. This is derived from the most recent revision have a revision. This is derived from the most recent revision
statement within the module or submodule. statement within the 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.
In addition, the following information is needed by a client In addition, the following information is needed by a client
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,
skipping to change at page 6, line 8 skipping to change at page 6, line 8
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 datastores, 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. Make it possible to use the YANG library by schema mount
[I-D.ietf-netmod-schema-mount]. [I-D.ietf-netmod-schema-mount].
4. 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.
+-----------+ +-----------+
| datastore | | datastore |
+-----------+ +-----------+
| |
skipping to change at page 8, line 42 skipping to change at page 8, line 42
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 checksum 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 checksum changes.
5. 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 [I-D.ietf-netmod-revised-datastores]. "ietf-datastores" defined in [RFC8342]. While the YANG module is
While the YANG module is defined using YANG version 1.1, the YANG defined using YANG version 1.1, the YANG library supports 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-02-21.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";
skipping to change at page 11, line 45 skipping to change at page 11, line 45
} }
} }
grouping implementation-parameters { grouping 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 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.";
} }
leaf-list deviation { leaf-list deviation {
type leafref { type leafref {
path "../../module/name"; path "../../module/name";
} }
description description
"List of YANG deviation modules used by this server to modify "List of all YANG deviation modules used by this server to
the conformance of the module associated with this entry. modify the conformance of the module associated with this
Note that the same module can be used for deviations for entry. Note that the same module can be used for deviations
multiple modules, so the same entry MAY appear within for multiple modules, so the same entry MAY appear within
multiple 'module' entries. multiple 'module' entries.
This reference MUST NOT (directly or indirectly) This reference MUST NOT (directly or indirectly)
refer to the module being deviated. refer to the module being deviated.
Robust clients may want to make sure that they handle a Robust clients may want to make sure that they handle a
situation where a module deviates itself (directly or situation where a module deviates itself (directly or
indirectly) gracefully."; indirectly) gracefully.";
} }
} }
skipping to change at page 21, line 5 skipping to change at page 21, line 5
"Contains the module-set-id value representing the "Contains the module-set-id value representing the
set of modules and submodules supported at the server set of modules and submodules supported at the server
at the time the notification is generated."; at the time the notification is generated.";
} }
} }
} }
<CODE ENDS> <CODE ENDS>
6. IANA Considerations 5. IANA Considerations
RFC 7895 previously registered one URI in the IETF XML registry RFC 7895 previously registered one URI in the IETF XML registry
[RFC3688]. This document takes over this registration entry made by [RFC3688]. This document takes over this registration entry made by
RFC 7895 and changes the Registrant to the IESG according to RFC 7895 and changes the Registrant to the IESG according to
Section 4 in [RFC3688]. Section 4 in [RFC3688].
URI: urn:ietf:params:xml:ns:yang:ietf-yang-library URI: urn:ietf:params:xml:ns:yang:ietf-yang-library
Registrant Contact: The IESG. Registrant Contact: The IESG.
skipping to change at page 21, line 28 skipping to change at page 21, line 28
RFC 7895 previously registered one YANG module in the "YANG Module RFC 7895 previously registered one YANG module in the "YANG Module
Names" registry [RFC6020] as follows: Names" registry [RFC6020] as follows:
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
reference: RFC 7895 reference: RFC 7895
This document takes over this registration entry made by RFC 7895. This document takes over this registration entry made by RFC 7895.
7. 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]. [RFC5246].
The NETCONF access control model [RFC6536] provides the means to The NETCONF access control model [RFC6536] provides the means to
skipping to change at page 22, line 17 skipping to change at page 22, line 17
management protocols), this YANG module potentially exposes management protocols), this YANG module potentially exposes
additional details that could be of some assistance to an attacker. additional details that could be of some assistance to an attacker.
Server vulnerabilities may be specific to particular modules, module Server vulnerabilities may be specific to particular modules, module
revisions, module features, or even module deviations. For example, revisions, module features, or even module deviations. For example,
if a particular operation on a particular data node is known to cause if a particular operation on a particular data node is known to cause
a server to crash or significantly degrade device performance, then a 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-of-
service attack on the device. service attack on the device.
8. Acknowledgments 7. Acknowledgments
Contributions to this material by Andy Bierman are based upon work Contributions to this material by Andy Bierman are based upon work
supported by the The Space & Terrestrial Communications Directorate supported by the The Space & Terrestrial Communications Directorate
(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).
9. References 8. References
9.1. Normative References
[I-D.ietf-netmod-revised-datastores] 8.1. Normative References
Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore
Architecture", draft-ietf-netmod-revised-datastores-10
(work in progress), January 2018.
[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, DOI 10.17487/
RFC2119, March 1997, <https://www.rfc-editor.org/info/ RFC2119, March 1997, <https://www.rfc-editor.org/info/
rfc2119>. 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>.
skipping to change at page 23, line 36 skipping to change at page 23, line 26
editor.org/info/rfc6991>. 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>.
9.2. Informative References [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[I-D.ietf-i2rs-yang-network-topo] [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
Clemm, A., Medved, J., Varga, R., Bahadur, N., and R. Wilton, "Network Management Datastore Architecture
Ananthakrishnan, H., and X. Liu, "A Data Model for Network (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
Topologies", draft-ietf-i2rs-yang-network-topo-20 (work in <https://www.rfc-editor.org/info/rfc8342>.
progress), December 2017.
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-03 (work in progress), February 2018. nmda-netconf-04 (work in progress), March 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-02 (work in progress), January 2018. nmda-restconf-03 (work in progress), March 2018.
[I-D.ietf-netmod-entity]
Bierman, A., Bjorklund, M., Dong, J., and D. Romascanu, "A
YANG Data Model for Hardware Management", draft-ietf-
netmod-entity-08 (work in progress), January 2018.
[I-D.ietf-netmod-rfc7223bis]
Bjorklund, M., "A YANG Data Model for Interface
Management", draft-ietf-netmod-rfc7223bis-03 (work in
progress), January 2018.
[I-D.ietf-netmod-rfc7277bis]
Bjorklund, M., "A YANG Data Model for IP Management",
draft-ietf-netmod-rfc7277bis-03 (work in progress),
January 2018.
[I-D.ietf-netmod-rfc8022bis]
Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for
Routing Management (NMDA Version)", draft-ietf-netmod-
rfc8022bis-11 (work in progress), January 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-08 (work in progress), October ietf-netmod-schema-mount-09 (work in progress), March
2017. 2018.
[I-D.ietf-netmod-yang-tree-diagrams]
Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft-
ietf-netmod-yang-tree-diagrams-06 (work in progress),
February 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>.
[RFC7895] Bierman, A., Bjorklund, M., and K. Watsen, "YANG Module [RFC7895] Bierman, A., Bjorklund, M., and K. Watsen, "YANG Module
Library", RFC 7895, DOI 10.17487/RFC7895, June 2016, Library", RFC 7895, DOI 10.17487/RFC7895, June 2016,
<https://www.rfc-editor.org/info/rfc7895>. <https://www.rfc-editor.org/info/rfc7895>.
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>.
[RFC8343] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,
<https://www.rfc-editor.org/info/rfc8343>.
[RFC8344] Bjorklund, M., "A YANG Data Model for IP Management", RFC
8344, DOI 10.17487/RFC8344, March 2018, <https://www.rfc-
editor.org/info/rfc8344>.
[RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N.,
Ananthakrishnan, H., and X. Liu, "A YANG Data Model for
Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March
2018, <https://www.rfc-editor.org/info/rfc8345>.
[RFC8348] Bierman, A., Bjorklund, M., Dong, J., and D. Romascanu, "A
YANG Data Model for Hardware Management", RFC 8348, DOI
10.17487/RFC8348, March 2018, <https://www.rfc-
editor.org/info/rfc8348>.
[RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for
Routing Management (NMDA Version)", RFC 8349, DOI
10.17487/RFC8349, March 2018, <https://www.rfc-
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
YANG library providing information about module sets, schemas, and YANG library providing information about module sets, schemas, and
datastores. datastores.
skipping to change at page 25, line 37 skipping to change at page 25, line 30
o Deprecated the "/modules-state" tree. o Deprecated the "/modules-state" tree.
o Deprecated the "/module-list" grouping. o Deprecated the "/module-list" grouping.
o Deprecated the "/yang-library-change" notification. o Deprecated the "/yang-library-change" notification.
Appendix B. Example YANG Library Instance for a Basic Server Appendix B. Example YANG Library Instance for a Basic Server
The following example shows the YANG Library of a basic server The following example shows the YANG Library of a basic server
implementing the "ietf-interfaces" [I-D.ietf-netmod-rfc7223bis] and implementing the "ietf-interfaces" [RFC8343] and "ietf-ip" [RFC8344]
"ietf-ip" [I-D.ietf-netmod-rfc7277bis] modules in the <running>, modules in the <running>, <startup>, and <operational> datastores and
<startup>, and <operational> datastores and the "ietf-hardware" the "ietf-hardware" [RFC8348] module in the <operational> datastore.
[I-D.ietf-netmod-entity] module in the <operational> datastore.
Newlines in leaf values are added for formatting reasons. Newlines in leaf values are added for formatting reasons.
<yang-library <yang-library
xmlns="urn:ietf:params:xml:ns:yang:ietf-yang-library" xmlns="urn:ietf:params:xml:ns:yang:ietf-yang-library"
xmlns:ds="urn:ietf:params:xml:ns:yang:ietf-datastores"> xmlns:ds="urn:ietf:params:xml:ns:yang:ietf-datastores">
<module-set> <module-set>
<name>config-modules</name> <name>config-modules</name>
<module> <module>
skipping to change at page 27, line 45 skipping to change at page 27, line 37
<name>ds:operational</name> <name>ds:operational</name>
<schema>state-schema</schema> <schema>state-schema</schema>
</datastore> </datastore>
<checksum>75a43df9bd56b92aacc156a2958fbe12312fb285</checksum> <checksum>75a43df9bd56b92aacc156a2958fbe12312fb285</checksum>
</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 [I-D.ietf-netmod-rfc8022bis] and example, by using modules from [RFC8345] and [RFC8349], to illustrate
[I-D.ietf-i2rs-yang-network-topo], to illustrate a slightly more a slightly more advanced server that:
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
<operational>, but the "multiple-ribs" and "router-id" features <operational>, but the "multiple-ribs" and "router-id" features
are only enabled in <operational>. Hence the "router-id" leaf may are only enabled in <operational>. Hence the "router-id" leaf may
be read but not configured. be read but not configured.
o Supports a dynamic configuration datastore "example-ds-ephemeral", o Supports a dynamic configuration datastore "example-ds-ephemeral",
with only the "ietf-network" and "ietf-network-topology" modules with only the "ietf-network" and "ietf-network-topology" modules
configurable via a notional dynamic configuration protocol. configurable via a notional dynamic configuration protocol.
 End of changes. 35 change blocks. 
102 lines changed or deleted 97 lines changed or added

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