One document matched: draft-ietf-netconf-yang-library-05.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt"?>
<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>
<?rfc toc="yes"?>
<?rfc compact="no"?>
<?rfc subcompact="no"?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc iprnotified="no"?>
<?rfc strict="yes"?>
<rfc ipr="trust200902" category="std"
docName="draft-ietf-netconf-yang-library-05" >
<front>
<title abbrev="YANG Library">YANG Module Library</title>
<author initials="A" surname="Bierman" fullname='Andy Bierman' >
<organization>YumaWorks</organization>
<address>
<email>andy@yumaworks.com</email>
</address>
</author>
<author initials="M" surname="Bjorklund" fullname='Martin Bjorklund' >
<organization>Tail-f Systems</organization>
<address>
<email>mbj@tail-f.com</email>
</address>
</author>
<author initials="K" surname="Watsen" fullname='Kent Watsen' >
<organization>Juniper Networks</organization>
<address>
<email>kwatsen@juniper.net</email>
</address>
</author>
<date/>
<abstract>
<t>
This document describes a YANG library, which provides information
about all the YANG modules used by a network management server (e.g.,
a Network Configuration Protocol (NETCONF) server). Simple caching
mechanisms are provided to allow clients to minimize retrieval of this
information.
</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>
There is a need for standard mechanisms to identify the YANG modules
and submodules that are in use by a server that implements YANG data
models. If a large number of YANG modules are utilized by the server,
then the YANG library contents needed can be relatively large. This
information changes very infrequently, so it is important that clients
be able to cache the YANG library contents and easily identify whether
their cache is out-of-date.
</t>
<t>
YANG library information can be different on every server,
and can change at run-time or across a server reboot.
</t>
<t>
If the server implements multiple protocols to access the
YANG-defined data, each such protocol has it's own conceptual
instantiation of the YANG library.
</t>
<t>
The following information is needed by a client application
(for each YANG module in the library)
to fully utilize the YANG data modeling language:
</t>
<t>
<list style="symbols">
<t>
name: The name of the YANG module.
</t>
<t>
revision: Each YANG module and submodule within the library
has a revision. This is derived from the most
recent revision statement within the module or submodule. If no such
revision statement exists, the module's or submodule's revision is the
zero-length string.
</t>
<t>
submodule list: The name and revision of each submodule
used by the module MUST be identified.
</t>
<t>
feature list: The name of each YANG feature supported by the
server MUST be identified.
</t>
<t>
deviation list: The name of each YANG module used for deviation
statements MUST be identified.
</t>
</list>
</t>
<section title="Terminology">
<t>
The keywords "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, <xref target="RFC2119"/>.
</t>
<t>
The following terms are defined in <xref target="RFC6241"/>:
</t>
<t>
<list style="symbols">
<t>
client
</t>
<t>
server
</t>
</list>
</t>
<t>
The following terms are defined in <xref target="I-D.ietf-netmod-rfc6020bis"/>:
</t>
<t>
<list style="symbols">
<t>
module
</t>
<t>
submodule
</t>
</list>
</t>
<t>
The following terms are used within this document:
</t>
<t>
<list style="symbols">
<t>
YANG library: a collection of YANG modules and submodules
used by a server
</t>
</list>
</t>
</section>
<section title="Tree Diagrams">
<t>
A simplified graphical representation of the data model is used in
this document. The meaning of the symbols in these
diagrams is as follows:
</t>
<t>
<list style="symbols">
<t>
Brackets "[" and "]" enclose list keys.
</t>
<t>
Abbreviations before data node names: "rw" means configuration
data (read-write) and "ro" state data (read-only).
</t>
<t>
Symbols after data node names: "?" means an optional node, "!" means
a presence container, and "*" denotes a list and leaf-list.
</t>
<t>
Parentheses enclose choice and case nodes, and case nodes are also
marked with a colon (":").
</t>
<t>
Ellipsis ("...") stands for contents of subtrees that are not shown.
</t>
</list>
</t>
</section>
</section>
<section title="YANG Module Library">
<t>
The "ietf‑yang‑library" module provides information about
the YANG library used by a server. This module is defined
using YANG version 1, but it supports the description of YANG modules
written in any revision of YANG.
</t>
<t>
YANG Tree Diagram for "ietf‑yang‑library" module:
</t>
<figure>
<artwork><![CDATA[
+--ro modules-state
+--ro module-set-id string
+--ro module* [name revision]
+--ro name yang:yang-identifier
+--ro revision union
+--ro schema? inet:uri
+--ro namespace inet:uri
+--ro feature* yang:yang-identifier
+--ro deviation* [name revision]
| +--ro name yang:yang-identifier
| +--ro revision union
+--ro conformance-type enumeration
+--ro submodules
+--ro submodule* [name revision]
+--ro name yang:yang-identifier
+--ro revision union
+--ro schema? inet:uri
]]></artwork>
</figure>
<section title="modules-state">
<t>
This mandatory container holds the identifiers
for the YANG data model modules supported by the server.
</t>
<section title="modules-state/module-set-id">
<t>
This mandatory leaf contains a unique implementation-specific
identifier representing the current set of modules and submodules
on a specific server.
The value of this leaf MUST change whenever the set of modules and
submodules in the YANG library changes. There is no requirement that
the same set always results in the same module-set-id value.
</t>
<t>
This leaf allows a client to fetch the module list once, cache
it, and only re-fetch it if the value of this leaf has been
changed.
</t>
<t>
If the value of this leaf changes, the server also generates a
"yang‑library‑change" notification, with the new value of
"module‑set‑id".
</t>
<t>
Note that for a NETCONF server that implements YANG 1.1
<xref target="I-D.ietf-netmod-rfc6020bis"/>, a change of the "module‑set‑id" value
results in a new value for the :yang-library capability defined in
<xref target="I-D.ietf-netmod-rfc6020bis"/>. Thus, if such a server implements
NETCONF notifications <xref target="RFC5277"/>, and the notification
"netconf‑capability‑change" <xref target="RFC6470"/>, a "netconf‑capability‑change"
notification is generated whenever the "module‑set‑id" changes.
</t>
</section>
<section title="modules-state/module">
<t>
This mandatory list contains one entry
for each YANG data model module supported by the server.
There MUST be an entry in this list for each revision
of each YANG module that is used by the server.
It is possible for multiple revisions of the same module
to be imported, in addition to an entry for the revision
that is implemented by the server.
</t>
</section>
</section>
<section title="YANG Library Module" anchor="library-module">
<t>
The "ietf‑yang‑library" module defines monitoring
information for the YANG modules used by a server.
</t>
<t>
The "ietf‑yang‑types" and "ietf‑inet‑types" modules from <xref target="RFC6991"/>
are used by this module for some type definitions.
</t>
<t>
RFC Ed.: update the date below with the date of RFC publication and
remove this note.
</t>
<t><CODE BEGINS> file "ietf-yang-library@2016-04-09.yang"</t>
<figure>
<artwork><![CDATA[
module ietf-yang-library {
namespace "urn:ietf:params:xml:ns:yang:ietf-yang-library";
prefix "yanglib";
import ietf-yang-types {
prefix yang;
}
import ietf-inet-types {
prefix inet;
}
organization
"IETF NETCONF (Network Configuration) Working Group";
contact
"WG Web: <http://tools.ietf.org/wg/netconf/>
WG List: <mailto:netconf@ietf.org>
WG Chair: Mehmet Ersue
<mailto:mehmet.ersue@nsn.com>
WG Chair: Mahesh Jethanandani
<mailto:mjethanandani@gmail.com>
Editor: Andy Bierman
<mailto:andy@yumaworks.com>
Editor: Martin Bjorklund
<mailto:mbj@tail-f.com>
Editor: Kent Watsen
<mailto:kwatsen@juniper.net>";
description
"This module contains monitoring information about the YANG
modules and submodules that are used within a YANG-based
server.
Copyright (c) 2016 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.";
// RFC Ed.: replace XXXX with actual RFC number and remove this
// note.
// RFC Ed.: remove this note
// Note: extracted from draft-ietf-netconf-yang-library-05.txt
// RFC Ed.: update the date below with the date of RFC publication
// and remove this note.
revision 2016-04-09 {
description
"Initial revision.";
reference
"RFC XXXX: 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-list {
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 {
description
"Common parameters for YANG modules and submodules.";
leaf name {
type yang:yang-identifier;
description
"The YANG module or submodule name.";
}
leaf revision {
type union {
type revision-identifier;
type string { length 0; }
}
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 {
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";
description
"Each entry represents one revision of one module
currently supported by the server.";
uses common-leafs;
uses schema-leaf;
leaf namespace {
type inet:uri;
mandatory true;
description
"The XML namespace identifier for this module.";
}
leaf-list feature {
type yang:yang-identifier;
description
"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.";
}
list deviation {
key "name revision";
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;
}
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;
description
"Indicates the type of conformance the server is claiming
for the YANG module identified by this entry.";
}
container submodules {
description
"Contains information about all the submodules used
by the parent module entry";
list submodule {
key "name revision";
description
"Each entry represents one submodule within the
parent module.";
uses common-leafs;
uses schema-leaf;
}
}
}
}
/*
* Operational state data nodes
*/
container modules-state {
config false;
description
"Contains YANG module monitoring information.";
leaf module-set-id {
type string;
mandatory true;
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;
}
/*
* Notifications
*/
notification yang-library-change {
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;
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.";
}
}
}
]]></artwork>
</figure>
<t><CODE ENDS></t>
</section>
</section>
<section title="IANA Considerations" anchor="iana">
<section title="YANG Module Registry">
<t>
This document registers one URI in the IETF XML registry
<xref target="RFC3688"/>. Following the format in RFC 3688, the following
registration is requested to be made.
</t>
<figure>
<artwork><![CDATA[
URI: urn:ietf:params:xml:ns:yang:ietf-yang-library
Registrant Contact: The NETMOD WG of the IETF.
XML: N/A, the requested URI is an XML namespace.
]]></artwork>
</figure>
<t>
This document registers one YANG module in the YANG Module Names
registry <xref target="RFC6020"/>.
</t>
<figure>
<artwork><![CDATA[
name: ietf-yang-library
namespace: urn:ietf:params:xml:ns:yang:ietf-yang-library
prefix: yanglib
// RFC Ed.: replace XXXX with RFC number and remove this note
reference: RFC XXXX
]]></artwork>
</figure>
</section>
</section>
<section title="Security Considerations">
<t>
The YANG module defined in this memo is designed to be accessed
via the NETCONF protocol <xref target="RFC6241"/>. The lowest NETCONF layer is
the secure transport layer and the mandatory-to-implement secure
transport is SSH <xref target="RFC6242"/>. Authorization for access to specific
portions of conceptual data and operations within this module
is provided by the NETCONF access control model (NACM) <xref target="RFC6536"/>.
</t>
<t>
Some of the readable data nodes in this YANG module may be
considered sensitive or vulnerable in some network environments.
It is thus important to control read access (e.g., via get,
get-config, or notification) to these data nodes. These are the
subtrees and data nodes and their sensitivity/vulnerability:
</t>
<t>
<list style="symbols">
<t>
/modules-state/module: The module list used in a server
implementation may help an attacker identify the server capabilities
and server implementations with known bugs.
Although some of this information may
be available to all users via the NETCONF <hello> message (or similar
messages in other management protocols), this YANG module potentially
exposes additional details that could be of some assistance to an
attacker. Server vulnerabilities may be
specific to particular modules, module revisions, module features,
or even module deviations. This information is included in each module entry.
For example, if a particular operation on a particular data node is
known to cause a server to crash or significantly degrade device performance,
then the module list information will help an
attacker identify server implementations with such a defect, in order
to launch a denial of service attack on the device.
</t>
</list>
</t>
</section>
<section title="Acknowledgements">
<t>
Contributions to this material by Andy Bierman are based upon work
supported by the The Space & Terrestrial Communications Directorate
(S&TCD) under Contract No. W15P7T-13-C-A616. Any opinions, findings
and conclusions or recommendations expressed in this material are
those of the author(s) and do not necessarily reflect the views of
The Space & Terrestrial Communications Directorate (S&TCD).
</t>
</section>
</middle>
<back>
<!-- -*- nxml -*- -->
<references title="Normative References">
<reference anchor="RFC2119" target="http://www.rfc-editor.org/info/rfc2119">
<front>
<title>Key words for use in RFCs to Indicate Requirement Levels</title>
<author initials="S." surname="Bradner" fullname="S. Bradner">
<organization/>
</author>
<date year="1997" month="March"/>
<abstract>
<t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="14"/>
<seriesInfo name="RFC" value="2119"/>
<seriesInfo name="DOI" value="10.17487/RFC2119"/>
</reference>
<reference anchor="RFC3688" target="http://www.rfc-editor.org/info/rfc3688">
<front>
<title>The IETF XML Registry</title>
<author initials="M." surname="Mealling" fullname="M. Mealling">
<organization/>
</author>
<date year="2004" month="January"/>
<abstract>
<t>This document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="81"/>
<seriesInfo name="RFC" value="3688"/>
<seriesInfo name="DOI" value="10.17487/RFC3688"/>
</reference>
<reference anchor="RFC6020" target="http://www.rfc-editor.org/info/rfc6020">
<front>
<title>YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)</title>
<author initials="M." surname="Bjorklund" fullname="M. Bjorklund" role="editor">
<organization/>
</author>
<date year="2010" month="October"/>
<abstract>
<t>YANG is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF), NETCONF remote procedure calls, and NETCONF notifications. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="6020"/>
<seriesInfo name="DOI" value="10.17487/RFC6020"/>
</reference>
<reference anchor="RFC6241" target="http://www.rfc-editor.org/info/rfc6241">
<front>
<title>Network Configuration Protocol (NETCONF)</title>
<author initials="R." surname="Enns" fullname="R. Enns" role="editor">
<organization/>
</author>
<author initials="M." surname="Bjorklund" fullname="M. Bjorklund" role="editor">
<organization/>
</author>
<author initials="J." surname="Schoenwaelder" fullname="J. Schoenwaelder" role="editor">
<organization/>
</author>
<author initials="A." surname="Bierman" fullname="A. Bierman" role="editor">
<organization/>
</author>
<date year="2011" month="June"/>
<abstract>
<t>The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="6241"/>
<seriesInfo name="DOI" value="10.17487/RFC6241"/>
</reference>
<reference anchor="RFC6242" target="http://www.rfc-editor.org/info/rfc6242">
<front>
<title>Using the NETCONF Protocol over Secure Shell (SSH)</title>
<author initials="M." surname="Wasserman" fullname="M. Wasserman">
<organization/>
</author>
<date year="2011" month="June"/>
<abstract>
<t>This document describes a method for invoking and running the Network Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as an SSH subsystem. This document obsoletes RFC 4742. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="6242"/>
<seriesInfo name="DOI" value="10.17487/RFC6242"/>
</reference>
<reference anchor="RFC6991" target="http://www.rfc-editor.org/info/rfc6991">
<front>
<title>Common YANG Data Types</title>
<author initials="J." surname="Schoenwaelder" fullname="J. Schoenwaelder" role="editor">
<organization/>
</author>
<date year="2013" month="July"/>
<abstract>
<t>This document introduces a collection of common data types to be used with the YANG data modeling language. This document obsoletes RFC 6021.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="6991"/>
<seriesInfo name="DOI" value="10.17487/RFC6991"/>
</reference>
<reference anchor="RFC6536" target="http://www.rfc-editor.org/info/rfc6536">
<front>
<title>Network Configuration Protocol (NETCONF) Access Control Model</title>
<author initials="A." surname="Bierman" fullname="A. Bierman">
<organization/>
</author>
<author initials="M." surname="Bjorklund" fullname="M. Bjorklund">
<organization/>
</author>
<date year="2012" month="March"/>
<abstract>
<t>The standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability. There is a need for standard mechanisms to restrict NETCONF protocol access for particular users to a pre-configured subset of all available NETCONF protocol operations and content. This document defines such an access control model. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="6536"/>
<seriesInfo name="DOI" value="10.17487/RFC6536"/>
</reference>
</references>
<references title="Informative References">
<reference anchor="I-D.ietf-netmod-rfc6020bis">
<front>
<title>The YANG 1.1 Data Modeling Language</title>
<author initials="M" surname="Bjorklund" fullname="Martin Bjorklund">
<organization/>
</author>
<date month="February" day="4" year="2016"/>
<abstract>
<t>YANG is a data modeling language used to model configuration data, state data, remote procedure calls, and notifications for network management protocols like the Network Configuration Protocol (NETCONF).</t>
</abstract>
</front>
<seriesInfo name="Internet-Draft" value="draft-ietf-netmod-rfc6020bis-10"/>
<format type="TXT" target="http://www.ietf.org/internet-drafts/draft-ietf-netmod-rfc6020bis-10.txt"/>
</reference>
<reference anchor="RFC5277" target="http://www.rfc-editor.org/info/rfc5277">
<front>
<title>NETCONF Event Notifications</title>
<author initials="S." surname="Chisholm" fullname="S. Chisholm">
<organization/>
</author>
<author initials="H." surname="Trevino" fullname="H. Trevino">
<organization/>
</author>
<date year="2008" month="July"/>
<abstract>
<t>This document defines mechanisms that provide an asynchronous message notification delivery service for the Network Configuration protocol (NETCONF). This is an optional capability built on top of the base NETCONF definition. This document defines the capabilities and operations necessary to support this service. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="5277"/>
<seriesInfo name="DOI" value="10.17487/RFC5277"/>
</reference>
<reference anchor="RFC6470" target="http://www.rfc-editor.org/info/rfc6470">
<front>
<title>Network Configuration Protocol (NETCONF) Base Notifications</title>
<author initials="A." surname="Bierman" fullname="A. Bierman">
<organization/>
</author>
<date year="2012" month="February"/>
<abstract>
<t>The Network Configuration Protocol (NETCONF) provides mechanisms to manipulate configuration datastores. However, client applications often need to be aware of common events, such as a change in NETCONF server capabilities, that may impact management applications. Standard mechanisms are needed to support the monitoring of the base system events within the NETCONF server. This document defines a YANG module that allows a NETCONF client to receive notifications for some common system events. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="6470"/>
<seriesInfo name="DOI" value="10.17487/RFC6470"/>
</reference>
</references>
<section title="Change Log">
<figure>
<artwork><![CDATA[
-- RFC Ed.: remove this section before publication.
]]></artwork>
</figure>
<section title="v04 to v05">
<t>
<list style="symbols">
<t>
clarify security considerations per secdir review
</t>
<t>
clarifications for AD review
</t>
</list>
</t>
</section>
<section title="v03 to v04">
<t>
<list style="symbols">
<t>
editorial changes after WGLC
</t>
<t>
one library instance per management protocol
</t>
<t>
removed protocol definitions
</t>
<t>
removed requirements on YANG 1.1 modules (text is moved to
draft-ietf-netmod-rfc6020bis)
</t>
<t>
added notification yang-library-change
</t>
<t>
changed top-level node name from "modules" to "modules‑state"
</t>
<t>
changed leaf "conformance" to "conformance‑type"
</t>
</list>
</t>
</section>
<section title="v02 to v03">
<t>
<list style="symbols">
<t>
added yang-protocol identity
</t>
<t>
added identities for NETCONF and RESTCONF protocols
</t>
<t>
added yang-protocol leaf-list to /modules
</t>
<t>
added restricted-protocol leaf-list to /modules/module
</t>
</list>
</t>
</section>
<section title="v01 to v02">
<t>
<list style="symbols">
<t>
clarify 'implement' conformance for YANG 1.1 modules
</t>
</list>
</t>
</section>
<section title="v00 to v01">
<t>
<list style="symbols">
<t>
change conformance leaf to enumeration
</t>
<t>
filled in security considerations section
</t>
</list>
</t>
</section>
<section title="draft-ietf-netconf-restconf-03 to v00">
<t>
<list style="symbols">
<t>
moved ietf-yang-library from RESTCONF draft to new draft
</t>
</list>
</t>
</section>
</section>
<section title="Open Issues">
<figure>
<artwork><![CDATA[
-- RFC Ed.: remove this section before publication.
]]></artwork>
</figure>
<t>
The YANG Library issue tracker can be found here:
</t>
<figure>
<artwork><![CDATA[
https://github.com/netconf-wg/yang-library/issues
]]></artwork>
</figure>
</section>
</back></rfc>
| PAFTECH AB 2003-2026 | 2026-04-23 05:27:24 |