<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.4.12) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-netmod-yang-config-templates-00" category="std" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="YANG Config Templates">YANG Configuration Templates</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-netmod-yang-config-templates-00"/>
    <author fullname="Kent Watsen">
      <organization>Watsen Networks</organization>
      <address>
        <email>kent+ietf@watsen.net</email>
      </address>
    </author>
    <author fullname="Qiufang Ma">
      <organization>Huawei</organization>
      <address>
        <postal>
          <street>101 Software Avenue, Yuhua District</street>
          <city>Jiangsu</city>
          <code>210012</code>
          <country>China</country>
        </postal>
        <email>maqiufang1@huawei.com</email>
      </address>
    </author>
    <author fullname="Deepak Rajaram">
      <organization>Nokia</organization>
      <address>
        <postal>
          <country>India</country>
        </postal>
        <email>deepak.rajaram@nokia.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="15"/>
    <area>Operations and Management</area>
    <workgroup>Network Modeling</workgroup>
    <keyword>YANG</keyword>
    <keyword>template</keyword>
    <keyword>NMDA</keyword>
    <abstract>
      <?line 58?>

<t>This document defines a YANG-based configuration template mechanism
   whereby repetitive configuration data can be factored out into
   templates and applied where needed.  This avoids the redundant
   definition of identical configuration and ensures the consistency
   of it, thus allowing configuration data to be managed more
   conveniently and efficiently.</t>
    </abstract>
    <note removeInRFC="true">
      <name>Discussion Venues</name>
      <t>Discussion of this document takes place on the
    Network Modeling Working Group mailing list (netmod@ietf.org),
    which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/netmod/"/>.</t>
      <t>Source for this draft and an issue tracker can be found at
    <eref target="https://github.com/QiufangMa/template-mechanism"/>.</t>
    </note>
  </front>
  <middle>
    <?line 67?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>This document defines the "template" mechanism mentioned but
   not defined in Network Management Datastore Architecture (NMDA) <xref target="RFC8342"/>.</t>
      <t>Templates enable repetitive configuration to be factored out into
   hierarchies of living templates and applied where the configuration
   is needed.  This avoids the redundant definition of identical
   configuration and ensures the consistency of it, thus allowing
   configuration data to be managed more conveniently and efficiently.</t>
      <t>Templates are "hierarchal" in that templates may apply yet other
   templates.  Templates are "living" in that their affect on
   configuration is maintained so long as the template is applied.
   Any change made to an applied template has immediate effect on
   the configuration.</t>
      <t>By example, an network management system (NMS) may manage many
   devices.  Devices may be come from different vendors, each of
   which may have multiple types of devices (router, firewall, etc.),
   though sharing a common operating system.  Further, each type of
   device may have different models (e.g., fw-100, fw-1000, etc.).
   In this case, common "fw-100" configuration could be put into
   a template called "common-fw-100-template", which itself inherits
   from a template called "common-fw-template", which itself inherits
   from a template called "common-vendor-template".  Similarly, a
   "common-fw-1000-template" could inherit from "common-fw-template"
   and, likewise, a "common-rtr-template" could inherit from the
   "common-vendor-template".</t>
      <t>Templates are mostly for humans, but are still important even
   when the management of a server's configuration is fully automated.
   For instance, when provided templates, a server can optimize
   internal memory usage, enabling higher performance and scability.</t>
      <t>The solution presented in this document supports both servers that do
   and do not support NMDA.  In both cases, templates are edited and
   applied as configuration in &lt;running&gt;.  For servers supporting NMDA,
   templates may be defined in &lt;system&gt; <xref target="I-D.ietf-netmod-system-config"/>,
   if supported by the server, and &lt;intended&gt; always returns the
   configuration with the templates expanded.  For servers not
   supporting NMDA, a "with-templates-expanded" parameter may be passed
   by a client, when fetching configuration from &lt;running&gt;, to obtain
   the configuration with the templates expanded.  However templates
   are expanded, a "with-template-inheritance" parameter may be passed
   by a client, when fetching expanded configuration, to obtain the
   expanded configuration with annotations indicating from which
   template values came from.</t>
      <t>Templates may be expanded off-box.  If a client has knowledge
   of the complete contents of &lt;running&gt; and &lt;system&gt;, if
   supported by the server, the client can calculate the exact
   result of template expansion.  Template expansion is
   independent of the server's operational state.</t>
      <t>Templates can be used with any YANG data model, including
   those defined with augmentations and/or deviations.</t>
      <section anchor="editorial-note-to-be-removed-by-rfc-editor">
        <name>Editorial Note (To be removed by RFC Editor)</name>
        <t>Note to the RFC Editor: This section is to be removed prior to publication.</t>
        <t>This document contains placeholder values that need to be replaced with finalized
values at the time of publication.  This note summarizes all of the
substitutions that are needed.  No other RFC Editor instructions are specified
elsewhere in this document.</t>
        <t>Please apply the following replacements:</t>
        <ul spacing="normal">
          <li>
            <t>XXXX --&gt; the assigned RFC number for this draft</t>
          </li>
          <li>
            <t>2026-07-03 --&gt; the actual date of the publication of this document</t>
          </li>
        </ul>
      </section>
      <section anchor="conventions-and-definitions">
        <name>Conventions and Definitions</name>
        <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
        <?line -18?>

<t>The meanings of the symbols in tree diagrams are defined in
<xref target="RFC8340"/>.</t>
        <t>This document uses the terminology defined in <xref section="3" sectionFormat="of" target="RFC7950"/> and <xref section="3" sectionFormat="of" target="RFC8342"/>.</t>
        <t>This document uses the following terminology in <xref target="RFC6241"/>:</t>
        <ul spacing="normal">
          <li>
            <t>configuration data</t>
          </li>
        </ul>
        <t>Besides, this document defines the following terminology:</t>
        <dl>
          <dt>configuration template:</dt>
          <dd>
            <t>A snippet of configuration data that may be applied to the
configuration repeatedly, in order to simplify the delivery
of network configuration and ensure the consistency of it.
A configuration template is referred to interchangeably as
"template" or "YANG template" throughout this document.</t>
          </dd>
        </dl>
        <t>Examples used in this document encode YANG data using XML,
as defined in <xref target="RFC7950"/>.  Other encodings such as
JSON <xref target="RFC7951"/> and CBOR <xref target="RFC9254"/> could have been
instead.</t>
      </section>
      <section anchor="applicability-statement">
        <name>Applicability Statement</name>
        <t>The solution presented in this document can be implemented by
any YANG-based server.  The solution is data model independent
and can be wholly realized as a preprocessor to the existing
configuration management mechanism on a server.</t>
      </section>
    </section>
    <section anchor="configuration-template-solution">
      <name>Configuration Template Solution</name>
      <section anchor="defining-templates">
        <name>Defining Templates</name>
        <t>Templates must first be defined before they can be applied
(see <xref target="applying-templates"/>).  Templates that are defined
but not applied have no impact on configuration.</t>
        <t>The creation, modification, and deletion of references to templates
is achieved by network management operations on the &lt;running&gt;
datastore via YANG driven protocols such as NETCONF <xref target="RFC6241"/>
and RESTCONF <xref target="RFC8040"/>.</t>
        <t>A server supporting templates <bcp14>MUST</bcp14> implement the
"ietf-config-templates" YANG module defined in <xref target="yang-module"/>.
This module defines a top-level "container" node called "templates"
having a "list" node called "template".  Each "template" node
instance is a YANG configuration template containing the
following descendant nodes:</t>
        <ul spacing="compact">
          <li>
            <t>id: a unique identifier for the template used when applying it.</t>
          </li>
          <li>
            <t>description: an optional description for the template.</t>
          </li>
          <li>
            <t>data-path: an optional schema location, if not root.</t>
          </li>
          <li>
            <t>content: the configuration data the template holds.</t>
          </li>
        </ul>
        <t>Servers <bcp14>SHOULD</bcp14> validate templates at the time they are defined,
that is, before they are applied, as described in <xref target="applying-templates"/>.
Validation is limited as templates do not need to, e.g., define
mandatory nodes, but other checks are possible, such as ensuring
nodes exist in the schema tree and that their values are of the
correct type.</t>
        <t>The subsections below focus solely on how templates are defined, without
any consideration for how they are applied.</t>
        <section anchor="static-config">
          <name>Templates for Static Configuration</name>
          <t>Templates <bcp14>MAY</bcp14> be defined to set static configuration, i.e.,
configuration the is not repetitive, as described in
<xref target="repetitive-config"/>.  Such templates do not reduce the size
of the configuration, but may be useful if wanting to group
configuration scattered throughout the tree. For instance,
for a server providing customer-facing services, there may
be a group for each customer that sets all the configuration
needed for the one customer.</t>
          <t>For example, the following template would, if applied, set the
"/my-yang-module:top-level-node/foo/bar/baz" node to the "empty"
value, creating any missing ancestor nodes as needed.</t>
          <artwork><![CDATA[
{
    "ietf-config-templates:templates": {
        "template": [
            {
                "name": "my-template",
                "description": "...",
                "content": {
                    "my-yang-module:top-level-node": {
                        "foo": {
                            "bar": {
                                "baz": [null]
                            }
                        }
                    }
                }
            }
        ]
    }
}
]]></artwork>
          <t>The following template is identical to the one shown previously, but
uses the "data-path" leaf to compress the "content" leaf's value.</t>
          <artwork><![CDATA[
{
    "ietf-config-templates:templates": {
        "template": [
            {
                "name": "my-template",
                "description": "...",
                "data-path": "/my-yang-module:top-level-node/foo/bar",
                "content": {
                    "my-yang-module:baz": [null]
                }
            }
        ]
    }
}
]]></artwork>
          <t>Templates can set values under "list" nodes as well. For instance, the
following template would, if applied, set the
"/my-yang-module:top-level-node/foo[key='f1']/bar[key='b1']/baz"
node to the "empty" value, creating any missing ancestor nodes as needed.</t>
          <artwork><![CDATA[
{
    "ietf-config-templates:templates": {
        "template": [
            {
                "name": "my-template",
                "description": "...",
                "content": {
                    "my-yang-module:top-level-node": [
                        {
                            "foo": [
                                {
                                    "key": "f1",
                                    "bar": [
                                        {
                                            "key": "b1",
                                            "baz": [null]
                                        }
                                    ]
                                }
                            ]
                        }
                    ]
                }
            }
        ]
    }
}
]]></artwork>
          <t>The following template is identical to the one shown previously, but
uses the "data-path" leaf to compress the "content" leaf's value.</t>
          <artwork><![CDATA[
{
    "ietf-config-templates:templates": {
        "template": [
            {
                "name": "my-template",
                "description": "...",
                "data-path": "/my-yang-module:top-level-node/foo[key='f1']/bar[key='b1']",
                "content": {
                    "my-yang-module:baz": [null]
                }
            }
        ]
    }
}
]]></artwork>
        </section>
        <section anchor="repetitive-config">
          <name>Templates for Repetitve Configuration</name>
          <t>The previous example shows a template setting configuration under
a very specific list.  But many times it is desirable to set the
same configuration under any list or any list whose key values
match a pattern.</t>
          <t>To allow a single template to apply to multiple list instances
a wildcard pattern may be used within the key leafs
to identify which list entries a template takes effect for.
This only works for list keys with built-in type "string",
or types derived from "string".</t>
          <t>The wildcard pattern <bcp14>MUST</bcp14> conform to the "Pattern Matching
Notation" defined in Section 2.13 of IEEE-1003.1-2008.</t>
          <t>For example, the following template would, if applied, set the
"baz" node to empty for any existing "bar" list beginning with
'b' under any existing "foo" list.</t>
          <artwork><![CDATA[
{
    "ietf-config-templates:templates": {
        "template": [
            {
                "name": "my-template",
                "description": "...",
                "content": {
                    "my-yang-module:top-level-node": [
                        {
                            "foo": [
                                {
                                    "key": "*",
                                    "bar": [
                                        {
                                            "key": "b*",
                                            "baz": [null]
                                        }
                                    ]
                                }
                            ]
                        }
                    ]
                }
            }
        ]
    }
}
]]></artwork>
          <t>The following template is identical to the one shown previously, but
uses the "data-path" leaf to compress the "content" leaf's value.</t>
          <artwork><![CDATA[
{
    "ietf-config-templates:templates": {
        "template": [
            {
                "name": "my-template",
                "description": "...",
                "data-path": "/my-yang-module:top-level-node/foo[key='*']/bar[key='b*']",
                "content": {
                    "my-yang-module:baz": [null]
                }
            }
        ]
    }
}
]]></artwork>
        </section>
      </section>
      <section anchor="applying-templates">
        <name>Applying Templates</name>
        <t>Once templates have been defined (see <xref target="defining-templates"/>, they
may be applied (referenced) to the configuration where needed.
Templates <bcp14>MUST</bcp14> be applied to have any effect on configuration.</t>
        <t>The creation, modification, and deletion of references to templates
is achieved by network management operations on the &lt;running&gt;
datastore via YANG driven protocols such as NETCONF <xref target="RFC6241"/>
and RESTCONF <xref target="RFC8040"/>.</t>
        <t>Servers <bcp14>MUST</bcp14> validate templates at the time they are applied.
Validation is achieved by first fully expanding the templates
(see <xref target="template-expansion"/>) and then performing normal YANG
validation on the expanded configuration.</t>
        <t>The subsections below focus solely on how templates are applied, without
any consideration for how they are expanded.</t>
        <section anchor="config-applying-templates">
          <name>Configuration Applying Templates</name>
          <t>A server supporting templates <bcp14>MUST</bcp14> conceptually use the
"apply-templates" grouping, defined in the "ietf-config-templates"
YANG module, in every "container" and "list" node in the configuration,
excluding nodes defined by the "ietf-config-templates" YANG module
itself.</t>
          <t>As seen in <xref target="yang-module"/>, the "apply-templates" grouping defines
an ordered-by user "leaf-list" called "apply-templates".  The
"apply-templates" leaf-list is of type "leafref" having a "path"
pointing to "/templates/template/name".  That is, it identifies
a list of templates to apply.</t>
          <t>That it is a list, and not a scalar, enables more than one template
to be applied.  That the list is ordered enables subsequent templates
overriding values set by earlier templates.  The algorithm for template
expansion is discussed in <xref target="template-expansion"/>.</t>
          <t>The following example illustrates the configuration's root node
applying three templates.</t>
          <artwork><![CDATA[
{
    "ietf-config-templates:templates": {
        "template": [
            {
                "name": "one",
                "content": {
                    "my-yang-module:top-level-node": {
                        "foo": 1
                    }
                }
            },
            {
                "name": "two",
                "content": {
                    "my-yang-module:top-level-node": {
                        "foo": 2
                    }
                }
            },
            {
                "name": "three",
                "content": {
                    "my-yang-module:top-level-node": {
                        "foo": 3
                    }
                }
            }
        ]
    },
    "my-yang-module:apply-templates": [one, two, three]

}
]]></artwork>
        </section>
        <section anchor="templates-applying-templates">
          <name>Templates Applying Templates</name>
          <t>The template's "content" anydata node contains configuration, and
therefore can apply templates like regular configuration.  It is
that templates can recursively apply templates that enables this
enables templates to be "hierarchal".</t>
          <t>There <bcp14>MUST NOT</bcp14> be any circular chains of template applications.
For example, if template "a" applies template "b", "b" cannot
apply "a".</t>
          <t>The following example illustrates the configuration's root node
applying a template that applies a template that applies a template.</t>
          <artwork><![CDATA[
{
    "ietf-config-templates:templates": [
        {
            "name": "three",
            "content": {
                "my-yang-module:top-level-node": {
                    "foo": 3
                }
            }
        },
        {
            "name": "two",
            "content": {
                "apply-templates": [three]
            }
        },
        {
            "name": "one",
            "content": {
                "apply-templates": [two]
            }
        }
    ],
    "my-yang-module:apply-templates": [one]
}
]]></artwork>
        </section>
      </section>
      <section anchor="template-expansion">
        <name>Template Expansion</name>
        <t>Templates <bcp14>MUST</bcp14> be expanded, sometimes called "flattened", in order to
produce a configuration that can be subject to YANG validation and
applied by the server.</t>
        <t>Conceptually, template expansion is a generic (data-model independent)
pre-processor to a server's backend that knows nothing about templates.
That said, a server wishing to optimize internal memory usage to enable
higher performance and scability may have a backend that is template-aware.</t>
        <t>This section presents an algorithm for how to expand templates.</t>
        <section anchor="basic-rules">
          <name>Basic Rules</name>
          <t>When a configuration template is applied to a node in the data tree,
it acts as if the configuration defined in the template is merged
with the configuration provided explicitly at the corresponding level
in the data tree, with the explicitly provided configuration taking
precedence.</t>
          <t>The rules are as follows:</t>
          <ul spacing="normal">
            <li>
              <t>The value of a node in the expanded configuration is determined
by using precedence to decide where to take the value from.  </t>
              <ul spacing="normal">
                <li>
                  <t>Non-template configuration always has the highest precedence.</t>
                </li>
                <li>
                  <t>When templates are applied from multiple ancestors and/or self,
the innermost (furthest from root) applications takes precedence.</t>
                </li>
                <li>
                  <t>When multiple templates are applied to a particular node, the
order of application (as indicated by the client when applying the
templates) determines the precedence within that node.</t>
                </li>
                <li>
                  <t>When a template configuring list elements uses wildcards, and
more than one matches, each match is applied in order, with the
contents being merged.</t>
                </li>
              </ul>
            </li>
            <li>
              <t>When a template configures nodes higher (closer to the root node)
in the configuration tree than where the template is applied, the
template's higher-level nodes are ignored.</t>
            </li>
          </ul>
        </section>
        <section anchor="merging-notes">
          <name>Merging Notes</name>
          <t>Merging configuration is a concept introduced in RFC 4741 without
a formal definition, which is provided in this section for templates.</t>
          <t>Generally, when configuration C1 is merged into C2, nodes in C2 take
precedence over nodes in C1.  Details follow.</t>
          <ul spacing="normal">
            <li>
              <t>When "leaf" L1 is merged into a "leaf" L2, the L2 leaf is retained
(L1 is discarded).</t>
            </li>
            <li>
              <t>When "anydata" A1 is merged into a "anydata" A2, the A2 anydata is
retained (A1 is discarded).</t>
            </li>
            <li>
              <t>When "leaf-list" LL1 is merged into a "leaf-list" LL2, new values
from LL1 are added (in order) to the end of LL2.  Matching values
are discarded.</t>
            </li>
            <li>
              <t>When "container" C1 is merged into "container" C2, all non-matching
descendant nodes are retained, and all matching descendant nodes are
recursively merged.</t>
            </li>
            <li>
              <t>When "list" LL1 is merged into a "list" LL2, all non-matching elements
from LL1 are added (in order) to the end of LL2, and all matching
elements are recursively merged.</t>
            </li>
          </ul>
          <t>For "ordered-by user" lists/leaf-lists, postpending new values/elements
preserves the understanding that values/elements are processed Left to
Right (or Top to Bottom).  Thus, postpending values/elements causes the
less important configuration (C1) to be processed after the more important
configuration (C2). This may not be semantically accurate in all cases.
For instance, the merging of two sorted lists of numbers should obstensibly
be interleaved as necessary to produce an ordered list of numbers.</t>
        </section>
        <section anchor="algorithm">
          <name>Algorithm</name>
          <aside>
            <t>Note: this section was written by AI by analysing an implementation
that passes all of the test vectors in <xref target="test-vectors"/>.</t>
          </aside>
          <t>This section describes an algorithm that implements the rules above.
The algorithm walks the configuration tree from the root, and, at each
node, merges the node's explicitly-provided configuration with the
configuration contributed by any applied templates.</t>
          <t>The algorithm relies on the underlying YANG data model in order to
classify each node (as a "container", "list", "leaf", "leaf-list", or
"anydata") and to learn each list's key leaf(s), as the merging rules
differ per node type and cannot be inferred from the encoded data alone.</t>
          <section anchor="preparation">
            <name>Preparation</name>
            <t>Before expansion begins:</t>
            <ol spacing="normal" type="1"><li>
                <t>Index every template definition by its "name", so that an
"apply-templates" reference can be resolved to a template's content.</t>
              </li>
              <li>
                <t>Remove the template definitions from the configuration, as they are
not themselves part of the expanded (&lt;intended&gt;) configuration.</t>
              </li>
            </ol>
            <t>Expansion then proceeds by processing the root node as a "container".</t>
          </section>
          <section anchor="collecting-a-nodes-sources-in-precedence-order">
            <name>Collecting a Node's Sources (in Precedence Order)</name>
            <t>At each container (including each list entry, which is a container), the
algorithm assembles an ordered list of "sources" that contribute
configuration to that location, ordered from highest precedence to
lowest:</t>
            <ol spacing="normal" type="1"><li>
                <t>The node's explicitly-provided configuration (i.e., everything
except its "apply-templates" value) comes first.</t>
              </li>
              <li>
                <t>For each name in the node's "apply-templates" value, in the order
listed by the client, the template's content is resolved to this
location (see below) and appended.  Because a template's content may
itself apply further templates, each template's content is processed
recursively, so that templates applied by a template rank below the
template that applied them.</t>
              </li>
            </ol>
            <t>Processing the sources in this order realizes the precedence rules:
explicit configuration outranks templates, self-applied templates
outrank ancestor-applied templates, and, among templates applied at the
same node, earlier-listed templates outrank later ones.  Applying a
template that is already being applied further up the current chain is a
circular reference and is an error.</t>
          </section>
          <section anchor="resolving-a-template-to-the-applied-location-ignore-above">
            <name>Resolving a Template to the Applied Location ("ignore above")</name>
            <t>A template is authored as a full configuration subtree rooted at the top
of the data tree, but it may be applied deep within the tree.  To find
the content a template contributes at the location where it is applied,
the algorithm navigates from the template's root down the same path
(the sequence of container and list-entry steps) that leads to the
applied node.  A list-entry step matches a template entry by comparing
key values, honoring wildcards ("*" and "?") in the template's keys.</t>
            <t>If the template configures nothing at (or below) the applied location,
it contributes nothing.  Any nodes the template configures above the
applied location are simply never reached by this navigation, which is
how the "ignore above" rule is realized.</t>
          </section>
          <section anchor="merging-the-sources">
            <name>Merging the Sources</name>
            <t>Once a location's sources have been collected (highest precedence
first), they are merged according to node type:</t>
            <ul spacing="normal">
              <li>
                <t>"container": The children of all sources are grouped by name,
preserving the order in which each name is first seen (i.e.,
highest-precedence first).  Each group is then merged recursively
according to that child's node type.</t>
              </li>
              <li>
                <t>"leaf" and "anydata"/"anyxml": The value from the highest-precedence
source is kept; lower-precedence values are discarded.</t>
              </li>
              <li>
                <t>"leaf-list": The higher-precedence values are kept, and any
not-yet-present values from lower-precedence sources are appended, in
order.  Duplicate values are discarded.</t>
              </li>
              <li>
                <t>"list": Entries are matched by their key value(s).  Concrete (non-
wildcard) entries establish the set of resulting entries, in order of
first appearance.  A wildcard entry contributes only to already-
established (higher-precedence) entries that it matches; when several
wildcard entries match the same entry, the later ones take
precedence.  Each resulting entry is then merged recursively as a
container.</t>
              </li>
            </ul>
          </section>
        </section>
      </section>
    </section>
    <section anchor="protocol-query-parameters">
      <name>Protocol Query Parameters</name>
      <t>This section defines query parameters that can be used with YANG-driven
protocols such as NETCONF <xref target="RFC6241"/> and RESTCONF <xref target="RFC8040"/>.  For
specific information regarding how these parameters are supported in
NETCONF and RESTCONF, please see "I-D.ietf-netmod-config-templates-nc"
and "I-D.ietf-netmod-config-templates-rc" respectively.</t>
      <section anchor="the-with-template-inheritance-parameter">
        <name>The "with-template-inheritance" Parameter</name>
        <aside>
          <t>FIXME: An R24-comment suggest returning such annotations all time - is that preferred?</t>
        </aside>
        <t>When viewing configuration with templates expanded, it can sometimes
become confusing where certain values were set.  The "with-template-inheritance"
parameter can be passed into configuration-fetching requests such as
RESTCONF's <tt>GET</tt> or NETCONF's <tt>&lt;get-data&gt;</tt>.</t>
        <t>When the "with-template-inheritance" parameter is passed, the configuration
returned is annotated with metadata indicating from which template values
were set from, if any.</t>
        <t>The annotation is a string having a value following the pattern
'node-foo' was inherited from template 'template-bar'`.</t>
      </section>
      <section anchor="the-with-templates-expanded-parameter">
        <name>The "with-templates-expanded" Parameter</name>
        <aside>
          <t>This section applies only to servers that do not support NMDA.</t>
        </aside>
        <t>For servers supporting NMDA, templates are always expanded when the
configuration is fetched from &lt;intended&gt;.</t>
        <t>For servers that do not support NMDA, the "with-templates-expanded"
parameter can be passed into &lt;running&gt; configuration-fetching requests
such as RESTCONF's <tt>GET</tt> or NETCONF's <tt>&lt;get-config&gt;</tt>.</t>
        <t>When the "with-templates-expanded" parameter is passed, the response
is the same as if the configuration had been expanded.</t>
      </section>
      <section anchor="the-with-inactive-removed-parameter">
        <name>The "with-inactive-removed" Parameter</name>
        <aside>
          <t>This section will be deleted.</t>
        </aside>
        <t>This paramter is NOT related to the template solution.  It is a parameter
that could be defined by some future "draft-ietf-netmod-inactive-config" I-D.</t>
        <t>The reason for this section is to lay bare logical extensions to the
"with-template-expanded" parameter.  That is, we could end up with
a multiplicity of such parameters for servers that do not support NMDA
to simulate fetching config from &lt;intended&gt;.</t>
        <t>Would a generic "get-intended" RPC for non-NMDA servers make more sense?</t>
      </section>
    </section>
    <section anchor="yang-module">
      <name>The "ietf-config-templates" YANG Module</name>
      <section anchor="data-model-overview">
        <name>Data Model Overview</name>
        <t>The following tree diagram <xref target="RFC8340"/> illustrates the "ietf-config-templates" module:</t>
        <artwork><![CDATA[
module: ietf-config-templates
  +--rw templates
     +--rw template* [name]
        +--rw name           string
        +--rw description?   string
        +--rw data-path?     yang:xpath1.0
        +--rw content        <anydata>

  grouping apply-templates:
    +-- apply-templates*   -> /templates/template/name
]]></artwork>
      </section>
      <section anchor="ietf-config-templates.yang">
        <name>YANG Module</name>
        <sourcecode markers="true" name="ietf-config-templates@2026-07-03.yang"><![CDATA[
module ietf-config-templates {
  yang-version 1.1;
  namespace "urn:ietf:params:xml:ns:yang:ietf-config-templates";
  prefix yct;

  import ietf-yang-types {
    prefix yang;
    reference
      "RFC 6991: Common YANG Data Types";
  }

  organization
    "IETF NETMOD (Network Modeling) Working Group";
  contact
    "WG Web:  https://datatracker.ietf.org/wg/netmod/
     WG List: NETMOD <mailto:netmod@ietf.org>
     
     Editor: Kent Watsen
             <mailto:kent+ietf@watsen.net>
     Editor: Qiufang Ma
             <mailto:maqiufang1@huawei.com>
     Editor: Deepak Rajaram
             <mailto:deepak.rajaram@nokia.com>";
             
  description
    "This module defines a top-level 'templates' node, and an
     'apply-templates' grouping.

     Copyright (c) 2026 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 Revised
     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 XXXX
     (https://www.rfc-editor.org/info/rfcXXXX); see the RFC
     itself for full legal notices.

     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 (RFC 2119)
     (RFC 8174) when, and only when, they appear in all
     capitals, as shown here.";

   revision 2026-07-03 {
     description
       "Initial revision.";
     reference
       "RFC XXXX: YANG Templates";
   }

   list templates {
     key name;
     description
       "The list of templates managed on this device.";
     leaf name {
       type string;
       description
         "The name of the template.";
     }
     leaf description {
       type string;
       description
         "A textual description of the template.";
     }
     leaf data-path {
       type yang:xpath1.0; // FIXME: should be YPath?
       default "/";
       description
         "The path location in the server's data tree that the
         ../content node is an instance of.  The data-path MUST
         not begin with '/ietf-config-template:templates'.";
     }
     anydata content {
       mandatory true;
       description
         "A subset of server configuration beginning at the
          location identified by the ../data-path node.  All
          top-level nodes MUST be namespace qualified.  When
          ../data-path is '/', the content MUST NOT define
          any nodes under '/ietf-config-template:templates'.";
     }
   }

   grouping apply-templates {
     description
       "A grouping that is conceptually used (i.e., the 'uses'
        statement) at every 'container' and 'list' node in the
        configuration.";
     leaf-list apply-templates {
       type leafref {
         path /yct:templates/yct:name;
       }
       ordered-by user;
       description
         "A user-ordered list of template references.";
     }
   }


   // FIXME: augment "with-templates-expanded" into NETCONF RPCs, what about RESTCONF?


}
]]></sourcecode>
      </section>
    </section>
    <section anchor="operational-consideration">
      <name>Operational Considerations</name>
      <section anchor="human-oriented">
        <name>Human Oriented</name>
        <section anchor="smaller-footprint">
          <name>Smaller Footprint</name>
          <t>Configuration templates are designed to factor out repetititive configuration
to a single definition that is applied repetitively.  Use of templates therefore
generally reduces the size of &lt;running&gt;.</t>
        </section>
        <section anchor="lower-cognative-load">
          <name>Lower Cognative Load</name>
          <t>Configuration templates enable a label (i.e., the template's name) to be given
for semantically related configuration, and then for that label to be referenced
where needed.  The additional structure provided by the template solution
generally improves readability and understandability.</t>
        </section>
      </section>
      <section anchor="machine-oriented">
        <name>Machine Oriented</name>
        <section anchor="scalability-concerns">
          <name>Scalability Concerns</name>
          <t>Large numbers of templates and/or large configurations may have performance
issues during template expansion.  Such issues may be improved by caching
intermediate expansion results, trading CPU-time for storage.</t>
        </section>
        <section anchor="one-to-many-implications">
          <name>One to Many Implications</name>
          <t>Configuration templates are designed to factor out configuration that is
applied repetitively, possibly a large number of times.  In some applications,
(e.g., a network device controller), a single change to a single template
could entail a potentially slow interaction with a large number of external
systems.</t>
          <!--
FIXME: Discuss with co-Authors

(See R9) Implementations MAY restrict, using a mechanism outside the scope of this document, the applications of configuration templates to some specific nodes in the YANG data tree. Restrictions should be applied consistently across all client operations. Any attempts to apply a template to a restricted node will be rejected. Implementations are recommended to expose the list of configuration nodes that do not support template application, any mechanisms to achieve this are outside the scope of this document.

Implementations MAY differ in whether the configuration templates themselves appear in \<intended\>, independent of whether the templates are applied. Implementations MAY also support conditional visibility, where templates appear in \<intended\> only when they are applied by at least one node via the "apply-templates" annotation. Regardless of the approach chosen, implementations MUST ensure the behavior is consistent and deterministic, and SHOULD be documented to allow clients to rely on predictable operational behaviors.
-->

</section>
      </section>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <section anchor="access-control">
        <name>Access Control</name>
        <t>Editing configuration in a template <bcp14>MUST</bcp14> be authorized using the same access control
settings used for standard configuration.</t>
      </section>
      <section anchor="the-ietf-config-templates-module">
        <name>The "ietf-config-templates" Module</name>
        <t>This section is modelled after...FIXME.</t>
      </section>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <section anchor="the-ietf-xml-registry">
        <name>The "IETF XML" Registry</name>
        <t>This document registers the following URI in the "IETF XML Registry" <xref target="RFC3688"/>.</t>
        <artwork><![CDATA[
        URI: urn:ietf:params:xml:ns:yang:ietf-config-templates
        Registrant Contact: The IESG.
        XML: N/A, the requested URI is an XML namespace.
]]></artwork>
      </section>
      <section anchor="the-yang-module-names-registry">
        <name>The "YANG Module Names" Registry</name>
        <t>This document registers the following YANG module in the "YANG Module Names"
   registry <xref target="RFC6020"/>.</t>
        <artwork><![CDATA[
        name:               ietf-config-templates
        namespace:          urn:ietf:params:xml:ns:yang:ietf-config-templates
        prefix:             ct
        maintained by IANA? N
        reference:          RFC XXXX
]]></artwork>
      </section>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC8342">
          <front>
            <title>Network Management Datastore Architecture (NMDA)</title>
            <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
            <author fullname="J. Schoenwaelder" initials="J." surname="Schoenwaelder"/>
            <author fullname="P. Shafer" initials="P." surname="Shafer"/>
            <author fullname="K. Watsen" initials="K." surname="Watsen"/>
            <author fullname="R. Wilton" initials="R." surname="Wilton"/>
            <date month="March" year="2018"/>
            <abstract>
              <t>Datastores are a fundamental concept binding the data models written in the YANG data modeling language to network management protocols such as the Network Configuration Protocol (NETCONF) and RESTCONF. This document defines an architectural framework for datastores based on the experience gained with the initial simpler model, addressing requirements that were not well supported in the initial model. This document updates RFC 7950.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8342"/>
          <seriesInfo name="DOI" value="10.17487/RFC8342"/>
        </reference>
        <reference anchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <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="RFC8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
        <reference anchor="RFC7950">
          <front>
            <title>The YANG 1.1 Data Modeling Language</title>
            <author fullname="M. Bjorklund" initials="M." role="editor" surname="Bjorklund"/>
            <date month="August" 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. This document describes the syntax and semantics of version 1.1 of the YANG language. YANG version 1.1 is a maintenance release of the YANG language, addressing ambiguities and defects in the original specification. There are a small number of backward incompatibilities from YANG version 1. This document also specifies the YANG mappings to the Network Configuration Protocol (NETCONF).</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7950"/>
          <seriesInfo name="DOI" value="10.17487/RFC7950"/>
        </reference>
        <reference anchor="RFC6241">
          <front>
            <title>Network Configuration Protocol (NETCONF)</title>
            <author fullname="R. Enns" initials="R." role="editor" surname="Enns"/>
            <author fullname="M. Bjorklund" initials="M." role="editor" surname="Bjorklund"/>
            <author fullname="J. Schoenwaelder" initials="J." role="editor" surname="Schoenwaelder"/>
            <author fullname="A. Bierman" initials="A." role="editor" surname="Bierman"/>
            <date month="June" year="2011"/>
            <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="RFC3688">
          <front>
            <title>The IETF XML Registry</title>
            <author fullname="M. Mealling" initials="M." surname="Mealling"/>
            <date month="January" year="2004"/>
            <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">
          <front>
            <title>YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)</title>
            <author fullname="M. Bjorklund" initials="M." role="editor" surname="Bjorklund"/>
            <date month="October" year="2010"/>
            <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>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="I-D.ietf-netmod-system-config">
          <front>
            <title>System-defined Configuration</title>
            <author fullname="Qiufang Ma" initials="Q." surname="Ma">
              <organization>Huawei</organization>
            </author>
            <author fullname="Qin Wu" initials="Q." surname="Wu">
              <organization>Huawei</organization>
            </author>
            <author fullname="Chong Feng" initials="C." surname="Feng">
         </author>
            <date day="28" month="January" year="2026"/>
            <abstract>
              <t>   The Network Management Datastore Architecture (NMDA) in RFC 8342
   defines several configuration datastores holding configuration.  The
   contents of these configuration datastores are controlled by clients.
   This document introduces the concept of system configuration
   datastore holding configuration controlled by the system on which a
   server is running.  The system configuration can be referenced (e.g.,
   leafref) by configuration explicitly created by clients.

   This document updates RFC 8342.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-netmod-system-config-20"/>
        </reference>
        <reference anchor="RFC8340">
          <front>
            <title>YANG Tree Diagrams</title>
            <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
            <author fullname="L. Berger" initials="L." role="editor" surname="Berger"/>
            <date month="March" year="2018"/>
            <abstract>
              <t>This document captures the current syntax used in YANG module tree diagrams. The purpose of this document is to provide a single location for this definition. This syntax may be updated from time to time based on the evolution of the YANG language.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="215"/>
          <seriesInfo name="RFC" value="8340"/>
          <seriesInfo name="DOI" value="10.17487/RFC8340"/>
        </reference>
        <reference anchor="RFC7951">
          <front>
            <title>JSON Encoding of Data Modeled with YANG</title>
            <author fullname="L. Lhotka" initials="L." surname="Lhotka"/>
            <date month="August" year="2016"/>
            <abstract>
              <t>This document defines encoding rules for representing configuration data, state data, parameters of Remote Procedure Call (RPC) operations or actions, and notifications defined using YANG as JavaScript Object Notation (JSON) text.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7951"/>
          <seriesInfo name="DOI" value="10.17487/RFC7951"/>
        </reference>
        <reference anchor="RFC9254">
          <front>
            <title>Encoding of Data Modeled with YANG in the Concise Binary Object Representation (CBOR)</title>
            <author fullname="M. Veillette" initials="M." role="editor" surname="Veillette"/>
            <author fullname="I. Petrov" initials="I." role="editor" surname="Petrov"/>
            <author fullname="A. Pelov" initials="A." surname="Pelov"/>
            <author fullname="C. Bormann" initials="C." surname="Bormann"/>
            <author fullname="M. Richardson" initials="M." surname="Richardson"/>
            <date month="July" year="2022"/>
            <abstract>
              <t>YANG (RFC 7950) is a data modeling language used to model configuration data, state data, parameters and results of Remote Procedure Call (RPC) operations or actions, and notifications.</t>
              <t>This document defines encoding rules for YANG in the Concise Binary Object Representation (CBOR) (RFC 8949).</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9254"/>
          <seriesInfo name="DOI" value="10.17487/RFC9254"/>
        </reference>
        <reference anchor="RFC8040">
          <front>
            <title>RESTCONF Protocol</title>
            <author fullname="A. Bierman" initials="A." surname="Bierman"/>
            <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
            <author fullname="K. Watsen" initials="K." surname="Watsen"/>
            <date month="January" year="2017"/>
            <abstract>
              <t>This document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF).</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8040"/>
          <seriesInfo name="DOI" value="10.17487/RFC8040"/>
        </reference>
      </references>
    </references>
    <?line 983?>

<section anchor="test-vectors">
      <name>Test Vectors</name>
      <t>This section provides normative vector tests for implementations.</t>
      <section anchor="example-yang-module">
        <name>Example YANG Module</name>
        <t>This section presents a YANG module that is used by the vector tests.</t>
        <section anchor="original">
          <name>Original</name>
          <t>This is the original YANG module.</t>
          <artwork><![CDATA[
module my-yang-module {
  yang-version 1.1;
  namespace "urn:ietf:params:xml:ns:yang:my-yang-module";
  prefix mym;

  leaf leaf {
    type string;
  }

  leaf-list leaf-list {
    type string;
  }

  container container {
    presence "so mandatory-leaf doesn't make mandatory-container";
    leaf mandatory-leaf {
      type string;
      mandatory true;
    }
  }

  list list {
    key key;
    leaf key {
      type string;
    }
    leaf val {
      type string;
    }
  }

  anydata anydata;

}
]]></artwork>
        </section>
        <section anchor="annotated">
          <name>Annotated</name>
          <t>This is the original YANG module after it has been annotated with
<tt>uses "yct:apply-templates"</tt> statements, as required by <xref target="config-applying-templates"/>.</t>
          <artwork><![CDATA[
module my-yang-module {
  yang-version 1.1;
  namespace "urn:ietf:params:xml:ns:yang:my-yang-module";
  prefix mym;

  import ietf-config-templates {
    prefix yct;
  }

  uses "yct:apply-templates";

  leaf leaf {
    type string;
  }

  leaf-list leaf-list {
    type string;
  }

  container container {
    presence "so mandatory-leaf doesn't make mandatory-container";
    leaf mandatory-leaf {
      type string;
      mandatory true;
    }
    uses "yct:apply-templates";
  }

  list list {
    key key;
    leaf key {
      type string;
    }
    leaf val {
      type string;
    }
    uses "yct:apply-templates";
  }

  anydata anydata;

}
]]></artwork>
        </section>
      </section>
      <section anchor="basic-tests">
        <name>Basic Tests</name>
        <section anchor="no-templates-applied">
          <name>No Templates Applied</name>
          <t>When the &lt;running&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "my-yang-module:leaf": "1",
    "my-yang-module:leaf-list": ["1", "2", "3"],
    "my-yang-module:container": {
        "mandatory-leaf": "1"
    },
    "my-yang-module:list": [
        {
            "key": "foo",
            "val": "1"
        },
        {
            "key": "bar",
            "val": "1"
        },
        {
            "key": "baz",
            "val": "1"
        }
    ],
    "my-yang-module:anydata": {
        "some-other-module:zero": 0
    }
}

]]></artwork>
          <t>The &lt;intended&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "my-yang-module:leaf": "1",
    "my-yang-module:leaf-list": ["1", "2", "3"],
    "my-yang-module:container": {
        "mandatory-leaf": "1"
    },
    "my-yang-module:list": [
        {
            "key": "foo",
            "val": "1"
        },
        {
            "key": "bar",
            "val": "1"
        },
        {
            "key": "baz",
            "val": "1"
        }
    ],
    "my-yang-module:anydata": {
        "some-other-module:zero": 0
    }
}

]]></artwork>
        </section>
        <section anchor="all-configuration-in-a-single-template">
          <name>All Configuration in a Single Template</name>
          <t>When the &lt;running&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "ietf-config-templates:templates": [
        {
            "name": "t1",
            "content": {
                "my-yang-module:leaf": "1",
                "my-yang-module:leaf-list": ["1", "2", "3"],
                "my-yang-module:container": {
                    "mandatory-leaf": "1"
                },
                "my-yang-module:list": [
                    {
                        "key": "foo",
                        "val": "1"
                    },
                    {
                        "key": "bar",
                        "val": "1"
                    },
                    {
                        "key": "baz",
                        "val": "1"
                    }
                ],
                "my-yang-module:anydata": {
                    "some-other-module:zero": 0
                }
            }
        }
    ],
    "my-yang-module:apply-templates": ["t1"]

}

]]></artwork>
          <t>The &lt;intended&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "my-yang-module:leaf": "1",
    "my-yang-module:leaf-list": ["1", "2", "3"],
    "my-yang-module:container": {
        "mandatory-leaf": "1"
    },
    "my-yang-module:list": [
        {
            "key": "foo",
            "val": "1"
        },
        {
            "key": "bar",
            "val": "1"
        },
        {
            "key": "baz",
            "val": "1"
        }
    ],
    "my-yang-module:anydata": {
        "some-other-module:zero": 0
    }
}

]]></artwork>
        </section>
        <section anchor="all-configuration-in-a-multiplicity-of-templates">
          <name>All Configuration in a Multiplicity of Templates</name>
          <t>When the &lt;running&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "ietf-config-templates:templates": [
        {
            "name": "t1",
            "content": {
                "my-yang-module:leaf": "1"
            }
        },
        {
            "name": "t2",
            "content": {
                "my-yang-module:leaf-list": ["1", "2", "3"]
            }
        },
        {
            "name": "t3",
            "content": {
                "my-yang-module:container": {
                    "mandatory-leaf": "1"
                }
            }
        },
        {
            "name": "t4",
            "content": {
                "my-yang-module:list": [
                    {
                        "key": "foo",
                        "val": "1"
                    },
                    {
                        "key": "bar",
                        "val": "1"
                    },
                    {
                        "key": "baz",
                        "val": "1"
                    }
                ]
            }
        },
        {
            "name": "t5",
            "content": {
                "my-yang-module:anydata": {
                    "some-other-module:zero": 0
                }
            }
        }
    ],
    "my-yang-module:apply-templates": ["t1", "t2", "t3", "t4", "t5"]

}

]]></artwork>
          <t>The &lt;intended&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "my-yang-module:leaf": "1",
    "my-yang-module:leaf-list": ["1", "2", "3"],
    "my-yang-module:container": {
        "mandatory-leaf": "1"
    },
    "my-yang-module:list": [
        {
            "key": "foo",
            "val": "1"
        },
        {
            "key": "bar",
            "val": "1"
        },
        {
            "key": "baz",
            "val": "1"
        }
    ],
    "my-yang-module:anydata": {
        "some-other-module:zero": 0
    }
}

]]></artwork>
        </section>
      </section>
      <section anchor="empty-node-tests">
        <name>Empty Node Tests</name>
        <section anchor="empty-apply-template-list">
          <name>Empty "apply-template" List</name>
          <t>When the &lt;running&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "my-yang-module:apply-templates": []
}
]]></artwork>
          <t>The &lt;intended&gt; datastore is:</t>
          <artwork><![CDATA[
{
}
]]></artwork>
        </section>
        <section anchor="empty-template-content">
          <name>Empty Template Content</name>
          <t>When the &lt;running&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "ietf-config-templates:templates": [
        {
            "name": "t1",
            "content": {}
        }
    ],
    "my-yang-module:apply-templates": ["t1"]
}
]]></artwork>
          <t>The &lt;intended&gt; datastore is:</t>
          <artwork><![CDATA[
{
}
]]></artwork>
        </section>
      </section>
      <section anchor="node-leaf-tests">
        <name>Node "leaf" Tests</name>
        <section anchor="hierarchal-precedence">
          <name>Hierarchal Precedence</name>
          <t>When the &lt;running&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "ietf-config-templates:templates": [
        {
            "name": "t1",
            "content": {
                "my-yang-module:leaf": "t1-1"
            }
        }
    ],
    "my-yang-module:apply-templates": ["t1"],
    "my-yang-module:leaf": "1"
}

]]></artwork>
          <t>The &lt;intended&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "my-yang-module:leaf": "t1"
}

]]></artwork>
        </section>
        <section anchor="ordered-precedence">
          <name>Ordered Precedence</name>
          <t>When the &lt;running&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "ietf-config-templates:templates": [
        {
            "name": "t1",
            "content": {
                "my-yang-module:leaf": "t1"
            }
        },
        {
            "name": "t2",
            "content": {
                "my-yang-module:leaf": "t2"
            }
        },
        {
            "name": "t3",
            "content": {
                "my-yang-module:leaf": "t3"
            }
        }
    ],
    "my-yang-module:apply-templates": ["t1", "t2", "t3"]
}

]]></artwork>
          <t>The &lt;intended&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "my-yang-module:leaf": "t1"
}

]]></artwork>
        </section>
      </section>
      <section anchor="node-leaf-list-tests">
        <name>Node "leaf-list" Tests</name>
        <section anchor="hierarchal-precedence-1">
          <name>Hierarchal Precedence</name>
          <t>When the &lt;running&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "ietf-config-templates:templates": [
        {
            "name": "t1",
            "content": {
                "my-yang-module:leaf-list": ["t1"]
            }
        }
    ],
    "my-yang-module:apply-templates": ["t1"],
    "my-yang-module:leaf-list": ["1"]
}

]]></artwork>
          <t>The &lt;intended&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "my-yang-module:leaf-list": ["1", "t1"]
}

]]></artwork>
        </section>
        <section anchor="ordered-precedence-1">
          <name>Ordered Precedence</name>
          <t>When the &lt;running&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "ietf-config-templates:templates": [
        {
            "name": "t1",
            "content": {
                "my-yang-module:leaf-list": "t1"
            }
        },
        {
            "name": "t2",
            "content": {
                "my-yang-module:leaf-list": "t2"
            }
        },
        {
            "name": "t3",
            "content": {
                "my-yang-module:leaf-list": "t3"
            }
        }
    ],
    "my-yang-module:apply-templates": ["t1", "t2", "t3"]
}

]]></artwork>
          <t>The &lt;intended&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "my-yang-module:leaf-list": ["t1", "t2", "t3"]
}

]]></artwork>
        </section>
      </section>
      <section anchor="node-container-tests">
        <name>Node "container" Tests</name>
        <section anchor="hierarchal-precedence-2">
          <name>Hierarchal Precedence</name>
          <t>When the &lt;running&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "ietf-config-templates:templates": [
        {
            "name": "t1",
            "content": {
                "my-yang-module:container": {
                    "mandatory-leaf": "t1"
                }
            }
        }
    ],
    "my-yang-module:apply-templates": ["t1"],
    "my-yang-module:container": {
        "mandatory-leaf": "1"
    }
}
]]></artwork>
          <t>The &lt;intended&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "my-yang-module:container": {
        "mandatory-leaf": "1"
    }
}

]]></artwork>
        </section>
        <section anchor="ignore-above">
          <name>Ignore Above</name>
          <t>When the &lt;running&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "ietf-config-templates:templates": [
        {
            "name": "t1",
            "content": {
                "my-yang-module:leaf": "t1",
                "my-yang-module:leaf-list": ["t1", "t2", "t3"],
                "my-yang-module:container": {
                    "mandatory-leaf": "t1"
                },
                "my-yang-module:list": [
                    {
                        "key": "foo",
                        "val": "t1"
                    },
                    {
                        "key": "bar",
                        "val": "t1"
                    }
                ],
                "my-yang-module:anydata": {
                    "some-other-module:zero": 0
                }
            }
        }
    ],
    "my-yang-module:container": {
        "apply-templates": ["t1"]
    }
}
]]></artwork>
          <t>The &lt;intended&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "my-yang-module:container": {
        "mandatory-leaf": "t1"
    }
}

]]></artwork>
        </section>
        <section anchor="ordered-precedence-2">
          <name>Ordered Precedence</name>
          <t>When the &lt;running&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "ietf-config-templates:templates": [
        {
            "name": "t1",
            "content": {
                "my-yang-module:container": {
                    "mandatory-leaf": "t1"
                }
            }
        },
        {
            "name": "t2",
            "content": {
                "my-yang-module:container": {
                    "mandatory-leaf": "t2"
                }
            }
        },
        {
            "name": "t3",
            "content": {
                "my-yang-module:container": {
                    "mandatory-leaf": "t3"
                }
            }
        }
    ],
    "my-yang-module:apply-templates": ["t1", "t2", "t3"]
}

]]></artwork>
          <t>The &lt;intended&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "my-yang-module:container": {
        "mandatory-leaf": "t1"
    }
}

]]></artwork>
        </section>
      </section>
      <section anchor="node-list-tests">
        <name>Node "list" Tests</name>
        <section anchor="hierarchal-precedence-3">
          <name>Hierarchal Precedence</name>
          <t>When the &lt;running&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "ietf-config-templates:templates": [
        {
            "name": "t1",
            "content": {
                "my-yang-module:list": [
                    {
                        "key": "foo",
                        "val": "t1"
                    },
                    {
                        "key": "baz",
                        "val": "t1"
                    }
                ]
            }
        }
    ],
    "my-yang-module:apply-templates": ["t1"],
    "my-yang-module:list": [
        {
            "key": "foo",
            "val": "1"
        },
        {
            "key": "bar",
            "val": "1"
        }
    ]
}
]]></artwork>
          <t>The &lt;intended&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "my-yang-module:list": [
        {
            "key": "foo",
            "val": "1"
        },
        {
            "key": "bar",
            "val": "1"
        },
        {
            "key": "baz",
            "val": "t1"
        }
    ]
}

]]></artwork>
        </section>
        <section anchor="ignore-above-1">
          <name>Ignore Above</name>
          <t>When the &lt;running&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "ietf-config-templates:templates": [
        {
            "name": "t1",
            "content": {
                "my-yang-module:leaf": "t1",
                "my-yang-module:leaf-list": ["t1", "t2", "t3"],
                "my-yang-module:container": {
                    "mandatory-leaf": "t1"
                },
                "my-yang-module:list": [
                    {
                        "key": "foo",
                        "val": "t1"
                    },
                    {
                        "key": "bar",
                        "val": "t1"
                    }
                ],
                "my-yang-module:anydata": {
                    "some-other-module:zero": 0
                }
            }
        }
    ],
    "my-yang-module:list": [
        {
            "apply-templates": ["t1"],
            "key": "foo"
        }
    ]
}
]]></artwork>
          <t>The &lt;intended&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "my-yang-module:list": [
        {
            "key": "foo",
            "val": "t1"
        }
    ]
}

]]></artwork>
        </section>
        <section anchor="ordered-precedence-3">
          <name>Ordered Precedence</name>
          <t>When the &lt;running&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "ietf-config-templates:templates": [
        {
            "name": "t1",
            "content": {
                "my-yang-module:list": [
                    {
                        "key": "foo",
                        "val": "t1"
                    }
                ]
            }
        },
        {
            "name": "t2",
            "content": {
                "my-yang-module:list": [
                    {
                        "key": "foo",
                        "val": "t2"
                    }
                ]
            }
        },
        {
            "name": "t3",
            "content": {
                "my-yang-module:list": [
                    {
                        "key": "foo",
                        "val": "t3"
                    }
                ]
            }
        }
    ],
    "my-yang-module:apply-templates": ["t1", "t2", "t3"]
}

]]></artwork>
          <t>The &lt;intended&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "my-yang-module:list": [
        {
            "key": "foo",
            "val": "t1"
        }
    ]
}

]]></artwork>
        </section>
        <section anchor="wildcards">
          <name>Wildcards</name>
          <t>When the &lt;running&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "ietf-config-templates:templates": [
        {
            "name": "t1",
            "content": {
                "my-yang-module:list": [
                    {
                        "key": "*",
                        "val": "t1-*"
                    },
                    {
                        "key": "b*",
                        "val": "t1-b*"
                    },
                    {
                        "key": "?a?",
                        "val": "t1-?a?"
                    }
                ]
            }
        }
    ],
    "my-yang-module:apply-templates": ["t1"],
    "my-yang-module:list": [
        {
            "key": "foo"
        },
        {
            "key": "bar"
        },
        {
            "key": "baz"
        }
    ]
}

]]></artwork>
          <t>The &lt;intended&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "my-yang-module:list": [
        {
            "key": "foo",
            "val": "t1-*"
        },
        {
            "key": "bar",
            "val": "t1-?a?"
        },
        {
            "key": "baz",
            "val": "t1-?a?"
        }
    ]
}

]]></artwork>
        </section>
      </section>
      <section anchor="node-anydata-tests">
        <name>Node "anydata" Tests</name>
        <section anchor="hierarchal-precedence-4">
          <name>Hierarchal Precedence</name>
          <t>When the &lt;running&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "ietf-config-templates:templates": [
        {
            "name": "t1",
            "content": {
                "my-yang-module:anydata": {
                    "some-t1-module:color": "red"
                }
            }
        }
    ],
    "my-yang-module:apply-templates": ["t1"],
    "my-yang-module:anydata": {
        "some-other-module:zero": 0
    }
}

]]></artwork>
          <t>The &lt;intended&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "my-yang-module:anydata": {
        "some-other-module:zero": 0
    }
}

]]></artwork>
        </section>
        <section anchor="ordered-precedence-4">
          <name>Ordered Precedence</name>
          <t>When the &lt;running&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "ietf-config-templates:templates": [
        {
            "name": "t1",
            "content": {
                "my-yang-module:anydata": {
                    "some-t1-module:color": "red"
                }
            }
        },
        {
            "name": "t2",
            "content": {
                "my-yang-module:anydata": {
                    "some-t2-module:age": 23
                }
            }
        },
        {
            "name": "t3",
            "content": {
                "my-yang-module:anydata": {
                    "some-t3-module:planet": "earth"
                }
            }
        }
    ],
    "my-yang-module:apply-templates": ["t1", "t2", "t3"]
}

]]></artwork>
          <t>The &lt;intended&gt; datastore is:</t>
          <artwork><![CDATA[
{
    "my-yang-module:anydata": {
        "some-t1-module:color": "red"
    }
}

]]></artwork>
        </section>
      </section>
    </section>
    <section anchor="requirement-implementation-status">
      <name>Requirement Implementation Status</name>
      <t>Note to the RFC Editor: Please remove this section before publication.</t>
      <t>This appendix tracks the status of requirements identified on the
[Template Requirements Issue Tracker([https://github.com/netmod-wg/template-reqs/issues).</t>
      <t>R1: <eref target="https://github.com/netmod-wg/template-reqs/issues/1">Wherever a template-reference can occur, more than one template-reference can occur (and they are applied)</eref></t>
      <ul spacing="normal">
        <li>
          <t>discussed: strongly in favor</t>
        </li>
        <li>
          <t>status: supported in document (done)</t>
        </li>
      </ul>
      <t>R2: <eref target="https://github.com/netmod-wg/template-reqs/issues/2">Templates must be able to reference other templates (hierarchal templates)</eref></t>
      <ul spacing="normal">
        <li>
          <t>discussed: originally a split opinion, subsequently supported.</t>
        </li>
        <li>
          <t>status: supported in document (done)</t>
        </li>
      </ul>
      <t>R3: <eref target="https://github.com/netmod-wg/template-reqs/issues/3">Templates must work with any YANG module (including augments and deviations)</eref></t>
      <ul spacing="normal">
        <li>
          <t>discussed: strongly in favor</t>
        </li>
        <li>
          <t>status: supported in document (done)</t>
        </li>
      </ul>
      <t>R4: <eref target="https://github.com/netmod-wg/template-reqs/issues/4">Template syntax must be validated when defined (not only when used)</eref></t>
      <ul spacing="normal">
        <li>
          <t>discussed: originally a split opinion, subsequently supported.</t>
        </li>
        <li>
          <t>status: supported in document (done)</t>
        </li>
      </ul>
      <t>R5: <eref target="https://github.com/netmod-wg/template-reqs/issues/5">Wherever a template-reference can occur, it must be possible to delete nodes from the template</eref></t>
      <ul spacing="normal">
        <li>
          <t>discussed: mildly NOT in favor</t>
        </li>
        <li>
          <t>unsure if opposed to idea or to doing it in a first release.</t>
        </li>
        <li>
          <t>status: not supported in document (done)</t>
        </li>
      </ul>
      <t>R6: <eref target="https://github.com/netmod-wg/template-reqs/issues/6">Local-config overrides template-config</eref></t>
      <ul spacing="normal">
        <li>
          <t>discussed: strongly in favor</t>
        </li>
        <li>
          <t>status: supported in document (done)</t>
        </li>
      </ul>
      <t>R7: <eref target="https://github.com/netmod-wg/template-reqs/issues/7">Templates are persistent (living templates) modifications to them are automatically applied to all consumers</eref></t>
      <ul spacing="normal">
        <li>
          <t>discussed: strongly in favor</t>
        </li>
        <li>
          <t>status: supported in document (done)</t>
        </li>
      </ul>
      <t>R8: <eref target="https://github.com/netmod-wg/template-reqs/issues/8">Support basic programmatic elements in templates</eref></t>
      <ul spacing="normal">
        <li>
          <t>discussed: strongly opposed (but Joe Clarke later said he would've voted in favor)</t>
        </li>
        <li>
          <t>unsure if opposed to idea or to doing it in a first release.</t>
        </li>
        <li>
          <t>status: NOT supported in document (discuss more?)</t>
        </li>
      </ul>
      <t>R9: <eref target="https://github.com/netmod-wg/template-reqs/issues/9">It must be possible to constrain which nodes can be template-consumers</eref></t>
      <ul spacing="normal">
        <li>
          <t>discussed: strongly in favor</t>
        </li>
        <li>
          <t>really? how can it be important?</t>
        </li>
        <li>
          <t>status: NOT supported in document (discuss more first?)</t>
        </li>
      </ul>
      <t>R10: <eref target="https://github.com/netmod-wg/template-reqs/issues/10">For living templates, the configuration with both unexpanded and expanded templates is able to be returned</eref></t>
      <ul spacing="normal">
        <li>
          <t>discussed: strongly in favor (with jstern's refinement)</t>
        </li>
        <li>
          <t>status: supported in document (done)</t>
        </li>
      </ul>
      <t>R11: <eref target="https://github.com/netmod-wg/template-reqs/issues/11">Possibility to reorder some user-ordered list/leaf-list entries defined in a template</eref></t>
      <ul spacing="normal">
        <li>
          <t>discussed: strongly opposed</t>
        </li>
        <li>
          <t>status: not supported in document (done)</t>
        </li>
      </ul>
      <t>R12: <eref target="https://github.com/netmod-wg/template-reqs/issues/12">The &lt;running&gt; datastore contains the unexpanded template</eref></t>
      <ul spacing="normal">
        <li>
          <t>discussed: strongly in favor</t>
        </li>
        <li>
          <t>status: supported in document (done)</t>
        </li>
      </ul>
      <t>R13: <eref target="https://github.com/netmod-wg/template-reqs/issues/13">For NMDA, the &lt;intended&gt; datastore returns the expanded template</eref></t>
      <ul spacing="normal">
        <li>
          <t>discussed: strongly in favor</t>
        </li>
        <li>
          <t>status: supported in document (done)</t>
        </li>
      </ul>
      <t>R14: <eref target="https://github.com/netmod-wg/template-reqs/issues/14">Off-box template-expansion of &lt;running&gt; containing templates must be possible (potentially enabling off-box validation)</eref></t>
      <ul spacing="normal">
        <li>
          <t>discussed: strongly in favor</t>
        </li>
        <li>
          <t>status: supported in document (done)</t>
        </li>
      </ul>
      <t>R15: <eref target="https://github.com/netmod-wg/template-reqs/issues/15">For NMDA, the &lt;intended&gt; datastore returns the unexpanded templates</eref></t>
      <ul spacing="normal">
        <li>
          <t>discussed: mostly opposed</t>
        </li>
        <li>
          <t>status: supported in document (done)</t>
        </li>
      </ul>
      <t>R16: <eref target="https://github.com/netmod-wg/template-reqs/issues/16">Common data nodes</eref></t>
      <ul spacing="normal">
        <li>
          <t>never discussed: this requirement is closed in GitHub</t>
        </li>
        <li>
          <t>status: not supported in document (done)</t>
        </li>
      </ul>
      <t>R17: <eref target="https://github.com/netmod-wg/template-reqs/issues/17">For NMDA, The &lt;operational&gt; datastore returns unexpanded template config (depends on #15)</eref></t>
      <ul spacing="normal">
        <li>
          <t>discussed: mostly opposed</t>
        </li>
        <li>
          <t>status: not supported in document (done)</t>
        </li>
      </ul>
      <t>R18: <eref target="https://github.com/netmod-wg/template-reqs/issues/18">Support limited-regex in template-config for template-consumer application</eref></t>
      <ul spacing="normal">
        <li>
          <t>discussed: strongly in favor</t>
        </li>
        <li>
          <t>status: supported in document (done)</t>
        </li>
      </ul>
      <t>R19: <eref target="https://github.com/netmod-wg/template-reqs/issues/19">When multiple templates are applied to a node, a precedence order must be defined (either ascending or descending)</eref></t>
      <ul spacing="normal">
        <li>
          <t>discussed: strongly in favor</t>
        </li>
        <li>
          <t>status: supported in document (done)</t>
        </li>
      </ul>
      <t>R20: <eref target="https://github.com/netmod-wg/template-reqs/issues/20">When templates are applied at multiple ancestor nodes, the innermost (closest) template takes precedence.</eref></t>
      <ul spacing="normal">
        <li>
          <t>discussed: mostly in favor</t>
        </li>
        <li>
          <t>status: supported in document (done)</t>
        </li>
      </ul>
      <t>R21: <eref target="https://github.com/netmod-wg/template-reqs/issues/21">The solution enables non-nmda servers to return the expanded data</eref></t>
      <ul spacing="normal">
        <li>
          <t>discussed: strongly in favor</t>
        </li>
        <li>
          <t>status: supported in document (but does it make sense?)</t>
        </li>
      </ul>
      <t>R22: <eref target="https://github.com/netmod-wg/template-reqs/issues/22">Method to exclude templates applied at ancestor nodes</eref></t>
      <ul spacing="normal">
        <li>
          <t>never discussed</t>
        </li>
        <li>
          <t>status: needs to be discussed (will schedule an Interim meeting)</t>
        </li>
      </ul>
      <t>R23: <eref target="https://github.com/netmod-wg/template-reqs/issues/23">Clarify the ability to apply a template at the datastore root node '/'</eref></t>
      <ul spacing="normal">
        <li>
          <t>never discussed</t>
        </li>
        <li>
          <t>status: needs to be discussed (will schedule an Interim meeting)</t>
        </li>
      </ul>
      <t>R24: <eref target="https://github.com/netmod-wg/template-reqs/issues/24">Metadata annotation to determine which template a node was applied from</eref></t>
      <ul spacing="normal">
        <li>
          <t>never discussed</t>
        </li>
        <li>
          <t>supported in document via "with-template-inheritance"?</t>
        </li>
        <li>
          <t>an R24-comment suggest returning such annotations all time - is that preferred?</t>
        </li>
        <li>
          <t>status: needs to be discussed (will schedule an Interim meeting)</t>
        </li>
      </ul>
      <t>R25: <eref target="https://github.com/netmod-wg/template-reqs/issues/25">Misaligned module template name</eref></t>
      <ul spacing="normal">
        <li>
          <t>never discussed</t>
        </li>
        <li>
          <t>status: needs to be discussed (will schedule an Interim meeting)</t>
        </li>
      </ul>
      <t>R26: <eref target="https://github.com/netmod-wg/template-reqs/issues/26">Seems a typo in this example</eref></t>
      <ul spacing="normal">
        <li>
          <t>never discussed</t>
        </li>
        <li>
          <t>status: needs to be discussed (will schedule an Interim meeting)</t>
        </li>
      </ul>
      <t>R27: <eref target="https://github.com/netmod-wg/template-reqs/issues/27">Adding an example for this might help</eref></t>
      <ul spacing="normal">
        <li>
          <t>never discussed</t>
        </li>
        <li>
          <t>status: needs to be discussed (will schedule an Interim meeting)</t>
        </li>
      </ul>
      <t>R28: <eref target="https://github.com/netmod-wg/template-reqs/issues/28">Good to have apply-groups-except equivalent feature as in Junos</eref></t>
      <ul spacing="normal">
        <li>
          <t>never discussed</t>
        </li>
        <li>
          <t>status: needs to be discussed (will schedule an Interim meeting)</t>
        </li>
      </ul>
      <t>R29: <eref target="https://github.com/netmod-wg/template-reqs/issues/29">Provide the ability to see the expanded view of configuration</eref></t>
      <ul spacing="normal">
        <li>
          <t>never discussed</t>
        </li>
        <li>
          <t>status: needs to be discussed (will schedule an Interim meeting)</t>
        </li>
      </ul>
      <t>R30: <eref target="https://github.com/netmod-wg/template-reqs/issues/30">Can the template be applied to a leaf/leaf-list?</eref></t>
      <ul spacing="normal">
        <li>
          <t>never discussed</t>
        </li>
        <li>
          <t>status: needs to be discussed (will schedule an Interim meeting)</t>
        </li>
      </ul>
    </section>
    <section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>The author would like to thank Lou Berger, Jason Sterne, Kent Watsen, and Robert
Wilton for comments and contributions made during interim meetings.</t>
      <t>The author would like to acknowledge the following drafts and
presenters for kick-starting discussions on Yang Templates:</t>
      <ul spacing="normal">
        <li>
          <t>draft-ma-netmod-yang-config-template-00</t>
        </li>
        <li>
          <t>draft-rajaram-netmod-yang-cfg-template-framework-00</t>
        </li>
        <li>
          <t>draft-wills-netmod-yang-templates-00</t>
        </li>
        <li>
          <t>Jan Lindblad</t>
        </li>
      </ul>
    </section>
    <section anchor="contributors" numbered="false" toc="include" removeInRFC="false">
      <name>Contributors</name>
      <contact fullname="Robert Wills">
        <organization>Cisco</organization>
        <address>
          <postal>
            <country>United Kingdom</country>
          </postal>
          <email>rowills@cisco.com</email>
        </address>
      </contact>
      <contact fullname="Qin Wu">
        <organization>Huawei</organization>
        <address>
          <postal>
            <street>101 Software Avenue, Yuhua District</street>
            <city>Jiangsu</city>
            <code>210012</code>
            <country>China</country>
          </postal>
          <email>bill.wu@huawei.com</email>
        </address>
      </contact>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA+196XbbxpLwfzxFD/1DkoekFjuJw2TsyLKdKOPtSs7k5iQ+
JyDYpHAFAgwASmZ89D3L9yzzZFNbL1hISbS8JNc6J7FE9lpdXXtV93q9oIzL
RA9U55f959+rgywdx5N5HpZxlqpXejpLwlIXnSAcDnN9Vm3mfx/BP5MsXwxU
UY6CYJRFaTiFYUd5OC57sS7HvVSX02zUW4TppBfRAL3SDNDb2QmK+XAaFwVM
XC5m0PXw8asnSt1SYVJkMHGcjvRMw//SstNVHT2KyyyPwwT/ONx/CP9kOfx2
9OpJJ0jn06HOB8EIxh4EMFmh02JeDFSZz3UA27gThLkOYdQXM82bLVSYjtSz
MA0neopzBOdZfjrJs/kMmj3XJf6pnmUjncTppBOc6gV8MhoEqqcQJviv2Q7+
/vzZo/0gCOflSQYL6QVKqfE8SRgq/w0TqJ/DEpaFX2T5JEzjP2kdA/lcyZQF
NtDTME4G6hS6/SfC8rtzatMHkNaH/kc8HwOEYSfNkX+Yh+c6xs+LMte6HKjd
nV11nI3LcwCH2j/T6Vx31S/zk3moHsXQKI5KbB7FJZzsjzEMXMzpA4DDQO3t
7uzs7vHf87TE0z84idPQW/I0/IMXtPvdCc3ej7Jpfc2PtJ6Fp+oo/FeYh9Pm
up9np3FYmeYwHcX+NCMaoZ/zCN+l2IFmwsOHbQznZcsxHGWAJXAQcZIUzVkP
4iLKKrP+lMalHqn/BgQYZVNv+jw7xzG+i7BL2w7/Eafq5/kncSJDWGn/fO4f
RxCkWT6FJZ3BbQnidOz91ev1VDiEiUOYGId5dRIXCu73HG8JAH4cpxouD12C
3jAsAEBRhYqYW6GmOjqBvRcEufMTnevhQuVwqYEEwWS1bnB3QxWFqRpqNYbJ
sxxGzualitOSjsUSD7q54WyWxNCCxlWp1iM96stqw7MsHhWqPNEw3WiejsKU
gEiLj2m2bKxiJC1xFCa1heDoSD5yzUMgOYGT0Gm0oAOFnmUXvpnDREkCmAC3
r2UrZYY7mRKBGakpbIePKYUzjmHmZMEzjcdxxH/3GfrTeDRKdBDcAqwv82w0
j3DQFWeBi+wY6HQc2BW2gq4wPdwH7J9mptcIwKoslbNUUD2CpRcIe7WfRyeA
/lEJgFCbSN621Nu3D46eHNy7c3fv4qLPK7KHotNwmOjl58vwaD3ZkxiIMk4H
wwB4k/gMYbrqvOVc3PA4DMDmcjxYhgRyOFfDg1YkaI6wBA8uQ4IKWJEsdAyA
gPvhuZUnYemBZxouCDwLtdClymCteeW+9BvjMYS9sU50nKtwPIbjVgzM6k5i
nAWOKyTUKTKVZHBCIQPGXngEOR9TH4fYTxcKUXGC2x9phARcb3OQttcJDBNP
p8Dg8S/tL6JxzAydhwul34TQHUgljJgKGk8dGhcLOKgpou3xFsGHv8N/FkwJ
zuKIIPOIf6NGQ5xtCkiaZ1M1imElOQ4GZzXK8qKrdBidwNEzOYvhd+x0EgKq
T+dJGcN6FIoyhMQyg9oEiaLUeVeN41yfA67AMGXU3+ry/rL55EQVJ2GOGB/i
9FNETJZS4CPeCKzzyTzHg5VF4DSyEp7ILcWte4rCC6xA9yd9mP+8B8zC/Lsj
y6CDOkQ0gMOLgJp3zRo63LBTwwTgM8kIITXzLnDoThOuUgKn2+FRejyIFfxA
amPIxSDPJHCJUtgT/E7cE6G+cqQbGIXP0o0EkD2Op3ES5skCkAlHqC7dW7vs
XWbjmdpWRxBJR10gZKf6PEaYhrZhXuarR4RT9lfRWHALfZhmBVISYOPqZA4o
DqgKBJ++Kkpg/3C9ZlleIvXTZyyCAhlN6Xp5lwawNlSFzs90vlE0CQBKN0Bo
QLICYUGu+BOYMk4LGDrSXR50lmdnQFXdBS+6dlji79msBIj/SbsEBNJ5Cix4
qoEyLtS8gMV0mZcg+p/EEwCNgutAMgrMQvSyiEIQa0AkEmjAPoosmdNKZ0Cv
YTfM4coKwyzmM4RDoYZAJGVJBVPAUSanBr8Rm5S2JNf36YpQJ7wisKGyAn/U
TWA+6E2DCIELGzBM1W/f5vM0hZ3d/63P0DOrkPlw0zhltyrxCHXyePdv3zJp
+O0+cuXD3qO+r3Txd6J2XVzQaPHYTIICwYJOn2fv0sZ/+xZPAxSuEYwZJufh
ogC2Cew/LQxSVvdzHgNAfAYAQsCbWZgyB/Y3BwAlmbe2R7wWOIinF5oBOmqG
kr0G9DCbn4UFCJs4DiweSGWCDFOQbgzE7KQpiNGFsjD/7X4XeVA2RDbWyl4u
2dIP2blGLLZf0nEjAkib5o56crcRddfdkxm9ulZvL+Z42hvypsIUDkE0X1Ct
QeShcyAIETH1EU6dhclcI0MQblinOrJ8O2E2HveG2Ru8KGO7D+Lsp2l2DgR4
okV2Zpgj7y4J+IBxJTFM75gEHQ2CdwF1PfRpYi+NyVMigQGSH81pG/gFSAqs
QgFdAC5NazDbpPWjBcITkdyHQPSYRllDhNmAJZKZMScACQMqWOo6oEShmaOa
JOewINWJhUNi0bC/NErmI5EhQSgo3FXnTvMJEjBnuNiGy4WMnz+BSYNbt9Rj
YyIBBRr2sfmKJM8cKOsZwwxkd2m0FQTUBlAI9+O+GLDkXOjIkP2yMsosj2Fq
+Gw2BwodGaGsqpjgsQJaFgqAEOmTLBkBxgtKEbVFMd0OTI1ko7DnMAHeMAqk
OQunCjgGyjuVWUXIT3EfxXw6BRnqT03iuBwTWpiA/5VzBhvNHPrK4vOMpWVv
/8TNcla5mLgXMx3FYyDoAQhTmtWPOmcBCLxMNLAGkcNxyePMKIeyRWxYDAg/
bqt/wo/q9e5TUyAC8QQPG9fBtixi5jwHWtS4097O3pe9na96O3dcV9DP4MDR
8GWQ04MRf+QtlPDkgNQPZwR7ZDWiAk9Sq1O9UGjsKlTn2U/Hr9Dihv+q5y/o
96PH//jp8OjxI/z9+If9p0/tL4G0OP7hxU9PH7nfXM+DF8+ePX7+iDvDp6ry
UdB5tv9Lh9lR58XLV4cvnu8/7TQZOZ4Low8JEMDyif8WwUgXUR4PmUU+PHj5
v/9/9y7wx/8AwO7t7n59cSF/3Nv96i78gXSWZ8tSODb+E2C4COAcdYjYQPgU
hTMg4QlKMnA3TrLzVCEewLHf/hUh83qgvh1Gs9279+UD3HDlQwOzyocEs+Yn
jc4MxJaPWqax0Kx8XoN0db37v1T+NnD3Pvz2AUhjWvV27z24HzCOTHWIxLqw
JHExHWZJQWeVa1RDwgkwO75DTm4JrAlhh0wIVcIBZNKolPk0TrMkmyx8oeft
22MhTHdwXjzJr77+AkaiM2z51poqlszjLqk/I82E3b/cu7t7cYF39naLah8E
D3UBoi7Kg0sNM60zDMhO2WIzGwQDta+KNAb0I27TZlBAOiYM2CrTmcgA1fZo
jEFZHXUb2BRcaU3EuwCFIInHTKjQwg3cDPVimNAo08tsIe2mEFQG9pfZAWOU
I0EnzXmhdGXZLgBS/gKvrfLtV2jWJw7pPipPclSU0WZUp7uP2RBQMIttUApY
IrBYj+POCzyLfz572g3gLldw64FFJ+ANL4gxUHdC82IO+iYs9cfjF89d211B
vYOHL47k06/3vkDSwpodaeRDDToX8hUdgtaEFHgfj83oMOoYBQemzlfVZESs
wGOknsTfAyNbiFmWpZR+TT/CYazo4Qs3AW5EBj4Hpp2gsZa5MZK9ENcDyl2k
i4JFAJauAA9QcKmevadVOnMk4pFZFEosS7xP6liWSqBi5pR6zif19tZIPnSK
wwXAzkmn86JEewv831OahnqcMf4uzDbl+gSbBVCst2+JeVeHvdiqWM+sDCGD
Bqhno7poLiIdeJrhyYRkxmrYr/AwIgAsy/BwCiBcRPIX6Z8aRGPh3XRtAAc1
iWFO7UBDG5pLRa5rMYBlzs+VsaLvydfoJxMrL4iQcjlyIAKkvZdZhIRcEF49
f/zq4MXzJ4LdTBEJVY4eH/vf3NsRkr5vlH1P3XPqFHFHi7dEtTqkudZdhB1e
FwBonujqRSWXIn+BMxJtr7RDbC2zWS8BCCVoSmHLZd6Boxk5m5CbK4BzYwtc
JwGEXtIOrUWP0fzmUStsGBgTCFlAed1LaKEshWACW3fcASUXzRZqHBIFxbcD
VJQAjS6AQPZUPBrA4PM0/mOuxW4NYqmRFD0zLCsbqEIahBYK3VMsH83YGSW2
GFJevC8aA0pXwJneLCxPqh2L6ERPQ5VkBofjMV2IPMtkTlHyBi3qtvAzb+2o
LKA+cyyWA5FzQBuIScb1DC+eZkB32ruW3YAuaoyGMO/WYwu5qCTJVaTF9uvf
D/6HpxbSmcRTtvUU3lLEZCRaTVexwZXXEsClhO5o3KJzZdMcqx0AuuiUJaRZ
BjrAEA3a5t4Ru0XKSt2Y0DIj0AboJGjhVfSM+EZvyo0+AJQZOC/QIrQZC/1B
xUiLjjPUgIFw5tG8QCahgezDVkHGrRm5DGhJUQNOTNyGBIGRNuYWNEBixxqw
iend8sgoNkSuF0c1HvD2VkEfG8uVT9VBTvXJOYoxICNx+7ppJO7rfrcuY53Q
/STktE6qBh6AgOq+tQY0NBPjuTTOHP1KEQtFBdo0rYWjshw8cpHY4HKO5wne
knO460QHMkVhB7XlFnChQFDCnfrSj6ZT71ctrwEC1BpZ2QJL1jBghNlU571x
GJE3ARqgV4KUnJycBgGyQV4AHQu5F0w/RiwAM6vVTa8bq9KWYmSgJJi+cOi4
RuuoqQvDcuHPUU4iqmFvJh4r8YXt6aLn0fqBJek9vBPb4yzbHoY5/PenEGwR
SjoweLnosA2hK9wWqTtgLIWc0O8AB1T4+XqF1ncYBP8PfoK3qHKrdtY0cIxj
oLghNbZcYaB+tZ/iz9vKX9QW4wSgXQe26NwazWYeXcbW/X6/rZWQ2MpqKg1W
AnJpN+oKUF7ZgBrBMVzaSBr+idBJ50nyemXri6Xftn/T/LT6ifuL570ILvig
iSC2ICaQChchIIiF+M3qP8jCZ3E2L1CzQue61Sg7lk92VKLDMXZFNg6yvDQw
h0VfbxRMsf+SaOe2Cm2udllvAntX4tCVT71iokWSI5xznqKS7ImBRBzOdZLU
iG5NgLshivbbr6d68V8b492N314jwOTvofz9ZydooXTqM6VbgisNSvfrUrpy
CYljOri8+9WGscPBqeI2x7stu2ztwCT28vmvt476eoZXXY+3ritSdP9nOXX3
fy4fb/U4y/u393sHavKZhzSavRceYqkjEUdLG19/MnylqegcsTpxphu6TlPR
YEwyiGGEZ8KXwo9qAYZSNt3dxLqCUKE11/itIoWcDPSXh6SDAF9AjRnwsiRL
oC7inOL2RJ0itxl6fVtGJq6Co6GJ1v5+Tu5KdBkxAwWFt0QNVs1IfyGTV8ZB
cqiiwKoTT9/HmDB2mWUuiCphVZf5bAEbOo+TURTmIzOmp0yx41D0YlwF3ogi
QDszm0gWEitEg2oMDtYVUJbhKarXHHYG5yX2JHYIYUA2HSL1huEL9lMO53FS
9nBWDMTqYJxuOgEcRD2IIsAAXDFa5zhISL4X7buxG7KJIcCzfGo5+0vzZchh
AOiwpcPo+MYw4/HY6++S0+Pw8ePHGLZ0p7/b29vZuXcDWlhFvSJ5gyCCCGCs
v8ydGEhDPYnJzkiQCjaGGx72uA7IThk1/4pU6+8mhtz+xKSQq67HW9dnKeSz
FPJhpZDbFSHk9ickhBgf46LuOGsxcQfBC/RcOMum9VlaPiPusRav24WES9Tc
0ZvWcTXaMhhXi0nz0zZ8Iy+ywqpjm9ZDzMOEhv/7+dSMO4TAc1VniLW+V10Y
/i7ZScqRvRzMJ54pDzBy+jai0cbHXVxsifcBN8khutidkosSzpI7c1MLzNqD
FN/BMWEllms4JmxQJwvsVcG89eYICWu9QFfweEL3SM8wVivBKGfNohWN5rs8
yQ4P3bu+jEe0tt1HGng+Ugrx0CT7+x5PiqXynJoyYNVDEeg3EoEoViLrNF+s
mt530QYcjI8OYIwf1GmLr5blz+XbNu7bIJRgFT3qDQleaJEDJtPjjRjHbH0g
jnVogavtixcAfTQktuOnQA46ynl/iQcEsyy2vpnOth3H/rZNzIdmEzcjqlPG
JYsaC6tJYw8NjKZDmI69SvYWY0umUhRHgH6fJMwlBh6DGdh9iRBJ3bUMOPzN
XHFZCULX7pLhZ8ehq/XHnJzu9m5ngC45+4rE/IliP4Bch3kS+6HOEkYSJpMs
h3s2ZZ+PWY0fM6tGcQF3tjBu1TbC0a8LK0bTjZNkjsmHpUu6cmgKIga6ldnn
bn3b5Qm6Qd1CP7D8AafycVwyu+v5QbpX3Rjwv4+zsb33vTFEmI+ztTs347vi
tdeXU6d6gMSAnEBzz7Mu35LXwRI7VZPl8QU1g8HNc9I+8FcK3OAYGRPrXXN5
YzIMOZkp/CKSxL+FRxAxOwqksckcyF1NGFDqEGlYUEt0xFFyHc3zAuSqZNEY
kZobeocBc4H9wyfDw2pGJdMiWKQJ3CXCijJEnEe8uBPaoZ85EHIEn4TfV0ws
sdesE3aERhfeh0MMfh4iG8OkDKZk2PQmqaJv4aKgNVnF5Z9fm4A6UlnF/5UX
buVlW/OiLb1ky66TRzOWLb1BBFcvvOUOys1bdwVN/nL9FZxnS+en315fh6C8
9miIC9p8bCWAt7daOH7QouO5rKkim2o2SxvJbpyg+RMk0E4lcjmYUUK8plTZ
anBPaKNiQdL5FwU8ZSyfejoIUiWjWlaSiADpDzwR3WX4VdKBMFIGFpXHkdok
k0EjiHYLVqh7lTBZL6dyGEan2sRrYWYUhSNRklc4pPgeJ8WQQFeE8chLnzyP
ixMRS00WZXsKJZlqifYFl6VQuszhsLq+2JGsXojlKUwYvUkOkvjkgrK6K3Ih
6VqZHHBFNEO28zAsAIBHgGHAZX6mOMUVoeOeJSCsaDAcPAh3qwuqBybCkG87
bgnAqitT/vBTnU/0KLCJf9WONpkVtgL0PqaE/VIa5rD/WcYqM1GnoLEyl1Do
DWAHrW06PEUzP0A10iM0UAg7yBFQrOkWwhswOvQ2C+QktnPqrg+cJamA5PLh
RASbdsgR8W5ahPRIR7BCU2whIycJjcvTuZTAHmZRpZZG1NMGOIv0RAoFECqC
dlLZIg9CaNCq17MLxfqGTDSDTYNDpdPQRwrxS+GCYka02hxTznwhidXIJLcq
jFt8P8uW45L6W9dFCDkLQd1nKQHB3zWpmEoJzcrG/pRqM7Tpl44ESe5iNWTX
DWSn33KHxwD1Ds16wUKWBMxW5H41DoiQllxiHIldcFKM8U0VXZPOrGoaKLn3
tKmGwM4+75oaYu1QnwexqZ5DjVPztesTGi9boi7EGCEkbDNKskLb1AMr9Gzh
DG1mDQ6QpZW7siEttMWemifu8pwSQS6RM5j5N0mxfIlQsmewC8pmzkhiNn82
7lxo7D9IrZmDEaQw3+/uV3d3nelKjdl45qqU2FoHhSMcJh/EUGJfF0cq+z0y
KeZjhFTVBR3sOsJHJRzUwV5X9ggjH+zRvfAIkUIzgddgl+pmgNifGILkHSRZ
VTrqaWOS0H61x3agp3vsV6D8IC4tEmxyPzQhABbq0ZY/sigeHbXfNrj7Vsbf
37OqCqgCZgq1ub9iCs/I9HTpFmwDBJs+N45vojLYi6jECA9q01wHawZH9go0
AfoCEI1v14xAcdZmXf6yPHte8/Qq38KSMFQ3BaI8NZ7jem4BLdDAg21P2Me0
b+QiYPvAV7wat7ezEmQOWvWlWepzXeA1Vx1YQsa7a1ktqmmdml2RndDFtj1X
oGwz4B4oz5E51J7vtl0rCT4gkDERJu82xiqI7Tws6x04wp9lQtjXUz1G4TQ4
AhIDXAoW9Sqb4RYfZmWZTSnj6GReW0d9yCg0jrogQYecK/FRveybB7tbovS6
FYTjUnPENtF22zeo992DxXB6Tbgg+ySK13oasjMRhaEowtbaZcoWWhTiSqAk
HQLuA5Xo8wwkfkrkJ4BT2iFlPVNyLebNZUPMLsSMCApQJxkXTuiMMy9SjfsI
c4oasRqBNRlb46sMislmRK73jZAaBPeJZg+qZPQcAz2hAUyNrHn/kKoygGy9
kEBKl7jE4e/3+bipioOfeQ7EuMC6QREJKmIFLcqefIL2z7eDEB0UFzWZ2qQi
1IRqFsjN5FLSiuXCIRDnflC1zZ6HyWmLpYD5oakyQwy0y5Vq0G4C7DxgGYYu
DPfHDzYKT3rtLZFeLbevlwuScnws7aBZpV4AqhA51y0/12SSEIcR3S+WiWqF
EyqaYZRgGv14wXIJycKblLbokceuEKOusKKuT8+xoGRguYi4tjJkUXnKg2Iz
AIaJMtostrqmBpZBbzqUgGswoc4lgTPobpD0SrlFcSoZsfY4OFV1xPsLE5C1
WMq4pV7mGiuHcE7kQ7aoObWUAm5QI9ilOjUj/Ua8QFbS8UqewRnEgD9sXUDF
W6xAadBqPHDeUqNcA+nLkjMj/noCkwh4sGbkbEdUL6IqcLllFG7XdbNhYZ10
tCKEFnwwBSkf6S2K2+aOWRVn069cs9XwKzrLRCn1iSKtRwWCQiii8XlaiVLV
EcecxAFIO3hTycD2nO/GcTbPqdIXYONLJzO9IM4VBPul5NSYwbChcbZZtKLI
tIUn64WuwxbLp+5+ILmZkl2zheh1Cl5PR2wi9gLW06Hk6F3mnhmJzqapq+El
A1EPPhRce3Ud+rBJKVmMmWTxoOPVb1gqRpRs4B6xvC0qyVawp1qQ64nJU0Is
NpK/rGTJMF3TjDZJcyPA6jpYt4KxDqtZRnWYT8ZlGiQzih16ycllvWXqFWop
G/RQE7NuvS6UgoUDSSkztgWz4urJ9KbsW+vCLF+ngTzJx91vT4N11i9P5crD
9FQc7kZjazMTk68fNf+X1YsjKGf1EibKkj3eUFWJRg4CgzM1RAE1CFdT+JtH
0PQafCOQptYm0Gxi2Ns0qxaUNCW6vIBXZn3i9+wJcrguZi78K0dFGD2i1m0S
BlVw4QVOYP+jhei71pghJzufMdbNcyrVRx4G6hVYr4MjvYhPMV12YBkYocrE
6IgQkmmRtcOKpLwv8z21+Nlh1ZUFhg4SpqoqTJWLTao/RoTUzqWYD0l8QCJp
QYdZ1ibn0bN6Yb5j3ChSgUV7/WhdTmQE4RfL/pC3yGJ11RogBMyGudhLJ9V4
Sl+Xp3EcrUzDs3jCsdiG5Xi3iCj+CMPgCI0RDzACINhkyzC6yyMtdTiEeuNh
IHb0iGIrQJNZsSWkFA68MLU4zK7JGIPVMWqdjCHF3yt/O1xQnB3VhAxcYHVX
nWRwghxZK1YaONbbEuLxAESWmn2TZRWUrw7HlS+qJhYxQLMqIiSMgCg7sBwi
iMvKcUjXPpf6ZFVx2TSEdhXA2FOkKkso3GLU1RkTDoCMkGZM2eUzrBhDAonn
UVW8JuLC1JpLV5jLYmwz2EU4tkS+ueT1jcJSMhcEFzHLRzmjyRMDYkvMoDmy
SHRf0IuACIqt3sqAbLb15IoBMVHQX5MRXHUyFsLFM4vA8Sg0RkLSAD3J0in6
p9kOU9s4Fdh4nFHYJofjMAfG/rKPnkeTeR+mvgGnA8cFS0yyJY+x4CCVHbKo
gdvYKNx22UAgVh9CUiNdb+Nvb6aJAMBZlX07sbc+nJChgqs6BZnhG4WySO7v
wUt9rxlRPCmfJxTrXntnHF7sC1wtFvC8t9C0noIKwnJbWm9jFf7hGSEApY/A
mITReDZni/DqNfNyH5uUhdzYXo3MEucu7QJ0ERgXXVhYC0ttopEFZzSUYsum
PgBgsbhmcSLer5KDIrE2Hkmk3MzzunGZWUYkLouF/JZIms1kYMLl0wbKn0Ad
gdkgLcZObS+TDzm3xFLio4RCfsNGzAJpAxdqrswbUz1CNENbGi7CNPEKy6/Z
qsnXx9j7Bd+r21+swHxij4HYs+kOs3UBJH8O8lT/mKPu9dJUeiwaCj4XKPmD
mtmCkEXFg+nKBVI5H44jDa4WR6qWx5GS5BzYxCBb+J0qRU1Cvs1CVwvtL45I
tC2/CMhsZvYn66oZF8FDUbhTL0laDyHopVGHYl4vb5lHqIjiuks6BC6ihPd4
VbFNewRo7Xly+M9njwfAp9TR3t0e1tblgrCTCRJ0LnNKFRIIsl6tTKp7gGG1
PcaKkMg/6+4PPCsOmUHPYt1SDp5NI1aSdG7vmA/cer+Doab609idvXIs4EQ6
pzKfQizO8TO4uKKCrYBB4AqOCmZxwVE2zVZW2bPlRnMUe9AsZ0pemfMF0v77
949f/Y7pX3L++NG3EyCNSNXv/94XOJSXHI1bFqovtKRu0xoQ8LFoEX7pTMy9
gN4hW/bbapnWC5kGBmTUhvOc0oWxO9nTZr2bk7VcTKgwJ5dXcaJN5lawgbyu
N86yDTIeyiatVcesYsOCYRjmG78vw1+//G0FeysUxETsGApbq2PcrF7sYemq
isN1Nyf7bq2VxVSMrpkRUMbQzJWk2q6zxfSrEy5bYLcFXzxQrEZiv2zsJQgd
GLJ5FYTmsVahdHux4hpCc4hAoQNmKcyeloUpnIQjljm98PQqpsRpSDSwJ/VY
V+EJPlHCBXOw1u6oYXKmNcuSMeot1wndL9EgXa6plGMzUXns9ZZJxcYkNeG9
qPGCCunP6fWITvNVILsRhkBHIROQeAfgIbYKVaMWbYI6JeJnkk0ooUm/IU8B
ufNZ86pRnpZT8iO3z7WsH51Lc1ZQg9A4/9FAQTUOCXc8jji+AmIHXGqRaxHX
SlS33pafaSEuyKiDmGhadNTRywOaF4U7HN8uYIrhGeTKwYeP9AMWSV5dFrj/
jGumvb3lB+lz1T0krfT4kXpxhqqGPm+kl3lVPpVf1bMRrbhsDRJlJuGG8pdq
bQwS13/2ermX+sFRBdUPb6tfUe9xsW78NelC7ofpe62Nlyb2YGkbkyT2gD5E
oA3e4N+7/Z1aU2PHkJ9vRe+5j0EZNtmhZqkcBNK//sVtDOS4r5blIXg5X9VT
bYVkH5d9ITD/9uDFo8fq4ePvD58f3wcRP1l2WN+50sM0QEeOq/20KCyRcAqx
E+/ubn/3G/gMl1vMQtCSOsDYB9h5QHeqGIAyOEiLAQG1HV9wABS94jdqEZXf
ICjZccmLoPk4+ZqjIk1b+PwbsYyKQU0Oq4PhF19+/fXuABQnevOC4Ee4/woH
oikvcCL/FSf2lNBrZcA0nr14pDbrz4VtqZ/hTzzj7/GwaRxSGLgSuer8/L36
WQ8HoIqX5awYbG8jduCbS6dAnHA7fZhx+3yyzeRym1cMvZ6CUjgw836LLzyV
2YAbfWf63efW/H9T1rv2BJn7MYO0PTZ2vzpG9a2x5hCtj3/Vxmi+/dUcZ9nr
Xvc731Q7BMq/uAzay6pBWlms2BCbL2v6PPJG7e5t2OvKAVWoY88WOXvuoy0q
yc0v173Kseqo5MOh66+gUvsmKUhiqUJjabWFkyOyD+4Dr6ZRyc+AZH1kJjzS
I3oIbDi3pXjRmxCnxiKCnwyBoeaUmD8tOPSKO2e5iS2qpUWiAIChZCWy/Bmo
t3OMHcDqhTbuy4uj5cSiCJkL1TEurP6LYhiLOkf6LDZOCPXw+BHgKncguRvu
6YlfsOBuPzIQcODbELL+FLTRBFVqGJE4+xHKJmJrouaPpBKudNg096jEYbR2
d0hW3UNld8uAlHDE0CZTI90vNxo7VyMSCazWXpvo/Py8n4+jHr9LSFPhFNvw
Gbbe+oa0YILLkwPuKy4e5OBkX09olyA00FNEdml+/fUNjJXe6PK/KKXh76aW
OP5OBcM3JP5xw5YP56+wdKb7zXW3dcBtx1p9cJpx/5cNvhsbpiL4RqMQsSD1
knLs1QKbDw9eqt27ahMBisXYtwSi+DfWY99aXo5dVcqxS0DhkprsHeIMCrPa
6Xi9ovkSLV8nGUTO0TENp2G69Q2pqTMN5hp4xAPGmFcVBsXsgp2xVX4IP3iu
yAK/Wb6OVyaDr5I7aF4Pywz46c0nu0aKoiMpx+YDUMQBSzGWZrbMJzNS36zq
I7CjX3iT+GVi15gLXU5v+MECb6ArTWxkr9q0FSHsG7W9bSw9EkgEOPnLSxTZ
3MLGIT4D0tnuXAEwNKN1VJjqqyac33q8lCnA6rr3+9tGCOS4bPLf2ULB2Vis
N25jeMVdfw4TmcRiPtrYbhOKXBrORh1qJvLRLMKCzdWjxcdRLz0wShsldDRP
OFVUVlftpQ4AD2yWBxpnOwDH7ds4yMzF5sO1/JrdSiZnxEmQfwAa0aB9jkH0
OleGB8BvbG9Y8xIBw2Z6SY1e1zW0jiwuWnNNuPPtXybhryJA+66X8SDXc8ZH
JogCt7KB4X8bduWFqSG/RbFcFP+zYW3UG0zHKX7JTxOw3asxMz5d4azpJRuR
Syh51H42EoF+G+R0Byr6yyN/XhpSLSbzUqTERr164IsLZrAVHhqHg/84GiHP
6qyw65CJydi6Qf1G2YrCIShbx9iRUN++EGUK+OfxfauSqRfeA0EHfk0CrCng
vR7UqxQsYCX8B3zLTb3IYyrwzyGMx1NMkMrVkywrZ0BxS8pbakmdMUWb5WUZ
2AY/vUkPb5rCY81nOgNOWOIqXV7cmI1qEOetK12WLOAC/lToWra7Sf0MJiYW
XWolix0MU5eqrz5JTP1TdKgBrCZpSMt7moWj5ZuUV0dDlYRDIBbeBfGc4Ih0
Jgh2Qq4Utt54cazG+NXMYmVPEFuj0MdP85i3i0yVk6DxDC0FMcemSDo9KTTn
KGCOjhJK2LCyefAC7RZaa/Jlj0y2Fon/NuLYPYOHLm6s7JHqOsZgPQHpTClu
OT7z8zTMJ9pG3VaOTvJqEmpRgUfhcsW8dLIgLgp0S4w4qaSZOGeKZ0s7iQqR
3REkopBDuEl8tC+B2rg9ds9h1eo8JB/VwcufeuSUoXMErAbpSNDnRUqy6DMk
5IdTl+uz1j1pyTGMi6DtDnRNBfcF4aIDLsEWnTv8iCCZRf0cpG4g73OGtuSM
vOhJ3lQMPsAAQHsn5UFV/5raKgzGjomZGWilzZDZxYRLBYZ2EXhDYx3Gd8Ua
S0VrKmYTBvz4GsdOf/sfvV4gNPMRF3fg/lHW22dtNgg2j0EOOvp6i6DuYqS5
bjucID1l3ZVss9B/FmReIuVjshBlM914tarrwlFM5lbjaZxKhjdB2fo5beIK
juJCiDn86EhWRqM6odGccWReuqHMvyiHQ+Y4d07ZciWB+hQDg26h6ax01T4q
+dZ4ZgYSEhlkrfS5/hdFmfQb8JN0BnJZjhhF4WpkXEPGcr8qNEwsTtMu3ZbB
3uV6weZEePVcJYgPgl4TuPSYMM6o5ewlGJriUzSHNTYD033GYYJ9ndLnm8m7
9Qf5/FFbM/WaIMVlgeqYWahEmMYpxBoVQKaXXZM25gcOtizJqasuDsiPs6TI
MDymlMMMqUJU2VoJxzkjETXRJ0/ZHaIiQfM8o2BiLLqJVpz6xlCw9R5qGmp0
Y2a5iJOCylITi1MJsSBjxJxO7AToyJEjlThvKt7JKE/IkUsxJtD0R4DLxIL9
pxDNtEA+er37JAgdYwyF8CBPCuJSZREGk+I3SPCCAG2FLXl0lSRBWyiM6A89
UjR38ajkZeNRhYwGUjJVHopixoEcNG9WorI+tyWOC7aw1wI72OqoKX2d8mv6
/T7RTH7r6HD/+X7b3nkismn989nTDh46WvsWLe+95/QVO5x8T8xPR4e2TJQZ
yI7TkafM7nx57x7V3SHR1MjS0HWgrm2Kt91lErQcHrB5m8OrDh8ff9+3rWA5
A/V8e994RMkbC1CidZNajAu2ml3fVRdg4PhejefYai0oVcx7Aq3myGw64sHN
I3A7eztNyOFyB6r6sxpYdoNet/VBz96N6grEu4A/3mvtQIEQ+R6o5/ZbK7h6
/a2dU3SXXq9H9QDYlYhRMv8j+UxY4MFLZmpUBSAJt+AycCTCc0tKimLHaY1s
sfgqL7n5TqylBQcqp2l0E7rYIlf7UxrJMI8n+LyoDCoO+Uw+9UfsV1ySqloV
412dW9XRfK/WdDEl2yUZvOh/rFDX7GsXpg2r5u635a1d9LL7zTrJCgpb7AA3
tKahHtvcMl2kG6V4l+13LnqVlWtqW+tqLAEtpsE2+9OF3RbtyG0GLabwnzcR
frJ09AvX7gyOdGU7ms9YyeTfb6r1kfZNzNHlKCMplTE/ekxBHNWIpeB3ytfs
oBGkzvV/d+YbNmcjjYxzxua3b6OlpQcvPjKm+v7XVidw1WMrQF8OiH9j9F8N
lg9/Pa60nlXXR8q8vKLIK7pOzzPnLDEJKl50lR/J5YqpxsWgWo+qVqOIgssH
qmPerWj73kR+/4qtVGcP/3ens6TokR+c75UGrJ4wz8jAWjKvTGlHqJV3Mu9/
ZI36UnA03vDeFMtHaT6ss94of15hFPptWcEoCe+vQA6V8R49eGea/alzrNO1
I8hmolEowKiiV31Gg39HNOBU/aRWlZfUv2O2eBkycn3qcRPV7OpP5FyrlF0d
US9ruxJpV3VuR+Bqj2XI7P9cXGGddST3f1bUxFyK/JVWTeS7ZHlXm7X9MbL3
P2v9cl1n1sanV8CDtstYaX/JxVy+gPWrCOIdolqknwn/Z8J/JcL/rBaObQXJ
vzQLWHadLi9LuveuC1hyJ9Zf0Z13WdGNMav113/3nSD6mQNefdab5YDrn/gX
73Linypb7TJx4AvJaE1b/cxuP7NbHtCiARnd6T03rGTkW2r405p3skPJB+9s
sGnB29eVF6yugJm+kZbXauufHPAd/vTEgneVltcEUUCGt5E2ZRi8U/7B1sD3
6lZ9eoC7sjxV7vaWi1TrwHw5iZNbepMUtfTHY38Vxzf+Tc7mYwq7MspHEm7t
Cu7cJHb6jP71+8PEKv2Qyrd/UyLiBBeiuDd3VisoiS8s3dwx1kSwsjL234q4
mJ1+ZArjlvFRyYxbxl+A1lSu25IpHPlxisLfkfysZQCpo3z1oN/92G9KZbuu
7HpTk3r07pCLxO1jkbi/IHp4J35dt1H9br0nz1ErLn4irqO2tS1Z39WmvZrl
bOm0jU//Cm6cJRdwqb7KA37Im1+2X/2/hajz/vnDexaS1tvA3o1u4MO7KOpi
2MoNfBKC2bvcNk9X/NuqiX9RfnUVn8s1+NUH0I0/PYM+b+4mWNonuLn1vRVl
K4w+y96fZe/PsvcNyd6X0YvVpNU28w7uk6Rql1KSv4Uo/3Gv3dV5+fu2mn4Q
MLQoENVtmp+PFfn0YcDQooZUt2l+blKyew9W4/dOYX42L2v8+xGW21ciK73b
N83Przjv8KYnfhA+uNrM2PAvqRhdT0e4ni6w/Bp93Pvt4+c7qEb1Y38n/ag2
VB1gzmxin7D9G1pOriZEA7CsJpRkqAV1cqwBX2/9AdxcHy+Z7QbC6P8WkvIH
Qpn3LOhecRd7tv0EJ927c5MbeCcR9YobuGPaA3qkmqIQdJiXJ381C/jy27cK
03wzOFbMOOIUfipJUi0/pI7h3zlQd3yB2BRXxuobpkT2S35FJzdPqHoVMIb8
+OtsPjS1m/pSm4CfmorfKKoiLkX2aCJ+38muxq9JLU/sBr/a8Nkjv+EhFmxT
r7gs+eavpvTxJC5P5kMsyC3lyXvnE1uSvgdTFdtc6g3rLQdHu3BSP2MdJawe
6ir49KpPy2b4kHSXHzEoT/CDVK9sqzalOF+l3tLW681rL3N7dwuT2Xv0Atcc
3+4YYDp8lk6wCF+qxuFZllMDBuig8hSSqzyzOYI1w1BHe7Bjl+k+xbrgWKkI
qyRR8SSzl6ysPPKJb2JZXm8/XWtHe80dmaoVVJOsAGBh9bI4pfJfVOQVHzvE
Kmd2c/3r7PlOc89UzI7rzKWLSrEM7wVcqcFZSE2qs5hLwqy16zs3fI53vT2p
YgH39409TRDu4hFX90C2al4+2cRaa64cGJakWWsrdz/4AX5xnWuKj7MJIKTu
IaE2PzUj1eca722uA4cvmnCYgooOu8TyvZVDnXPZs3gMYMHyeFS6DGhdiEXw
cXEZ4hs+FooJhfyeXa6J1lYB5ZXLWwasLwFY+LRqIvKRAkqd51T2yG6Dv1ln
01/eMB5/VbmbSC3xeQKpBbeZxGd+3c5iq/JSgHlVZ8pUdl5mWNSJi6ba53Yz
rokIrWHmvFhnz1/d8J7vwZ6PpbrfkCqRzPIM36qh5SudGGboFR9cZ933Vqzb
4OEmvof7Y6bVQRLmp+ZNwiKMRwquxznWnNzAMlmZ7IY2u3WzSI3XZRnIpKQn
8t4HCLuvAXaH7TcczxgkDPvYKF91eZfLR/31MeHrq2ICPvGaLB7Qi4W4griU
urKwxzAtH6yzfwYhQWF3B8CA75fVL0jLU3XM5obA0OHE7JNpyNLsH47No7Qm
4KTCn/zI3VqCy84VYKU2aXH/wqJ4+MRtTqyKaoVf50Ltohz3klCBiwmTKMNP
hFK91UZR7m1Xm8m802nYZKWW41o7XyWzyVW5LlHfJbltqX4srlkWrb1Tfqdt
tAhq70T2du8I0rqH9ZaoQYx3vJub2ctNi1+7KH+9GI97w+yNoy2uLHS1fLg5
n8pVbdKwTb8qMlUPxw6ZzCJSHYy+niLRIra9Gwi+WOc4W5BzLUq82yZ9ZUW5
5IpdthcUmuShLaoaRrxjrXUZAYmfC/dWR8qyp+xS3dsk49ci1fdx+cN8eG2y
8FXlDJhAeNVuW4+h5QjMw3+bXL0YH/BUtwDEa0GgRVxacTJX2aUvMCXxFF8x
hSkn+o0vIhlxl8rh17m9X1J6rU2tkqXWuj1fs06TmtcclxSI5src8hiY9zy0
PIBtaIjV8XRMintYRGhyQfKR01MV/Nd6B3plqeeqNogds/f2LYelAwpW8Uf0
5RvJZCZOU50jSqlNukBFueVVMg9PYTjvHe21bBQtwovg8Fob3hXubV5SkLch
CnouM52OQvdeZyb3tMr88BavtZGbsh+hmoBVJ/nt81PzmiftDmWTZ7o8yaQA
PNpPapXJzblWj3OtHe21E9gqUdF6VIgQa1ugsAmqYIEPAlNZ1FQd4qsD8VRN
tcYC3LQblFJQGYrHXK43dDJlo2w+Pyzk09gsk0eVNrY31trenfe8vbt8WKEU
x7TvS5OJhMuu6/pL1aG8BxC6s0QLylr7u7tqf624hxXpV7zYzbpUeMOvp98U
uFFIehYXILvRGx5iZLSQpTdh1wHjF+8ZTVAgOtZ6Sg9ULmaZfV5PcynstRa9
RDa6sUWjNLQ/YtttalbqXmue0tOYJzqZrbX6r97z6lHK+T5jIkoP2bBbid7e
woef8MEthfIjaAKI42Md0rs99Li7+nGeZusR1HvveV8o6bzkyut1gmreobR8
Dl9zbjwZstauvn6/u7qDMsxBmFZfShrW5Da0MjhTw4O1HAc773Uj6A/cj07T
7DzRI3Z3BG8H/OiOHv1XZxwmhe5csNeSH7RgqyAI4qfiIgzTU/U0m6uHOp/o
vKt+pEfSj9GmA1Kr97ovP+VxlMHYZfAzvqfLr1cJ1WZHCz2KIS/K4otMgDXy
fFNcXX3RX7Gq0O5J1x5boAffaapAivabN9NP4+i0ByDN6YUPgSM/6ZOqX/B1
YWupHgTBbcVD9aaheTmeXLW1qITezo7XVt4NrnYYe63H+Io7eqeq/fAki0ov
K16Zhj/C+T6N09EwCUfB/wF2246ITucAAA==

-->

</rfc>
