<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" ipr="trust200902" docName="draft-ietf-core-yang-sid-pen-06" category="std" consensus="true" submissionType="IETF" xml:lang="en" number="9997" tocDepth="4" tocInclude="true" sortRefs="true" symRefs="true" prepTime="2026-07-23T09:23:28" indexInclude="true" scripts="Common,Latin">
  <link href="https://dx.doi.org/10.17487/rfc9997" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <link href="https://datatracker.ietf.org/doc/draft-ietf-core-yang-sid-pen-06" rel="prev"/>
  <front>
    <title abbrev="SID Ranges for PEN Holders">YANG-CBOR: Allocating SID Ranges for Private Enterprise Number (PEN) Holders</title>
    <seriesInfo name="RFC" value="9997" stream="IETF"/>
    <author initials="C." surname="Bormann" fullname="Carsten Bormann">
      <organization showOnFrontPage="true">Universität Bremen TZI</organization>
      <address>
        <postal>
          <street>Postfach 330440</street>
          <city>D-28359 Bremen</city>
          <country>Germany</country>
        </postal>
        <phone>+49-421-218-63921</phone>
        <email>cabo@tzi.org</email>
      </address>
    </author>
    <date month="07" year="2026"/>
    <area>WIT</area>
    <workgroup>core</workgroup>
    <keyword>YANG-CBOR</keyword>
    <abstract pn="section-abstract">
      <t indent="0" pn="section-abstract-1">YANG-CBOR (RFC 9254, "Encoding of Data Modeled with YANG in the
Concise Binary Object Representation (CBOR)") defines
    YANG Schema Item iDentifiers (YANG SIDs), globally unique 63-bit
    unsigned integers used to identify YANG items. RFC 9595
("YANG Schema Item iDentifier (YANG SID)") defines ways to allocate these SIDs using
    IANA registries.</t>
      <t indent="0" pn="section-abstract-2">The present specification employs these SID allocation mechanisms to
   allocate ranges of 100 000 SIDs (representation size 64 bits) 
   to each holder of an IANA Private Enterprise Number (PEN) of a value 
   below 1 000 000.  Holders of PENs of
   values smaller than 100 000 are also allocated ranges of 10 000 SIDs 
   (representation size 32 bits).</t>
    </abstract>
    <boilerplate>
      <section anchor="status-of-memo" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.1">
        <name slugifiedName="name-status-of-this-memo">Status of This Memo</name>
        <t indent="0" pn="section-boilerplate.1-1">
            This is an Internet Standards Track document.
        </t>
        <t indent="0" pn="section-boilerplate.1-2">
            This document is a product of the Internet Engineering Task Force
            (IETF).  It represents the consensus of the IETF community.  It has
            received public review and has been approved for publication by
            the Internet Engineering Steering Group (IESG).  Further
            information on Internet Standards is available in Section 2 of 
            RFC 7841.
        </t>
        <t indent="0" pn="section-boilerplate.1-3">
            Information about the current status of this document, any
            errata, and how to provide feedback on it may be obtained at
            <eref target="https://www.rfc-editor.org/info/rfc9997" brackets="none"/>.
        </t>
      </section>
      <section anchor="copyright" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.2">
        <name slugifiedName="name-copyright-notice">Copyright Notice</name>
        <t indent="0" pn="section-boilerplate.2-1">
            Copyright (c) 2026 IETF Trust and the persons identified as the
            document authors. All rights reserved.
        </t>
        <t indent="0" pn="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<eref target="https://trustee.ietf.org/license-info" brackets="none"/>) in effect on the date of
            publication of this document. Please review these documents
            carefully, as they describe your rights and restrictions with
            respect to this document. Code Components extracted from this
            document must include Revised BSD License text as described in
            Section 4.e of the Trust Legal Provisions and are provided without
            warranty as described in the Revised BSD License.
        </t>
      </section>
    </boilerplate>
    <toc>
      <section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" pn="section-toc.1">
        <name slugifiedName="name-table-of-contents">Table of Contents</name>
        <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1">
          <li pn="section-toc.1-1.1">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.1"><xref derivedContent="1" format="counter" sectionFormat="of" target="section-1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-introduction">Introduction</xref></t>
          </li>
          <li pn="section-toc.1-1.2">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.2.1"><xref derivedContent="2" format="counter" sectionFormat="of" target="section-2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-example-sid-range-allocatio">Example: SID Range Allocation for Holder of PEN 32473</xref></t>
          </li>
          <li pn="section-toc.1-1.3">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.3.1"><xref derivedContent="3" format="counter" sectionFormat="of" target="section-3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-discussion">Discussion</xref></t>
          </li>
          <li pn="section-toc.1-1.4">
            <t indent="0" pn="section-toc.1-1.4.1"><xref derivedContent="4" format="counter" sectionFormat="of" target="section-4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.5">
            <t indent="0" pn="section-toc.1-1.5.1"><xref derivedContent="5" format="counter" sectionFormat="of" target="section-5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-security-considerations">Security Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.6">
            <t indent="0" pn="section-toc.1-1.6.1"><xref derivedContent="6" format="counter" sectionFormat="of" target="section-6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-references">References</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.6.2">
              <li pn="section-toc.1-1.6.2.1">
                <t indent="0" pn="section-toc.1-1.6.2.1.1"><xref derivedContent="6.1" format="counter" sectionFormat="of" target="section-6.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t>
              </li>
              <li pn="section-toc.1-1.6.2.2">
                <t indent="0" pn="section-toc.1-1.6.2.2.1"><xref derivedContent="6.2" format="counter" sectionFormat="of" target="section-6.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.7">
            <t indent="0" pn="section-toc.1-1.7.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.a"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgments">Acknowledgments</xref></t>
          </li>
          <li pn="section-toc.1-1.8">
            <t indent="0" pn="section-toc.1-1.8.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-address">Author's Address</xref></t>
          </li>
        </ul>
      </section>
    </toc>
  </front>
  <middle>
    <section anchor="introduction" numbered="true" removeInRFC="false" toc="include" pn="section-1">
      <name slugifiedName="name-introduction">Introduction</name>
      <t indent="0" pn="section-1-1">YANG-CBOR <xref target="RFC9254" format="default" sectionFormat="of" derivedContent="RFC9254"/> defines
    YANG Schema Item iDentifiers (YANG SID), globally unique 63-bit
    unsigned integers used to identify YANG items. <xref target="RFC9595" format="default" sectionFormat="of" derivedContent="RFC9595"/> defines ways to allocate these SIDs using
    IANA registries.</t>
      <t indent="0" pn="section-1-2">The present specification employs these SID allocation mechanisms to
   allocate ranges of 100 000 SIDs (representation size 64 bits) 
   to each holder of an IANA Private Enterprise Number (PEN) of a value 
   below 1 000 000.  Holders of PENs of
   values smaller than 100 000 are also allocated ranges of 10 000 SIDs 
   (representation size 32 bits).</t>
      <t indent="0" pn="section-1-3">IANA has allocated a mega-range with
100 billion SIDs (representation size 64 bits) for the SID numbers 300 000 000 000 to 399 999 999 999.</t>
      <t indent="0" pn="section-1-4">IANA has also allocated a mega-range with
1 billion SIDs (representation size 32 bits) for the SID numbers 3 000 000 000 to 3 999 999 999.</t>
      <t indent="0" pn="section-1-5">PENs are registered in
<xref target="IANA.enterprise-numbers" format="default" sectionFormat="of" derivedContent="IANA.enterprise-numbers"/> using a low-threshold, low-overhead
registration process.
At the time of writing (~38 years after
registry creation), around 66 000 PENs are registered.
In this document, the registrant for a PEN is referred to as the "PEN holder".</t>
      <t indent="0" pn="section-1-6">This specification makes the following SID ranges available to
certain (current or future) PEN holders for allocation in a scheme defined
by the holder:</t>
      <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-1-7">
        <li pn="section-1-7.1">
          <t indent="0" pn="section-1-7.1.1">The holder of a PEN ppp ppp (&lt; 1 000 000) can use the SID numbers
3pp ppp p00 000 to 3pp ppp p99 999.</t>
        </li>
        <li pn="section-1-7.2">
          <t indent="0" pn="section-1-7.2.1">The holder of a PEN pp ppp (&lt; 100 000) can also use the smaller SID numbers
3 ppp pp0 000 to 3 ppp pp9 999.</t>
        </li>
      </ul>
    </section>
    <section anchor="example-sid-range-allocation-for-holder-of-pen-32473" numbered="true" removeInRFC="false" toc="include" pn="section-2">
      <name slugifiedName="name-example-sid-range-allocatio">Example: SID Range Allocation for Holder of PEN 32473</name>
      <t indent="0" pn="section-2-1"><xref target="RFC5612" format="default" sectionFormat="of" derivedContent="RFC5612"/> allocated Enterprise Number 32473 "for use in examples
in RFCs, books, documentation, and the like".</t>
      <t indent="0" pn="section-2-2">If this Enterprise Number had an actual PEN holder, the present
specification would confer control over the following SID ranges to the holder:</t>
      <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-2-3">
        <li pn="section-2-3.1">
          <t indent="0" pn="section-2-3.1.1">3<strong>03 247 3</strong>00 000 up to 3<strong>03 247 3</strong>99 999, and</t>
        </li>
        <li pn="section-2-3.2">
          <t indent="0" pn="section-2-3.2.1">3 <strong>324 73</strong>0 000 up to 3 <strong>324 73</strong>9 999.</t>
        </li>
      </ul>
      <t indent="0" pn="section-2-4">(The plaintext form of this document shows "*" characters around the
digits conveying the PEN, which are shown in <strong>boldface</strong> in the other renditions.)</t>
      <t indent="0" pn="section-2-5">As Enterprise Number 32473 is intended to be used in documentation,
the SIDs in the two SID ranges 
are consequently also available for use in documentation.</t>
    </section>
    <section anchor="discussion" numbered="true" removeInRFC="false" toc="include" pn="section-3">
      <name slugifiedName="name-discussion">Discussion</name>
      <t indent="0" pn="section-3-1">This document assigns two mega-ranges as an extremely-low-threshold (zero-interaction) way for a PEN holder to obtain a number space for the YANG
  SIDs used in their YANG modules.  If a PEN is not already available
  to the entity needing such a number space, it can be obtained through a very
  low-threshold process.  However, use of values in these mega-ranges is not
  always the recommended approach for a module author:</t>
      <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-3-2">
        <li pn="section-3-2.1">
          <t indent="0" pn="section-3-2.1.1">In the larger of the two spaces, each SID number needs a
representation size of 64 bits ("64-bit SIDs").
(This larger representation size of the absolute value of the SID is
of comparatively little consequence due to the delta-encoding used for
SIDs in YANG-CBOR.)</t>
        </li>
        <li pn="section-3-2.2">
          <t indent="0" pn="section-3-2.2.1">For the holders of PENs with values less than 100 000 in the 
  "Private Enterprise Numbers (PENs)" registry, there is another smaller 
  space of SID numbers that need a representation size of 32 bits 
  ("32-bit SIDs"). By or around 2040, the PENs with a value less than 
  100 000 are likely to be exhausted; the expectation is that there will be
  enough opportunities by that time to request SID ranges within mega-ranges 
  already allocated by other registrants that this mechanism is less needed.</t>
        </li>
        <li pn="section-3-2.3">
          <t indent="0" pn="section-3-2.3.1">This document does not define infrastructure to discover the YANG module
behind a SID in one of its ranges. Of course, each PEN holder can provide such infrastructure,
but even then the problem of how to find that infrastructure
for a SID remains.  (Search engines may mitigate this somewhat.)
On the other hand, in some cases this relative obscurity may be exactly what a PEN
holder wants to achieve by using this mechanism.  </t>
          <t indent="0" pn="section-3-2.3.2">
If obscurity is not the intention, one or both of the following
approaches are encouraged:  </t>
          <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-3-2.3.3">
            <li pn="section-3-2.3.3.1">
              <t indent="0" pn="section-3-2.3.3.1.1">The PEN holder can provide a public repository where their YANG
models can be found alongside the applicable SID files.
Such a repository may be easy to set up using a popular git forge
such as, at the time of writing, GitHub.</t>
            </li>
            <li pn="section-3-2.3.3.2">
              <t indent="0" pn="section-3-2.3.3.2.1">Implementations that employ PEN-based SIDs can facilitate
   information discovery by providing a form of a
   YANG library <xref target="RFC8525" format="default" sectionFormat="of" derivedContent="RFC8525"/>, possibly a constrained version
   <xref target="I-D.ietf-core-yang-library" format="default" sectionFormat="of" derivedContent="core-yang-library"/>.</t>
            </li>
          </ul>
        </li>
      </ul>
      <t indent="0" pn="section-3-3">Relying on the PEN registry might theoretically trigger a land grab
of PEN assignments by prospective writers of YANG modules.
However, PENs have been around for decades (see <xref section="3.1.4" sectionFormat="of" target="RFC1065" format="default" derivedLink="https://rfc-editor.org/rfc/rfc1065#section-3.1.4" derivedContent="RFC1065"/>, which continues to be in force with no technical changes as
Section <xref target="RFC1155" section="3.1.4" sectionFormat="bare" format="default" derivedLink="https://rfc-editor.org/rfc/rfc1155#section-3.1.4" derivedContent="RFC1155"/> of RFC 1155 <xref target="STD16" format="default" sectionFormat="of" derivedContent="STD16"/>), and such a land grab has not
occurred for the other allocations implicitly provided by obtaining a
PEN.</t>
    </section>
    <section anchor="iana-considerations" numbered="true" removeInRFC="false" toc="include" pn="section-4">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <t indent="0" pn="section-4-1">As summarized in <xref target="tab-allocations" format="default" sectionFormat="of" derivedContent="Table 1"/>, this document allocates the following two mega-ranges (<xref section="6.3" sectionFormat="of" target="RFC9595" format="default" derivedLink="https://rfc-editor.org/rfc/rfc9595#section-6.3" derivedContent="RFC9595"/>) in the "YANG-SID Mega-Ranges" registry 
within the "YANG SIDs" registry group <xref target="IANA.yang-sid" format="default" sectionFormat="of" derivedContent="IANA.yang-sid"/>:</t>
      <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-4-2">
        <li pn="section-4-2.1">
          <t indent="0" pn="section-4-2.1.1">1 billion SIDs ranging from 3 000 000 000 up to 3 999 999 999 (32-bit
representation size)</t>
        </li>
        <li pn="section-4-2.2">
          <t indent="0" pn="section-4-2.2.1">100 billion SIDs ranging from 300 000 000 000 up to 399 999 999 999 (64-bit
representation size)</t>
        </li>
      </ul>
      <table anchor="tab-allocations" align="center" pn="table-1">
        <name slugifiedName="name-yang-sid-mega-range-allocat">YANG-SID Mega-Range Allocations for Use by PEN Holders</name>
        <thead>
          <tr>
            <th align="left" colspan="1" rowspan="1">Entry Point</th>
            <th align="left" colspan="1" rowspan="1">Size</th>
            <th align="left" colspan="1" rowspan="1">Allocation</th>
            <th align="left" colspan="1" rowspan="1">Org Name</th>
            <th align="left" colspan="1" rowspan="1">URL</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left" colspan="1" rowspan="1">3 000 000 000</td>
            <td align="left" colspan="1" rowspan="1">1 000 000 000</td>
            <td align="left" colspan="1" rowspan="1">Private</td>
            <td align="left" colspan="1" rowspan="1">IANA</td>
            <td align="left" colspan="1" rowspan="1">https://rfc-editor.org/info/rfc9997</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">300 000 000 000</td>
            <td align="left" colspan="1" rowspan="1">100 000 000 000</td>
            <td align="left" colspan="1" rowspan="1">Private</td>
            <td align="left" colspan="1" rowspan="1">IANA</td>
            <td align="left" colspan="1" rowspan="1">https://rfc-editor.org/info/rfc9997</td>
          </tr>
        </tbody>
      </table>
      <t indent="0" pn="section-4-4">IANA has marked the following ranges as Reserved for Documentation:</t>
      <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-4-5">
        <li pn="section-4-5.1">
          <t indent="0" pn="section-4-5.1.1">303 247 300 000 up to 303 247 399 999</t>
        </li>
        <li pn="section-4-5.2">
          <t indent="0" pn="section-4-5.2.1">3 324 730 000 up to 3 324 739 999</t>
        </li>
      </ul>
      <t indent="0" pn="section-4-6">An additional contact for the allocation is: IETF CORE Working Group
(core@ietf.org) or IETF Applications and Real-Time Area
(art@ietf.org).</t>
      <t indent="0" pn="section-4-7">The allocation policy inside the mega-range is "Private" (see <xref section="6.3.2" sectionFormat="of" target="RFC9595" format="default" derivedLink="https://rfc-editor.org/rfc/rfc9595#section-6.3.2" derivedContent="RFC9595"/>).
The URL is that of the present specification.</t>
      <t indent="0" pn="section-4-8">The management of each SID block of 100 000 SIDs, ranging from
3pp ppp p00 000 to 3pp ppp p99 999, is delegated to the PEN holder
for PEN ppp ppp (i.e., the PEN holder for ppp ppp controls SID
3pp ppp p00 000 to 3pp ppp p99 999).</t>
      <t indent="0" pn="section-4-9">Similarly, the management of each SID block of 10 000 SIDs,
ranging from 3 ppp pp0 000 to 3 ppp pp9 999, is delegated to the PEN holder
for PEN pp ppp (i.e., the PEN holder for pp ppp controls SID
3 ppp pp0 000 to 3 ppp pp9 999).</t>
      <t indent="0" pn="section-4-10"><xref section="6.3.2" sectionFormat="of" target="RFC9595" format="default" derivedLink="https://rfc-editor.org/rfc/rfc9595#section-6.3.2" derivedContent="RFC9595"/> requires an organization that requests an
entry in the "YANG-SID Mega-Ranges" registry to ensure the technical
capacity to manage the SID ranges within those mega-ranges for a
period of at least 10 years (Private ranges).
The individual SID ranges within the mega-ranges allocated in this
document are assigned through the registration of PEN numbers.
The technical capacity to ensure the sustained operation of the PEN
number registry is derived from the demonstrated capacity of IANA to
maintain this registry as well as the importance of a functioning PEN
number registry in other contexts.</t>
    </section>
    <section anchor="security-considerations" numbered="true" removeInRFC="false" toc="include" pn="section-5">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <t indent="0" pn="section-5-1">The Security Considerations of <xref section="5" sectionFormat="of" target="RFC9595" format="default" derivedLink="https://rfc-editor.org/rfc/rfc9595#section-5" derivedContent="RFC9595"/> and 
<xref section="8" sectionFormat="of" target="RFC9254" format="default" derivedLink="https://rfc-editor.org/rfc/rfc9254#section-8" derivedContent="RFC9254"/> apply.
In particular, the fact that a certain Private Enterprise Number
appears in a SID is not an indicator of provenance, i.e., it does not
guarantee that the SID or underlying YANG model actually
originates from the holder of that PEN.
The requirement to ascertain the authoritative source of this
information, as discussed in the above security considerations, remains.</t>
    </section>
  </middle>
  <back>
    <displayreference target="I-D.ietf-core-yang-library" to="core-yang-library"/>
    <references anchor="sec-combined-references" pn="section-6">
      <name slugifiedName="name-references">References</name>
      <references anchor="sec-normative-references" pn="section-6.1">
        <name slugifiedName="name-normative-references">Normative References</name>
        <reference anchor="IANA.enterprise-numbers" target="https://www.iana.org/assignments/enterprise-numbers" quoteTitle="true" derivedAnchor="IANA.enterprise-numbers">
          <front>
            <title>Private Enterprise Numbers (PENs)</title>
            <author>
              <organization showOnFrontPage="true">IANA</organization>
            </author>
            <date/>
          </front>
        </reference>
        <reference anchor="IANA.yang-sid" target="https://www.iana.org/assignments/yang-sid" quoteTitle="true" derivedAnchor="IANA.yang-sid">
          <front>
            <title>YANG SIDs</title>
            <author>
              <organization showOnFrontPage="true">IANA</organization>
            </author>
          </front>
        </reference>
        <reference anchor="RFC9254" target="https://www.rfc-editor.org/info/rfc9254" quoteTitle="true" derivedAnchor="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 indent="0">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 indent="0">This document defines encoding rules for YANG in the Concise Binary Object Representation (CBOR) (RFC 8949).</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9254"/>
          <seriesInfo name="DOI" value="10.17487/RFC9254"/>
        </reference>
        <reference anchor="RFC9595" target="https://www.rfc-editor.org/info/rfc9595" quoteTitle="true" derivedAnchor="RFC9595">
          <front>
            <title>YANG Schema Item iDentifier (YANG SID)</title>
            <author fullname="M. Veillette" initials="M." role="editor" surname="Veillette"/>
            <author fullname="A. Pelov" initials="A." role="editor" surname="Pelov"/>
            <author fullname="I. Petrov" initials="I." role="editor" surname="Petrov"/>
            <author fullname="C. Bormann" initials="C." surname="Bormann"/>
            <author fullname="M. Richardson" initials="M." surname="Richardson"/>
            <date month="July" year="2024"/>
            <abstract>
              <t indent="0">YANG Schema Item iDentifiers (YANG SIDs) are globally unique 63-bit unsigned integers used to identify YANG items. SIDs provide a more compact method for identifying those YANG items that can be used efficiently, notably in constrained environments (RFC 7228). This document defines the semantics, registration processes, and assignment processes for YANG SIDs for 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>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9595"/>
          <seriesInfo name="DOI" value="10.17487/RFC9595"/>
        </reference>
      </references>
      <references anchor="sec-informative-references" pn="section-6.2">
        <name slugifiedName="name-informative-references">Informative References</name>
        <reference anchor="I-D.ietf-core-yang-library" target="https://datatracker.ietf.org/doc/html/draft-ietf-core-yang-library-03" quoteTitle="true" derivedAnchor="core-yang-library">
          <front>
            <title>Constrained YANG Module Library</title>
            <author fullname="Michel Veillette" initials="M." surname="Veillette">
              <organization showOnFrontPage="true">Trilliant Networks Inc.</organization>
            </author>
            <author fullname="Ivaylo Petrov" initials="I." surname="Petrov">
              <organization showOnFrontPage="true">Acklio</organization>
            </author>
            <date day="11" month="January" year="2021"/>
            <abstract>
              <t indent="0">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"/>
          <refcontent>Work in Progress</refcontent>
        </reference>
        <reference anchor="RFC1065" target="https://www.rfc-editor.org/info/rfc1065" quoteTitle="true" derivedAnchor="RFC1065">
          <front>
            <title>Structure and identification of management information for TCP/IP-based internets</title>
            <author fullname="K. McCloghrie" initials="K." surname="McCloghrie"/>
            <author fullname="M.T. Rose" initials="M.T." surname="Rose"/>
            <date month="August" year="1988"/>
            <abstract>
              <t indent="0">This RFC provides the common definitions for the structure and identification of management information for TCP/IP-based internets. In particular, together with its companion memos, which describe the initial management information base along with the initial network management protocol, these documents provide a simple, working architecture and system for managing TCP/IP-based internets and in particular, the Internet. This memo specifies a draft standard for the Internet community. TCP/IP implementation in the Internet which are network manageable are expected to adopt and implement this specification.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="1065"/>
          <seriesInfo name="DOI" value="10.17487/RFC1065"/>
        </reference>
        <reference anchor="RFC5612" target="https://www.rfc-editor.org/info/rfc5612" quoteTitle="true" derivedAnchor="RFC5612">
          <front>
            <title>Enterprise Number for Documentation Use</title>
            <author fullname="P. Eronen" initials="P." surname="Eronen"/>
            <author fullname="D. Harrington" initials="D." surname="Harrington"/>
            <date month="August" year="2009"/>
            <abstract>
              <t indent="0">This document describes an Enterprise Number (also known as SMI Network Management Private Enterprise Code) for use in documentation. This memo provides information for the Internet community.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5612"/>
          <seriesInfo name="DOI" value="10.17487/RFC5612"/>
        </reference>
        <reference anchor="RFC8525" target="https://www.rfc-editor.org/info/rfc8525" quoteTitle="true" derivedAnchor="RFC8525">
          <front>
            <title>YANG Library</title>
            <author fullname="A. Bierman" initials="A." surname="Bierman"/>
            <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
            <author fullname="J. Schoenwaelder" initials="J." surname="Schoenwaelder"/>
            <author fullname="K. Watsen" initials="K." surname="Watsen"/>
            <author fullname="R. Wilton" initials="R." surname="Wilton"/>
            <date month="March" year="2019"/>
            <abstract>
              <t indent="0">This document describes a YANG library that provides information about the YANG modules, datastores, and datastore schemas used by a network management server. Simple caching mechanisms are provided to allow clients to minimize retrieval of this information. This version of the YANG library supports the Network Management Datastore Architecture (NMDA) by listing all datastores supported by a network management server and the schema that is used by each of these datastores.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8525"/>
          <seriesInfo name="DOI" value="10.17487/RFC8525"/>
        </reference>
        <referencegroup anchor="STD16" target="https://www.rfc-editor.org/info/std16" derivedAnchor="STD16">
          <reference anchor="RFC1155" target="https://www.rfc-editor.org/info/rfc1155" quoteTitle="true">
            <front>
              <title>Structure and identification of management information for TCP/IP-based internets</title>
              <author fullname="M.T. Rose" initials="M.T." surname="Rose"/>
              <author fullname="K. McCloghrie" initials="K." surname="McCloghrie"/>
              <date month="May" year="1990"/>
              <abstract>
                <t indent="0">This RFC is a re-release of RFC 1065, with a changed "Status of this Memo", plus a few minor typographical corrections. The technical content of the document is unchanged from RFC 1065. [STANDARDS-TRACK]</t>
              </abstract>
            </front>
            <seriesInfo name="STD" value="16"/>
            <seriesInfo name="RFC" value="1155"/>
            <seriesInfo name="DOI" value="10.17487/RFC1155"/>
          </reference>
          <reference anchor="RFC1212" target="https://www.rfc-editor.org/info/rfc1212" quoteTitle="true">
            <front>
              <title>Concise MIB definitions</title>
              <author fullname="M.T. Rose" initials="M.T." surname="Rose"/>
              <author fullname="K. McCloghrie" initials="K." surname="McCloghrie"/>
              <date month="March" year="1991"/>
              <abstract>
                <t indent="0">This memo describes a straight-forward approach toward producing concise, yet descriptive, MIB modules. This memo defines a format for producing MIB modules. [STANDARDS-TRACK]</t>
              </abstract>
            </front>
            <seriesInfo name="STD" value="16"/>
            <seriesInfo name="RFC" value="1212"/>
            <seriesInfo name="DOI" value="10.17487/RFC1212"/>
          </reference>
        </referencegroup>
      </references>
    </references>
    <section numbered="false" anchor="acknowledgments" removeInRFC="false" toc="include" pn="section-appendix.a">
      <name slugifiedName="name-acknowledgments">Acknowledgments</name>
      <t indent="0" pn="section-appendix.a-1">This document was inspired by the discussion of the authors of
<xref target="RFC9254" format="default" sectionFormat="of" derivedContent="RFC9254"/> and <xref target="RFC9595" format="default" sectionFormat="of" derivedContent="RFC9595"/> on how to handle <contact fullname="Rob Wilton's"/> feedback.</t>
    </section>
    <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.b">
      <name slugifiedName="name-authors-address">Author's Address</name>
      <author initials="C." surname="Bormann" fullname="Carsten Bormann">
        <organization showOnFrontPage="true">Universität Bremen TZI</organization>
        <address>
          <postal>
            <street>Postfach 330440</street>
            <city>D-28359 Bremen</city>
            <country>Germany</country>
          </postal>
          <phone>+49-421-218-63921</phone>
          <email>cabo@tzi.org</email>
        </address>
      </author>
    </section>
  </back>
</rfc>
