<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" ipr="trust200902" docName="draft-ietf-teas-yang-te-44" number="10057" updates="" obsoletes="" category="std" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" xml:lang="en" prepTime="2026-11-18T22:47:26" indexInclude="true" scripts="Common,Latin" tocDepth="3">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-teas-yang-te-44" rel="prev"/>
  <link href="https://dx.doi.org/10.17487/rfc10057" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <front>
    <title abbrev="TE YANG Data Model">A YANG Data Model for Traffic Engineering Tunnels, Label Switched Paths, and Interfaces</title>
    <seriesInfo name="RFC" value="10057" stream="IETF"/>
    <author initials="T." surname="Saad" fullname="Tarek Saad">
      <organization showOnFrontPage="true">Cisco Systems Inc</organization>
      <address>
        <email>tsaad.net@gmail.com</email>
      </address>
    </author>
    <author initials="R." surname="Gandhi" fullname="Rakesh Gandhi">
      <organization showOnFrontPage="true">Cisco Systems Inc</organization>
      <address>
        <email>rgandhi@cisco.com</email>
      </address>
    </author>
    <author initials="X." surname="Liu" fullname="Xufeng Liu">
      <organization showOnFrontPage="true">Individual</organization>
      <address>
        <email>xufeng.liu.ietf@gmail.com</email>
      </address>
    </author>
    <author initials="V. P." surname="Beeram" fullname="Vishnu Pavan Beeram">
      <organization showOnFrontPage="true">Juniper Networks</organization>
      <address>
        <email>vbeeram@juniper.net</email>
      </address>
    </author>
    <author initials="I." surname="Bryskin" fullname="Igor Bryskin">
      <organization showOnFrontPage="true">Individual</organization>
      <address>
        <email>i_bryskin@yahoo.com</email>
      </address>
    </author>
    <date month="11" year="2026"/>
    <area>RTG</area>
    <workgroup>teas</workgroup>
    <keyword>YANG</keyword>
    <keyword>Traffic Engineering</keyword>
    <keyword>TE Tunnel</keyword>
    <keyword>Label Switched Path</keyword>
    <keyword>MPLS</keyword>
    <keyword>RSVP-TE</keyword>
    <keyword>Segment Routing</keyword>
    <keyword>NETCONF</keyword>
    <abstract pn="section-abstract">
      <t indent="0" pn="section-abstract-1">This document defines a YANG data model for the provisioning and management of
Traffic Engineering (TE) tunnels, Label Switched Paths (LSPs), and interfaces.
The model covers data pertinent to TE tunnels, TE LSPs, and TE interfaces that
are independent of any technology or data plane encapsulation. The model is
divided into two YANG modules that address both device-specific
and device-independent data, supporting configuration, operational state,
Remote Procedure Calls (RPCs), and event notifications.</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/rfc10057" 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" 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-terms-and-conventions">Terms and Conventions</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.2.2">
              <li pn="section-toc.1-1.2.2.1">
                <t indent="0" keepWithNext="true" pn="section-toc.1-1.2.2.1.1"><xref derivedContent="2.1" format="counter" sectionFormat="of" target="section-2.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-terminology">Terminology</xref></t>
              </li>
              <li pn="section-toc.1-1.2.2.2">
                <t indent="0" keepWithNext="true" pn="section-toc.1-1.2.2.2.1"><xref derivedContent="2.2" format="counter" sectionFormat="of" target="section-2.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-prefixes-in-data-node-names">Prefixes in Data Node Names</xref></t>
              </li>
              <li pn="section-toc.1-1.2.2.3">
                <t indent="0" pn="section-toc.1-1.2.2.3.1"><xref derivedContent="2.3" format="counter" sectionFormat="of" target="section-2.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-model-tree-diagrams">Model Tree Diagrams</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.3">
            <t indent="0" 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-design-considerations">Design Considerations</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-model-overview">Model Overview</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.4.2">
              <li pn="section-toc.1-1.4.2.1">
                <t indent="0" pn="section-toc.1-1.4.2.1.1"><xref derivedContent="4.1" format="counter" sectionFormat="of" target="section-4.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-module-relationship">Module Relationship</xref></t>
              </li>
            </ul>
          </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-te-yang-module">TE YANG Module</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.5.2">
              <li pn="section-toc.1-1.5.2.1">
                <t indent="0" pn="section-toc.1-1.5.2.1.1"><xref derivedContent="5.1" format="counter" sectionFormat="of" target="section-5.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-relationship-between-te-tun">Relationship Between TE Tunnel, LSP, and Path</xref></t>
              </li>
              <li pn="section-toc.1-1.5.2.2">
                <t indent="0" pn="section-toc.1-1.5.2.2.1"><xref derivedContent="5.2" format="counter" sectionFormat="of" target="section-5.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-module-structure">Module Structure</xref></t>
                <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.5.2.2.2">
                  <li pn="section-toc.1-1.5.2.2.2.1">
                    <t indent="0" pn="section-toc.1-1.5.2.2.2.1.1"><xref derivedContent="5.2.1" format="counter" sectionFormat="of" target="section-5.2.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-te-globals">TE Globals</xref></t>
                  </li>
                  <li pn="section-toc.1-1.5.2.2.2.2">
                    <t indent="0" pn="section-toc.1-1.5.2.2.2.2.1"><xref derivedContent="5.2.2" format="counter" sectionFormat="of" target="section-5.2.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-te-tunnels">TE Tunnels</xref></t>
                  </li>
                  <li pn="section-toc.1-1.5.2.2.2.3">
                    <t indent="0" pn="section-toc.1-1.5.2.2.2.3.1"><xref derivedContent="5.2.3" format="counter" sectionFormat="of" target="section-5.2.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-te-lsps">TE LSPs</xref></t>
                  </li>
                </ul>
              </li>
              <li pn="section-toc.1-1.5.2.3">
                <t indent="0" pn="section-toc.1-1.5.2.3.1"><xref derivedContent="5.3" format="counter" sectionFormat="of" target="section-5.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-tree-diagram">Tree Diagram</xref></t>
              </li>
              <li pn="section-toc.1-1.5.2.4">
                <t indent="0" pn="section-toc.1-1.5.2.4.1"><xref derivedContent="5.4" format="counter" sectionFormat="of" target="section-5.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-yang-module-for-traffic-eng">YANG Module for Traffic Engineering</xref></t>
              </li>
            </ul>
          </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-te-device-yang-module">TE Device YANG Module</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-module-structure-2">Module Structure</xref></t>
                <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.6.2.1.2">
                  <li pn="section-toc.1-1.6.2.1.2.1">
                    <t indent="0" pn="section-toc.1-1.6.2.1.2.1.1"><xref derivedContent="6.1.1" format="counter" sectionFormat="of" target="section-6.1.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-te-device-globals-tunnels-a">TE Device Globals, Tunnels, and LSPs</xref></t>
                  </li>
                  <li pn="section-toc.1-1.6.2.1.2.2">
                    <t indent="0" pn="section-toc.1-1.6.2.1.2.2.1"><xref derivedContent="6.1.2" format="counter" sectionFormat="of" target="section-6.1.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-te-device-interfaces">TE Device Interfaces</xref></t>
                  </li>
                </ul>
              </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-tree-diagram-2">Tree Diagram</xref></t>
              </li>
              <li pn="section-toc.1-1.6.2.3">
                <t indent="0" pn="section-toc.1-1.6.2.3.1"><xref derivedContent="6.3" format="counter" sectionFormat="of" target="section-6.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-yang-module-for-traffic-engi">YANG Module for Traffic Engineering</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.7">
            <t indent="0" pn="section-toc.1-1.7.1"><xref derivedContent="7" format="counter" sectionFormat="of" target="section-7"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-notifications">Notifications</xref></t>
          </li>
          <li pn="section-toc.1-1.8">
            <t indent="0" pn="section-toc.1-1.8.1"><xref derivedContent="8" format="counter" sectionFormat="of" target="section-8"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.9">
            <t indent="0" pn="section-toc.1-1.9.1"><xref derivedContent="9" format="counter" sectionFormat="of" target="section-9"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-security-considerations">Security Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.10">
            <t indent="0" pn="section-toc.1-1.10.1"><xref derivedContent="10" format="counter" sectionFormat="of" target="section-10"/>. <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.10.2">
              <li pn="section-toc.1-1.10.2.1">
                <t indent="0" pn="section-toc.1-1.10.2.1.1"><xref derivedContent="10.1" format="counter" sectionFormat="of" target="section-10.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t>
              </li>
              <li pn="section-toc.1-1.10.2.2">
                <t indent="0" pn="section-toc.1-1.10.2.2.1"><xref derivedContent="10.2" format="counter" sectionFormat="of" target="section-10.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.11">
            <t indent="0" pn="section-toc.1-1.11.1"><xref derivedContent="Appendix A" format="default" sectionFormat="of" target="section-appendix.a"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-data-tree-examples">Data Tree Examples</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.11.2">
              <li pn="section-toc.1-1.11.2.1">
                <t indent="0" pn="section-toc.1-1.11.2.1.1"><xref derivedContent="A.1" format="counter" sectionFormat="of" target="section-appendix.a.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-basic-tunnel-setup">Basic Tunnel Setup</xref></t>
              </li>
              <li pn="section-toc.1-1.11.2.2">
                <t indent="0" pn="section-toc.1-1.11.2.2.1"><xref derivedContent="A.2" format="counter" sectionFormat="of" target="section-appendix.a.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-global-named-path-constrain">Global Named Path Constraints</xref></t>
              </li>
              <li pn="section-toc.1-1.11.2.3">
                <t indent="0" pn="section-toc.1-1.11.2.3.1"><xref derivedContent="A.3" format="counter" sectionFormat="of" target="section-appendix.a.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-tunnel-with-global-path-con">Tunnel with Global Path Constraint</xref></t>
              </li>
              <li pn="section-toc.1-1.11.2.4">
                <t indent="0" pn="section-toc.1-1.11.2.4.1"><xref derivedContent="A.4" format="counter" sectionFormat="of" target="section-appendix.a.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-tunnel-with-per-tunnel-path">Tunnel with Per-Tunnel Path Constraint</xref></t>
              </li>
              <li pn="section-toc.1-1.11.2.5">
                <t indent="0" pn="section-toc.1-1.11.2.5.1"><xref derivedContent="A.5" format="counter" sectionFormat="of" target="section-appendix.a.5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-tunnel-state">Tunnel State</xref></t>
              </li>
              <li pn="section-toc.1-1.11.2.6">
                <t indent="0" pn="section-toc.1-1.11.2.6.1"><xref derivedContent="A.6" format="counter" sectionFormat="of" target="section-appendix.a.6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-example-te-tunnel-with-prim">Example TE Tunnel with Primary and Secondary Paths</xref></t>
              </li>
              <li pn="section-toc.1-1.11.2.7">
                <t indent="0" pn="section-toc.1-1.11.2.7.1"><xref derivedContent="A.7" format="counter" sectionFormat="of" target="section-appendix.a.7"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-example-multi-domain-te-tun">Example Multi-Domain TE Tunnel with Primary and Secondary Paths</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.12">
            <t indent="0" pn="section-toc.1-1.12.1"><xref derivedContent="Appendix B" format="default" sectionFormat="of" target="section-appendix.b"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-full-model-tree-diagram">Full Model Tree Diagram</xref></t>
          </li>
          <li pn="section-toc.1-1.13">
            <t indent="0" pn="section-toc.1-1.13.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.c"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgements">Acknowledgements</xref></t>
          </li>
          <li pn="section-toc.1-1.14">
            <t indent="0" pn="section-toc.1-1.14.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.d"/><xref derivedContent="" format="title" sectionFormat="of" target="name-contributors">Contributors</xref></t>
          </li>
          <li pn="section-toc.1-1.15">
            <t indent="0" pn="section-toc.1-1.15.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.e"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-addresses">Authors' Addresses</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">This document defines a YANG data model intended for the provisioning and management
of point-to-point Traffic Engineering (TE) tunnels, Label Switched Paths (LSPs),
and interfaces. The modeling of point-to-multipoint TE Tunnels <xref target="RFC4875" format="default" sectionFormat="of" derivedContent="RFC4875"/>
and Segment Routing (SR) Policies <xref target="RFC9256" format="default" sectionFormat="of" derivedContent="RFC9256"/> falls outside the scope of this
document.</t>
      <t indent="0" pn="section-1-2">The data model described herein is divided into two YANG modules. The "ietf-te"
module contains generic, device-independent data, and the "ietf-te-device"
module addresses device-specific data.</t>
      <t indent="0" pn="section-1-3">This document outlines the high-level relationships between the YANG modules it
defines and other external protocol YANG modules. The TE data
model intentionally excludes data specific to any signaling protocol, 
such as RSVP-TE <xref target="RFC3209" format="default" sectionFormat="of" derivedContent="RFC3209"/> <xref target="RFC3473" format="default" sectionFormat="of" derivedContent="RFC3473"/> or SR <xref target="RFC8402" format="default" sectionFormat="of" derivedContent="RFC8402"/> <xref target="RFC9256" format="default" sectionFormat="of" derivedContent="RFC9256"/> with the expectation that such technology models will be defined in separate documents
and will augment the TE model as needed.</t>
    </section>
    <section anchor="terms-and-conventions" numbered="true" removeInRFC="false" toc="include" pn="section-2">
      <name slugifiedName="name-terms-and-conventions">Terms and Conventions</name>
      <section anchor="terminology" numbered="true" removeInRFC="false" toc="include" pn="section-2.1">
        <name slugifiedName="name-terminology">Terminology</name>
        <t indent="0" pn="section-2.1-1">The following terms are defined in <xref target="RFC6241" format="default" sectionFormat="of" derivedContent="RFC6241"/> and are used in this specification:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-2.1-2">
          <li pn="section-2.1-2.1">
            <t indent="0" pn="section-2.1-2.1.1">client</t>
          </li>
          <li pn="section-2.1-2.2">
            <t indent="0" pn="section-2.1-2.2.1">configuration data</t>
          </li>
          <li pn="section-2.1-2.3">
            <t indent="0" pn="section-2.1-2.3.1">state data</t>
          </li>
        </ul>
        <t indent="0" pn="section-2.1-3">This document also makes use of the following terminology introduced in the
YANG Data Modeling Language <xref target="RFC7950" format="default" sectionFormat="of" derivedContent="RFC7950"/>:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-2.1-4">
          <li pn="section-2.1-4.1">
            <t indent="0" pn="section-2.1-4.1.1">augment</t>
          </li>
          <li pn="section-2.1-4.2">
            <t indent="0" pn="section-2.1-4.2.1">data model</t>
          </li>
          <li pn="section-2.1-4.3">
            <t indent="0" pn="section-2.1-4.3.1">data node</t>
          </li>
        </ul>
      </section>
      <section anchor="prefixes-in-data-node-names" numbered="true" removeInRFC="false" toc="include" pn="section-2.2">
        <name slugifiedName="name-prefixes-in-data-node-names">Prefixes in Data Node Names</name>
        <t indent="0" pn="section-2.2-1">In this document, names of data nodes and other data model objects are prefixed
using the standard prefix associated with the corresponding YANG imported
modules as shown in <xref target="tab1" format="default" sectionFormat="of" derivedContent="Table 1"/>.</t>
        <table anchor="tab1" align="center" pn="table-1">
          <name slugifiedName="name-prefixes-and-corresponding-">Prefixes and Corresponding YANG Modules</name>
          <thead>
            <tr>
              <th align="left" colspan="1" rowspan="1">Prefix</th>
              <th align="left" colspan="1" rowspan="1">YANG Module</th>
              <th align="left" colspan="1" rowspan="1">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left" colspan="1" rowspan="1">yang</td>
              <td align="left" colspan="1" rowspan="1">ietf-yang-types</td>
              <td align="left" colspan="1" rowspan="1">
                <xref target="RFC9911" format="default" sectionFormat="of" derivedContent="RFC9911"/></td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">inet</td>
              <td align="left" colspan="1" rowspan="1">ietf-inet-types</td>
              <td align="left" colspan="1" rowspan="1">
                <xref target="RFC9911" format="default" sectionFormat="of" derivedContent="RFC9911"/></td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">rt-types</td>
              <td align="left" colspan="1" rowspan="1">ietf-routing-types</td>
              <td align="left" colspan="1" rowspan="1">
                <xref target="RFC8294" format="default" sectionFormat="of" derivedContent="RFC8294"/></td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">te-types</td>
              <td align="left" colspan="1" rowspan="1">ietf-te-types</td>
              <td align="left" colspan="1" rowspan="1">
                <xref target="RFC10056" format="default" sectionFormat="of" derivedContent="RFC10056"/></td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">te-packet-types</td>
              <td align="left" colspan="1" rowspan="1">ietf-te-packet-types</td>
              <td align="left" colspan="1" rowspan="1">
                <xref target="RFC10056" format="default" sectionFormat="of" derivedContent="RFC10056"/></td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">te</td>
              <td align="left" colspan="1" rowspan="1">ietf-te</td>
              <td align="left" colspan="1" rowspan="1">RFC 10057</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">te-dev</td>
              <td align="left" colspan="1" rowspan="1">ietf-te-device</td>
              <td align="left" colspan="1" rowspan="1">RFC 10057</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section anchor="model-tree-diagrams" numbered="true" removeInRFC="false" toc="include" pn="section-2.3">
        <name slugifiedName="name-model-tree-diagrams">Model Tree Diagrams</name>
        <t indent="0" pn="section-2.3-1">The YANG tree diagrams extracted from the modules defined in this document are given in
subsequent sections as per the syntax defined in <xref target="RFC8340" format="default" sectionFormat="of" derivedContent="RFC8340"/>.</t>
      </section>
    </section>
    <section anchor="design-considerations" numbered="true" removeInRFC="false" toc="include" pn="section-3">
      <name slugifiedName="name-design-considerations">Design Considerations</name>
      <t indent="0" pn="section-3-1">This document describes a YANG data model for TE tunnels, TE LSPs, and TE interfaces
that are independent of any data plane technology. One of the design objectives is to allow specific
data plane technology models to reuse the TE data model and possibly
augment it with technology-specific data.</t>
      <t indent="0" pn="section-3-2">The elements of the TE data model, including TE Tunnels, LSPs, and
interfaces, have leafs that identify the technology layer where they reside.
For example, the LSP encoding type can identify the technology associated with a
TE Tunnel or LSP.</t>
      <t indent="0" pn="section-3-3">Also, the TE data model does not cover signaling protocol data.
The signaling protocols used to instantiate TE LSPs are outside the scope of this
document and are expected to be covered by augmentations defined in other documents.</t>
      <t indent="0" pn="section-3-4">The following other design considerations are taken into account with respect to data
organization:</t>
      <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-3-5">
        <li pn="section-3-5.1">
          <t indent="0" pn="section-3-5.1.1">The device-independent TE data is defined in the "ietf-te" module and
can be used to manage data off a device, such as a TE controller. When the
model is used to manage a specific device, the model contains the TE Tunnels
originating from the specific device. When the model is used to manage a TE
controller, the 'tunnel' list contains all TE Tunnels and TE tunnel segments
originating from devices that the TE controller manages.</t>
        </li>
        <li pn="section-3-5.2">
          <t indent="0" pn="section-3-5.2.1">The device-specific TE data is defined in the "ietf-te-device" module.</t>
        </li>
        <li pn="section-3-5.3">
          <t indent="0" pn="section-3-5.3.1">The TE interfaces in the "ietf-te-device" module are modeled as references
to existing interfaces defined in the 'ietf-interfaces' YANG module
<xref target="RFC8343" format="default" sectionFormat="of" derivedContent="RFC8343"/>. This approach ensures consistency by leveraging standardized
interface definitions, allowing TE-specific parameters to be associated with
interfaces already defined elsewhere, rather than redefining interface
structures within the TE module.</t>
        </li>
        <li pn="section-3-5.4">
          <t indent="0" pn="section-3-5.4.1">Minimal elements in the model are designated as "mandatory" to
allow freedom to vendors to adapt the data model to their specific product
implementation.</t>
        </li>
        <li pn="section-3-5.5">
          <t indent="0" pn="section-3-5.5.1">Suitable defaults are specified for all configurable elements.</t>
        </li>
        <li pn="section-3-5.6">
          <t indent="0" pn="section-3-5.6.1">Where TE functions or features might be optional within the
deployed TE network, the model declares them as optional.</t>
        </li>
        <li pn="section-3-5.7">
          <t indent="0" pn="section-3-5.7.1">Some groupings defined in this document include 'default' statements,
which can be problematic for use cases involving templates or profiling.
This design does not conform to the guidelines specified in <xref section="4.13" target="RFC9907" format="default" sectionFormat="of" derivedLink="https://rfc-editor.org/rfc/rfc9907#section-4.13" derivedContent="RFC9907"/>. 
However, this deviation is intentional as these groupings are specifically
tailored for use within the YANG modules defined in this document 
as well as in <xref target="I-D.ietf-teas-yang-path-computation" format="default" sectionFormat="of" derivedContent="PATH-COMP"/>.
The customization ensures appropriate behavior and consistency across these
related modules.</t>
        </li>
      </ul>
    </section>
    <section anchor="model-overview" numbered="true" removeInRFC="false" toc="include" pn="section-4">
      <name slugifiedName="name-model-overview">Model Overview</name>
      <t indent="0" pn="section-4-1">The data model defined in this document covers the core TE features that are
commonly supported by different vendor implementations. The support of extended
or vendor specific TE features is expected to be in either augmentations or
deviations to this model that are defined in separate documents.</t>
      <section anchor="module-relationship" numbered="true" removeInRFC="false" toc="include" pn="section-4.1">
        <name slugifiedName="name-module-relationship">Module Relationship</name>
        <t indent="0" pn="section-4.1-1">The TE YANG module "ietf-te" provides
device-independent building blocks that are agnostic of specific technologies
or control plane instances. The TE device YANG module, defined in the
"ietf-te-device", augments the "ietf-te" YANG module as illustrated in
<xref target="figctrl" format="default" sectionFormat="of" derivedContent="Figure 1"/> by including device-specific data such as TE interface attributes and
local TE node timers.</t>
        <t indent="0" pn="section-4.1-2">The augmentation of the TE data model for specific instances of data plane technology and
signaling protocols are outside the scope of this document.</t>
        <figure anchor="figctrl" align="left" suppress-title="false" pn="figure-1">
          <name slugifiedName="name-relationship-of-te-modules-">Relationship of TE Modules with Signaling Protocol Modules</name>
          <artwork align="left" pn="section-4.1-3.1">
     TE module      +---------+
                    | ietf-te |o-------------+
                    +---------+               \
                        o  o                   \
                        |   \                   \
                        |    \ TE device module  \
                        |     +----------------+  \
                        |     | ietf-te-device |   \
                        |     +----------------+    \
                        |        o                   \
                        |        |                    \
                        |        |                     \
                    +---------------+          +---------------+
     RSVP-TE module | ietf-rsvp-te^ |o         | ietf-te-mpls^ |
                    +---------------+ \        +---------------+
                        |              \
                        |               \
                        |                \
                        |                 \
                        |                  \
                        o                +-------------------+
                    +------------+       | ietf-rsvp-otn-te^ |
     RSVP module    | ietf-rsvp^ |       +-------------------+
                    +------------+         RSVP-TE with OTN
                                              extensions</artwork>
        </figure>
        <dl spacing="normal" newline="false" indent="3" pn="section-4.1-4">
          <dt pn="section-4.1-4.1">X---oY</dt>
          <dd pn="section-4.1-4.2">Indicates that module X augments module Y.</dd>
          <dt pn="section-4.1-4.3">^</dt>
          <dd pn="section-4.1-4.4">Indicates a module defined in other documents.</dd>
        </dl>
      </section>
    </section>
    <section anchor="te-yang-module" numbered="true" removeInRFC="false" toc="include" pn="section-5">
      <name slugifiedName="name-te-yang-module">TE YANG Module</name>
      <t indent="0" pn="section-5-1">The TE YANG module "ietf-te" supports the management and
operation of a TE network. This includes creating, modifying, and retrieving
information about TE Tunnels, LSPs, and interfaces and their associated
attributes, e.g.,  Administrative Groups (AGs), Shared Risk Link Groups (SRLGs), etc.</t>
      <t indent="0" pn="section-5-2">A full tree diagram of the TE data model is shown in <xref target="AppendixB" format="default" sectionFormat="of" derivedContent="Appendix B"/>.</t>
      <section anchor="relationship-between-te-tunnel-lsp-and-path" numbered="true" removeInRFC="false" toc="include" pn="section-5.1">
        <name slugifiedName="name-relationship-between-te-tun">Relationship Between TE Tunnel, LSP, and Path</name>
        <t indent="0" pn="section-5.1-1">The TE model is built around several core constructs: TE tunnel, TE path,
and LSP. These concepts are central to the model's structure and functionality.</t>
        <dl spacing="normal" newline="true" indent="3" pn="section-5.1-2">
          <dt pn="section-5.1-2.1">TE Tunnel:</dt>
          <dd pn="section-5.1-2.2">In this context, a TE tunnel represents a logical construct that
defines an engineered connectivity service between two endpoints in the
network, typically an ingress (source) and an egress (destination). A tunnel is
characterized by its attributes (such as name, encoding, and constraints) and
serves as the container for the forwarding resources used to realize the
desired connectivity.</dd>
          <dt pn="section-5.1-2.3">TE Path:</dt>
          <dd pn="section-5.1-2.4">A path refers to a specific sequence of nodes and links through the
network that traffic will follow to traverse the TE tunnel from source to
destination. A TE tunnel may have one or more associated TE paths, such as a primary
TE path (the preferred path) and secondary TE paths (used for protection or
restoration). Each path specifies the constraints, preferences, and
optimization criteria that guide its computation and selection.</dd>
          <dt pn="section-5.1-2.5">LSP:</dt>
          <dd pn="section-5.1-2.6">An LSP is an actual, instantiated connection in the
data plane that follows a computed TE path through the network. It is the result
of signaling protocols (such as RSVP-TE or Segment Routing) setting up
forwarding state along the TE path, enabling the tunnel to carry traffic.</dd>
        </dl>
        <t indent="0" pn="section-5.1-3">The relationship among these concepts is as follows:</t>
        <t indent="3" pn="section-5.1-4">A TE tunnel is the high-level logical object that defines the desired
connectivity and its properties. Each TE tunnel can have one or more TE paths,
which define candidate or active routes through the network that may be used to
realize the tunnel's connectivity, subject to certain constraints and
preferences. For each TE path selected for use, one or more LSPs are instantiated
in the network to realize the forwarding state necessary to carry traffic along
the specified TE path.</t>
        <t indent="0" pn="section-5.1-5">In summary, a TE tunnel defines the service, a TE path defines how to achieve the
service, and an LSP is the instantiated mechanism that actually provides the
service in the forwarding plane.</t>
      </section>
      <section anchor="module-structure" numbered="true" removeInRFC="false" toc="include" pn="section-5.2">
        <name slugifiedName="name-module-structure">Module Structure</name>
        <t indent="0" pn="section-5.2-1">The 'te' container is the top-level container in the "ietf-te" module. The
presence of the 'te' container enables TE function system-wide. Further
descriptions of containers that exist under the 'te' top-level container are
provided in the following sections.</t>
        <t indent="0" pn="section-5.2-2">The three containers grouped under the 'te'
container are shown in <xref target="fig-highlevel" format="default" sectionFormat="of" derivedContent="Figure 2"/> and described below.</t>
        <dl spacing="normal" newline="true" indent="3" pn="section-5.2-3">
          <dt pn="section-5.2-3.1">globals:</dt>
          <dd pn="section-5.2-3.2">The 'globals' container maintains the set of global TE attributes that can be
applicable to TE Tunnels and interfaces. Refer to <xref target="TeGlobals" format="default" sectionFormat="of" derivedContent="Section 5.2.1"/> for further details.</dd>
          <dt pn="section-5.2-3.3">tunnels:</dt>
          <dd pn="section-5.2-3.4">The 'tunnels' container includes the list of TE Tunnels that are instantiated.
Refer to <xref target="TE_TUNNELS" format="default" sectionFormat="of" derivedContent="Section 5.2.2"/> for further details on the properties of a TE Tunnel.</dd>
          <dt pn="section-5.2-3.5">lsps:</dt>
          <dd pn="section-5.2-3.6">The 'lsps' container includes the list of TE LSPs that are instantiated for
TE Tunnels. Refer to <xref target="TE_LSPS" format="default" sectionFormat="of" derivedContent="Section 5.2.3"/> for further details on the properties of a TE LSP.</dd>
        </dl>
        <t indent="0" pn="section-5.2-4">The model also contains two Remote Procedure Calls (RPCs) as shown
in <xref target="AppendixB" format="default" sectionFormat="of" derivedContent="Appendix B"/> and described below.</t>
        <dl spacing="normal" newline="true" indent="3" pn="section-5.2-5">
          <dt pn="section-5.2-5.1">tunnels-path-compute:</dt>
          <dd pn="section-5.2-5.2">An RPC to request path computation for a specific TE Tunnel.
The RPC allows requesting path computation using atomic and stateless operation.
A tunnel may also be configured in 'compute-only' mode to provide stateful path updates; see <xref target="TE_TUNNELS" format="default" sectionFormat="of" derivedContent="Section 5.2.2"/> for further details.</dd>
          <dt pn="section-5.2-5.3">tunnels-action:</dt>
          <dd pn="section-5.2-5.4">An RPC to request a specific action (e.g., reoptimize, or tear-and-setup) to be taken
on a specific tunnel or all tunnels.</dd>
        </dl>
        <figure anchor="fig-highlevel" align="left" suppress-title="false" pn="figure-2">
          <name slugifiedName="name-te-tunnel-high-level-yang-t">TE Tunnel High-Level YANG Tree View</name>
          <sourcecode type="yangtree" markers="false" pn="section-5.2-6.1">
module: ietf-te
  +--rw te!
     +--rw globals
     |     ...
     +--rw tunnels
     |     ...
     +--ro lsps
           ...

  rpcs:
    +---x tunnels-path-compute
    |  +---w input
    |  |     ...
    |  +--ro output
    |        ...
    +---x tunnels-actions
       +---w input
       |     ...
       +--ro output
             ...</sourcecode>
        </figure>
        <section anchor="TeGlobals" numbered="true" removeInRFC="false" toc="include" pn="section-5.2.1">
          <name slugifiedName="name-te-globals">TE Globals</name>
          <t indent="0" pn="section-5.2.1-1">The 'globals' container covers properties that control a TE feature's
behavior system-wide and its respective state as shown in <xref target="fig-globals" format="default" sectionFormat="of" derivedContent="Figure 3"/>
and described in the text that follows.</t>
          <figure anchor="fig-globals" align="left" suppress-title="false" pn="figure-3">
            <name slugifiedName="name-te-globals-yang-subtree-hig">TE Globals YANG Subtree High-Level Structure</name>
            <sourcecode type="yangtree" markers="false" pn="section-5.2.1-2.1">
     +--rw globals
     |  +--rw named-admin-groups
     |  |  +--rw named-admin-group* [name]
     |  |        ...
     |  +--rw named-srlgs
     |  |  +--rw named-srlg* [name]
     |  |        ...
     |  +--rw named-path-constraints
     |     +--rw named-path-constraint* [name]</sourcecode>
          </figure>
          <dl spacing="normal" newline="true" indent="3" pn="section-5.2.1-3">
            <dt pn="section-5.2.1-3.1">named-admin-groups:</dt>
            <dd pn="section-5.2.1-3.2">A YANG container for the list of named (extended) administrative groups that may be applied
to TE links.</dd>
            <dt pn="section-5.2.1-3.3">named-srlgs:</dt>
            <dd pn="section-5.2.1-3.4">A YANG container for the list of named SRLGs that may be
applied to TE links.</dd>
            <dt pn="section-5.2.1-3.5">named-path-constraints:</dt>
            <dd pn="section-5.2.1-3.6">
              <t indent="0" pn="section-5.2.1-3.6.1">A YANG container for a list of named path constraints. Each named path constraint is
composed of a set of constraints that can be applied during path computation.
A named path constraint can be applied to multiple TE Tunnels. Path constraints may also
be specified directly under the TE Tunnel. The path constraints specified under
the TE Tunnel take precedence over the path constraints 
derived from the referenced named path constraint. A named path constraint entry can be
formed of the path constraints shown in <xref target="fig-named-constraints" format="default" sectionFormat="of" derivedContent="Figure 4"/>:</t>
              <figure anchor="fig-named-constraints" align="left" suppress-title="false" pn="figure-4">
                <name slugifiedName="name-named-path-constraints-yang">Named Path Constraints YANG Subtree</name>
                <sourcecode type="yangtree" markers="false" pn="section-5.2.1-3.6.2.1">
|  +--rw named-path-constraints
|     +--rw named-path-constraint* [name]
|             {te-types:named-path-constraints}?
|        +--rw name                             string
|        +--rw te-bandwidth
|        |     ...
|        +--rw link-protection?                 identityref
|        +--rw setup-priority?                  uint8
|        +--rw hold-priority?                   uint8
|        +--rw signaling-type?                  identityref
|        +--rw path-metric-bounds
|        |     ...
|        +--rw path-affinities-values
|        |     ...
|        +--rw path-affinity-names
|        |     ...
|        +--rw path-srlgs-lists
|        |     ...
|        +--rw path-srlgs-names
|        |     ...
|        +--rw disjointness?
|        |       te-path-disjointness
|        +--rw explicit-route-objects
|        |     ...
|        +--rw path-in-segment!
|        |     ...
|        +--rw path-out-segment!
|              ...</sourcecode>
              </figure>
              <dl spacing="normal" newline="true" indent="3" pn="section-5.2.1-3.6.3">
                <dt pn="section-5.2.1-3.6.3.1">name:</dt>
                <dd pn="section-5.2.1-3.6.3.2">A YANG leaf that holds the named path constraint entry. This is unique in the list and used as a key.</dd>
                <dt pn="section-5.2.1-3.6.3.3">te-bandwidth:</dt>
                <dd pn="section-5.2.1-3.6.3.4">A YANG container that holds the technology-agnostic TE bandwidth constraint.</dd>
                <dt pn="section-5.2.1-3.6.3.5">link-protection:</dt>
                <dd pn="section-5.2.1-3.6.3.6">A YANG leaf that holds the link protection type constraint required for the links to be included in the computed path.</dd>
                <dt pn="section-5.2.1-3.6.3.7">setup/hold priority:</dt>
                <dd pn="section-5.2.1-3.6.3.8">YANG leafs that hold the LSP setup and hold admission priority as defined in <xref target="RFC3209" format="default" sectionFormat="of" derivedContent="RFC3209"/>.</dd>
                <dt pn="section-5.2.1-3.6.3.9">signaling-type:</dt>
                <dd pn="section-5.2.1-3.6.3.10">A YANG leaf that holds the LSP setup type, such as RSVP-TE or SR.</dd>
                <dt pn="section-5.2.1-3.6.3.11">path-metric-bounds:</dt>
                <dd pn="section-5.2.1-3.6.3.12">A YANG container that holds the set of metric bounds applicable on the
computed TE tunnel path.</dd>
                <dt pn="section-5.2.1-3.6.3.13">path-affinities-values:</dt>
                <dd pn="section-5.2.1-3.6.3.14">A YANG container that holds the set of affinity values and
mask to be used during path computation.</dd>
                <dt pn="section-5.2.1-3.6.3.15">path-affinity-names:</dt>
                <dd pn="section-5.2.1-3.6.3.16">A YANG container that holds the set of named affinity constraints and
corresponding inclusion or exclusion instructions for each to be used during path computation.</dd>
                <dt pn="section-5.2.1-3.6.3.17">path-srlgs-lists:</dt>
                <dd pn="section-5.2.1-3.6.3.18">A YANG container that holds the set of SRLG values and
corresponding inclusion or exclusion instructions to be used during path computation.</dd>
                <dt pn="section-5.2.1-3.6.3.19">path-srlgs-names:</dt>
                <dd pn="section-5.2.1-3.6.3.20">A YANG container that holds the set of named SRLG constraints and
corresponding inclusion or exclusion instructions for each to be used during path computation.</dd>
                <dt pn="section-5.2.1-3.6.3.21">disjointness:</dt>
                <dd pn="section-5.2.1-3.6.3.22">The level of resource disjointness constraint that the secondary path
of a TE tunnel has to adhere to.</dd>
                <dt pn="section-5.2.1-3.6.3.23">explicit-route-objects:</dt>
                <dd pn="section-5.2.1-3.6.3.24">
                  <t indent="0" pn="section-5.2.1-3.6.3.24.1">A YANG container that holds path constraints in the form of route entries present in the following two lists:</t>
                  <dl spacing="normal" newline="true" indent="3" pn="section-5.2.1-3.6.3.24.2">
                    <dt pn="section-5.2.1-3.6.3.24.2.1">'route-object-exclude-always':</dt>
                    <dd pn="section-5.2.1-3.6.3.24.2.2">A list of route entries that are always excluded from the path computation. The exclusion of a route entry in this list during path computation is not order sensitive. The route entries in this list have a 'strict' hop-type as described in <xref target="RFC4874" sectionFormat="comma" section="3.1" format="default" derivedLink="https://rfc-editor.org/rfc/rfc4874#section-3.1" derivedContent="RFC4874"/>.</dd>
                    <dt pn="section-5.2.1-3.6.3.24.2.3">'route-object-include-exclude':</dt>
                    <dd pn="section-5.2.1-3.6.3.24.2.4">
                      <t indent="0" pn="section-5.2.1-3.6.3.24.2.4.1">A list of route entries to include or exclude for the path computation. For route entries in this list that are to be excluded, the hop-type is only allowed to be 'strict' as described in <xref target="RFC4874" sectionFormat="comma" section="3.1" format="default" derivedLink="https://rfc-editor.org/rfc/rfc4874#section-3.1" derivedContent="RFC4874"/>.</t>
                      <t indent="0" pn="section-5.2.1-3.6.3.24.2.4.2">The constraint type (include or exclude) is specified with each route entry. The path computation considers route entry constraints in the order they appear in this list. Once a route entry constraint is consumed from this list, it is not considered any further in the computation of the TE path.</t>
                      <t indent="0" pn="section-5.2.1-3.6.3.24.2.4.3">The 'route-object-include-exclude' is used to configure constraints on which route objects (e.g., nodes, links) are included or excluded in the path computation.</t>
                      <t indent="0" pn="section-5.2.1-3.6.3.24.2.4.4">The interpretation of an empty 'route-object-include-exclude' list depends on the TE Tunnel (end-to-end or Tunnel Segment) and on the specific path according to the following rules:</t>
                      <ol spacing="normal" type="1" indent="adaptive" start="1" pn="section-5.2.1-3.6.3.24.2.4.5">
			<li pn="section-5.2.1-3.6.3.24.2.4.5.1" derivedCounter="1.">
                          <t indent="0" pn="section-5.2.1-3.6.3.24.2.4.5.1.1">An empty 'route-object-include-exclude' list for the primary path of an end-to-end TE Tunnel indicates that there are no route objects to be included or excluded in the path computation.</t>
                        </li>
                        <li pn="section-5.2.1-3.6.3.24.2.4.5.2" derivedCounter="2.">
                          <t indent="0" pn="section-5.2.1-3.6.3.24.2.4.5.2.1">An empty 'route-object-include-exclude' list for the primary path of a TE Tunnel Segment indicates that no primary LSP is required for that TE Tunnel Segment.</t>
                        </li>
                        <li pn="section-5.2.1-3.6.3.24.2.4.5.3" derivedCounter="3.">
                          <t indent="0" pn="section-5.2.1-3.6.3.24.2.4.5.3.1">An empty 'route-object-include-exclude' list for a reverse path means it always follows the forward path (i.e., the TE Tunnel is co-routed). When the 'route-object-include-exclude' list is not empty, the reverse path is routed independently of the forward path.</t>
                        </li>
                        <li pn="section-5.2.1-3.6.3.24.2.4.5.4" derivedCounter="4.">
                          <t indent="0" pn="section-5.2.1-3.6.3.24.2.4.5.4.1">An empty 'route-object-include-exclude' list for the secondary (forward) path of a TE Tunnel segment indicates that the secondary path has the same endpoints as the primary path.</t>
                        </li>
                      </ol>
                    </dd>
                  </dl>
                </dd>
                <dt pn="section-5.2.1-3.6.3.25">path-in-segment:</dt>
                <dd pn="section-5.2.1-3.6.3.26">A YANG container that contains a list of label restrictions
that have to be taken into consideration when stitching to another tunnel
segment such as at a domain boundary. The TE tunnel segment in this case
is being stitched to the upstream TE tunnel segment.</dd>
                <dt pn="section-5.2.1-3.6.3.27">path-out-segment:</dt>
                <dd pn="section-5.2.1-3.6.3.28">A YANG container that contains a list of label restrictions
that have to be taken into consideration when stitching to another tunnel
segment such as at a domain boundary. The TE tunnel segment in this case
is being stitched to the downstream TE tunnel segment.</dd>
              </dl>
            </dd>
          </dl>
        </section>
        <section anchor="TE_TUNNELS" numbered="true" removeInRFC="false" toc="include" pn="section-5.2.2">
          <name slugifiedName="name-te-tunnels">TE Tunnels</name>
          <t indent="0" pn="section-5.2.2-1">The 'tunnels' container holds the list of TE Tunnels that are provisioned on
ingress router devices in the network as shown in <xref target="fig-te-tunnel" format="default" sectionFormat="of" derivedContent="Figure 5"/>.</t>
          <figure anchor="fig-te-tunnel" align="left" suppress-title="false" pn="figure-5">
            <name slugifiedName="name-te-tunnel-yang-subtree-stru">TE Tunnel YANG Subtree Structure</name>
            <sourcecode type="yangtree" markers="false" pn="section-5.2.2-2.1">
module: ietf-te
  +--rw te
     +--rw tunnels
        +--rw tunnel* [name]
           +--rw name                            string
           +--rw alias?                          string
           +--rw identifier?                     uint32
           +--rw color?                          uint32
           +--rw description?                    string
           +--rw admin-state?                    identityref
           +--ro operational-state?              identityref
           +--rw encoding?                       identityref
           +--rw switching-type?                 identityref
           +--rw source
           |     ...
           +--rw destination
           |     ...
           +--rw bidirectional?                  boolean
           +--rw controller
           |     ...
           +--rw reoptimize-timer?               uint16
           +--rw association-objects
           |     ...
           +--rw protection
           |     ...
           +--rw restoration
           |     ...
           +--rw network-id?                     nw:network-id
           +--rw te-topology-identifier
           |     ...
           +--rw te-bandwidth
           |     ...
           +--rw link-protection?                identityref
           +--rw setup-priority?                 uint8
           +--rw hold-priority?                  uint8
           +--rw signaling-type?                 identityref
           +--rw hierarchy
           |     ...
           +--rw primary-paths
           |     ...
           +--rw secondary-paths
           |     ...
           +--rw secondary-reverse-paths
           |     ...
           +---x tunnel-action
           |     ...
           +---x protection-external-commands
                 ...</sourcecode>
          </figure>
          <t indent="0" pn="section-5.2.2-3">When the TE model is used to manage a specific device, the 'tunnel' list contains
the TE Tunnels originating from the specific device. When the model is used to
manage a TE controller, the 'tunnel' list contains all TE Tunnels and TE
tunnel segments originating from devices that the TE controller manages.</t>
          <t indent="0" pn="section-5.2.2-4">The TE Tunnel model allows the configuration and management of the following TE
tunnel objects:</t>
          <dl spacing="normal" newline="true" indent="3" pn="section-5.2.2-5">
            <dt pn="section-5.2.2-5.1">TE Tunnel:</dt>
            <dd pn="section-5.2.2-5.2">A YANG container of one or more TE LSPs established between the source and destination
TE Tunnel termination points.</dd>
            <dt pn="section-5.2.2-5.3">TE Path:</dt>
            <dd pn="section-5.2.2-5.4">An engineered path that, once instantiated in the forwarding plane, can be used
to forward traffic from the source to the destination TE Tunnel termination points.</dd>
            <dt pn="section-5.2.2-5.5">TE LSP:</dt>
            <dd pn="section-5.2.2-5.6">A TE LSP is a connection-oriented service established over a TE path
and that allows the delivery of traffic between the TE Tunnel source and
destination termination points.</dd>
            <dt pn="section-5.2.2-5.7">TE Tunnel Segment:</dt>
            <dd pn="section-5.2.2-5.8">A segment of a TE Tunnel that is stitched with other segments in order to provision an end-to-end tunnel.</dd>
          </dl>
          <t indent="0" pn="section-5.2.2-6">The TE Tunnel has a number of attributes that are set directly under the
tunnel (as shown in <xref target="fig-te-tunnel" format="default" sectionFormat="of" derivedContent="Figure 5"/>). The main attributes of a TE Tunnel are described below:</t>
          <dl spacing="normal" newline="true" indent="3" pn="section-5.2.2-7">
            <dt pn="section-5.2.2-7.1">name:</dt>
            <dd pn="section-5.2.2-7.2">A YANG leaf that holds the name of a TE Tunnel. The name of the
TE Tunnel uniquely identifies the tunnel within the TE tunnel list. The name
of the TE Tunnel can be formatted as a Uniform Resource Identifier (URI) by
including the namespace to ensure uniqueness of the name among all the TE
Tunnels present on devices and controllers. The configured TE Tunnels can
be reported with the name of the device embedded within the TE Tunnel name.
For TE Tunnels initiated by the controller, the controller is responsible
to ensure that TE Tunnel names are unique.</dd>
            <dt pn="section-5.2.2-7.3">alias:</dt>
            <dd pn="section-5.2.2-7.4">A YANG leaf that holds a user-friendly alternate name to the TE tunnel,
which is typically, but not necessarily, unique. Unlike the TE tunnel
name, the alias can be modified at any time during the lifetime of the TE tunnel.</dd>
            <dt pn="section-5.2.2-7.5">identifier:</dt>
            <dd pn="section-5.2.2-7.6">A YANG leaf that holds an identifier of the tunnel. This identifier is unique among tunnels
originated from the same ingress device.</dd>
            <dt pn="section-5.2.2-7.7">color:</dt>
            <dd pn="section-5.2.2-7.8">A YANG leaf that holds the color associated with the TE tunnel. The color is used
to map or steer services that carry matching colors onto the TE tunnel as described in
<xref target="RFC9012" format="default" sectionFormat="of" derivedContent="RFC9012"/>.</dd>
            <dt pn="section-5.2.2-7.9">admin-state:</dt>
            <dd pn="section-5.2.2-7.10">A YANG leaf that holds the tunnel administrative state.</dd>
            <dt pn="section-5.2.2-7.11">operational-state:</dt>
            <dd pn="section-5.2.2-7.12">A YANG leaf that holds the tunnel operational state.</dd>
            <dt pn="section-5.2.2-7.13">encoding/switching:</dt>
            <dd pn="section-5.2.2-7.14">The 'encoding' and 'switching-type' are YANG leafs that define the specific
technology in which the tunnel operates in as described in <xref target="RFC3945" format="default" sectionFormat="of" derivedContent="RFC3945"/>.</dd>
            <dt pn="section-5.2.2-7.15">source/destination:</dt>
            <dd pn="section-5.2.2-7.16">
              <t indent="0" pn="section-5.2.2-7.16.1">YANG containers that hold the tunnel source and destination node endpoint identities, including:</t>
              <dl spacing="normal" newline="false" indent="3" pn="section-5.2.2-7.16.2">
                <dt pn="section-5.2.2-7.16.2.1">te-node-id:</dt>
                <dd pn="section-5.2.2-7.16.2.2">A YANG leaf that holds the TE node identifier (as defined in <xref target="RFC10056" format="default" sectionFormat="of" derivedContent="RFC10056"/>) of the source or destination of the TE Tunnel.</dd>
                <dt pn="section-5.2.2-7.16.2.3">node-id:</dt>
                <dd pn="section-5.2.2-7.16.2.4">A YANG leaf that holds the node identifier (as defined in <xref target="RFC8345" format="default" sectionFormat="of" derivedContent="RFC8345"/>) of the source or destination of the TE Tunnel.</dd>
                <dt pn="section-5.2.2-7.16.2.5">tunnel-tp-id:</dt>
                <dd pn="section-5.2.2-7.16.2.6">A YANG leaf that holds the identifier of the source or destination of the TE Tunnel Termination Points (TTPs) as defined in <xref target="RFC8795" format="default" sectionFormat="of" derivedContent="RFC8795"/>. The TTP identifiers are optional on nodes that have a single TTP per node. For example, TTP identifiers are optional for packet (IP/MPLS) routers.</dd>
              </dl>
            </dd>
            <dt pn="section-5.2.2-7.17">bidirectional:</dt>
            <dd pn="section-5.2.2-7.18">A YANG leaf that, when present, indicates the LSP of a TE Tunnel is bidirectional
as defined in <xref target="RFC3473" format="default" sectionFormat="of" derivedContent="RFC3473"/>.</dd>
            <dt pn="section-5.2.2-7.19">controller:</dt>
            <dd pn="section-5.2.2-7.20">A YANG container that holds tunnel data relevant to an optional external TE controller that
may initiate or control a tunnel. This target node may be augmented by external modules, for example, to add data for Path Computation Element Communication Protocol (PCEP) initiated and/or
delegated tunnels.</dd>
            <dt pn="section-5.2.2-7.21">reoptimize-timer:</dt>
            <dd pn="section-5.2.2-7.22">A YANG leaf to set the interval period for tunnel reoptimization.</dd>
            <dt pn="section-5.2.2-7.23">association-objects:</dt>
            <dd pn="section-5.2.2-7.24">A YANG container that holds the set of associations of the TE Tunnel to other
TE Tunnels. Associations at the TE Tunnel level apply to all paths of the TE
Tunnel. The TE tunnel associations can be overridden by associations
configured directly under the TE Tunnel path.</dd>
            <dt pn="section-5.2.2-7.25">protection:</dt>
            <dd pn="section-5.2.2-7.26">A YANG container that holds the TE Tunnel protection properties.</dd>
            <dt pn="section-5.2.2-7.27">restoration:</dt>
            <dd pn="section-5.2.2-7.28">A YANG container that holds the TE Tunnel restoration properties.</dd>
            <dt pn="section-5.2.2-7.29">te-topology-identifier:</dt>
            <dd pn="section-5.2.2-7.30">A YANG container that holds the topology identifier associated with the topology where paths for the TE tunnel are computed as defined in <xref target="RFC8795" format="default" sectionFormat="of" derivedContent="RFC8795"/>.</dd>
            <dt pn="section-5.2.2-7.31">network-id:</dt>
            <dd pn="section-5.2.2-7.32">A YANG leaf that can optionally be used to identify the network topology where paths for the TE tunnel are computed as defined in <xref target="RFC8345" format="default" sectionFormat="of" derivedContent="RFC8345"/>.</dd>
            <dt pn="section-5.2.2-7.33">hierarchy:</dt>
            <dd pn="section-5.2.2-7.34">
              <t indent="0" pn="section-5.2.2-7.34.1">A YANG container that holds hierarchy related properties of the TE Tunnel. A TE LSP
  can be set up in MPLS or Generalized MPLS (GMPLS) networks to be used as
  a TE link to carry traffic in other (client) networks <xref target="RFC6107" format="default" sectionFormat="of" derivedContent="RFC6107"/>. In this
  case, the model introduces the TE Tunnel hierarchical link endpoint parameters
  to identify the specific link in the client layer that the underlying TE Tunnel is
  associated with. The hierarchy container includes the following:</t>
              <dl spacing="normal" newline="true" indent="3" pn="section-5.2.2-7.34.2">
                <dt pn="section-5.2.2-7.34.2.1">dependency-tunnels:</dt>
                <dd pn="section-5.2.2-7.34.2.2">A hierarchical set of TE Tunnels either provisioned or
to be provisioned in the immediate lower layer, upon which the
current TE Tunnel relies for multi-layer path computation. A dependency TE
Tunnel is provisioned if it has been selected by path computation to support
at least one client-layer TE Tunnel. When a dependency TE Tunnel is
provisioned, it makes the TE link operational in the client layer's network
topology, enabling the provisioning of TE Tunnels in the client layer.</dd>
                <dt pn="section-5.2.2-7.34.2.3">hierarchical-link:</dt>
                <dd pn="section-5.2.2-7.34.2.4">A YANG container that holds the identity of the
hierarchical link (in the client layer) that is supported by this TE Tunnel.
The endpoints of the hierarchical link are defined by TE tunnel source and
destination node endpoints. The hierarchical link can be identified by its source
and destination link termination point identifiers.</dd>
              </dl>
            </dd>
            <dt pn="section-5.2.2-7.35">primary-paths:</dt>
            <dd pn="section-5.2.2-7.36">
              <t indent="0" pn="section-5.2.2-7.36.1">A YANG container that holds the list of primary paths.
A primary path is identified by 'name'. A primary path is selected from the list
to instantiate a primary forwarding LSP for the tunnel. The list of primary
paths is visited by order of preference. A primary path has the following
attributes:</t>
              <dl spacing="normal" newline="true" indent="3" pn="section-5.2.2-7.36.2">
                <dt pn="section-5.2.2-7.36.2.1">primary-reverse-path:</dt>
                <dd pn="section-5.2.2-7.36.2.2">A YANG container that holds properties of the primary reverse path. The reverse path is applicable to bidirectional TE Tunnels.</dd>
                <dt pn="section-5.2.2-7.36.2.3">candidate-secondary-paths:</dt>
                <dd pn="section-5.2.2-7.36.2.4">A YANG container that holds a list of candidate
secondary paths that may be used for the primary path to support path
protection. The candidate secondary paths reference paths from the
tunnel secondary paths list. The preference of the secondary paths is
specified within the list and dictates the order of visiting the secondary
path from the list. The attributes of a secondary path can be defined
separately from the primary path. The attributes of a secondary path will be
inherited from the associated 'active' primary when not explicitly defined
for the secondary path.</dd>
              </dl>
            </dd>
            <dt pn="section-5.2.2-7.37">secondary-paths:</dt>
            <dd pn="section-5.2.2-7.38">A YANG container that holds the set of secondary paths. A secondary path is
 identified by 'name'. A secondary path can be referenced from the TE Tunnel's
'candidate-secondary-path' list.</dd>
            <dt pn="section-5.2.2-7.39">secondary-reverse-paths:</dt>
            <dd pn="section-5.2.2-7.40">A YANG container that holds the set of secondary reverse paths. A secondary reverse
path is identified by 'name'. A secondary reverse path can be referenced from the
TE Tunnel's 'candidate-secondary-reverse-paths' list. A secondary reverse path is modeled with
the same data attributes as those of the primary path.</dd>
          </dl>
          <t indent="0" pn="section-5.2.2-8">The following set of common path attributes are shared for primary (forward and reverse) and secondary paths:</t>
          <dl spacing="normal" newline="true" indent="3" pn="section-5.2.2-9">
            <dt pn="section-5.2.2-9.1">path-computation-method:</dt>
            <dd pn="section-5.2.2-9.2">A YANG leaf that specifies the method used for computing the TE path.</dd>
            <dt pn="section-5.2.2-9.3">path-computation-server:</dt>
            <dd pn="section-5.2.2-9.4">A YANG container that holds the path computation server properties when the path is
 externally queried.</dd>
            <dt pn="section-5.2.2-9.5">compute-only:</dt>
            <dd pn="section-5.2.2-9.6">A path of a TE Tunnel is, by default, provisioned so that it can be instantiated
  in the forwarding plane so that it can carry traffic.
  In some cases, a TE path may be configured only for the
  purpose of computing a path and reporting it without the need to instantiate
  the LSP or commit any resources. In such a case, the path is configured in
  'compute-only' mode to distinguish it from the default behavior. A
  'compute-only' path is configured as usual with the associated per-path
  constraints and properties on a device or TE controller. The device or TE
  controller computes the feasible paths subject to configured constraints.
  A client may query the 'compute-only' computed path properties 'on-demand',
  or alternatively, can subscribe to be notified of computed paths and
  whenever the path properties change.</dd>
            <dt pn="section-5.2.2-9.7">use-path-computation:</dt>
            <dd pn="section-5.2.2-9.8">A YANG leaf that indicates whether or not path computation is to
  be used for a specified path.</dd>
            <dt pn="section-5.2.2-9.9">lockdown:</dt>
            <dd pn="section-5.2.2-9.10">A YANG leaf that, when set, indicates the existing path should not
be globally repaired or reoptimized.</dd>
            <dt pn="section-5.2.2-9.11">path-scope:</dt>
            <dd pn="section-5.2.2-9.12">A YANG leaf that specifies whether the path is a segment or an end-to-end path.</dd>
            <dt pn="section-5.2.2-9.13">preference:</dt>
            <dd pn="section-5.2.2-9.14">A YANG leaf that specifies the preference for the path, used to
choose between paths in a list. The lower the number, the higher the
preference. Paths with the same preference are treated as equal
and other methods are used to choose between them.</dd>
            <dt pn="section-5.2.2-9.15">k-requested-paths:</dt>
            <dd pn="section-5.2.2-9.16">A YANG leaf that specifies the number of k-shortest paths requested from the path
  computation server, which are returned in order based on their computed optimization
  objective costs.</dd>
            <dt pn="section-5.2.2-9.17">association-objects:</dt>
            <dd pn="section-5.2.2-9.18">A YANG container that holds a list of tunnel association properties.</dd>
            <dt pn="section-5.2.2-9.19">optimizations:</dt>
            <dd pn="section-5.2.2-9.20">A YANG container that holds the optimization objectives
  that path computation will use to select a path.</dd>
            <dt pn="section-5.2.2-9.21">named-path-constraint:</dt>
            <dd pn="section-5.2.2-9.22">A YANG leafref that references an entry from the global list of named path constraints.</dd>
            <dt pn="section-5.2.2-9.23">te-bandwidth:</dt>
            <dd pn="section-5.2.2-9.24">A YANG container that holds the path bandwidth (see <xref target="RFC10056" format="default" sectionFormat="of" derivedContent="RFC10056"/>).</dd>
            <dt pn="section-5.2.2-9.25">link-protection:</dt>
            <dd pn="section-5.2.2-9.26">A YANG leaf that specifies the link protection type required for the links to
be included in the computed path (see <xref target="RFC10056" format="default" sectionFormat="of" derivedContent="RFC10056"/>).</dd>
            <dt pn="section-5.2.2-9.27">setup/hold-priority:</dt>
            <dd pn="section-5.2.2-9.28">See the description provided in <xref target="TeGlobals" format="default" sectionFormat="of" derivedContent="Section 5.2.1"/>. These values override
those provided in the referenced named-path-constraint.</dd>
            <dt pn="section-5.2.2-9.29">signaling-type:</dt>
            <dd pn="section-5.2.2-9.30">See the description provided in <xref target="TeGlobals" format="default" sectionFormat="of" derivedContent="Section 5.2.1"/>. This value overrides
the provided one in the referenced named-path-constraint.</dd>
            <dt pn="section-5.2.2-9.31">path-metric-bounds:</dt>
            <dd pn="section-5.2.2-9.32">See the description provided in <xref target="TeGlobals" format="default" sectionFormat="of" derivedContent="Section 5.2.1"/>. These values override
those provided in the referenced named-path-constraint.</dd>
            <dt pn="section-5.2.2-9.33">path-affinities-values:</dt>
            <dd pn="section-5.2.2-9.34">See the description provided in <xref target="TeGlobals" format="default" sectionFormat="of" derivedContent="Section 5.2.1"/>. These values override
those provided in the referenced named-path-constraint.</dd>
            <dt pn="section-5.2.2-9.35">path-affinity-names:</dt>
            <dd pn="section-5.2.2-9.36">See the description provided in <xref target="TeGlobals" format="default" sectionFormat="of" derivedContent="Section 5.2.1"/>. These values override
those provided in the referenced named-path-constraint.</dd>
            <dt pn="section-5.2.2-9.37">path-srlgs-lists:</dt>
            <dd pn="section-5.2.2-9.38">See the description provided in <xref target="TeGlobals" format="default" sectionFormat="of" derivedContent="Section 5.2.1"/>. These values override
those provided in the referenced named-path-constraint.</dd>
            <dt pn="section-5.2.2-9.39">path-srlgs-names:</dt>
            <dd pn="section-5.2.2-9.40">See the description provided in <xref target="TeGlobals" format="default" sectionFormat="of" derivedContent="Section 5.2.1"/>. These values override
those provided in the referenced named-path-constraint.</dd>
            <dt pn="section-5.2.2-9.41">disjointness:</dt>
            <dd pn="section-5.2.2-9.42">See the description provided in <xref target="TeGlobals" format="default" sectionFormat="of" derivedContent="Section 5.2.1"/>. These values override
those provided in the referenced named-path-constraint.</dd>
            <dt pn="section-5.2.2-9.43">explicit-route-objects:</dt>
            <dd pn="section-5.2.2-9.44">See the description provided in <xref target="TeGlobals" format="default" sectionFormat="of" derivedContent="Section 5.2.1"/>. These values override
those provided in the referenced named-path-constraint.</dd>
            <dt pn="section-5.2.2-9.45">path-in-segment:</dt>
            <dd pn="section-5.2.2-9.46">See the description provided in <xref target="TeGlobals" format="default" sectionFormat="of" derivedContent="Section 5.2.1"/>. These values override
those provided in the referenced named-path-constraint.</dd>
            <dt pn="section-5.2.2-9.47">path-out-segment:</dt>
            <dd pn="section-5.2.2-9.48">See the description provided in <xref target="TeGlobals" format="default" sectionFormat="of" derivedContent="Section 5.2.1"/>. These values override
those provided in the referenced named-path-constraint.</dd>
            <dt pn="section-5.2.2-9.49">computed-paths-properties:</dt>
            <dd pn="section-5.2.2-9.50">A YANG container that holds properties for the list of computed paths.</dd>
            <dt pn="section-5.2.2-9.51">computed-path-error-infos:</dt>
            <dd pn="section-5.2.2-9.52">A YANG container that holds the list of path computation error information. The
TE system populates entries in this list whenever an error is encountered during the computation of the TE path.</dd>
            <dt pn="section-5.2.2-9.53">path-compute-info:</dt>
            <dd pn="section-5.2.2-9.54">
              <t indent="0" pn="section-5.2.2-9.54.1">A YANG grouping that contains leafs representing the path attributes that are passed to the TE path computation engine to be considered during the path computation. This includes:</t>
              <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.2.2-9.54.2">
                <li pn="section-5.2.2-9.54.2.1">path constraints,</li>
                <li pn="section-5.2.2-9.54.2.2">path optimization objectives, and</li>
                <li pn="section-5.2.2-9.54.2.3">path associations.</li>
              </ul>
              <t indent="0" pn="section-5.2.2-9.54.3">Note: Unless overridden under a specific path of the TE tunnel, the TE tunnel's primary path constraints, optimization objectives, and associations are inherited by the primary reverse path, secondary path, and secondary reverse path.</t>
            </dd>
            <dt pn="section-5.2.2-9.55">lsps:</dt>
            <dd pn="section-5.2.2-9.56">A YANG container that holds a list of LSPs that have been instantiated for this specific path.</dd>
          </dl>
          <t indent="0" pn="section-5.2.2-10">In addition to the path common attributes, the primary path has the following
attributes that are not present in the secondary path:</t>
          <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.2.2-11">
            <li pn="section-5.2.2-11.1">
              <t indent="0" pn="section-5.2.2-11.1.1">Only the primary path contains the list of 'candidate-secondary-paths' that
can protect the primary path.</t>
            </li>
            <li pn="section-5.2.2-11.2">
              <t indent="0" pn="section-5.2.2-11.2.1">Only the primary path can contain a primary-reverse-path associated with the
primary path (and its associated list of
'candidate-secondary-reverse-path').</t>
            </li>
          </ul>
          <dl spacing="normal" newline="true" indent="3" pn="section-5.2.2-12">
            <dt pn="section-5.2.2-12.1">lsp-provisioning-error-infos:</dt>
            <dd pn="section-5.2.2-12.2">A YANG container that holds the list of LSP provisioning error information. The
TE system populates entries in this list whenever an error is encountered during the LSP provisioning.</dd>
          </dl>
        </section>
        <section anchor="TE_LSPS" numbered="true" removeInRFC="false" toc="include" pn="section-5.2.3">
          <name slugifiedName="name-te-lsps">TE LSPs</name>
          <t indent="0" pn="section-5.2.3-1">The 'lsps' container includes the set of TE LSPs that have been instantiated.
A TE LSP is identified by a 3-tuple ('tunnel-name', 'lsp-id', 'node').</t>
          <t indent="0" pn="section-5.2.3-2">When the model is used to manage a specific device, the 'lsps' list contains all TE
LSPs that traverse the device (including ingressing, transiting, and egressing the device).</t>
          <t indent="0" pn="section-5.2.3-3">When the model is used to manage a TE controller, the 'lsps' list contains the TE LSPs on devices managed by the controller that act as ingress, and may optionally include TE LSPs on devices managed by the controller that act as a transit or egress role.</t>
        </section>
      </section>
      <section anchor="tree-diagram" numbered="true" removeInRFC="false" toc="include" pn="section-5.3">
        <name slugifiedName="name-tree-diagram">Tree Diagram</name>
        <t indent="0" pn="section-5.3-1"><xref target="fig-te-tree" format="default" sectionFormat="of" derivedContent="Figure 6"/> shows the YANG tree diagram of depth=4 for the TE YANG module
"ietf-te". The full tree diagram is shown in <xref target="AppendixB" format="default" sectionFormat="of" derivedContent="Appendix B"/>.</t>
        <figure anchor="fig-te-tree" align="left" suppress-title="false" pn="figure-6">
          <name slugifiedName="name-tree-diagram-of-depth-4-of-">Tree Diagram of Depth-4 of TE Tunnels</name>
          <sourcecode type="yangtree" markers="false" pn="section-5.3-2.1">
module: ietf-te
  +--rw te
     +--rw enable?    boolean
     +--rw globals
     |  +--rw named-admin-groups
     |  |  +--rw named-admin-group* [name]
     |  |          {te-types:extended-admin-groups,
     |  |           te-types:named-extended-admin-groups}?
     |  |        ...
     |  +--rw named-srlgs
     |  |  +--rw named-srlg* [name] {te-types:named-srlg-groups}?
     |  |        ...
     |  +--rw named-path-constraints
     |     +--rw named-path-constraint* [name]
     |             {te-types:named-path-constraints}?
     |           ...
     +--rw tunnels
     |  +--rw tunnel* [name]
     |     +--rw name                            string
     |     +--rw alias?                          string
     |     +--rw identifier?                     uint32
     |     +--rw color?                          uint32
     |     +--rw description?                    string
     |     +--rw admin-state?                    identityref
     |     +--ro operational-state?              identityref
     |     +--rw encoding?                       identityref
     |     +--rw switching-type?                 identityref
     |     +--rw source
     |     |     ...
     |     +--rw destination
     |     |     ...
     |     +--rw bidirectional?                  boolean
     |     +--rw controller
     |     |     ...
     |     +--rw reoptimize-timer?               uint16
     |     +--rw association-objects
     |     |     ...
     |     +--rw protection
     |     |     ...
     |     +--rw restoration
     |     |     ...
     |     +--rw network-id?                     nw:network-id
     |     +--rw te-topology-identifier
     |     |     ...
     |     +--rw te-bandwidth
     |     |     ...
     |     +--rw link-protection?                identityref
     |     +--rw setup-priority?                 uint8
     |     +--rw hold-priority?                  uint8
     |     +--rw signaling-type?                 identityref
     |     +--rw hierarchy
     |     |     ...
     |     +--rw primary-paths
     |     |     ...
     |     +--rw secondary-paths
     |     |     ...
     |     +--rw secondary-reverse-paths
     |     |     ...
     |     +---x tunnel-action
     |     |     ...
     |     +---x protection-external-commands
     |           ...
     +--ro lsps
        +--ro lsp* [tunnel-name lsp-id node]
           +--ro tunnel-name                         string
           +--ro lsp-id                              uint16
           +--ro node
           |       te-types:te-node-id
           +--ro source?
           |       te-types:te-node-id
           +--ro destination?
           |       te-types:te-node-id
           +--ro tunnel-id?                          uint16
           +--ro extended-tunnel-id?
           |       yang:dotted-quad
           +--ro operational-state?                  identityref
           +--ro signaling-type?                     identityref
           +--ro origin-type?                        enumeration
           +--ro lsp-resource-status?                enumeration
           +--ro lockout-of-normal?                  boolean
           +--ro freeze?                             boolean
           +--ro lsp-protection-role?                enumeration
           +--ro lsp-protection-state?               identityref
           +--ro ingress-node-id?
           |       te-types:te-node-id
           +--ro egress-node-id?
           |       te-types:te-node-id
           +--ro lsp-actual-route-information
                 ...

  rpcs:
    +---x tunnels-path-compute
    |  +---w input
    |  |  +---w path-compute-info
    |  +--ro output
    |     +--ro path-compute-result
    +---x tunnels-actions
       +---w input
       |  +---w tunnel-info
       |  |  +---w (filter-type)
       |  |        ...
       |  +---w action-info
       |     +---w action?       identityref
       |     +---w disruptive?   empty
       +--ro output
          +--ro action-result?   identityref</sourcecode>
        </figure>
      </section>
      <section anchor="yang-module" numbered="true" removeInRFC="false" toc="include" pn="section-5.4">
        <name slugifiedName="name-yang-module-for-traffic-eng">YANG Module for Traffic Engineering</name>
        <t indent="0" pn="section-5.4-1">The TE YANG module "ietf-te" imports the following modules:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.4-2">
          <li pn="section-5.4-2.1">
            <t indent="0" pn="section-5.4-2.1.1">ietf-te-types defined in <xref target="RFC10056" format="default" sectionFormat="of" derivedContent="RFC10056"/></t>
          </li>
          <li pn="section-5.4-2.2">
            <t indent="0" pn="section-5.4-2.2.1">ietf-yang-types and ietf-inet-types defined in <xref target="RFC9911" format="default" sectionFormat="of" derivedContent="RFC9911"/></t>
          </li>
          <li pn="section-5.4-2.3">
            <t indent="0" pn="section-5.4-2.3.1">ietf-network and ietf-network-topology defined in <xref target="RFC8345" format="default" sectionFormat="of" derivedContent="RFC8345"/></t>
          </li>
        </ul>
        <t indent="0" pn="section-5.4-3">This module references the following documents:
<xref target="RFC4206" format="default" sectionFormat="of" derivedContent="RFC4206"/>, <xref target="RFC4427" format="default" sectionFormat="of" derivedContent="RFC4427"/>,
<xref target="RFC4872" format="default" sectionFormat="of" derivedContent="RFC4872"/>, <xref target="RFC3209" format="default" sectionFormat="of" derivedContent="RFC3209"/>, <xref target="RFC6780" format="default" sectionFormat="of" derivedContent="RFC6780"/>,
<xref target="RFC7471" format="default" sectionFormat="of" derivedContent="RFC7471"/>, <xref target="RFC9012" format="default" sectionFormat="of" derivedContent="RFC9012"/>, <xref target="RFC8570" format="default" sectionFormat="of" derivedContent="RFC8570"/>,
<xref target="RFC8232" format="default" sectionFormat="of" derivedContent="RFC8232"/>, <xref target="RFC7271" format="default" sectionFormat="of" derivedContent="RFC7271"/>, <xref target="RFC8234" format="default" sectionFormat="of" derivedContent="RFC8234"/>, <xref target="RFC4655" format="default" sectionFormat="of" derivedContent="RFC4655"/>, <xref target="RFC8231" format="default" sectionFormat="of" derivedContent="RFC8231"/>, <xref target="RFC7308" format="default" sectionFormat="of" derivedContent="RFC7308"/>, <xref target="RFC8345" format="default" sectionFormat="of" derivedContent="RFC8345"/>, <xref target="RFC9256" format="default" sectionFormat="of" derivedContent="RFC9256"/>, and <xref target="ITU_G.808.1" format="default" sectionFormat="of" derivedContent="ITU_G.808.1"/>.</t>
        <sourcecode markers="true" name="ietf-te@2026-11-18.yang" type="yang" pn="section-5.4-4">
module ietf-te {
  yang-version 1.1;
  namespace "urn:ietf:params:xml:ns:yang:ietf-te";

  prefix te;

  /* Import TE generic types */

  import ietf-te-types {
    prefix te-types;
    reference
      "RFC 10056: Common YANG Data Types for Traffic Engineering";
  }
  import ietf-yang-types {
    prefix yang;
    reference
      "RFC 9911: Common YANG Data Types";
  }

  import ietf-network {
    prefix nw;
    reference
      "RFC 8345: A YANG Data Model for Network Topologies";
  }

  import ietf-network-topology {
    prefix nt;
    reference
      "RFC 8345: A YANG Data Model for Network Topologies";
  }

  organization
    "IETF Traffic Engineering Architecture and Signaling (TEAS)
     Working Group.";
  contact
    "WG Web:   &lt;https://datatracker.ietf.org/wg/teas/&gt;
     WG List:  &lt;mailto:teas@ietf.org&gt;

     Editor:   Tarek Saad
               &lt;mailto:tsaad.net@gmail.com&gt;

     Editor:   Rakesh Gandhi
               &lt;mailto:rgandhi@cisco.com&gt;

     Editor:   Vishnu Pavan Beeram
               &lt;mailto:vbeeram@juniper.net&gt;

     Editor:   Xufeng Liu
               &lt;mailto: xufeng.liu.ietf@gmail.com&gt;

     Editor:   Igor Bryskin
               &lt;mailto:i_bryskin@yahoo.com&gt;";

  description
    "YANG data module for TE configuration, state, and RPCs.

     Copyright (c) 2026 IETF Trust and the persons identified as
     authors of the code. All rights reserved.

     Redistribution and use in source and binary forms, with or
     without modification, is permitted pursuant to, and subject to
     the license terms contained in, the Revised BSD License set
     forth in Section 4.c of the IETF Trust's Legal Provisions
     Relating to IETF Documents
     (https://trustee.ietf.org/license-info).

     All revisions of IETF and IANA published modules can be found at
     the YANG Parameters registry group:
     https://www.iana.org/assignments/yang-parameters.

     This version of this YANG module is part of RFC 10057; see
     the RFC itself for full legal notices.";

  revision 2026-11-18 {
    description
      "Initial revision for the TE generic YANG module.";
    reference
      "RFC 10057: A YANG Data Model for Traffic Engineering Tunnels,
       Label Switched Paths, and Interfaces";
  }

  typedef tunnel-ref {
    type leafref {
      path "/te:te/te:tunnels/te:tunnel/te:name";
      require-instance false;
    }
    description
      "This type is used by data models that need to reference
       a configured TE tunnel.";
  }

  /**
   * TE tunnel generic groupings
   */

  grouping path-common-properties {
    description
      "Common path attributes.";
    leaf name {
      type string;
      description
        "TE path name.";
    }
    leaf symbolic-name {
      type string;
      description
        "The symbolic path name is a human-readable string that
         identifies an LSP in the network. The symbolic path name
         must remain constant throughout an LSP's lifetime.";
      reference
        "RFC 8231: Path Computation Element Communication Protocol
                   (PCEP) Extensions for Stateful PCE,
                   Section 7.3.2";
    }
    leaf path-computation-method {
      type identityref {
        base te-types:path-computation-method;
      }
      default "te-types:path-locally-computed";
      description
        "The method used for computing the path, either
         locally computed, queried from a server or not
         computed at all (explicitly configured).";
    }
    container path-computation-server {
      when "derived-from-or-self(../path-computation-method, "
         + "'te-types:path-externally-queried')" {
        description
          "The IP address or the TE identifier of the external
           path computation server.";
      }
      uses te-types:te-generic-node-id;
      description
        "Address of the external path computation
         server.";
    }
    leaf compute-only {
      when "../use-path-computation = 'true'" {
        description
          "Applicable when path computation is requested.";
      }
      type empty;
      description
        "When present, the path is computed, but no resources
         are committed or reserved in the network. The path may
         be recomputed upon topology changes.";
    }
    leaf use-path-computation {
      when "derived-from-or-self(../path-computation-method, "
         + "'te-types:path-locally-computed')";
      type boolean;
      default "true";
      description
        "When 'true' indicates the path is dynamically computed
         and/or validated against the Traffic-Engineering Database
         (TED), and when 'false' indicates no path expansion or
         validation against the TED is required.";
    }
    leaf lockdown {
      type empty;
      description
        "When present, indicates the existing path should not be
         globally repaired or reoptimized.";
    }
    leaf path-scope {
      type identityref {
        base te-types:path-scope-type;
      }
      default "te-types:path-scope-end-to-end";
      config false;
      description
        "Indicates whether the path is a segment or portion of
         the full path, or is an end-to-end path for
         the TE Tunnel.";
    }
  }

  grouping path-compute-info {
    description
      "Attributes used for path computation request.";
    uses tunnel-associations-properties;
    uses te-types:generic-path-optimization;
    leaf named-path-constraint {
      if-feature "te-types:named-path-constraints";
      type leafref {
        path "/te:te/te:globals/te:named-path-constraints/"
           + "te:named-path-constraint/te:name";
      }
      description
        "Reference to a globally defined named path constraint set.";
    }
    uses path-constraints-common;
  }

  grouping path-forward-properties {
    description
      "The path preference.";
    leaf preference {
      type uint8 {
        range "1..255";
      }
      default "1";
      description
        "Specifies a preference for this path. The lower the number,
         the higher the preference.";
    }
    leaf co-routed {
      when "/te:te/te:tunnels/te:tunnel/te:bidirectional = 'true'" {
        description
          "Applicable to bidirectional tunnels only.";
      }
      type boolean;
      default "false";
      description
        "When set to true, indicates whether the reverse path must
         be co-routed with the primary.";
    }
  }

  grouping k-requested-paths {
    description
      "The k-shortest paths requests.";
    leaf k-requested-paths {
      type uint8;
      default "1";
      description
        "The number of k-shortest paths requested from the path
         computation server, which are returned in order based on
         their computed optimization objective costs.";
    }
  }

  grouping path-state {
    description
      "TE per path state parameters.";
    uses path-computation-response;
    container lsp-provisioning-error-infos {
      config false;
      description
        "LSP provisioning error information.";
      list lsp-provisioning-error-info {
        description
          "List of LSP provisioning error info entries.";
        leaf error-reason {
          type identityref {
            base te-types:lsp-provisioning-error-reason;
          }
          description
            "LSP provision error type.";
        }
        leaf error-description {
          type string;
          description
            "The textual representation of the error that occurred
             during LSP provisioning.";
        }
        leaf error-timestamp {
          type yang:date-and-time;
          description
            "Timestamp of when the reported error occurred.";
        }
        leaf error-node-id {
          type te-types:te-node-id;
          description
            "Node identifier of node where error occurred.";
        }
        leaf error-link-id {
          type te-types:te-tp-id;
          description
            "Link ID where the error occurred.";
        }
        leaf lsp-id {
          type uint16;
          description
            "The LSP-ID for which LSP provisioning error was
             returned.";
        }
      }
    }
    container lsps {
      config false;
      description
        "The TE LSPs container.";
      list lsp {
        key "node lsp-id";
        description
          "List of LSPs associated with the tunnel.";
        leaf tunnel-name {
          type leafref {
            path "/te:te/te:lsps/te:lsp/te:tunnel-name";
          }
          description
            "TE tunnel name.";
        }
        leaf node {
          type leafref {
            path "/te:te/te:lsps/te:lsp[tunnel-name="
               + "current()/../te:tunnel-name][lsp-id="
               + "current()/../te:lsp-id]/te:node";
          }
          description
            "The node where the LSP state resides.";
        }
        leaf lsp-id {
          type leafref {
            path "/te:te/te:lsps/te:lsp[tunnel-name="
               + "current()/../tunnel-name]/te:lsp-id";
          }
          description
            "The TE LSP identifier.";
        }
        leaf state-change-timestamp {
          type yang:date-and-time;
          description
            "Indicates the time at which the LSP operational
             state was last updated.";
        }
      }
    }
  }

  grouping path-computation-response {
    description
      "Attributes reported by path computation response.";
    container computed-paths-properties {
      config false;
      description
        "Computed path properties container.";
      list computed-path-properties {
        key "k-index";
        description
          "List of computed paths.";
        leaf k-index {
          type uint8;
          description
            "The k-th path returned from the computation server.
             A lower k value path is more optimal than higher k
             value paths.";
        }
        uses te-types:generic-path-properties {
          augment "path-properties" {
            description
              "Additional path properties returned by path
               computation.";
            uses te-types:te-bandwidth;
            leaf disjointness-type {
              type te-types:te-path-disjointness;
              description
                "The type of resource disjointness.
                 When reported for a primary path, it represents the
                 minimum level of disjointness of all the secondary
                 paths. When reported for a secondary path, it
                 represents the disjointness of the secondary path.";
            }
            leaf last-computed-timestamp {
              type yang:date-and-time;
              description
                "Timestamp of when the path was last computed.";
            }
          }
        }
      }
    }
    container computed-path-error-infos {
      config false;
      description
        "Path computation information container.";
      list computed-path-error-info {
        description
          "List of path computation info entries.";
        leaf error-description {
          type string;
          description
            "Textual representation of the error that occurred
             during path computation.";
        }
        leaf error-timestamp {
          type yang:date-and-time;
          description
            "Timestamp of last path computation attempt.";
        }
        leaf error-reason {
          type identityref {
            base te-types:path-computation-error-reason;
          }
          description
            "Reason for the path computation error.";
        }
      }
    }
  }

  grouping protection-restoration-properties {
    description
      "Protection and restoration parameters.";
    container protection {
      description
        "Protection parameters.";
      leaf protection-type {
        type identityref {
          base te-types:lsp-protection-type;
        }
        default "te-types:lsp-protection-unprotected";
        description
          "LSP protection type.";
      }
      leaf protection-reversion-disable {
        type boolean;
        default "false";
        description
          "Disable protection reversion to working path.";
      }
      leaf hold-off-time {
        type uint32;
        units "milliseconds";
        description
          "The time interval from the declaration of a Signal Fail
           (SF) or Signal Degrade (SD) condition until the protect-
           ion switching algorithm is initiated to maintain service
           continuity.";
        reference
          "RFC 4427: Recovery (Protection and Restoration)
                     Terminology for Generalized Multi-Protocol
                     Label Switching (GMPLS)";
      }
      leaf wait-to-revert {
        type uint16;
        units "seconds";
        description
          "Time to wait before attempting LSP reversion.";
        reference
          "RFC 4427: Recovery (Protection and Restoration)
                     Terminology for Generalized Multi-Protocol
                     Label Switching (GMPLS)";
      }
      leaf aps-signal-id {
        type uint8 {
          range "1..255";
        }
        default "1";
        description
          "The Automatic Protection Switching (APS) signal number
           used to reference the traffic of this tunnel. The default
           value for normal traffic is 1.
           The default value for extra-traffic is 255. If not
           specified, non-default values can be assigned by the
           server, if and only if, the server controls both
            endpoints.";
        reference
          "ITU_G.808.1: Generic protection switching - Linear trail
                        and subnetwork protection";
      }
    }
    container restoration {
      description
        "Restoration parameters.";
      leaf restoration-type {
        type identityref {
          base te-types:lsp-restoration-type;
        }
        description
          "LSP restoration type.";
      }
      leaf restoration-scheme {
        type identityref {
          base te-types:restoration-scheme-type;
        }
        description
          "LSP restoration scheme.";
      }
      leaf restoration-reversion-disable {
        type boolean;
        default "false";
        description
          "When 'true', disables restoration reversion to the working
           path.";
      }
      leaf hold-off-time {
        type uint32;
        units "milliseconds";
        description
          "The time interval from the declaration of a Signal Fail
           (SF) or Signal Degrade (SD) condition until the protect-
           ion switching algorithm is initiated to maintain service
           continuity.";
        reference
          "RFC 4427: Recovery (Protection and Restoration)
                     Terminology for Generalized Multi-Protocol
                     Label Switching (GMPLS)";
      }
      leaf wait-to-restore {
        type uint16;
        units "seconds";
        description
          "Time to wait before attempting LSP restoration.";
        reference
          "RFC 4427: Recovery (Protection and Restoration)
                     Terminology for Generalized Multi-Protocol
                     Label Switching (GMPLS)";
      }
      leaf wait-to-revert {
        type uint16;
        units "seconds";
        description
          "Time to wait before attempting LSP reversion.";
        reference
          "RFC 4427: Recovery (Protection and Restoration)
                     Terminology for Generalized Multi-Protocol
                     Label Switching (GMPLS)";
      }
    }
  }

  grouping tunnel-associations-properties {
    description
      "TE tunnel association grouping.";
    container association-objects {
      description
        "TE tunnel associations.";
      list association-object {
        key "association-key";
        unique "type id source/id source/type";
        description
          "List of association base objects.";
        reference
          "RFC 4872: RSVP-TE Extensions in Support of End-to-End
                     Generalized Multi-Protocol Label Switching
                     (GMPLS) Recovery";
        leaf association-key {
          type string;
          description
            "Association key used to identify a specific
             association in the list.";
        }
        leaf type {
          type identityref {
            base te-types:association-type;
          }
          description
            "Association type.";
          reference
            "RFC 4872: RSVP-TE Extensions in Support of End-to-End
                       Generalized Multi-Protocol Label Switching
                       (GMPLS) Recovery";
        }
        leaf id {
          type uint16;
          description
            "Association identifier.";
          reference
            "RFC 4872: RSVP-TE Extensions in Support of End-to-End
                       Generalized Multi-Protocol Label Switching
                       (GMPLS) Recovery";
        }
        container source {
          uses te-types:te-generic-node-id;
          description
            "Association source.";
          reference
            "RFC 4872: RSVP-TE Extensions in Support of End-to-End
                       Generalized Multi-Protocol Label Switching
                       (GMPLS) Recovery";
        }
      }
      list association-object-extended {
        key "association-key";
        unique
          "type id source/id source/type global-source extended-id";
        description
          "List of extended ASSOCIATION objects.";
        reference
          "RFC 6780: RSVP ASSOCIATION Object Extensions";
        leaf association-key {
          type string;
          description
            "Association key used to identify a specific
             association in the list.";
        }
        leaf type {
          type identityref {
            base te-types:association-type;
          }
          description
            "Association type.";
          reference
            "RFC 4427: Recovery (Protection and Restoration)
                       Terminology for Generalized Multi-Protocol
                       Label Switching (GMPLS)
             RFC 6780: RSVP ASSOCIATION Object Extensions";
        }
        leaf id {
          type uint16;
          description
            "Association identifier.";
          reference
            "RFC 4427: Recovery (Protection and Restoration)
                       Terminology for Generalized Multi-Protocol
                       Label Switching (GMPLS)
             RFC 6780: RSVP ASSOCIATION Object Extensions";
        }
        container source {
          uses te-types:te-generic-node-id;
          description
            "Association source.";
          reference
            "RFC 4427: Recovery (Protection and Restoration)
                       Terminology for Generalized Multi-Protocol
                       Label Switching (GMPLS)
             RFC 6780: RSVP ASSOCIATION Object Extensions";
        }
        leaf global-source {
          type uint32;
          description
            "Association global source.";
          reference
            "RFC 6780: RSVP ASSOCIATION Object Extensions";
        }
        leaf extended-id {
          type yang:hex-string;
          description
            "Association extended identifier.";
          reference
            "RFC 6780: RSVP ASSOCIATION Object Extensions";
        }
      }
    }
  }

  grouping tunnel-end-point {
    description
      "Common grouping used to specify the tunnel source and
       destination end-points.";
    leaf node-id {
      type nw:node-id;
      description
        "The TE tunnel end-point node identifier.";
    }
    leaf te-node-id {
      type te-types:te-node-id;
      description
        "The TE tunnel end-point TE node identifier.";
    }
    leaf tunnel-tp-id {
      when '../node-id or ../te-node-id' {
        description
          "The TE tunnel termination point identifier is local to
           a node.";
      }
      type binary;
      description
        "The TE tunnel end-point TE tunnel termination point
         identifier.";
    }
  }

  /* Some of the groupings defined in this module are reused
   * in the ietf-te-path-computation YANG module
   * defined in draft-ietf-teas-yang-path-computation */
  grouping tunnel-common-attributes {
    description
      "Common grouping to define the TE tunnel parameters.";
    container source {
      description
        "TE tunnel source end-point.";
      uses tunnel-end-point;
    }
    container destination {
      description
        "TE tunnel destination end-point.";
      uses tunnel-end-point;
    }
    leaf bidirectional {
      type boolean;
      default "false";
      description
        "When 'true', it indicates a bidirectional tunnel.";
    }
  }

  /* This grouping is reused in the ietf-te-path-computation YANG
   * module defined in draft-ietf-teas-yang-path-computation */
  grouping tunnel-hierarchy-properties {
    description
      "A grouping for TE tunnel hierarchy information.";
    container hierarchy {
      description
        "Container for TE hierarchy related information.";
      container dependency-tunnels {
        description
          "List of tunnels that this tunnel can be potentially
           dependent on.";
        list dependency-tunnel {
          key "name";
          description
            "A tunnel entry that this tunnel can potentially depend
             on.";
          leaf name {
            type tunnel-ref;
            description
              "Dependency tunnel name. The tunnel may not have been
               instantiated yet.";
          }
          uses te-types:encoding-and-switching-type;
        }
      }
      container hierarchical-link {
        description
          "Identifies a hierarchical link (in client layer)
           that this tunnel is associated with. By default, the
           topology of the hierarchical link is the same topology of
           the tunnel.";
        reference
          "RFC 4206: Label Switched Paths (LSP) Hierarchy with
                     Generalized Multi-Protocol Label Switching
                     (GMPLS) Traffic Engineering (TE)";
        leaf enable {
          type boolean;
          default "false";
          description
            "When 'true', enables the hierarchical link properties
             supported by this tunnel.";
        }
        leaf local-node-id {
          type nw:node-id;
          description
            "The local node identifier.";
        }
        leaf local-te-node-id {
          type te-types:te-node-id;
          description
            "The local TE node identifier.";
        }
        leaf local-link-tp-id {
          type nt:tp-id;
          description
            "The local link termination point identifier.";
          reference
            "RFC 8345: A YANG Data Model for Network Topologies";
        }
        leaf local-te-link-tp-id {
          type te-types:te-tp-id;
          description
            "The local TE link termination point identifier.";
        }
        leaf remote-node-id {
          type nw:node-id;
          description
            "The remote node identifier.";
        }
        leaf remote-link-tp-id {
          type nt:tp-id;
          description
            "The remote link termination point identifier.";
          reference
            "RFC 8345: A YANG Data Model for Network Topologies";
        }
        leaf remote-te-link-tp-id {
          type te-types:te-tp-id;
          description
            "The remote TE link termination point identifier.";
        }
        leaf remote-te-node-id {
          type te-types:te-node-id;
          description
            "Remote TE node identifier.";
        }
        leaf link-id {
          type nt:link-id;
          description
            "A network topology assigned identifier to the link.";
          reference
            "RFC 8345: A YANG Data Model for Network Topologies";
        }
        leaf network-id {
          type nw:network-id;
          description
            "The network topology identifier where the hierarchical
             link supported by this TE tunnel is instantiated.";
        }
        uses te-types:te-topology-identifier {
          description
            "The TE topology identifier where the hierarchical link
             supported by this TE tunnel is instantiated.";
        }
      }
    }
  }

  grouping path-constraints-common {
    description
      "Global named path constraints configuration
       grouping.";
    uses te-types:common-path-constraints-attributes;
    uses te-types:generic-path-disjointness;
    uses te-types:path-constraints-route-objects;
    container path-in-segment {
      presence "The end-to-end tunnel starts in a previous domain;
                this tunnel is a segment in the current domain.";
      description
        "If an end-to-end tunnel crosses multiple domains using
         the same technology, some additional constraints have to be
         taken in consideration in each domain.
         This TE tunnel segment is stitched to the upstream TE tunnel
         segment.";
      uses te-types:label-set-info;
    }
    container path-out-segment {
      presence
        "The end-to-end tunnel is not terminated in this domain;
         this tunnel is a segment in the current domain.";
      description
        "If an end-to-end tunnel crosses multiple domains using
         the same technology, some additional constraints have to be
         taken in consideration in each domain.
         This TE tunnel segment is stitched to the downstream TE
         tunnel segment.";
      uses te-types:label-set-info;
    }
  }

  /**
   * TE container
   */

  container te {
    description
      "TE global container.";
    leaf enable {
      type boolean;
      description
        "When 'true', the TE component features are enabled.";
    }

    /* TE Global Data */
    container globals {
      description
        "Globals TE system-wide configuration data container.";
      container named-admin-groups {
        description
          "TE named admin groups container.";
        list named-admin-group {
          if-feature "te-types:extended-admin-groups";
          if-feature "te-types:named-extended-admin-groups";
          key "name";
          description
            "List of named TE admin-groups.";
          leaf name {
            type string;
            description
              "A name that uniquely identifies a TE
               interface named admin-group.";
          }
          leaf bit-position {
            type uint32;
            description
              "Bit-position value for a named Administrative Group
               (AG). The value is an integer that represents one of
               the bit positions in the administrative group bitmask.
               Values for bit-positions between 0 and 31 are
               interpreted as the original 32 bit AGs. Values of bit-
               positions &gt;=32 are interpreted as Extended
               Administrative Group (EAG) values as per RFC 7308.";
            reference
              "RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels
               RFC 7308: Extended Administrative Groups in MPLS
                         Traffic Engineering (MPLS-TE)";
          }


        }
      }
      container named-srlgs {
        description
          "TE named SRLGs container.";
        list named-srlg {
          if-feature "te-types:named-srlg-groups";
          key "name";
          description
            "A list of named SRLG groups.";
          leaf name {
            type string;
            description
              "A name that uniquely identifies a TE
               interface named SRLG.";
          }
          leaf value {
            type te-types:srlg;
            description
              "An SRLG value.";
          }
          leaf cost {
            type uint32;
            description
              "The cost associated with an SRLG. This is used as
               a penalty during path computation when the TE path
               traverses a link with this SRLG.";
          }
        }
      }
      container named-path-constraints {
        description
          "TE named path constraints container.";
        list named-path-constraint {
          if-feature "te-types:named-path-constraints";
          key "name";
          leaf name {
            type string;
            description
              "A unique identifier for a set of path constraints.
               Operators should ensure that when this model is used
               to manage multiple devices, the parameters associated
               with the set of path constraints sharing the same name
               remain consistent across those devices in order to
               maintain uniform path behavior.";
          }
          uses path-constraints-common;
          description
            "A list of named path constraints.";
        }
      }
    }

    /* TE Tunnel Data */
    container tunnels {
      description
        "Tunnels TE configuration data container.";
      list tunnel {
        key "name";
        description
          "The list of TE tunnels.";
        leaf name {
          type string;
          description
            "TE tunnel name.";
        }
        leaf alias {
          type string;
          description
            "An alternate name of the TE tunnel that can be modified
             anytime during its lifetime.";
        }
        leaf identifier {
          type uint32;
          description
            "A numeric identifier for the tunnel, unique within the
             scope of the ingress node. While the 'name' leaf serves
             as a human-readable management key, this
             'identifier' corresponds to the Tunnel ID used in
             control plane signaling (e.g., the RSVP-TE SESSION
             object as defined in RFC 3209), allowing for
             correlation between management state and network-wide
             signaling.";
          reference
            "RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels";
        }
        leaf color {
          type uint32;
          description
            "A TE Tunnel (RFC 3209) can be associated with an intent
             or objective (e.g., low latency) by tagging it with a
             color. This color attribute is used as a guiding
             criterion for mapping services onto the TE Tunnel
             (RFC 9012) (RFC 9256).";
          reference
            "RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels
             RFC 9012: The BGP Tunnel Encapsulation Attribute
             RFC 9256: Segment Routing Policy Architecture";
        }
        leaf description {
          type string;
          default "None";
          description
            "Textual description for this TE tunnel.";
        }
        leaf admin-state {
          type identityref {
            base te-types:tunnel-admin-state-type;
          }
          default "te-types:tunnel-admin-state-up";
          description
            "TE tunnel administrative state.";
        }
        leaf operational-state {
          type identityref {
            base te-types:tunnel-state-type;
          }
          config false;
          description
            "TE tunnel operational state.";
        }
        leaf state-change-timestamp {
          type yang:date-and-time;
          description
            "Indicates the time at which the TE tunnel's operational
             state was last updated.";
        }
        uses te-types:encoding-and-switching-type;
        uses tunnel-common-attributes;
        container controller {
          description
            "Contains tunnel data relevant to external controllers.
             This target node may be augmented by external modules,
             for example, to add data for PCEP initiated and/or
             delegated tunnels.";
          leaf protocol-origin {
            type identityref {
              base te-types:protocol-origin-type;
            }
            description
              "The protocol origin for instantiating the tunnel.";
          }
          leaf controller-entity-id {
            type string;
            description
              "An identifier that is associated with the entity that
               controls the tunnel as defined in RFC 8232.";
            reference
              "RFC 8232: Optimizations of Label Switched Path State
                         Synchronization Procedures for a Stateful
                         PCE";
          }
        }
        leaf reoptimize-timer {
          type uint16;
          units "seconds";
          description
            "Frequency of reoptimization of a traffic-engineered
             LSP. A value of 0 means that the LSP is never
             reoptimized.";
        }
        uses tunnel-associations-properties;
        uses protection-restoration-properties;
        uses te-types:tunnel-constraints;
        uses tunnel-hierarchy-properties;
        container primary-paths {
          description
            "The set of primary paths.";
          reference
            "RFC 4872: RSVP-TE Extensions in Support of End-to-End
                       Generalized Multi-Protocol Label Switching
                       (GMPLS) Recovery";
          list primary-path {
            key "name";
            description
              "List of primary paths for this tunnel.";
            leaf active {
              type boolean;
              config false;
              description
                "When 'true', indicates an active path has been
                 selected from the primary paths list.";
            }
            uses path-common-properties;
            uses path-forward-properties;
            uses k-requested-paths;
            uses path-compute-info;
            uses path-state;
            container primary-reverse-path {
              when "../../../te:bidirectional = 'true'";
              description
                "The reverse primary path properties.";
              uses path-common-properties;
              uses path-compute-info;
              uses path-state;
              container candidate-secondary-reverse-paths {
                description
                  "The set of referenced candidate reverse secondary
                   paths from the full set of secondary reverse paths
                   which may be used for this primary path.";
                list candidate-secondary-reverse-path {
                  key "secondary-reverse-path";
                  ordered-by user;
                  description
                    "List of candidate secondary reverse paths.";
                  leaf secondary-reverse-path {
                    type leafref {
                      path "../../../../../../"
                         + "te:secondary-reverse-paths/"
                         + "te:secondary-reverse-path/te:name";
                    }
                    description
                      "A reference to the secondary reverse path that
                       may be utilized when the containing primary
                       reverse path is in use.";
                  }
                  leaf active {
                    type boolean;
                    config false;
                    description
                      "When 'true', indicates an active path has been
                       selected from the secondary reverse paths
                       list.";
                  }
                }
              }
            }
            container candidate-secondary-paths {
              description
                "The set of candidate secondary paths which may be
                 used for this primary path. When secondary paths are
                 specified in the list the path of the secondary LSP
                 in use must be restricted to those paths
                 referenced.
                 The priority of the secondary paths is specified
                 within the list. Higher priority values are less
                 preferred, i.e., a path with priority 0 is the
                 most preferred path. In the case that the
                 list is empty, any secondary path may be
                 utilized when the current primary path is in use.";
              list candidate-secondary-path {
                key "secondary-path";
                ordered-by user;
                description
                  "List of candidate secondary paths for this
                   tunnel.";
                leaf secondary-path {
                  type leafref {
                    path "../../../../../te:secondary-paths/"
                       + "te:secondary-path/te:name";
                  }
                  description
                    "A reference to the secondary path that may be
                     utilized when the containing primary path is
                     in use.";
                }
                leaf active {
                  type boolean;
                  config false;
                  description
                    "When 'true', indicates an active path has been
                     selected from the candidate secondary paths.";
                }
              }
            }
          }
        }
        container secondary-paths {
          description
            "The set of secondary paths.";
          reference
            "RFC 4872: RSVP-TE Extensions in Support of End-to-End
                       Generalized Multi-Protocol Label Switching
                       (GMPLS) Recovery";
          list secondary-path {
            key "name";
            description
              "List of secondary paths for this tunnel.";
            uses path-common-properties;
            leaf preference {
              type uint8 {
                range "1..255";
              }
              default "1";
              description
                "Specifies a preference for this path. The lower the
                 number, the higher the preference.";
            }
            leaf secondary-reverse-path {
              type leafref {
                path "../../../"
                   + "te:secondary-reverse-paths/"
                   + "te:secondary-reverse-path/te:name";
              }
              description
                "A reference to the reverse secondary path when
                 co-routed with the secondary path.";
            }
            uses path-compute-info;
            uses protection-restoration-properties;
            uses path-state;
          }
        }
        container secondary-reverse-paths {
          description
            "The set of secondary reverse paths.";
          list secondary-reverse-path {
            key "name";
            description
              "List of secondary paths for this tunnel.";
            uses path-common-properties;
            leaf preference {
              type uint8 {
                range "1..255";
              }
              default "1";
              description
                "Specifies a preference for this path. The lower the
                 number, the higher the preference. Paths that have
                 the same preference will be activated together.";
            }
            uses path-compute-info;
            uses protection-restoration-properties;
            uses path-state;
          }
        }
        action tunnel-action {
          description
            "Action commands to manipulate the TE tunnel state.";
          reference
            "RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels,
             Section 2.5";
          input {
            leaf action-type {
              type identityref {
                base te-types:tunnel-action-type;
              }
              description
                "The action to be invoked on the TE tunnel.";
            }
          }
          output {
            leaf action-result {
              type identityref {
                base te-types:te-action-result;
              }
              description
                "The result of the tunnel action operation.";
            }
          }
        }
        action protection-external-commands {
          description
            "Actions to manipulate the protection external
             commands of the TE tunnel.";
          reference
            "RFC 4427: Recovery (Protection and Restoration)
             Terminology for Generalized Multi-Protocol Label
             Switching (GMPLS)";
          input {
            leaf protection-external-command {
              type identityref {
                base te-types:protection-external-commands;
              }
              description
                "Protection external command.";
            }
            leaf ingress-node {
              type boolean;
              default "true";
              description
                "When 'true', indicates that the action is
                 applied on the ingress node.
                 By default, the action applies to the ingress
                 node.";
            }
            leaf egress-node {
              type boolean;
              default "false";
              description
                "When 'true', indicates that the action is
                 applied on the egress node. By default,
                 the action applies to the ingress node.";
            }
            leaf path-name {
              type string;
              description
                "The name of the path that the external command
                 applies to.";
            }
            leaf path-type {
              type te-types:path-type;
              description
                "The type of the path that the external command
                 applies to.";
            }
            leaf traffic-type {
              type enumeration {
                enum normal-traffic {
                  description
                    "The manual-switch or forced-switch command
                     applies to the normal traffic (this Tunnel).";
                }
                enum null-traffic {
                  description
                    "The manual-switch or forced-switch command
                     applies to the null traffic.";
                }
                enum extra-traffic {
                  description
                    "The manual-switch or forced-switch command
                     applies to the extra traffic (the extra-traffic
                     Tunnel sharing protection bandwidth with this
                     Tunnel).";
                }
              }
              description
                "Indicates whether the manual-switch or forced-switch
                 commands applies to the normal traffic, the null
                 traffic or the extra-traffic.";
              reference
                "RFC 4427: Recovery (Protection and Restoration)
                           Terminology for Generalized Multi-Protocol
                           Label Switching (GMPLS).";
            }
            leaf extra-traffic-tunnel-ref {
              type tunnel-ref;
              description
                "In case there are multiple extra-traffic tunnels
                 sharing protection bandwidth with this Tunnel
                 (m:n protection), represents which extra-traffic
                 Tunnel the manual-switch or forced-switch to
                 extra-traffic command applies to.";
            }
          }
        }
      }
    }

    /* TE LSPs Data */
    container lsps {
      config false;
      description
        "TE LSPs state container.";
      list lsp {
        key "tunnel-name lsp-id node";
        unique "source destination tunnel-id lsp-id "
             + "extended-tunnel-id";
        description
          "List of LSPs associated with the tunnel.";
        leaf tunnel-name {
          type string;
          description
            "The TE tunnel name.";
        }
        leaf lsp-id {
          type uint16;
          description
            "An identifier unique in the context of the ingress LSP.
             For example, as used in the RSVP-TE SENDER_TEMPLATE and
             FILTER_SPEC objects. The value can be changed to allow a
             sender to share resources with itself.";
          reference
            "RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels";
        }
        leaf node {
          type te-types:te-node-id;
          description
            "The node where the LSP state is retrieved.";
        }
        leaf source {
          type te-types:te-node-id;
          description
            "The address of the ingress LSP endpoint that identifies
             the start of the tunnel. This typically corresponds to
             the Tunnel Sender Address extracted from the RSVP-TE
             SENDER_TEMPLATE object.";
          reference
            "RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels";
        }
        leaf destination {
          type te-types:te-node-id;
          description
            "The address of the egress LSP endpoint that identifies
             the end of the tunnel. This typically corresponds to
             the Tunnel Endpoint Address extracted from the RSVP-TE
             SESSION object.";
          reference
            "RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels";
        }
        leaf tunnel-id {
          type uint16;
          description
            "An identifier of the tunnel that remains constant over
             the life of the tunnel. For example, this may be the
             Tunnel ID extracted from RSVP-TE SESSION object.";
          reference
            "RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels";
        }
        leaf extended-tunnel-id {
          type te-types:te-node-id;
          description
            "A qualifier used to ensure the global uniqueness of the
             tunnel identifier. It carries a 4-byte or 16-byte value,
             typically corresponding to the Extended Tunnel ID
             extracted from the RSVP-TE SESSION object as defined in
             RFC 3209.";
          reference
            "RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels";
        }
        leaf operational-state {
          type identityref {
            base te-types:lsp-state-type;
          }
          description
            "The LSP operational state.";
        }
        leaf signaling-type {
          type identityref {
            base te-types:path-signaling-type;
          }
          description
            "The signaling protocol used to set up this LSP.";
        }
        leaf origin-type {
          type enumeration {
            enum ingress {
              description
                "Origin ingress.";
            }
            enum egress {
              description
                "Origin egress.";
            }
            enum transit {
              description
                "Origin transit.";
            }
          }
          description
            "The origin of the LSP relative to the location of the
             local switch in the path.";
        }
        leaf lsp-resource-status {
          type enumeration {
            enum primary {
              description
                "A primary LSP is a fully established LSP for which
                 the resource allocation has been committed at the
                 data plane.";
            }
            enum secondary {
              description
                "A secondary LSP is an LSP that has been provisioned
                 in the control plane only; e.g., resource allocation
                 has not been committed at the data plane.";
            }
          }
          description
            "LSP resource allocation state.";
          reference
            "RFC 4872: RSVP-TE Extensions in Support of End-to-End
                       Generalized Multi-Protocol Label Switching
                       (GMPLS) Recovery, Section 4.2.1";
        }
        leaf lockout-of-normal {
          type boolean;
          description
            "When set to 'true', it represents a lockout of normal
             traffic external command. When set to 'false', it
             represents a clear lockout of normal traffic external
             command. The lockout of normal traffic command applies
             to this Tunnel.";
          reference
            "RFC 4427: Recovery (Protection and Restoration)
                       Terminology for Generalized Multi-Protocol
                       Label Switching (GMPLS)";
        }
        leaf freeze {
          type boolean;
          description
            "When set to 'true', it represents a freeze external
             command. When set to 'false', it represents a clear
             freeze external command. The freeze command applies to
             all the Tunnels which are sharing the protection
             resources with this Tunnel.";
          reference
            "RFC 4427: Recovery (Protection and Restoration)
                       Terminology for Generalized Multi-Protocol
                       Label Switching (GMPLS)";
        }
        leaf lsp-protection-role {
          type enumeration {
            enum working {
              description
                "A working LSP must be a primary LSP whilst a
                 protecting LSP can be either a primary or a
                 secondary LSP. Also, known as protected LSPs when
                 working LSPs are associated with protecting LSPs.";
            }
            enum protecting {
              description
                "A secondary LSP is an LSP that has been provisioned
                 in the control plane only; e.g., resource allocation
                 has not been committed at the data plane.";
            }
          }
          description
            "LSP role type.";
          reference
            "RFC 4872: RSVP-TE Extensions in Support of End-to-End
                       Generalized Multi-Protocol Label Switching
                       (GMPLS) Recovery, Section 4.2.1";
        }
        leaf lsp-protection-state {
          type identityref {
            base te-types:lsp-protection-state;
          }
          config false;
          description
            "The reported protection state controlling which
             tunnel is using the resources of the protecting LSP.";
        }
        leaf ingress-node-id {
          type te-types:te-node-id;
          description
            "Indicates the te-node-id of the ingress node of the TE
             tunnel or tunnel segment when the protection action is
             applied to the ingress node or the Wait To Restore (WTR)
             timer is active.
             This is set to '0.0.0.0' when the controller is not
             aware of the te-node-id of ingress-node.";
        }
        leaf egress-node-id {
          type te-types:te-node-id;
          description
            "Indicates the te-node-id of the egress node of the TE
             tunnel or tunnel segment when the protection action is
             applied to the ingress node or the WTR timer is active.
             This is set to '0.0.0.0' when the controller is not
             aware of the te-node-id of ingress-node.";
        }
        container lsp-actual-route-information {
          description
            "RSVP recorded route object information.";
          list lsp-actual-route-information {
            when "../../origin-type = 'ingress'" {
              description
                "Applicable on ingress LSPs only.";
            }
            key "index";
            description
              "Record route list entry.";
            uses te-types:record-route-state;
          }
        }
      }
    }
  }

  /* TE Tunnel RPCs/execution Data */

  rpc tunnels-path-compute {
    description
      "This RPC is a generic API whose
       input and output parameters are expected to be provided by
       augments to this module.";
    reference
      "RFC 4655: A Path Computation Element (PCE)-Based
       Architecture.";
    input {
      container path-compute-info {
        /*
         * An external path compute module may augment this
         * target.
         */
        description
          "RPC input information.";
      }
    }
    output {
      container path-compute-result {
        /*
         * An external path compute module may augment this
         * target.
         */
        description
          "RPC output information.";
      }
    }
  }

  rpc tunnels-actions {
    description
      "RPC that manipulates the state of a TE tunnel.";
    reference
      "RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels,
       Section 2.5";
    input {
      container tunnel-info {
        description
          "TE tunnel information.";
        choice filter-type {
          mandatory true;
          description
            "Filter choice.";
          case all-tunnels {
            leaf all {
              type empty;
              mandatory true;
              description
                "When present, applies the action on all TE
                 tunnels.";
            }
          }
          case one-tunnel {
            leaf tunnel {
              type tunnel-ref;
              description
                "Apply action on the specific TE tunnel.";
            }
          }
        }
      }
      container action-info {
        description
          "TE tunnel action information.";
        leaf action {
          type identityref {
            base te-types:tunnel-action-type;
          }
          description
            "The action type.";
        }
        leaf disruptive {
          when "derived-from-or-self(../action, "
             + "'te-types:tunnel-action-reoptimize')";
          type empty;
          description
            "Specifies whether reoptimization operations,
             particularly when multiple tunnels are involved,
             are permitted to cause traffic disruption on some
             TE tunnels.";
        }
      }
    }
    output {
      leaf action-result {
        type identityref {
          base te-types:te-action-result;
        }
        description
          "The result of the tunnel action operation.";
      }
    }
  }
}</sourcecode>
      </section>
    </section>
    <section anchor="te-device-yang-module" numbered="true" removeInRFC="false" toc="include" pn="section-6">
      <name slugifiedName="name-te-device-yang-module">TE Device YANG Module</name>
      <t indent="0" pn="section-6-1">The TE device YANG module "ietf-te-device" models data that is specific to
managing a TE device. This module augments the TE YANG module.</t>
      <section anchor="module-structure-1" numbered="true" removeInRFC="false" toc="include" pn="section-6.1">
        <name slugifiedName="name-module-structure-2">Module Structure</name>
        <t indent="0" pn="section-6.1-1">The "ietf-te-device" module defines the configuration and operational state data
that is specific to the device, including those related to the TE subsystem, tunnels, LSPs, and interfaces.</t>
        <section anchor="te-device-globals-tunnels-and-lsps" numbered="true" removeInRFC="false" toc="include" pn="section-6.1.1">
          <name slugifiedName="name-te-device-globals-tunnels-a">TE Device Globals, Tunnels, and LSPs</name>
          <t indent="0" pn="section-6.1.1-1">The "ietf-te-device" module augments the TE YANG module "ietf-te" at the
'globals', 'tunnels', and 'lsps' levels to include the device-specific
configurations and operational state.</t>
          <t indent="0" pn="section-6.1.1-2"><xref target="fig-if-te-01" format="default" sectionFormat="of" derivedContent="Figure 7"/> shows the
"ietf-te-device" subtree generated with depth=4 that describes those
augmentations.</t>
          <figure anchor="fig-if-te-01" align="left" suppress-title="false" pn="figure-7">
            <name slugifiedName="name-te-device-augmentations-to-">TE Device Augmentations to Globals, Tunnels, and LSPs YANG Subtree</name>
            <sourcecode type="yangtree" markers="false" pn="section-6.1.1-3.1">
module: ietf-te-device

  augment /te:te/te:globals:
    +--rw lsp-install-interval?        uint32
    +--rw lsp-cleanup-interval?        uint32
    +--rw lsp-invalidation-interval?   uint32
  augment /te:te/te:tunnels/te:tunnel:
    +--rw path-invalidation-action?    identityref
    +--rw lsp-install-interval?        uint32
    +--rw lsp-cleanup-interval?        uint32
    +--rw lsp-invalidation-interval?   uint32
  augment /te:te/te:lsps/te:lsp:
    +--ro lsp-timers
    |  +--ro uptime?            uint32
    |  +--ro time-to-install?   uint32
    |  +--ro time-to-destroy?   uint32
    +--ro downstream-info
    |     ..
    +--ro upstream-info
          ..</sourcecode>
          </figure>
          <t indent="0" pn="section-6.1.1-4">The following is the description of the augmented data at each level.</t>
          <dl newline="true" spacing="normal" indent="3" pn="section-6.1.1-5">
            <dt pn="section-6.1.1-5.1">Global Timers (Augmenting /te:te/te:globals):</dt>
            <dd pn="section-6.1.1-5.2">
              <t indent="0" pn="section-6.1.1-5.2.1">These are device-specific global configuration parameters related to LSP timers, applied system-wide.</t>
              <dl newline="true" spacing="normal" indent="3" pn="section-6.1.1-5.2.2">
                <dt pn="section-6.1.1-5.2.2.1">lsp-install-interval:</dt>
                <dd pn="section-6.1.1-5.2.2.2">An optional leaf that specifies the delay time, in seconds, before a newly provisioned LSP is installed into the forwarding plane to carry traffic.</dd>
                <dt pn="section-6.1.1-5.2.2.3">lsp-cleanup-interval:</dt>
                <dd pn="section-6.1.1-5.2.2.4">An optional leaf that specifies the delay time, in seconds, before an LSP is completely removed from the system after it is no longer in use.</dd>
                <dt pn="section-6.1.1-5.2.2.5">lsp-invalidation-interval:</dt>
                <dd pn="section-6.1.1-5.2.2.6">An optional leaf that specifies the delay time, in seconds, during which a TE LSP's path is considered invalid before any corrective action is taken.</dd>
              </dl>
            </dd>
            <dt pn="section-6.1.1-5.3">Tunnel Device-Dependent Attributes (Augmenting /te:te/te:tunnels/te:tunnel):</dt>
            <dd pn="section-6.1.1-5.4">
              <t indent="0" pn="section-6.1.1-5.4.1">These are device-specific configuration parameters that apply to individual TE Tunnels:</t>
              <dl newline="true" spacing="normal" indent="3" pn="section-6.1.1-5.4.2">
                <dt pn="section-6.1.1-5.4.2.1">path-invalidation-action:</dt>
                <dd pn="section-6.1.1-5.4.2.2">An optional identityref that specifies the action to be taken when a TE Tunnel's path is deemed invalid (e.g., tear down, recompute).</dd>
                <dt pn="section-6.1.1-5.4.2.3">lsp-install-interval:</dt>
                <dd pn="section-6.1.1-5.4.2.4">An optional leaf that specifies the delay time, in seconds, for this specific TE Tunnel before its LSPs are installed into the forwarding plane. This value can override the global lsp-install-interval.</dd>
                <dt pn="section-6.1.1-5.4.2.5">lsp-cleanup-interval:</dt>
                <dd pn="section-6.1.1-5.4.2.6">An optional leaf that specifies the delay time, in seconds, for this specific TE Tunnel before its LSPs are cleaned up. This value can override the global lsp-cleanup-interval.</dd>
                <dt pn="section-6.1.1-5.4.2.7">lsp-invalidation-interval:</dt>
                <dd pn="section-6.1.1-5.4.2.8">An optional leaf that specifies the delay time, in seconds, for this specific TE Tunnel during which its path is considered invalid before action is taken. This value can override the global lsp-invalidation-interval.</dd>
              </dl>
            </dd>
            <dt pn="section-6.1.1-5.5">LSP Device-Dependent State (Augmenting /te:te/te:lsps/te:lsp):</dt>
            <dd pn="section-6.1.1-5.6">
              <t indent="0" pn="section-6.1.1-5.6.1">These are read-only operational state parameters providing device-specific details for individual LSPs:</t>
              <dl newline="true" spacing="normal" indent="3" pn="section-6.1.1-5.6.2">
                <dt pn="section-6.1.1-5.6.2.1">lsp-timers:</dt>
                <dd pn="section-6.1.1-5.6.2.2">A container that holds various timer-related operational state for an LSP, applicable primarily to ingress LSPs.</dd>
                <dt pn="section-6.1.1-5.6.2.3">uptime:</dt>
                <dd pn="section-6.1.1-5.6.2.4">An optional leaf that indicates the total time, in seconds, that the LSP has been operational.</dd>
                <dt pn="section-6.1.1-5.6.2.5">time-to-install:</dt>
                <dd pn="section-6.1.1-5.6.2.6">An optional leaf that indicates the remaining time, in seconds, for a new LSP to be fully instantiated and ready to carry traffic.</dd>
                <dt pn="section-6.1.1-5.6.2.7">time-to-destroy:</dt>
                <dd pn="section-6.1.1-5.6.2.8">An optional leaf that indicates the remaining time, in seconds, before an existing LSP is torn down.</dd>
                <dt pn="section-6.1.1-5.6.2.9">downstream-info:</dt>
                <dd pn="section-6.1.1-5.6.2.10">A container that holds information about the downstream neighbor and label for the LSP, applicable when the LSP is not at its egress.</dd>
                <dt pn="section-6.1.1-5.6.2.11">upstream-info:</dt>
                <dd pn="section-6.1.1-5.6.2.12">A container that holds information about the upstream neighbor and label for the LSP, applicable when the LSP is not at its ingress.</dd>
              </dl>
            </dd>
          </dl>
        </section>
        <section anchor="te-device-interfaces" numbered="true" removeInRFC="false" toc="include" pn="section-6.1.2">
          <name slugifiedName="name-te-device-interfaces">TE Device Interfaces</name>
          <t indent="0" pn="section-6.1.2-1">The TE interface is modeled as a reference to an existing interface as defined
in the 'ietf-interfaces' YANG module <xref target="RFC8343" format="default" sectionFormat="of" derivedContent="RFC8343"/>.</t>
          <t indent="0" pn="section-6.1.2-2"><xref target="fig-if-te-02" format="default" sectionFormat="of" derivedContent="Figure 8"/> shows the TE interface subtree from the TE device module "ietf-te-device" with depth=4.
The full tree diagram is shown in <xref target="AppendixB" format="default" sectionFormat="of" derivedContent="Appendix B"/>.</t>
          <figure anchor="fig-if-te-02" align="left" suppress-title="false" pn="figure-8">
            <name slugifiedName="name-te-interfaces-yang-subtree-">TE Interfaces YANG Subtree from the TE Device YANG Data Model</name>
            <sourcecode type="yangtree" markers="false" pn="section-6.1.2-3.1">
module: ietf-te-device

  augment /te:te:
    +--rw interfaces
       +--rw threshold-type?            enumeration
       +--rw delta-percentage?          rt-types:percentage
       +--rw threshold-specification?   enumeration
       +--rw up-thresholds*             rt-types:percentage
       +--rw down-thresholds*           rt-types:percentage
       +--rw up-down-thresholds*        rt-types:percentage
       +--rw interface* [name]
          +--rw name                                if:interface-ref
          +--rw te-metric?
          |       te-types:te-metric
          +--rw (admin-group-type)?
          |  +--:(value-admin-groups)
          |  |     ...
          |  +--:(named-admin-groups)
          |        ...
          +--rw (srlg-type)?
          |  +--:(value-srlgs)
          |  |     ...
          |  +--:(named-srlgs)
          |        ...
          +--rw threshold-type?                     enumeration
          +--rw delta-percentage?
          |       rt-types:percentage
          +--rw threshold-specification?            enumeration
          +--rw up-thresholds*
          |       rt-types:percentage
          +--rw down-thresholds*
          |       rt-types:percentage
          +--rw up-down-thresholds*
          |       rt-types:percentage
          +--rw switching-capabilities* [switching-capability]
          |  +--rw switching-capability    identityref
          |  +--rw encoding?               identityref
          +--ro te-advertisements-state
             +--ro flood-interval?           uint32
             +--ro last-flooded-time?        uint32
             +--ro next-flooded-time?        uint32
             +--ro last-flooded-trigger?     enumeration
             +--ro advertised-level-areas* [level-area]
                   ...</sourcecode>
          </figure>
          <t indent="0" pn="section-6.1.2-4">The main elements under the interfaces container are:</t>
          <dl spacing="normal" newline="true" indent="3" pn="section-6.1.2-5">
            <dt pn="section-6.1.2-5.1">threshold-type:</dt>
            <dd pn="section-6.1.2-5.2">An optional enumeration that specifies the type of thresholding mechanism used for flooding bandwidth updates for all TE interfaces on the device. Options include 'delta' (flooding on a change greater than a specified delta) or 'threshold-crossed' (flooding when bandwidth crosses a defined threshold).</dd>
            <dt pn="section-6.1.2-5.3">delta-percentage:</dt>
            <dd pn="section-6.1.2-5.4">An optional percentage value, used when threshold-type is 'delta', indicating the change in reservable bandwidth that triggers an IGP update for all TE interfaces.</dd>
            <dt pn="section-6.1.2-5.5">threshold-specification:</dt>
            <dd pn="section-6.1.2-5.6">An optional enumeration, used when threshold-type is 'threshold-crossed', to define whether a single set of 'mirrored-up-down' thresholds or separate 'separate-up-down' thresholds are used for increasing and decreasing bandwidth. This applies globally to all TE interfaces.</dd>
            <dt pn="section-6.1.2-5.7">up-thresholds:</dt>
            <dd pn="section-6.1.2-5.8">A list of percentage values, used with 'separate-up-down' thresholding, that define the points at which bandwidth updates are triggered when the reservable bandwidth is increasing across all TE interfaces.</dd>
            <dt pn="section-6.1.2-5.9">down-thresholds:</dt>
            <dd pn="section-6.1.2-5.10">A list of percentage values, used with 'separate-up-down' thresholding, that define the points at which bandwidth updates are triggered when the reservable bandwidth is decreasing across all TE interfaces.</dd>
            <dt pn="section-6.1.2-5.11">up-down-thresholds:</dt>
            <dd pn="section-6.1.2-5.12">A list of percentage values, used with 'mirrored-up-down' thresholding, that define the points at which bandwidth updates are triggered for both increasing and decreasing reservable bandwidth across all TE interfaces.</dd>
            <dt pn="section-6.1.2-5.13">interface:</dt>
            <dd pn="section-6.1.2-5.14">
              <t indent="0" pn="section-6.1.2-5.14.1">A list of individual TE interfaces configured on the device. Each entry represents a network interface enabled for Traffic Engineering and contains its specific attributes and state. A TE interface is identified by the 'name' leaf, which references an existing network interface on the device.</t>
              <dl spacing="normal" newline="true" indent="3" pn="section-6.1.2-5.14.2">
                <dt pn="section-6.1.2-5.14.2.1">name:</dt>
                <dd pn="section-6.1.2-5.14.2.2">A leaf that uniquely identifies the TE interface, referencing an existing network interface.</dd>
                <dt pn="section-6.1.2-5.14.2.3">te-metric:</dt>
                <dd pn="section-6.1.2-5.14.2.4">An optional leaf that holds the TE metric value associated with this specific interface, used during path computation.</dd>
                <dt pn="section-6.1.2-5.14.2.5">admin-group-type:</dt>
                <dd pn="section-6.1.2-5.14.2.6">A choice node that allows configuring administrative groups for the interface using either direct values or named references.</dd>
                <dt pn="section-6.1.2-5.14.2.7">value-admin-groups:</dt>
                <dd pn="section-6.1.2-5.14.2.8">A choice for defining administrative groups using direct bitmask values.</dd>
                <dt pn="section-6.1.2-5.14.2.9">named-admin-groups:</dt>
                <dd pn="section-6.1.2-5.14.2.10">A list of named administrative groups applied to this TE interface, referencing globally defined named administrative groups.</dd>
                <dt pn="section-6.1.2-5.14.2.11">srlg-type:</dt>
                <dd pn="section-6.1.2-5.14.2.12">
                  <t indent="0" pn="section-6.1.2-5.14.2.12.1">A choice node that allows configuring SRLGs for the interface using either direct values or named references.</t>
                  <dl spacing="normal" newline="true" indent="3" pn="section-6.1.2-5.14.2.12.2">
                    <dt pn="section-6.1.2-5.14.2.12.2.1">value-srlgs:</dt>
                    <dd pn="section-6.1.2-5.14.2.12.2.2">A list of direct SRLG values that this link is a part of.</dd>
                    <dt pn="section-6.1.2-5.14.2.12.2.3">named-srlgs:</dt>
                    <dd pn="section-6.1.2-5.14.2.12.2.4">A list of named SRLGs applied to this interface, referencing globally defined named SRLGs.</dd>
                  </dl>
                </dd>
                <dt pn="section-6.1.2-5.14.2.13">threshold-type:</dt>
                <dd pn="section-6.1.2-5.14.2.14">An optional enumeration, similar to the global threshold-type, but specifically for this individual TE interface, allowing per-interface override of the global bandwidth flooding behavior.</dd>
                <dt pn="section-6.1.2-5.14.2.15">delta-percentage:</dt>
                <dd pn="section-6.1.2-5.14.2.16">An optional percentage value, specific to this interface, used when its threshold-type is 'delta'.</dd>
                <dt pn="section-6.1.2-5.14.2.17">threshold-specification:</dt>
                <dd pn="section-6.1.2-5.14.2.18">An optional enumeration, specific to this interface, used when its threshold-type is 'threshold-crossed'.</dd>
                <dt pn="section-6.1.2-5.14.2.19">up-thresholds:</dt>
                <dd pn="section-6.1.2-5.14.2.20">A list of percentage values, specific to this interface, used with 'separate-up-down' thresholding for increasing bandwidth.</dd>
                <dt pn="section-6.1.2-5.14.2.21">down-thresholds:</dt>
                <dd pn="section-6.1.2-5.14.2.22">A list of percentage values, specific to this interface, used with 'separate-up-down' thresholding for decreasing bandwidth.</dd>
                <dt pn="section-6.1.2-5.14.2.23">up-down-thresholds:</dt>
                <dd pn="section-6.1.2-5.14.2.24">A list of percentage values, specific to this interface, used with 'mirrored-up-down' thresholding for both increasing and decreasing bandwidth.</dd>
                <dt pn="section-6.1.2-5.14.2.25">switching-capabilities:</dt>
                <dd pn="section-6.1.2-5.14.2.26">
                  <t indent="0" pn="section-6.1.2-5.14.2.26.1">A list of switching capabilities supported by this interface.</t>
                  <dl newline="true" spacing="normal" indent="3" pn="section-6.1.2-5.14.2.26.2">
                    <dt pn="section-6.1.2-5.14.2.26.2.1">switching-capability:</dt>
                    <dd pn="section-6.1.2-5.14.2.26.2.2">An identityref indicating a specific switching capability (e.g., Packet, Lambda, Fiber).</dd>
                    <dt pn="section-6.1.2-5.14.2.26.2.3">encoding:</dt>
                    <dd pn="section-6.1.2-5.14.2.26.2.4">An optional identityref indicating the LSP encoding type supported by this capability on the interface.</dd>
                  </dl>
                </dd>
                <dt pn="section-6.1.2-5.14.2.27">te-advertisements-state:</dt>
                <dd pn="section-6.1.2-5.14.2.28">
                  <t indent="0" pn="section-6.1.2-5.14.2.28.1">A read-only container that provides operational state information related to how this TE interface's attributes are advertised.</t>
                  <dl spacing="normal" newline="true" indent="3" pn="section-6.1.2-5.14.2.28.2">
                    <dt pn="section-6.1.2-5.14.2.28.2.1">flood-interval:</dt>
                    <dd pn="section-6.1.2-5.14.2.28.2.2">An optional leaf indicating the configured periodic flooding interval for this interface.</dd>
                    <dt pn="section-6.1.2-5.14.2.28.2.3">last-flooded-time:</dt>
                    <dd pn="section-6.1.2-5.14.2.28.2.4">An optional leaf showing the time elapsed since the last advertisement flood for this interface.</dd>
                    <dt pn="section-6.1.2-5.14.2.28.2.5">next-flooded-time:</dt>
                    <dd pn="section-6.1.2-5.14.2.28.2.6">An optional leaf showing the time remaining until the next scheduled advertisement flood for this interface.</dd>
                    <dt pn="section-6.1.2-5.14.2.28.2.7">last-flooded-trigger:</dt>
                    <dd pn="section-6.1.2-5.14.2.28.2.8">An optional enumeration indicating the event that triggered the last advertisement flood (e.g., link-up, bandwidth-change, periodic-timer).</dd>
                    <dt pn="section-6.1.2-5.14.2.28.2.9">advertised-level-areas:</dt>
                    <dd pn="section-6.1.2-5.14.2.28.2.10">A list of IGP level-areas in which this TE interface's link state information is advertised.</dd>
                  </dl>
                </dd>
              </dl>
            </dd>
          </dl>
        </section>
      </section>
      <section anchor="tree-diagram-1" numbered="true" removeInRFC="false" toc="include" pn="section-6.2">
        <name slugifiedName="name-tree-diagram-2">Tree Diagram</name>
        <t indent="0" pn="section-6.2-1"><xref target="fig-te-dev-tree" format="default" sectionFormat="of" derivedContent="Figure 9"/> shows the YANG tree diagram of the TE device YANG module defined in
"ietf-te-device".</t>
        <figure anchor="fig-te-dev-tree" align="left" suppress-title="false" pn="figure-9">
          <name slugifiedName="name-te-tunnel-device-model-yang">TE Tunnel Device Model YANG Tree Diagram</name>
          <sourcecode type="yangtree" markers="false" pn="section-6.2-2.1">
module: ietf-te-device

  augment /te:te:
    +--rw interfaces
       +--rw threshold-type?            enumeration
       +--rw delta-percentage?          rt-types:percentage
       +--rw threshold-specification?   enumeration
       +--rw up-thresholds*             rt-types:percentage
       +--rw down-thresholds*           rt-types:percentage
       +--rw up-down-thresholds*        rt-types:percentage
       +--rw interface* [name]
          +--rw name                                if:interface-ref
          +--rw te-metric?
          |       te-types:te-metric
          +--rw (admin-group-type)?
          |  +--:(value-admin-groups)
          |  |  +--rw (value-admin-group-type)?
          |  |     +--:(admin-groups)
          |  |     |  +--rw admin-group?
          |  |     |          te-types:admin-group
          |  |     +--:(extended-admin-groups)
          |  |              {te-types:extended-admin-groups}?
          |  |        +--rw extended-admin-group?
          |  |                te-types:extended-admin-group
          |  +--:(named-admin-groups)
          |     +--rw named-admin-groups* [named-admin-group]
          |             {te-types:extended-admin-groups,
          |              te-types:named-extended-admin-groups}?
          |        +--rw named-admin-group    leafref
          +--rw (srlg-type)?
          |  +--:(value-srlgs)
          |  |  +--rw values* [value]
          |  |     +--rw value    uint32
          |  +--:(named-srlgs)
          |     +--rw named-srlgs* [named-srlg]
          |             {te-types:named-srlg-groups}?
          |        +--rw named-srlg    leafref
          +--rw threshold-type?                     enumeration
          +--rw delta-percentage?
          |       rt-types:percentage
          +--rw threshold-specification?            enumeration
          +--rw up-thresholds*
          |       rt-types:percentage
          +--rw down-thresholds*
          |       rt-types:percentage
          +--rw up-down-thresholds*
          |       rt-types:percentage
          +--rw switching-capabilities* [switching-capability]
          |  +--rw switching-capability    identityref
          |  +--rw encoding?               identityref
          +--ro te-advertisements-state
             +--ro flood-interval?           uint32
             +--ro last-flooded-time?        uint32
             +--ro next-flooded-time?        uint32
             +--ro last-flooded-trigger?     enumeration
             +--ro advertised-level-areas* [level-area]
                +--ro level-area    uint32
  augment /te:te/te:globals:
    +--rw lsp-install-interval?        uint32
    +--rw lsp-cleanup-interval?        uint32
    +--rw lsp-invalidation-interval?   uint32
  augment /te:te/te:tunnels/te:tunnel:
    +--rw path-invalidation-action?    identityref
    +--rw lsp-install-interval?        uint32
    +--rw lsp-cleanup-interval?        uint32
    +--rw lsp-invalidation-interval?   uint32
  augment /te:te/te:lsps/te:lsp:
    +--ro lsp-timers
    |  +--ro uptime?            uint32
    |  +--ro time-to-install?   uint32
    |  +--ro time-to-destroy?   uint32
    +--ro downstream-info
    |  +--ro nhop?                 te-types:te-tp-id
    |  +--ro outgoing-interface?   if:interface-ref
    |  +--ro neighbor
    |  |  +--ro id?     te-gen-node-id
    |  |  +--ro type?   enumeration
    |  +--ro label?                rt-types:generalized-label
    +--ro upstream-info
       +--ro phop?       te-types:te-tp-id
       +--ro neighbor
       |  +--ro id?     te-gen-node-id
       |  +--ro type?   enumeration
       +--ro label?      rt-types:generalized-label

  rpcs:
    +---x link-state-update
       +---w input
          +---w (filter-type)
             +--:(match-all)
             |  +---w all          empty
             +--:(match-one-interface)
                +---w interface?   if:interface-ref</sourcecode>
        </figure>
      </section>
      <section anchor="yang-module-1" numbered="true" removeInRFC="false" toc="include" pn="section-6.3">
        <name slugifiedName="name-yang-module-for-traffic-engi">YANG Module for Traffic Engineering</name>
        <t indent="0" pn="section-6.3-1">The "ietf-te-device" module imports the following modules:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-6.3-2">
          <li pn="section-6.3-2.1">
            <t indent="0" pn="section-6.3-2.1.1">ietf-interfaces defined in <xref target="RFC8343" format="default" sectionFormat="of" derivedContent="RFC8343"/></t>
          </li>
          <li pn="section-6.3-2.2">
            <t indent="0" pn="section-6.3-2.2.1">ietf-routing-types defined in <xref target="RFC8294" format="default" sectionFormat="of" derivedContent="RFC8294"/></t>
          </li>
          <li pn="section-6.3-2.3">
            <t indent="0" pn="section-6.3-2.3.1">ietf-te-types defined in <xref target="RFC10056" format="default" sectionFormat="of" derivedContent="RFC10056"/></t>
          </li>
          <li pn="section-6.3-2.4">
            <t indent="0" pn="section-6.3-2.4.1">ietf-te defined in this document</t>
          </li>
        </ul>
        <sourcecode markers="true" name="ietf-te-device@2026-11-18.yang" type="yang" pn="section-6.3-3">
module ietf-te-device {
  yang-version 1.1;
  namespace "urn:ietf:params:xml:ns:yang:ietf-te-device";

  prefix te-dev;

  /* Import TE module */

  import ietf-te {
    prefix te;
    reference
      "RFC 10057: A YANG Data Model for Traffic Engineering Tunnels,
       Label Switched Paths, and Interfaces";
  }

  /* Import TE types */

  import ietf-te-types {
    prefix te-types;
    reference
      "RFC 10056: Common YANG Data Types for Traffic Engineering.";
  }
  import ietf-interfaces {
    prefix if;
    reference
      "RFC8343: A YANG Data Model for Interface Management";
  }
  import ietf-routing-types {
    prefix rt-types;
    reference
      "RFC8294: Common YANG Data Types for the Routing Area";
  }

  organization
    "IETF Traffic Engineering Architecture and Signaling (TEAS)
     Working Group";
  contact
    "WG Web:   &lt;https://datatracker.ietf.org/wg/teas/&gt;
     WG List:  &lt;mailto:teas@ietf.org&gt;

     Editor:   Tarek Saad
               &lt;mailto:tsaad.net@gmail.com&gt;

     Editor:   Rakesh Gandhi
               &lt;mailto:rgandhi@cisco.com&gt;

     Editor:   Vishnu Pavan Beeram
               &lt;mailto:vbeeram@juniper.net&gt;

     Editor:   Himanshu Shah
               &lt;mailto:hshah@ciena.com&gt;

     Editor:   Xufeng Liu
               &lt;mailto: xufeng.liu.ietf@gmail.com&gt;

     Editor:   Igor Bryskin
               &lt;mailto:i_bryskin@yahoo.com&gt;";

  description
    "This module defines a data model for TE device configurations,
     state, and RPCs.

     Copyright (c) 2026 IETF Trust and the persons identified as
     authors of the code. All rights reserved.

     Redistribution and use in source and binary forms, with or
     without modification, is permitted pursuant to, and subject to
     the license terms contained in, the Revised BSD License set
     forth in Section 4.c of the IETF Trust's Legal Provisions
     Relating to IETF Documents
     (https://trustee.ietf.org/license-info).

     This version of this YANG module is part of RFC 10057
     (https://www.rfc-editor.org/info/rfc10057); see the RFC itself
     for full legal notices.";

  revision 2026-11-18 {
    description
      "Initial revision for the TE device YANG module.";
    reference
      "RFC 10057: A YANG Data Model for Traffic Engineering Tunnels,
       Label Switched Paths, and Interfaces";
  }

  grouping lsp-device-timers {
    description
      "Device TE LSP timers configs.";
    leaf lsp-install-interval {
      type uint32;
      units "seconds";
      description
        "TE LSP installation delay time.";
    }
    leaf lsp-cleanup-interval {
      type uint32;
      units "seconds";
      description
        "TE LSP cleanup delay time.";
    }
    leaf lsp-invalidation-interval {
      type uint32;
      units "seconds";
      description
        "TE LSP path invalidation before taking action delay time.";
    }
  }

  grouping te-igp-flooding-bandwidth-config {
    description
      "Configurable items for igp flooding bandwidth
       threshold configuration.";
    leaf threshold-type {
      type enumeration {
        enum delta {
          description
            "'delta' indicates that the local
             system should flood IGP updates when a
             change in reserved bandwidth &gt;= the specified
             delta occurs on the interface.";
        }
        enum threshold-crossed {
          description
            "THRESHOLD-CROSSED indicates that
             the local system should trigger an update (and
             hence flood) the reserved bandwidth when the
             reserved bandwidth changes such that it crosses,
             or becomes equal to one of the threshold values.";
        }
      }
      description
        "The type of threshold that should be used to specify the
         values at which bandwidth is flooded. 'delta' indicates that
         the local system should flood IGP updates when a change in
         reserved bandwidth &gt;= the specified delta occurs on the
         interface. Where 'threshold-crossed' is specified, the local
         system should trigger an update (and hence flood) the
         reserved bandwidth when the reserved bandwidth changes such
         that it crosses, or becomes equal to one of the threshold
         values.";
    }
    leaf delta-percentage {
      when "../threshold-type = 'delta'" {
        description
          "The percentage delta can only be specified when the
           threshold type is specified to be a percentage delta of
           the reserved bandwidth.";
      }
      type rt-types:percentage;
      description
        "The percentage of the maximum-reservable-bandwidth
         considered as the delta that results in an IGP update
         being flooded.";
    }
    leaf threshold-specification {
      when "../threshold-type = 'threshold-crossed'" {
        description
          "The selection of whether mirrored or separate threshold
           values are to be used requires user-specified thresholds
           to be set.";
      }
      type enumeration {
        enum mirrored-up-down {
          description
            "mirrored-up-down indicates that a single set of
             threshold values should be used for both increasing
             and decreasing bandwidth when determining whether
             to trigger updated bandwidth values to be flooded
             in the IGP TE extensions.";
        }
        enum separate-up-down {
          description
            "separate-up-down indicates that a separate
             threshold values should be used for the increasing
             and decreasing bandwidth when determining whether
             to trigger updated bandwidth values to be flooded
             in the IGP TE extensions.";
        }
      }
      description
        "This value specifies whether a single set of threshold
         values should be used for both increasing and decreasing
         bandwidth when determining whether to trigger updated
         bandwidth values to be flooded in the IGP TE extensions.
         'mirrored-up-down' indicates that a single value (or set of
         values) should be used for both increasing and decreasing
         values, where 'separate-up-down' specifies that the
         increasing and decreasing values will be separately
         specified.";
    }
    leaf-list up-thresholds {
      when "../threshold-type = 'threshold-crossed'"
         + "and ../threshold-specification = 'separate-up-down'" {
        description
          "A list of up-thresholds can only be specified when the
           bandwidth update is triggered based on crossing a
           threshold and separate up and down thresholds are
           required.";
      }
      type rt-types:percentage;
      description
        "The thresholds (expressed as a percentage of the maximum
         reservable bandwidth) at which bandwidth updates are to be
         triggered when the bandwidth is increasing.";
    }
    leaf-list down-thresholds {
      when "../threshold-type = 'threshold-crossed'"
         + "and ../threshold-specification = 'separate-up-down'" {
        description
          "A list of down-thresholds can only be specified when the
           bandwidth update is triggered based on crossing a
           threshold and separate up and down thresholds are
           required.";
      }
      type rt-types:percentage;
      description
        "The thresholds (expressed as a percentage of the maximum
         reservable bandwidth) at which bandwidth updates are to be
         triggered when the bandwidth is decreasing.";
    }
    leaf-list up-down-thresholds {
      when "../threshold-type = 'threshold-crossed'"
         + "and ../threshold-specification = 'mirrored-up-down'" {
        description
          "A list of thresholds corresponding to both increasing
           and decreasing bandwidths can be specified only when an
           update is triggered based on crossing a threshold, and
           the same up and down thresholds are required.";
      }
      type rt-types:percentage;
      description
        "The thresholds (expressed as a percentage of the maximum
         reservable bandwidth of the interface) at which bandwidth
         updates are flooded -- used both when the bandwidth is
         increasing and decreasing.";
    }
  }

  /**
   * TE device augmentations
   */
  augment "/te:te" {
    description
      "TE global container.";
    /* TE Interface Configuration Data */
    container interfaces {
      description
        "Configuration data model for TE interfaces.";
      uses te-igp-flooding-bandwidth-config;
      list interface {
        key "name";
        description
          "The list of interfaces enabled for TE.";
        leaf name {
          type if:interface-ref;
          description
            "The reference to interface enabled for TE.";
        }
        /* TE interface parameters */
        leaf te-metric {
          type te-types:te-metric;
          description
            "TE interface metric.";
        }
        choice admin-group-type {
          description
            "TE interface administrative groups
             representation type.";
          case value-admin-groups {
            choice value-admin-group-type {
              description
                "The type of admin-groups.";
              case admin-groups {
                description
                  "Administrative group/Resource
                   class.";
                leaf admin-group {
                  type te-types:admin-group;
                  description
                    "TE interface administrative group.";
                }
              }
              case extended-admin-groups {
                if-feature "te-types:extended-admin-groups";
                description
                  "Extended administrative group/Resource
                   class.";
                leaf extended-admin-group {
                  type te-types:extended-admin-group;
                  description
                    "TE interface extended administrative group.";
                }
              }
            }
          }
          case named-admin-groups {
            list named-admin-groups {
              if-feature "te-types:extended-admin-groups";
              if-feature "te-types:named-extended-admin-groups";
              key "named-admin-group";
              description
                "A list of named admin-group entries.";
              leaf named-admin-group {
                type leafref {
                  path "../../../../te:globals/"
                     + "te:named-admin-groups/te:named-admin-group/"
                     + "te:name";
                }
                description
                  "A named admin-group entry.";
              }
            }
          }
        }
        choice srlg-type {
          description
            "Choice of SRLG configuration.";
          case value-srlgs {
            list values {
              key "value";
              description
                "List of SRLG values that
                 this link is part of.";
              leaf value {
                type uint32 {
                  range "0..4294967295";
                }
                description
                  "Value of the SRLG.";
              }
            }
          }
          case named-srlgs {
            list named-srlgs {
              if-feature "te-types:named-srlg-groups";
              key "named-srlg";
              description
                "A list of named SRLG entries.";
              leaf named-srlg {
                type leafref {
                  path "../../../../te:globals/"
                     + "te:named-srlgs/te:named-srlg/te:name";
                }
                description
                  "A named SRLG entry.";
              }
            }
          }
        }
        uses te-igp-flooding-bandwidth-config;
        list switching-capabilities {
          key "switching-capability";
          description
            "List of interface capabilities for this interface.";
          leaf switching-capability {
            type identityref {
              base te-types:switching-capabilities;
            }
            description
              "Switching Capability for this interface.";
          }
          leaf encoding {
            type identityref {
              base te-types:lsp-encoding-types;
            }
            description
              "Encoding supported by this interface.";
          }
        }
        container te-advertisements-state {
          config false;
          description
            "TE interface advertisements state container.";
          leaf flood-interval {
            type uint32;
            description
              "The periodic flooding interval.";
          }
          leaf last-flooded-time {
            type uint32;
            units "seconds";
            description
              "Time elapsed since last flooding in seconds.";
          }
          leaf next-flooded-time {
            type uint32;
            units "seconds";
            description
              "Time remained for next flooding in seconds.";
          }
          leaf last-flooded-trigger {
            type enumeration {
              enum link-up {
                description
                  "Link-up flooding trigger.";
              }
              enum link-down {
                description
                  "Link-down flooding trigger.";
              }
              enum threshold-up {
                description
                  "Bandwidth reservation up threshold.";
              }
              enum threshold-down {
                description
                  "Bandwidth reservation down threshold.";
              }
              enum bandwidth-change {
                description
                  "Bandwidth capacity change.";
              }
              enum user-initiated {
                description
                  "Initiated by user.";
              }
              enum srlg-change {
                description
                  "SRLG property change.";
              }
              enum periodic-timer {
                description
                  "Periodic timer expired.";
              }
            }
            default "periodic-timer";
            description
              "Trigger for the last flood.";
          }
          list advertised-level-areas {
            key "level-area";
            description
              "List of level-areas that the TE interface is
               advertised in.";
            leaf level-area {
              type uint32;
              description
                "The IGP area or level where the TE interface link
                 state is advertised in.";
            }
          }
        }
      }
    }
  }

  /* TE globals device augmentation */

  augment "/te:te/te:globals" {
    description
      "Global TE device specific configuration parameters.";
    uses lsp-device-timers;
  }

  /* TE tunnels device configuration augmentation */

  augment "/te:te/te:tunnels/te:tunnel" {
    description
      "Tunnel device dependent augmentation.";
    leaf path-invalidation-action {
      type identityref {
        base te-types:path-invalidation-action-type;
      }
      description
        "Tunnel path invalidation action.";
    }
    uses lsp-device-timers;
  }

  /* TE LSPs device state augmentation */

  augment "/te:te/te:lsps/te:lsp" {
    description
      "TE LSP device dependent augmentation.";
    container lsp-timers {
      when "../te:origin-type = 'ingress'" {
        description
          "Applicable to ingress LSPs only.";
      }
      description
        "Ingress LSP timers.";
      leaf uptime {
        type uint32;
        units "seconds";
        description
          "The LSP uptime.";
      }
      leaf time-to-install {
        type uint32;
        units "seconds";
        description
          "The time remaining for a new LSP to be instantiated
           in forwarding to carry traffic.";
      }
      leaf time-to-destroy {
        type uint32;
        units "seconds";
        description
          "The time remaining for an existing LSP to be torn down.";
      }
    }
    container downstream-info {
      when "../te:origin-type != 'egress'" {
        description
          "Downstream information of the LSP.";
      }
      description
        "Downstream information.";
      leaf nhop {
        type te-types:te-tp-id;
        description
          "Downstream next-hop address.";
      }
      leaf outgoing-interface {
        type if:interface-ref;
        description
          "Downstream interface.";
      }
      container neighbor {
        uses te-types:te-generic-node-id;
        description
          "Downstream neighbor address.";
      }
      leaf label {
        type rt-types:generalized-label;
        description
          "Downstream label.";
      }
    }
    container upstream-info {
      when "../te:origin-type != 'ingress'" {
        description
          "Upstream information of the LSP.";
      }
      description
        "Upstream information.";
      leaf phop {
        type te-types:te-tp-id;
        description
          "Upstream next-hop or previous-hop address.";
      }
      container neighbor {
        uses te-types:te-generic-node-id;
        description
          "Upstream neighbor address.";
      }
      leaf label {
        type rt-types:generalized-label;
        description
          "Upstream label.";
      }
    }
  }

  /* TE interfaces RPCs/execution Data */

  rpc link-state-update {
    description
      "Triggers a link state update for the specific interface.";
    input {
      choice filter-type {
        mandatory true;
        description
          "Filter choice.";
        case match-all {
          leaf all {
            type empty;
            mandatory true;
            description
              "Match all TE interfaces.";
          }
        }
        case match-one-interface {
          leaf interface {
            type if:interface-ref;
            description
              "Match a specific TE interface.";
          }
        }
      }
    }
  }
}</sourcecode>
      </section>
    </section>
    <section anchor="notifications" numbered="true" removeInRFC="false" toc="include" pn="section-7">
      <name slugifiedName="name-notifications">Notifications</name>
      <t indent="0" pn="section-7-1">Notifications are a key component of any topology data model.</t>
      <t indent="0" pn="section-7-2"><xref target="RFC8639" format="default" sectionFormat="of" derivedContent="RFC8639"/> and <xref target="RFC8641" format="default" sectionFormat="of" derivedContent="RFC8641"/> define a subscription mechanism and a push
mechanism for YANG datastores. These mechanisms currently allow the
user to:</t>
      <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-7-3">
        <li pn="section-7-3.1">
          <t indent="0" pn="section-7-3.1.1">Subscribe to notifications on a per-client basis.</t>
        </li>
        <li pn="section-7-3.2">
          <t indent="0" pn="section-7-3.2.1">Specify subtree filters or XML Path Language (XPath) filters so
that only contents of interest will be sent.</t>
        </li>
        <li pn="section-7-3.3">
          <t indent="0" pn="section-7-3.3.1">Specify either periodic or on-demand notifications.</t>
        </li>
      </ul>
    </section>
    <section anchor="iana-considerations" numbered="true" removeInRFC="false" toc="include" pn="section-8">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <t indent="0" pn="section-8-1">This document registers the following URIs in the IETF XML registry
<xref target="RFC3688" format="default" sectionFormat="of" derivedContent="RFC3688"/>.
Following the format in <xref target="RFC3688" format="default" sectionFormat="of" derivedContent="RFC3688"/>, the following registrations have been made.</t>
      <dl spacing="compact" newline="false" indent="3" pn="section-8-2">
        <dt pn="section-8-2.1">URI:</dt>
        <dd pn="section-8-2.2">urn:ietf:params:xml:ns:yang:ietf-te</dd>
        <dt pn="section-8-2.3">Registrant Contact:</dt>
        <dd pn="section-8-2.4">The IESG.</dd>
        <dt pn="section-8-2.5">XML:</dt>
        <dd pn="section-8-2.6">N/A; the requested URI is an XML namespace.</dd>
      </dl>
      <dl spacing="compact" newline="false" indent="3" pn="section-8-3">
        <dt pn="section-8-3.1">URI:</dt>
        <dd pn="section-8-3.2">urn:ietf:params:xml:ns:yang:ietf-te-device</dd>
        <dt pn="section-8-3.3">Registrant Contact:</dt>
        <dd pn="section-8-3.4">The IESG.</dd>
        <dt pn="section-8-3.5">XML:</dt>
        <dd pn="section-8-3.6">N/A; the requested URI is an XML namespace.</dd>
      </dl>
      <t indent="0" pn="section-8-4">IANA has registered two YANG modules in the "YANG Module Names"
registry <xref target="RFC6020" format="default" sectionFormat="of" derivedContent="RFC6020"/>.</t>
      <dl spacing="compact" newline="false" indent="3" pn="section-8-5">
        <dt pn="section-8-5.1">Name:</dt>
        <dd pn="section-8-5.2">ietf-te</dd>
        <dt pn="section-8-5.3">Namespace:</dt>
        <dd pn="section-8-5.4">urn:ietf:params:xml:ns:yang:ietf-te</dd>
        <dt pn="section-8-5.5">Prefix:</dt>
        <dd pn="section-8-5.6">te</dd>
        <dt pn="section-8-5.7">Reference:</dt>
        <dd pn="section-8-5.8">RFC 10057</dd>
        <dt pn="section-8-5.9">Maintained by IANA:</dt>
        <dd pn="section-8-5.10">N</dd>
      </dl>
      <dl spacing="compact" newline="false" indent="3" pn="section-8-6">
        <dt pn="section-8-6.1">Name:</dt>
        <dd pn="section-8-6.2">ietf-te-device</dd>
        <dt pn="section-8-6.3">Namespace:</dt>
        <dd pn="section-8-6.4">urn:ietf:params:xml:ns:yang:ietf-te-device</dd>
        <dt pn="section-8-6.5">Prefix:</dt>
        <dd pn="section-8-6.6">te-device</dd>
        <dt pn="section-8-6.7">Reference:</dt>
        <dd pn="section-8-6.8">RFC 10057</dd>
        <dt pn="section-8-6.9">Maintained by IANA:</dt>
        <dd pn="section-8-6.10">N</dd>
      </dl>
    </section>
    <section anchor="security-considerations" numbered="true" removeInRFC="false" toc="include" pn="section-9">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <t indent="0" pn="section-9-1">The "ietf-te" and "ietf-te-device" YANG modules define a data model that is
designed to be accessed via YANG-based management protocols, such as the Network Configuration Protocol (NETCONF) <xref target="RFC6241" format="default" sectionFormat="of" derivedContent="RFC6241"/> and RESTCONF <xref target="RFC8040" format="default" sectionFormat="of" derivedContent="RFC8040"/>. These YANG-based management
protocols (1) have to use a secure transport layer
(e.g., Secure Shell (SSH) <xref target="RFC6242" format="default" sectionFormat="of" derivedContent="RFC6242"/>, TLS <xref target="RFC9846" format="default" sectionFormat="of" derivedContent="RFC9846"/>, and QUIC <xref target="RFC9000" format="default" sectionFormat="of" derivedContent="RFC9000"/>) and (2) have
to use mutual authentication.</t>
      <t indent="0" pn="section-9-2">The Network Configuration Access Control Model (NACM) <xref target="RFC8341" format="default" sectionFormat="of" derivedContent="RFC8341"/> provides the
means to restrict access for particular NETCONF or RESTCONF users to a
preconfigured subset of all available NETCONF or RESTCONF protocol operations
and content.</t>
      <t indent="0" pn="section-9-3">There are a number of data nodes defined in these YANG modules that are writable/creatable/deletable (i.e., "config true", which is the default). All writable data nodes are likely to be sensitive or
vulnerable in some network environments. Write operations (e.g., edit-config) and delete operations to these data
nodes without proper protection or authentication can have a negative
effect on network operations.  The following subtrees and data nodes
have particular sensitivities/vulnerabilities:</t>
      <dl spacing="normal" newline="true" indent="3" pn="section-9-4">
        <dt pn="section-9-4.1">"/te/globals":</dt>
        <dd pn="section-9-4.2">This module specifies the global TE configurations on a device.
Unauthorized access to this container could cause the device to ignore packets
it should receive and process.</dd>
        <dt pn="section-9-4.3">"/te/tunnels":</dt>
        <dd pn="section-9-4.4">This list specifies the configuration and state of TE Tunnels
present on the device or controller. Unauthorized access to this list could
cause the device to ignore packets it should receive and process. An attacker
may also use state to derive information about the network topology
and subsequently orchestrate further attacks.</dd>
        <dt pn="section-9-4.5">"/te/interfaces":</dt>
        <dd pn="section-9-4.6">This list specifies the configuration and state TE interfaces
on a device. Unauthorized access to this list could cause the device to ignore packets it
should receive and process.</dd>
      </dl>
      <t indent="0" pn="section-9-5">Some of the readable data nodes in these YANG modules 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.
Specifically, the following subtrees and data nodes have particular sensitivities/vulnerabilities:</t>
      <dl spacing="normal" newline="true" indent="3" pn="section-9-6">
        <dt pn="section-9-6.1">"/te/lsps":</dt>
        <dd pn="section-9-6.2">This list contains information state about established LSPs in the network.
An attacker can use this information to derive information about the network topology
and subsequently orchestrate further attacks.</dd>
      </dl>
      <t indent="0" pn="section-9-7">Some of the RPC or action operations in these YANG modules may be
considered sensitive or vulnerable in some network environments.
It is thus important to control access to these operations.
Specifically, the following operations have particular
sensitivities/ vulnerabilities:
</t>
      <dl spacing="normal" newline="true" indent="3" pn="section-9-8">
        <dt pn="section-9-8.1">"/te/tunnels-actions":</dt>
        <dd pn="section-9-8.2">Using this RPC, an attacker can modify existing paths that
may be carrying live traffic, and hence result in interruption to services
carried over the network.</dd>
        <dt pn="section-9-8.3">"/te/tunnels-path-compute":</dt>
        <dd pn="section-9-8.4">Using this RPC, an attacker can retrieve sensitive
information about the network provider which can be used to orchestrate further
attacks.</dd>
      </dl>
      <t indent="0" pn="section-9-9">The "ietf-te" YANG module defines a set of identities, types, and
groupings.  These nodes are intended to be reused by other YANG
modules.  The module by itself does not expose any data nodes that
are writable, data nodes that contain read-only state, or RPCs.
As such, there are no additional security issues related to
the "ietf-te" YANG module that need to be considered.
</t>
      <t indent="0" pn="section-9-10">Modules that use the groupings that are defined in this document
should identify the corresponding security considerations.  For
example, reusing some of these groupings will expose privacy-related
information (e.g., 'node-example').</t>
    </section>
  </middle>
  <back>
    <displayreference target="I-D.ietf-teas-yang-path-computation" to="PATH-COMP"/>
    <references anchor="sec-combined-references" pn="section-10">
      <name slugifiedName="name-references">References</name>
      <references anchor="sec-normative-references" pn="section-10.1">
        <name slugifiedName="name-normative-references">Normative References</name>
        <reference anchor="ITU_G.808.1" target="https://www.itu.int/rec/T-REC-G.808.1-201405-I" quoteTitle="true" derivedAnchor="ITU_G.808.1">
          <front>
            <title>Generic protection switching - Linear trail and subnetwork protection</title>
            <author>
              <organization showOnFrontPage="true">ITU-T</organization>
            </author>
            <date year="2014" month="May"/>
          </front>
          <seriesInfo name="ITU-T Recommendation" value="G.808.1"/>
        </reference>
        <reference anchor="RFC3209" target="https://www.rfc-editor.org/info/rfc3209" quoteTitle="true" derivedAnchor="RFC3209">
          <front>
            <title>RSVP-TE: Extensions to RSVP for LSP Tunnels</title>
            <author fullname="D. Awduche" initials="D." surname="Awduche"/>
            <author fullname="L. Berger" initials="L." surname="Berger"/>
            <author fullname="D. Gan" initials="D." surname="Gan"/>
            <author fullname="T. Li" initials="T." surname="Li"/>
            <author fullname="V. Srinivasan" initials="V." surname="Srinivasan"/>
            <author fullname="G. Swallow" initials="G." surname="Swallow"/>
            <date month="December" year="2001"/>
            <abstract>
              <t indent="0">This document describes the use of RSVP (Resource Reservation Protocol), including all the necessary extensions, to establish label-switched paths (LSPs) in MPLS (Multi-Protocol Label Switching). Since the flow along an LSP is completely identified by the label applied at the ingress node of the path, these paths may be treated as tunnels. A key application of LSP tunnels is traffic engineering with MPLS as specified in RFC 2702. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3209"/>
          <seriesInfo name="DOI" value="10.17487/RFC3209"/>
        </reference>
        <reference anchor="RFC3473" target="https://www.rfc-editor.org/info/rfc3473" quoteTitle="true" derivedAnchor="RFC3473">
          <front>
            <title>Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions</title>
            <author fullname="L. Berger" initials="L." role="editor" surname="Berger"/>
            <date month="February" year="2003"/>
            <abstract>
              <t indent="0">This document describes extensions to Multi-Protocol Label Switching (MPLS) Resource ReserVation Protocol - Traffic Engineering (RSVP-TE) signaling required to support Generalized MPLS. Generalized MPLS extends the MPLS control plane to encompass time-division (e.g., Synchronous Optical Network and Synchronous Digital Hierarchy, SONET/SDH), wavelength (optical lambdas) and spatial switching (e.g., incoming port or fiber to outgoing port or fiber). This document presents a RSVP-TE specific description of the extensions. A generic functional description can be found in separate documents. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3473"/>
          <seriesInfo name="DOI" value="10.17487/RFC3473"/>
        </reference>
        <reference anchor="RFC3688" target="https://www.rfc-editor.org/info/rfc3688" quoteTitle="true" derivedAnchor="RFC3688">
          <front>
            <title>The IETF XML Registry</title>
            <author fullname="M. Mealling" initials="M." surname="Mealling"/>
            <date month="January" year="2004"/>
            <abstract>
              <t indent="0">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="RFC4206" target="https://www.rfc-editor.org/info/rfc4206" quoteTitle="true" derivedAnchor="RFC4206">
          <front>
            <title>Label Switched Paths (LSP) Hierarchy with Generalized Multi-Protocol Label Switching (GMPLS) Traffic Engineering (TE)</title>
            <author fullname="K. Kompella" initials="K." surname="Kompella"/>
            <author fullname="Y. Rekhter" initials="Y." surname="Rekhter"/>
            <date month="October" year="2005"/>
            <abstract>
              <t indent="0">To improve scalability of Generalized Multi-Protocol Label Switching (GMPLS) it may be useful to aggregate Label Switched Paths (LSPs) by creating a hierarchy of such LSPs. A way to create such a hierarchy is by (a) a Label Switching Router (LSR) creating a Traffic Engineering Label Switched Path (TE LSP), (b) the LSR forming a forwarding adjacency (FA) out of that LSP (by advertising this LSP as a Traffic Engineering (TE) link into the same instance of ISIS/OSPF as the one that was used to create the LSP), (c) allowing other LSRs to use FAs for their path computation, and (d) nesting of LSPs originated by other LSRs into that LSP (by using the label stack construct).</t>
              <t indent="0">This document describes the mechanisms to accomplish this. [PROPOSED STANDARD]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4206"/>
          <seriesInfo name="DOI" value="10.17487/RFC4206"/>
        </reference>
        <reference anchor="RFC4655" target="https://www.rfc-editor.org/info/rfc4655" quoteTitle="true" derivedAnchor="RFC4655">
          <front>
            <title>A Path Computation Element (PCE)-Based Architecture</title>
            <author fullname="A. Farrel" initials="A." surname="Farrel"/>
            <author fullname="J.-P. Vasseur" initials="J.-P." surname="Vasseur"/>
            <author fullname="J. Ash" initials="J." surname="Ash"/>
            <date month="August" year="2006"/>
            <abstract>
              <t indent="0">Constraint-based path computation is a fundamental building block for traffic engineering systems such as Multiprotocol Label Switching (MPLS) and Generalized Multiprotocol Label Switching (GMPLS) networks. Path computation in large, multi-domain, multi-region, or multi-layer networks is complex and may require special computational components and cooperation between the different network domains.</t>
              <t indent="0">This document specifies the architecture for a Path Computation Element (PCE)-based model to address this problem space. This document does not attempt to provide a detailed description of all the architectural components, but rather it describes a set of building blocks for the PCE architecture from which solutions may be constructed. This memo provides information for the Internet community.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4655"/>
          <seriesInfo name="DOI" value="10.17487/RFC4655"/>
        </reference>
        <reference anchor="RFC4872" target="https://www.rfc-editor.org/info/rfc4872" quoteTitle="true" derivedAnchor="RFC4872">
          <front>
            <title>RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery</title>
            <author fullname="J.P. Lang" initials="J.P." role="editor" surname="Lang"/>
            <author fullname="Y. Rekhter" initials="Y." role="editor" surname="Rekhter"/>
            <author fullname="D. Papadimitriou" initials="D." role="editor" surname="Papadimitriou"/>
            <date month="May" year="2007"/>
            <abstract>
              <t indent="0">This document describes protocol-specific procedures and extensions for Generalized Multi-Protocol Label Switching (GMPLS) Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE) signaling to support end-to-end Label Switched Path (LSP) recovery that denotes protection and restoration. A generic functional description of GMPLS recovery can be found in a companion document, RFC 4426. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4872"/>
          <seriesInfo name="DOI" value="10.17487/RFC4872"/>
        </reference>
        <reference anchor="RFC6020" target="https://www.rfc-editor.org/info/rfc6020" quoteTitle="true" derivedAnchor="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 indent="0">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="RFC6780" target="https://www.rfc-editor.org/info/rfc6780" quoteTitle="true" derivedAnchor="RFC6780">
          <front>
            <title>RSVP ASSOCIATION Object Extensions</title>
            <author fullname="L. Berger" initials="L." surname="Berger"/>
            <author fullname="F. Le Faucheur" initials="F." surname="Le Faucheur"/>
            <author fullname="A. Narayanan" initials="A." surname="Narayanan"/>
            <date month="October" year="2012"/>
            <abstract>
              <t indent="0">The RSVP ASSOCIATION object was defined in the context of GMPLS-controlled Label Switched Paths (LSPs). In this context, the object is used to associate recovery LSPs with the LSP they are protecting. This object also has broader applicability as a mechanism to associate RSVP state. This document defines how the ASSOCIATION object can be more generally applied. This document also defines Extended ASSOCIATION objects that, in particular, can be used in the context of the MPLS Transport Profile (MPLS-TP). This document updates RFC 2205, RFC 3209, and RFC 3473. It also generalizes the definition of the Association ID field defined in RFC 4872. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6780"/>
          <seriesInfo name="DOI" value="10.17487/RFC6780"/>
        </reference>
        <reference anchor="RFC7271" target="https://www.rfc-editor.org/info/rfc7271" quoteTitle="true" derivedAnchor="RFC7271">
          <front>
            <title>MPLS Transport Profile (MPLS-TP) Linear Protection to Match the Operational Expectations of Synchronous Digital Hierarchy, Optical Transport Network, and Ethernet Transport Network Operators</title>
            <author fullname="J. Ryoo" initials="J." role="editor" surname="Ryoo"/>
            <author fullname="E. Gray" initials="E." role="editor" surname="Gray"/>
            <author fullname="H. van Helvoort" initials="H." surname="van Helvoort"/>
            <author fullname="A. D'Alessandro" initials="A." surname="D'Alessandro"/>
            <author fullname="T. Cheung" initials="T." surname="Cheung"/>
            <author fullname="E. Osborne" initials="E." surname="Osborne"/>
            <date month="June" year="2014"/>
            <abstract>
              <t indent="0">This document describes alternate mechanisms to perform some of the functions of MPLS Transport Profile (MPLS-TP) linear protection defined in RFC 6378, and also defines additional mechanisms. The purpose of these alternate and additional mechanisms is to provide operator control and experience that more closely models the behavior of linear protection seen in other transport networks.</t>
              <t indent="0">This document also introduces capabilities and modes for linear protection. A capability is an individual behavior, and a mode is a particular combination of capabilities. Two modes are defined in this document: Protection State Coordination (PSC) mode and Automatic Protection Switching (APS) mode.</t>
              <t indent="0">This document describes the behavior of the PSC protocol including priority logic and state machine when all the capabilities associated with the APS mode are enabled.</t>
              <t indent="0">This document updates RFC 6378 in that the capability advertisement method defined here is an addition to that document.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7271"/>
          <seriesInfo name="DOI" value="10.17487/RFC7271"/>
        </reference>
        <reference anchor="RFC7308" target="https://www.rfc-editor.org/info/rfc7308" quoteTitle="true" derivedAnchor="RFC7308">
          <front>
            <title>Extended Administrative Groups in MPLS Traffic Engineering (MPLS-TE)</title>
            <author fullname="E. Osborne" initials="E." surname="Osborne"/>
            <date month="July" year="2014"/>
            <abstract>
              <t indent="0">MPLS Traffic Engineering (MPLS-TE) advertises 32 administrative groups (commonly referred to as "colors" or "link colors") using the Administrative Group sub-TLV. This is defined for OSPFv2 (RFC 3630), OSPFv3 (RFC 5329) and IS-IS (RFC 5305).</t>
              <t indent="0">This document adds a sub-TLV to the IGP TE extensions, "Extended Administrative Group". This sub-TLV provides for additional administrative groups (link colors) beyond the current limit of 32.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7308"/>
          <seriesInfo name="DOI" value="10.17487/RFC7308"/>
        </reference>
        <reference anchor="RFC7471" target="https://www.rfc-editor.org/info/rfc7471" quoteTitle="true" derivedAnchor="RFC7471">
          <front>
            <title>OSPF Traffic Engineering (TE) Metric Extensions</title>
            <author fullname="S. Giacalone" initials="S." surname="Giacalone"/>
            <author fullname="D. Ward" initials="D." surname="Ward"/>
            <author fullname="J. Drake" initials="J." surname="Drake"/>
            <author fullname="A. Atlas" initials="A." surname="Atlas"/>
            <author fullname="S. Previdi" initials="S." surname="Previdi"/>
            <date month="March" year="2015"/>
            <abstract>
              <t indent="0">In certain networks, such as, but not limited to, financial information networks (e.g., stock market data providers), network performance information (e.g., link propagation delay) is becoming critical to data path selection.</t>
              <t indent="0">This document describes common extensions to RFC 3630 "Traffic Engineering (TE) Extensions to OSPF Version 2" and RFC 5329 "Traffic Engineering Extensions to OSPF Version 3" to enable network performance information to be distributed in a scalable fashion. The information distributed using OSPF TE Metric Extensions can then be used to make path selection decisions based on network performance.</t>
              <t indent="0">Note that this document only covers the mechanisms by which network performance information is distributed. The mechanisms for measuring network performance information or using that information, once distributed, are outside the scope of this document.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7471"/>
          <seriesInfo name="DOI" value="10.17487/RFC7471"/>
        </reference>
        <reference anchor="RFC7950" target="https://www.rfc-editor.org/info/rfc7950" quoteTitle="true" derivedAnchor="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 indent="0">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="RFC8231" target="https://www.rfc-editor.org/info/rfc8231" quoteTitle="true" derivedAnchor="RFC8231">
          <front>
            <title>Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE</title>
            <author fullname="E. Crabbe" initials="E." surname="Crabbe"/>
            <author fullname="I. Minei" initials="I." surname="Minei"/>
            <author fullname="J. Medved" initials="J." surname="Medved"/>
            <author fullname="R. Varga" initials="R." surname="Varga"/>
            <date month="September" year="2017"/>
            <abstract>
              <t indent="0">The Path Computation Element Communication Protocol (PCEP) provides mechanisms for Path Computation Elements (PCEs) to perform path computations in response to Path Computation Client (PCC) requests.</t>
              <t indent="0">Although PCEP explicitly makes no assumptions regarding the information available to the PCE, it also makes no provisions for PCE control of timing and sequence of path computations within and across PCEP sessions. This document describes a set of extensions to PCEP to enable stateful control of MPLS-TE and GMPLS Label Switched Paths (LSPs) via PCEP.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8231"/>
          <seriesInfo name="DOI" value="10.17487/RFC8231"/>
        </reference>
        <reference anchor="RFC8232" target="https://www.rfc-editor.org/info/rfc8232" quoteTitle="true" derivedAnchor="RFC8232">
          <front>
            <title>Optimizations of Label Switched Path State Synchronization Procedures for a Stateful PCE</title>
            <author fullname="E. Crabbe" initials="E." surname="Crabbe"/>
            <author fullname="I. Minei" initials="I." surname="Minei"/>
            <author fullname="J. Medved" initials="J." surname="Medved"/>
            <author fullname="R. Varga" initials="R." surname="Varga"/>
            <author fullname="X. Zhang" initials="X." surname="Zhang"/>
            <author fullname="D. Dhody" initials="D." surname="Dhody"/>
            <date month="September" year="2017"/>
            <abstract>
              <t indent="0">A stateful Path Computation Element (PCE) has access to not only the information disseminated by the network's Interior Gateway Protocol (IGP) but also the set of active paths and their reserved resources for its computation. The additional Label Switched Path (LSP) state information allows the PCE to compute constrained paths while considering individual LSPs and their interactions. This requires a State Synchronization mechanism between the PCE and the network, the PCE and Path Computation Clients (PCCs), and cooperating PCEs. The basic mechanism for State Synchronization is part of the stateful PCE specification. This document presents motivations for optimizations to the base State Synchronization procedure and specifies the required Path Computation Element Communication Protocol (PCEP) extensions.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8232"/>
          <seriesInfo name="DOI" value="10.17487/RFC8232"/>
        </reference>
        <reference anchor="RFC8234" target="https://www.rfc-editor.org/info/rfc8234" quoteTitle="true" derivedAnchor="RFC8234">
          <front>
            <title>Updates to MPLS Transport Profile (MPLS-TP) Linear Protection in Automatic Protection Switching (APS) Mode</title>
            <author fullname="J. Ryoo" initials="J." surname="Ryoo"/>
            <author fullname="T. Cheung" initials="T." surname="Cheung"/>
            <author fullname="H. van Helvoort" initials="H." surname="van Helvoort"/>
            <author fullname="I. Busi" initials="I." surname="Busi"/>
            <author fullname="G. Wen" initials="G." surname="Wen"/>
            <date month="August" year="2017"/>
            <abstract>
              <t indent="0">This document contains updates to MPLS Transport Profile (MPLS-TP) linear protection in Automatic Protection Switching (APS) mode defined in RFC 7271. The updates provide rules related to the initialization of the Protection State Coordination (PSC) Control Logic (in which the state machine resides) when operating in APS mode and clarify the operation related to state transition table lookup.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8234"/>
          <seriesInfo name="DOI" value="10.17487/RFC8234"/>
        </reference>
        <reference anchor="RFC8294" target="https://www.rfc-editor.org/info/rfc8294" quoteTitle="true" derivedAnchor="RFC8294">
          <front>
            <title>Common YANG Data Types for the Routing Area</title>
            <author fullname="X. Liu" initials="X." surname="Liu"/>
            <author fullname="Y. Qu" initials="Y." surname="Qu"/>
            <author fullname="A. Lindem" initials="A." surname="Lindem"/>
            <author fullname="C. Hopps" initials="C." surname="Hopps"/>
            <author fullname="L. Berger" initials="L." surname="Berger"/>
            <date month="December" year="2017"/>
            <abstract>
              <t indent="0">This document defines a collection of common data types using the YANG data modeling language. These derived common types are designed to be imported by other modules defined in the routing area.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8294"/>
          <seriesInfo name="DOI" value="10.17487/RFC8294"/>
        </reference>
        <reference anchor="RFC8340" target="https://www.rfc-editor.org/info/rfc8340" quoteTitle="true" derivedAnchor="RFC8340">
          <front>
            <title>YANG Tree Diagrams</title>
            <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
            <author fullname="L. Berger" initials="L." role="editor" surname="Berger"/>
            <date month="March" year="2018"/>
            <abstract>
              <t indent="0">This document captures the current syntax used in YANG module tree diagrams. The purpose of this document is to provide a single location for this definition. This syntax may be updated from time to time based on the evolution of the YANG language.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="215"/>
          <seriesInfo name="RFC" value="8340"/>
          <seriesInfo name="DOI" value="10.17487/RFC8340"/>
        </reference>
        <reference anchor="RFC8341" target="https://www.rfc-editor.org/info/rfc8341" quoteTitle="true" derivedAnchor="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 indent="0">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 indent="0">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" target="https://www.rfc-editor.org/info/rfc8343" quoteTitle="true" derivedAnchor="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 indent="0">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 indent="0">The YANG data model in this document conforms to the Network Management Datastore Architecture (NMDA) defined in RFC 8342.</t>
              <t indent="0">This document obsoletes RFC 7223.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8343"/>
          <seriesInfo name="DOI" value="10.17487/RFC8343"/>
        </reference>
        <reference anchor="RFC8345" target="https://www.rfc-editor.org/info/rfc8345" quoteTitle="true" derivedAnchor="RFC8345">
          <front>
            <title>A YANG Data Model for Network Topologies</title>
            <author fullname="A. Clemm" initials="A." surname="Clemm"/>
            <author fullname="J. Medved" initials="J." surname="Medved"/>
            <author fullname="R. Varga" initials="R." surname="Varga"/>
            <author fullname="N. Bahadur" initials="N." surname="Bahadur"/>
            <author fullname="H. Ananthakrishnan" initials="H." surname="Ananthakrishnan"/>
            <author fullname="X. Liu" initials="X." surname="Liu"/>
            <date month="March" year="2018"/>
            <abstract>
              <t indent="0">This document defines an abstract (generic, or base) YANG data model for network/service topologies and inventories. The data model serves as a base model that is augmented with technology-specific details in other, more specific topology and inventory data models.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8345"/>
          <seriesInfo name="DOI" value="10.17487/RFC8345"/>
        </reference>
        <reference anchor="RFC8570" target="https://www.rfc-editor.org/info/rfc8570" quoteTitle="true" derivedAnchor="RFC8570">
          <front>
            <title>IS-IS Traffic Engineering (TE) Metric Extensions</title>
            <author fullname="L. Ginsberg" initials="L." role="editor" surname="Ginsberg"/>
            <author fullname="S. Previdi" initials="S." role="editor" surname="Previdi"/>
            <author fullname="S. Giacalone" initials="S." surname="Giacalone"/>
            <author fullname="D. Ward" initials="D." surname="Ward"/>
            <author fullname="J. Drake" initials="J." surname="Drake"/>
            <author fullname="Q. Wu" initials="Q." surname="Wu"/>
            <date month="March" year="2019"/>
            <abstract>
              <t indent="0">In certain networks, such as, but not limited to, financial information networks (e.g., stock market data providers), network-performance criteria (e.g., latency) are becoming as critical to data-path selection as other metrics.</t>
              <t indent="0">This document describes extensions to IS-IS Traffic Engineering Extensions (RFC 5305). These extensions provide a way to distribute and collect network-performance information in a scalable fashion. The information distributed using IS-IS TE Metric Extensions can then be used to make path-selection decisions based on network performance.</t>
              <t indent="0">Note that this document only covers the mechanisms with which network-performance information is distributed. The mechanisms for measuring network performance or acting on that information, once distributed, are outside the scope of this document.</t>
              <t indent="0">This document obsoletes RFC 7810.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8570"/>
          <seriesInfo name="DOI" value="10.17487/RFC8570"/>
        </reference>
        <reference anchor="RFC8639" target="https://www.rfc-editor.org/info/rfc8639" quoteTitle="true" derivedAnchor="RFC8639">
          <front>
            <title>Subscription to YANG Notifications</title>
            <author fullname="E. Voit" initials="E." surname="Voit"/>
            <author fullname="A. Clemm" initials="A." surname="Clemm"/>
            <author fullname="A. Gonzalez Prieto" initials="A." surname="Gonzalez Prieto"/>
            <author fullname="E. Nilsen-Nygaard" initials="E." surname="Nilsen-Nygaard"/>
            <author fullname="A. Tripathy" initials="A." surname="Tripathy"/>
            <date month="September" year="2019"/>
            <abstract>
              <t indent="0">This document defines a YANG data model and associated mechanisms enabling subscriber-specific subscriptions to a publisher's event streams. Applying these elements allows a subscriber to request and receive a continuous, customized feed of publisher-generated information.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8639"/>
          <seriesInfo name="DOI" value="10.17487/RFC8639"/>
        </reference>
        <reference anchor="RFC8641" target="https://www.rfc-editor.org/info/rfc8641" quoteTitle="true" derivedAnchor="RFC8641">
          <front>
            <title>Subscription to YANG Notifications for Datastore Updates</title>
            <author fullname="A. Clemm" initials="A." surname="Clemm"/>
            <author fullname="E. Voit" initials="E." surname="Voit"/>
            <date month="September" year="2019"/>
            <abstract>
              <t indent="0">This document describes a mechanism that allows subscriber applications to request a continuous and customized stream of updates from a YANG datastore. Providing such visibility into updates enables new capabilities based on the remote mirroring and monitoring of configuration and operational state.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8641"/>
          <seriesInfo name="DOI" value="10.17487/RFC8641"/>
        </reference>
        <reference anchor="RFC8795" target="https://www.rfc-editor.org/info/rfc8795" quoteTitle="true" derivedAnchor="RFC8795">
          <front>
            <title>YANG Data Model for Traffic Engineering (TE) Topologies</title>
            <author fullname="X. Liu" initials="X." surname="Liu"/>
            <author fullname="I. Bryskin" initials="I." surname="Bryskin"/>
            <author fullname="V. Beeram" initials="V." surname="Beeram"/>
            <author fullname="T. Saad" initials="T." surname="Saad"/>
            <author fullname="H. Shah" initials="H." surname="Shah"/>
            <author fullname="O. Gonzalez de Dios" initials="O." surname="Gonzalez de Dios"/>
            <date month="August" year="2020"/>
            <abstract>
              <t indent="0">This document defines a YANG data model for representing, retrieving, and manipulating Traffic Engineering (TE) Topologies. The model serves as a base model that other technology-specific TE topology models can augment.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8795"/>
          <seriesInfo name="DOI" value="10.17487/RFC8795"/>
        </reference>
        <reference anchor="RFC9012" target="https://www.rfc-editor.org/info/rfc9012" quoteTitle="true" derivedAnchor="RFC9012">
          <front>
            <title>The BGP Tunnel Encapsulation Attribute</title>
            <author fullname="K. Patel" initials="K." surname="Patel"/>
            <author fullname="G. Van de Velde" initials="G." surname="Van de Velde"/>
            <author fullname="S. Sangli" initials="S." surname="Sangli"/>
            <author fullname="J. Scudder" initials="J." surname="Scudder"/>
            <date month="April" year="2021"/>
            <abstract>
              <t indent="0">This document defines a BGP path attribute known as the "Tunnel Encapsulation attribute", which can be used with BGP UPDATEs of various Subsequent Address Family Identifiers (SAFIs) to provide information needed to create tunnels and their corresponding encapsulation headers. It provides encodings for a number of tunnel types, along with procedures for choosing between alternate tunnels and routing packets into tunnels.</t>
              <t indent="0">This document obsoletes RFC 5512, which provided an earlier definition of the Tunnel Encapsulation attribute. RFC 5512 was never deployed in production. Since RFC 5566 relies on RFC 5512, it is likewise obsoleted. This document updates RFC 5640 by indicating that the Load-Balancing Block sub-TLV may be included in any Tunnel Encapsulation attribute where load balancing is desired.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9012"/>
          <seriesInfo name="DOI" value="10.17487/RFC9012"/>
        </reference>
        <reference anchor="RFC9256" target="https://www.rfc-editor.org/info/rfc9256" quoteTitle="true" derivedAnchor="RFC9256">
          <front>
            <title>Segment Routing Policy Architecture</title>
            <author fullname="C. Filsfils" initials="C." surname="Filsfils"/>
            <author fullname="K. Talaulikar" initials="K." role="editor" surname="Talaulikar"/>
            <author fullname="D. Voyer" initials="D." surname="Voyer"/>
            <author fullname="A. Bogdanov" initials="A." surname="Bogdanov"/>
            <author fullname="P. Mattes" initials="P." surname="Mattes"/>
            <date month="July" year="2022"/>
            <abstract>
              <t indent="0">Segment Routing (SR) allows a node to steer a packet flow along any path. Intermediate per-path states are eliminated thanks to source routing. SR Policy is an ordered list of segments (i.e., instructions) that represent a source-routed policy. Packet flows are steered into an SR Policy on a node where it is instantiated called a headend node. The packets steered into an SR Policy carry an ordered list of segments associated with that SR Policy.</t>
              <t indent="0">This document updates RFC 8402 as it details the concepts of SR Policy and steering into an SR Policy.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9256"/>
          <seriesInfo name="DOI" value="10.17487/RFC9256"/>
        </reference>
        <reference anchor="RFC9911" target="https://www.rfc-editor.org/info/rfc9911" quoteTitle="true" derivedAnchor="RFC9911">
          <front>
            <title>Common YANG Data Types</title>
            <author fullname="J. Schönwälder" initials="J." role="editor" surname="Schönwälder"/>
            <date month="December" year="2025"/>
            <abstract>
              <t indent="0">This document defines a collection of common data types to be used with the YANG data modeling language. It includes several new type definitions and obsoletes RFC 6991.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9911"/>
          <seriesInfo name="DOI" value="10.17487/RFC9911"/>
        </reference>
        <reference anchor="RFC10056" target="https://www.rfc-editor.org/info/rfc10056" quoteTitle="true" derivedAnchor="RFC10056">
          <front>
            <title>Common YANG Data Types for Traffic Engineering</title>
            <author initials="I." surname="Busi" fullname="Italo Busi">
              <organization showOnFrontPage="true">Huawei</organization>
            </author>
            <author initials="A." surname="Guo" fullname="Aihua Guo">
              <organization showOnFrontPage="true">Futurewei Technologies</organization>
            </author>
            <author initials="X." surname="Liu" fullname="Xufeng Liu">
              <organization showOnFrontPage="true">Individual</organization>
            </author>
            <author initials="T." surname="Saad" fullname="Tarek Saad">
              <organization showOnFrontPage="true">Cisco Systems Inc.</organization>
            </author>
            <author initials="I." surname="Bryskin" fullname="Igor Bryskin">
              <organization showOnFrontPage="true">Individual</organization>
            </author>
            <date month="November" year="2026"/>
          </front>
          <seriesInfo name="RFC" value="10056"/>
          <seriesInfo name="DOI" value="10.17487/RFC10056"/>
        </reference>
      </references>
      <references anchor="sec-informative-references" pn="section-10.2">
        <name slugifiedName="name-informative-references">Informative References</name>
        <reference anchor="I-D.ietf-teas-yang-path-computation" target="https://datatracker.ietf.org/doc/html/draft-ietf-teas-yang-path-computation-28" quoteTitle="true" derivedAnchor="PATH-COMP">
          <front>
            <title>A YANG Data Model for requesting path computation</title>
            <author initials="I." surname="Busi" fullname="Italo Busi" role="editor">
              <organization showOnFrontPage="true">Huawei Technologies</organization>
            </author>
            <author initials="S." surname="Belotti" fullname="Sergio Belotti" role="editor">
              <organization showOnFrontPage="true">Nokia</organization>
            </author>
            <author initials="O." surname="Gonzales de Dios" fullname="Oscar Gonzalez de Dios">
              <organization showOnFrontPage="true">Telefonica</organization>
            </author>
            <author initials="A." surname="Sharma" fullname="Anurag Sharma">
              <organization showOnFrontPage="true">Google</organization>
            </author>
            <author initials="Y." surname="Shi" fullname="Yan Shi">
              <organization showOnFrontPage="true">China Unicom</organization>
            </author>
            <date month="May" day="12" year="2026"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-teas-yang-path-computation-28"/>
          <refcontent>Work in Progress</refcontent>
        </reference>
        <reference anchor="RFC3945" target="https://www.rfc-editor.org/info/rfc3945" quoteTitle="true" derivedAnchor="RFC3945">
          <front>
            <title>Generalized Multi-Protocol Label Switching (GMPLS) Architecture</title>
            <author fullname="E. Mannie" initials="E." role="editor" surname="Mannie"/>
            <date month="November" year="2004"/>
            <abstract>
              <t indent="0">Future data and transmission networks will consist of elements such as routers, switches, Dense Wavelength Division Multiplexing (DWDM) systems, Add-Drop Multiplexors (ADMs), photonic cross-connects (PXCs), optical cross-connects (OXCs), etc. that will use Generalized Multi-Protocol Label Switching (GMPLS) to dynamically provision resources and to provide network survivability using protection and restoration techniques.</t>
              <t indent="0">This document describes the architecture of GMPLS. GMPLS extends MPLS to encompass time-division (e.g., SONET/SDH, PDH, G.709), wavelength (lambdas), and spatial switching (e.g., incoming port or fiber to outgoing port or fiber). The focus of GMPLS is on the control plane of these various layers since each of them can use physically diverse data or forwarding planes. The intention is to cover both the signaling and the routing part of that control plane. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3945"/>
          <seriesInfo name="DOI" value="10.17487/RFC3945"/>
        </reference>
        <reference anchor="RFC4427" target="https://www.rfc-editor.org/info/rfc4427" quoteTitle="true" derivedAnchor="RFC4427">
          <front>
            <title>Recovery (Protection and Restoration) Terminology for Generalized Multi-Protocol Label Switching (GMPLS)</title>
            <author fullname="E. Mannie" initials="E." role="editor" surname="Mannie"/>
            <author fullname="D. Papadimitriou" initials="D." role="editor" surname="Papadimitriou"/>
            <date month="March" year="2006"/>
            <abstract>
              <t indent="0">This document defines a common terminology for Generalized Multi-Protocol Label Switching (GMPLS)-based recovery mechanisms (i.e., protection and restoration). The terminology is independent of the underlying transport technologies covered by GMPLS. This memo provides information for the Internet community.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4427"/>
          <seriesInfo name="DOI" value="10.17487/RFC4427"/>
        </reference>
        <reference anchor="RFC4874" target="https://www.rfc-editor.org/info/rfc4874" quoteTitle="true" derivedAnchor="RFC4874">
          <front>
            <title>Exclude Routes - Extension to Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)</title>
            <author fullname="CY. Lee" initials="CY." surname="Lee"/>
            <author fullname="A. Farrel" initials="A." surname="Farrel"/>
            <author fullname="S. De Cnodder" initials="S." surname="De Cnodder"/>
            <date month="April" year="2007"/>
            <abstract>
              <t indent="0">This document specifies ways to communicate route exclusions during path setup using Resource ReserVation Protocol-Traffic Engineering (RSVP-TE).</t>
              <t indent="0">The RSVP-TE specification, "RSVP-TE: Extensions to RSVP for LSP Tunnels" (RFC 3209) and GMPLS extensions to RSVP-TE, "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions" (RFC 3473) allow abstract nodes and resources to be explicitly included in a path setup, but not to be explicitly excluded.</t>
              <t indent="0">In some networks where precise explicit paths are not computed at the head end, it may be useful to specify and signal abstract nodes and resources that are to be explicitly excluded from routes. These exclusions may apply to the whole path, or to parts of a path between two abstract nodes specified in an explicit path. How Shared Risk Link Groups (SRLGs) can be excluded is also specified in this document. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4874"/>
          <seriesInfo name="DOI" value="10.17487/RFC4874"/>
        </reference>
        <reference anchor="RFC4875" target="https://www.rfc-editor.org/info/rfc4875" quoteTitle="true" derivedAnchor="RFC4875">
          <front>
            <title>Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)</title>
            <author fullname="R. Aggarwal" initials="R." role="editor" surname="Aggarwal"/>
            <author fullname="D. Papadimitriou" initials="D." role="editor" surname="Papadimitriou"/>
            <author fullname="S. Yasukawa" initials="S." role="editor" surname="Yasukawa"/>
            <date month="May" year="2007"/>
            <abstract>
              <t indent="0">This document describes extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for the set up of Traffic Engineered (TE) point-to-multipoint (P2MP) Label Switched Paths (LSPs) in Multi- Protocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks. The solution relies on RSVP-TE without requiring a multicast routing protocol in the Service Provider core. Protocol elements and procedures for this solution are described.</t>
              <t indent="0">There can be various applications for P2MP TE LSPs such as IP multicast. Specification of how such applications will use a P2MP TE LSP is outside the scope of this document. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4875"/>
          <seriesInfo name="DOI" value="10.17487/RFC4875"/>
        </reference>
        <reference anchor="RFC6107" target="https://www.rfc-editor.org/info/rfc6107" quoteTitle="true" derivedAnchor="RFC6107">
          <front>
            <title>Procedures for Dynamically Signaled Hierarchical Label Switched Paths</title>
            <author fullname="K. Shiomoto" initials="K." role="editor" surname="Shiomoto"/>
            <author fullname="A. Farrel" initials="A." role="editor" surname="Farrel"/>
            <date month="February" year="2011"/>
            <abstract>
              <t indent="0">Label Switched Paths (LSPs) set up in Multiprotocol Label Switching (MPLS) or Generalized MPLS (GMPLS) networks can be used to form links to carry traffic in those networks or in other (client) networks.</t>
              <t indent="0">Protocol mechanisms already exist to facilitate the establishment of such LSPs and to bundle traffic engineering (TE) links to reduce the load on routing protocols. This document defines extensions to those mechanisms to support identifying the use to which such LSPs are to be put and to enable the TE link endpoints to be assigned addresses or unnumbered identifiers during the signaling process. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6107"/>
          <seriesInfo name="DOI" value="10.17487/RFC6107"/>
        </reference>
        <reference anchor="RFC6241" target="https://www.rfc-editor.org/info/rfc6241" quoteTitle="true" derivedAnchor="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 indent="0">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="RFC6242" target="https://www.rfc-editor.org/info/rfc6242" quoteTitle="true" derivedAnchor="RFC6242">
          <front>
            <title>Using the NETCONF Protocol over Secure Shell (SSH)</title>
            <author fullname="M. Wasserman" initials="M." surname="Wasserman"/>
            <date month="June" year="2011"/>
            <abstract>
              <t indent="0">This document describes a method for invoking and running the Network Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as an SSH subsystem. This document obsoletes RFC 4742. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6242"/>
          <seriesInfo name="DOI" value="10.17487/RFC6242"/>
        </reference>
        <reference anchor="RFC8040" target="https://www.rfc-editor.org/info/rfc8040" quoteTitle="true" derivedAnchor="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 indent="0">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="RFC8402" target="https://www.rfc-editor.org/info/rfc8402" quoteTitle="true" derivedAnchor="RFC8402">
          <front>
            <title>Segment Routing Architecture</title>
            <author fullname="C. Filsfils" initials="C." role="editor" surname="Filsfils"/>
            <author fullname="S. Previdi" initials="S." role="editor" surname="Previdi"/>
            <author fullname="L. Ginsberg" initials="L." surname="Ginsberg"/>
            <author fullname="B. Decraene" initials="B." surname="Decraene"/>
            <author fullname="S. Litkowski" initials="S." surname="Litkowski"/>
            <author fullname="R. Shakir" initials="R." surname="Shakir"/>
            <date month="July" year="2018"/>
            <abstract>
              <t indent="0">Segment Routing (SR) leverages the source routing paradigm. A node steers a packet through an ordered list of instructions, called "segments". A segment can represent any instruction, topological or service based. A segment can have a semantic local to an SR node or global within an SR domain. SR provides a mechanism that allows a flow to be restricted to a specific topological path, while maintaining per-flow state only at the ingress node(s) to the SR domain.</t>
              <t indent="0">SR can be directly applied to the MPLS architecture with no change to the forwarding plane. A segment is encoded as an MPLS label. An ordered list of segments is encoded as a stack of labels. The segment to process is on the top of the stack. Upon completion of a segment, the related label is popped from the stack.</t>
              <t indent="0">SR can be applied to the IPv6 architecture, with a new type of routing header. A segment is encoded as an IPv6 address. An ordered list of segments is encoded as an ordered list of IPv6 addresses in the routing header. The active segment is indicated by the Destination Address (DA) of the packet. The next active segment is indicated by a pointer in the new routing header.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8402"/>
          <seriesInfo name="DOI" value="10.17487/RFC8402"/>
        </reference>
        <reference anchor="RFC9000" target="https://www.rfc-editor.org/info/rfc9000" quoteTitle="true" derivedAnchor="RFC9000">
          <front>
            <title>QUIC: A UDP-Based Multiplexed and Secure Transport</title>
            <author fullname="J. Iyengar" initials="J." role="editor" surname="Iyengar"/>
            <author fullname="M. Thomson" initials="M." role="editor" surname="Thomson"/>
            <date month="May" year="2021"/>
            <abstract>
              <t indent="0">This document defines the core of the QUIC transport protocol. QUIC provides applications with flow-controlled streams for structured communication, low-latency connection establishment, and network path migration. QUIC includes security measures that ensure confidentiality, integrity, and availability in a range of deployment circumstances. Accompanying documents describe the integration of TLS for key negotiation, loss detection, and an exemplary congestion control algorithm.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9000"/>
          <seriesInfo name="DOI" value="10.17487/RFC9000"/>
        </reference>
        <reference anchor="RFC9846" target="https://www.rfc-editor.org/info/rfc9846" quoteTitle="true" derivedAnchor="RFC9846">
          <front>
            <title>The Transport Layer Security (TLS) Protocol Version 1.3</title>
            <author fullname="E. Rescorla" initials="E." surname="Rescorla"/>
            <date month="July" year="2026"/>
            <abstract>
              <t indent="0">This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery.</t>
              <t indent="0">This document obsoletes RFC 8446, which specified TLS 1.3. This document obsoletes RFC 5246 (specifying TLS 1.2) and RFCs 5077, 6961, 7627, and 8422, all of which pertain to TLS 1.2 or earlier, and updates RFCs 5705 and 6066. This document also specifies new requirements for TLS 1.2 implementations.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9846"/>
          <seriesInfo name="DOI" value="10.17487/RFC9846"/>
        </reference>
        <reference anchor="RFC9907" target="https://www.rfc-editor.org/info/rfc9907" quoteTitle="true" derivedAnchor="RFC9907">
          <front>
            <title>Guidelines for Authors and Reviewers of Documents Containing YANG Data Models</title>
            <author fullname="A. Bierman" initials="A." surname="Bierman"/>
            <author fullname="M. Boucadair" initials="M." role="editor" surname="Boucadair"/>
            <author fullname="Q. Wu" initials="Q." surname="Wu"/>
            <date month="March" year="2026"/>
            <abstract>
              <t indent="0">This document provides guidelines for authors and reviewers of specifications containing YANG data models, including IANA-maintained 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.</t>
              <t indent="0">This document obsoletes RFC 8407; it also updates RFC 8126 by providing additional guidelines for writing the IANA considerations for RFCs that specify IANA-maintained YANG modules.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="216"/>
          <seriesInfo name="RFC" value="9907"/>
          <seriesInfo name="DOI" value="10.17487/RFC9907"/>
        </reference>
      </references>
    </references>
    <section anchor="AppendixA" numbered="true" removeInRFC="false" toc="include" pn="section-appendix.a">
      <name slugifiedName="name-data-tree-examples">Data Tree Examples</name>
      <t indent="0" pn="section-appendix.a-1">This section provides examples demonstrating the use of the model with RESTCONF <xref target="RFC8040" format="default" sectionFormat="of" derivedContent="RFC8040"/> and JSON encoding.
The examples are based on a 4-node network topology depicted in <xref target="AppFig-Topo" format="default" sectionFormat="of" derivedContent="Figure 10"/>, where RSVP-TE tunnels can be established.
The loopback addresses for each node, which serve as the TE node IDs, are detailed in <xref target="tab2" format="default" sectionFormat="of" derivedContent="Table 2"/>.</t>
      <table anchor="tab2" align="center" pn="table-2">
        <name slugifiedName="name-loopback-addresses-used-in-">Loopback Addresses Used in the Following Examples</name>
        <thead>
          <tr>
            <th align="left" colspan="1" rowspan="1">Node</th>
            <th align="left" colspan="1" rowspan="1">TE Node ID (IPv4)</th>
            <th align="left" colspan="1" rowspan="1">TE Node ID (IPv6)</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left" colspan="1" rowspan="1">A</td>
            <td align="left" colspan="1" rowspan="1">192.0.2.1</td>
            <td align="left" colspan="1" rowspan="1">2001:db8::1</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">B</td>
            <td align="left" colspan="1" rowspan="1">192.0.2.2</td>
            <td align="left" colspan="1" rowspan="1">2001:db8::2</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">C</td>
            <td align="left" colspan="1" rowspan="1">192.0.2.3</td>
            <td align="left" colspan="1" rowspan="1">2001:db8::3</td>
          </tr>
          <tr>
            <td align="left" colspan="1" rowspan="1">D</td>
            <td align="left" colspan="1" rowspan="1">192.0.2.4</td>
            <td align="left" colspan="1" rowspan="1">2001:db8::4</td>
          </tr>
        </tbody>
      </table>
      <t indent="0" pn="section-appendix.a-3">This network topology forms the foundation for the subsequent examples, which
illustrate the setup and configuration of RSVP-TE tunnels using the model.</t>
      <figure anchor="AppFig-Topo" align="left" suppress-title="false" pn="figure-10">
        <name slugifiedName="name-te-network-used-in-data-tre">TE Network Used in Data Tree Examples</name>
        <artwork align="left" pn="section-appendix.a-4.1">
 2001:db8::1      2001:db8::2    2001:db8::4
 192.0.2.1        192.0.2.2      192.0.2.4
 +-------+        +-------+      +-------+
 |       |        |       |      |       |
 |   A   +--------+   B   +------+   D   |
 +---+---+        +-------+      +---+---+
     |                               |
     |            +-------+          |
     |            |       |          |
     +------------+   C   +----------+
                  |       |
                  +-------+
                  192.0.2.3
                  2001:db8::3</artwork>
      </figure>
      <section anchor="TeTunnel" numbered="true" removeInRFC="false" toc="include" pn="section-appendix.a.1">
        <name slugifiedName="name-basic-tunnel-setup">Basic Tunnel Setup</name>
        <t indent="0" pn="section-appendix.a.1-1">This example uses the TE Tunnel YANG data model defined in this document to create an
RSVP-TE signaled Tunnel of packet LSP encoding type. First, the TE Tunnel is created with no specific restrictions or constraints (e.g., protection or restoration).
The TE Tunnel ingresses on router A and egresses on router D.</t>
        <t indent="0" pn="section-appendix.a.1-2">In this case, the TE Tunnel is created without specifying additional information about the primary paths.</t>
        <sourcecode type="json" markers="false" pn="section-appendix.a.1-3">
POST /restconf/data/ietf-te:te/tunnels HTTP/1.1
    Host: example.com
    Accept: application/yang-data+json
    Content-Type: application/yang-data+json

{
  "ietf-te:tunnel": [
    {
      "name": "Example_LSP_Tunnel_A_2",
      "admin-state": "ietf-te-types:tunnel-admin-state-up",
      "encoding": "ietf-te-types:lsp-encoding-packet",
      "source": {
        "te-node-id": "192.0.2.1"
      },
      "destination": {
        "te-node-id": "192.0.2.4"
      },
      "bidirectional": false,
      "signaling-type": "ietf-te-types:path-setup-rsvp"
    }
  ]
}

{
  "ietf-te:tunnel": [
    {
      "name": "Example_LSP_Tunnel_A_2 (IPv6)",
      "admin-state": "ietf-te-types:tunnel-admin-state-up",
      "encoding": "ietf-te-types:lsp-encoding-packet",
      "source": {
        "te-node-id": "2001:db8::1"
      },
      "destination": {
        "te-node-id": "2001:db8::4"
      },
      "bidirectional": false,
      "signaling-type": "ietf-te-types:path-setup-rsvp"
    }
  ]
}</sourcecode>
      </section>
      <section anchor="global-named-path-constraints" numbered="true" removeInRFC="false" toc="include" pn="section-appendix.a.2">
        <name slugifiedName="name-global-named-path-constrain">Global Named Path Constraints</name>
        <t indent="0" pn="section-appendix.a.2-1">This example uses the YANG data model to create a 'named path constraint' that can be referenced by TE Tunnels.
The path constraint, in this case, limits the TE Tunnel hops for the computed path.</t>
        <sourcecode type="json" markers="false" pn="section-appendix.a.2-2">
POST /restconf/data/ietf-te:te/globals/named-path-constraints
     HTTP/1.1
    Host: example.com
    Accept: application/yang-data+json
    Content-Type: application/yang-data+json

{
  "ietf-te:named-path-constraint": [
    {
      "name": "max-hop-3",
      "path-metric-bounds": {
        "path-metric-bound": [
          {
            "metric-type": "ietf-te-types:path-metric-hop",
            "upper-bound": "3"
          }
        ]
      }
    }
  ]
}</sourcecode>
      </section>
      <section anchor="tunnel-with-global-path-constraint" numbered="true" removeInRFC="false" toc="include" pn="section-appendix.a.3">
        <name slugifiedName="name-tunnel-with-global-path-con">Tunnel with Global Path Constraint</name>
        <t indent="0" pn="section-appendix.a.3-1">In this example, the previously created 'named path constraint' is applied to the TE Tunnel created in <xref target="TeTunnel" format="default" sectionFormat="of" derivedContent="Appendix A.1"/>.</t>
        <sourcecode type="json" markers="false" pn="section-appendix.a.3-2">
POST /restconf/data/ietf-te:te/tunnels HTTP/1.1
    Host: example.com
    Accept: application/yang-data+json
    Content-Type: application/yang-data+json

{
  "ietf-te:tunnel": [
    {
      "name": "Example_LSP_Tunnel_A_4_1",
      "description": "Simple_LSP_with_named_path",
      "admin-state": "ietf-te-types:tunnel-admin-state-up",
      "encoding": "ietf-te-types:lsp-encoding-packet",
      "source": {
        "te-node-id": "192.0.2.1"
      },
      "destination": {
        "te-node-id": "192.0.2.4"
      },
      "signaling-type": "ietf-te-types:path-setup-rsvp",
      "primary-paths": {
        "primary-path": [
          {
            "name": "Simple_LSP_1",
            "use-path-computation": true,
            "path-scope": "ietf-te-types:path-scope-end-to-end",
            "named-path-constraint": "max-hop-3"
          }
        ]
      }
    }
  ]
}</sourcecode>
      </section>
      <section anchor="tunnel-with-per-tunnel-path-constraint" numbered="true" removeInRFC="false" toc="include" pn="section-appendix.a.4">
        <name slugifiedName="name-tunnel-with-per-tunnel-path">Tunnel with Per-Tunnel Path Constraint</name>
        <t indent="0" pn="section-appendix.a.4-1">In this example, the per-tunnel path constraint is explicitly indicated under the TE Tunnel created in <xref target="TeTunnel" format="default" sectionFormat="of" derivedContent="Appendix A.1"/> to constrain the computed path for the tunnel.</t>
        <sourcecode type="json" markers="false" pn="section-appendix.a.4-2">
POST /restconf/data/ietf-te:te/tunnels HTTP/1.1
    Host: example.com
    Accept: application/yang-data+json
    Content-Type: application/yang-data+json

{
  "ietf-te:tunnel": [
    {
      "name": "Example_LSP_Tunnel_A_4_2",
      "admin-state": "ietf-te-types:tunnel-admin-state-up",
      "encoding": "ietf-te-types:lsp-encoding-packet",
      "source": {
        "te-node-id": "192.0.2.1"
      },
      "destination": {
        "te-node-id": "192.0.2.4"
      },
      "bidirectional": false,
      "signaling-type": "ietf-te-types:path-setup-rsvp",
      "primary-paths": {
        "primary-path": [
          {
            "name": "path1",
            "path-scope": "ietf-te-types:path-scope-end-to-end",
            "path-metric-bounds": {
              "path-metric-bound": [
                {
                  "metric-type": "ietf-te-types:path-metric-hop",
                  "upper-bound": "3"
                }
              ]
            }
          }
        ]
      }
    }
  ]
}</sourcecode>
      </section>
      <section anchor="tunnel-state" numbered="true" removeInRFC="false" toc="include" pn="section-appendix.a.5">
        <name slugifiedName="name-tunnel-state">Tunnel State</name>
        <t indent="0" pn="section-appendix.a.5-1">In this example, the 'GET' query is sent to return the state stored about the tunnel.</t>
        <sourcecode type="pseudocode" markers="false" pn="section-appendix.a.5-2">
GET  /restconf/data/ietf-te:te/tunnels +
     /tunnel="Example_LSP_Tunnel_A_4_1"
     /primary-paths/ HTTP/1.1
    Host: example.com
    Accept: application/yang-data+json</sourcecode>
        <t indent="0" pn="section-appendix.a.5-3">The request, with status code 200 would include, for example, the following json:</t>
        <sourcecode type="json" markers="false" pn="section-appendix.a.5-4">
{
  "ietf-te:primary-path": [
    {
      "name": "path1",
      "path-computation-method":
      "ietf-te-types:path-locally-computed",
      "path-scope": "ietf-te-types:path-scope-end-to-end",
      "computed-paths-properties": {
        "computed-path-properties": [
          {
            "k-index": 1,
            "path-properties": {
              "path-route-objects": {
                "path-route-object": [
                  {
                    "index": 1,
                    "numbered-node-hop": {
                      "node-id": "192.0.2.2",
                      "hop-type": "strict"
                    }
                  },
                  {
                    "index": 2,
                    "numbered-node-hop": {
                      "node-id": "192.0.2.4",
                      "hop-type": "strict"
                    }
                  }
                ]
              }
            }
          }
        ]
      },
      "lsps": {
        "lsp": [
          {
            "node": "192.0.2.1",
            "lsp-id": 25356,
            "tunnel-name": "Example_LSP_Tunnel_A_4_1"
          }
        ]
      }
    }
  ]
}</sourcecode>
      </section>
      <section anchor="example-te-tunnel-with-primary-and-secondary-paths" numbered="true" removeInRFC="false" toc="include" pn="section-appendix.a.6">
        <name slugifiedName="name-example-te-tunnel-with-prim">Example TE Tunnel with Primary and Secondary Paths</name>
        <t indent="0" pn="section-appendix.a.6-1">The example in this section uses the network topology depicted in <xref target="AppFig-Topo2" format="default" sectionFormat="of" derivedContent="Figure 11"/>.
The loopback addresses for each node, which serve as the TE node IDs, are detailed in <xref target="tab3" format="default" sectionFormat="of" derivedContent="Table 3"/>.</t>
        <table anchor="tab3" align="center" pn="table-3">
          <name slugifiedName="name-loopback-addresses-used-in-t">Loopback Addresses Used in This Section</name>
          <thead>
            <tr>
              <th align="left" colspan="1" rowspan="1">Node</th>
              <th align="left" colspan="1" rowspan="1">TE Node ID (IPv4)</th>
              <th align="left" colspan="1" rowspan="1">TE Node ID (IPv6)</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left" colspan="1" rowspan="1">A</td>
              <td align="left" colspan="1" rowspan="1">192.0.2.1</td>
              <td align="left" colspan="1" rowspan="1">2001:db8::1</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">B</td>
              <td align="left" colspan="1" rowspan="1">192.0.2.2</td>
              <td align="left" colspan="1" rowspan="1">2001:db8::2</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">C</td>
              <td align="left" colspan="1" rowspan="1">192.0.2.3</td>
              <td align="left" colspan="1" rowspan="1">2001:db8::3</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">D</td>
              <td align="left" colspan="1" rowspan="1">192.0.2.4</td>
              <td align="left" colspan="1" rowspan="1">2001:db8::4</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">E</td>
              <td align="left" colspan="1" rowspan="1">192.0.2.5</td>
              <td align="left" colspan="1" rowspan="1">2001:db8::5</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">F</td>
              <td align="left" colspan="1" rowspan="1">192.0.2.6</td>
              <td align="left" colspan="1" rowspan="1">2001:db8::6</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">G</td>
              <td align="left" colspan="1" rowspan="1">192.0.2.7</td>
              <td align="left" colspan="1" rowspan="1">2001:db8::7</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">H</td>
              <td align="left" colspan="1" rowspan="1">192.0.2.8</td>
              <td align="left" colspan="1" rowspan="1">2001:db8::8</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">I</td>
              <td align="left" colspan="1" rowspan="1">192.0.2.9</td>
              <td align="left" colspan="1" rowspan="1">2001:db8::9</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">J</td>
              <td align="left" colspan="1" rowspan="1">192.0.2.10</td>
              <td align="left" colspan="1" rowspan="1">2001:db8::a</td>
            </tr>
          </tbody>
        </table>
        <figure anchor="AppFig-Topo2" align="left" suppress-title="false" pn="figure-11">
          <name slugifiedName="name-te-network-used-in-data-tree">TE Network Used in Data Tree Examples</name>
          <artwork align="left" pn="section-appendix.a.6-3.1">
                       +----------+          +----------+
                     +-|192.0.2.9 |---+      |192.0.2.10|
                     | +----------+   |      +----------+
                     |                |          |   |
+----------+    +----------+     +----------+    |   |
|192.0.2.8 |----|192.0.2.3 |-----|192.0.2.4 |----+   |
+----------+    +----------+     +----------+        |
  |                  |                |              |
+----------+         |                |              |
|192.0.2.1 |---------+                |           +----------+
+----------+                          +-----------|192.0.2.5 |
      |  |                                        +----------+
      |  |              +----------+                     | |
      |  +--------------|192.0.2.2 |---------------------+ |
      |                 +----------+                       |
      |                       | |                          |
  +----------+                | |                   +----------+
  |192.0.2.6 |----------------+ +-------------------|192.0.2.7 |
  +----------+                                      +----------+</artwork>
        </figure>
        <t indent="0" pn="section-appendix.a.6-4">Below is the state retrieved for a TE tunnel that is set up from ingress node A
(192.0.2.1) to egress node E (192.0.2.5) with primary, secondary, reverse, and
secondary reverse paths as shown in <xref target="AppFig-Topo2" format="default" sectionFormat="of" derivedContent="Figure 11"/>.</t>
        <sourcecode type="json" markers="false" pn="section-appendix.a.6-5">
{
  "ietf-te:te": {
    "tunnels": {
      "tunnel": [
        {
          "name": "example-1",
          "description": "Example in slide 1",
          "source": {
            "te-node-id": "192.0.2.1"
          },
          "destination": {
            "te-node-id": "192.0.2.5"
          },
          "bidirectional": true,
          "primary-paths": {
            "primary-path": [
              {
                "name": "primary-1 (fwd)",
                "path-scope": "ietf-te-types:path-scope-end-to-end",
                "co-routed": false,
                "explicit-route-objects": {
                  "route-object-include-exclude": [
                    {
                      "index": 1,
                      "explicit-route-usage":
                      "ietf-te-types:route-include-object",
                      "numbered-node-hop": {
                        "node-id": "192.0.2.2",
                        "hop-type": "loose"
                      }
                    }
                  ]
                },
                "primary-reverse-path": {
                  "name": "primary-2 (rev)",
                  "path-scope":
                  "ietf-te-types:path-scope-end-to-end",
                  "explicit-route-objects": {
                    "route-object-include-exclude": [
                      {
                        "index": 1,
                        "explicit-route-usage":
                        "ietf-te-types:route-include-object",
                        "numbered-node-hop": {
                          "node-id": "192.0.2.3",
                          "hop-type": "loose"
                        }
                      }
                    ]
                  },
                  "candidate-secondary-reverse-paths": {
                    "candidate-secondary-reverse-path": [
                      {
                        "secondary-reverse-path": "secondary-3 (rev)"
                      },
                      {
                        "secondary-reverse-path": "secondary-4 (rev)"
                      },
                      {
                        "secondary-reverse-path": "secondary-5 (rev)"
                      }
                    ]
                  }
                },
                "candidate-secondary-paths": {
                  "candidate-secondary-path": [
                    {
                      "secondary-path": "secondary-1 (fwd)"
                    },
                    {
                      "secondary-path": "secondary-2 (fwd)"
                    }
                  ]
                }
              }
            ]
          },
          "secondary-paths": {
            "secondary-path": [
              {
                "name": "secondary-1 (fwd)",
                "path-scope": "ietf-te-types:path-scope-end-to-end",
                "explicit-route-objects": {
                  "route-object-include-exclude": [
                    {
                      "index": 1,
                      "explicit-route-usage":
                      "ietf-te-types:route-include-object",
                      "numbered-node-hop": {
                        "node-id": "192.0.2.1"
                      }
                    },
                    {
                      "index": 2,
                      "numbered-node-hop": {
                        "node-id": "192.0.2.2",
                        "hop-type": "loose"
                      }
                    }
                  ]
                }
              },
              {
                "name": "secondary-2 (fwd)",
                "path-scope": "ietf-te-types:path-scope-end-to-end",
                "explicit-route-objects": {
                  "route-object-include-exclude": [
                    {
                      "index": 1,
                      "explicit-route-usage":
                      "ietf-te-types:route-include-object",
                      "numbered-node-hop": {
                        "node-id": "192.0.2.2"
                      }
                    },
                    {
                      "index": 2,
                      "numbered-node-hop": {
                        "node-id": "192.0.2.5",
                        "hop-type": "loose"
                      }
                    }
                  ]
                }
              }
            ]
          },
          "secondary-reverse-paths": {
            "secondary-reverse-path": [
              {
                "name": "secondary-3 (rev)",
                "path-scope": "ietf-te-types:path-scope-end-to-end",
                "explicit-route-objects": {
                  "route-object-include-exclude": [
                    {
                      "index": 1,
                      "explicit-route-usage":
                      "ietf-te-types:route-include-object",
                      "numbered-node-hop": {
                        "node-id": "192.0.2.5"
                      }
                    },
                    {
                      "index": 2,
                      "numbered-node-hop": {
                        "node-id": "192.0.2.4",
                        "hop-type": "loose"
                      }
                    }
                  ]
                }
              },
              {
                "name": "secondary-4 (rev)",
                "path-scope": "ietf-te-types:path-scope-end-to-end",
                "explicit-route-objects": {
                  "route-object-include-exclude": [
                    {
                      "index": 1,
                      "explicit-route-usage":
                      "ietf-te-types:route-include-object",
                      "numbered-node-hop": {
                        "node-id": "192.0.2.4"
                      }
                    },
                    {
                      "index": 2,
                      "numbered-node-hop": {
                        "node-id": "192.0.2.3",
                        "hop-type": "loose"
                      }
                    }
                  ]
                }
              },
              {
                "name": "secondary-5 (rev)",
                "path-scope": "ietf-te-types:path-scope-end-to-end",
                "explicit-route-objects": {
                  "route-object-include-exclude": [
                    {
                      "index": 1,
                      "explicit-route-usage":
                      "ietf-te-types:route-include-object",
                      "numbered-node-hop": {
                        "node-id": "192.0.2.3"
                      }
                    },
                    {
                      "index": 2,
                      "numbered-node-hop": {
                        "node-id": "192.0.2.1",
                        "hop-type": "loose"
                      }
                    }
                  ]
                }
              }
            ]
          }
        },
        {
          "name": "example-3",
          "description": "Example in slide 3",
          "source": {
            "te-node-id": "192.0.2.1"
          },
          "destination": {
            "te-node-id": "192.0.2.5"
          },
          "bidirectional": true,
          "primary-paths": {
            "primary-path": [
              {
                "name": "primary-1 (bidir)",
                "path-scope": "ietf-te-types:path-scope-end-to-end",
                "co-routed": true,
                "explicit-route-objects": {
                  "route-object-include-exclude": [
                    {
                      "index": 1,
                      "explicit-route-usage":
                      "ietf-te-types:route-include-object",
                      "numbered-node-hop": {
                        "node-id": "192.0.2.2",
                        "hop-type": "loose"
                      }
                    }
                  ]
                },
                "primary-reverse-path": {
                  "path-scope": "ietf-te-types:path-scope-end-to-end"
                },
                "candidate-secondary-paths": {
                  "candidate-secondary-path": [
                    {
                      "secondary-path": "secondary-1 (bidir)"
                    },
                    {
                      "secondary-path": "secondary-2 (bidir)"
                    }
                  ]
                }
              }
            ]
          },
          "secondary-paths": {
            "secondary-path": [
              {
                "name": "secondary-1 (bidir)",
                "path-scope": "ietf-te-types:path-scope-end-to-end",
                "explicit-route-objects": {
                  "route-object-include-exclude": [
                    {
                      "index": 1,
                      "explicit-route-usage":
                      "ietf-te-types:route-include-object",
                      "numbered-node-hop": {
                        "node-id": "192.0.2.1"
                      }
                    },
                    {
                      "index": 2,
                      "numbered-node-hop": {
                        "node-id": "192.0.2.2",
                        "hop-type": "loose"
                      }
                    }
                  ]
                }
              },
              {
                "name": "secondary-2 (bidir)",
                "path-scope": "ietf-te-types:path-scope-end-to-end",
                "explicit-route-objects": {
                  "route-object-include-exclude": [
                    {
                      "index": 1,
                      "explicit-route-usage":
                      "ietf-te-types:route-include-object",
                      "numbered-node-hop": {
                        "node-id": "192.0.2.2"
                      }
                    },
                    {
                      "index": 2,
                      "numbered-node-hop": {
                        "node-id": "192.0.2.5",
                        "hop-type": "loose"
                      }
                    }
                  ]
                }
              }
            ]
          }
        },
        {
          "name": "example-4",
          "description": "Example in slide 4",
          "source": {
            "te-node-id": "192.0.2.1"
          },
          "destination": {
            "te-node-id": "192.0.2.5"
          },
          "bidirectional": true,
          "primary-paths": {
            "primary-path": [
              {
                "name": "primary-1 (fwd)",
                "path-scope": "ietf-te-types:path-scope-end-to-end",
                "co-routed": true,
                "explicit-route-objects": {
                  "route-object-include-exclude": [
                    {
                      "index": 1,
                      "explicit-route-usage":
                      "ietf-te-types:route-include-object",
                      "numbered-node-hop": {
                        "node-id": "192.0.2.2",
                        "hop-type": "loose"
                      }
                    }
                  ]
                },
                "primary-reverse-path": {
                  "name": "primary-2 (rev)",
                  "path-scope":
                  "ietf-te-types:path-scope-end-to-end",
                  "candidate-secondary-reverse-paths": {
                    "candidate-secondary-reverse-path": [
                      {
                        "secondary-reverse-path": "secondary-3 (rev)"
                      },
                      {
                        "secondary-reverse-path": "secondary-4 (rev)"
                      }
                    ]
                  }
                },
                "candidate-secondary-paths": {
                  "candidate-secondary-path": [
                    {
                      "secondary-path": "secondary-1 (fwd)"
                    },
                    {
                      "secondary-path": "secondary-2 (fwd)"
                    }
                  ]
                }
              }
            ]
          },
          "secondary-paths": {
            "secondary-path": [
              {
                "name": "secondary-1 (fwd)",
                "path-scope": "ietf-te-types:path-scope-end-to-end",
                "explicit-route-objects": {
                  "route-object-include-exclude": [
                    {
                      "index": 1,
                      "explicit-route-usage":
                      "ietf-te-types:route-include-object",
                      "numbered-node-hop": {
                        "node-id": "192.0.2.1"
                      }
                    },
                    {
                      "index": 2,
                      "numbered-node-hop": {
                        "node-id": "192.0.2.2",
                        "hop-type": "loose"
                      }
                    }
                  ]
                }
              },
              {
                "name": "secondary-2 (fwd)",
                "path-scope": "ietf-te-types:path-scope-end-to-end",
                "explicit-route-objects": {
                  "route-object-include-exclude": [
                    {
                      "index": 1,
                      "explicit-route-usage":
                      "ietf-te-types:route-include-object",
                      "numbered-node-hop": {
                        "node-id": "192.0.2.2"
                      }
                    },
                    {
                      "index": 2,
                      "numbered-node-hop": {
                        "node-id": "192.0.2.5",
                        "hop-type": "loose"
                      }
                    }
                  ]
                }
              }
            ]
          },
          "secondary-reverse-paths": {
            "secondary-reverse-path": [
              {
                "name": "secondary-3 (rev)",
                "path-scope": "ietf-te-types:path-scope-end-to-end"
              },
              {
                "name": "secondary-4 (rev)",
                "path-scope": "ietf-te-types:path-scope-end-to-end"
              }
            ]
          }
        }
      ]
    }
  }
}</sourcecode>
      </section>
      <section anchor="example-multi-domain-te-tunnel-with-primary-and-secondary-paths" numbered="true" removeInRFC="false" toc="include" pn="section-appendix.a.7">
        <name slugifiedName="name-example-multi-domain-te-tun">Example Multi-Domain TE Tunnel with Primary and Secondary Paths</name>
        <figure anchor="AppFig-Topo3" align="left" suppress-title="false" pn="figure-12">
          <name slugifiedName="name-te-network-used-in-the-mult">TE Network Used in the Multi-Domain TE Tunnel Example</name>
          <artwork align="left" pn="section-appendix.a.7-1.1">
                            XXXXXXX
                         XXX       XXX
                       XX             XX
                     X                  X
                     X    Domain 2      X
            XXXXXXX   X                X    XXXXXXXX
         XXX    +-----------+    +-----------+      XXX
       XX       | 192.0.2.1 |    | 192.0.2.2 |         XX
      X         +-----------+    +-----------+           X
      X                 X   XXXXXX    X                  X
+-----------+           X             X             +-----------+
|192.0.2.100| Domain 1  X             X   Domain 3  |192.0.2.200|
+-----------+           X   XXXXXX    X             +-----------+
      X         +-----------+    +-----------+           X
      X         | 192.0.2.3 |    | 192.0.2.4 |          X
       XX       +-----------+    +-----------+        XX
         XXX       X  X                  XXX       XXX
            XXXXXXX  X                    X  XXXXXXX
                     X                    X
                     X    Domain 4        X
                       XX             XX
                         XXX       XXX
                            XXXXXXX</artwork>
        </figure>
        <t indent="0" pn="section-appendix.a.7-2">The following state is retrieved for a multi-domain TE tunnel, where both the
primary and secondary paths consist of TE tunnel segments, as shown in <xref target="AppFig-Topo3" format="default" sectionFormat="of" derivedContent="Figure 12"/>.
In each domain, a TE tunnel segment is established to form the complete end-to-end TE path.
The nodes (192.0.2.100) and (192.0.2.200) form the multi-domain end-to-end source and destination
respectively. The nodes (192.0.2.1), (192.0.2.2), (192.0.2.3), and (192.0.2.4) act as domain
border nodes and transit nodes for the end-to-end TE tunnel LSPs.</t>
        <sourcecode type="json" markers="false" pn="section-appendix.a.7-3">
{
  "ietf-te:te": {
    "tunnels": {
      "tunnel": [
        {
          "name": "Example_Head_End_Tunnel_Segment",
          "admin-state": "ietf-te-types:tunnel-admin-state-up",
          "encoding": "ietf-te-types:lsp-encoding-packet",
          "source": {
            "te-node-id": "192.0.2.100"
          },
          "bidirectional": true,
          "signaling-type": "ietf-te-types:path-setup-rsvp",
          "primary-paths": {
            "primary-path": [
              {
                "name": "primary-path-1",
                "path-scope": "ietf-te-types:path-scope-end-to-end",
                "co-routed": true,
                "explicit-route-objects": {
                  "route-object-include-exclude": [
                    {
                      "index": 1,
                      "explicit-route-usage":
                      "ietf-te-types:route-include-object",
                      "numbered-link-hop": {
                        "link-tp-id": "192.0.2.1"
                      }
                    }
                  ]
                },
                "primary-reverse-path": {
                  "path-scope": "ietf-te-types:path-scope-end-to-end"
                },
                "candidate-secondary-paths": {
                  "candidate-secondary-path": [
                    {
                      "secondary-path": "secondary-path-1"
                    }
                  ]
                }
              }
            ]
          },
          "secondary-paths": {
            "secondary-path": [
              {
                "name": "secondary-path-1",
                "path-scope": "ietf-te-types:path-scope-end-to-end",
                "explicit-route-objects": {
                  "route-object-include-exclude": [
                    {
                      "index": 1,
                      "explicit-route-usage":
                      "ietf-te-types:route-include-object",
                      "numbered-link-hop": {
                        "link-tp-id": "192.0.2.3"
                      }
                    }
                  ]
                }
              }
            ]
          }
        },
        {
          "name": "Example_Primary_Transit_Tunnel_Segment",
          "admin-state": "ietf-te-types:tunnel-admin-state-up",
          "encoding": "ietf-te-types:lsp-encoding-packet",
          "bidirectional": true,
          "signaling-type": "ietf-te-types:path-setup-rsvp",
          "primary-paths": {
            "primary-path": [
              {
                "name": "primary-path-2",
                "path-scope": "ietf-te-types:path-scope-end-to-end",
                "co-routed": true,
                "explicit-route-objects": {
                  "route-object-include-exclude": [
                    {
                      "index": 1,
                      "explicit-route-usage":
                      "ietf-te-types:route-include-object",
                      "numbered-link-hop": {
                        "link-tp-id": "192.0.2.1"
                      }
                    },
                    {
                      "index": 2,
                      "explicit-route-usage":
                      "ietf-te-types:route-include-object",
                      "numbered-link-hop": {
                        "link-tp-id": "192.0.2.2"
                      }
                    }
                  ]
                },
                "primary-reverse-path": {
                  "path-scope": "ietf-te-types:path-scope-end-to-end"
                }
              }
            ]
          }
        },
        {
          "name": "Example_Secondary_Transit_Tunnel_Segment",
          "admin-state": "ietf-te-types:tunnel-admin-state-up",
          "encoding": "ietf-te-types:lsp-encoding-packet",
          "bidirectional": true,
          "signaling-type": "ietf-te-types:path-setup-rsvp",
          "primary-paths": {
            "primary-path": [
              {
                "name": "primary-path-4",
                "path-scope": "ietf-te-types:path-scope-end-to-end",
                "co-routed": true,
                "primary-reverse-path": {
                  "path-scope": "ietf-te-types:path-scope-end-to-end"
                },
                "candidate-secondary-paths": {
                  "candidate-secondary-path": [
                    {
                      "secondary-path": "secondary-path-4"
                    }
                  ]
                }
              }
            ]
          },
          "secondary-paths": {
            "secondary-path": [
              {
                "name": "secondary-path-4",
                "path-scope": "ietf-te-types:path-scope-end-to-end",
                "explicit-route-objects": {
                  "route-object-include-exclude": [
                    {
                      "index": 1,
                      "explicit-route-usage":
                      "ietf-te-types:route-include-object",
                      "numbered-link-hop": {
                        "link-tp-id": "192.0.2.3"
                      }
                    },
                    {
                      "index": 2,
                      "explicit-route-usage":
                      "ietf-te-types:route-include-object",
                      "numbered-link-hop": {
                        "link-tp-id": "192.0.2.4"
                      }
                    }
                  ]
                }
              }
            ]
          }
        },
        {
          "name": "Example_Tail_End_Tunnel_Segment",
          "admin-state": "ietf-te-types:tunnel-admin-state-up",
          "encoding": "ietf-te-types:lsp-encoding-packet",
          "destination": {
            "te-node-id": "192.0.2.200"
          },
          "bidirectional": true,
          "signaling-type": "ietf-te-types:path-setup-rsvp",
          "primary-paths": {
            "primary-path": [
              {
                "name": "primary-path-3",
                "path-scope": "ietf-te-types:path-scope-end-to-end",
                "co-routed": true,
                "explicit-route-objects": {
                  "route-object-include-exclude": [
                    {
                      "index": 1,
                      "explicit-route-usage":
                      "ietf-te-types:route-include-object",
                      "numbered-link-hop": {
                        "link-tp-id": "192.0.2.2"
                      }
                    }
                  ]
                },
                "primary-reverse-path": {
                  "path-scope": "ietf-te-types:path-scope-end-to-end"
                },
                "candidate-secondary-paths": {
                  "candidate-secondary-path": [
                    {
                      "secondary-path": "secondary-path-3"
                    }
                  ]
                }
              }
            ]
          },
          "secondary-paths": {
            "secondary-path": [
              {
                "name": "secondary-path-3",
                "path-scope": "ietf-te-types:path-scope-end-to-end",
                "explicit-route-objects": {
                  "route-object-include-exclude": [
                    {
                      "index": 1,
                      "explicit-route-usage":
                      "ietf-te-types:route-include-object",
                      "numbered-link-hop": {
                        "link-tp-id": "192.0.2.4"
                      }
                    }
                  ]
                }
              }
            ]
          }
        }
      ]
    }
  }
}</sourcecode>
      </section>
    </section>
    <section anchor="AppendixB" numbered="true" removeInRFC="false" toc="include" pn="section-appendix.b">
      <name slugifiedName="name-full-model-tree-diagram">Full Model Tree Diagram</name>
      <t indent="0" pn="section-appendix.b-1">The full tree diagram of the TE YANG data model defined in module "ietf-te" is shown below.</t>
      <sourcecode type="yangtree" markers="false" pn="section-appendix.b-2">
module: ietf-te
  +--rw te
     +--rw enable?    boolean
     +--rw globals
     |  +--rw named-admin-groups
     |  |  +--rw named-admin-group* [name]
     |  |          {te-types:extended-admin-groups,
     |  |           te-types:named-extended-admin-groups}?
     |  |     +--rw name            string
     |  |     +--rw bit-position?   uint32
     |  +--rw named-srlgs
     |  |  +--rw named-srlg* [name] {te-types:named-srlg-groups}?
     |  |     +--rw name     string
     |  |     +--rw value?   te-types:srlg
     |  |     +--rw cost?    uint32
     |  +--rw named-path-constraints
     |     +--rw named-path-constraint* [name]
     |             {te-types:named-path-constraints}?
     |        +--rw name                       string
     |        +---u path-constraints-common
     +--rw tunnels
     |  +--rw tunnel* [name]
     |     +--rw name                                    string
     |     +--rw alias?                                  string
     |     +--rw identifier?                             uint32
     |     +--rw color?                                  uint32
     |     +--rw description?                            string
     |     +--rw admin-state?                            identityref
     |     +--ro operational-state?                      identityref
     |     +--rw state-change-timestamp?
     |     |       yang:date-and-time
     |     +---u te-types:encoding-and-switching-type
     |     +---u tunnel-common-attributes
     |     +--rw controller
     |     |  +--rw protocol-origin?        identityref
     |     |  +--rw controller-entity-id?   string
     |     +--rw reoptimize-timer?                       uint16
     |     +---u tunnel-associations-properties
     |     +---u protection-restoration-properties
     |     +---u te-types:tunnel-constraints
     |     +---u tunnel-hierarchy-properties
     |     +--rw primary-paths
     |     |  +--rw primary-path* [name]
     |     |     +--ro active?                      boolean
     |     |     +---u path-common-properties
     |     |     +---u path-forward-properties
     |     |     +---u k-requested-paths
     |     |     +---u path-compute-info
     |     |     +---u path-state
     |     |     +--rw primary-reverse-path
     |     |     |  +---u path-common-properties
     |     |     |  +---u path-compute-info
     |     |     |  +---u path-state
     |     |     |  +--rw candidate-secondary-reverse-paths
     |     |     |     +--rw candidate-secondary-reverse-path*
     |     |     |             [secondary-reverse-path]
     |     |     |        +--rw secondary-reverse-path    leafref
     |     |     |        +--ro active?                   boolean
     |     |     +--rw candidate-secondary-paths
     |     |        +--rw candidate-secondary-path* [secondary-path]
     |     |           +--rw secondary-path    leafref
     |     |           +--ro active?           boolean
     |     +--rw secondary-paths
     |     |  +--rw secondary-path* [name]
     |     |     +---u path-common-properties
     |     |     +--rw preference?                          uint8
     |     |     +--rw secondary-reverse-path?              leafref
     |     |     +---u path-compute-info
     |     |     +---u protection-restoration-properties
     |     |     +---u path-state
     |     +--rw secondary-reverse-paths
     |     |  +--rw secondary-reverse-path* [name]
     |     |     +---u path-common-properties
     |     |     +--rw preference?                          uint8
     |     |     +---u path-compute-info
     |     |     +---u protection-restoration-properties
     |     |     +---u path-state
     |     +---x tunnel-action
     |     |  +---w input
     |     |  |  +---w action-type?   identityref
     |     |  +--ro output
     |     |     +--ro action-result?   identityref
     |     +---x protection-external-commands
     |        +---w input
     |           +---w protection-external-command?   identityref
     |           +---w ingress-node?                  boolean
     |           +---w egress-node?                   boolean
     |           +---w path-name?                     string
     |           +---w path-type?
     |           |       te-types:path-type
     |           +---w traffic-type?                  enumeration
     |           +---w extra-traffic-tunnel-ref?      tunnel-ref
     +--ro lsps
        +--ro lsp* [tunnel-name lsp-id node]
           +--ro tunnel-name                     string
           +--ro lsp-id                          uint16
           +--ro node                            te-types:te-node-id
           +--ro source?                         te-types:te-node-id
           +--ro destination?                    te-types:te-node-id
           +--ro tunnel-id?                      uint16
           +--ro extended-tunnel-id?             yang:dotted-quad
           +--ro operational-state?              identityref
           +--ro signaling-type?                 identityref
           +--ro origin-type?                    enumeration
           +--ro lsp-resource-status?            enumeration
           +--ro lockout-of-normal?              boolean
           +--ro freeze?                         boolean
           +--ro lsp-protection-role?            enumeration
           +--ro lsp-protection-state?           identityref
           +--ro ingress-node-id?                te-types:te-node-id
           +--ro egress-node-id?                 te-types:te-node-id
           +--ro lsp-actual-route-information
              +--ro lsp-actual-route-information* [index]
                 +---u te-types:record-route-state

  rpcs:
    +---x tunnels-path-compute
    |  +---w input
    |  |  +---w path-compute-info
    |  +--ro output
    |     +--ro path-compute-result
    +---x tunnels-actions
       +---w input
       |  +---w tunnel-info
       |  |  +---w (filter-type)
       |  |     +--:(all-tunnels)
       |  |     |  +---w all       empty
       |  |     +--:(one-tunnel)
       |  |        +---w tunnel?   tunnel-ref
       |  +---w action-info
       |     +---w action?       identityref
       |     +---w disruptive?   empty
       +--ro output
          +--ro action-result?   identityref

  grouping path-common-properties:
    +-- name?                      string
    +-- path-computation-method?   identityref
    +-- path-computation-server
    |  +---u te-types:te-generic-node-id
    +-- compute-only?              empty
    +-- use-path-computation?      boolean
    +-- lockdown?                  empty
    +--ro path-scope?                identityref
  grouping path-compute-info:
    +---u tunnel-associations-properties
    +---u te-types:generic-path-optimization
    +-- named-path-constraint?                leafref
    |       {te-types:named-path-constraints}?
    +---u path-constraints-common
  grouping path-forward-properties:
    +-- preference?   uint8
    +-- co-routed?    boolean
  grouping k-requested-paths:
    +-- k-requested-paths?   uint8
  grouping path-state:
    +---u path-computation-response
    +--ro lsp-provisioning-error-infos
    |  +--ro lsp-provisioning-error-info* []
    |     +--ro error-reason?        identityref
    |     +--ro error-description?   string
    |     +--ro error-timestamp?     yang:date-and-time
    |     +--ro error-node-id?       te-types:te-node-id
    |     +--ro error-link-id?       te-types:te-tp-id
    |     +--ro lsp-id?              uint16
    +--ro lsps
       +--ro lsp* [node lsp-id]
          +--ro tunnel-name?              -&gt; /te/lsps/lsp/tunnel-name
          +--ro node?                     leafref
          +--ro lsp-id?                   leafref
          +--ro state-change-timestamp?   yang:date-and-time
  grouping path-computation-response:
    +--ro computed-paths-properties
    |  +--ro computed-path-properties* [k-index]
    |     +--ro k-index?                            uint8
    |     +---u te-types:generic-path-properties
    +--ro computed-path-error-infos
       +--ro computed-path-error-info* []
          +--ro error-description?   string
          +--ro error-timestamp?     yang:date-and-time
          +--ro error-reason?        identityref
  grouping protection-restoration-properties:
    +-- protection
    |  +-- protection-type?                identityref
    |  +-- protection-reversion-disable?   boolean
    |  +-- hold-off-time?                  uint32
    |  +-- wait-to-revert?                 uint16
    |  +-- aps-signal-id?                  uint8
    +-- restoration
       +-- restoration-type?                identityref
       +-- restoration-scheme?              identityref
       +-- restoration-reversion-disable?   boolean
       +-- hold-off-time?                   uint32
       +-- wait-to-restore?                 uint16
       +-- wait-to-revert?                  uint16
  grouping tunnel-associations-properties:
    +-- association-objects
       +-- association-object* [association-key]
       |  +-- association-key?   string
       |  +-- type?              identityref
       |  +-- id?                uint16
       |  +-- source
       |     +---u te-types:te-generic-node-id
       +-- association-object-extended* [association-key]
          +-- association-key?   string
          +-- type?              identityref
          +-- id?                uint16
          +-- source
          |  +---u te-types:te-generic-node-id
          +-- global-source?     uint32
          +-- extended-id?       yang:hex-string
  grouping tunnel-end-point:
    +-- node-id?        nw:node-id
    +-- te-node-id?     te-types:te-node-id
    +-- tunnel-tp-id?   binary
  grouping tunnel-common-attributes:
    +-- source
    |  +---u tunnel-end-point
    +-- destination
    |  +---u tunnel-end-point
    +-- bidirectional?   boolean
  grouping tunnel-hierarchy-properties:
    +-- hierarchy
       +-- dependency-tunnels
       |  +-- dependency-tunnel* [name]
       |     +-- name?                                   tunnel-ref
       |     +---u te-types:encoding-and-switching-type
       +-- hierarchical-link
          +-- enable?                            boolean
          +-- local-node-id?                     nw:node-id
          +-- local-te-node-id?                  te-types:te-node-id
          +-- local-link-tp-id?                  nt:tp-id
          +-- local-te-link-tp-id?               te-types:te-tp-id
          +-- remote-node-id?                    nw:node-id
          +-- remote-link-tp-id?                 nt:tp-id
          +-- remote-te-link-tp-id?              te-types:te-tp-id
          +-- remote-te-node-id?                 te-types:te-node-id
          +--ro link-id?                           nt:link-id
          +-- network-id?                        nw:network-id
          +---u te-types:te-topology-identifier
  grouping path-constraints-common:
    +---u te-types:common-path-constraints-attributes
    +---u te-types:generic-path-disjointness
    +---u te-types:path-constraints-route-objects
    +-- path-in-segment!
    |  +---u te-types:label-set-info
    +-- path-out-segment!
       +---u te-types:label-set-info</sourcecode>
    </section>
    <section anchor="acknowledgement" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.c">
      <name slugifiedName="name-acknowledgements">Acknowledgements</name>
      <t indent="0" pn="section-appendix.c-1">The authors would like to thank the  members of the multivendor YANG design team who are involved in the definition of this model.</t>
      <t indent="0" pn="section-appendix.c-2">The authors would like to thank <contact fullname="Tom Petch"/> and <contact fullname="Adrian Farrel"/> for reviewing and providing useful feedback about the document. The authors would also like to thank <contact fullname="Loa Andersson"/>, <contact fullname="Lou Berger"/>, <contact fullname="Sergio Belotti"/>, <contact fullname="Italo Busi"/>, <contact fullname="Carlo Perocchio"/>, <contact fullname="Francesco Lazzeri"/>, <contact fullname="Aihua Guo"/>, <contact fullname="Dhruv Dhody"/>, and <contact fullname="Raqib Jones"/> for providing feedback on this document.</t>
    </section>
    <section anchor="contributors" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.d">
      <name slugifiedName="name-contributors">Contributors</name>
      <contact fullname="Oscar Gonzalez de Dios">
        <organization showOnFrontPage="true">Telefonica</organization>
        <address>
          <email>oscar.gonzalezdedios@telefonica.com</email>
        </address>
      </contact>
      <contact fullname="Himanshu Shah">
        <organization showOnFrontPage="true">Ciena</organization>
        <address>
          <email>hshah@ciena.com</email>
        </address>
      </contact>
      <contact fullname="Xia Chen">
        <organization showOnFrontPage="true">Huawei Technologies</organization>
        <address>
          <email>jescia.chenxia@huawei.com</email>
        </address>
      </contact>
      <contact fullname="Bin Wen">
        <organization showOnFrontPage="true">Comcast</organization>
        <address>
          <email>Bin_Wen@cable.comcast.com</email>
        </address>
      </contact>
    </section>
    <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.e">
      <name slugifiedName="name-authors-addresses">Authors' Addresses</name>
      <author initials="T." surname="Saad" fullname="Tarek Saad">
        <organization showOnFrontPage="true">Cisco Systems Inc</organization>
        <address>
          <email>tsaad.net@gmail.com</email>
        </address>
      </author>
      <author initials="R." surname="Gandhi" fullname="Rakesh Gandhi">
        <organization showOnFrontPage="true">Cisco Systems Inc</organization>
        <address>
          <email>rgandhi@cisco.com</email>
        </address>
      </author>
      <author initials="X." surname="Liu" fullname="Xufeng Liu">
        <organization showOnFrontPage="true">Individual</organization>
        <address>
          <email>xufeng.liu.ietf@gmail.com</email>
        </address>
      </author>
      <author initials="V. P." surname="Beeram" fullname="Vishnu Pavan Beeram">
        <organization showOnFrontPage="true">Juniper Networks</organization>
        <address>
          <email>vbeeram@juniper.net</email>
        </address>
      </author>
      <author initials="I." surname="Bryskin" fullname="Igor Bryskin">
        <organization showOnFrontPage="true">Individual</organization>
        <address>
          <email>i_bryskin@yahoo.com</email>
        </address>
      </author>
    </section>
  </back>
</rfc>
