<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
    <!ENTITY RFC3688 PUBLIC '' 
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3688.xml'>
    <!ENTITY RFC6020 PUBLIC '' 
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.6020.xml'>
    <!ENTITY RFC6241 PUBLIC '' 
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.6241.xml'>
    <!ENTITY RFC6242 PUBLIC '' 
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.6242.xml'>
    <!ENTITY RFC7950 PUBLIC '' 
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.7950.xml'>
    <!ENTITY RFC8040 PUBLIC '' 
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8040.xml'>
    <!ENTITY RFC8340 PUBLIC ''
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8340.xml'>
    <!ENTITY RFC8341 PUBLIC ''
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8341.xml'>
    <!ENTITY RFC8342 PUBLIC '' 
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8342.xml'>
    <!ENTITY RFC8349 PUBLIC '' 
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8349.xml'>
    <!ENTITY RFC8446 PUBLIC ''
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8446.xml'>
    <!ENTITY RFC8476 PUBLIC '' 
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8476.xml'>
    <!ENTITY RFC8491 PUBLIC '' 
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8491.xml'>
    <!ENTITY RFC8662 PUBLIC '' 
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8662.xml'>
    <!ENTITY RFC8960 PUBLIC '' 
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8960.xml'>
    <!ENTITY RFC9088 PUBLIC '' 
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.9088.xml'>
    <!ENTITY RFC9110 PUBLIC '' 
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.9110.xml'>
    <!ENTITY RFC9352 PUBLIC '' 
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.9352.xml'>
    ]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc strict="no" ?>
<?rfc toc="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>

<?rfc rfcedstyle="yes" ?>
<?rfc subcompact="no" ?>

<rfc category="std" docName="draft-ietf-mpls-msd-yang-12" ipr="trust200902">
  <!-- category values: std, bcp, info, exp, and historic
     ipr values: full3667, noModification3667, noDerivatives3667
     you can add the attributes updates="NNNN" and obsoletes="NNNN" 
     they will automatically be output with "(if approved)" -->

  <!-- ***** FRONT MATTER ***** -->

  <front>
    <!-- The abbreviated title is used in the page header - it is only necessary if the 
         full title is longer than 39 characters -->

  <title abbrev="MPLS MSD YANG">YANG Data Model for Maximum SID Depth Types and MPLS Maximum SID Depth </title>

    <!-- add 'role="editor"' below for the editors if appropriate -->

    <!-- Another author who claims to be an editor -->

    <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/>

    <!-- If the month and year are both specified and are the current ones, xml2rfc will fill 
         in the current day for you. If only the current year is specified, xml2rfc will fill 
   in the current day and month for you. If the year is not the current one, it is 
   necessary to specify at least a month (xml2rfc assumes day="1" if not specified for the 
   purpose of calculating the expiry date).  With drafts it is normally sufficient to 
   specify just the year. -->

    <!-- Meta-data Declarations -->

    <area>General</area>

    <workgroup>MPLS Working Group</workgroup>

    <!-- WG name at the upperleft corner of the doc,
         IETF is fine for individual submissions.  
   If this element is not present, the default is "Network Working Group",
         which is used by the RFC Editor as a nod to the history of the IETF. -->

    <!-- Keywords will be incorporated into HTML output
         files in a meta tag but they have no effect on text or nroff
         output. If you submit your draft to the RFC Editor, the
         keywords will be used for the search engine. -->

    <abstract>
      <t>This document defines two YANG data modules. The first
        is the initial version of the IANA-maintained YANG module for Maximum Segment Identifier (SID)
        Depths (MSDs) Types, which includes identities for both the MPLS and SRv6 data planes. The second
        augments the IETF MPLS YANG model to
        provide support for MPLS MSDs as defined in RFC 8476 and RFC 8491. </t>
    </abstract>
  </front>

  <middle>
    <section title="Overview">
      <t>There are two YANG modules defined in this document. Module 
        iana-msd-types defines the identities for Maximum Segment Identifier (SID) Depth (MSD)
        Types as per the IANA IGP MSD-Types registry <xref target="IANA-IGP-MSD-Types"/>,
        which include MSD types for both the MPLS data plane and the SRv6 data plane. This document also
        defines module ietf-mpls-msd augmenting the IETF MPLS 
      YANG model <xref target="RFC8960"/>, which itself augments the routing RIB data model 
      <xref target="RFC8349"/>, to provide operational state for 
      various MSDs<xref target="RFC8662"/> 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 MSDs on links.
      </t>
  
      <t>
        The YANG modules in this document conform to the Network Management
        Datastore Architecture (NMDA) <xref target="RFC8342"/>.
      </t>
               
    </section>
   
  <section title="Design of the Model">
    <section title="IANA MSD Types Module">
      <t>
        IANA has created an IANA-managed registry titled "IGP MSD-Types"
        under the "Interior Gateway Protocol (IGP) Parameters" registry 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.
      </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 MPLS data
        plane, and identity "msd-base-srh" is defined to serve as the
        base for MSD types for Segment Routing Header (SRH) in IPv6
        data plane.
      </t>
      <t>
        This module will be maintained by IANA and updated if and when
        there is any change to the registry.
      </t>
    </section>
    <section title="IETF MPLS MSD Module">
      <t>
        Module ietf-mpls-msd augments the base MPLS model <xref target="RFC8960"/>,
        and it provides support of different types of MSDs in 
        MPLS data plane.
      </t>
      <t>
        As defined in <xref target="RFC8491"/>, 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 interfaces.
        The module defines lists
        of MSDs with different MSD Types for a node and links. Please
        note that these are read-only data as per the node's hardware
        capability.
      </t>
    </section>
  </section>
  <section title="Tree for IETF MPLS MSD Types YANG Module">
    <t>
      This document uses the graphical representation of data models
      per <xref target="RFC8340"/>.
    </t>
    <figure align="left">
      <artwork align="left">  
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

      </artwork>
    </figure> 
  </section>
  <section title="YANG Modules">
    <t>There are two YANG modules defined in this document.</t>

    <section anchor="iana-msd-types" title="IANA-Maintained Module for MSD-Types">

    <t>This document defines the initial version of the IANA-maintained YANG
      module for MSD Types, which mirrors the IANA IGP MSD-Types
      registry <xref target="IANA-IGP-MSD-Types"/>.
    </t>
        <t>
    <figure>
      <artwork><![CDATA[
<CODE BEGINS> file "iana-msd-types@2024-07-04.yang"
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) 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 initial version of this YANG module is part of RFC XXXX
     (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself
     for full legal notices.

     //RFC Ed.: replace XXXX with actual RFC number and remove
       this note

     //RFC Ed.: replace IANA_FOO_URL and remove this note.

     The latest version of this YANG module is available at
     <IANA_FOO_URL>.";

  revision 2024-07-04 {
    description
      "Initial Version";
    reference
      "RFC XXXX: YANG Data Model for Maximum 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 IANA IGP MSD-Types registry.";
  }

  identity msd-base-mpls {
    base msd-base;
    description
      "Base identity of MSD types for 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 Segment 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";
  }
}
<CODE ENDS>
      ]]></artwork>
    </figure></t>
</section>

    <section title="MPLS MSD YANG">
    <t>This document also defines a YANG module for MSD extensions 
      <xref target="RFC8476"/><xref target="RFC8491"/> to MPLS base 
      model as defined in <xref target="RFC8960"/>.
    </t>
        <t>
    <figure>
      <artwork><![CDATA[
<CODE BEGINS> file "ietf-mpls-msd@2024-07-05.yang"
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
    "The YANG module augments the base MPLS model, and it is to
     provide support for different types of Maximum SID Depth (MSD).

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

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

  revision 2024-07-05 {
    description
      "Initial Version";
    reference
      "RFC XXXX: YANG Data Model for Maximum 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.";
      }
    }
  }
}
<CODE ENDS>
      ]]></artwork>
    </figure>
  </t> 
  </section>
  </section>

  

    <section anchor="Security" title="Security Considerations">
    <t>
      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"/> or RESTCONF <xref target="RFC8040"/>.
      These network management protocols are required to use a secure
      transport layer and mutual authentication, e.g., SSH <xref target="RFC6242"/>
      without the "none" authentication option, Transport Layer Security (TLS)
      <xref target="RFC8446"/> with mutual X.509 authentication, and HTTPS
      with HTTP authentication (Section 11 of <xref target="RFC9110"/>).</t>


   <t>The NETCONF Access Control Model (NACM) <xref target="RFC8341"/> 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> 

   <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:
      <list style="empty">
        <t>/rt:routing/mpls:mpls/msd/node-msds</t>
        <t>/rt:routing/mpls:mpls/msd/link-msds</t>
        <t>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>
      </list></t>
    <t>
      The iana-msd-types YANG module defines a set of identities, which mirrors
      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 title="IANA Considerations">
  <section title="Registering YANG Modules">
<t>This document registers URIs in the IETF XML registry 
   <xref target="RFC3688"/>.  Following the format in <xref target="RFC3688"/>, 
   the following registrations are requested to be made:
   <figure>
   <artwork>  
   URI: urn:ietf:params:xml:ns:yang:iana-msd-types
   Registrant Contact: The IESG.
   XML: N/A, the requested URI is an XML namespace.
   </artwork> 
   </figure>

   <figure>
   <artwork>  
   URI: urn:ietf:params:xml:ns:yang:ietf-mpls-msd
   Registrant Contact: The IESG.
   XML: N/A, the requested URI is an XML namespace.
   </artwork> 
   </figure>
</t>
   <t>This document registers the YANG modules in the YANG Module Names
   registry <xref target="RFC6020"/>.
   <figure>
   <figure>
   <artwork>  
   name: iana-msd-types
   Maintained by IANA?  Y
   namespace: urn:ietf:params:xml:ns:yang:iana-msd-types
   prefix: iana-msd-types
   reference: RFC XXXX
   </artwork> 
   </figure>

   <artwork>  
   name: ietf-mpls-msd
   Maintained by IANA?  N
   namespace: urn:ietf:params:xml:ns:yang:ietf-mpls-msd
   prefix: mpls-msd
   reference: RFC XXXX
   </artwork> 
   </figure>
   </t>
  </section>
  <section title="IANA MSD-Types Module">
    <t>This document defines the initial version of the IANA-maintained
      "iana-msd-types" YANG module <xref target="iana-msd-types"/>. The latest
      version of the YANG module is available from the "YANG Parameters"
      registry <xref target="IANA-YANG-Parameters"/>.</t>

    <t>
      IANA is requested to add this note to the "YANG Module Names" registry:
      <list style="empty">
        <t>MSD Types must not be added directly to the iana-msd-types YANG module.
          They must first be added to <xref target="IANA-IGP-MSD-Types"/>, which it mirrors.</t>
      </list></t>

    <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 lower-case version of the data plane name .
      The identity statement should have the following sub-statements defined:</t>
      <dl newline="false" spacing="normal" indent="15">
          <dt>"base":</dt>
          <dd>Contains 'msd-base'.</dd>
          <dt>"description":</dt>
          <dd>Replicates the description from "msd-base-mpls" and change 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. Then name of the
      "identity" is a lower-case 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" indent="15">
          <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 is requested to the add 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>
    <artwork>
    
Value      Name                      Data-Plane   Reference 
0          Reserved                  N/A          [RFC8491] 
1          Base MPLS Imposition MSD  MPLS         [RFC8491]  
2          ERLD-MSD                  MPLS         [RFC9088] 
3-40       Unassigned                N/A  
41         SRH Max SL                SRv6         [RFC9352] 
42         SRH Max End Pop           SRv6         [RFC9352] 
43         Unassigned                N/A  
44         SRH Max H.encaps          SRv6         [RFC9352] 
45         SRH Max End               SRv6         [RFC9352] 
46-250     Unassigned                N/A  
251-254    Experimental Use          N/A          [RFC8491] 
255        Reserved                  N/A          [RFC8491]
   </artwork>
    <t>
        IANA is requested to add this note to <xref target="IANA-IGP-MSD-Types"/>:
      <list style="empty">
        <t>When this registry is modified, the YANG module "iana-msd-types"
          must be updated as defined in RFC XXXX.</t>
      </list>
    </t>
  </section>
</section>
    <section anchor="Acknowledgements" title="Acknowledgements">
      <t>This document was produced using Marshall Rose's xml2rfc tool.</t>
      <t>The YANG model was developed using the suite of YANG tools written 
         and maintained by numerous authors.</t>
      <t>We would like to thank Jan Lindblad, Tom Petch, Dhruv Dhody, Mohamed Boucadair
        and Susan Hares for their reviews and comments.</t>
    </section>   
  </middle>

  <!--  *****BACK MATTER ***** -->

  <back>
    <!-- References split into informative and normative -->

    <!-- There are 2 ways to insert reference entries from the citation libraries:
     1. define an ENTITY at the top, and use "ampersand character"RFC2629; here (as shown)
     2. simply use a PI "less than character"?rfc include="reference.RFC.2119.xml"?> here
        (for I-Ds: include="reference.I-D.narten-iana-considerations-rfc2434bis.xml")

     Both are cited textually in the same manner: by using xref elements.
     If you use the PI option, xml2rfc will, by default, try to find included files in the same
     directory as the including file. You can also define the XML_LIBRARY environment variable
     with a value containing a set of directories to search.  These can be either in the local
     filing system or remote ones accessed by http (http://domain/dir/... ).-->

    <references title="Normative References">
      <!--?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"?-->
      &RFC3688;
      &RFC6020;
      &RFC6241;
      &RFC6242;
      &RFC7950;
      &RFC8040;
      &RFC8341;
      &RFC8342;
      &RFC8349;
      &RFC8446;
      &RFC8476;
      &RFC8491;
      &RFC8960;
      &RFC9088;
      &RFC9110;
      &RFC9352;
      <reference anchor="IANA-IGP-MSD-Types" target="https://www.iana.org/assignments/igp-parameters/igp-parameters.xhtml#igp-msd-types" quoteTitle="true" derivedAnchor="IANA-IGP-MSD-Types">
          <front>
            <title>IGP MSD-Types</title>
            <author>
              <organization showOnFrontPage="true">IANA</organization>
            </author>
            <date/>
          </front>
      </reference>
      <reference anchor="IANA-YANG-Parameters" target="https://www.iana.org/assignments/yang-parameters" quoteTitle="true" derivedAnchor="IANA-YANG-Parameters">
          <front>
            <title>YANG Module Names</title>
            <author>
              <organization showOnFrontPage="true">IANA</organization>
            </author>
            <date/>
          </front>
        </reference>
    </references>
    <references title="Informative References">
      <!-- Here we use entities that we defined at the beginning. -->
      &RFC8340;
      &RFC8662;
    </references>

  </back>
</rfc>
