--- /dev/null
+<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="m-1">
+ <data xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring"><?xml version="1.0" encoding="UTF-8"?>
+<module name="ietf-yang-library"
+ xmlns="urn:ietf:params:xml:ns:yang:yin:1"
+ xmlns:yanglib="urn:ietf:params:xml:ns:yang:ietf-yang-library"
+ xmlns:yang="urn:ietf:params:xml:ns:yang:ietf-yang-types"
+ xmlns:inet="urn:ietf:params:xml:ns:yang:ietf-inet-types"
+ xmlns:ds="urn:ietf:params:xml:ns:yang:ietf-datastores">
+ <yang-version value="1.1"/>
+ <namespace uri="urn:ietf:params:xml:ns:yang:ietf-yang-library"/>
+ <prefix value="yanglib"/>
+ <import module="ietf-yang-types">
+ <prefix value="yang"/>
+ <reference>
+ <text>RFC 6991: Common YANG Data Types.</text>
+ </reference>
+ </import>
+ <import module="ietf-inet-types">
+ <prefix value="inet"/>
+ <reference>
+ <text>RFC 6991: Common YANG Data Types.</text>
+ </reference>
+ </import>
+ <import module="ietf-datastores">
+ <prefix value="ds"/>
+ <reference>
+ <text>I-D.ietf-revised-datastores:
+Network Management Datastore Architecture.</text>
+ </reference>
+ </import>
+ <organization>
+ <text>IETF NETCONF (Network Configuration) Working Group</text>
+ </organization>
+ <contact>
+ <text>WG Web: &lt;http://tools.ietf.org/wg/netconf/&gt;
+WG List: &lt;mailto:netconf@ietf.org&gt;
+
+Author: Andy Bierman
+ &lt;mailto:andy@yumaworks.com&gt;
+
+Author: Martin Bjorklund
+ &lt;mailto:mbj@tail-f.com&gt;
+
+Author: Kent Watsen
+ &lt;mailto:kwatsen@juniper.net&gt;</text>
+ </contact>
+ <description>
+ <text>This module contains information about the YANG server
+instance, including the modules and datastores the
+server supports, and which modules are present in
+which datastores.
+
+Copyright (c) 2017 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
+(http://trustee.ietf.org/license-info).
+
+This version of this YANG module is part of RFC XXXX; see
+the RFC itself for full legal notices.</text>
+ </description>
+ <revision date="2017-08-17">
+ <description>
+ <text>Updated revision.</text>
+ </description>
+ <reference>
+ <text>RFC XXXX: YANG Library.</text>
+ </reference>
+ </revision>
+ <revision date="2016-04-09">
+ <description>
+ <text>Initial revision.</text>
+ </description>
+ <reference>
+ <text>RFC 7895: YANG Module Library.</text>
+ </reference>
+ </revision>
+ <typedef name="revision-identifier">
+ <type name="string">
+ <pattern value="\d{4}-\d{2}-\d{2}"/>
+ </type>
+ <description>
+ <text>Represents a specific date in YYYY-MM-DD format.</text>
+ </description>
+ </typedef>
+ <grouping name="module-identification-leafs">
+ <description>
+ <text>Parameters for identifying YANG modules and submodules.</text>
+ </description>
+ <leaf name="name">
+ <type name="yang:yang-identifier"/>
+ <mandatory value="true"/>
+ <description>
+ <text>The YANG module or submodule name.</text>
+ </description>
+ </leaf>
+ <leaf name="revision">
+ <type name="union">
+ <type name="revision-identifier"/>
+ <type name="string">
+ <length value="0"/>
+ </type>
+ </type>
+ <mandatory value="true"/>
+ <description>
+ <text>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.</text>
+ </description>
+ </leaf>
+ </grouping>
+ <grouping name="schema-leaf">
+ <description>
+ <text>Common schema leaf parameter for modules and submodules.</text>
+ </description>
+ <leaf name="schema">
+ <type name="inet:uri"/>
+ <description>
+ <text>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.</text>
+ </description>
+ </leaf>
+ </grouping>
+ <grouping name="implementation-parameters">
+ <description>
+ <text>Parameters for describing the implementation of a module.</text>
+ </description>
+ <leaf-list name="feature">
+ <type name="yang:yang-identifier"/>
+ <description>
+ <text>List of YANG feature names from this module that are
+supported by the server, regardless whether they are defined
+in the module or any included submodule.</text>
+ </description>
+ </leaf-list>
+ <list name="deviation">
+ <key value="name revision"/>
+ <description>
+ <text>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.</text>
+ </description>
+ <uses name="module-identification-leafs"/>
+ </list>
+ <leaf name="conformance-type">
+ <type name="enumeration">
+ <enum name="implement">
+ <description>
+ <text>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.</text>
+ </description>
+ </enum>
+ <enum name="import">
+ <description>
+ <text>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.</text>
+ </description>
+ </enum>
+ </type>
+ <mandatory value="true"/>
+ <description>
+ <text>Indicates the type of conformance the server is claiming
+for the YANG module identified by this entry.</text>
+ </description>
+ </leaf>
+ </grouping>
+ <grouping name="yang-library-parameters">
+ <description>
+ <text>The YANG library data structure is represented as a grouping
+so it can be reused in configuration or another monitoring
+data structure.</text>
+ </description>
+ <container name="modules">
+ <description>
+ <text>A container holding a list of modules. Note, modules being
+listed here does not mean that they are supported by any
+particular datastore.</text>
+ </description>
+ <list name="module">
+ <key value="id"/>
+ <description>
+ <text>Each entry represents one revision of one module
+currently supported by the server.</text>
+ </description>
+ <leaf name="id">
+ <type name="string"/>
+ <description>
+ <text>A stable identifier, independent of any other part
+of this module instance.</text>
+ </description>
+ </leaf>
+ <uses name="module-identification-leafs"/>
+ <uses name="schema-leaf"/>
+ <leaf name="namespace">
+ <type name="inet:uri"/>
+ <mandatory value="true"/>
+ <description>
+ <text>The XML namespace identifier for this module.</text>
+ </description>
+ </leaf>
+ <uses name="implementation-parameters"/>
+ <list name="submodule">
+ <key value="name revision"/>
+ <description>
+ <text>Each entry represents one submodule within the
+parent module.</text>
+ </description>
+ <uses name="module-identification-leafs"/>
+ <uses name="schema-leaf"/>
+ </list>
+ </list>
+ </container>
+ <container name="module-sets">
+ <description>
+ <text>A container for a list of module-sets. Module-sets being
+listed here does not mean that they are used by any
+particular datastore.</text>
+ </description>
+ <list name="module-set">
+ <key value="id"/>
+ <description>
+ <text>An arbitrary module-set definition provided by the
+server.</text>
+ </description>
+ <leaf name="id">
+ <type name="string"/>
+ <description>
+ <text>A system-generated value that uniquely represents the
+referenced set of modules. Any change to the number
+of modules referenced, or to the modules themselves,
+generates a different value.</text>
+ </description>
+ </leaf>
+ <leaf-list name="module">
+ <type name="leafref">
+ <path value="../../../modules/module/id"/>
+ </type>
+ <description>
+ <text>A module-instance supported by the server, including its
+features and deviations.</text>
+ </description>
+ </leaf-list>
+ </list>
+ </container>
+ <container name="datastores">
+ <description>
+ <text>A container for a list of datastores supported by the
+server. Each datastore indicates which module-sets it
+supports.</text>
+ </description>
+ <list name="datastore">
+ <key value="name"/>
+ <description>
+ <text>A datastore supported by this server.</text>
+ </description>
+ <leaf name="name">
+ <type name="identityref">
+ <base name="ds:datastore"/>
+ </type>
+ <description>
+ <text>The identity of the datastore.</text>
+ </description>
+ </leaf>
+ <leaf name="module-set">
+ <type name="leafref">
+ <path value="../../../module-sets/module-set/id"/>
+ </type>
+ <description>
+ <text>A reference to a module-set supported by this
+datastore</text>
+ </description>
+ </leaf>
+ </list>
+ </container>
+ </grouping>
+ <grouping name="module-list">
+ <status value="deprecated"/>
+ <description>
+ <text>The module data structure is represented as a grouping
+so it can be reused in configuration or another monitoring
+data structure.</text>
+ </description>
+ <grouping name="common-leafs">
+ <status value="deprecated"/>
+ <description>
+ <text>Common parameters for YANG modules and submodules.</text>
+ </description>
+ <leaf name="name">
+ <type name="yang:yang-identifier"/>
+ <status value="deprecated"/>
+ <description>
+ <text>The YANG module or submodule name.</text>
+ </description>
+ </leaf>
+ <leaf name="revision">
+ <type name="union">
+ <type name="revision-identifier"/>
+ <type name="string">
+ <length value="0"/>
+ </type>
+ </type>
+ <status value="deprecated"/>
+ <description>
+ <text>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.</text>
+ </description>
+ </leaf>
+ </grouping>
+ <list name="module">
+ <key value="name revision"/>
+ <status value="deprecated"/>
+ <description>
+ <text>Each entry represents one revision of one module
+currently supported by the server.</text>
+ </description>
+ <uses name="common-leafs">
+ <status value="deprecated"/>
+ </uses>
+ <uses name="schema-leaf">
+ <status value="deprecated"/>
+ </uses>
+ <leaf name="namespace">
+ <type name="inet:uri"/>
+ <mandatory value="true"/>
+ <status value="deprecated"/>
+ <description>
+ <text>The XML namespace identifier for this module.</text>
+ </description>
+ </leaf>
+ <leaf-list name="feature">
+ <type name="yang:yang-identifier"/>
+ <status value="deprecated"/>
+ <description>
+ <text>List of YANG feature names from this module that are
+supported by the server, regardless whether they are
+defined in the module or any included submodule.</text>
+ </description>
+ </leaf-list>
+ <list name="deviation">
+ <key value="name revision"/>
+ <status value="deprecated"/>
+ <description>
+ <text>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.</text>
+ </description>
+ <uses name="common-leafs">
+ <status value="deprecated"/>
+ </uses>
+ </list>
+ <leaf name="conformance-type">
+ <type name="enumeration">
+ <enum name="implement">
+ <description>
+ <text>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.</text>
+ </description>
+ </enum>
+ <enum name="import">
+ <description>
+ <text>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.</text>
+ </description>
+ </enum>
+ </type>
+ <mandatory value="true"/>
+ <status value="deprecated"/>
+ <description>
+ <text>Indicates the type of conformance the server is claiming
+for the YANG module identified by this entry.</text>
+ </description>
+ </leaf>
+ <list name="submodule">
+ <key value="name revision"/>
+ <status value="deprecated"/>
+ <description>
+ <text>Each entry represents one submodule within the
+parent module.</text>
+ </description>
+ <uses name="common-leafs">
+ <status value="deprecated"/>
+ </uses>
+ <uses name="schema-leaf">
+ <status value="deprecated"/>
+ </uses>
+ </list>
+ </list>
+ </grouping>
+ <container name="yang-library">
+ <config value="false"/>
+ <description>
+ <text>Container providing all the YANG meta information the
+server possesses.</text>
+ </description>
+ <uses name="yang-library-parameters"/>
+ <leaf name="checksum">
+ <type name="string"/>
+ <config value="false"/>
+ <mandatory value="true"/>
+ <description>
+ <text>A server-generated checksum 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/checksum, has
+changed.</text>
+ </description>
+ </leaf>
+ </container>
+ <container name="modules-state">
+ <config value="false"/>
+ <status value="deprecated"/>
+ <description>
+ <text>Contains YANG module monitoring information.</text>
+ </description>
+ <leaf name="module-set-id">
+ <type name="string"/>
+ <mandatory value="true"/>
+ <status value="deprecated"/>
+ <description>
+ <text>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.</text>
+ </description>
+ </leaf>
+ <uses name="module-list">
+ <status value="deprecated"/>
+ </uses>
+ </container>
+ <notification name="yang-library-update">
+ <description>
+ <text>Generated when any YANG library information on the
+server has changed.</text>
+ </description>
+ </notification>
+ <notification name="yang-library-change">
+ <status value="deprecated"/>
+ <description>
+ <text>Generated when the set of modules and submodules supported
+by the server has changed.</text>
+ </description>
+ <leaf name="module-set-id">
+ <type name="leafref">
+ <path value="/yanglib:modules-state/yanglib:module-set-id"/>
+ </type>
+ <mandatory value="true"/>
+ <status value="deprecated"/>
+ <description>
+ <text>Contains the module-set-id value representing the
+set of modules and submodules supported at the server
+at the time the notification is generated.</text>
+ </description>
+ </leaf>
+ </notification>
+</module>
+</data>
+</rpc-reply>