wdiff rfc9595.original.xml rfc9595.xml

<?xml version='1.0' encoding='utf-8'?> encoding='UTF-8'?>

<!-- draft submitted in xml v3 -->

<!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.4 (Ruby 3.2.2) -->
<?rfc strict="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>

<rfc xmlns:xi="http://www.w3.org/2001/XInclude"
ipr="trust200902"
docName="draft-ietf-core-sid-24"
number="9595"
category="std"
consensus="true"
submissionType="IETF"
tocDepth="4"
tocInclude="true"
updates=""
obsoletes=""
sortRefs="true"
symRefs="true"
xml:lang="en"
version="3">
  <!-- xml2rfc v2v3 conversion 3.19.0 -->

  <front>
    <title>YANG
    <title abbrev="YANG Schema Item iDentifier (YANG SID)">YANG Schema Item iDentifier (YANG SID)</title>

    <seriesInfo name="Internet-Draft" value="draft-ietf-core-sid-24"/> name="RFC" value="9595"/>

    <author initials="M. V." initials="M." surname="Veillette" fullname="Michel Veillette" role="editor">
      <organization>Trilliant Networks Inc.</organization>
      <address>
        <postal>
          <street>610 Rue du Luxembourg</street>
          <city>Granby</city>
          <region>Quebec</region>
          <code>J2J 2V2</code>
          <country>Canada</country>
        </postal>
        <phone>+14503750556</phone>
        <phone>+1-450-375-0556</phone>
        <email>michel.veillette@trilliant.com</email>
      </address>
    </author>
    <author initials="A." surname="Pelov" fullname="Alexander Pelov" role="editor">
      <organization>IMT Atlantique</organization>
      <address>
        <postal>
          <street>2 rue de la Châtaigneraie</street>
          <city>Cesson-Sevigne</city>
          <region>Bretagne</region>
          <city>Cesson-Sévigné Cedex</city>
          <code>35510</code>
          <country>France</country>
        </postal>
        <email>alexander.pelov@imt-atlantique.fr</email>
      </address>
    </author>
    <author initials="I." surname="Petrov" fullname="Ivaylo Petrov" role="editor">
      <organization>Google Switzerland GmbH</organization>
      <address>
        <postal>
          <street>Brandschenkestrasse 110</street>
          <city>Zurich</city>
          <region>Zurich</region>
          <code>8002</code>
          <country>Switzerland</country>
        </postal>
        <email>ivaylopetrov@google.com</email>
      </address>
    </author>
    <author initials="C." surname="Bormann" fullname="Carsten Bormann">
      <organization>Universität Bremen TZI</organization>
      <address>
        <postal>
          <street>Postfach 330440</street>
          <city>D-28359 Bremen</city>
          <city>Bremen</city>
          <country>Germany</country>
	  <code>D-28359</code>
        </postal>
        <phone>+49-421-218-63921</phone>
        <email>cabo@tzi.org</email>
      </address>
    </author>
    <author initials="M." surname="Richardson" fullname="Michael Richardson">
      <organization>Sandelman Software Works</organization>
      <address>
        <postal>
          <country>Canada</country>
        </postal>
        <email>mcr+ietf@sandelman.ca</email>
      </address>
    </author>

    <date year="2023" month="December" day="22"/>
    <area>Applications and Real-Time Area (art)</area>
    <workgroup>Internet Engineering Task Force</workgroup> year="2024" month="July"/>

    <area>WIT</area>
    <workgroup>core</workgroup>

    <keyword>CBOR</keyword>
    <abstract>
      <?line 123?>
<t>YANG Schema Item iDentifiers (YANG SID) SIDs) are globally unique 63-bit unsigned integers used to identify YANG items, as items. SIDs provide a more compact method to identify for identifying those YANG items that can be used for efficiency and efficiently, notably in constrained environments (RFC 7228).
This document defines the semantics, the registration, registration processes, and assignment processes of for YANG SIDs for IETF managed IETF-managed YANG modules.
To enable the implementation of these processes, this document also defines a file format used to persist and publish assigned YANG SIDs.</t>
      <t><cref anchor="status">The present version (–24) is intended to address the remaining IESG comments.</cref></t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-ietf-core-sid/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        Constrained RESTful Environments Working Group mailing list (<eref target="mailto:core@ietf.org"/>),
        which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/core/"/>.
        Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/core/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/core-wg/yang-cbor"/>.</t>
    </note>
  </front>
  <middle>
    <?line 136?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>Some of the items defined in YANG <xref target="RFC7950"/> require the use of a
unique identifier.
In both the Network Configuration Protocol (NETCONF) <xref target="RFC6241"/> and RESTCONF <xref target="RFC8040"/>, these identifiers are implemented using names.
To allow the implementation of data models defined in YANG in constrained devices <xref target="RFC7228"/> and constrained networks, a more compact method to identify YANG items is required.
This compact identifier, called the YANG Schema Item iDentifier or YANG SID (or simply SID in this document and when the context is clear), is encoded using a 63-bit unsigned integer.
The limitation to 63-bit unsigned integers allows SIDs to be manipulated more easily on platforms that might otherwise lack 64-bit unsigned arithmetic.
The loss of a single bit of range is not significant significant, given the size of the remaining space.</t>
      <t>The following items are identified using SIDs:</t>
      <ul spacing="normal">
        <li>
          <t>identities</t>
        </li>
        <li>
          <t>data nodes (Note: (note: including those nodes defined by the
'rc:yang-data' extension <xref target="RFC8040"/> and the 'sx:structure' extension <xref target="RFC8791"/> extensions.)</t> target="RFC8791"/>)</t>
        </li>
        <li>
          <t>remote procedure calls (RPCs) and associated input(s) and output(s)</t>
        </li>
        <li>
          <t>actions and associated input(s) and output(s)</t>
        </li>
        <li>
          <t>notifications and associated information</t>
        </li>
        <li>
          <t>YANG modules and features</t>
        </li>
      </ul>
      <t>It is possible that some protocols will use only a subset of the assigned SIDs, SIDs; for
example, for protocols equivalent to other than NETCONF <xref target="RFC6241"/> like that provide access to YANG-modeled data, such as <xref target="I-D.ietf-core-comi"/> target="CORE-COMI"/>, the
transportation
transport of YANG module SIDs might be unnecessary. Other protocols
might need to be able to transport this information, information -- for example example, protocols
related to discovery such as the Constrained YANG Module Library <xref target="I-D.ietf-core-yang-library"/>.</t> target="YANG-LIBRARY"/>.</t>
      <t>SIDs are globally unique integers.  A registration system is used in order to
guarantee their uniqueness. SIDs are registered in blocks called "SID ranges".
Once they are considered "stable", SIDs are assigned permanently.
Items introduced by a new revision of a YANG
module are added to the list of SIDs already assigned.
This is discussed in more detail in <xref target="objectives"/>.</t>
      <t>Assignment
      <t>The assignment of SIDs to YANG items is usually automated as
discussed in <xref target="sid-auto-generation"/>, which also discusses some cases
where manual interventions may be appropriate.</t>
      <t><xref target="sid-lifecycle"/> provides more details about the registration process of processes for YANG
modules and associated SIDs. To enable the implementation of this registry, these processes,
<xref target="sid-file-format"/> defines a standard file format used to store and publish
SIDs.</t>
      <t>IETF managed
      <t>IETF-managed YANG modules that need to allocate SIDs will use the IANA mechanism mechanisms specified in this document.
See <xref target="IANA"/> for details.
YANG modules created by other parties allocate SID ranges using the IANA allocation mechanisms via Mega-Ranges (see <xref target="mega-range-registry"/>); within the Mega-Range allocation, those other parties are free to make up their own mechanism.</t>
      <t>Among other uses, YANG SIDs are particularly useful to obtain for obtaining a
compact encoding for YANG-CBOR <xref target="RFC9254"/>.
At the time of writing, a tool for automated ".sid" file generation is
available as part of the open-source project PYANG <xref target="PYANG"/>.</t>
      <section anchor="terminology-and-notation">
        <name>Terminology and Notation</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"/> target="BCP14"/> (RFC 2119) (RFC 8174) when, and only
        when, they appear in all capitals, as shown here.</t>
        <?line -18?>

<t>The following terms are defined in <xref target="RFC7950"/>:</t>
        <ul spacing="normal">
          <li>
            <t>action</t>
          </li>
          <li>
            <t>feature</t>
          </li>
          <li>
            <t>module</t>
          </li>
          <li>
            <t>notification</t>
          </li>
          <li>
            <t>RPC</t>
          </li>
          <li>
            <t>schema node</t>
          </li>
          <li>
            <t>schema tree</t>
          </li>
          <li>
            <t>submodule</t>
          </li>
        </ul>
        <t>This specification also makes use of the following terminology:</t>
        <ul
        <dl spacing="normal">
          <li>
            <t>item:  A
          <dt>item:</dt><dd>A schema node, an identity, a module, or a feature defined using the YANG modeling language.</t>
          </li>
          <li>
            <t>YANG language.</dd>
          <dt>YANG Schema Item iDentifier (YANG SID or simply SID): Unsigned SID):</dt><dd>Unsigned
integer used to identify different YANG items (cf. <xref (cf.&nbsp;<xref section="3.2" sectionFormat="of" target="RFC9254"/>).</t>
          </li>
          <li>
            <t>YANG Name: Text target="RFC9254"/>).</dd>
          <dt>YANG name:</dt><dd>Text string used to identify different YANG items
(cf. <xref
(cf.&nbsp;<xref section="3.3" sectionFormat="of" target="RFC9254"/>).</t>
          </li>
        </ul> target="RFC9254"/>).</dd>
	</dl>
      </section>
    </section>
    <section anchor="objectives">
      <name>Objectives</name>
      <t>The overriding objective of the SID assignment and registration system is to
ensure global interoperability of protocols that employ SIDs in order
to communicate about data modeled in YANG.
This objective poses certain requirements on the stability of SIDs
while at the same time not hindering active evolution of the YANG
modules the SIDs are intended to support.</t>
      <t>Additional objectives include:</t>
      <ul spacing="normal">
        <li>
          <t>enabling the developer of a YANG module to also be the originating
entity for the SIDs pertaining to that module.</t>
        </li>
        <li>
          <t>making it easy for YANG developers to obtain SIDs.</t>
        </li>
        <li>
          <t>enabling other developers to define SIDs for a module where the
developer of the module is not interested in assigning the SIDs.</t>
        </li>
        <li>
          <t>keeping an assignment regime that keeps short (2..4 byte) SIDs (2..4 bytes)
readily available for the applications that would benefit from them
while at the same time employing the vast 63-bit SID space to
facilitate permissionless actions.</t>
        </li>
        <li>
          <t>enabling multiple entities to provide services that support the
assignment of SIDs.</t>
        </li>
        <li>
          <t>maintaining some locality in the assignment of SIDs so the
efficiencies of the SID delta mechanism can be fully employed.</t>
        </li>
        <li>
          <t>enabling various software components to deal operate in terms of SIDs
without having complete information about other parties in the
communication process.</t>
        </li>
      </ul>
      <t>While IANA ultimately maintains the registries that govern SIDs for
IETF-defined modules, various support tools (such as, at the time of
writing, the YANG Catalog <xref target="yangcatalog"/>)
need to provide the support to enable SID assignment and use for
modules still in IETF development.  Developers of open-source or
proprietary YANG modules also need to be able to serve as such
entities autonomously, possibly forming alliances independent of the
IETF, while still fitting in the overall SID number space managed by
IANA.  Obviously, this process has a number of parallels to the
management of IP addresses, addresses but also is also very different.</t>
      <section anchor="technical-objectives">
        <name>Technical Objectives</name>
        <t>As discussed in the introduction, <xref format="none" target="introduction">the Introduction</xref>, SIDs are intended as globally unique
(unsigned) integers.</t>
        <t>Specifically, this means that:</t>
        <dl>
          <dt><strong>Objective 1</strong> (<bcp14>MUST</bcp14>):</dt>
          <dd>
            <t>any
            <t>Any 63-bit unsigned integer is either (1)&nbsp;is unassigned as a SID or immutably (2)&nbsp;immutably maps to EXACTLY one YANG name.
Only the transition from unassigned to that immutable mapping is
defined.</t>
          </dd>
        </dl>
        <t>This enables a recipient of a data structure employing SIDs to
translate them into the globally meaningful YANG names that the
existing encodings of YANG data such as YANG-XML <xref target="RFC7950"/> and
YANG-JSON <xref target="RFC7951"/> employ today.</t>
        <t>The term YANG name "YANG name" is not defined outside this document, and YANG has
a complex system of names and entities that can have those names.
Instead of defining the term technically, this set of objectives uses
it in such a way that the overall objectives of YANG-SID YANG SID can be
achieved.</t>
        <t>A desirable objective is that:</t>
        <dl>
          <dt><strong>Objective 2</strong> (<bcp14>SHOULD</bcp14>):</dt>
          <dd>
            <t>any
            <t>Any YANG name in active use has one SID assigned.</t>
          </dd>
        </dl>
        <t>This means that:</t>
        <ol spacing="normal" type="1"><li>
            <t>There should not be YANG names without SIDs assigned</t> assigned.</t>
          </li>
          <li>
            <t>YANG names should not have multiple SIDs assigned</t> assigned.</t>
          </li>
        </ol>
        <t>These objectives are unattainable in full, because YANG names are not
necessarily born with a SID assignment, assignment and because entirely autonomous
entities might decide to assign SIDs for the same YANG name without
communicating ("like ships in the night").
Note that as long as this autonomy is maintained, any single observer
will have the impression that Objective 2 is attained.
Only when entities that have acted autonomously start communicating, communicating will a
deviation is be observed.</t>
      </section>
      <section anchor="module-evolution-versioning">
        <name>Module evolution, versioning</name> Evolution and Versioning</name>
        <t>YANG modules evolve (see <xref section="11" sectionFormat="of" target="RFC7950"/>, target="RFC7950"/> and
Section&nbsp;<xref target="RFC8407" sectionFormat="bare" section="4.27"/> of RFC 8407
<xref section="4.27" sectionFormat="of" target="RFC8407"/>). target="BCP216"/>).
The technical objectives listed above are states stated in terms that are
independent of this evolution.</t>
        <t>However, some modules are still in a very fluid state, and the
assignment of permanent SIDs to the YANG names created in them is less
desirable.  This is true not only true for new modules, modules but also for
emerging new revisions of existing stable modules.</t>
        <dl>
          <dt><strong>Objective 3</strong> (<bcp14>MUST</bcp14>):</dt>
          <dd>
            <t>the
            <t>The SID management system is independent of any module versioning.</t>
          </dd>
        </dl>
      </section>
      <section anchor="solution-components-and-derived-objectives">
        <name>Solution Components and Derived Objectives</name>
        <t>A registration system is used in order to guarantee the uniqueness of
SIDs.
To be able to provide some autonomy in allocation (and avoid
information disclosure where it is not desirable), SIDs are registered
in blocks called "SID ranges".</t>
        <t>SIDs are assigned permanently.</t>
        <t>Items introduced by a new revision of a YANG
module are added to the list of SIDs already assigned.</t>
      </section>
      <section anchor="parties-roles">
        <name>Parties and Roles</name>
        <t>In the YANG development process, we can discern a number of parties
that are concerned with a YANG module:</t>
        <dl newline="true">
          <dt>module controller:</dt>
          <dd>
            <t>The owner of the YANG module, i.e., the controller
about its
of the module's evolution.</t>
          </dd>
          <dt>registration entity:</dt>
          <dd>
            <t>The controller of the module namespace, specifically also of the
prefixes that are in common use.  (This is not a required party.)</t>
          </dd>
          <dt>module repository:</dt>
          <dd>
            <t>An entity that supplies modules to module users.  This can be an
"official" entity (e.g., IANA for IETF modules) or unofficial an "unofficial" entity (e.g., the
YANG Catalog <xref target="yangcatalog"/>).  Not all repositories are in a position to act as
a registry, i.e., as a permanent record for the information they
supply; these repositories need to recur to module owners as a
stable source.</t>
          </dd>
          <dt>module user:</dt>
          <dd>
            <t>An entity that uses a module, after obtaining it from the module
controller or a module repository.</t>
          </dd>
        </dl>
        <t>This set of parties needs to evolve to take on the additional roles
that the SID assignment process requires:</t>
        <dl newline="true">
          <dt>SID assigner:</dt>
          <dd>
            <t>An entity that assigns SIDs for a module.  Objective 2 aims at
having only one SID assigner for each module.  SID assigners
preferably stay the same over a module development process; however however,
this specification provides SID ".sid" files to ensure an organized handover.</t>
          </dd>
          <dt>SID range registries:</dt> registry:</dt>
          <dd>
            <t>The entities
            <t>An entity that supply supplies a SID assigner with SID ranges that they it can
use in assigning SIDs for a module.  (In this specification, there
is a structure with mega-ranges Mega-Ranges and individual SID ranges; this is
not relevant here.)</t>
          </dd>
          <dt>SID repository:</dt>
          <dd>
            <t>An entity that supplies SID assignments to SID users, usually in the
form of a SID ".sid" file.</t>
          </dd>
          <dt>SID users:</dt> user:</dt>
          <dd>
            <t>The module user that uses the SIDs provided by a SID assigner for a YANG
module.  SID users need to find SID assigners (or at least their SID
assignments).</t>
          </dd>
        </dl>
        <t>During
        <t>As the introduction use of SIDs, SIDs with YANG data models is introduced, the distribution of the SID roles to
the existing parties for a YANG module will evolve.</t>
        <t>The desirable end state of this evolution is shown in <xref target="roles-parties"/>.</t>
        <table anchor="roles-parties">
          <name>Roles and Parties: Desired End State</name>
          <thead>
            <tr>
              <th align="left">Role</th>
              <th align="left">Party</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">SID assigner</td>
              <td align="left">module developer</td>
            </tr>
            <tr>
              <td align="left">SID range registry</td>
              <td align="left">(as discussed in this specification)</td>
            </tr>
            <tr>
              <td align="left">SID repository</td>
              <td align="left">module repository</td>
            </tr>
            <tr>
              <td align="left">SID user</td>
              <td align="left">module user (naturally)</td>
            </tr>
          </tbody>
        </table>
        <t>This grouping of roles and parties puts the module developer into in a
position where it can achieve the objectives laid out in this section
(a "type-1", "SID-guiding" module controller).
(While a third party might theoretically assign additional SIDs and
conflict with objective Objective 2, there is very little reason to do so if SID ".sid"
files are always provided by the module developer with the module.)</t>
        <t>The rest of this section is concerned with the transition to this end
state.</t>
        <t>For existing modules, there is no SID ".sid" file.  The entity that stands in
as the SID assigner is not specified.  This situation has the highest
potential of a for conflict with objective Objective 2.</t>
        <t>Similarly, for new module development, the module owner may not have
heard about SIDs or may not be interested in assigning them (e.g., because
of lack of software or procedures within their organization).</t>
        <t>For these two cases (which we will collectively call type-3, "type-3", "SID-oblivious" module
controller), module repositories can act as a mediator, giving SID
users access to a SID assigner that is carefully chosen to be a likely
choice by other module repositories as well, maximizing the likelihood
of achieving objective Objective 2.</t>
        <t>If the a module controller has heard about SIDs, SIDs but is not assigning
them yet, it can designate a SID assigner instead.  This can lead to a
stable, unique set of SID assignments being provided indirectly by a
(type-2,
("type-2", "SID-aware") module developer.  Entities offering designated
SID assigner services could make these available in an easy-to-use
way, e.g., via a Web web interface.</t>
        <t>The entity acting as a SID assigner minimally needs to record the SID
range it uses for the SID assignment.  If the SID range registry employed can
record the module name and revision, revision and if the assignment processes
(including the software used) are stable, the SID assigner can
theoretically reconstruct its assignments, but this is an invitation
for could invite
implementation bugs.</t>
        <t>SID assigners attending to a module in development (not yet stable)
need to decide whether SIDs for a new revision are re-assigned reassigned from
scratch ("clean-slate") ("clean slate") or use existing assignments from a previous
revision as a base, only assigning new SIDs for new names.
Once a module is declared stable, its SID assignments <bcp14>SHOULD</bcp14> be
declared stable as well (the exception being (except that, for existing YANG
modules, some review may be needed before this is done).</t>
        <t>This specification does not further discuss how mediating entities
such as designated SID assigners or SID repositories could operate;
instead, it supplies objectives for their operation.</t>
      </section>
    </section>
    <section anchor="sid-lifecycle">
      <name>".sid" file lifecycle</name> File Lifecycle</name>
      <t>YANG is a language designed to model data accessed using one of the compatible
protocols (e.g. (e.g., NETCONF <xref target="RFC6241"/>, RESTCONF <xref target="RFC8040"/> target="RFC8040"/>, and CORECONF the CoAP Management Interface (CORECONF) <xref target="I-D.ietf-core-comi"/>). target="CORE-COMI"/>). A
YANG module defines hierarchies of data, including configuration, state data,
RPCs, actions actions, and notifications.</t>
      <t>Many YANG modules are not created in the context of constrained
applications. YANG modules can be implemented using NETCONF <xref target="RFC6241"/> or
RESTCONF <xref target="RFC8040"/> without the need to assign SIDs.</t>
      <t>As needed, authors of YANG modules can assign SIDs to their YANG modules. In
order to do that, they should first obtain a SID range from a registry and use
that range to assign or generate SIDs to items of in their YANG module. The
assignments can then be stored in a ".sid" file. For an
example on of how this could be achieved, please refer to <xref target="sid-lifecycle-ex"/>.</t>
      <t>Items introduced by a new revision of a YANG module are added to the list of SIDs already assigned.
When this is done during the development of a new protocol document, it may be necessary to make provisional assignments.
They may get changed, revised revised, or withdrawn during the development of a new standard.
These provisional assignments are marked with a status of "unstable",
so that they can be removed and the SID number possibly be reassigned
for a different YANG schema name/path later during development. in the development process.
When the specification is advanced to a final document, then
the assignment is marked with a status of "stable".
During a period of development starting from a published
specification, two variants of the SID ".sid" file should
be made available by the tooling involved in that development: (1) a
"published" SID ".sid" file with the existing stable SID assignments only
(which the development effort should keep stable), as
well as (2) an "unpublished" SID ".sid" file that also contains the unstable
SID assignments.</t>
      <t>Registration of the ".sid" file associated to with a YANG module is optional but
recommended, <!-- sic. --> in order to
recommended; doing so will promote interoperability between devices and to avoid duplicate
allocation of SIDs to a single YANG module. Different registries might have
different requirements for the registration and publication of the ".sid"
files. For a diagram of one of the possibilities, possible scenario, please refer to the activity
diagram on shown in <xref target="fig-sid-file-creation"/> in <xref target="sid-lifecycle-ex"/>.</t>
      <t>Each time a YANG module or module, one or more of its imported module(s) modules, or one or more of its included
submodule(s) is
submodules are updated, a new ".sid" file <bcp14>MAY</bcp14> be created if the new or
updated items will need SIDs. All the SIDs present in the a previous version of
the ".sid" file that was in active use <bcp14>MUST</bcp14> be present in the new version as well. The creation of
this new version of the ".sid" file <bcp14>SHOULD</bcp14> be performed using an automated
tool.</t>
      <t>If a new revision requires more SIDs than initially allocated, a new SID range
<bcp14>MUST</bcp14> be added to the 'assignment-range' item as defined in <xref target="sid-file-format"/>.
These extra SIDs are used for subsequent assignments.</t>
      <t>For an example of this update process, see the activity diagram shown in
<xref target="fig-sid-file-update"/> in <xref target="sid-lifecycle-ex"/>.</t>
    </section>
    <section anchor="sid-file-format">
      <name>".sid" file format</name> File Format</name>
      <t>".sid" files are used to persist and publish SIDs assigned to the different
YANG items of in a specific YANG module.</t>
      <t>It has the
      <t>The following structure:</t> tree diagram <xref target="BCP215"/> provides an overview of the data
 model:</t>
      <figure>
        <name>YANG tree Tree for ietf-sid-file</name> &apos;ietf-sid-file&apos;</name>
        <sourcecode type="yangtree"><![CDATA[
module: ietf-sid-file

  structure sid-file:
    +-- module-name            yang:yang-identifier
    +-- module-revision?       revision-identifier
    +-- sid-file-version?      sid-file-version-identifier
    +-- sid-file-status?       enumeration
    +-- description?           string
    +-- dependency-revision*   [module-name]
    |  +-- module-name         yang:yang-identifier
    |  +-- module-revision     revision-identifier
    +-- assignment-range*      [entry-point]
    |  +-- entry-point         sid
    |  +-- size                uint64
    +-- item*                  [namespace identifier]
       +-- status?             enumeration
       +-- namespace           enumeration
       +-- identifier          union
       +-- sid                 sid
]]></sourcecode>
      </figure>
      <t>The following YANG module defines the structure of this file, encoding ".sid" files. Encoding is
performed in JSON <xref target="RFC8259"/> target="STD90"/> using the rules defined in <xref target="RFC7951"/>.
It references ietf-yang-types defined in
This module imports 'ietf-yang-types' <xref target="RFC6991"/> and ietf-yang-structure-ext defined in 'ietf-yang-structure-ext' <xref target="RFC8791"/>.</t>
      <t>RFC Ed.: please update the date of the module and Copyright if needed target="RFC8791"/>.  It also references <xref target="STD68"/>, <xref target="RFC7950"/>, and remove this note.</t> <xref target="BCP216"/>.</t>
      <figure>
        <name>YANG module ietf-sid-file</name> Module &apos;ietf-sid-file&apos;</name>
        <sourcecode name="ietf-sid-file@2024-06-17.yang" type="yang" markers="true" name="ietf-sid-file@2023-10-27.yang"><![CDATA[ markers="true"><![CDATA[
module ietf-sid-file {
  yang-version 1.1;
  namespace "urn:ietf:params:xml:ns:yang:ietf-sid-file";
  prefix sid;

  import ietf-yang-types {
    prefix yang;
    reference
      "RFC 6991: Common YANG Data Types."; Types";
  }
  import ietf-yang-structure-ext {
    prefix sx;
    reference
      "RFC 8791: YANG Data Structure Extensions."; Extensions";
  }

  organization
    "IETF Core CORE Working Group";

  contact
    "WG Web:   <https://datatracker.ietf.org/wg/core/>

     WG List:  <mailto:core@ietf.org>

     Editor:   Michel Veillette
               <mailto:michel.veillette@trilliant.com>

     Editor:   Andy Bierman
               <mailto:andy@yumaworks.com>

     Editor:   Alexander Pelov
               <mailto:a@ackl.io>
               <mailto:alexander.pelov@imt-atlantique.fr>

     Editor:   Ivaylo Petrov
               <mailto:ivaylopetrov@google.com>";

  description
    "Copyright
    "This module defines the structure of the '.sid' files.

     Each '.sid' file contains the mapping between each
     string identifier defined by a YANG module and a
     corresponding numeric value called a YANG SID.

     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.

     Copyright (c) 2023 2024 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); 9595; 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.

     This module defines the structure of the .sid files.

     Each .sid file contains the mapping between each
     string identifier defined by a YANG module and a
     corresponding numeric value called YANG SID."; notices.";

  revision 2023-10-27 2024-06-17 {
    description
      "Initial revision.";
    reference
      "[RFC XXXX]
      "RFC 9595: YANG Schema Item iDentifier (YANG SID)";
  }

  typedef revision-identifier {
    type string {
      pattern '[0-9]{4}-[0-9]{2}-[0-9]{2}';
    }
    description
      "Represents a date in YYYY-MM-DD format.";
  }

  typedef sid-file-version-identifier {
    type uint32;
    description
      "Represents the version of a .sid '.sid' file.";
  }

  typedef sid {
    type uint64 {
      range "0..9223372036854775807";
    }
    description
      "YANG Schema Item iDentifier"; iDentifier.";
    reference
      "[RFC XXXX]
      "RFC 9595: YANG Schema Item iDentifier (YANG SID)";
  }

  typedef schema-node-path {
    type string {
      pattern
        '/[a-zA-Z_][a-zA-Z0-9\-_.]*:[a-zA-Z_][a-zA-Z0-9\-_.]*' +
        '(/[a-zA-Z_][a-zA-Z0-9\-_.]*(:[a-zA-Z_][a-zA-Z0-9\-_.]*)?)*';
    }
    description
      "A schema-node path is an absolute YANG schema node schema-node
       identifier as defined by the YANG ABNF rule absolute-schema-nodeid,
       'absolute-schema-nodeid', except that module names are used
       instead of prefixes.

       This string additionally follows the following rules:

       o

       -  The leftmost (top-level) data node name is always in the
          namespace-qualified form.
       o
       -  Any subsequent schema node schema-node name is in the
          namespace-qualified form if the node is defined in a
          module other than its parent node, and node.  Otherwise, the
          simple form is used
          otherwise. used.  No predicates are allowed.";
    reference
      "RFC 7950, 5234 (STD 68): Augmented BNF for Syntax Specifications:
                          ABNF
       RFC 7950: The YANG 1.1 Data Modeling Language; Language,
                 Section 6.5: Schema Node Identifier;"; Identifier";
  }

  sx:structure sid-file {
    uses sid-file-contents;
  }

  grouping sid-file {
    description
      "A grouping that contains a YANG container
       representing the file structure of a .sid files."; '.sid' file.";

    container sid-file {
      description
        "A wrapper container that together with the sx:structure 'sx:structure'
         extension marks the YANG data structures inside as not
         being intended to be implemented as part of a
         configuration datastore or as an operational state within
         the server.";
      uses sid-file-contents;
    }
  }

  grouping sid-file-contents {
    description
      "A grouping that defines the contents of a container that
       represents the file structure of a .sid files."; '.sid' file.";

    leaf module-name {
      type yang:yang-identifier;
      mandatory true;
      description
        "Name of the YANG module associated with this .sid
         '.sid' file.";
    }

    leaf module-revision {
      type revision-identifier;
      description
        "Revision of the YANG module associated with this .sid '.sid'
         file.
         This leaf is not present if no revision statement is
         defined in the YANG module.";
    }

    leaf sid-file-version {
      type sid-file-version-identifier;
      default 0;
      description
        "Optional leaf that specifies the version number of the
        .sid
         '.sid' file.  .sid  '.sid' files and the version sequence are
         specific to a given YANG module revision.  This number
         starts at zero when there is a new YANG module revision
         and increases monotonically.  This number can distinguish
         updates to the .sid '.sid' file which are - for instance, as the result
         of new
        processing, processing or the result of reported errata.";
    }

    leaf sid-file-status {
      type enumeration {
        enum unpublished {
          description
            "This .sid '.sid' file is unpublished [RFC8407], (BCP 216) and is
             also called a work-in-progress or workfile.
             This may be when it accompanies an unpublished YANG
              module,
             module or when only the .sid '.sid' file itself is
             unpublished.
             The 'item' list MAY contain entries with a status
             value of 'unstable'.";
          reference
            "RFC 8407 (BCP 216): Guidelines for Authors and
                                 Reviewers of Documents Containing
                                 YANG Data Models";
        }
        enum published {
          description
            "This .sid '.sid' file is published, published.  This status
             applies to '.sid' files for a published YANG
              module. modules.
             The 'item' list MUST NOT contain entries with a
             status value of 'unstable'.";
        }
      }
      default published; "published";
      description
        "Optional leaf that specifies the status of the
        .sid
         '.sid' file.";
    }

    leaf description {
      type string;
      description
        "Free-form meta information meta-information about the generated file.  It
         might include .sid a '.sid' file generation tool and time time,
         among other things.";
    }

    list dependency-revision {
      key "module-name";

      description
        "Information about the revision used during the .sid
         '.sid' file generation of each dependency, i.e., each
         YANG module that the YANG module in
        'module-name' associated with this
         '.sid' file imported.";

      leaf module-name {
        type yang:yang-identifier;
        description
          "Name of the YANG module, dependency
          "YANG module name of 'module-name',
          for which revision information is provided."; this dependency.";
      }
      leaf module-revision {
        type revision-identifier;
        mandatory true;
        description
          "Revision of the YANG module, dependency module of
          'module-name', for which revision information is
          provided."; this dependency.";
      }
    }

    list assignment-range {
      key "entry-point";
      description
        "YANG SID range(s)
        "YANG-SID Range(s) allocated to the YANG module
         identified by 'module-name' and 'module-revision'.

         -  The YANG SID range first available value in the YANG-SID Range is entry-point
            'entry-point', and the last available value in the
            range is
          (entry-point ('entry-point' + size - 1).
         -  The YANG SID ranges YANG-SID Ranges specified by all assignment-ranges
            'assignment-range' entries MUST NOT overlap.";

      leaf entry-point {
        type sid;
        description
          "Lowest YANG SID available for assignment.";
      }

      leaf size {
        type uint64;
        mandatory true;
        description
          "Number of YANG SIDs available for assignment.";
      }
    }

    list item {
      key "namespace identifier";
      unique "sid";

      description
        "Each entry within this list defines the mapping between
         a YANG item string identifier and a YANG SID.  This list
         MUST include a mapping entry for each YANG item defined
         by the YANG module identified by 'module-name' and
         'module-revision'.";

      leaf status {
        type enumeration {
          enum stable {
            value 0;
            description
              "This SID allocation has been published as the
               stable allocation for the given namespace and
               identifier.";
          }
          enum unstable {
            value 1;
            description
              "This SID allocation has been done during a
               development process; it is not yet stable.";
          }
          enum obsolete {
            value 2;
            description
              "This SID allocation is no longer in use.  It is
               recorded to avoid reallocation of its SID value.";
          }
        }
        default stable; "stable";
        description
          "The status field contains information about the
           stability of the allocation.  For each specific SID
           value, over time it can only transition from unstable
           'unstable' to stable, 'stable', and possibly from stable 'stable' to obsolete.";
           'obsolete'.";
      }

      leaf namespace {
        type enumeration {
          enum module {
            value 0;
            description
              "All module and submodule names share the same
               global module identifier namespace.";
          }
          enum identity {
            value 1;
            description
              "All identity names defined in a module and its
               submodules share the same identity identifier
               namespace.";
          }
          enum feature {
            value 2;
            description
              "All feature names defined in a module and its
               submodules share the same feature identifier
               namespace.";
          }
          enum data {
            value 3;
            description
              "The namespace for all data nodes, as defined in
               YANG.";
          }
        }
        description
          "Namespace of the YANG item for this mapping entry.";
      }

      leaf identifier {
        type union {
          type yang:yang-identifier;
          type schema-node-path;
        }
        description
          "String identifier of the YANG item for this mapping
           entry.

           If the corresponding 'namespace' field is 'module',
           'feature', or 'identity', then this field MUST
           contain a valid YANG identifier string.

           If the corresponding 'namespace' field is 'data',
           then this field MUST contain a valid schema-node
           path.";
      }

      leaf sid {
        type sid;
        mandatory true;
        description
          "YANG SID assigned to the YANG item for this mapping
           entry.";
      }
    }
  }
}
]]></sourcecode>
      </figure>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>This document defines a new type of identifier used to encode data that are modeled in YANG <xref target="RFC7950"/>.
This new identifier maps semantic concepts to integers, and if the
source of this mapping is not trusted, then new security risks might
occur if an attacker can control the mapping.</t>
      <t>At the time of writing, it is expected that the SID ".sid" files will be
processed by a software developer, within a software development
environment.  Developers are advised to only import SID ".sid" files from
authoritative sources.  IANA is the authoritative source for IETF
managed IETF-managed
YANG modules.</t>
      <t>Conceptually, SID ".sid" files could be processed by less-constrained target
systems such as network management systems.  Such systems need to take
extra care to make sure that they are only processing SID ".sid" files from
authoritative sources, sources that are as authoritative as the YANG modules that they
are using.</t>
      <t>SID
      <t>".sid" files are identified with and can employ <em>dereferenceable
identifiers</em>, i.e., identifiers that could lead implementations in
certain situations to automatically perform a remote access access, the target
of which is indicated at least partially by those identifiers.
This can give an attacker information from and/or control over such
accesses, which can have security and privacy implications.
Please also see Sections <xref target="I-D.bormann-t2trg-deref-id" section="5" target="DEREF-ID" section="6" sectionFormat="bare"/> and <xref target="I-D.bormann-t2trg-deref-id" section="6" target="DEREF-ID" section="7" sectionFormat="bare"/> of <xref target="I-D.bormann-t2trg-deref-id"/> target="DEREF-ID"/>
for further considerations that may be applicable.</t>
    </section>
    <section anchor="IANA">
      <name>IANA Considerations</name>
      <section anchor="yang-namespace-registration">
        <name>YANG Namespace Registration</name>
        <t>This document registers the following XML namespace URN in the "IETF XML
Registry", following the format defined in <xref target="RFC3688"/>:</t>
        <t>URI: please assign urn:ietf:params:xml:ns:yang:ietf-sid-file</t>
        <t>Registrant Contact: The IESG.</t>
        <t>XML: N/A, target="BCP81"/>:</t>
     <dl spacing="compact">
        <dt>URI:</dt><dd>urn:ietf:params:xml:ns:yang:ietf-sid-file</dd>
        <dt>Registrant Contact:</dt><dd>The IESG.</dd>
        <dt>XML:</dt><dd>N/A; the requested URI is an XML namespace.</t>
        <t>Reference:    RFC XXXX</t>
        <t>// RFC Ed.: please replace XXXX with RFC number and remove this note</t> namespace.</dd>
        <dt>Reference:</dt><dd>RFC 9595</dd>
     </dl>
      </section>
      <section anchor="iana-module-registration">
        <name>Register ".sid"
        <name>".sid" File Format Module</name> Module Registration</name>
        <t>This document registers one YANG module in the "YANG Module Names" registry <xref target="RFC6020"/>:</t>
        <ul spacing="normal">
          <li>
            <t>name:         ietf-sid-file</t>
          </li>
          <li>
            <t>namespace:    urn:ietf:params:xml:ns:yang:ietf-sid-file</t>
          </li>
          <li>
            <t>prefix:       sid</t>
          </li>
          <li>
            <t>reference:    RFC XXXX</t>
          </li>
        </ul>
        <t>// RFC Ed.: please replace XXXX with RFC number and remove this note</t>
        <dl spacing="compact">
          <dt>Name:</dt><dd>ietf-sid-file</dd>
          <dt>Namespace:</dt><dd>urn:ietf:params:xml:ns:yang:ietf-sid-file</dd>
          <dt>Prefix:</dt><dd>sid</dd>
          <dt>Reference:</dt><dd>RFC 9595</dd>
	</dl>
      </section>

      <section anchor="mega-range-registry">
        <name>Create new
        <name>New IANA Registry: "YANG SID Mega-Range" registry</name> YANG-SID Mega-Ranges</name>
        <t>The name of this registry is "YANG SID Mega-Range". "YANG-SID Mega-Ranges". This registry is used to record the delegation of the management of a block of SIDs to a third parties party (such as SDOs Standards Development Organizations (SDOs) or registrars).</t>
        <section anchor="structure">
          <name>Structure</name>
          <t>Each entry in this registry must include:</t>
          <ul spacing="normal">
            <li>
              <t>The entry point (first SID) of the registered SID block.</t>
            </li>
            <li>
              <t>The size of the registered SID block.
The size <bcp14>SHOULD</bcp14> be one million (1 000 000) (1,000,000) SIDs,
but in exceptional cases,
it <bcp14>MAY</bcp14> exceptionally be a multiple of 1 000 000.</t> 1,000,000.</t>
            </li>
            <li>
              <t>The policy of SID range allocations: Public, Private Private, or Both.</t> both.</t>
            </li>
            <li>
              <t>The contact information of the requesting organization including: organization, including the following:
              </t>
              <ul spacing="normal">
                <li>
                  <t>Organization name</t> name.</t>
                </li>
                <li>
                  <t>URL</t>
                  <t>URL.</t>
                </li>
              </ul>
            </li>
          </ul>
        </section>
        <section anchor="allocation-policy">
          <name>Allocation policy</name> Policy</name>
          <t>The IANA policy for future additions to this registry is "Expert Review" (Section&nbsp;<xref target="RFC8126" sectionFormat="bare" section="4.5"/> of RFC 8126 <xref target="RFC8126"/>.</t> target="BCP26"/>).</t>
          <t>An organization requesting to manage a YANG SID YANG-SID Range (and thus have an entry in the YANG SID Mega-Range Registry), "YANG-SID Mega-Ranges" registry) must ensure the following capacities:</t>
          <ul spacing="normal">
            <li>
              <t>The capacity to manage and operate a YANG SID Range Registry. registry of YANG-SID Ranges. A YANG SID Range Registry registry of YANG-SID Ranges <bcp14>MUST</bcp14> provide the following information for all YANG SID YANG-SID Ranges allocated by the Registry:
              </t> registry:</t>
              <ul spacing="normal">
                <li>
                  <t>Entry Point
                  <t>The entry point of the allocated YANG SID Range</t> YANG-SID Range.</t>
                </li>
                <li>
                  <t>Size
                  <t>The size of the allocated YANG SID Range</t> YANG-SID Range.</t>
                </li>
                <li>
                  <t>Type: Public or Private Private.
                  </t>
                  <ul spacing="normal">
                    <li>
                      <t>Public Ranges ranges <bcp14>MUST</bcp14> include at least a reference to the YANG module and ".sid" files for that YANG SID YANG-SID Range (e.g., compare see <xref target="publink"/> as an example for how this is handled for the IETF YANG SID "IETF YANG-SID Ranges" registry).</t>
                    </li>
                    <li>
                      <t>Private Ranges ranges <bcp14>MUST</bcp14> be marked as "Private"</t> "Private".</t>
                    </li>
                  </ul>
                </li>
              </ul>
            </li>
            <li>
              <t>A Policy policy of allocation, which clearly identifies if whether the YANG SID YANG-SID Range allocations would be Private, Public Public, or Both.</t> both.</t>
            </li>
            <li>
              <t>Technical capacity to provide or refer to ".sid" files in a way that
meets the security objective of data integrity for these files (see
also <xref target="security-considerations"/>).</t>
            </li>
            <li>
              <t>Technical capacity to ensure the sustained operation of the registry for a period of at least 5 years. If registrations in the Private Registrations category are allowed, the period must be of at least 10 years.</t>
            </li>
          </ul>
          <t>If a size of the allocation beyond 1 000 000 1,000,000 is desired, the
organization must demonstrate the sustainability of the technical
approach for utilizing this size of allocation and how it does not
negatively impact the overall usability of the SID allocation
mechanisms; such allocations are preferably placed in the space above
4 295 000 000
4,295,000,000 (64-bit space).</t>
          <section anchor="first-allocation">
            <name>First allocation</name> Allocation</name>
            <t>For a first allocation to be provided, the requesting organization must demonstrate a functional registry infrastructure.</t>
          </section>

          <section anchor="consecutive-allocations">
            <name>Consecutive allocations</name> Allocations</name>
            <t>On one or more subsequent allocation request(s), requests, the organization must demonstrate the
exhaustion of the prior range. These conditions need to be asserted by the
assigned expert(s).</t>
            <t>If that extra-allocation such a request for an additional allocation is done made within 3 years from of the last allocation, the
experts need to discuss this request on the CORE working group Working Group mailing list and
consensus needs to be obtained before allocating a new Mega-Range.</t>
          </section>
        </section>
        <section anchor="initial-contents-of-the-registry">
          <name>Initial contents Contents of the Registry</name>
          <t>The initial entry in this

          <t>This registry is allocated to IANA:</t> contains the following initial entry:</t>
          <table align="left">
           <name>YANG-SID Mega-Ranges Registry: Initial Assignment</name>
            <thead>
              <tr>
                <th align="left">Entry Point</th>
                <th align="left">Size</th>
                <th align="left">Allocation</th>
                <th align="left">Organization name</th> Name</th>
                <th align="left">URL</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">0</td>
                <td align="left">1000000</td> align="left">1,000,000</td>
                <td align="left">Public</td>
                <td align="left">IANA</td>
                <td align="left">https://iana.org</td> align="left"><eref brackets="angle" target="https://www.iana.org/"/></td>
              </tr>
            </tbody>
          </table>
        </section>
      </section>
      <section anchor="ietf-iana-sid-range-allocation">
        <name>Create a new
        <name>New IANA Registry: IETF YANG YANG-SID Ranges</name>
        <t>The name of this registry is "IETF YANG-SID Ranges". This
        registry is used to record information related to the assignment of SID Range Registry (managed
        Ranges (e.g., entry point and size) to YANG modules identified by IANA)</name> module
        name.</t>
        <section anchor="ietf-iana-sid-range-structure">
          <name>Structure</name>
          <t>Each entry in this registry must include:</t>
          <ul spacing="normal">
            <li>
              <t>The SID range entry point.</t>
            </li>
            <li>
              <t>The SID range size.</t>
            </li>
            <li>
              <t>The YANG module name.</t>
            </li>
            <li>
              <t>Document reference.</t>
              <t>A document reference (the document making the registration).</t>
            </li>
          </ul>
        </section>
        <section anchor="ietf-iana-sid-range-allocation-policy">
          <name>Allocation policy</name> Policy</name>
          <t>The first million SIDs assigned to IANA is are subdivided as follows:</t>
          <ul spacing="normal">
          <ol spacing="normal" type="1">
            <li>
              <t>The range of 0 to 999 (size 1000) 1,000) is subject to "IESG Approval" as defined in Section&nbsp;<xref target="RFC8126" sectionFormat="bare" section="4.10"/> of RFC 8126 <xref target="RFC8126"/>; target="BCP26"/>; of these, SID value 0 has been reserved for implementations to internally signify the absence of a SID number and does not occur in interchange.</t>
            </li>
            <li>
              <t>The ranges of 1000 1,000 to 59,999 (size 59,000) and 100,000 to 299,999 (size 200,000) are designated for YANG modules defined in RFCs.
              </t>
              <ul spacing="normal">
              <ol spacing="normal" type="a">
                <li>
                  <t>The IANA policy for additions to this registry is either: is:
                  </t>
                  <ul spacing="normal">
                  <ol spacing="normal" type="i">
                    <li>
                      <t>"Expert Review" (Section&nbsp;<xref target="RFC8126" sectionFormat="bare" section="4.5"/> of RFC 8126 <xref target="RFC8126"/> in case target="BCP26"/>) if the ".sid" file comes from a YANG module from an existing RFC, or</t> RFC.</t>
                    </li>
                    <li>
                      <t>"RFC Required" (Section&nbsp;<xref target="RFC8126" sectionFormat="bare" section="4.7"/> of RFC 8126 <xref target="RFC8126"/> target="BCP26"/>) otherwise.</t>
                    </li>
                  </ul>
		  </ol>
                </li>
                <li>
                  <t>The Expert expert <bcp14>MUST</bcp14> verify that the YANG module for which this allocation is made has an RFC (existing RFC) OR is on track to become an RFC (early allocation (Early Allocation with a request from the WG working group chairs as defined by <xref target="BCP100"/>).</t>
                </li>
              </ul>
              </ol>
            </li>
            <li>
              <t>The range of 60,000 to 99,999 (size 40,000) is reserved for experimental YANG modules. This range <bcp14>MUST NOT</bcp14> be used in operational deployments deployments, since these SIDs are not globally unique which limit and their interoperability. interoperability is therefore limited. The IANA policy for this range is "Experimental use" Use" (Section&nbsp;<xref target="RFC8126" sectionFormat="bare" section="4.2"/> of RFC 8126 <xref target="RFC8126"/>.</t> target="BCP26"/>).</t>
            </li>
            <li>
              <t>The range of 300,000 to 999,999 (size 900,000) 700,000) is "Reserved" as defined in Section&nbsp;<xref target="RFC8126" sectionFormat="bare" section="6"/> of RFC 8126 <xref target="RFC8126"/>.</t> target="BCP26"/>.</t>
            </li>
          </ul>
          </ol>

          <table align="left">
           <name>IETF YANG-SID Ranges Registry: Policies for IETF Ranges</name>
            <thead>
              <tr>
                <th align="left">Entry Point</th>
                <th align="left">Size</th>
                <th align="left">IANA policy</th> Policy</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">0</td>
                <td align="left">1,000</td>
                <td align="left">IESG Approval</td>
              </tr>
              <tr>
                <td align="left">1,000</td>
                <td align="left">59,000</td>
                <td align="left">RFC Required</td> and Expert Review Required (see item 2 above)</td>
              </tr>
              <tr>
                <td align="left">60,000</td>
                <td align="left">40,000</td>
                <td align="left">Experimental/Private use</td> align="left">Reserved for Experimental Use</td>
              </tr>
              <tr>
                <td align="left">100,000</td>
                <td align="left">200,000</td>
                <td align="left">RFC Required</td> and Expert Review Required (see item 2 above)</td>
              </tr>
              <tr>
                <td align="left">300,000</td>
                <td align="left">700,000</td>
                <td align="left">Reserved</td>
              </tr>
            </tbody>
          </table>
          <t>The size of the SID range allocated for a YANG module is recommended to be a multiple of 50 and to be at least 33% above the current number of YANG items. This headroom allows assignment assignments within the same range of new YANG items introduced by subsequent revisions. The SID range size <bcp14>SHOULD NOT</bcp14> exceed 1000; 1,000; a larger size may be requested by the authors if this recommendation is considered insufficient. It is important to note that an additional SID range can be allocated to an existing YANG module if the initial range is exhausted; this then just leads to a slightly less efficient representation.</t>
          <t>In case
          <t>If a SID range is allocated for an existing RFC through the "Expert
Review" policy, policy (Section&nbsp;<xref target="RFC8126" sectionFormat="bare" section="4.5"/> of RFC 8126 <xref target="BCP26"/>), the Document reference Reference field for the given allocation should
point to the RFC that the YANG module is defined in.</t>
          <t>In case
          <t>If a SID range is required before publishing the RFC due to
implementations needing stable SID values, early allocation Early Allocation as defined in
<xref target="BCP100"/> can be employed for the "RFC Required" range (<xref section="2" sectionFormat="of" (Section&nbsp;<xref target="RFC7120" sectionFormat="bare" section="2"/> of RFC 7120 <xref target="BCP100"/>).</t>
        </section>
        <section anchor="publink">
          <name>Publication of the ".sid" file</name> File</name>
          <t>During publication of an RFC, RFC's publication process, IANA contacts the designated expert team
("the team"), who are responsible for delivering a final SID ".sid" file for
each module defined by the RFC.
For a type-3 developer (SID-oblivious, (SID-oblivious; see <xref target="parties-roles"/>), the team
creates a new SID ".sid" file from each YANG module, module; see below.
For a type-2 (SID-aware) developer, the team first obtains the existing draft SID ".sid"
file from a stable reference in the approved draft; for a type-1 (SID-guiding)
developer, the team extracts the SID ".sid" file from the approved draft.</t>
          <t>The team uses a tool to generate a final SID ".sid" file from each YANG
module; the final SID ".sid" file has all SID assignments set to "stable" and
the SID ".sid" file status set to "published".
A published ".sid" file <bcp14>MUST NOT</bcp14> contain SID assignments with an
unstable status.</t> a
status of "unstable".</t>
          <t>For the cases other than type-3 (SID-oblivious), the team feeds the existing draft SID ".sid"
file as an input ("reference SID ".sid" file") to the tool so that the changes resulting from
re-generation
regeneration are minimal.
For YANG modules that are revisions of previously published modules,
any existing published SID ".sid" file needs to serve as a reference SID ".sid" file
for the tool, either during generation of either the revised draft ".sid" file (type-1,
type-2) or during generation of the final SID ".sid" file (type-3).</t>
          <t>In any case, the team checks the generated file, including checking for
validity as a SID ".sid" file, for consistency with the SID range
allocations, for full coverage of the YANG items in the YANG module, and
for the best achievable consistency with the existing draft SID ".sid" file.</t>
          <t>The designated experts then give the SID ".sid" file to IANA to publish into in
the YANG SID Registry "IETF YANG-SID Modules" registry (<xref target="ietf-sid-registry"/>) along with the YANG
module.</t>
          <t>The ".sid" file <bcp14>MUST NOT</bcp14> be published as part of the RFC: the IANA
Registry
registry is authoritative authoritative, and a link to it is to be inserted in the RFC.
(Note that the present RFC is an exception to this rule rule, as the SID ".sid"
file also serves as an example for exposition.)
RFCs
Internet-Drafts that need SIDs assigned to their new modules for use in the text
of the document, e.g., for examples, need to alert the RFC editor Editor in
the draft text that this is the case.
Such RFCs cannot be produced by type-3 (SID-oblivious) developers:
the SIDs used in the text need to be assigned in the existing draft
SID
".sid" file, and the designated expert team needs to check that the
assignments in the final SID ".sid" file are consistent with the usage in the
RFC text or that the approved draft test text is changed appropriately.</t>
        </section>
        <section anchor="ietf-iana-sid-range-initial-contents">
          <name>Initial contents Contents of the registry</name> Registry</name>
          <t>Initial entries in this registry are as follows:</t>
          <table align="left">
          <name>IETF YANG-SID Ranges Registry: Initial Range Assignments</name>
            <thead>
              <tr>
                <th align="right">Entry Point</th>
                <th align="right">Size</th>
                <th align="left">Module name</th> Name</th>
                <th align="left">Document reference</th> align="left">Reference</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="right">0</td>
                <td align="right">1</td>
                <td align="left">(Reserved: not a valid SID)</td>
                <td align="left">RFCXXXX</td> align="left">RFC 9595</td>
              </tr>
<!-- [LB] June and July 2024
Update 28 June 2024:  Removed the "2400  50" entry per
this note from IANA:
"NOTE: Per the authors, please note the following changes:
"- The name of the registry group for the new registries in Section
6.3 is YANG SID.
"- The following entry has been removed from the IETF YANG SID Range
registry: 2400 50 ietf-voucher [RFC8366].

"We suggested they upload a new version of the document to reflect
these changes."

Original:
 |  2400 |  50| ietf-voucher | [RFC8366]                            |

Update 16 July 2024:  Removed the "2450  50" and "2500  50" rows per
this note from IANA (15 July 2024):
"With chair and AD approval, we've completed the early allocations for the ANIMA document registrations. These can be removed from Table 4:

"Entry Point 	Size 	Module Name 	Reference
2450	50	ietf-voucher (TEMPORARY - registered 2024-07-15, expires 2025-07-15)	[draft-ietf-anima-rfc8366bis-12]
2500	50	ietf-voucher-request (TEMPORARY - registered 2024-07-15, expires 2025-07-15)	[draft-ietf-anima-rfc8366bis-12]

"We've also listed this document as an additional reference for the following registration to match Table 4:

"1000	100	ietf-coreconf	[RFC-ietf-core-sid-24][draft-ietf-core-comi-16]"
-->

              <tr>
                <td align="right">1000</td> align="right">1,000</td>
                <td align="right">100</td>
                <td align="left">ietf-coreconf</td>
                <td align="left"> align="left">RFC 9595, <xref target="I-D.ietf-core-comi"/></td> target="CORE-COMI"/></td>
              </tr>
              <tr>
                <td align="right">1100</td> align="right">1,100</td>
                <td align="right">50</td>
                <td align="left">ietf-yang-types</td>
                <td align="left">
                  <xref target="RFC6991"/></td>
              </tr>
              <tr>
                <td align="right">1150</td> align="right">1,150</td>
                <td align="right">50</td>
                <td align="left">ietf-inet-types</td>
                <td align="left">
                  <xref target="RFC6991"/></td>
              </tr>
              <tr>
                <td align="right">1200</td> align="right">1,200</td>
                <td align="right">50</td>
                <td align="left">iana-crypt-hash</td>
                <td align="left">
                  <xref target="RFC7317"/></td>
              </tr>
              <tr>
                <td align="right">1250</td> align="right">1,250</td>
                <td align="right">50</td>
                <td align="left">ietf-netconf-acm</td>
                <td align="left">
                  <xref target="RFC8341"/></td> target="STD91"/></td>
              </tr>
              <tr>
                <td align="right">1300</td> align="right">1,300</td>
                <td align="right">50</td>
                <td align="left">ietf-sid-file</td>
                <td align="left">RFCXXXX</td> align="left">RFC 9595</td>
              </tr>
              <tr>
                <td align="right">1500</td> align="right">1,500</td>
                <td align="right">100</td>
                <td align="left">ietf-interfaces</td>
                <td align="left">
                  <xref target="RFC8343"/></td>
              </tr>
              <tr>
                <td align="right">1600</td> align="right">1,600</td>
                <td align="right">100</td>
                <td align="left">ietf-ip</td>
                <td align="left">
                  <xref target="RFC8344"/></td>
              </tr>
              <tr>
                <td align="right">1700</td> align="right">1,700</td>
                <td align="right">100</td>
                <td align="left">ietf-system</td>
                <td align="left">
                  <xref target="RFC7317"/></td>
              </tr>
              <tr>
                <td align="right">1800</td> align="right">1,800</td>
                <td align="right">400</td>
                <td align="left">iana-if-type</td>
                <td align="left">
                  <xref target="RFC7224"/></td>
              </tr>
<!--              <tr>
                <td align="right">2400</td> align="right">2,400</td>
                <td align="right">50</td>
                <td align="left">ietf-voucher</td>
                <td align="left">
                  <xref target="RFC8366"/></td>
              </tr>
              <tr>
                <td align="right">2450</td> align="right">2,450</td>
                <td align="right">50</td>
                <td align="left">ietf-constrained-voucher</td>
                <td align="left">
                  <xref target="I-D.ietf-anima-constrained-voucher"/></td> target="CONSTRAINED-VOUCHER"/></td>
              </tr>
              <tr>
                <td align="right">2500</td> align="right">2,500</td>
                <td align="right">50</td>
                <td align="left">ietf-constrained-voucher-request</td>
                <td align="left">
                  <xref target="I-D.ietf-anima-constrained-voucher"/></td> target="CONSTRAINED-VOUCHER"/></td>
              </tr> -->
            </tbody>
          </table>
          <t>// RFC Ed.: replace XXXX with RFC number assigned to this draft.</t>
          <t>For allocation, RFC publication of the YANG module is required as per the "RFC Required" policy defined in
Section&nbsp;<xref target="RFC8126" sectionFormat="bare" section="4.7"/> of RFC 8126 <xref target="RFC8126"/>. target="BCP26"/>. The YANG module must be registered in the "YANG module Name" Module Names" registry according to the rules specified in <xref section="14" sectionFormat="of" target="RFC6020"/>.</t>
        </section>
      </section>

      <section anchor="ietf-sid-registry">
        <name>Create new
        <name>New IANA Registry: "IETF YANG SID Registry"</name> IETF YANG-SID Modules</name>
        <t>The name of this registry is "IETF YANG SID Registry". YANG-SID Modules".  This registry is used to
record the allocation of SIDs for individual YANG module items.</t>
        <section anchor="structure-1">
          <name>Structure</name>
          <t>Each entry in this registry must include:</t>
          <ul spacing="normal">
            <li>

              <t>The YANG module name. This module name must be present in the "Name" column of the "YANG Module Names" registry.</t>
            </li>
            <li>
              <t>A URI for the associated ".yang" file.  This file link must be present in the "File" column of the "YANG Module Names" registry.</t>
            </li>
            <li>
              <t>The URI for the ".sid" file which that defines the allocation. The ".sid" file is stored by IANA.</t>
            </li>
            <li>
              <t>The number of actually allocated SIDs in the ".sid" file.</t>
            </li>
          </ul>
        </section>
        <section anchor="allocation-policy-1">
          <name>Allocation policy</name> Policy</name>
          <t>The allocation policy is Expert review. "Expert Review" (Section&nbsp;<xref target="RFC8126" sectionFormat="bare" section="4.5"/> of RFC 8126 <xref target="BCP26"/>). The Expert expert <bcp14>MUST</bcp14> ensure that the following conditions are met:</t>
          <ul spacing="normal">
            <li>
              <t>The ".sid" file has a valid structure:
              </t>
              <ul spacing="normal">
                <li>

                  <t>The ".sid" file <bcp14>MUST</bcp14> be a valid JSON file following the structure of the
module defined in RFCXXXX (RFC Ed: replace XXX with RFC number assigned
to this draft).</t> document.</t>
                </li>
              </ul>
            </li>
            <li>
              <t>The ".sid" file allocates individual SIDs ONLY in the YANG SID YANG-SID Ranges for this
YANG module (as allocated in the IETF YANG SID Range Registry): "IETF YANG-SID Ranges" registry):
              </t>
              <ul spacing="normal">
                <li>
                  <t>All SIDs in this ".sid" file <bcp14>MUST</bcp14> be within the ranges allocated to this
YANG module in the "IETF YANG SID Range Registry".</t> YANG-SID Ranges" registry.</t>
                </li>
              </ul>
            </li>
            <li>
              <t>If another ".sid" file has already allocated SIDs for this YANG module (e.g. (e.g.,
for older or newer versions of the YANG module), the YANG items are assigned
the same SIDs as those in the other ".sid" file.</t>
            </li>
            <li>
              <t>If there is an older version of the ".sid" file, all allocated SIDs from that
version are still present in the current version of the ".sid" file.</t>
            </li>
          </ul>
        </section>
        <section anchor="recursive-allocation-at-adoption">
          <name>Recursive Allocation of YANG SID Range SIDs at Document Adoption</name>
          <t>Due to the difficulty in changing SID values during IETF document processing,
it is expected that most documents will ask for SID range allocations using Early
Allocations <xref target="BCP100"/>. The details of the Early Allocation to be
requested, including the timeline envisioned, should be included
in any Working Group Adoption working group adoption call. Prior to Working Group Adoption, working group adoption, an internet
draft
Internet-Draft author can use the experimental SID range (as per
<xref target="ietf-iana-sid-range-allocation-policy"/>) for their SIDs SID allocations or
other values that do not create ambiguity with other SID uses (for example example,
they can use ranges and SIDs registered in a range non-IANA-managed registry that comes from is based on a non-IANA managed "YANG SID Mega-Range"
registry).</t> YANG-SID Mega-Range assignment).</t>
          <t>After Working Group Adoption, working group adoption, any modification of a ".sid" file is expected to be
discussed on the mailing list lists of the appropriate Working Groups. working groups. Specific
attention should be paid to implementers' opinion opinions after Working Group Last Call
if a SID value is to change its meaning. In all cases, a ".sid" file and the SIDs
associated with it are subject to change before the publication of an internet
draft
Internet-Draft as an RFC.</t>
          <t>During
          <t>As the early use concept of SIDs, SIDs is first used, many existing, previously published YANG modules
will not have SID allocations.  For an allocation to be useful useful, the included
YANG modules may also need to have SID allocations made, in a process
that will generally be analogous to that in <xref target="publink"/> for the type-3 (SID-oblivious) case.</t>
          <t>The Expert Reviewer expert reviewer who performs the (Early) Allocation analysis will need to
go through the list of included YANG modules and perform SID allocations for
those modules as well.</t>
          <ul spacing="normal">
            <li>
              <t>If the document is a published RFC, then the allocation of SIDs for its
referenced YANG modules is permanent.  The Expert Reviewer expert reviewer provides the
generated ".sid" file to IANA for registration.</t>
            </li>
            <li>
              <t>If the document is an unprocessed Internet-Draft adopted in a WG, working group, then an
Early Allocation is performed for this document as well. Early Allocations
require approval by an IESG Area Director. area director.  An early allocation which Early Allocation that
requires additional allocations will list the other allocations in its
description,
description and will be cross-posted to the mailing lists of any
other working groups concerned.</t>
            </li>
            <li>
              <t>A YANG module which that references a module in a document which that has not yet been
adopted by any working group will be unable to perform an Early Allocation
for that other document until it is adopted by a working group.  As described
in Section&nbsp;<xref target="RFC7120"
sectionFormat="bare" section="3"/> of RFC 7120 <xref target="BCP100"/>, an a shepherding AD Sponsored document acts as will stand in for the working group chairs if it had a the document is not the product of an IETF working group.  The
approving group, effectively allowing the AD may also to exempt a document from this policy by agreeing to AD
Sponsor the document.</t> policy.</t>
            </li>
          </ul>
          <t>At the end of the IETF process process, all the dependencies of a given module for which
SIDs are assigned, assigned should also have SIDs assigned. Those dependencies'
assignments should be permanent (not Early Allocation).</t>
          <t>A previously SID-allocated YANG module which that changes its references to include
a YANG module for which there is no SID allocation needs to repeat the Early
Allocation process.</t>
          <t><xref target="BCP100"/> defines a time limit for the validity of Early Allocations,
after which they expire unless they are renewed.  Section&nbsp;<xref target="RFC7120" sectionFormat="bare" section="3.3"/> of RFC 7120 <xref target="BCP100"/> also says:</t>
          <blockquote cite="https://www.rfc-editor.org/rfc/rfc7120.html#section-3.3" quotedFrom="RFC7120 (BCP100), Section 3.3">

<!-- DNE; fixed (OKed by author) -->
          <blockquote>
            <t>Note that if a document is submitted for review to the IESG IESG, and at
   the time of submission some early allocations Early Allocations are valid (not
   expired), these allocations should must not be considered to have expired
   while the document is under IESG consideration or waiting is awaiting
   publication in the RFC Editor's queue after approval by the IESG.</t>
          </blockquote>
        </section>
        <section anchor="initial-contents-of-the-registry-1">
          <name>Initial contents Contents of the registry</name>
          <t>None.</t> Registry</name>
          <t>At the time of writing, this registry does not contain any entries.</t>
        </section>
      </section>
      <section anchor="register-media-type-and-content-format">
        <name>Register Media
        <name>Media Type and Content-Format</name> Content-Format Registration</name>
        <section anchor="media-type-applicationyang-sidjson">
          <name>Media Type application/yang-sid+json</name>
          <t>This document adds the following Media-Type media type to the "Media Types" registry.</t>
          <table align="left">
            <name>SID
            <name>&quot;.sid&quot; File Media-Type Media Type Registration</name>
            <thead>
              <tr>
                <th align="left">Name</th>
                <th align="left">Template</th>
                <th align="left">Reference</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">yang-sid+json</td>
                <td align="left">application/yang-sid+json</td>
                <td align="left">RFC XXXX</td> 9595</td>
              </tr>
            </tbody>
          </table>
          <t>// RFC Ed.: please replace RFC XXXX with this RFC number and remove this note.</t>
          <dl spacing="compact"> spacing="normal">
            <dt>Type name:</dt>
            <dd>
              <t>application</t>
            </dd>
            <dt>Subtype name:</dt>
            <dd>
              <t>yang-sid+json</t>
            </dd>
            <dt>Required parameters:</dt>
            <dd>
              <t>N/A</t>
            </dd>
            <dt>Optional parameters:</dt>
            <dd>
              <t>N/A</t>
            </dd>
            <dt>Encoding considerations:</dt>
            <dd>
              <t>binary (UTF-8)</t>
            </dd>
            <dt>Security considerations:</dt>
            <dd>
              <t>see
              <t>See <xref target="security-considerations"/> of RFC XXXX</t> 9595.</t>
            </dd>
            <dt>Published specification:</dt>
            <dd>
              <t>RFC XXXX</t> 9595</t>
            </dd>
            <dt>Applications that use this media type:</dt>
            <dd>
              <t>applications
              <t>Applications that need to obtain YANG SIDs to interchange
YANG-modeled data in a concise and efficient representation</t> representation.</t>
            </dd>
            <dt>Fragment identifier considerations:</dt>
            <dd>
              <t>The syntax and semantics of
    fragment identifiers specified for "application/yang-sid+json" is
    as specified for "application/json".  (At publication of this
    document, there is no fragment identification syntax defined for
    "application/json".)</t>
            </dd>
            <dt>Additional information:</dt>
            <dd>
              <dl>
                <dt><br/></dt>
                <dd>
                  <t/>
                </dd>
            <dd><t><br/></t>
            <dl spacing="compact">
                <dt>Magic number(s):</dt>
                <dd>
                  <t>N/A</t>
                </dd>
                <dt>File extension(s):</dt>
                <dd>
                  <t>.sid</t>
                </dd>
                <dt>Macintosh file type code(s):</dt>
                <dd>
                  <t>N/A</t>
                </dd>
              </dl>
            </dd>
            <dt>Person &amp; email address to contact for further information:</dt>
            <dd>
              <t>CORE WG mailing list (core@ietf.org), (core@ietf.org)
or IETF Applications and Real-Time Area (art@ietf.org)</t>
            </dd>
            <dt>Intended usage:</dt>
            <dd>
              <t>COMMON</t>
            </dd>
            <dt>Restrictions on usage:</dt>
            <dd>
              <t>none</t>
            </dd>
            <dt>Author/Change controller:</dt>
            <dd>
              <t>IETF</t>
            </dd>
          </dl>
        </section>
        <section anchor="coap-content-format">
          <name>CoAP Content-Format</name>
          <t>This document adds the following Content-Format to the "CoAP Content-Formats", Content-Formats" registry
within the "Constrained RESTful Environments (CoRE) Parameters"
registry, group of
registries, where TBD1 comes 260 has been assigned from the "IETF Review" 256-999 range.</t> (256-9,999) range (see Section&nbsp;<xref target="RFC8126" sectionFormat="bare" section="4.8"/> of RFC 8126 <xref target="BCP26"/>).</t>
          <table align="left">
            <name>SID
            <name>&quot;.sid&quot; File Content-format Content-Format Registration</name>
            <thead>
              <tr>
                <th align="left">Content Type</th>
                <th align="left">Content Coding</th>
                <th align="left">ID</th>
                <th align="left">Reference</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">application/yang-sid+json</td>
                <td align="left">-</td>
                <td align="left">TBD1</td> align="left">260</td>
                <td align="left">RFC XXXX</td> 9595</td>
              </tr>
            </tbody>
          </table>
          <t>// RFC Ed.: please replace TBD1 with the assigned ID, remove the
requested range, and remove this note.<br/>
// RFC Ed.: please replace RFC XXXX with this RFC number and remove this note.</t>
        </section>
      </section>
    </section>
  </middle>
  <back>

    <references>
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <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="RFC6991">
          <front>
            <title>Common YANG Data Types</title>
            <author fullname="J. Schoenwaelder" initials="J." role="editor" surname="Schoenwaelder"/>
            <date month="July" year="2013"/>
            <abstract>
              <t>This document introduces a collection of common data types to be used with the YANG data modeling language. This document obsoletes RFC 6021.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6991"/>
          <seriesInfo name="DOI" value="10.17487/RFC6991"/>
        </reference>
        <reference anchor="BCP100">
          <front>
            <title>Early IANA Allocation of Standards Track Code Points</title>
            <author fullname="M. Cotton" initials="M." surname="Cotton"/>
            <date month="January" year="2014"/>
            <abstract>
              <t>This memo describes the process for early allocation of code points by IANA from registries for which "Specification Required", "RFC Required", "IETF Review", or "Standards Action" policies apply. This process can be used to alleviate the problem where code point allocation is needed to facilitate desired or required implementation and deployment experience prior to publication of an RFC, which would normally trigger code point allocation. The procedures in this document are intended to apply only to IETF Stream documents.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="100"/>
          <seriesInfo name="RFC" value="7120"/>
          <seriesInfo name="DOI" value="10.17487/RFC7120"/>
        </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="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="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>
        <reference anchor="RFC8259">
          <front>
            <title>The JavaScript Object Notation (JSON) Data Interchange Format</title>
            <author fullname="T. Bray" initials="T." role="editor" surname="Bray"/>
            <date month="December" year="2017"/>
            <abstract>
              <t>JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard. JSON defines a small set of formatting rules for the portable representation of structured data.</t>
              <t>This document removes inconsistencies with other specifications of JSON, repairs specification errors, and offers experience-based interoperability guidance.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="90"/>
          <seriesInfo name="RFC" value="8259"/>
          <seriesInfo name="DOI" value="10.17487/RFC8259"/>
        </reference>
        <reference anchor="RFC8791">
          <front>
            <title>YANG Data Structure Extensions</title>
            <author fullname="A. Bierman" initials="A." surname="Bierman"/>
            <author fullname="M. Björklund" initials="M." surname="Björklund"/>
            <author fullname="K. Watsen" initials="K." surname="Watsen"/>
            <date month="June" year="2020"/>
            <abstract>
              <t>This document describes YANG mechanisms for defining abstract data structures with YANG.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8791"/>
          <seriesInfo name="DOI" value="10.17487/RFC8791"/>
        </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>

	<xi:include href="https://bib.ietf.org/public/rfc/bibxml9/reference.BCP.81.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml9/reference.STD.68.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6991.xml"/>
	<referencegroup anchor="BCP100" target="https://www.rfc-editor.org/info/bcp100">
	  <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7120.xml"/>
	</referencegroup>

	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7950.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7951.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8040.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml9/reference.STD.90.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8791.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml9/reference.BCP.14.xml"/>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <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>
        <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="RFC7224">
          <front>
            <title>IANA Interface Type YANG Module</title>
            <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
            <date month="May" year="2014"/>
            <abstract>
              <t>This document defines the initial version of the iana-if-type YANG module.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7224"/>
          <seriesInfo name="DOI" value="10.17487/RFC7224"/>
        </reference>
        <reference anchor="RFC7228">
          <front>
            <title>Terminology for Constrained-Node Networks</title>
            <author fullname="C. Bormann" initials="C." surname="Bormann"/>
            <author fullname="M. Ersue" initials="M." surname="Ersue"/>
            <author fullname="A. Keranen" initials="A." surname="Keranen"/>
            <date month="May" year="2014"/>
            <abstract>
              <t>The Internet Protocol Suite is increasingly used on small devices with severe constraints on power, memory, and processing resources, creating constrained-node networks. This document provides a number of basic terms that have been useful in the standardization work for constrained-node networks.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7228"/>
          <seriesInfo name="DOI" value="10.17487/RFC7228"/>
        </reference>
        <reference anchor="RFC7317">
          <front>
            <title>A YANG Data Model for System Management</title>
            <author fullname="A. Bierman" initials="A." surname="Bierman"/>
            <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
            <date month="August" year="2014"/>
            <abstract>
              <t>This document defines a YANG data model for the configuration and identification of some common system properties within a device containing a Network Configuration Protocol (NETCONF) server. This document also includes data node definitions for system identification, time-of-day management, user management, DNS resolver configuration, and some protocol operations for system management.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7317"/>
          <seriesInfo name="DOI" value="10.17487/RFC7317"/>
        </reference>
        <reference anchor="RFC8126">
          <front>
            <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
            <author fullname="M. Cotton" initials="M." surname="Cotton"/>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <author fullname="T. Narten" initials="T." surname="Narten"/>
            <date month="June" year="2017"/>
            <abstract>
              <t>Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).</t>
              <t>To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.</t>
              <t>This is the third edition of this document; it obsoletes RFC 5226.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="26"/>
          <seriesInfo name="RFC" value="8126"/>
          <seriesInfo name="DOI" value="10.17487/RFC8126"/>
        </reference>
        <reference anchor="RFC8341">
          <front>
            <title>Network Configuration Access Control Model</title>
            <author fullname="A. Bierman" initials="A." surname="Bierman"/>
            <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
            <date month="March" year="2018"/>
            <abstract>
              <t>The standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) or the RESTCONF protocol requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability. There is a need for standard mechanisms to restrict NETCONF or RESTCONF protocol access for particular users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. This document defines such an access control model.</t>
              <t>This document obsoletes RFC 6536.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="91"/>
          <seriesInfo name="RFC" value="8341"/>
          <seriesInfo name="DOI" value="10.17487/RFC8341"/>
        </reference>
        <reference anchor="RFC8343">
          <front>
            <title>A YANG Data Model for Interface Management</title>
            <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
            <date month="March" year="2018"/>
            <abstract>
              <t>This document defines a YANG data model for the management of network interfaces. It is expected that interface-type-specific data models augment the generic interfaces data model defined in this document. The data model includes definitions for configuration and system state (status information and counters for the collection of statistics).</t>
              <t>The YANG data model in this document conforms to the Network Management Datastore Architecture (NMDA) defined in RFC 8342.</t>
              <t>This document obsoletes RFC 7223.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8343"/>
          <seriesInfo name="DOI" value="10.17487/RFC8343"/>
        </reference>
        <reference anchor="RFC8344">
          <front>
            <title>A YANG Data Model for IP Management</title>
            <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
            <date month="March" year="2018"/>
            <abstract>
              <t>This document defines a YANG data model for management of IP implementations. The data model includes configuration and system state.</t>
              <t>The YANG data model in this document conforms to the Network Management Datastore Architecture defined in RFC 8342.</t>
              <t>This document obsoletes RFC 7277.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8344"/>
          <seriesInfo name="DOI" value="10.17487/RFC8344"/>
        </reference>
        <reference anchor="RFC8366">
          <front>
            <title>A Voucher Artifact for Bootstrapping Protocols</title>
            <author fullname="K. Watsen" initials="K." surname="Watsen"/>
            <author fullname="M. Richardson" initials="M." surname="Richardson"/>
            <author fullname="M. Pritikin" initials="M." surname="Pritikin"/>
            <author fullname="T. Eckert" initials="T." surname="Eckert"/>
            <date month="May" year="2018"/>
            <abstract>
              <t>This document defines a strategy to securely assign a pledge to an owner using an artifact signed, directly or indirectly, by the pledge's manufacturer. This artifact is known as a "voucher".</t>
              <t>This document defines an artifact format as a YANG-defined JSON document that has been signed using a Cryptographic Message Syntax (CMS) structure. Other YANG-derived formats are possible. The voucher artifact is normally generated by the pledge's manufacturer (i.e., the Manufacturer Authorized Signing Authority (MASA)).</t>
              <t>This document only defines the voucher artifact, leaving it to other documents to describe specialized protocols for accessing it.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8366"/>
          <seriesInfo name="DOI" value="10.17487/RFC8366"/>
        </reference>
        <reference anchor="RFC8407">
          <front>
            <title>Guidelines for Authors and Reviewers of Documents Containing YANG Data Models</title>
            <author fullname="A. Bierman" initials="A." surname="Bierman"/>
            <date month="October" year="2018"/>
            <abstract>
              <t>This memo provides guidelines for authors and reviewers of specifications containing YANG modules. Recommendations and procedures are defined, which are intended to increase interoperability and usability of Network Configuration Protocol (NETCONF) and RESTCONF protocol implementations that utilize YANG modules. This document obsoletes RFC 6087.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="216"/>
          <seriesInfo name="RFC" value="8407"/>
          <seriesInfo name="DOI" value="10.17487/RFC8407"/>
        </reference>
        <reference anchor="RFC8792">
          <front>
            <title>Handling Long Lines in Content of Internet-Drafts and RFCs</title>
            <author fullname="K. Watsen" initials="K." surname="Watsen"/>
            <author fullname="E. Auerswald" initials="E." surname="Auerswald"/>
            <author fullname="A. Farrel" initials="A." surname="Farrel"/>
            <author fullname="Q. Wu" initials="Q." surname="Wu"/>
            <date month="June" year="2020"/>
            <abstract>
              <t>This document defines two strategies for handling long lines in width-bounded text content. One strategy, called the "single backslash" strategy, is based on the historical use of a single backslash ('\') character to indicate where line-folding has occurred, with the continuation occurring with the first character that is not a space character (' ') on the next line. The second strategy, called the "double backslash" strategy, extends the first strategy by adding a second backslash character to identify where the continuation begins

	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6020.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6241.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7224.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7228.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7317.xml"/>
        <referencegroup anchor="BCP26"
target="https://www.rfc-editor.org/info/bcp26">
	 <xi:include
href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml"/>
        </referencegroup>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml9/reference.BCP.215.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml9/reference.STD.91.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8343.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8344.xml"/>
<!--	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8366.xml"/> -->
        <referencegroup anchor="BCP216"
target="https://www.rfc-editor.org/info/bcp216">
	 <xi:include
href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8407.xml"/>
        </referencegroup>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8792.xml"/>

<!-- draft-ietf-core-comi (I-D Exists)
     "Long way" to fix initials, add surname, and is thereby able to handle cases not supported by the first strategy. Both strategies use a self-describing header enabling automated reconstitution of the original content.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8792"/>
          <seriesInfo name="DOI" value="10.17487/RFC8792"/>
        </reference> add editor designations -->
<reference anchor="I-D.ietf-core-comi"> anchor="CORE-COMI">
   <front>
      <title>CoAP Management Interface (CORECONF)</title>
      <author initials="M." surname="Veillette" fullname="Michel Veillette" initials="M." surname="Veillette"> role="editor">
         <organization>Trilliant Networks Inc.</organization>
      </author>
      <author fullname="Peter Van initials="P." surname="van der Stok" initials="P." surname="Van fullname="Peter van der Stok"> Stok" role="editor">
         <organization>consultant</organization>
      </author>
      <author initials="A." surname="Pelov" fullname="Alexander Pelov" initials="A." surname="Pelov">
              <organization>Acklio</organization> role="editor">
         <organization>IMT Atlantique</organization>
      </author>
      <author fullname="Andy Bierman" initials="A." surname="Bierman"> surname="Bierman" fullname="Andy Bierman">
         <organization>YumaWorks</organization>
      </author>
      <author initials="C." surname="Bormann" fullname="Carsten Bormann" initials="C." surname="Bormann"> role="editor">
         <organization>Universität Bremen TZI</organization>
      </author>
      <date day="4" month="September" year="2023"/>
            <abstract>
              <t>   This document describes a network management interface for
   constrained devices and networks, called CoAP Management Interface
   (CORECONF).  The Constrained Application Protocol (CoAP) is used to
   access datastore and data node resources specified in YANG, or SMIv2
   converted to YANG.  CORECONF uses the YANG to CBOR mapping and
   converts YANG identifier strings to numeric identifiers for payload
   size reduction.  CORECONF extends the set of YANG based protocols,
   NETCONF and RESTCONF, with the capability to manage constrained
   devices and networks.

              </t>
            </abstract> month="July" day="23" year="2024" />
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-core-comi-16"/> value="draft-ietf-core-comi-18" />
</reference>

<!-- draft-ietf-core-yang-library (Expired)
     "Long way" to add editor designations -->
<reference anchor="I-D.ietf-core-yang-library"> anchor="YANG-LIBRARY">
  <front>
    <title>Constrained YANG Module Library</title>
    <author fullname="Michel Veillette" initials="M." surname="Veillette"> surname="Veillette" role="editor">
      <organization>Trilliant Networks Inc.</organization>
    </author>
    <author fullname="Ivaylo Petrov" initials="I." surname="Petrov"> surname="Petrov" role="editor">
      <organization>Acklio</organization>
    </author>
    <date day="11" month="January" year="2021"/>
            <abstract>
              <t>   This document describes a constrained version of the YANG library
   that provides information about the YANG modules, datastores, and
   datastore schemas used by a constrained network management server
   (e.g., a CORECONF server).

              </t>
            </abstract>
  </front>
  <seriesInfo name="Internet-Draft" value="draft-ietf-core-yang-library-03"/>
</reference>

<!-- draft-ietf-anima-constrained-voucher (WG Last Call)
     "Long way" to fix surname
   NOTE:  Removed this reference entry, as the 16 July 2024 updates to
   Table 4 per IANA removed any mention of this draft.
<reference anchor="I-D.ietf-anima-constrained-voucher"> anchor="CONSTRAINED-VOUCHER">
  <front>
    <title>Constrained Bootstrapping Remote Secure Key Infrastructure (BRSKI)</title> (cBRSKI)</title>
    <author fullname="Michael Richardson" initials="M." surname="Richardson">
      <organization>Sandelman Software Works</organization>
    </author>
    <author fullname="Peter Van van der Stok" initials="P." surname="Van surname="van der Stok">
      <organization>vanderstok consultancy</organization>
    </author>
    <author fullname="Panos Kampanakis" initials="P." surname="Kampanakis">
      <organization>Cisco Systems</organization>
    </author>
    <author fullname="Esko Dijk" initials="E." surname="Dijk">
      <organization>IoTconsultancy.nl</organization>
    </author>
    <date day="21" month="November" year="2023"/>
            <abstract>
              <t>   This document defines the Constrained Bootstrapping Remote Secure Key
   Infrastructure (Constrained BRSKI) protocol, which provides a
   solution for secure zero-touch bootstrapping of resource-constrained
   (IoT) devices into the network of a domain owner.  This protocol is
   designed for constrained networks, which may have limited data
   throughput or may experience frequent packet loss.  Constrained BRSKI
   is a variant of the BRSKI protocol, which uses an artifact signed by
   the device manufacturer called the "voucher" which enables a new
   device and the owner's network to mutually authenticate.  While the
   BRSKI voucher is typically encoded in JSON, Constrained BRSKI uses a
   compact CBOR-encoded voucher.  The BRSKI voucher definition is
   extended with new data types that allow for smaller voucher sizes.
   The Enrollment over Secure Transport (EST) protocol, used in BRSKI,
   is replaced with EST-over-CoAPS; and HTTPS used in BRSKI is replaced
   with DTLS-secured CoAP (CoAPS).  This document Updates RFC 8366 and
   RFC 8995.

              </t>
            </abstract> day="3" month="March" year="2024"/>
  </front>
  <seriesInfo name="Internet-Draft" value="draft-ietf-anima-constrained-voucher-22"/>
        </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"/> value="draft-ietf-anima-constrained-voucher-24"/>
</reference> -->

	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9254.xml"/>

        <reference anchor="yangcatalog" target="https://yangcatalog.org">
          <front>
            <title>YANG Catalog</title>
            <author>
              <organization/>
              <organization></organization>
            </author>
            <date/>
          </front>
        </reference>

        <reference anchor="PYANG" target="https://github.com/mbj4668/pyang">
          <front>
            <title>An extensible YANG validator and converter in python</title>
            <author initials="M." surname="Bjorklund" surname="Björklund" fullname="Martin Bjorklund"> Björklund">
              <organization/>
            </author>
            <date/>
            <date month="March" year="2024"/>
          </front>
         <refcontent>commit 25f69e8</refcontent>
        </reference>

<!-- draft-bormann-t2trg-deref-id (I-D Exists)
     "Long way" to fix "double quotes within double quotes" in title -->
<reference anchor="I-D.bormann-t2trg-deref-id"> anchor="DEREF-ID">
  <front>
    <title>The "dereferenceable identifier" &apos;dereferenceable identifier&apos; pattern</title>
    <author fullname="Carsten Bormann" initials="C." surname="Bormann">
      <organization>Universität Bremen TZI</organization>
    </author>
    <author fullname="Christian Amsüss" initials="C." surname="Amsüss">
         </author> surname="Amsüss"/>
    <date day="19" month="December" year="2023"/>
            <abstract>
              <t>   In a protocol or an application environment, it is often important to
   be able to create unambiguous identifiers for some meaning (concept
   or some entity).

   Due to the simplicity of creating URIs, these have become popular for
   this purpose.  Beyond the purpose of identifiers to be uniquely
   associated with a meaning, some of these URIs are in principle
   _dereferenceable_, so something can be placed that can be retrieved
   when encountering such a URI.

   // The present -01 version is a stub to draw some attention to the
   // opportunity that this pattern would benefit from a common
   // description, documenting its benefits and pitfalls, and some
   // mitigations for the latter.

              </t>
            </abstract> day="2" month="March" year="2024"/>
  </front>
  <seriesInfo name="Internet-Draft" value="draft-bormann-t2trg-deref-id-02"/>
        </reference>
        <reference anchor="RFC9195">
          <front>
            <title>A File Format for YANG Instance Data</title>
            <author fullname="B. Lengyel" initials="B." surname="Lengyel"/>
            <author fullname="B. Claise" initials="B." surname="Claise"/>
            <date month="February" year="2022"/>
            <abstract>
              <t>There is a need to document data defined in YANG models at design time, implementation time, or when a live server is unavailable. This document specifies a standard file format for YANG instance data, which follows the syntax and semantics of existing YANG models and annotates it with metadata.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9195"/>
          <seriesInfo name="DOI" value="10.17487/RFC9195"/> value="draft-bormann-t2trg-deref-id-03"/>
</reference>

	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9195.xml"/>

      </references>
    </references>
    <?line 1331?>

<section anchor="sid-file-example">
      <name>".sid" file example</name> File Example</name>
      <t>The following ".sid" file (ietf-system@2014-08-06.sid) ('ietf-system@2014-08-06.sid') has been generated using the following yang YANG modules:</t>
      <ul spacing="normal">
        <li>
          <t>ietf-system@2014-08-06.yang
          <t>'ietf-system@2014-08-06.yang' (defined in <xref target="RFC7317"/>)</t>
        </li>
        <li>
          <t>ietf-yang-types@2013-07-15.yang
          <t>'ietf-yang-types@2013-07-15.yang' (defined in <xref target="RFC6991"/>)</t>
        </li>
        <li>
          <t>ietf-inet-types@2013-07-15.yang
          <t>'ietf-inet-types@2013-07-15.yang' (defined in <xref target="RFC6991"/>)</t>
        </li>
        <li>
          <t>ietf-netconf-acm@2018-02-14.yang
          <t>'ietf-netconf-acm@2018-02-14.yang' (defined in <xref target="RFC8341"/>)</t> target="STD91"/>)</t>
        </li>
        <li>
          <t>iana-crypt-hash@2014-08-06.yang
          <t>'iana-crypt-hash@2014-08-06.yang' (defined in <xref target="RFC7317"/>)</t>
        </li>
      </ul>
      <t>For purposes of exposition, per <xref target="RFC8792"/>, line breaks have been introduced below in
some JSON strings that represent overly long identifiers.</t>
      <!-- /^ *[^" ]+"/ -->

<figure anchor="sid-example-pretty">
        <name>Example .sid file (ietf-system, &quot;.sid&quot; File ('ietf-system', with extra line-breaks)</name> Extra Line Breaks)</name>

        <sourcecode type="yang-sid"><![CDATA[ type="yang-sid+json"><![CDATA[
=============== NOTE: '\' line wrapping per RFC 8792 ================

{
  "ietf-sid-file:sid-file": {
    "module-name": "ietf-system",
    "module-revision": "2014-08-06",
    "description": "Example sid '.sid' file",
    "dependency-revision": [
      {
        "module-name": "ietf-yang-types",
        "module-revision": "2013-07-15"
      },
      {
        "module-name": "ietf-inet-types",
        "module-revision": "2013-07-15"
      },
      {
        "module-name": "ietf-netconf-acm",
        "module-revision": "2018-02-14"
      },
      {
        "module-name": "iana-crypt-hash",
        "module-revision": "2014-08-06"
      }
    ],
    "assignment-range": [
      {
        "entry-point": "1700",
        "size": "100"
      }
    ],
    "item": [
      {
        "namespace": "module",
        "identifier": "ietf-system",
        "sid": "1700"
      },
      {
        "namespace": "identity",
        "identifier": "authentication-method",
        "sid": "1701"
      },
      {
        "namespace": "identity",
        "identifier": "local-users",
        "sid": "1702"
      },
      {
        "namespace": "identity",
        "identifier": "radius",
        "sid": "1703"
      },
      {
        "namespace": "identity",
        "identifier": "radius-authentication-type",
        "sid": "1704"
      },
      {
        "namespace": "identity",
        "identifier": "radius-chap",
        "sid": "1705"
      },
      {
        "namespace": "identity",
        "identifier": "radius-pap",
        "sid": "1706"
      },
      {
        "namespace": "feature",
        "identifier": "authentication",
        "sid": "1707"
      },
      {
        "namespace": "feature",
        "identifier": "dns-udp-tcp-port",
        "sid": "1708"
      },
      {
        "namespace": "feature",
        "identifier": "local-users",
        "sid": "1709"
      },
      {
        "namespace": "feature",
        "identifier": "ntp",
        "sid": "1710"
      },
      {
        "namespace": "feature",
        "identifier": "ntp-udp-port",
        "sid": "1711"
      },
      {
        "namespace": "feature",
        "identifier": "radius",
        "sid": "1712"
      },
      {
        "namespace": "feature",
        "identifier": "radius-authentication",
        "sid": "1713"
      },
      {
        "namespace": "feature",
        "identifier": "timezone-name",
        "sid": "1714"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:set-current-datetime",
        "sid": "1715"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:set-current-datetime/input",
        "sid": "1775"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:set-current-datetime/input/\
                                                   current-datetime",
        "sid": "1776"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system",
        "sid": "1717"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system-restart",
        "sid": "1718"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system-shutdown",
        "sid": "1719"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system-state",
        "sid": "1720"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system-state/clock",
        "sid": "1721"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system-state/clock/boot-datetime\
                                                                   ",
        "sid": "1722"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system-state/clock/current-\
                                                           datetime",
        "sid": "1723"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system-state/platform",
        "sid": "1724"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system-state/platform/machine",
        "sid": "1725"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system-state/platform/os-name",
        "sid": "1726"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system-state/platform/os-release\
                                                                   ",
        "sid": "1727"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system-state/platform/os-version\
                                                                   ",
        "sid": "1728"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/authentication",
        "sid": "1729"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/authentication/user",
        "sid": "1730"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/authentication/user-\
                                               authentication-order",
        "sid": "1731"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/authentication/user/\
                                                     authorized-key",
        "sid": "1732"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/authentication/user/\
                                           authorized-key/algorithm",
        "sid": "1733"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/authentication/user/\
                                            authorized-key/key-data",
        "sid": "1734"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/authentication/user/\
                                                authorized-key/name",
        "sid": "1735"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/authentication/user/name",
        "sid": "1736"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/authentication/user/\
                                                           password",
        "sid": "1737"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/clock",
        "sid": "1738"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/clock/timezone-name",
        "sid": "1739"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/clock/timezone-utc-offset\
                                                                   ",
        "sid": "1740"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/contact",
        "sid": "1741"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/dns-resolver",
        "sid": "1742"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/dns-resolver/options",
        "sid": "1743"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/dns-resolver/options/\
                                                           attempts",
        "sid": "1744"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/dns-resolver/options/\
                                                            timeout",
        "sid": "1745"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/dns-resolver/search",
        "sid": "1746"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/dns-resolver/server",
        "sid": "1747"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/dns-resolver/server/name",
        "sid": "1748"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/dns-resolver/server/udp-\
                                                            and-tcp",
        "sid": "1749"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/dns-resolver/server/udp-\
                                                    and-tcp/address",
        "sid": "1750"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/dns-resolver/server/udp-\
                                                       and-tcp/port",
        "sid": "1751"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/hostname",
        "sid": "1752"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/location",
        "sid": "1753"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/ntp",
        "sid": "1754"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/ntp/enabled",
        "sid": "1755"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/ntp/server",
        "sid": "1756"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/ntp/server/association-\
                                                               type",
        "sid": "1757"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/ntp/server/iburst",
        "sid": "1758"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/ntp/server/name",
        "sid": "1759"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/ntp/server/prefer",
        "sid": "1760"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/ntp/server/udp",
        "sid": "1761"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/ntp/server/udp/address",
        "sid": "1762"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/ntp/server/udp/port",
        "sid": "1763"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/radius",
        "sid": "1764"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/radius/options",
        "sid": "1765"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/radius/options/attempts",
        "sid": "1766"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/radius/options/timeout",
        "sid": "1767"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/radius/server",
        "sid": "1768"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/radius/server/\
                                                authentication-type",
        "sid": "1769"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/radius/server/name",
        "sid": "1770"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/radius/server/udp",
        "sid": "1771"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/radius/server/udp/address\
                                                                   ",
        "sid": "1772"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/radius/server/udp/\
                                                authentication-port",
        "sid": "1773"
      },
      {
        "namespace": "data",
        "identifier": "/ietf-system:system/radius/server/udp/shared-\
                                                             secret",
        "sid": "1774"
      }
    ]
  }
}
]]></sourcecode>
      </figure>
    </section>
    <section anchor="sid-auto-generation">
      <name>SID auto generation</name>
      <t>Assignment Autogeneration</name>
      <t>The assignment of SIDs to YANG items <bcp14>SHOULD</bcp14> be automated.
The recommended process to assign SIDs is as follows:</t>
      <ol spacing="normal" type="1"><li>
          <t>A tool extracts the different items defined for a specific YANG module.</t>
        </li>
        <li>
          <t>The list of items is sorted in alphabetical order, order.  'namespace' entries are sorted in descending order, and 'identifier' entries are sorted in ascending order. The 'namespace' and 'identifier' formats are described in the YANG module 'ietf-sid-file' defined in <xref target="sid-file-format"/>.</t>
        </li>
        <li>
          <t>SIDs are assigned sequentially from the entry point up to the size of the registered SID range. This approach is recommended to minimize the serialization overhead, especially when the delta between a reference SID and the current SID is used by protocols aiming to reduce message size.</t>
        </li>
        <li>
          <t>If the number of items exceeds the SID range(s) allocated to a YANG module, an extra range is added for subsequent assignments.</t>
        </li>
        <li>
          <t>The "dependency-revision" 'dependency-revision' list item should reflect the revision numbers of each
YANG module that the YANG module imports at the moment of the file generation.</t>
        </li>
      </ol>
      <t>When updating a YANG module that is in active use, the existing SID assignments are maintained.
(In contrast, when evolving an early draft version of an Internet-Draft that has not yet been adopted by a community of developers, SID assignments are often better done from scratch after a revision.)
If the name of a schema node changes, changes but the data remain structurally and semantically similar to what was previously available under an old name, the SID that was used for the old name <bcp14>MAY</bcp14> continue to be used for the new name.
If the meaning of an item changes, a new SID <bcp14>MAY</bcp14> be assigned to it; this is particularly useful to allow for allowing the new SID to identify the new structure or semantics of the item.
If the YANG data type changes in a new revision of a published module, module
such that the resulting CBOR encoding is changed, then implementations will be aided significantly if a new SID is assigned.
Note that these decisions are generally at the discretion of the YANG module author, who should decide if the benefits of a manual intervention are worth the deviation from automatic assignment.</t>
      <t>In the case of an update to an existing ".sid" file, an additional step is needed
that increments the ".sid" file version number. If there was no version number
in the previous version of the ".sid" file, 0 is assumed as to be the version number
of the old version of the ".sid" file and the version number is 1 for the new
".sid" file. Apart from that, changes of to ".sid" files can also be automated using
the same method as that described above, except that in step #3, previous SID assignments are kept, only previously unassigned YÀNG YANG items are processed at
step #3. Already existing processed, and these are assigned previously unassigned SIDs. Already-existing items in the ".sid" file should not be given new SIDs.</t>
      <t>Note that ".sid" file versions are specific to a YANG module revision. For each
new YANG module or each new revision of an existing YANG module, the version
number of the initial ".sid" file should either (1)&nbsp;should be 0 or should (2)&nbsp;should not be present.</t>
      <t>Note also that RPC or action "input" and "output" YANG items <bcp14>MUST</bcp14> always be
assigned SID SIDs even if they don't contain further YANG items. The reason for this
requirement is that other modules can augment the given module and those SIDs
might be necessary.</t>
    </section>
    <section anchor="sid-lifecycle-ex">
      <name>".sid" file lifecycle</name> File Lifecycle</name>
      <t>Before assigning SIDs to their YANG modules, YANG module authors must acquire a
SID range from a "YANG SID Range Registry". registry of YANG-SID Ranges. If the YANG module is part of an IETF
draft
Internet-Draft or RFC, the SID range need needs to be acquired from the "IETF YANG SID Range
Registry" YANG-SID Ranges"
registry as defined in <xref target="ietf-iana-sid-range-allocation"/>. For the other YANG
modules, the authors can choose to acquire a SID range from any "YANG SID Range Registry" registry of
their choice.</t> YANG-SID Ranges.</t>
      <t>Once the SID range is acquired, owners can use it to generate one or more ".sid" file/s files for their YANG module/s. module or modules.  It is recommended to leave some unallocated SIDs
following the allocated range in each ".sid" file in order to allow better
evolution of the owners' YANG module modules in the future.  Generation of ".sid" files should
be performed using an automated tool.  Note that ".sid" files can only be
generated for YANG modules and not for submodules.</t>
      <section anchor="sid-file-creation">
        <name>".sid" File Creation</name>
        <t>The following activity diagram summarizes the creation of a YANG module and its associated ".sid" file.</t>
        <figure anchor="fig-sid-file-creation">
          <name>SID Lifecycle</name>
          <artset>
<!-- height="832" width="504" -->
            <artwork type="svg" align="left"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="832" width="504" viewBox="0 class='diagram' font-family='monospace' font-size='13px' text-anchor='middle' version='1.1' viewBox='0 0 504 832" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px"> 832' xmlns='http://www.w3.org/2000/svg'>
<path d="M d='M 8,240 L 8,336" fill="none" stroke="black"/> 8,336' fill='none' stroke='black'/>
<path d="M d='M 16,48 L 16,64" fill="none" stroke="black"/> 16,64' fill='none' stroke='black'/>
<path d="M d='M 48,320 L 48,368" fill="none" stroke="black"/> 48,368' fill='none' stroke='black'/>
<path d="M d='M 64,32 L 64,80" fill="none" stroke="black"/> 64,80' fill='none' stroke='black'/>
<path d="M d='M 104,272 L 104,312" fill="none" stroke="black"/> 104,312' fill='none' stroke='black'/>
<path d="M d='M 112,176 L 112,216" fill="none" stroke="black"/> 112,216' fill='none' stroke='black'/>
<path d="M d='M 120,80 L 120,120" fill="none" stroke="black"/> 120,120' fill='none' stroke='black'/>
<path d="M d='M 168,704 L 168,752" fill="none" stroke="black"/> 168,752' fill='none' stroke='black'/>
<path d="M d='M 176,320 L 176,368" fill="none" stroke="black"/> 176,368' fill='none' stroke='black'/>
<path d="M d='M 192,32 L 192,80" fill="none" stroke="black"/> 192,80' fill='none' stroke='black'/>
<path d="M d='M 208,416 L 208,464" fill="none" stroke="black"/> 208,464' fill='none' stroke='black'/>
<path d="M d='M 216,320 L 216,368" fill="none" stroke="black"/> 216,368' fill='none' stroke='black'/>
<path d="M d='M 224,224 L 224,272" fill="none" stroke="black"/> 224,272' fill='none' stroke='black'/>
<path d="M d='M 232,752 L 232,800" fill="none" stroke="black"/> 232,800' fill='none' stroke='black'/>
<path d="M d='M 248,656 L 248,696" fill="none" stroke="black"/> 248,696' fill='none' stroke='black'/>
<path d="M d='M 264,560 L 264,600" fill="none" stroke="black"/> 264,600' fill='none' stroke='black'/>
<path d="M d='M 272,464 L 272,504" fill="none" stroke="black"/> 272,504' fill='none' stroke='black'/>
<path d="M d='M 280,272 L 280,312" fill="none" stroke="black"/> 280,312' fill='none' stroke='black'/>
<path d="M d='M 280,368 L 280,408" fill="none" stroke="black"/> 280,408' fill='none' stroke='black'/>
<path d="M d='M 288,160 L 288,216" fill="none" stroke="black"/> 288,216' fill='none' stroke='black'/>
<path d="M d='M 296,704 L 296,752" fill="none" stroke="black"/> 296,752' fill='none' stroke='black'/>
<path d="M d='M 336,416 L 336,464" fill="none" stroke="black"/> 336,464' fill='none' stroke='black'/>
<path d="M d='M 344,320 L 344,368" fill="none" stroke="black"/> 344,368' fill='none' stroke='black'/>
<path d="M d='M 352,224 L 352,272" fill="none" stroke="black"/> 352,272' fill='none' stroke='black'/>
<path d="M d='M 368,704 L 368,752" fill="none" stroke="black"/> 368,752' fill='none' stroke='black'/>
<path d="M d='M 376,416 L 376,464" fill="none" stroke="black"/> 376,464' fill='none' stroke='black'/>
<path d="M d='M 432,256 L 432,416" fill="none" stroke="black"/> 432,416' fill='none' stroke='black'/>
<path d="M d='M 432,472 L 432,528" fill="none" stroke="black"/> 432,528' fill='none' stroke='black'/>
<path d="M d='M 432,640 L 432,696" fill="none" stroke="black"/> 432,696' fill='none' stroke='black'/>
<path d="M d='M 432,752 L 432,784" fill="none" stroke="black"/> 432,784' fill='none' stroke='black'/>
<path d="M d='M 488,416 L 488,464" fill="none" stroke="black"/> 488,464' fill='none' stroke='black'/>
<path d="M d='M 496,704 L 496,752" fill="none" stroke="black"/> 496,752' fill='none' stroke='black'/>
<path d="M d='M 64,32 L 192,32" fill="none" stroke="black"/> 192,32' fill='none' stroke='black'/>
<path d="M d='M 8,64 L 24,64" fill="none" stroke="black"/> 24,64' fill='none' stroke='black'/>
<path d="M d='M 40,64 L 56,64" fill="none" stroke="black"/> 56,64' fill='none' stroke='black'/>
<path d="M d='M 64,80 L 192,80" fill="none" stroke="black"/> 192,80' fill='none' stroke='black'/>
<path d="M d='M 64,128 L 176,128" fill="none" stroke="black"/> 176,128' fill='none' stroke='black'/>
<path d="M d='M 192,160 L 288,160" fill="none" stroke="black"/> 288,160' fill='none' stroke='black'/>
<path d="M d='M 64,176 L 176,176" fill="none" stroke="black"/> 176,176' fill='none' stroke='black'/>
<path d="M d='M 56,224 L 168,224" fill="none" stroke="black"/> 168,224' fill='none' stroke='black'/>
<path d="M d='M 224,224 L 352,224" fill="none" stroke="black"/> 352,224' fill='none' stroke='black'/>
<path d="M d='M 8,240 L 32,240" fill="none" stroke="black"/> 32,240' fill='none' stroke='black'/>
<path d="M d='M 184,256 L 216,256" fill="none" stroke="black"/> 216,256' fill='none' stroke='black'/>
<path d="M d='M 360,256 L 432,256" fill="none" stroke="black"/> 432,256' fill='none' stroke='black'/>
<path d="M d='M 56,272 L 168,272" fill="none" stroke="black"/> 168,272' fill='none' stroke='black'/>
<path d="M d='M 224,272 L 352,272" fill="none" stroke="black"/> 352,272' fill='none' stroke='black'/>
<path d="M d='M 48,320 L 176,320" fill="none" stroke="black"/> 176,320' fill='none' stroke='black'/>
<path d="M d='M 216,320 L 344,320" fill="none" stroke="black"/> 344,320' fill='none' stroke='black'/>
<path d="M d='M 8,336 L 48,336" fill="none" stroke="black"/> 48,336' fill='none' stroke='black'/>
<path d="M d='M 352,352 L 432,352" fill="none" stroke="black"/> 432,352' fill='none' stroke='black'/>
<path d="M d='M 48,368 L 176,368" fill="none" stroke="black"/> 176,368' fill='none' stroke='black'/>
<path d="M d='M 216,368 L 344,368" fill="none" stroke="black"/> 344,368' fill='none' stroke='black'/>
<path d="M d='M 208,416 L 336,416" fill="none" stroke="black"/> 336,416' fill='none' stroke='black'/>
<path d="M d='M 376,416 L 488,416" fill="none" stroke="black"/> 488,416' fill='none' stroke='black'/>
<path d="M d='M 208,464 L 336,464" fill="none" stroke="black"/> 336,464' fill='none' stroke='black'/>
<path d="M d='M 376,464 L 488,464" fill="none" stroke="black"/> 488,464' fill='none' stroke='black'/>
<path d="M d='M 224,512 L 312,512" fill="none" stroke="black"/> 312,512' fill='none' stroke='black'/>
<path d="M d='M 336,528 L 432,528" fill="none" stroke="black"/> 432,528' fill='none' stroke='black'/>
<path d="M d='M 224,560 L 312,560" fill="none" stroke="black"/> 312,560' fill='none' stroke='black'/>
<path d="M d='M 192,608 L 304,608" fill="none" stroke="black"/> 304,608' fill='none' stroke='black'/>
<path d="M d='M 320,640 L 432,640" fill="none" stroke="black"/> 432,640' fill='none' stroke='black'/>
<path d="M d='M 192,656 L 304,656" fill="none" stroke="black"/> 304,656' fill='none' stroke='black'/>
<path d="M d='M 168,704 L 296,704" fill="none" stroke="black"/> 296,704' fill='none' stroke='black'/>
<path d="M d='M 368,704 L 496,704" fill="none" stroke="black"/> 496,704' fill='none' stroke='black'/>
<path d="M d='M 168,752 L 296,752" fill="none" stroke="black"/> 296,752' fill='none' stroke='black'/>
<path d="M d='M 368,752 L 496,752" fill="none" stroke="black"/> 496,752' fill='none' stroke='black'/>
<path d="M d='M 232,784 L 432,784" fill="none" stroke="black"/> 432,784' fill='none' stroke='black'/>
<path d="M d='M 180,632 L 192,656" fill="none" stroke="black"/> 192,656' fill='none' stroke='black'/>
<path d="M d='M 44,248 L 56,272" fill="none" stroke="black"/> 56,272' fill='none' stroke='black'/>
<path d="M d='M 212,536 L 224,560" fill="none" stroke="black"/> 224,560' fill='none' stroke='black'/>
<path d="M d='M 52,152 L 64,176" fill="none" stroke="black"/> 64,176' fill='none' stroke='black'/>
<path d="M d='M 16,64 L 24,80" fill="none" stroke="black"/> 24,80' fill='none' stroke='black'/>
<path d="M d='M 304,608 L 316,632" fill="none" stroke="black"/> 316,632' fill='none' stroke='black'/>
<path d="M d='M 168,224 L 180,248" fill="none" stroke="black"/> 180,248' fill='none' stroke='black'/>
<path d="M d='M 312,512 L 324,536" fill="none" stroke="black"/> 324,536' fill='none' stroke='black'/>
<path d="M d='M 176,128 L 188,152" fill="none" stroke="black"/> 188,152' fill='none' stroke='black'/>
<path d="M d='M 8,80 L 16,64" fill="none" stroke="black"/> 16,64' fill='none' stroke='black'/>
<path d="M d='M 52,152 L 64,128" fill="none" stroke="black"/> 64,128' fill='none' stroke='black'/>
<path d="M d='M 44,248 L 56,224" fill="none" stroke="black"/> 56,224' fill='none' stroke='black'/>
<path d="M d='M 176,176 L 188,152" fill="none" stroke="black"/> 188,152' fill='none' stroke='black'/>
<path d="M d='M 168,272 L 180,248" fill="none" stroke="black"/> 180,248' fill='none' stroke='black'/>
<path d="M d='M 212,536 L 224,512" fill="none" stroke="black"/> 224,512' fill='none' stroke='black'/>
<path d="M d='M 180,632 L 192,608" fill="none" stroke="black"/> 192,608' fill='none' stroke='black'/>
<path d="M d='M 312,560 L 324,536" fill="none" stroke="black"/> 324,536' fill='none' stroke='black'/>
<path d="M d='M 304,656 L 316,632" fill="none" stroke="black"/> 316,632' fill='none' stroke='black'/>
<polygon class="arrowhead" points="440,696 class='arrowhead' fill='black' points='440,696 428,690.4 428,701.6 " fill="black" transform="rotate(90,432,696)"/> ' transform='rotate(90,432,696)'/>
<polygon class="arrowhead" points="440,472 class='arrowhead' fill='black' points='440,472 428,466.4 428,477.6 " fill="black" transform="rotate(270,432,472)"/> ' transform='rotate(270,432,472)'/>
<polygon class="arrowhead" points="368,256 class='arrowhead' fill='black' points='368,256 356,250.4 356,261.6 " fill="black" transform="rotate(180,360,256)"/> ' transform='rotate(180,360,256)'/>
<polygon class="arrowhead" points="360,352 class='arrowhead' fill='black' points='360,352 348,346.4 348,357.6 " fill="black" transform="rotate(180,352,352)"/> ' transform='rotate(180,352,352)'/>
<polygon class="arrowhead" points="296,216 class='arrowhead' fill='black' points='296,216 284,210.4 284,221.6 " fill="black" transform="rotate(90,288,216)"/> ' transform='rotate(90,288,216)'/>
<polygon class="arrowhead" points="288,408 class='arrowhead' fill='black' points='288,408 276,402.4 276,413.6 " fill="black" transform="rotate(90,280,408)"/> ' transform='rotate(90,280,408)'/>
<polygon class="arrowhead" points="288,312 class='arrowhead' fill='black' points='288,312 276,306.4 276,317.6 " fill="black" transform="rotate(90,280,312)"/> ' transform='rotate(90,280,312)'/>
<polygon class="arrowhead" points="280,504 class='arrowhead' fill='black' points='280,504 268,498.4 268,509.6 " fill="black" transform="rotate(90,272,504)"/> ' transform='rotate(90,272,504)'/>
<polygon class="arrowhead" points="272,600 class='arrowhead' fill='black' points='272,600 260,594.4 260,605.6 " fill="black" transform="rotate(90,264,600)"/> ' transform='rotate(90,264,600)'/>
<polygon class="arrowhead" points="256,696 class='arrowhead' fill='black' points='256,696 244,690.4 244,701.6 " fill="black" transform="rotate(90,248,696)"/> ' transform='rotate(90,248,696)'/>
<polygon class="arrowhead" points="240,800 class='arrowhead' fill='black' points='240,800 228,794.4 228,805.6 " fill="black" transform="rotate(90,232,800)"/> ' transform='rotate(90,232,800)'/>
<polygon class="arrowhead" points="224,256 class='arrowhead' fill='black' points='224,256 212,250.4 212,261.6 " fill="black" transform="rotate(0,216,256)"/> ' transform='rotate(0,216,256)'/>
<polygon class="arrowhead" points="128,120 class='arrowhead' fill='black' points='128,120 116,114.4 116,125.6 " fill="black" transform="rotate(90,120,120)"/> ' transform='rotate(90,120,120)'/>
<polygon class="arrowhead" points="120,216 class='arrowhead' fill='black' points='120,216 108,210.4 108,221.6 " fill="black" transform="rotate(90,112,216)"/> ' transform='rotate(90,112,216)'/>
<polygon class="arrowhead" points="112,312 class='arrowhead' fill='black' points='112,312 100,306.4 100,317.6 " fill="black" transform="rotate(90,104,312)"/> ' transform='rotate(90,104,312)'/>
<polygon class="arrowhead" points="64,64 class='arrowhead' fill='black' points='64,64 52,58.4 52,69.6 " fill="black" transform="rotate(0,56,64)"/> ' transform='rotate(0,56,64)'/>
<polygon class="arrowhead" points="40,240 class='arrowhead' fill='black' points='40,240 28,234.4 28,245.6 " fill="black" transform="rotate(0,32,240)"/> ' transform='rotate(0,32,240)'/>
<circle cx="16" cy="48" r="6" class="opendot" fill="white" stroke="black"/> class='opendot' cx='16' cy='48' fill='white' r='6' stroke='black'/>
<g class="text">
                  <text x="108" y="52">Creation</text>
                  <text x="156" y="52">of</text>
                  <text x="176" y="52">a</text>
                  <text x="92" y="68">YANG</text> class='text'>
<text x="140" y="68">module</text> x='108' y='52'>Creation</text>
<text x="116" y="148">Standardized</text> x='156' y='52'>of</text>
<text x="240" y="148">yes</text> x='176' y='52'>a</text>
<text x="84" y="164">YANG</text> x='92' y='68'>YANG</text>
<text x="132" y="164">module</text> x='140' y='68'>module</text>
<text x="168" y="164">?</text> x='116' y='148'>Standardized</text>
<text x="140" y="196">no</text> x='240' y='148'>yes</text>
<text x="104" y="244">Constrained</text> x='84' y='164'>YANG</text>
<text x="200" y="244">yes</text> x='136' y='164'>module?</text>
<text x="248" y="244">SID</text> x='140' y='196'>no</text>
<text x="288" y="244">range</text> x='104' y='244'>Constrained</text>
<text x="104" y="260">application</text> x='200' y='244'>yes</text>
<text x="160" y="260">?</text> x='248' y='244'>SID</text>
<text x="284" y="260">registration</text> x='288' y='244'>range</text>
<text x="132" y="292">no</text> x='108' y='260'>application?</text>
<text x="76" y="340">YANG</text> x='284' y='260'>registration</text>
<text x="124" y="340">module</text> x='132' y='292'>no</text>
<text x="240" y="340">SID</text> x='76' y='340'>YANG</text>
<text x="296" y="340">sub-range</text> x='124' y='340'>module</text>
<text x="84" y="356">update</text> x='240' y='340'>SID</text>
<text x="268" y="356">assignment</text> x='292' y='340'>subrange</text>
<text x="244" y="436">".sid"</text> x='84' y='356'>update</text>
<text x="292" y="436">file</text> x='268' y='356'>assignment</text>
<text x="412" y="436">Rework</text> x='244' y='436'>&quot;.sid&quot;</text>
<text x="460" y="436">YANG</text> x='292' y='436'>file</text>
<text x="260" y="452">generation</text> x='412' y='436'>Rework</text>
<text x="436" y="452">module</text> x='460' y='436'>YANG</text>
<text x="344" y="516">yes</text> x='260' y='452'>generation</text>
<text x="252" y="532">Work</text> x='436' y='452'>module</text>
<text x="284" y="532">in</text> x='344' y='516'>yes</text>
<text x="268" y="548">progress</text> x='268' y='532'>Work-in-</text>
<text x="292" y="580">no</text> x='272' y='548'>progress?</text>
<text x="248" y="628">RFC</text> x='292' y='580'>no</text>
<text x="332" y="628">no</text> x='248' y='628'>RFC</text>
<text x="252" y="644">publication?</text> x='332' y='628'>no</text>
<text x="216" y="676">yes</text> x='252' y='644'>publication?</text>
<text x="228" y="724">IANA</text> x='216' y='676'>yes</text>
<text x="400" y="724">Third</text> x='228' y='724'>IANA</text>
<text x="448" y="724">party</text> x='424' y='724'>Third-party</text>
<text x="228" y="740">registration</text> x='228' y='740'>registration</text>
<text x="428" y="740">registration</text> x='428' y='740'>registration</text>
<text x="236" y="820">[DONE]</text> x='236' y='820'>[DONE]</text>
</g>
</svg>
            </artwork>
            <artwork type="ascii-art"><![CDATA[
       +---------------+
 o     | Creation of a |
-+- -->| YANG module   |
/ \    +------+--------+
              |
              v
       .-------------.
      / Standardized  \     yes
      \ YANG module ? module?  /------------+
       '-----+-------'             |
             |  no                 |
             v                     v
      .-------------.      +---------------+
+--> / Constrained   \ yes | SID range     |
|    \ application ? application?  /---->| registration  |<--------+
|     '-----+-------'      +------+--------+         |
|           |  no                 |                  |
|           v                     v                  |
|    +---------------+    +---------------+          |
+----+ YANG module   |    | SID sub-range subrange  |          |
     | update        |    | assignment    |<---------+
     +---------------+    +-------+-------+          |
                                  |                  |
                                  v                  |
                         +---------------+    +------+------+
                         | ".sid" file   |    | Rework YANG |
                         | generation    |    |    module   |
                         +-------+-------+    +-------------+
                                 |                   ^
                                 v                   |
                           .----------.  yes         |
                          /  Work in  Work-in-  \ ------------+
                          \  progress  progress? /
                           '----+-----'
                                |  no
                                v
                       .-------------.
                      /      RFC      \ no
                      \  publication? /--------------+
                       '------+------'               |
                         yes  |                      |
                              v                      v
                    +---------------+        +---------------+
                    |     IANA      |        | Third party Third-party   |
                    | registration  |        | registration  |
                    +-------+-------+        +-------+-------+
                            |                        |
                            +------------------------+
                            v
                          [DONE]
]]></artwork>
          </artset>
        </figure>
      </section>
      <section anchor="sid-file-update">
        <name>".sid" File Update</name>
        <t>The following Activity activity diagram summarizes the update of a YANG module and its associated ".sid" file.</t>
        <figure anchor="fig-sid-file-update">
          <name>YANG and ".sid" file update</name> File Update</name>
          <artset>
<!-- height="656" width="520" -->
<artwork type="svg" align="left"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="672" width="520" viewBox="0 class='diagram' font-family='monospace' font-size='13px' text-anchor='middle' version='1.1' viewBox='0 0 520 672" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px"> 656'  xmlns='http://www.w3.org/2000/svg'>
<path d="M d='M 16,48 L 16,64" fill="none" stroke="black"/> 16,64' fill='none' stroke='black'/>
<path d="M d='M 64,32 L 64,112" fill="none" stroke="black"/> 64,112' fill='none' stroke='black'/>
<path d="M d='M 120,112 L 120,152" fill="none" stroke="black"/> 120,152' fill='none' stroke='black'/>
<path d="M d='M 144,208 L 144,576" fill="none" stroke="black"/> 144,576' fill='none' stroke='black'/>
<path d="M 192,32 L 192,112" fill="none" stroke="black"/>
                <path d="M d='M 200,368 L 200,448" fill="none" stroke="black"/> 200,448' fill='none' stroke='black'/>
<path d='M 232,32 L 232,112' fill='none' stroke='black'/>
<path d="M d='M 264,192 L 264,232" fill="none" stroke="black"/> 264,232' fill='none' stroke='black'/>
<path d="M d='M 264,288 L 264,360" fill="none" stroke="black"/> 264,360' fill='none' stroke='black'/>
<path d="M d='M 264,448 L 264,488" fill="none" stroke="black"/> 264,488' fill='none' stroke='black'/>
<path d="M d='M 264,544 L 264,608" fill="none" stroke="black"/> 264,608' fill='none' stroke='black'/>
<path d="M d='M 328,368 L 328,448" fill="none" stroke="black"/> 328,448' fill='none' stroke='black'/>
<path d="M d='M 376,240 L 376,288" fill="none" stroke="black"/> 376,288' fill='none' stroke='black'/>
<path d="M d='M 376,496 L 376,544" fill="none" stroke="black"/> 376,544' fill='none' stroke='black'/>
<path d="M d='M 440,288 L 440,320" fill="none" stroke="black"/> 440,320' fill='none' stroke='black'/>
<path d="M d='M 440,544 L 440,576" fill="none" stroke="black"/> 440,576' fill='none' stroke='black'/>
<path d="M d='M 504,496 L 504,544" fill="none" stroke="black"/> 504,544' fill='none' stroke='black'/>
<path d="M d='M 512,240 L 512,288" fill="none" stroke="black"/> 512,288' fill='none' stroke='black'/>
<path d="M d='M 64,32 L 192,32" fill="none" stroke="black"/> 232,32' fill='none' stroke='black'/>
<path d="M d='M 8,64 L 24,64" fill="none" stroke="black"/> 24,64' fill='none' stroke='black'/>
<path d="M d='M 40,64 L 56,64" fill="none" stroke="black"/> 56,64' fill='none' stroke='black'/>
<path d="M d='M 64,112 L 192,112" fill="none" stroke="black"/> 232,112' fill='none' stroke='black'/>
<path d="M d='M 88,160 L 200,160" fill="none" stroke="black"/> 200,160' fill='none' stroke='black'/>
<path d="M d='M 216,192 L 264,192" fill="none" stroke="black"/> 264,192' fill='none' stroke='black'/>
<path d="M d='M 88,208 L 200,208" fill="none" stroke="black"/> 200,208' fill='none' stroke='black'/>
<path d="M d='M 208,240 L 320,240" fill="none" stroke="black"/> 320,240' fill='none' stroke='black'/>
<path d="M d='M 376,240 L 512,240" fill="none" stroke="black"/> 512,240' fill='none' stroke='black'/>
<path d="M d='M 336,272 L 368,272" fill="none" stroke="black"/> 368,272' fill='none' stroke='black'/>
<path d="M d='M 208,288 L 320,288" fill="none" stroke="black"/> 320,288' fill='none' stroke='black'/>
<path d="M d='M 376,288 L 512,288" fill="none" stroke="black"/> 512,288' fill='none' stroke='black'/>
<path d="M d='M 264,320 L 440,320" fill="none" stroke="black"/> 440,320' fill='none' stroke='black'/>
<path d="M d='M 200,368 L 328,368" fill="none" stroke="black"/> 328,368' fill='none' stroke='black'/>
<path d="M d='M 200,448 L 328,448" fill="none" stroke="black"/> 328,448' fill='none' stroke='black'/>
<path d="M d='M 208,496 L 320,496" fill="none" stroke="black"/> 320,496' fill='none' stroke='black'/>
<path d="M d='M 376,496 L 504,496" fill="none" stroke="black"/> 504,496' fill='none' stroke='black'/>
<path d="M d='M 336,528 L 368,528" fill="none" stroke="black"/> 368,528' fill='none' stroke='black'/>
<path d="M d='M 208,544 L 320,544" fill="none" stroke="black"/> 320,544' fill='none' stroke='black'/>
<path d="M d='M 376,544 L 504,544" fill="none" stroke="black"/> 504,544' fill='none' stroke='black'/>
<path d="M d='M 144,576 L 440,576" fill="none" stroke="black"/> 440,576' fill='none' stroke='black'/>
<path d="M d='M 196,520 L 208,544" fill="none" stroke="black"/> 208,544' fill='none' stroke='black'/>
<path d="M d='M 16,64 L 24,80" fill="none" stroke="black"/> 24,80' fill='none' stroke='black'/>
<path d="M d='M 76,184 L 88,208" fill="none" stroke="black"/> 88,208' fill='none' stroke='black'/>
<path d="M d='M 196,264 L 208,288" fill="none" stroke="black"/> 208,288' fill='none' stroke='black'/>
<path d="M d='M 320,496 L 332,520" fill="none" stroke="black"/> 332,520' fill='none' stroke='black'/>
<path d="M d='M 200,160 L 212,184" fill="none" stroke="black"/> 212,184' fill='none' stroke='black'/>
<path d="M d='M 320,240 L 332,264" fill="none" stroke="black"/> 332,264' fill='none' stroke='black'/>
<path d="M d='M 8,80 L 16,64" fill="none" stroke="black"/> 16,64' fill='none' stroke='black'/>
<path d="M d='M 76,184 L 88,160" fill="none" stroke="black"/> 88,160' fill='none' stroke='black'/>
<path d="M d='M 200,208 L 212,184" fill="none" stroke="black"/> 212,184' fill='none' stroke='black'/>
<path d="M d='M 196,264 L 208,240" fill="none" stroke="black"/> 208,240' fill='none' stroke='black'/>
<path d="M d='M 196,520 L 208,496" fill="none" stroke="black"/> 208,496' fill='none' stroke='black'/>
<path d="M d='M 320,288 L 332,264" fill="none" stroke="black"/> 332,264' fill='none' stroke='black'/>
<path d="M d='M 320,544 L 332,520" fill="none" stroke="black"/> 332,520' fill='none' stroke='black'/>
<polygon class="arrowhead" points="376,528 class='arrowhead' fill='black' points='376,528 364,522.4 364,533.6 " fill="black" transform="rotate(0,368,528)"/> ' transform='rotate(0,368,528)'/>
<polygon class="arrowhead" points="376,272 class='arrowhead' fill='black' points='376,272 364,266.4 364,277.6 " fill="black" transform="rotate(0,368,272)"/> ' transform='rotate(0,368,272)'/>
<polygon class="arrowhead" points="272,608 class='arrowhead' fill='black' points='272,608 260,602.4 260,613.6 " fill="black" transform="rotate(90,264,608)"/> ' transform='rotate(90,264,608)'/>
<polygon class="arrowhead" points="272,488 class='arrowhead' fill='black' points='272,488 260,482.4 260,493.6 " fill="black" transform="rotate(90,264,488)"/> ' transform='rotate(90,264,488)'/>
<polygon class="arrowhead" points="272,360 class='arrowhead' fill='black' points='272,360 260,354.4 260,365.6 " fill="black" transform="rotate(90,264,360)"/> ' transform='rotate(90,264,360)'/>
<polygon class="arrowhead" points="272,232 class='arrowhead' fill='black' points='272,232 260,226.4 260,237.6 " fill="black" transform="rotate(90,264,232)"/> ' transform='rotate(90,264,232)'/>
<polygon class="arrowhead" points="128,152 class='arrowhead' fill='black' points='128,152 116,146.4 116,157.6 " fill="black" transform="rotate(90,120,152)"/> ' transform='rotate(90,120,152)'/>
<polygon class="arrowhead" points="64,64 class='arrowhead' fill='black' points='64,64 52,58.4 52,69.6 " fill="black" transform="rotate(0,56,64)"/> ' transform='rotate(0,56,64)'/>
<circle cx="16" cy="48" r="6" class="opendot" fill="white" stroke="black"/> class='opendot' cx='16' cy='48' fill='white' r='6' stroke='black'/>
<g class="text">
                  <text x="100" y="52">Update</text>
                  <text x="140" y="52">of</text> class='text'>
<text x="168" y="52">the</text> x='100' y='52'>Update</text>
<text x="92" y="68">YANG</text> x='140' y='52'>of</text>
<text x="140" y="68">module</text> x='168' y='52'>the</text>
<text x="84" y="84">or</text> x='92' y='68'>YANG</text>
<text x="140" y="84">include(s)</text> x='144' y='68'>module,</text>
<text x="84" y="100">or</text> x='192' y='68'>its</text>
<text x="136" y="100">import(s)</text> x='120' y='84'>include(s),</text>
<text x="112" y="180">New</text> x='180' y='84'>or</text>
<text x="152" y="180">items</text> x='208' y='84'>its</text>
<text x="232" y="180">yes</text> x='112' y='100'>import(s)</text>
<text x="128" y="196">created</text> x='112' y='180'>New</text>
<text x="176" y="196">?</text> x='152' y='180'>items</text>
<text x="172" y="228">no</text> x='232' y='180'>yes</text>
<text x="232" y="260">SID</text> x='132' y='196'>created?</text>
<text x="272" y="260">range</text> x='172' y='228'>no</text>
<text x="352" y="260">yes</text> x='232' y='260'>SID</text>
<text x="408" y="260">Extra</text> x='272' y='260'>range</text>
<text x="472" y="260">sub-range</text> x='352' y='260'>yes</text>
<text x="256" y="276">exhausted</text> x='408' y='260'>Extra</text>
<text x="304" y="276">?</text> x='468' y='260'>subrange</text>
<text x="428" y="276">assignment</text> x='260' y='276'>exhausted?</text>
<text x="292" y="308">no</text> x='428' y='276'>assignment</text>
<text x="236" y="388">".sid"</text> x='292' y='308'>no</text>
<text x="284" y="388">file</text> x='236' y='388'>&quot;.sid&quot;</text>
<text x="236" y="404">update</text> x='284' y='388'>file</text>
<text x="288" y="404">based</text> x='236' y='404'>update</text>
<text x="220" y="420">on</text> x='288' y='404'>based</text>
<text x="268" y="420">previous</text> x='220' y='420'>on</text>
<text x="236" y="436">".sid"</text> x='268' y='420'>previous</text>
<text x="284" y="436">file</text> x='236' y='436'>&quot;.sid&quot;</text>
<text x="252" y="516">Publicly</text> x='284' y='436'>file</text>
<text x="352" y="516">yes</text> x='252' y='516'>Publicly</text>
<text x="404" y="516">YANG</text> x='352' y='516'>yes</text>
<text x="452" y="516">module</text> x='404' y='516'>YANG</text>
<text x="256" y="532">available</text> x='452' y='516'>module</text>
<text x="304" y="532">?</text> x='260' y='532'>available?</text>
<text x="436" y="532">registration</text> x='436' y='532'>registration</text>
<text x="284" y="564">no</text> x='284' y='564'>no</text>
<text x="268" y="628">[DONE]</text> x='268' y='628'>[DONE]</text>
</g>
</svg>
            </artwork>
            <artwork type="ascii-art"><![CDATA[
        +---------------+
        +--------------------+
  o     | Update of the      |
 -+- -->| YANG module module, its   |
 / \    | include(s), or include(s) its |
        | or import(s)          |
        +------+--------+
        +------+-------------+
               |
               v
           .-------------.
          /  New items    \ yes
          \  created  ?  created?     /------+
           '------+------'       |
                  |  no          v
                  |       .-------------.      +----------------+
                  |      /  SID range    \ yes | Extra sub-range| subrange |
                  |      \  exhausted ?  exhausted?   /---->| assignment     |
                  |       '------+------'      +-------+--------+
                  |              |  no                 |
                  |              +---------------------+
                  |              |
                  |              v
                  |      +---------------+
                  |      | ".sid" file   |
                  |      | update based  |
                  |      | on previous   |
                  |      | ".sid" file   |
                  |      +-------+-------+
                  |              |
                  |              v
                  |       .-------------.      +---------------+
                  |      /  Publicly     \ yes | YANG module   |
                  |      \  available ?  available?   /---->| registration  |
                  |       '------+------'      +-------+-------+
                  |              | no                  |
                  +--------------+---------------------+
                                 |
                                 v
                               [DONE]
]]></artwork>
          </artset>
        </figure>
      </section>
    </section>
    <section anchor="keeping-a-sid-file-in-a-yang-instance-data-file">
      <name>Keeping a SID &quot;.sid&quot; File in a YANG Instance Data file</name> File</name>
      <t><xref target="RFC9195"/> defines a format for "YANG Instance Data". instance data".
This essentially leads to an encapsulation of the instance data within
some metadata envelope.</t>
      <t>If a SID ".sid" file needs to be stored in a YANG Instance Data instance data file, this
can be achieved by embedding the value of the SID ".sid" file as the value of the
<tt>content-data</tt> member in the following template, template and copying over the
second-level members as indicated with the angle brackets:</t>

      <sourcecode type="yang-instance-data"><![CDATA[ type="yang-instance-data+json"><![CDATA[
{
  "ietf-yang-instance-data:instance-data-set": {
    "name": "<module-name>@<module-revision>.sid",
    "description":  ["<description>"],
    "content-schema": {
      "module": "ietf-sid-file@2023-10-27" "ietf-sid-file@2024-06-17"
    },
    "content-data": {  <replace this object>
      "ietf-sid-file:sid-file" : {
        "module-name": ...
      }
    }
  }
}
]]></sourcecode>
      <t><cref anchor="rfced">RFC editor: Please replace the module date by the correct
one for the ietf-sid-file module.</cref></t>
    </section>
    <section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>The authors would like to thank <contact fullname="Andy Bierman"/>,
<contact fullname="Abhinav Somaraju"/>, <contact fullname="Peter van der Stok"/>, <contact fullname="Laurent Toutain"/> Toutain"/>, and
<contact fullname="Randy Turner"/> for their help during the development of this document and
their useful comments during the review process.
Special thanks go to the IESG members who supplied very useful
comments during the IESG processing phase, in particular to
<contact fullname="Benjamin Kaduk"/> and <contact fullname="Rob Wilton"/>, and to <contact fullname="Francesca Palombini"/> as
responsible AD.</t>
    </section>
    <section anchor="contributors" numbered="false" toc="include" removeInRFC="false">
      <name>Contributors</name>
      <contact initials="A." surname="Bierman" fullname="Andy Bierman">
        <organization>YumaWorks</organization>
        <address>
          <postal>
            <street>685 Cochran St.</street>
            <street>Suite #160</street>
            <city>Simi Valley</city>
            <region>CA</region>
            <code>93065</code>
            <country>USA</country>
            <country>United States of America</country>
          </postal>
          <email>andy@yumaworks.com</email>
        </address>
      </contact>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA7296XYbR5og+j+fIho6MwRlACTBRRJlu0wtdrNH20h0u922
qyYBJMgsAZmozAQpWOI98w73Bfrcc5+k+03uk9xvjSWRCVK2ODxVFglkRnwR
8cW3L/1+PyqrOJv8LZ7lWXJsqmKZROmioN/Kari7+2h3GE3ycRbP4etJEU+r
fppU0/44L5J+mU76s7hKyiqq0moGT/x88uoH8258kcxjc1olc5M+S7IqnaZJ
Ybr85emz7SgukvjYnCwWs3QcV2melQagMG+TeNY/S+eJOYEHTDcuqu3o6vzY
nGZVUmRJZZ5n52mWJEWanZuzuHxvvs+LcRK9vzo2T5+8fhvBaMemrCbRGMZM
snJZyqLK5WieliVMVa0WAOjp87Pvo0V6HBl4vEjH8NrWKim34O8qHwd/TJJF
dQGfHODf5WpeJNPSPVDmRRV+Ms7ni9gfEOZ2n2X5VhRdJtkywbnPi3y5ANgB
2qqIYWmwCc/fnU2XM1jqZVrk2Rz2r4Qn53E6Oza47d/hAQzy4hzfT6uL5Yg/
71+d76zi7Lw/HuVFFMXL6iIvjqO+KXI8mmSSVvC5MWkGwL4cmH+F/yXpbJZU
VQIf8xG/TOHwZsEXMNOxOSvggzTOKvMqqa7y4n0JhzIe8PYlCazsaG/XvF0m
ZrI0L5YfkvkoXxKI43wC4/7L8F/M8F+H+HdarY7ND0WcjVbwZ5Gcw6Ecm/+5
TEbJmJ5fZlUBjzyNs3gSwyeLC0LOzld7B4e7+w8Odw8PjzrwecJ7MieQB5cK
8neVwjqAbW9Z/8nAvElm+aVd+Mks+QA4CHiqn9O6T1+emZNqBoOl/4DFeesd
mgJXm5hZbJ5e/Nf/U8XpeZbAIdJTvOqt/cPDvd0tu+qnSVnmWf9dconPeqt/
UiRVzB/Z9X8PWzRO3DpjhXCwQAi/S+dVP7agDabF+lJ5aaeX8WqWw7qqwi3s
hzw/nyXm3VVa/Z4UM7x+P8xH/+wt8AnMPylhb7P3CWJnWSZmb2/XLu7h7q47
z39fwiW68FZkP7Dr8aZyi0oJtgWB9t05wSSnxrA/jYuySjLzJC/mcZYp9D9m
6WVSlGn1X/9vhZsHt8Sc/fupB/2bvKym8fjC7O/vHhzsWkCf9YcP9w8fyUs+
fD8kOMXKR7iDR/2D4V5/uPewf7T/aLjnYd04HuXfVb+ndBEtuHh9Yrg/b/Hf
YgKHrRC/w6ObwQTmXT6troACmp/wGnl4PC6+wqv9XamPDsZxw4VA2gYoPlpW
fL0Ff7PJyjxJaQ0658/LeayTyL7Ab31z9PAQSM74okBoqgF9tvVumVaJubd3
5OHru3Semn+N4V75V/XpiUPwR/u7R4dbPpQ/vjvxcBag+m4FYBDJoJONogzP
soIDRGjefv90/+jhQ/n16NGjPfz1ydM3e7u7x/jRg73hLn/54NEhfIQkzv69
x3/3/847DR8+3D2Ah4qx/DU8fHRsvG8fwPim/BCl2bQGxdHucFd/HR7sya8P
hsMD9+tDpLSWVMvH+3sP5ImHe8Mj/XXfDgG/7rtfD+yvR/bZg90HcGkv89ll
sj7mg0fDYzMCfvgePjjtPxs4/gvbmSJE83TtK9qVWToqYjwT/y//0ThL53Hf
W1L/Ml/CjS+CdeqHDNCj4eGBjEiMxtDvwHhBhjhHoAGbjv3P6KMqLs7xWl5U
1aI83tnxvhdWBs94MsRT790JiBjHZhrPStyeN/j9ceOgzA0Ry3bmo78fHB09
3FkIutjRTzKTfACKUqYjIH8012U8S2GOvCAhBBYOpAXkDWAUZrECJprR+8pP
Df3YCw8yCjz35O+A37MlUbY6wLjbIyZf/WpYFed9oOHJtJ9OQKKS34CC9Psm
HuGWj6so2iBHlZ4gZZCMnM/yEVzRlVlmxKOO9vujtIK/SmQyE1hGlZzje8sS
/qpyk05orBWvHm79vOyZGEQwMwfUUfnFzBNYcNsLprqIKyCCmRklPDDcJ5NM
p+k4TbLxirYSNsZDI5N4Eo3pAioZvFLbg+jsIi0NSJlL/Ar2ZAqP4wyJKWED
YOoxAIh/IgXC4VBk7NEUwJVglfTeosjHwF/hzXxqdItKggulPZCgsvgcwKCv
5vlkOUtKmDsHuGLEBZwgnS9myBcqmgIHgk+B79mxEQ4fWDjj3EIcm2kKAzFl
sdu9QEZVVgTuYjmapeWFgK3AIJwDIIzRL38Fcbxalr95vzLGnV0gEAAKzEmc
D6Dr/n//+/8eHmwbgAfPGJgGzRdPJvBgKRsGdDhDafn0+bsf8Ghp9weMb/N0
MpklUXQPBewCdmSMq46idzmI4Lx2OW1eIZ0oQfzxo9Dj62uY4x/LtOD9gzXj
i3EkuCiYA2g7iE4BV/LqQgVIFHqn6fmST9O8KXKQtfOZ6b56fvb09avvt3kS
pMUwCakHIBnjN/wFEvrr654ckJuopEthDxKAXpa4AXhf+bzhsuRXLccNVxev
AfDf9UXX0HkCUhwghewFYLKA6T+TibDc+7zLBScquzqR26HvuXX24PYBY55s
1LkA9xXDTBf+KHHFK/oTVlNDZYD9CqQ92hmUMYBOIiTjWRIX2z38FW52PrE7
GreRGoQZ5GIQHmRjYZmtVIlOo+S7Cs8BOYGLmi6WqFhOeNOSuEwBahhoAZ/i
9RL6M0/PLyoDSJUUV2mJovj4vTk6CGeKC2ALsN/pWODKSyIRscFVwH3Fp+Fv
kIbOE1xlllcG34UtHKPGcw5CAu9Kmf5uL4a7WiWcTAJXCgef5rgc/JRPknBR
z0w3Dtd6HEX35ZsqTUr8i3Avgw0G6vgqRxaSZuPZcoKvALbA+vhLxcvRCgEB
8rBVjI+JIeMIW4CQ/WIsyLhVfjgGbISbvSwS+qr8AF8JCwRMHWzj1LAYmJDJ
3GSJeArHgkT6zdNyWwltPk7pTNJssay68nm+rPgvHCYeO2X+Vi/AVtMut7wm
MhrSpPsB3aZHp0mMq4K9OyVEXcDBpkzJATdKJGILoSolU6YMsChGfbxMKj1H
S4rxVHpIvCPQs5Aw0B/eEHgjQVbAuwKIKmQqoFKz9H2Ce4wiGfyJpwOUICsX
eeFIjLcOxnrGYuSjWZYgmwEpbWBeI1a72SN+KkuYyMPTzLRyY2fg++ztGi9A
VuMNVSR8ueDlSVqOc2AoK9iVMfKlwBZBoL5kUF+w+IjL88XJ62vAfFpGkyyi
t3xgzEnAvU25KolWiVgC1CgvUPuu8uh8GcOSqoRYSlrIWMBgYRg7Ew8G4hO9
O5rl4/elUsQO0je6zmVnEL0GLZqIcjqhxzvAWGHrOj03mMWBBelPcMKzFTAs
psXCGvnCwQVNrmDyy7SU44xplyI5UBptIpy4IipYEqrxXDOQ40FP0/mEuCMV
hnNYlrITRPQmSQUqFP758WM++nsyRl2lpO0+cUKPjgyzhfxjWS7pIEBszed0
2nEZBbN8/Ij2O/y+f56g5QLPBTnq1UWKqECSjbxQ8nUax/BrBEyiICoNM9AJ
F5dIxvAGz+MVoeYCkG1R4DUGcHmiWTpNxitgJnAx4NvLFEmZt1LYnRHQhjU5
T2UvvTqRTwI8akFClLlZnCPeSsOvegIaSm19vjUAnJPmyDYKanyjWFdWCLsn
1EUixrUKm0yX9AYj3wPCJzQAyRNCfHry6gSEg/EF8MByDqwlGTPnqLPrQRQM
PQbEqhhFcyYcqJgkZTCN3AnhQnY6eQR3yM5cmss0Ni+T87j/ll/qlgnStjl+
ROP0dRuvr7cfmytgsilzSfeWN3RPWFgNOtjCaZEQHZvHQDyXC7n0+ZUHDeL8
PAeY+e0lCeJOxMdRaMQxSA0FUp8yQRMqDJqPALcyEEhVgCIRBpc/Fdmoj4Zj
S9VQpcU7dsKIWKUsCV+BDAEvoRhX5SCk4svuZnUGgEUdxhJ3leAWRvElYDah
I1BWBFG5Tr5Isn6ZL4sxEWa83qzZAiT0L130e/fMGVCkNMtBF2adCgQD4Ygo
brxPVgYEzElpOi9/fHcGNI3+Na9e0+9vn//PH0/fPn+Gv7/755MXL+wvkTzx
7p9f//jimfvNvfn09cuXz18945fhUxN8FHVenvzcYR2s8/rN2enrVycvOg1C
ZZEIuyJCASqMkqKkHBfpiDH7ydM3//kfewew9n8CZjrc23sE95D/eLj34AD+
QMGUZyMmzn/CRq4ioDUgn+IogGxAoRYgdM5YoS0vEIuQWsFe3v8Fd+a3Y/P1
aLzYO/hWPsAFBx/qngUf0p6tf7L2Mm9iw0cN09jdDD6v7XQI78nPwd+6796H
X/9lBsTL9Pce/uXbqC6SwgGISOqpNp4qd+xkOPhFxCv4jYlMTVyDP0E6hP+W
rHqgbOr+Qmsj/rUcycvM6YSeCbUhFoPXvlTFsVqDV3CfxWVgbscoSXhTIlKo
HL1iNQvn66HqE+sa7Hod5VPqmczwkxnc/SUQ7IEVNG9yYplAm9pGkzTzdPIw
kNSzbnCZpNMpYCPcC49Zd8fTAZzCu4Q23uwPhrgTYmkD2upgekUmpzPUy9Bp
BXDfagaAaG2O/bU57pnXVspgxEG5sEiJWFoBRA8Jd8CzveDFbBHvQKBDR5wV
DpkQAP0r4lE6g0PDIZ2QTTwygX3NV0zcVTKMYJlovwBpkPgZSwtOX3eKukhV
DmZQDJBFJgXxAtGs2QyVi2JXecDgtCDkIDWPmQ2UsPHMC1A3BD43YRdkzOOj
6XbpGYxCOUW2S3RBz1BTLhcotiNzm0xSfB92x4l6ov0lhPok1CjuTpLLBJ0m
hZM/VaEgwaIkgktspkjP0yxG3oVGebokxLwsUAveFRo6F62ahhrgxY/fsyqL
KvjKskwHQOnxWBZ/PFCZWYfP8kV0ljm9r4aFStZng/UhpPKM6OaEQEnJKqJg
oW6NAvE+SRZ0QpmPpoiic9EP8QliEcCUu8PB4ABkpyrZ5tNHZ0c8QaOD4+C6
bbHvtqahrvLlDEQv4PxT2Kppkc/xwTmM0oJFjN8K82UMKoLYR/BekT0B740x
03iMaIn4jqoJe7BnKA2Lqh1s+Hw5q1JU9dSqQOZHlrVNCWI62atYO2bckw2P
1xQKPn3YabVxoPiPshxdEhH01l+D52RIawpO2SCrRANuKt5YK+GKCRnENdhs
3hfUi7xVXcZFmi9xaPGboSiXZ3R9CaOIpghz0+trSCBFCnERX+Io+NIMhA9f
PxYaEoqkvDb24wux8bQQuKw/0ZmS5Iz7jSIggK6bpXZXooWpbvc50tLMoj3p
CH1lSkIoem6lejg5UsSuaOY9xSMRSiMrlFp+Jl4TlWbFwQL0PVKtQ7GB8NFO
ozpTA1VHxowQKzUrq3RG+01qjtxUUkiMeeauOpyDL+LCAKwRgqpXrGqmHKRX
DXYNRFiSm3H9kUVpFLuzfA77NAN+LzYfok1zuvDk+h/TQU6SBRLbTKVu2vae
XEpeCFzYikgcYzQeE4qRuBHZcj4CvODbqPrcaBXhycNiX48uUwGCRF5VUy/I
kyIvI2uLcUS0J7NFIOKh9NacvlGDPWLAaCkuBRiQrDKWn6s2ML5AlJwFzPqk
Zj8g1dez6Pca+A9AWTPWRF01mW47u00UvVORbWaXOk9iIX3Im+5bUMze/fum
i1L19nEEglqcrdrsvmRNTvHiRcvMml9o60S4SuH2oaEGr9aCNu/5v508PXvx
M/BsQXc06aN9Z7bie4GGMOKjTIO9gZW16aB4oAtiECmqInQPByKj8l1ASApY
+SKVg4pZ1rDGVI+IiwWGbX1oWiPyj0tlG5DdaNw4eAF1U7sAoRCIGckHIBo4
oCqpzpXFc4uJjtTWf3v5InDDYFgFffEv716/st+gVVKkqSqfxCsxUyOxdCAo
Y1WCBESxZCLhqXKsfdE7gOJRLBT1g4p6ACkvBx9zDEjdhECGE7VisyfmNIP3
4gl5XXBiZYcEW6WIbpFOTLaefIRmgChFeUB2xlzFK7ub9i57b8hu9hHFmPFE
8fgiBbKFp38CcJRpQejhhMe0EdOHiOms2hGuI6p7+5mpaIjkEylCnvnU1SFb
cJX2BujnA9QCqQQlCjyTUeKjijI1vs8yVjQc+M94L9OmW6kgfAnxoEz83UH6
AHemQjZGmwDLQL4MZCkZx7gSbxZ8GKaI1GKNstIoBx6HIMotdqyEkUeHQewo
EjFOMi139J3t3BO4ehMWZ2kQJzFaScptt+xK5HFswKVuh8zx5UW6UK5uMhy8
A+oO+lcYVeBwZmhaikvGM4FphQevTD2Z9OiExWGUj4g3FdEVshDBbLI2Ih0n
hxeO7GELDsYbi0f/Wk0YtXtCIwHiICX0uBxqJ8Cmg9UBPBE6INXSpDBNmE+I
zd4qJj11GqMiEFoOOe5EzXuqIe7t4WUhKQJNwu6Lg8HwAX3F75HuyBRFOZOH
UWj8xsWM8ks2jaNPW2SsxHrx4ItojVmnpYMe1vTP+RXc0qLHgqgVHYrECSQx
c8zpbJlOeCLGOqSsoaRqrfzWdm4lKEZutaYy1pAai0J3ZOnDAD3ybLnHe0Y2
KYwzJQxFD4GV6SxHJ8fSPCnOyRntORGILFnSXwp70viEgOrsB/xVRWpPoHBq
d21DEXtFi3KYQDEHgC3vVH196iRr3LlnoOUCSoWyxm3dOCZw43hOHBRdWcU4
C+Q9q6jgCbtbmPn26S4Z/S/zdBL5cjxKP7OcjAysR6aV42lyZNueFOScR9EN
ziPn2mr2Ef0fcRLhGb1RizkGQuSI/B/vicrSx6jP8jrCCAuLyJ5krqIpSL4J
sT3cLlRHamIq+aH1RqLHDB8CIIWie1QDeNXH40uSjK91URSVmMMWFoibZD+6
ypwK773dM+kgGfRsnAG/hWooqWNpFV79AN/YhKEzuLdrlgK6xghez5kcyRuG
N1GUAYMBNdP0Q+LIEId4zOcwEaAzXPKuf8tjG5RBu7VC17nMVySgiGDQLYF2
onA6XXtGrE0tQrnCCbOQc5RjPFgiMaaTk/IczzqmmwzOYatI23SRTDzONorJ
y0wf1md5bZv1QZjyFa4IKKcFXf0xRErpMwndQLdJjCp17DxncoQksDtyCgJz
Xkwsm/avKNnqDe/F6rFE7QRzqwoIgywLb48IjUqaiuJYiV6wXjmwB4Ab2bD1
KCJ6NuF4inF9bK8Sw5Zaa9TIbQKk8gxU7ohVdhOJVA0HCD+drXBUvNvo0hIT
Y+xsfHRfIyuo1rRuVSQF2crgsnkyZNN6+aty3b5GCqsTR+IUHQEVrFbMI8TB
akJqweEDGERtB/G/LuUKoSWXpZSVk85Q+nab10CNHpsL5umYZbHuG7AuYpwR
PWu8tWxJjpHNnIMu9TugzAWQRJyNibWE8TgDjNKKUNRiPAzkVICXKJ3nKNUj
WuHdBDhReA1Mjk373D3NGhZE97JA/ErZtaxqJM3pvKqlRE5OUlg+OtgdOI8l
wAP3HekRiNDJJQYokYdrW5Z/K0oUohxtLX5E5KhnYwesKQyvMbMxPQ3ZbHpB
d9i7it7tc5ZmPlHhkGt4JizShLhGE1jSAFriJERBimqDqWYJGlHZdQwPBDbN
Et0bz5aFKpi+aUS5LnOjCeHMKLDl06bmjH8RfmBFNb34DnprzEaRlMmAKNxO
swSZjKXTdTkXUYN9luSXo1n7Mgv5gz8R6zfhzyeSDVbmhp9P8Haw6fp2eEXt
F81vB7drBW934zXjUx31t93bFjnDuWuft8xNiOWv20e4boaePkTb7frbH4/N
vWAvORb8mw7LUXjfRLo6BpG3JAb/HBENT6lzLdSeUrWIVE4FHyj2Q0ZcLKvS
F0DcbpIVKI4sQ7UCKrJ7sT6wvcLTm+KUrDBuP1n7irqx6WACW3+PXPanz/rn
S/LQdcyaGAZY32VbdYyDFCK1iIINM+YFBkWyXMRKtsejWBTNKJNuOktBBCBC
5ewiQ6Fo1lQ5S6uKzjIuWW6Y5OgOSOmCRUzCSfKdXcWrkBw0bhzN575BAndG
pvXSqYiyLxSmGsqrNYMgCdpk3JtEdPvgNn1PwXFyma3CZheV5Y7aGcdClJRi
bBAK/lFsaZy7WxpFquE7KuIBNEvmbxfy2gWcBiZQLvIKh0f9Gels664j4U3n
KcW59Grqps9me/6msiSOwVlqFYouEgxsYombzhpHYnvTBv/aXIVMMeVEACwF
3cK/1j/DQZMcSFp6gUEY1cNcm8mCHAGLgtVVzuFlpsvxZ1dCRhFBDeH8vqB8
PpqlZHtXpI88pO+t0RS8nnzXKslySCYppnv0MLJXuHjEjCYek+iFNzY8ULYe
40BFwr6qMdoyM/VZUOjnbBXBp+k4cWFYTcAAEFcJmtXm8Qc4yt+VL9EQ6UWe
T3BbmTSEznc8/dNA0fGEVcSo+qmy/UH1Fz3JiE5ylQCSCB1C9nSekVu9hshs
pPVVlBkabYmmsSze02BPkYfrssUoIWap1x1FGxDxK7QXAuGJunS2QznbGDGo
s71GDQCA5yrA5egSwTEt1JNALnauzjFZQimwjLHMeXMRszNya/ervI+oDFSp
Zxi7MfYtNj8lI74LUxffLSQArbtsM6zt1zzFlCrED6sOiFIkNCKSMHORjjxf
vLdpsNpTT/oIeS6Kot6YnsYrYRhsdrDGr8Ycmajrx5Yn7vKiGWdbbXV0umvE
DQEI2QeCk7FIS+q7d/yMgSK4UqxOdilpAdGU3DxBiOZoeV6KbOlkvLhCp5WE
KFidIs0CtaKLKA44LXA7l6eYkoHv0o30RPbASsN2ob4186BiGJXjIq6AGHU7
mAWR9cm702HFu/REQR/fSaOMUTMiIhW5GRBbRkDjehKJbikrAmLhwj/ERUKh
y27BGPo/BsqfTOzh4G7XL5xEnI2SqPa4Uh7TZTl2nCx40xNGg7jSiHFZlh/H
IqZXXA0yHA70xT1GFp5M8yKxpzwBRXJ70BjyNckTJkbTZcHhISw7ojIohJkd
YJIWoS4vd9Vr8n9ehJJlaq89hRhVyeNIaBgRO6sBedKW3EFkTwuJ3aR4KD+s
00YvG/PxXhjOLPZ0Uus0jkzgZQSk8CT24DF/sYFoqHCLmkHxqRWmL0QuGIqY
bVOmQa8xGYpu/NPXGD5IX0gewvbAnPg2fxvhDAymiAvkM6XmPvW8nJOxn6DV
E6WFHoowL6QXpHsEmRywfS+tR8w31uPJh8Z1m2kEAPi5tX6UzSAcSEJG1lO8
mlIy8iJq3Cr1pJFXSEOynauJouwFvXuS++m8sT4kvn+KzblpEeYYmtMsslbx
SS4XjcwK4qubpgUKtRKr7BF9oSWW9ktEBtuO+BEHN6CxRB8nFhwOMWQcC+Ei
X2Pk0w1cTYVeqVHC0e0s//n3YIAFNzQ/Bi1bF5RJl+qdQ1FIHKo9s0ClHCnG
lJdeywPoJx9Iqf0cC7pi8Oda0H/ivDZHnsxkKSKE4yA0C86rF9DzfQPpsCRP
UnRszDqJNiWrTd5+kl9sRa+dA1vCgKdz3BZaFXrZWcWZFDEo/BNnnmgESVMR
BuK2bZmTNmYeF++d2Z7TSHGkzjLT1JeozEPjFq4Mk8DQ3aNygxcEY8NsRqzg
iQ+Z2Wgt5lSDc4GF7QBJuzDIM4uGDbfHktSYBJLSySVG8fC1RLtP7J8GYmlU
E23IXduycFn2QK1AZLNOc4k9cNtNjlZKDhAezpkdsNK6LQ+0FYzWiimG1Ilq
xCv4UkeUyTjxZU7RdDGsi2OOyEIklDCufFCOTXcPxLCoY0HouAmsglv3GtYl
ARQzItGn6qiVTKcY/CUUCKMhVXJCs35EcgIw3u4Q0/YQd5ogYaMzOlWQjNvw
N0W0qAYQ3Pa3vjdHds5ntF5GDx29f+vRzb0Q+wRIlSQFY0Iz0eiv/6nfB/16
PDD9/reBIxLuCmU3rgUej5LqKkkym8lLiJ+zfxHwlRkQ0Ejnf/TSrWz6aEBT
n9m74IUAssWF1O6J970XhqxqQODrsrlF44bdYoMK0WO6gvF5EZON1pMp+Nbi
WlOU3+r0mC4QykCwF5EdAS2PwPb7NjGK+DWlhrmssTUi/hy9BBSYGB4ZQCcA
oaQKLBtwzoY8dtmFJXHOk8hmC+AX6FJeYCUF5L9EA300eXnyM9IiK0tMhZFf
IcOX94T5kRWBWDyniJ2gPcEZpTmnXoQRFdptjn0+jeoYSlkjo6T+Ks6tb4mc
PWAnpewfj4W6uPdkww2w4jsSKbS8u4TrzCUdRUhF2BxQY5bqN+LkOkbXC1K8
UrQvkReUc8LszlqBI9LFBcx1y11hdlJssUju5ZCspdEpowLRroid592WiqAk
XIwIqGoEghA6s1mraunjM3WubAxXUeRV9I9qmMvvbMTbUMqXFD8R8f31RJH3
nLeUlvoOQaiVbqO9+5GX/cGJ6MJdAlpCac1qJnRJMdZzdBxF/xf8UKkVSrcR
37yh0i66gIhr/4izST/lohJfYQ0IeqlP5gPvBwflnHJXcaD+jmLcX+Qd/bvp
FbufgvjyTv3jja8yQ9fZEhBNRFuzj3JSGbGIv3iL4WQZ7ykOjBmv7BLum1+8
jfgtYv9C2wa1bs6nxv25aW/qtwuASbCWUn+RA8sKgPE+l+3zv6XyBO5nCU8d
HdhpEN9gaBsa4dWS+E2q2vAoG7dZHnKjbHjITUDgZLWvAXr/kGAtiM/oroln
sCHfdGbJtOqos4auBuI5kY8Ax9lH41+SJm2X5Ex7E5Su4Ps9lxWalpGjukA2
JJiWCkwBIXH5YwUpgA15dHtIV04rZrMJR6IjsIQvaOtcfwurXon27h61oPZR
O66/goWsiIBhGZ3nk8Gxcnehk0RvrJPRWgnJQJAvVgVJJMA1xYDDhkMU/3lX
QE9HAmTpi4ZZBNtuPkrxJ729Zm+w91jKzjFydJZFdowvHWMY/Lw8/jCfHWcl
XZ7j8Awf24AcRIXHSLdYXFjbvo+ERPIsfv444ismG246uClUSgwj2jCah/Dh
GVpgznCIAc123TRFuO3BVOWHxom4ppib4Z3FseeuyoZMyJXZrAuEhutQTM/T
XCrCIYL9gL7GDu0BydXjip/86Qc0Sh/Dr19rzSu0x2DRqPdJMdDCkDtX5ztY
BWzn24jvG7z3AlgUvPg11mWr8uOgkKQ+9pzqBuLwDWUggx8dZnPtxfVxa1Xq
GsdcrxnXMM5atcbmob6DjZkN0nx9hHpRxMb3W6oTfstH43EbPh53s7rjbTPc
He5zvNYZFlO1ajXKC2g188rCUHSVMb6diU1jE3Q9osBKw2JMkI3ypRfeJkHI
gibsYEQ8J95Q2DVozwVnyGAMIDkUmftYKxhcb0+7TUvONqtQiF4si3IZU80T
dimA5Ebp6pSgZoyYX8aA6YlE9YouSOSK/Qdvxebx5N0zwER+tkwYqxEwAAkz
CG2M8Vi3wO3fVmleJOeg+b1R00epezBjozGIWfT4M7ETyPddvSpU0zZJ3DUR
qPsYp7atW0pG60A8T8u6FqqZ/Hj9/w1+ahNdXV0Nium4z3U4aSqcYgc+w6e3
H5P0SvsCA4BilMymdiso5N7MaKloVB1TFLCA5mf8b6GsvtXjfzG/HH/X7HX8
nVLU7S88hDzGOob7zb1uM8/xz1oy+laPB9kC7WuLkWFLc9C3PiP3nwapFwAw
ewdcFA7T/7f5V0z+327M/beotzK3LQDgTvdmwSAxKO2zsK+vkoprPw4NHppN
pBYFDJrjtyRR2xOFvPJNNaMmxjbzW0Ce4aovcvZ6kXQF2sFlPFsmYdmv02cD
JkZW2ESy09/b7Q8fCPeqkynkOKwK2peYPXmcTR/8RTH8t1uWdnZ8Dnk1LLVJ
8hXA8Andn48y4wJ9fUVmtn7Z7T/67ePBdZ9/GbpfthjW67bFvU1EMy85Z4vI
4c/w03/5sv/smSh5g3VINygjPsQoVu8PH99iesQMj5LEDnuaZ6/PcnRg94Vt
/Z3dweDRcLi//2C4u3/08PDgwYPDh7sPOjfsyIaju8ODZztwH4s09MkOfOOp
Wza8tfNL3P/9pP/vf/tNfoGz/7X/t8Fv949bv9kyX7kBuu0jdNuH2P7L9v2b
0OvEX5ihhbFjOx6VGMeXhFZwfKim8xnfeiI2YXrn5Mmr70mxsGP1vbnSiVA9
8dwaL1nfS8qSPAybW6dB7krGJBCJD8AFfFEKLZfiC+0NpOgc68smZzaEqtk8
B6mmW+WL/gztytuugJ3NKpRYLxtIqj9WQ+j/YwnKHglBeC8H3jQnmHDlrET+
hurwtx7XGgjpOAINTN3r3igcusNGs4q4PQKg1UZYiqPaH4kMztkv9RGwJOHA
vEIDNEgCY8p84gA42FqQ4druHlVGfXS426OdJswAxYqVi5daseSFeJof66wq
PB0NDo/1ur7C5Z5a7HvsLqlfFtAECh3+UGiKMwCjhxbomX3ZhkLWXvRuC94T
+xgngSq/FKanQqLeiULppmrY7Evx+XLsc2Vme8aNs76M9dtL9/eqQJGh8N5k
V1h+zhEi1r3ib5IdwJZOJHdT6W5vmB6MyElJtHEpcXVqgsIfvwxIzZXtFYqK
Qxe8fRtn4vJjaCsl4mMjF4Crs6PeK8jF2YqKb5uOl+le8yHbB9vlivqZ+xKW
fVsX5u29rqwIeectMWCWxNPATKfnT6ymyVinGzFHpyqFHWPy3uNNaPMqdjVx
A6HN+asEb4Aa1Pi87GgIqRXYAmgbpKWNYL31XOS3Bs2+zpH8+hcxBgJRAgat
h2OKwbAWYMIv8bk6nHQUtQZH0x7URa1wEzYIYm4zpvFyVpndjbvzWr2FNCnH
7UpIbiiduTw4n5+4Y/R+Ly0L0JeZQ40pKsG+a0365CrkErL+4VjRm7edAXBv
oyMaA9/M70mR27K8HJjMPpumwUycTTwag56nkhxBcJq5pNNrKKcsWfIBkeou
sYihvs12RJsc6/QeqQ4pBZ8BQ/AYMPk/ubIvi5eG8pStZ1MfxFAtcgImBZCs
eCN6iA8/wA7P2Gy/MGyDNp6X2v+uGT0YR86CC0u83BvkF6nP/1tP3NykfNXs
RTFq5O/7adaHhZ9T8W0M7oDPwgvmXTMJJqGDTSuMC8P4r4wzPAMIJCvG//FK
nNEAuVbA8JZBRgX/gsqxupHX4UrMFjoJtjiaBl2sQqbJ75BKMLcNrai9z9op
HPCWuv+3HMsxKlG7s/oCJ2WH6ElE5y22bbC+ULGfNK527agFJW+72usawbIQ
/jnC5YJbmglWw6XypbOQ3JIusBGe74uEXaFYuDxuqKGEMGnwmdLMU8vXJQJC
HP3eGXrVMqmuJpFWiiLAcp/2dRXIsSRKfWl4gg0ePbtENJh1POlApYaWlZ42
Ls2OStqVF6xll2JH8JaEef1oNAoKtGnWp41idkqrB+WWjZUYOIBbBZ1biDpt
F6tNsOl5m0po7gPX8waYEhVCnmA3yUeP1GX6uPtx3bCgtYO7WSJqE+Ba17pB
Wqqt13srXPnN6/VebVu5j7t172+IuJ7Dt7Pxhtq6lDQIFVvXKI+gwIWinXU+
2CFGqxoGkn23djpb1oyAPVCsfupFrFIoq4t5YzpJmVd2Jd4OqSw1i5veYllS
C/N7r3V9R/hX7Pjum73twUbgSq+e8ojCYNZ235/E8gXMLp7Fi/pN9GGoIS15
MG9Axhf5FaayWRDDSoNeMoiHPP70tOjavGw1/MP345UVg73iyrcAq47TyFxD
PG6KOnD6KOcPdTDAZjN1Jhs87bvTb9NSmYBTNmv2eDtA7MqiNljmyQDvDOui
EMHY9n1CCWVjsZ2GIbLZ8m4OZ+Vz59R6Extv4Bp3cDexho41WXmztMwimISN
BvKX3L3dx8GHgWmH9oVQ1kVGYqDSCF0fTgSL6xKi9yMyDCWluEE0DJLUpfaX
HTJRyITrMeMLYL68qcrBhvXu/dH1+tHkcTvMjRUQXJkal7h0wyJytAxjHcum
RQw/cxGc5Yrlr7jdFRY9aV8Cd9ng1LPEi5QFLdOPkG0fQJOVCNi2dbrfVGTm
fbmReJ05sRiQYTZxFsdmcdXW/PUB1qYgdkGgLn+v99rq9HYRPa5zgSKrP4pk
VUpZqHpVQsFC6iFAWVz+qxRFaIta4gvucT37No7g7sXnEAGhQ59HBGqH3MEY
Bc+NaSN5bU06NRhgcZDay1IXuk4PC7eeG+6Elv/+zIvdtAY7FMPd4CdgmlPV
aZtdcX2xbsg1N5D+3HadWs38865+0zJ1pC+3Sh3xTy+SzOhNK9y/9QqREri7
QGLLbOa1V+qF4cu116mE+C2IU6s2xdP6KgbJAszcyPbjSQ1td3nN94w/LONl
9Wt8C+VP5dKaT/bx7Vf2bk1cunGFwdFWVDjJfXKqMU5+pMOWPbYtIeIwmkg+
gda5Jfi2RVawLb1jW5wbpKGdOACKbN6LauOJue2jQO8WxVLhH4WUGnD5cDZB
swaDdyq+8gjn0y77TzaqHJ8p9zsdpBay/hlnu6YO4P+vm0N6OTgNw9v6lLNV
lN90ENDgG9zgbzpBkOh3LrhlgKgeBgc3xahiaPA99I2CgAYk+Km0geK80qil
8yQb2GlX8+Amasg/98FjimJrx9W6EPjFeaUjAY7qjUZ1jbXDJdcvWXAtJi2/
zO5m9l1HWkp7GlIRESA5uG0i+E8pg7roIi3fSxJSlI+xuFo6pYCFqqK4UZJV
pJCErz1hDmxLGxwWXJMPIBCRgcEvZcZOEsq6GVEys6Q8U7yTrTNgKzv0VJNb
/xIPJfK6hoYlxjkHlOMKUThCYUvCeR0YlMXPYZVUdeBSS8dh1T2qqpeyxtj0
jK24FzX3Do2e8pktuUyxm9UmwwarxxKifrNd6V8bcQ3N0pZ3lqaR63U9EeZ3
+JC+oYnLWGcu4kybsUTdUWYqFUtzeZ5UnAW3yflnbrVVXOcv+CYu64qsVy0t
4jgURiE3Qa0XIvsSsGEmpvtwjeq/UUNcDoegBEKvr+fftOig3+tTQgtwu6ku
SVhOgurzaN8PW3uH0/c4kUoKWEjMP6VaU66gFoJB5OdTQvQnsx8XV03ZtGZL
j1EhKBqLInrysCepdvGElZ7T9nm3z9dOOO80m+zkhb2RpGFQDXypHlBqizZb
V9teddIeivQyHtNdcBn00RtODyAnVlDqtzSH9NoRVfXVhsTX1xHHonKVhnFA
NyXyyPZ6w2lGlLF0j+9USGYxnwo/vqZCpraTDYtJfj5onR5rmdZ6SBKWPnfy
3Y9vX6mlkEPp4WtNM111en4/oQub4lXPp8Ae5NQA6ce3pzaXQvLqb53D4LJb
AfinHLjPpfGw+y5sD0B2bF7tnGg3438sucwSTCpBZMHSKF1WbgPGrLt442hn
x9QzP4pkMcP9wAf4cuET4uZtSvCg43gre6x5cN+jW+Z73iSpIv3xXgqUqG/t
T+7ArttPzBbpd9Va6IT8lpKEBR1X3YCTYXaH2oqKW2zrT7jV99020SO3P6T7
EhKnI2NAxH0XhXVXG/2UUlWJM9MdUQw99sQv1znP35V7TT33OOMps84br60h
olLjmGLR9J9TicYrKIRSzHmQcRx2rIi5YLKfC+3Ky6WJa1hi3j17TZ5wRZmC
KjHew4rTNqwq8ky6as61AM4xb8Jvg3TGJZjgKza7d9ndgAGori+vbQyKyydY
B/Jq2L+36TnjnnN5uIjLc8xrwQrUe//5H7u7u/QfbhaE4n7K7nJbUocZAZmI
tfo+TOu9qhAtciCe2nVKPB3O+FQemzeUAN4zb5CqVxTx9SQHxUDel/SggInY
BRJ5oTozXs6RK/CCSaD3zWv/u4ytM/eBIr3gkzpxpj2GlRGPUFiAZ0ZB2r/G
kypW1JDy+QdsN0XZIMlVRzLZ9oZH3NU0C+H04Cd5BnHQM88b7jDZZQ/SspTq
+ZmPS54DyGtKqTcPa8UhgklR2ZDHjGMgLZQ4bxFPPlr54GS2ztA6aDrPwJy0
fcX6oN+Ux2sg7csFYsMIhyk9H5/EEVuqQkrYfSyaBrO8ocuCd9c+H44kT7+T
+3HDY5hDp5iJCCm4aVXC+/qdQBl6TVRiir1EugYPJXWW9HOuWQONqzUM4Jpt
FECDxrGP5IHI3l9fW38CiQXOF6jnP/AhlvvlgzyytVSAmHXkiQ5gwwnsqN5b
v8WpiGXYMH3m2ftKDT+uQe5ddNtDTAHpeftrL7ztseCjomIPEVop7RBsHOlW
2hoFljxPEgmwtHJj0N+P1FpSQQuvXVyZyHDYKQJGIUny40cdoh+KiNQXog1i
78KVcAFZGbIRrCGBFr+aX7HFYtChWcFOY4GlqTs/TzwJwq1Z5pJR6N6PkmC0
vV0ZTooq+MzCc3CMklUOqOnRcg4op7qxXH09IGM01QQkAtL7qmDZXtNB0jR0
tyJqoIyMEde+rOApqRJJNUSDS6p5f1iJCdiQFliLMmLilwlrxcgjcAptirMs
a3OHnqHINQJ+LHqph6vUb9cV/iZpyEZ+imMOW35EB//5H8NHh95OdY8OqB0U
PSTCwD2QOSlmwM3ORSA0lsCtk6OlNaqit5HNre07jLfMxhJX5dhSNi1iG2Os
EKECA4jNqq5beRS9zoLKFQ40AaNbbjNYN+IA6OsXMXzuYTxobniJkTZQlFpJ
/F05qt8iDbTAwlH9yJrtEmKwXZKzTiVwjOwC/dDrR05LsbvsM9q7SvgcixF0
bkZocWQHhdbtEyZPi9dS91iCjsIf8VAoIhw76XCjVamUgSVbS6QDXt18vI8j
oQZSUVChoJpNKDo7Nj6IWEDRXDY/vtznhCyvSPGTNkEzLcNwGRRvjrHets8/
PyGnIBb5yReLPq2LUPAZCFAm+PkUfer7P58afqv/0f4Z1sR2P7sw4d4u/WA5
cGYcNCkLaiEgRvNUUa3D7FSuke1baK99lSVuUlpCllqTarquXR69t406JCph
pEiiJsbajEOy65pe0PKCvajXf0BxcBK2p0IM1r5E+qqf+gIJd5u7b9OLnfgy
aBGVb1x1n5/T8hVE7lTRWCsho9ZKoD/UHIDFEknasovkNcAd2MV3Hj16BPwa
UXaP9BV+XdK30Vzy7gdzgrzmEpuN1Iv6WOn8sVwqLF1qfd8wgw2C0Lx0s17S
1Rq0C9aKqObplKXVGChpNk5cawFPibaVQsVknfEgXEZv4K+WrjyuD2c6fNRz
i4Y/aNk4HjzQk2eGj/yHhvzFtjTGtnVGbbdbtW96ewM7Uw5UGm5QhzbrQdz4
8NiTPjdoRtSTBs0OVa1OFAi8ia026yOqGBFddTgYq2dT/nk+tFi8lW424XQu
dc1bn4BHUjFIEHx+YvMPprbBkdxLLWA6VA3vgvOVcP6uD+C2ef2WCrxlhspZ
MEPANcqzJFJ7A0oourIey71++gFLLabcMcbLsvz48cnTN4AEKpn6d+XIokaA
GQeCGGkZIjjxwpQwfFYr9ckGFhrXhg+ObFJmkKY1SdDkzfXfypS0IGL5tlYW
In+tR6ds7iydp9rtol7VbtCIkJWDyyriugIArqaL17Znf9fbH3+DHu26Heq8
lS3aQEcG6yz1ndQs+hSA/Ec45zqD3A243h6tgWbyyV5tJvsYv8QUBH/zb0wd
PEUgeelgV1/y93lHVRSs0EEz7bq3PikZummm/eClB+4lRdD6TxNvr9vC1mxP
guhr5Re9iou28r1v4Trc1SKKI0/T39//b9IDkPzoy4LzacNg05QdXHSBLpJ4
UuRIxTgj2Svz6ac1oqRlkdTmRKUN9WQ9md223Rs08H3jymGQMS8hvrH7mEo7
F+eUZPp7oq4PZ8AX64vWb0mtRVa2y9JA1ZI5R3spTbKrgQTXsf+Sq62Q6Vjc
y/XWHAKyFG4NRFef8Aenx0etgrClBaKGJBNpL0T+47+j/IQONWJg5Qx9xzP2
YNrO3pVL19Sa2afCqvwSxoFoPdXifo7ww4SgIZxzxq3wwUj5IJMD1qjW5S6J
qQiiRn0WIYVY2VQsJiaesYF1BVnh7WuxLeBEQ5FwV3Uv4fCTJXVvr4tBqOfU
arWSHFX2zBpzC+OTHOvSE9dG6XbtNYbO4HZd284hBmZ6DJAl1jdt1UVZwvh4
T01ptn9SrR4pc3LpTye26FK8CFaQYtXRVEk8j7odNnTE88422styqbuPcTUY
88giBOa4XyZSqpeL/9qSs9RH0/UkqxdSAHAGYj7gpiFeR5lu0D2kJ37QsIvi
tejvBC2XF9WAEAcCyhr1zB4ebgRTXQUADHlaamyx7Yc96CxB9W/ePHs/JkU8
rWz/HBX2BIPcPRCCSFYj5AH02mMh4dwviKGQbkHbURMcZCjQ8wsXuz66bSQN
L0qXPcrgwsafWoR8/eyCjZOico/Z7h0+SWKiNGL3KxpjjxHUXKSiM5kSAnAl
Alifc0WLB9GJF5u+VtDVz/+rTyqRCpEN3eVJXP8a6Vzj1Y0Q3Asxbts/dLZ6
bDjsWNplLJaV6XbcYetSO9tK02jjvYreUmu8lKRbLWgdFUnfy06jmCVuV8II
ux7MwXfTa1Or9XHR6mf3UhtERFjy33VHs9/bs7GWHhJVcIHrq4qUouGieqIq
aXx9mFtXaWKe4qThXjJ7vYhvHlUXbn21hnH87v42k35cyphaddgTG18kY6n3
EGY6+j0TkDpRUB9FY2h7GH5qmksgBXBbzDKzdSZc+V3P1thzxcDGZLU9X48p
LW2wme1wmU3sDo5QL+Jy/IS1jXOvY5/29ztrouIiH1AQS3Dv1ECBDgkpgoud
z6LQ7WENRB8/Wqe8dWlfY84atuK2wHlUQgBqvLejJMg6sfUzhB9wp2SEzoaF
kFQSBjRR7g8yO26bQHFhUrxMjK1CZYnDdF0DcbbccqUEqudWsoij3VWsBYBr
Mui2ySXneJzikvtCeYWPRdGUtnGDbaz0KdfSFrOux2umQfNpdh6Ulj1gm41I
tsXV0mfvGc9GMwPm2YYYM2LcItdwOTsUSGgEwhdq3SHbwN0VlBwOIgpVI6hB
apHeYgtPKG+mkY5FlsdK2l13aV1HzRrOmyDfhygduQuoyYbNsokjT3TT7eEG
PTJkihrtkH7JfLsqh7/LEm+tVCkiyZM6nRQOcUKmCt+X3GaMm0Xw14sCi3hQ
t+mNFm8vYqTJ7CiSvy3jQg2jnVU8lb7sgbGKG197RsZG9f2TBvTUq0j76neD
+L5Bud+g2d+o/K/bxuFnD3tVqpJ8LP2cOfyaokcESjgkCutZU6LtkHusb+O/
8A9tNBZTxUo9zQu3fXg2DcqjGVSgP60VvG0c1NUNbh/0sD4oSMrVnxx0GECK
KDYuVouqDxLbReugD/b3HmwcdA1SABS3tB+P522DPtw/2Ajp/tqe2gpRDT+3
OvvDtbO3DeLadxTg3N8E59H6oIsmCOuDHmwa9MHaoBw0vHHQm47pIQ96sGvP
Pp0SOm0cdDjcBOnwYO2YLnPgHG2NaHX5R0cbB11DKC/wem0CuaRrD8AM/qCH
a5A2vNNXi/TGQesZEdju65vOYWEOCjM8mpnhcIaGOj/6cHPYYSAIoC1DlLTv
OXLI+nLxnYamImt2PrFyxFQKOLDhrjnGNJjCi6gLoj3nLtrTC2vEkjeFNvUj
9sVpZTZDn0zHar/YO5B6uxweOrgppLLmntRoYGWNgdx5Uyhly1haSKkhnNLv
z9jQPYacZK7Dd7D3ZAX980GSa47LoPItrVWPrdbHpMPnBAi5nDur0Iaw3QEF
RGEIsyoeXuGxjuTp2C66UnKfJe02EDAI+XNBwFX7QPiaAntN/AIBfoJvXa+g
8pjU/kzc1zq8s1jHY0768EybdLK6AK9j2sYwynjNZQyTi7ONOy0O1vxvNnpK
REgvZtEFi5Byn1QWH/z1kW1FU89cNxEkcesP24Yw8gI1RBBDnB9XXy+gLM7G
mpGOXadEwbpM2AK61krWZLSAuFk3XtA+Ss6j9C8YHc3rVy9+XosKlWg/9ZBF
Jrg43di3Xcu7mwIftnUXT2YzDyGQiDRsqefKKOrhnLJSWXdTIP0mODq4NRjE
lrFJau30tUFeiL3WURhsAiqIEdf5yWdYcp97lMIvUgCvbGAiYuryLBWsStjj
tA4c0WN1XWsAy1IqW/0uEzDaWyj1uLRLbXFsx6QISNunidrcYqZajQKpj6p9
DrnXbzH8sUQDwklA5+uRnpXTf04muRThulfo235MSFz1Y3mE7O42Ohb7B6Xj
5awiJkAqomZwsSNBbV2EGjYnwyvGFzXl7VEZX31aEvfi8j0deGNQunRBeY5O
i+jE+9z5KZhqTZIqTmcWPegFf59IfY+sF823o5Gen86x1i2G67AJEh+RfnVk
l5G2YSmb64LmGW6XMcFrgOGhOUXGNj/VY1MrBqkkVcS6ONuHyOOylPCLwPHv
9qbLUlIkRq0bw32ut72es9Kx0u1iXkR8CeRQuZJq7vVONfF8lJ4v0cTI3Rwq
aWzMlviuZ8xBC8rKriHWnqGcNefFj2QAHclQGrnVmEASeaHT0ckU04ba93MV
dJXgGJ8am3WISJggMYUYDMzXMIga1FBcZxIJJy8H5p0U6IioY7TnAyQhI05p
Ildstyi3TL5IKZ8+bljNC3ReP4WziVINULLlrMhMJK28Qa5KYmzkjK1epQsB
pemFC/b6apZRvThrytZ2LzpLhre9lZMG51sdZTW2ZmAddoS2dPEQAUQCxdbz
nq2+12zX9/0BEXfRy7mNYS1auJQiKXHgfWXjHMw6Xc7E9SwXNnA0oC+drKBq
0WuagGKHehzJLvSMe+ASWGyOJ3Esi2f5OTbwq8QdQlrEekZAi+2RDZeRJ3Kx
JxqrQl/kmibKImSX6Nm2T9Bw+lWZ+j0HQRk4zwMftyKzbketSzJmcEo2an0T
0LnAqaX2aWk0GFkm6eg+VYp1p0l+2kobrrZpJVTxw1roarBJX5g441zspl2S
2OxSREDnKPEvgvoKpl5uGEcQNK+CCqLaTOpTwfn+M8Z5JDlavOSnH2SN1F5o
jeHwAqS7l5V2XMMSbdtYf5E3hVRisdhiB1JEN4klArJsnsG3Y+z3gqXr1136
pIO4cUo/oiNIBEHUIRxx4pD/fZrJKXm1HNi0LSn3wCTysgReU3q1/3xKyiW4
M6x7xMMHodolVyIoqG/yfU1dEmFQCx/a1maxJ5bGbif5uYvYFbcacRk2PS3a
vFUtSFwXsMy04pHNy87WzkREUrrkvAw7+xJI/0x8OP6E4XR4TqVrQ4NZfJkn
wpBIcPIMeArsOmmDDk/QSR5TmE+KBHHSMPQZ4T8jC34OI1lKl3xI5ovK3y8R
ThE/WQ1EcM+LJBH7yMkzGEwgCe6Hq9GQZJOgaZJcGGJH7PSQ8pbS7V2LUtcj
NyMbf6jSuhW6CHglz875hMIeEiV/hq3Aa+IxYaUfpouYUT9Ukit8bkShE2E2
WoCK6ulOq9JHSwo5JvIa1WJjvQBVUSiyvF4WzTqCQDVNRMuuS7u6vwCwF57j
KohQyQyO01SeY/3CsPtrFKYXsQRigUP2vECCs8xmUopgJQ551L5g1z1kFT9i
vEIfzcfjfyzROzkGxeubzoamVPAn/v/B3nB3cFHNZ/dKtrb19wf7nYgGmSBm
foPRRfiU6fKEoN2pYQ4fvY6+BSXVeURJWvIpOJaN4m5iTPKRWShlIgJK3lcu
s6iSP+4SvVdykXWMBK4TVcZTNkwgPtEAvG0T1kDLUHMRRBRnpDyJez5LgmtF
A1EpcNQ0CcQgv41Kb8dUDMVzC0t7ua3SgEazZBMIn6rPNHTRg9t586LoFWg+
gzBZ/yWcIvcylJaO9G6f8/Z5XP+Rha0EscNNDtPJV9jRsp6+DyypXmuBhunT
MHJgHTdyYIKLPpFZzjfVn2GcGgrqDWZ8W9mATOwBWPBtK8gSH8uOmnU7utQD
wgtNlQw88P3MwLptvZbZb2dwfRNuSPFHMnBMaW2wad90KBl1jLG2NDUVMoiO
/VVF0bvlqPK/rJ2MjQCmggZJRf5wqh4RRbY8eMN3z7WVaZiQid9LI8Duj2ff
9x9uAwSa/rn+KIfGtSZ3Bs3vojdWyNQKifQcjuMeOnFrF52WtWq0ShNC4WbU
NsmPd6D6hxSe5WrTamYJcwGx3vW1EJPksXK3kXFa8l1pC1+Nou+L+JwplqvR
tL4zKPWWK3jpA1c6lPpNpat8OV0fx/drIAnstOJ3xxU6jje+RQ8DE+ieVOsO
HTuGi/Pw+d0ahBowy+tSa+3U5ow0zAz4c+IkWC9ZHTfp61HxLbz6Mj5Px3Jt
uiVZRwVLDV9P20zHfkv9SejVMcYPlReiMuBNwaJb4TBvqJem+e8mQQEX6Rd1
X0DtWQoj+FVsakBSmuJPP4RWhm7QGXUbiztIESgTYDCe/dsknvXPkFeRAtCN
i8q9idEV0uSHwkB4xpcvX7/Cu41l5qT8DlWVlwcyIPWwr2R52nnKBgCpAzTD
jCHOu5M4kKf5yZs10n8jQQ9fsES9YbCy04s8G3XnqVe66u3zd2eo1z931blK
032av32+bd5YouQMRhjri/h39uTZnm95cqZsDfkeHh71McOkkCTPTwoV87Ia
F9HvnjLN+2SA8K9zl03cpF8fkkD8PC6j+ybFhT6D09BkNl7IenFPn/Uci/FM
pLwrvWYW9OuvX5ynRf1+34zi8Xss7eSr8BqlZj7es81a5LO1Ztz+e10vFOG7
4e7eQX/3YX/3CJ/YdumEzmzgGm678fAE1SZBDq6WMem57lqLbopx2LbvuTgb
fHe/v/ugv3fY8i7Hxrh3XTjN57/rBbjgywDxsL930PIyh7rwy2HIzWcsGE10
i2WxyEvWAF10Yc+QnX0EVOy9FFKhc/CTaDCwHWP/SBAnLyCXyhQebZkpV8tf
UVXpsARa9PU/ATbt/NXc/+WvHfPbV50d0+9/63UZx2sZfRP+YIDn82Oz9esW
w0jN2yi+GLBW2m8PTe2lb0AaA8IdFo88tjUhj6V2ZtAW5FgfJzzq9IInNAga
n3Ibrg95lhh84LncDW0N4h5b61ICj/8iLNaV82wEy6Fpp7f2ZA08QcSOFuTs
3W4Kh813NoWH9DfPIVfic+YI78bNU+hBBqVLf5PzqveGaD4sv0MHDIqBV/68
mC9Gn8PHjbOgd7R5ZFvgDN9n+P2RvUYKjbgr008sVBv2MZhKi+m2T4auMfxb
3FrA7C/ySfO0e19wWtTjZ31QG4qyebLhF5ysiCfpsmWe/S8+T7+2pXgNm+fe
eB/+2NygPi2aJ9t4wf/YZIu2uY5uPZfUfr4tfjZP9+DLTTfJyv5ysuhX40Uf
8zebJ3z45Sa88SI8+nJzZVXzee3dnqDcZg7awNbN27s9Gblxsg0Xe+/2BOSW
0/RvgYp7tycnN86KltPfQYlkltg42+0JCBpQ2qfa8VjOcQmigwTN9LFxJMLR
PP3tScqfnH6HUucagXjwfxiInV/tAJ/xc6v9fHB7svk5S2kXJPZuTzg/e0IQ
z6jzafPEtyegnz9xebGsJvlVywW9PTn9AzNjN93GaYe3p7B/cNqdMVY9bZ78
9hT3T02+M8pzh+J/6J7Uf5rXc3vS/ufWo7f2Ty1l45Uf3p5f/NGloNcGjVnN
898NB2maf2eO+atZyz7cDRVvhCMv2znq8A5JcAMcRUKGvTu8KndJ4dfXIzG2
d7ieO2QcO7eQ74Z3yD5q8++gTtAIxP4dMpMmID6f/tU0YGwy17KUO2RNTUv5
Y9Kb0QTz35NJ/32yal7KHXKlP7+UcAE78ewc8+UvmrnC/h1ypS9wKrW1wP/7
dTDcUu6QwX0hBKstp5U37d8hj2xcSjskd8glv+St5Z9FXJZXQIKal3KHDHKD
SL5/l3yMhdebzQf7d8nMakAsq3E/n05Br7474eDgLvmiBCE0T3yXXAwtkqBL
57PLFh56cJeMx599hxNCmu1tB3fJM5qg+HNEAbNK5ouqZS13yTS+/FooxjJv
sY8d3CXXCNZSJnExvmgG4i4ZRg2IovWe3CWpbwCinX8e3CX1b4IEDfJ/DsXi
bII+kebl3CUf+bLLkWXsSHRZ43IO75KNfPHT0RW1+lsO75I5XeRl1Yrmh3fJ
mDQQvHnmu2RGbV60w7vkGjDpTkK5NM1y7OFdknmcfANhPbxL6u7m3tE8SzQp
/GkpstUrf3iXbMJbTTpaFmXLlb1L/uCB0H5z75KiewBw55lGEI7ukgp7IADx
bZ7/LslmOP9GbnR0l0S0BkcrDzm6S3q6wYl/dJcklefdqNQc3SVVDeff2aiR
HN0lia0BskmbOLpL4ihwbOA0R3dJGIPp/6Ad7zZhX0d3SVzDRbQS+Ad3SV1D
GNoI7IO7JLBrICiNvTvr04O7JNTr6/nT+NlK7B/cPbH3F1JexEUy+bMCXZmM
i6RlPY6J0L+/RfjbNcWqYzoIZT1IwkMfJJIKOxtyVoiGfw80/jtIeuB291xr
nSLa+xx1v009tzgTeemKqHOdIJwMP/XKd8PTJ64rhteL1yu55DrYSrdzTOk/
o9xS18ZD88Sx3C/3u+bCVWVY+HUPu5hSofGgTDzWJEqoVBJP6aWOYaF6SQf0
U7AH0ZCrA9k6GPQiZgnnWmY5ni0u4lFC3dkNOQJ7Zssi0RY+gjH3sABu+8cP
OESiJ+LwAZ7UHwVzXoKXOH2n1EZQXBcgqBkmWeRbQWLBVtjtxubD8HBYrHB/
YNay6o00JOGm8TYZKvG6Gy8Xmp61oXGxbReIJ6ZtI9dbtVCldxyFhksKmFY7
1mHCBnZc6ZmEDowAusIqGpNkVsWAP9UVZoP4DVsJT6WejRbLws+0BuJohYhV
5VjX0sQwM9cxAKCXY6xMV1JlZG61djDQqh+uwB4jBbdgcQ0JaK3dcrvW8aRe
Al1ul+s/MpkISvq9G119gkF0KFUAm1I0NGkcFj9LpI2mfikQczpNTPU9AkRp
7jRCTV5KI1/Nc73ClSstT9VQop/wEJaLiXZAXBs65e6u3Lp1qeXqbQHseiMD
qgoYpxk3WRxEXWxygumFcVn1+MiTy3xGBStirWEilalxunpBj7C6BuLbMpMC
B66Kd68RjHxaJdjKpKqockcmzSHg0sUVthvltHm70YPtSHFE6nQCdRlfJHMs
XTWxHQ96ZrTkXaXk3wLTQjNbm1BKBLmkXWlIN09nMRUHu6KSQljNy1WgiC9j
+BrrkXAxAK4/R2D0LGJW+iIhvxZ80OeoNzjuc5pxNTftCKYPYgVTbi8oi5R6
UlrlCS6DW6FrRoLD+vXPqXC9tPFJuQw+1ovT6k9Uhynnnkp2WoI+10Stlf3c
q+dYBEnOXMoJILLAElbSfnOWrpbkyARUe1no1Op9I3oR9Ze1N8X1rHj65PVb
oIeSzu6qokuJn3p/Ha0eE1NrRG4zCEecYeMiqkihy0290iVRUMefipiMpd0F
YqlXWUrQKi1RZmipnMteee5rI1QDx5vY7ksjGG+aSgUeLMK1pNzpCiWbzHbl
uALycCFFWy5T6QBOddqYjQNDddfJa1XE2EL0Iqm3ggrLIwb9pICZLCgxHGht
MomkbBYsk29rrfChrYnIpG/gijNeEXWofR8J+9QbtbFs466czXLOpYepako4
nLyGV6t9JMuawpdx9D3/0kV+QUdzQn0jbJ3InsVkmCBoqD2mQmdlHkhWnKoa
2bqWnBTlyRHUAa1n8oy6+dlL+/N//e+gRqYrdBVXER3NPRAfTqRipz1P2/6j
vvSwxAnX+BHMxxxMh+8NZ8oQWKmtzlsdNaZyb8TwbNs1eUQ+X7/4zW3Jev4x
RY7/c704rozSsDppCzPCJqRIn4I1SyKqLpZOilb89s1TfDrmyjUdzg/gRvP5
sqI/POmZyrTGs6t4hVnJrscykpAEd5Xv9Aq511ZlmwdpsYGwqR3uXYwJ57bU
rNQB0xI5Xh0rLbdGaLbkQg0kGvj1mhjDc+kXGc2xQxsuPksQe2IqyBKmbM/S
aTJejamvF8qo9m/QY0CbeCIdl2mZIjyUrq+IXwiu10D0Si7mHI+lSlrkymNK
iclOa7Fac9pYhFzbuFCVtbPvpcZhXthSdl4JTr8dyFgKp9QKDITTR64meL1d
5Q2diq8Z+111Nq9LTclw6ZbQCeqOmPqOZKv2PcFqIrzx44s8pRbDr6VFaK23
nqwWCMtVlsic1PSlCnpxeZiwU2qLoPBcd7COI/chrCkPswRTwinze5mFdXWj
sAy0+1IgzJgcBIU/M9bInDDCYmCEsueytSq9dF5ZUp92Y34IGjoF9Fn6/nG5
Man2x4UE6EYpwUZtduDXrVoj8kSr4e57/Z7qfbLwHiLdEe1CG8FSuSYZj0tE
YOXWlEsu+cUMSHZHmXmSxudFDBLwcj6PMbJPWunIeywxBPcOZk6pEJ1Xbd2v
T0x59XFcXp6rgeOrWqeUryKT0xefLHw8z6eo/1Ufs/M/BVNiLYwd86s31Ffe
UMHPp9rfl/r3IIBgIB/vmHcVLCguJhjTaHgO0DO0js2vARx/MTu1ZfDPVgDT
1iaAPhmUVeo/tYcu1x7wl1JbSdsWwyffwvr86im4Hlgb9s+xd5mn/8SL9QqW
6GLhKPxamfDw126OT+3LXzsob7F+n5yWDVlffvhayxa1vra2P60f6mtf8Sc1
PGTgcPvg1jGR9oGVg/yk0rC/nE9+P1njb6Ri0kYgv2oCsnEXwvU3bcnNrzXu
ZOvTmwDXf9rf/hSQabtbbxMsbskHsGHuT77N0r1tjE89boT8qwbI+zdC7mBY
//nrza81IfHGw/Gu/oDI1K1e2zFUYBpZGV7y264NaCEoBedU2crsbAJry+3g
1o2rpgt/41OXbU800/H6zw7/g4Va6OfX9jlxma6OWY3Eb9ihrQBxtmrfbjgP
OrYmjNn8Gv00k72W3Wolbw38uAkW+i9VTPb+pl/OLtKCKgRWq1ag1/hG6xcb
gV8je2tfbNyyln2+aafrO3RLYtCKtfDzy7PXr57/5jw50/TcmvL7VtxiZ84W
MpgXqiht1fuo12S8H4nX1CW8kxskPOFQX0K+a0QolfB+tPPgrLDtrSKeERnv
k6FGRVRHF63u7qj4G7Jj4xfeNzfJhevnHZxVO1UBSvIquRLd3IgE5X0PEHN3
BBCv/oLPN8zfTCqaMLAmDTXhk2L0rcTARnz9ZFcWiIEqGz4nL4YVb1rAlLXb
Nu64eBUYQzmnbaHtW1O/4ptW4f15s2Dd9GLzVb/NjDc/suH8bkODP+k/Nflo
06NyrUcxmvI2P0rVpMU8esOjtwbgNtT5i+7jbdWh1gHgGnA/+tmK/tZrsEad
2gaAW+CcNd4tuJnLfdYluNUdaLgCjTPX9uf2d+AWY9d+NvFE+hHG2MIZ1a3A
QQ50KMihfiWM/FVQkh/qrPFJ8z+SZME+TFs0k/xDNM4p9lVH69YzdCJRF/Do
48e/gND4aO/RYVBWXSpsUjXc9Xc7A65/ivZz9azPkpiLuaMFOhvHi3I5C1of
pjoCubC44ClXOZwnVUwfJhk7M9HXop1gwo7mo0R7xm1aVo9Nv2haIkMltuZm
72kyHyUT2/mIu8wIfK7LcLn2ZfS/pGw4JbP+L4CY/RxZrWRmJYW4uXLoOF+s
yLt4Se3qk6jE9rWT/gx9tjKG9OSapGPXo4YMfNn5DCtFxuP3SYWBIbZ4o+4j
geLVX1z/8jj4q18mWDlPSjJqKb+vvdJ+3373da1837dEBjlwp1Z+0fzS+dr7
5NuOFtrTnWK3sZ3R2Np6x7WCkd8Nd4f7/b3dvhZEuK6NRJFMMI4xX2uVVfK9
5tTD51sdvqUKpTn2Q6TCSoaDgYo+HH507cKPouiXvxbTcTL5zf127PXnPjZv
wsKvHGPAbfiII7GTd5wX2K+Ehif3u9i0w0a5tvk63OGT8fssv5olE3JJlEgi
2GGTTL7pTONZmXSk9qvav6/ILTNL30vx+Dh7bz5+/HiSTVbmSUqtIK6vYVfx
sxFcu/jSvMtBNo7/vsTP8dk3WEgYcB6DUQrzrsrf6zcv4iWFnZzlS3S8XGMX
hGyCY72NcYKzZZFht1Xb9CctzEUyW2iXNPGv4sV2ARhB8eRsIjZ4cZ6zTbwq
/RGkmYHtBvGOI2h4saXB3j9enwO9W+QgXqKRLyE/pvrno6Yp6E3Xxc0sLuKS
myE5Dz/2GYKVP0myv8dz+OZ/xJPle9kS3Ky3+cj8lM6qnDacvUc5fvF9gRex
HMfmTTzL56M0S+k1dFCV2HAkRW568mwQ/f8Xqn71LiQBAA==

-->
</rfc>