| RFC 8525 | YANG Library | January 2019 |
| Bierman, et al. | Standards Track | [Page] |
This document describes a YANG library that provides information aboutthe YANG modules, datastores, and datastore schemas used by a networkmanagement server. Simple caching mechanisms are provided to allowclients to minimize retrieval of this information. This version of theYANG library supports the Network Management Datastore Architecture (NMDA) bylisting all datastores supported by a network management server andthe schema that is used by each of these datastores.¶
This document obsoletes RFC 7895.¶
This is an Internet Standards Track document.¶
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.¶
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained athttps://www.rfc-editor.org/info/rfc8525.¶
Copyright (c) 2019 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.¶
There is a need for a standard mechanism to expose which YANG modules[RFC7950], datastores[RFC8342], and datastore schemas[RFC8342] are in use by a networkmanagement server.¶
This document defines the YANG module "ietf‑yang‑library" thatprovides this information. This version of the YANG library iscompatible with the Network Management Datastore Architecture (NMDA)[RFC8342]. The previous version of the YANGlibrary, defined in[RFC7895], is not compatible with the NMDA sinceit assumes that all datastores have exactly the same schema. This isnot necessarily true in the NMDA since dynamic configuration datastoresmay have their own datastore schema. Furthermore, the operationalstate datastore may support non-configurable YANG modules in additionto the YANG modules supported by conventional configurationdatastores.¶
The old YANG library definitions have been retained (forbackwards-compatibility reasons), but the definitions have been marked asdeprecated. For backwards compatibility, an NMDA-supporting serverSHOULD populate the deprecated "/modules‑state" tree in abackwards-compatible manner. The new "/yang‑library" tree will beignored by legacy clients but will provide all the data needed forNMDA-aware clients (which will ignore the "/modules‑state"tree). The recommended approach to populate "/modules-state" is to report the YANG modules with "config true" data nodes that are configurable via conventional configuration datastores and the YANG modules with "config false" data nodes that are returned via a Network Configuration Protocol (NETCONF) <get>operation or equivalent.¶
The YANG library information can be different on every server, and itcan change at runtime or across a server reboot. If a serverimplements multiple network management protocols to access theserver's datastores, then each such protocol may have its ownconceptual instantiation of the YANG library.¶
If a large number of YANG modules are utilized by a server, then theYANG library contents can be relatively large. Since the YANG librarycontents change very infrequently, it is important that clients beable to cache the YANG library contents and easily identify whethertheir cache is out of date.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14[RFC2119][RFC8174] when, and only when, they appear in all capitals, as shown here.¶
The following terms are defined in[RFC7950]:¶
This document uses the phrase "implement a module" as defined inSection 5.6.5 of[RFC7950].¶
The following terms are defined in[RFC8342]:¶
The following terms are used within this document:¶
Tree diagrams in this document use the notation defined in[RFC8340].¶
The following information is needed by a client application (for eachYANG module in the library) to fully utilize the YANG data modelinglanguage:¶
In addition, the following information is needed by a clientapplication for each datastore supported by a server:¶
In order to select one out of several possible designs for the YANG library data model, the following criteria were used:¶
The "ietf‑yang‑library" YANG module provides information about themodules, submodules, datastores, and datastore schemas supported by aserver. All data nodes in the "ietf‑yang‑library" module are"config false" andthus only accessible in the operational state datastore.¶
+-----------+| datastore |+-----------+ | | has a V+-----------+ +--------+ +------------+| datastore | union of | module | consists of | modules + || schema |----------->| set |--------------->| submodules |+-----------+ +--------+ +------------+
The conceptual model of the YANG library is depicted inFigure 1. Following the NMDA, every datastore has an associated datastoreschema. A datastore schema is a union of module sets, and every moduleset is a collection of modules and submodules, including the modulesand submodules used for imports. Note that multiple datastores mayrefer to the same datastore schema. Furthermore, it is possible forindividual datastore schemas to share module sets. A common use case is theoperational state datastore schema, which is a superset of the schemaused by conventional configuration datastores.¶
Below is the YANG tree diagram for the "ietf‑yang‑library" module,excluding the deprecated "/modules‑state" tree:¶
module: ietf-yang-library +--ro yang-library +--ro module-set* [name] | +--ro name string | +--ro module* [name] | | +--ro name yang:yang-identifier | | +--ro revision? revision-identifier | | +--ro namespace inet:uri | | +--ro location* inet:uri | | +--ro submodule* [name] | | | +--ro name yang:yang-identifier | | | +--ro revision? revision-identifier | | | +--ro location* inet:uri | | +--ro feature* yang:yang-identifier | | +--ro deviation* -> ../../module/name | +--ro import-only-module* [name revision] | +--ro name yang:yang-identifier | +--ro revision union | +--ro namespace inet:uri | +--ro location* inet:uri | +--ro submodule* [name] | +--ro name yang:yang-identifier | +--ro revision? revision-identifier | +--ro location* inet:uri +--ro schema* [name] | +--ro name string | +--ro module-set* -> ../../module-set/name +--ro datastore* [name] | +--ro name ds:datastore-ref | +--ro schema -> ../../schema/name +--ro content-id string notifications: +---n yang-library-update +--ro content-id -> /yang-library/content-id¶
The "/yang‑library" container holds the entire YANG library. Thecontainer has the following child nodes:¶
Note that for a NETCONF server implementing the NETCONF extensions tosupport the NMDA[RFC8526], a change of the YANGlibrary content identifier results in a new value for the:yang-library:1.1 capability defined in[RFC8526]. Thus, if such a server implementsNETCONF notifications[RFC5277] and the "netconf‑capability‑change" notification[RFC6470], a"netconf‑capability‑change"notification is generated whenever the YANG library content identifierchanges.¶
The "ietf‑yang‑library" YANG module imports definitions fromthe "ietf‑yang‑types" and"ietf‑inet‑types" modules defined in[RFC6991] andfrom the"ietf‑datastores" module defined in[RFC8342]. While the YANG module is defined using YANG version 1.1, the YANG library supports YANG modules written in any version of YANG.¶
Adding SVG diagram for testing purposes.¶
<CODE BEGINS> file "ietf-yang-library@2019-01-04.yang"¶
module ietf-yang-library { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-yang-library"; prefix yanglib; import ietf-yang-types { prefix yang; reference "RFC 6991: Common YANG Data Types"; } import ietf-inet-types { prefix inet; reference "RFC 6991: Common YANG Data Types"; } import ietf-datastores { prefix ds; reference "RFC 8342: Network Management Datastore Architecture (NMDA)"; } organization "IETF NETCONF (Network Configuration) Working Group"; contact "WG Web: <https://datatracker.ietf.org/wg/netconf/> WG List: <mailto:netconf@ietf.org> Author: Andy Bierman <mailto:andy@yumaworks.com> Author: Martin Bjorklund <mailto:mbj@tail-f.com> Author: Juergen Schoenwaelder <mailto:j.schoenwaelder@jacobs-university.de> Author: Kent Watsen <mailto:kwatsen@juniper.net> Author: Rob Wilton <mailto:rwilton@cisco.com>"; description "This module provides information about the YANG modules, datastores, and datastore schemas used by a network management server. Copyright (c) 2019 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC 8525; see the RFC itself for full legal notices."; revision 2019-01-04 { description "Added support for multiple datastores according to the Network Management Datastore Architecture (NMDA)."; reference "RFC 8525: YANG Library"; } revision 2016-04-09 { description "Initial revision."; reference "RFC 7895: YANG Module Library"; } /* * Typedefs */ typedef revision-identifier { type string { pattern '\d{4}-\d{2}-\d{2}'; } description "Represents a specific date in YYYY-MM-DD format."; } /* * Groupings */ grouping module-identification-leafs { description "Parameters for identifying YANG modules and submodules."; leaf name { type yang:yang-identifier; mandatory true; description "The YANG module or submodule name."; } leaf revision { type revision-identifier; description "The YANG module or submodule revision date. If no revision statement is present in the YANG module or submodule, this leaf is not instantiated."; } } grouping location-leaf-list { description "Common leaf-list parameter for the locations of modules and submodules."; leaf-list location { type inet:uri; description "Contains a URL that represents the YANG schema resource for this module or submodule. This leaf will only be present if there is a URL available for retrieval of the schema for this entry."; } } grouping module-implementation-parameters { description "Parameters for describing the implementation of a module."; leaf-list feature { type yang:yang-identifier; description "List of all YANG feature names from this module that are supported by the server, regardless whether they are defined in the module or any included submodule."; } leaf-list deviation { type leafref { path "../../module/name"; } description "List of all YANG deviation modules used by this server to modify the conformance of the module associated with this entry. Note that the same module can be used for deviations for multiple modules, so the same entry MAY appear within multiple 'module' entries. This reference MUST NOT (directly or indirectly) refer to the module being deviated. Robust clients may want to make sure that they handle a situation where a module deviates itself (directly or indirectly) gracefully."; } } grouping module-set-parameters { description "A set of parameters that describe a module set."; leaf name { type string; description "An arbitrary name of the module set."; } list module { key "name"; description "An entry in this list represents a module implemented by the server, as per Section 5.6.5 of RFC 7950, with a particular set of supported features and deviations."; reference "RFC 7950: The YANG 1.1 Data Modeling Language"; uses module-identification-leafs; leaf namespace { type inet:uri; mandatory true; description "The XML namespace identifier for this module."; } uses location-leaf-list; list submodule { key "name"; description "Each entry represents one submodule within the parent module."; uses module-identification-leafs; uses location-leaf-list; } uses module-implementation-parameters; } list import-only-module { key "name revision"; description "An entry in this list indicates that the server imports reusable definitions from the specified revision of the module but does not implement any protocol-accessible objects from this revision. Multiple entries for the same module name MAY exist. This can occur if multiple modules import the same module but specify different revision dates in the import statements."; leaf name { type yang:yang-identifier; description "The YANG module name."; } leaf revision { type union { type revision-identifier; type string { length "0"; } } description "The YANG module revision date. A zero-length string is used if no revision statement is present in the YANG module."; } leaf namespace { type inet:uri; mandatory true; description "The XML namespace identifier for this module."; } uses location-leaf-list; list submodule { key "name"; description "Each entry represents one submodule within the parent module."; uses module-identification-leafs; uses location-leaf-list; } } } grouping yang-library-parameters { description "The YANG library data structure is represented as a grouping so it can be reused in configuration or another monitoring data structure."; list module-set { key "name"; description "A set of modules that may be used by one or more schemas. A module set does not have to be referentially complete, i.e., it may define modules that contain import statements for other modules not included in the module set."; uses module-set-parameters; } list schema { key "name"; description "A datastore schema that may be used by one or more datastores. The schema must be valid and referentially complete, i.e., it must contain modules to satisfy all used import statements for all modules specified in the schema."; leaf name { type string; description "An arbitrary name of the schema."; } leaf-list module-set { type leafref { path "../../module-set/name"; } description "A set of module-sets that are included in this schema. If a non-import-only module appears in multiple module sets, then the module revision and the associated features and deviations must be identical."; } } list datastore { key "name"; description "A datastore supported by this server. Each datastore indicates which schema it supports. The server MUST instantiate one entry in this list per specific datastore it supports. Each datastore entry with the same datastore schema SHOULD reference the same schema."; leaf name { type ds:datastore-ref; description "The identity of the datastore."; } leaf schema { type leafref { path "../../schema/name"; } mandatory true; description "A reference to the schema supported by this datastore. All non-import-only modules of the schema are implemented with their associated features and deviations."; } } } /* * Top-level container */ container yang-library { config false; description "Container holding the entire YANG library of this server."; uses yang-library-parameters; leaf content-id { type string; mandatory true; description "A server-generated identifier of the contents of the '/yang-library' tree. The server MUST change the value of this leaf if the information represented by the '/yang-library' tree, except '/yang-library/content-id', has changed."; } } /* * Notifications */ notification yang-library-update { description "Generated when any YANG library information on the server has changed."; leaf content-id { type leafref { path "/yanglib:yang-library/yanglib:content-id"; } mandatory true; description "Contains the YANG library content identifier for the updated YANG library at the time the notification is generated."; } } /* * Legacy groupings */ grouping module-list { status deprecated; description "The module data structure is represented as a grouping so it can be reused in configuration or another monitoring data structure."; grouping common-leafs { status deprecated; description "Common parameters for YANG modules and submodules."; leaf name { type yang:yang-identifier; status deprecated; description "The YANG module or submodule name."; } leaf revision { type union { type revision-identifier; type string { length "0"; } } status deprecated; description "The YANG module or submodule revision date. A zero-length string is used if no revision statement is present in the YANG module or submodule."; } } grouping schema-leaf { status deprecated; description "Common schema leaf parameter for modules and submodules."; leaf schema { type inet:uri; description "Contains a URL that represents the YANG schema resource for this module or submodule. This leaf will only be present if there is a URL available for retrieval of the schema for this entry."; } } list module { key "name revision"; status deprecated; description "Each entry represents one revision of one module currently supported by the server."; uses common-leafs { status deprecated; } uses schema-leaf { status deprecated; } leaf namespace { type inet:uri; mandatory true; status deprecated; description "The XML namespace identifier for this module."; } leaf-list feature { type yang:yang-identifier; status deprecated; description "List of YANG feature names from this module that are supported by the server, regardless of whether they are defined in the module or any included submodule."; } list deviation { key "name revision"; status deprecated; description "List of YANG deviation module names and revisions used by this server to modify the conformance of the module associated with this entry. Note that the same module can be used for deviations for multiple modules, so the same entry MAY appear within multiple 'module' entries. The deviation module MUST be present in the 'module' list, with the same name and revision values. The 'conformance-type' value will be 'implement' for the deviation module."; uses common-leafs { status deprecated; } } leaf conformance-type { type enumeration { enum implement { description "Indicates that the server implements one or more protocol-accessible objects defined in the YANG module identified in this entry. This includes deviation statements defined in the module. For YANG version 1.1 modules, there is at most one 'module' entry with conformance type 'implement' for a particular module name, since YANG 1.1 requires that at most one revision of a module is implemented. For YANG version 1 modules, there SHOULD NOT be more than one 'module' entry for a particular module name."; } enum import { description "Indicates that the server imports reusable definitions from the specified revision of the module but does not implement any protocol-accessible objects from this revision. Multiple 'module' entries for the same module name MAY exist. This can occur if multiple modules import the same module but specify different revision dates in the import statements."; } } mandatory true; status deprecated; description "Indicates the type of conformance the server is claiming for the YANG module identified by this entry."; } list submodule { key "name revision"; status deprecated; description "Each entry represents one submodule within the parent module."; uses common-leafs { status deprecated; } uses schema-leaf { status deprecated; } } } } /* * Legacy operational state data nodes */ container modules-state { config false; status deprecated; description "Contains YANG module monitoring information."; leaf module-set-id { type string; mandatory true; status deprecated; description "Contains a server-specific identifier representing the current set of modules and submodules. The server MUST change the value of this leaf if the information represented by the 'module' list instances has changed."; } uses module-list { status deprecated; } } /* * Legacy notifications */ notification yang-library-change { status deprecated; description "Generated when the set of modules and submodules supported by the server has changed."; leaf module-set-id { type leafref { path "/yanglib:modules-state/yanglib:module-set-id"; } mandatory true; status deprecated; description "Contains the module-set-id value representing the set of modules and submodules supported at the server at the time the notification is generated."; } }}¶<CODE ENDS>¶
RFC 7895 previously registered one URI in the "IETF XML Registry"[RFC3688]. This document takes over this registration entry made byRFC 7895 and changes the Registrant Contact to the IESG according to Section 4of[RFC3688].¶
URI: urn:ietf:params:xml:ns:yang:ietf-yang-library Registrant Contact: The IESG. XML: N/A, the requested URI is an XML namespace.¶
This document registers a YANG module in the "YANG ModuleNames" registry[RFC6020]:¶
name: ietf-yang-library namespace: urn:ietf:params:xml:ns:yang:ietf-yang-library prefix: yanglib reference: RFC 7895¶
This document takes over this registration entry made by RFC 7895.¶
The YANG module specified in this document defines a schema for data that isdesigned to be accessed via network management protocols such as NETCONF[RFC6241] or RESTCONF[RFC8040]. The lowest NETCONF layer is the secure transport layer, and themandatory-to-implement secure transport is Secure Shell (SSH)[RFC6242]. The lowest RESTCONF layer is HTTPS, and themandatory-to-implement secure transport is TLS[RFC8446].¶
The Network Configuration Access Control Model (NACM)[RFC8341] provides the means to restrict access for particular NETCONF or RESTCONF usersto a preconfigured subset of all available NETCONF or RESTCONF protocoloperations and content.¶
Some of the readable data nodes in this YANG module may be consideredsensitive or vulnerable in some network environments. It is thus important tocontrol read access (e.g., via get, get-config, or notification) to these datanodes. These are the subtrees and data nodes and theirsensitivity/vulnerability:¶
The "/yang‑library" subtree of the YANG library may help an attackeridentify the server capabilities and server implementations with knownbugs since the set of YANG modules supported by a server may revealthe kind of device and the manufacturer of the device. Although someof this information may be available to all NETCONF users via theNETCONF <hello> message (or similar messages in other managementprotocols), this YANG module potentially exposes additional detailsthat could be of some assistance to an attacker. Servervulnerabilities may be specific to particular modules, modulerevisions, module features, or even module deviations. For example, ifa particular operation on a particular data node is known to cause aserver to crash or significantly degrade device performance, then the"module" list information will help an attacker identify serverimplementations with such a defect, in order to launch adenial-of-service attack on the device.¶
This document changes[RFC7895] in the following ways:¶
The following example shows the YANG library of a basic serverimplementing the "ietf‑interfaces"[RFC8343] and"ietf‑ip"[RFC8344] modules in the <running>,<startup>, and <operational> datastores and the "ietf‑hardware"[RFC8348] module in the <operational> datastore.¶
Newline characters in leaf values are added for formatting reasons.¶
<yang-library xmlns="urn:ietf:params:xml:ns:yang:ietf-yang-library" xmlns:ds="urn:ietf:params:xml:ns:yang:ietf-datastores"> <module-set> <name>config-modules</name> <module> <name>ietf-interfaces</name> <revision>2018-02-20</revision> <namespace> urn:ietf:params:xml:ns:yang:ietf-interfaces </namespace> </module> <module> <name>ietf-ip</name> <revision>2018-02-22</revision> <namespace> urn:ietf:params:xml:ns:yang:ietf-ip </namespace> </module> <import-only-module> <name>ietf-yang-types</name> <revision>2013-07-15</revision> <namespace> urn:ietf:params:xml:ns:yang:ietf-yang-types </namespace> </import-only-module> <import-only-module> <name>ietf-inet-types</name> <revision>2013-07-15</revision> <namespace> urn:ietf:params:xml:ns:yang:ietf-inet-types </namespace> </import-only-module> </module-set> <module-set> <name>state-modules</name> <module> <name>ietf-hardware</name> <revision>2018-03-13</revision> <namespace> urn:ietf:params:xml:ns:yang:ietf-hardware </namespace> </module> <import-only-module> <name>ietf-inet-types</name> <revision>2013-07-15</revision> <namespace> urn:ietf:params:xml:ns:yang:ietf-inet-types </namespace> </import-only-module> <import-only-module> <name>ietf-yang-types</name> <revision>2013-07-15</revision> <namespace> urn:ietf:params:xml:ns:yang:ietf-yang-types </namespace> </import-only-module> <import-only-module> <name>iana-hardware</name> <revision>2018-03-13</revision> <namespace> urn:ietf:params:xml:ns:yang:iana-hardware </namespace> </import-only-module> </module-set> <schema> <name>config-schema</name> <module-set>config-modules</module-set> </schema> <schema> <name>state-schema</name> <module-set>config-modules</module-set> <module-set>state-modules</module-set> </schema> <datastore> <name>ds:startup</name> <schema>config-schema</schema> </datastore> <datastore> <name>ds:running</name> <schema>config-schema</schema> </datastore> <datastore> <name>ds:operational</name> <schema>state-schema</schema> </datastore> <content-id>75a43df9bd56b92aacc156a2958fbe12312fb285</content-id></yang-library>¶
The following example extends the example inAppendix B by using modules from[RFC8345] and[RFC8349] to illustratea slightly more advanced server that:¶
<yang-library xmlns="urn:ietf:params:xml:ns:yang:ietf-yang-library" xmlns:ds="urn:ietf:params:xml:ns:yang:ietf-datastores" xmlns:ex-ds-eph="urn:example:ds-ephemeral"> <module-set> <name>config-state-modules</name> <module> <name>ietf-interfaces</name> <revision>2018-02-20</revision> <namespace> urn:ietf:params:xml:ns:yang:ietf-interfaces </namespace> </module> <module> <name>ietf-ip</name> <revision>2018-02-22</revision> <namespace> urn:ietf:params:xml:ns:yang:ietf-ip </namespace> </module> <module> <name>ietf-routing</name> <revision>2018-03-13</revision> <namespace> urn:ietf:params:xml:ns:yang:ietf-routing </namespace> </module> <import-only-module> <name>ietf-yang-types</name> <revision>2013-07-15</revision> <namespace> urn:ietf:params:xml:ns:yang:ietf-yang-types </namespace> </import-only-module> <import-only-module> <name>ietf-inet-types</name> <revision>2013-07-15</revision> <namespace> urn:ietf:params:xml:ns:yang:ietf-inet-types </namespace> </import-only-module> </module-set> <module-set> <name>config-only-modules</name> <module> <name>ietf-routing</name> <revision>2018-03-13</revision> <namespace> urn:ietf:params:xml:ns:yang:ietf-routing </namespace> </module> </module-set> <module-set> <name>dynamic-config-state-modules</name> <module> <name>ietf-network</name> <revision>2018-02-26</revision> <namespace> urn:ietf:params:xml:ns:yang:ietf-network </namespace> </module> <module> <name>ietf-network-topology</name> <revision>2018-02-26</revision> <namespace> urn:ietf:params:xml:ns:yang:ietf-network-topology </namespace> </module> <import-only-module> <name>ietf-inet-types</name> <revision>2013-07-15</revision> <namespace> urn:ietf:params:xml:ns:yang:ietf-inet-types </namespace> </import-only-module> </module-set> <module-set> <name>state-only-modules</name> <module> <name>ietf-hardware</name> <revision>2018-03-13</revision> <namespace> urn:ietf:params:xml:ns:yang:ietf-hardware </namespace> <deviation>example-vendor-hardware-deviations</deviation> </module> <module> <name>ietf-routing</name> <revision>2018-03-13</revision> <namespace> urn:ietf:params:xml:ns:yang:ietf-routing </namespace> <feature>multiple-ribs</feature> <feature>router-id</feature> </module> <module> <name>example-vendor-hardware-deviations</name> <revision>2018-01-31</revision> <namespace> urn:example:example-vendor-hardware-deviations </namespace> </module> <import-only-module> <name>ietf-inet-types</name> <revision>2013-07-15</revision> <namespace> urn:ietf:params:xml:ns:yang:ietf-inet-types </namespace> </import-only-module> <import-only-module> <name>ietf-yang-types</name> <revision>2013-07-15</revision> <namespace> urn:ietf:params:xml:ns:yang:ietf-yang-types </namespace> </import-only-module> <import-only-module> <name>iana-hardware</name> <revision>2018-03-13</revision> <namespace> urn:ietf:params:xml:ns:yang:iana-hardware </namespace> </import-only-module> </module-set> <schema> <name>config-schema</name> <module-set>config-state-modules</module-set> <module-set>config-only-modules</module-set> </schema> <schema> <name>dynamic-config-schema</name> <module-set>dynamic-config-state-modules</module-set> </schema> <schema> <name>state-schema</name> <module-set>config-state-modules</module-set> <module-set>dynamic-config-state-modules</module-set> <module-set>state-only-modules</module-set> </schema> <datastore> <name>ds:startup</name> <schema>config-schema</schema> </datastore> <datastore> <name>ds:running</name> <schema>config-schema</schema> </datastore> <datastore> <name>ex-ds-eph:ds-ephemeral</name> <schema>dynamic-config-schema</schema> </datastore> <datastore> <name>ds:operational</name> <schema>state-schema</schema> </datastore> <content-id>14782ab9bd56b92aacc156a2958fbe12312fb285</content-id></yang-library>¶