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

<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>

<rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="std" docName="draft-ietf-mpls-msd-yang-12" number="9702" consensus="true" ipr="trust200902" obsoletes="" updates="" submissionType="IETF" xml:lang="en" tocInclude="true" symRefs="true" sortRefs="true" version="3">

  <front>
    <title abbrev="MPLS MSD YANG">YANG Data Model for Maximum Segment Identifier (SID) Depth (MSD) Types and MPLS MSD</title>
    <seriesInfo name="RFC" value="9702"/>
    <author fullname="Yingzhen Qu" initials="Y" surname="Qu">
      <organization>Futurewei Technologies</organization>
      <address>
        <email>yingzhen.ietf@gmail.com</email>
      </address>
    </author>
    <author fullname="Acee Lindem" initials="A." surname="Lindem">
      <organization>LabN Consulting, L.L.C.</organization>
      <address>
        <email>acee.ietf@gmail.com</email>
      </address>
    </author>
    <author fullname="Stephane Litkowski" initials="S" surname="Litkowski">
      <organization>Cisco Systems</organization>
      <address>
        <email>slitkows.ietf@gmail.com</email>
      </address>
    </author>
    <author fullname="Jeff Tantsura" initials="J" surname="Tantsura">
      <organization>Nvidia</organization>
      <address>
        <email>jefftant.ietf@gmail.com</email>
      </address>
    </author>
    <date month="January" year="2025"/>

    <area>RTG</area>
    <workgroup>mpls</workgroup>

<keyword>example</keyword>

    <abstract>
      <t>This document defines two YANG modules.  The first module is the
   initial version of the IANA-maintained YANG module for Maximum
   Segment Identifier (SID) Depth (MSD) Types, which includes identities
   for both the MPLS data plane and Segment Routing over IPv6 (SRv6)
   data plane.  The second module augments the IETF MPLS YANG data model to provide
   support for MPLS MSDs as defined in RFCs 8476 and 8491.</t>
    </abstract>
  </front>
  <middle>
    <section numbered="true" toc="default">
      <name>Overview</name>
      <t>There are two YANG modules <xref target="RFC7950"/> defined in this
      document. Module iana-msd-types defines the identities for Maximum SID
      Depth (MSD) Types as per the "IGP MSD-Types" IANA registry <xref
      target="IANA-IGP-MSD-Types" format="default"/>, which includes MSD types
      for both the MPLS and SRv6 data planes. This document also defines
      module ietf-mpls-msd augmenting the IETF MPLS YANG data model <xref
      target="RFC8960" format="default"/>, which augments the routing RIB data
      model <xref target="RFC8349" format="default"/> to provide operational
      state for various MSDs <xref target="RFC8662" format="default"/> for the
      MPLS data plane.  The module augments the base MPLS model with a list of
      various types of Node MSDs as well as various types of Link MSDs.
      </t>
      <t>
        The YANG modules in this document conform to the Network Management
        Datastore Architecture (NMDA) <xref target="RFC8342" format="default"/>.
      </t>
    </section>
    <section numbered="true" toc="default">
      <name>Design of the Model</name>
      <section numbered="true" toc="default">
        <name>IANA MSD Types Module</name>
        <t>
        IANA has created a registry titled "IGP MSD-Types" under the "Interior
        Gateway Protocol (IGP) Parameters" registry group to identify
        MSD-Types. Module iana-msd-types is an IANA-maintained module, which
        defines the identities for the MSD-Types as in the IANA "IGP
        MSD-Types" registry. This module references <xref target="RFC8476"/>,
        <xref target="RFC8491"/>, <xref target="RFC8662"/>, <xref
        target="RFC8664"/>, <xref target="RFC8814"/>, <xref
        target="RFC9088"/>, and <xref target="RFC9352"/>.
        </t>
        <t>
        On top of the base identity "msd-base", identity "msd-base-mpls"
        is defined to serve as the base for MSD types for the MPLS data
        plane, and identity "msd-base-srh" is defined to serve as the
        base for MSD types for the Segment Routing Header (SRH) in the IPv6
        data plane.
        </t>
        <t>
        This module is maintained by IANA and will be updated if and when
        there is any change to the registry.
        </t>
      </section>
      <section numbered="true" toc="default">
        <name>IETF MPLS MSD Module</name>
        <t>
        Module ietf-mpls-msd augments the base MPLS model <xref target="RFC8960" format="default"/>,
        and it provides support of different types of MSDs in the
        MPLS data plane.
        </t>
        <t>
        As defined in <xref target="RFC8491" format="default"/>, a Link MSD is
        the number of SIDs supported by a node's link, while a Node MSD is the
        smallest MSD supported by the node across all its links.  The module
        defines lists of MSDs and their MSD Types for a node and its links.
        Please note that these are read-only data nodes exposing a node's
        hardware capability.
        </t>
      </section>
    </section>
    <section numbered="true" toc="default">
      <name>Tree for IETF MPLS MSD Types YANG Module</name>
      <t>
      This document uses the graphical representation of data models
      per <xref target="RFC8340" format="default"/>.
      </t>

<sourcecode name="" type="yangtree">
module: ietf-mpls-msd

  augment /rt:routing/mpls:mpls:
    +--ro node-msds
       +--ro node-msd* [msd-type]
          +--ro msd-type     identityref
          +--ro msd-value?   uint8
  augment /rt:routing/mpls:mpls/mpls:interfaces/mpls:interface:
    +--ro link-msds
       +--ro link-msd* [msd-type]
          +--ro msd-type     identityref
          +--ro msd-value?   uint8
</sourcecode>

    </section>
    <section numbered="true" toc="default">
      <name>YANG Modules</name>
      <t>There are two YANG modules defined in this document.</t>
      <section anchor="iana-msd-types" numbered="true" toc="default">
        <name>IANA-Maintained Module for MSD-Types</name>
        <t>This document defines the initial version of the IANA-maintained YANG
      module for MSD Types that mirrors the IANA "IGP MSD-Types"
      registry <xref target="IANA-IGP-MSD-Types" format="default"/>.
        </t>
        <sourcecode name="iana-msd-types@2025-01-10.yang" type="yang" markers="true"><![CDATA[
module iana-msd-types {
  yang-version 1.1;
  namespace "urn:ietf:params:xml:ns:yang:iana-msd-types";
  prefix iana-msd-types;

  organization
    "Internet Assigned Numbers Authority (IANA)";

  contact
    "Internet Assigned Numbers Authority

     ICANN
     12025 Waterfront Drive, Suite 300
     Los Angeles, CA 90094-2536
     United States of America
     
     Tel:    +1 310 301 5800
     <mailto:iana@iana.org>";

  description
    "The YANG module defines the identities for Maximum Segment
     Identifier (SID) Depth (MSD) Types.

     This YANG module is maintained by IANA and reflects the 'IGP
     MSD-Types' registry.

     Copyright (c) 2025 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 initial version of this YANG module is part of RFC 9702
     (https://www.rfc-editor.org/info/rfc9702); see the RFC itself
     for full legal notices.

     The latest version of this YANG module is available at
     https://www.iana.org/assignments/yang-parameters.";

  revision 2025-01-10 {
    description
      "Initial Version";
    reference
      "RFC 9702: YANG Data Model for Maximum Segment Identifier (SID)
                 Depth Types and MPLS Maximum SID Depth";
  }

  identity msd-base {
    description
      "Base identity for Maximum SID Depth (MSD) Type. The MSD type
       definition is defined in the IANA 'IGP MSD-Types' registry.";
  }

  identity msd-base-mpls {
    base msd-base;
    description
      "Base identity of MSD types for the MPLS data plane.";
  }

  identity base-mpls-imposition-msd {
    base msd-base-mpls;
    description
      "Base MPLS Imposition MSD.";
    reference
      "RFC 8491: Signaling Maximum SID Depth (MSD) Using IS-IS
       RFC 8476: Signaling Maximum SID Depth (MSD) Using OSPF
       RFC 8664: Path Computation Element Communication Protocol
                 (PCEP) Extensions for Segment Routing
       RFC 8814: Signaling Maximum SID Depth (MSD) Using the Border
                 Gateway Protocol - Link State";
  }

  identity erld-msd {
    base msd-base-mpls;
    description
      "msd-erld is defined to advertise the Entropy Readable
       Label Depth (ERLD).";
    reference
      "RFC 8662: Entropy Label for Source Packet Routing in
                 Networking (SPRING) Tunnels
       RFC 9088: Signaling Entropy Label Capability and Entropy
                 Readable Label Depth Using IS-IS";
  }

  identity msd-base-srh {
    base msd-base;
    description
      "Base identity of MSD types for Segment Routing Header (SRH).";
  }

  identity srh-max-sl {
    base msd-base-srh;
    description
      "The Maximum Segments Left MSD type.";
    reference
      "RFC 9352: IS-IS Extensions to Support Segment Routing
                 over the IPv6 Data Plane";
  }

  identity srh-max-end-pop {
    base msd-base-srh;
    description
      "The Maximum End Pop MSD Type.";
    reference
      "RFC 9352: IS-IS Extensions to Support Segment Routing
                 over the IPv6 Data Plane";
  }

  identity srh-max-h-encaps {
    base msd-base-srh;
    description
      "The Maximum H.Encaps MSD Type.";
    reference
      "RFC 9352: IS-IS Extensions to Support Segment Routing
                 over the IPv6 Data Plane";
  }

  identity srh-max-end-d {
    base msd-base-srh;
    description
      "The Maximum End D MSD Type.";
    reference
      "RFC 9352: IS-IS Extensions to Support Segment Routing
                 over the IPv6 Data Plane";
  }
}
]]></sourcecode>
      </section>
      <section numbered="true" toc="default">
        <name>MPLS MSD YANG</name>
        <t>This document also defines a YANG module for MSD extensions 
      <xref target="RFC8476" format="default"/> <xref target="RFC8491" format="default"/> to the MPLS base 
      model as defined in <xref target="RFC8960" format="default"/>.
        </t>
        <sourcecode name="ietf-mpls-msd@2025-01-10.yang" type="yang" markers="true"><![CDATA[
module ietf-mpls-msd {
  yang-version 1.1;
  namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-msd";
  prefix mpls-msd;

  import ietf-routing {
    prefix rt;
    reference
      "RFC 8349: A YANG Data Model for Routing
                 Management (NMDA Version)";
  }
  import ietf-mpls {
    prefix mpls;
    reference
      "RFC 8960: A YANG Data Model for MPLS Base";
  }
  import iana-msd-types {
    prefix iana-msd-types;
  }

  organization
    "IETF Multiprotocol Label Switching (MPLS) Working Group";
  contact
    "WG Web:   <https://datatracker.ietf.org/wg/mpls/>
     WG List:  <mailto:mpls@ietf.org>

     Author:    Yingzhen Qu
               <mailto:yingzhen.ietf@gmail.com>
     Author:    Acee Lindem
               <mailto:acee.ietf@gmail.com>
     Author:    Stephane Litkowski
               <mailto:slitkows.ietf@gmail.com>
     Author:    Jeff Tantsura
               <mailto:jefftant.ietf@gmail.com>
     
    ";
  description
    "This YANG module augments the base MPLS model, and it is to
     provide support for different types of Maximum SID Depth (MSD).

     This YANG module conforms to the Network Management
     Datastore Architecture (NMDA) as described in RFC 8342.

     Copyright (c) 2025 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 9702;
     see the RFC itself for full legal notices.";

  revision 2025-01-10 {
    description
      "Initial Version";
    reference
      "RFC 9702: YANG Data Model for Maximum Segment Identifier (SID)
                 Depth Types and MPLS Maximum SID Depth";
  }

  grouping msd-type-value {
    description
      "Grouping for MSD type and value.";
    leaf msd-type {
      type identityref {
        base iana-msd-types:msd-base-mpls;
      }
      description
        "MSD types. The MSD type is defined in IANA 'IGP
         MSD-Types' registry.";
    }
    leaf msd-value {
      type uint8;
      description
        "MSD value, in the range of 0-255. 0 represents the lack
         of ability to support a SID stack of any depth.";
    }  
  }
  augment "/rt:routing/mpls:mpls" {
    description
      "This module augments MPLS data model (RFC 8960)
       with Node MSD.";
    container node-msds {
      config false;
      description
        "Maximum SID Depth (MSD) of a node.";
      list node-msd {
        key "msd-type";
        uses msd-type-value;
        description
          "List of different types of Node MSDs. For the same
           type, the value of Node MSD is the smallest among Link MSD
           values.";
      }
    }
  }

  augment "/rt:routing/mpls:mpls/mpls:interfaces/mpls:interface" {
    description
      "This module augments MPLS data model (RFC 8960)
       with Link MSD.";
    container link-msds {
      config false;
      description
        "Maximum SID Depth (MSD) of an interface.";
      list link-msd {
        key "msd-type";
        uses msd-type-value;
        description
          "List of different types of MSDs on the link.";
      }
    }
  }
}
]]></sourcecode>
      </section>
    </section>
    <section anchor="Security" numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>
<!-- DNE begins-->
      The YANG modules specified in this document define a schema for data
      that is designed to be accessed via network management protocols such as
      NETCONF <xref target="RFC6241" format="default"/> or RESTCONF <xref
      target="RFC8040" format="default"/>.  
The lowest NETCONF layer
is the secure transport layer, and the mandatory-to-implement secure
transport is Secure Shell (SSH) <xref target="RFC6242" format="default"/>.  The lowest RESTCONF layer
is HTTPS, and the mandatory-to-implement secure transport is TLS
<xref target="RFC8446" format="default"/>.</t>
      <t>The Network Configuration Access Control Model (NACM) <xref target="RFC8341" format="default"/> provides the 
      means to restrict access for particular NETCONF or RESTCONF users to a
      pre-configured subset of all available NETCONF or RESTCONF protocol 
      operations and content.</t>
<!-- DNE ends -->
      <t>Some of the readable data nodes in the ietf-mpls-msd YANG module
      may be considered sensitive or vulnerable in some network environments. It is
      thus important to control read access (e.g., via get, get-config, or notification)
      to these data nodes. These are the
      subtrees and data nodes and their sensitivity/vulnerability:
      </t>
          <t indent="3">/rt:routing/mpls:mpls/msd/node-msds</t>
          <t indent="3">/rt:routing/mpls:mpls/msd/link-msds</t>
          <t indent="3">Exposure of the node's maximum SID depth may be useful in mounting a
          Denial-of-Service (DoS) attack by sending packets to the node that 
          the router can't process.</t>
      <t>
      The iana-msd-types YANG module defines a set of identities that mirror
      the IANA "IGP MSD-Types" registry. These identities are intended to be reused
      by other YANG modules. The module by itself does not expose any data nodes
      that are writable or readable. As such, there are no additional security
      issues related to this YANG module that need to be considered.
      </t>
    </section>
    <section numbered="true" toc="default">
      <name>IANA Considerations</name>
      <section numbered="true" toc="default">
        <name>Registering YANG Modules</name>
        <t>This document registers URIs in the IETF XML registry 
   as defined in <xref target="RFC3688" format="default"/>.  
   The following registrations have been made:
        </t>
  <dl spacing="compact">
   <dt>URI:</dt><dd>urn:ietf:params:xml:ns:yang:iana-msd-types</dd>
   <dt>Registrant Contact:</dt><dd>The IESG.</dd>
   <dt>XML:</dt><dd>N/A; the requested URI is an XML namespace.</dd>
  </dl>
  <dl spacing="compact">
   <dt>URI:</dt><dd>urn:ietf:params:xml:ns:yang:ietf-mpls-msd</dd>
   <dt>Registrant Contact:</dt><dd>The IESG.</dd>
   <dt>XML:</dt><dd>N/A; the requested URI is an XML namespace.</dd>
  </dl>

        <t>This document registers the YANG modules in the "YANG Module Names"
   registry as defined in <xref target="RFC6020" format="default"/>.
        </t>

  <dl spacing="compact">
   <dt>Name:</dt><dd>iana-msd-types</dd>
   <dt>Maintained by IANA?</dt><dd>Y</dd>
   <dt>Namespace:</dt><dd>urn:ietf:params:xml:ns:yang:iana-msd-types</dd>
   <dt>Prefix:</dt><dd>iana-msd-types</dd>
   <dt>Reference:</dt><dd>RFC 9702</dd>
  </dl>

  <dl spacing="compact">
   <dt>Name:</dt><dd>ietf-mpls-msd</dd>
   <dt>Maintained by IANA?</dt><dd>N</dd>
   <dt>Namespace:</dt><dd>urn:ietf:params:xml:ns:yang:ietf-mpls-msd</dd>
   <dt>Prefix:</dt><dd>mpls-msd</dd>
   <dt>Reference:</dt><dd>RFC 9702</dd>
  </dl>

      </section>
      <section numbered="true" toc="default">
        <name>IANA MSD-Types Module</name>
        <t>This document defines the initial version of the IANA-maintained
      "iana-msd-types" YANG module (<xref target="iana-msd-types" format="default"/>). The latest
      version of the YANG module is available from the "YANG Parameters"
      registry <xref target="IANA-YANG-Parameters" format="default"/>.</t>
        <t>
      IANA has added this note to the "YANG Module Names" registry:
        </t>
      <blockquote>
<t>New values must not be directly added to the "iana-msd-types" YANG module. They must instead be added to the "IGP MSD-Types" registry in the "Interior Gateway Protocol (IGP) Parameters" registry group <xref target="IANA-IGP-MSD-Types" format="default"/>.</t>
      </blockquote>
        <t>
      The identities defined in the iana-msd-types YANG module are organized hierarchically
      based on the data plane. In this initial version, only MPLS and SRv6 data
      planes are supported, hence "msd-base-mpls" and "msd-base-srh" are defined.
      When a new data plane is added to the "IGP MSD-Types" registry, a new "identity"
      statement should be added to the "iana-msd-types" YANG module. The name of the
      "identity" is the prefix "msd-base-" plus a lowercase version of the data plane name.
      The identity statement should have the following sub-statements defined:</t>
        <dl newline="false" spacing="normal">
          <dt>"base":</dt>
          <dd>Contains 'msd-base'.</dd>
          <dt>"description":</dt>
          <dd>Replicates the description from "msd-base-mpls" and changes the corresponding data plane name.</dd>
          <dt>"reference":</dt>
          <dd>Replicates the reference from
            the registry with the title of the document added.</dd>
        </dl>
        <t>
      When an MSD type is added to the "IGP MSD-Types" registry, a new "identity"
      statement must be added to the "iana-msd-types" YANG module. The name of the
      "identity" is a lowercase version of the type name provided in the name with
      the space replaced with "-". The "identity" statement should have the
      following sub-statements defined:</t>
        <dl newline="false" spacing="normal">
          <dt>"base":</dt>
          <dd>Contains the base name of the corresponding data plane.</dd>
          <dt>"description":</dt>
          <dd>Replicates the name from the registry.</dd>
          <dt>"reference":</dt>
          <dd>Replicates the reference from
            the registry with the title of the document added.</dd>
        </dl>
        <t>Unassigned or reserved values are not present in the module.</t>
        <t>When the "iana-msd-types" YANG module is updated, a new "revision"
        statement with a unique revision date must be added in front of the
        existing revision statements.</t>
        <t>
      IANA has added a "Data Plane" column to the 
     "IGP MSD-Types" registry. This will unequivocally identify the 
     base identity for MSD-Types. The values for the "Data Plane"
     column for existing MSD-Types are: </t>

<table anchor="tab-1">
  <thead>
    <tr>
      <th>Value</th>
      <th>Name</th>
      <th>Data Plane</th>
      <th>Reference</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>0</td>
      <td>Reserved</td>
      <td></td>
      <td><xref target="RFC8491"/></td>
    </tr>
    <tr>
      <td>1</td>
      <td>Base MPLS Imposition MSD</td>
      <td>MPLS</td>
      <td><xref target="RFC8491"/></td>
    </tr>
    <tr>
      <td>2</td>
      <td>ERLD-MSD</td>
      <td>MPLS</td>
      <td><xref target="RFC9088"/></td>
    </tr>
    <tr>
      <td>3-40</td>
      <td>Unassigned</td>
      <td></td>
      <td></td>
    </tr>
    <tr>
      <td>41</td>
      <td>SRH Max SL</td>
      <td>SRv6</td>
      <td><xref target="RFC9352"/></td>
    </tr>
    <tr>
      <td>42</td>
      <td>SRH Max End Pop</td>
      <td>SRv6</td>
      <td><xref target="RFC9352"/></td>
    </tr>
    <tr>
      <td>43</td>
      <td>Unassigned</td>
      <td></td>
      <td></td>
    </tr>
    <tr>
      <td>44</td>
      <td>SRH Max H.encaps</td>
      <td>SRv6</td>
      <td><xref target="RFC9352"/></td>
    </tr>
    <tr>
      <td>45</td>
      <td>SRH Max End</td>
      <td>SRv6</td>
      <td><xref target="RFC9352"/></td>
    </tr>
    <tr>
      <td>46-250</td>
      <td>Unassigned</td>
      <td></td>
      <td></td>
    </tr>
    <tr>
      <td>251-254</td>
      <td>Experimental Use</td>
      <td></td>
      <td><xref target="RFC8491"/></td>
    </tr>
    <tr>
      <td>255</td>
      <td>Reserved</td>
      <td></td>
      <td><xref target="RFC8491"/></td>
    </tr>
  </tbody>
</table>

        <t>
        IANA has added this note to <xref target="IANA-IGP-MSD-Types" format="default"/>:
        </t>
    <blockquote>
            <t>When this registry is modified, the YANG module "iana-msd-types"
          must be updated as defined in RFC 9702.</t>
    </blockquote>
      </section>
    </section>
  </middle>
  <back>

    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3688.xml"/>
        <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.6242.xml"/>
        <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.8040.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8341.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8342.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8349.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8446.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8476.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8491.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8960.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9088.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9352.xml"/>

        <reference anchor="IANA-IGP-MSD-Types" target="https://www.iana.org/assignments/igp-parameters">
          <front>
            <title>IGP MSD-Types</title>
            <author>
              <organization>IANA</organization>
            </author>
            <date/>
          </front>
        </reference>

        <reference anchor="IANA-YANG-Parameters" target="https://www.iana.org/assignments/yang-parameters">
          <front>
            <title>YANG Module Names</title>
            <author>
              <organization>IANA</organization>
            </author>
            <date/>
          </front>
        </reference>

      </references>
      <references>
        <name>Informative References</name>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8340.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8662.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8664.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8814.xml"/>
      </references>
    </references>
    <section anchor="Acknowledgements" numbered="false" toc="default">
      <name>Acknowledgements</name>
      <t>The YANG data model was developed using the suite of YANG tools written
      and maintained by numerous authors.</t>
      <t>We would like to thank <contact fullname="Jan Lindblad"/>, <contact
      fullname="Tom Petch"/>, <contact fullname="Dhruv Dhody"/>, <contact
      fullname="Mohamed Boucadair"/>, and <contact fullname="Susan Hares"/>
      for their reviews and comments.</t>
    </section>
</back>
</rfc>
