<?xml version='1.0' encoding='utf-8'?> <!DOCTYPE rfc SYSTEM"rfc2629.dtd" [ <!ENTITY RFC2119 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"> <!ENTITY RFC3688 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3688.xml"> <!ENTITY RFC3945 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3945.xml"> <!ENTITY RFC6241 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6241.xml"> <!ENTITY RFC6242 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6242.xml"> <!ENTITY RFC6991 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6991.xml"> <!ENTITY RFC7926 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7926.xml"> <!ENTITY RFC7950 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7950.xml"> <!ENTITY RFC8040 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8040.xml"> <!ENTITY RFC8174 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"> <!ENTITY RFC8341 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8341.xml"> <!ENTITY RFC8342 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8342.xml"> <!ENTITY RFC8345 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8345.xml"> <!ENTITY RFC8446 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8446.xml"> <!ENTITY I-D.ietf-teas-yang-te-types SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ietf-teas-yang-te-types-08.xml"> <!ENTITY RFC1195 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.1195.xml"> <!ENTITY RFC2702 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2702.xml"> <!ENTITY RFC3209 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3209.xml"> <!ENTITY RFC3272 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3272.xml"> <!ENTITY RFC3471 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3471.xml"> <!ENTITY RFC3630 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3630.xml"> <!ENTITY RFC3785 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3785.xml"> <!ENTITY RFC4201 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4201.xml"> <!ENTITY RFC4202 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4202.xml"> <!ENTITY RFC4203 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4203.xml"> <!ENTITY RFC4206 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4206.xml"> <!ENTITY RFC4872 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4872.xml"> <!ENTITY RFC5152 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5152.xml"> <!ENTITY RFC5212 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5212.xml"> <!ENTITY RFC5305 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5305.xml"> <!ENTITY RFC5316 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5316.xml"> <!ENTITY RFC5329 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5329.xml"> <!ENTITY RFC5392 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5392.xml"> <!ENTITY RFC6001 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6001.xml"> <!ENTITY RFC7308 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7308.xml"> <!ENTITY RFC7471 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7471.xml"> <!ENTITY RFC7579 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7579.xml"> <!ENTITY RFC7752 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7752.xml"> <!ENTITY RFC8340 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8340.xml"> <!ENTITY I-D.ietf-netconf-subscribed-notifications SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ietf-netconf-subscribed-notifications-23.xml"> <!ENTITY I-D.ietf-netconf-yang-push SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ietf-netconf-yang-push-22.xml"> <!ENTITY I-D.liu-netmod-yang-schedule SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-liu-netmod-yang-schedule-05.xml"> <!ENTITY I-D.ietf-ccamp-wson-yang SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ietf-ccamp-wson-yang-20.xml"> <!ENTITY I-D.ietf-ccamp-otn-topo-yang SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ietf-ccamp-otn-topo-yang-06.xml"> <!ENTITY I-D.ietf-teas-yang-l3-te-topo SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ietf-teas-yang-l3-te-topo-04.xml"> <!ENTITY I-D.ietf-teas-te-topo-and-tunnel-modeling SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ietf-teas-te-topo-and-tunnel-modeling-03.xml"> ]>"rfc2629-xhtml.ent"> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" submissionType="IETF" consensus="true" docName="draft-ietf-teas-yang-te-topo-22" number="8795" category="std"ipr="trust200902">ipr="trust200902" obsoletes="" updates="" xml:lang="en" sortRefs="true" symRefs="true" tocInclude="true" version="3"> <!-- xml2rfc v2v3 conversion 2.38.1 --> <!-- Generated by id2xml 1.5.0 on 2019-12-18T20:08:29Z --><?rfc compact="yes"?> <?rfc text-list-symbols="-o*+"?> <?rfc subcompact="no"?> <?rfc sortrefs="yes"?> <?rfc symrefs="yes"?> <?rfc strict="yes"?> <?rfc toc="yes"?><front> <title abbrev="YANG - TETopology">YANGTopologies">YANG Data Model for Traffic Engineering (TE) Topologies</title> <seriesInfo name="RFC" value="8795"/> <author fullname="Xufeng Liu" initials="X." surname="Liu"> <organization>Volta Networks</organization><address><email>xufeng.liu.ietf@gmail.com</email><address> <email>xufeng.liu.ietf@gmail.com</email> </address> </author> <author fullname="Igor Bryskin" initials="I." surname="Bryskin"><organization>Huawei Technologies</organization> <address><email>Igor.Bryskin@huawei.com</email><organization>Futurewei Technologies, Inc.</organization> <address> <email>i_bryskin@yahoo.com</email> </address> </author> <author fullname="Vishnu Pavan Beeram" initials="V." surname="Beeram"> <organization>Juniper Networks</organization><address><email>vbeeram@juniper.net</email><address> <email>vbeeram@juniper.net</email> </address> </author> <author fullname="Tarek Saad" initials="T." surname="Saad"> <organization>Juniper Networks</organization><address><email>tsaad@juniper.net</email><address> <email>tsaad@juniper.net</email> </address> </author> <author fullname="Himanshu Shah" initials="H." surname="Shah"> <organization>Ciena</organization><address><email>hshah@ciena.com</email><address> <email>hshah@ciena.com</email> </address> </author> <author fullname="Oscar GonzalezDede Dios" initials="O." surname="GonzalezDede Dios"> <organization>Telefonica</organization><address><email>oscar.gonzalezdedios@telefonica.com</email><address> <email>oscar.gonzalezdedios@telefonica.com</email> </address> </author> <datemonth="January"month="July" year="2020"/> <workgroup>TEAS Working Group</workgroup><!-- [rfced] Please insert any keywords (beyond those that appear inthe title) for use on https://www.rfc-editor.org/search. --> <keyword>example</keyword> <abstract><t><keyword>TE topology</keyword> <keyword>TE topology YANG model</keyword> <keyword>Abstract TE topology</keyword> <keyword>Native TE topology</keyword> <keyword>Customized TE topology</keyword> <keyword>Underlay TE topology</keyword> <keyword>Overlay TE topology</keyword> <abstract> <t> This document defines a YANG data model for representing,retrievingretrieving, and manipulating Traffic Engineering (TE) Topologies. The model serves as a base model that othertechnology specifictechnology-specific TETopologytopology models can augment.</t> </abstract> </front> <middle> <sectiontitle="Introduction" anchor="sect-1"><t>anchor="sect-1" numbered="true" toc="default"> <name>Introduction</name> <t> The Traffic Engineering Database (TED) is an essential component of Traffic Engineered (TE) systems that are based on MPLS-TE <xreftarget="RFC2702"/>target="RFC2702" format="default"/> and GMPLS <xreftarget="RFC3945"/>.target="RFC3945" format="default"/>. The TED is a collection of all TE information about all TE nodes and TE links in the network. The TETopologytopology is a schematic arrangement of TE nodes and TE links present in a given TED. There could be one or more TETopologiestopologies present in a givenTraffic EngineeredTE system. A TETopologytopology is the topology on which path computational algorithms are run to computeTraffic Engineered Paths (TE Paths).</t>TE paths.</t> <t> This document defines a YANG<xref target="RFC7950"/>data model <xref target="RFC7950" format="default"/> forrepresentingrepresenting, retrieving, and manipulating TETopologies.topologies. This model containstechnology agnostictechnology-agnostic TETopologytopology building blocks that can be augmented and used by other technology-specific TETopologytopology models.</t> <sectiontitle="Terminology" anchor="sect-1.1"><t> Theanchor="sect-1.1" numbered="true" toc="default"> <name>Terminology</name> <t>The key words"MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY","<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and"OPTIONAL""<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described inBCP 14BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shown here.</t> <t>TheWe assume that the reader isassumed to befamiliar with the general body of work captured in currently availableTERFCs relatedRFCs.to Traffic Engineering. <xreftarget="RFC7926"/>target="RFC7926" format="default"/> serves as a good starting point for those who may be less familiar withTraffic EngineeringRFCs relatedRFCs.</t>to Traffic Engineering.</t> <t> Some of the key terms used in this documentare: <list style="hanging" hangIndent="3"> <t hangText="TED:">Theare as follows: </t> <dl newline="false" spacing="normal" indent="3"> <dt>TED:</dt> <dd>The Traffic Engineering Database (TED) is a collection of all TE information about all TE nodes and TE links in a givennetwork.</t> <t hangText="TE-Topology:">Thenetwork.</dd> <dt>TE topology:</dt> <dd>The TETopologytopology is a schematic arrangement of TE nodes and TE links in a given TED. It forms the basis for a graph suitable for TE pathcomputations.</t> <t hangText="Nativecomputations.</dd> <dt>Native TETopology:">topology:</dt> <dd>A Native TETopologytopology is a topology that is native to a given provider network. A Native TE topology could be discovered via various routing protocols and/or subscribe/publish techniques. This is the topology on which path computational algorithms are run to compute TEPaths.</t> <t hangText="Customizedpaths.</dd> <dt>Customized TETopology:">topology:</dt> <dd>A Customized TETopologytopology is a custom topology that is produced by a provider for a given client. This topology typically makes abstractions on the provider's Native TETopology,topology and is provided to the client. The client receives the Customized TETopology,topology and merges it into the client's Native TETopology.topology. The client's path computational algorithms aren't typically run on the Customized TETopology;topology; they are run on the client's Native TETopologytopology after themerge.</t> </list> </t>merge.</dd> </dl> </section> <sectiontitle="Tree Structure" anchor="sect-1.2"><t>anchor="sect-1.2" numbered="true" toc="default"> <name>Tree Structure</name> <t> A simplified graphical representation of the data model is presented inAppendix A.<xref target="append-a"/> of this document. The tree format defined in <xreftarget="RFC8340"/>target="RFC8340" format="default"/> is used for the YANG data model tree representation. </t> </section> <sectiontitle="Prefixesanchor="sect-1.3" numbered="true" toc="default"> <name>Prefixes in Data NodeNames" anchor="sect-1.3"><t>InNames</name> <t>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 inTable 1.</t> <texttable title="Prefixes<xref target="tab-prefixes-and-corresponding-yang-modules"/>.</t> <table anchor="tab-prefixes-and-corresponding-yang-modules" align="center"> <name>Prefixes andcorrespondingCorresponding YANGmodules" anchor="tab-prefixes-and-corresponding-yang-modules" style="full"><ttcol> Prefix</ttcol> <ttcol>Modules</name> <thead> <tr> <th align="left"> Prefix</th> <th align="left"> YANGmodule</ttcol> <ttcol> Reference</ttcol> <c>yang</c> <c>ietf-yang-types</c> <c>[RFC6991]</c> <c>inet</c> <c>ietf-inet-types</c> <c>[RFC6991]</c> <c>nw</c> <c>ietf-network</c> <c>[RFC6991]</c> <c>nt</c> <c>ietf-network-topology</c> <c>[RFC8345]</c> <c>te-types</c> <c>ietf-te-types</c> <c>[I-D.ietf-teas-yang-te</c> <c></c> <c></c> <c>-types]</c> </texttable>Module</th> <th align="left"> Reference</th> </tr> </thead> <tbody> <tr> <td align="left">yang</td> <td align="left">ietf-yang-types</td> <td align="left"><xref target="RFC6991"/></td> </tr> <tr> <td align="left">inet</td> <td align="left">ietf-inet-types</td> <td align="left"><xref target="RFC6991"/></td> </tr> <tr> <td align="left">nw</td> <td align="left">ietf-network</td> <td align="left"><xref target="RFC8345"/></td> </tr> <tr> <td align="left">nt</td> <td align="left">ietf-network-topology</td> <td align="left"><xref target="RFC8345"/></td> </tr> <tr> <td align="left">te-types</td> <td align="left">ietf-te-types</td> <td align="left"><xref target="RFC8776"/></td> </tr> </tbody> </table> </section> </section> <sectiontitle="Characterizinganchor="sect-2" numbered="true" toc="default"> <name>Characterizing TETopologies" anchor="sect-2"><t>Topologies</name> <t> The data modelproposeddefined by this document takes the following characteristics of TETopologiestopologies into account:</t><t><list style="symbols"><t>TE Topology<ul spacing="normal"> <li>The TE topology is an abstract control-plane representation of the data-plane topology.HenceHence, attributes specific to thedata-planedata plane must make their way into the corresponding TETopologytopology modeling. The TETopology comprisestopology is comprised of dynamicauto-discoveredautodiscovered data as well as fairly static data associated with data-plane nodes and links. The dynamicdata may change frequently,data, such as unreserved bandwidth available on data-planelinks.links, may change frequently. The staticdata rarely changes,data, such as layer network identification, switching and adaptation capabilities and limitations,fate sharing,fate-sharing, and administrativecolors.colors, rarely changes. It is possible for a single TETopologytopology to encompass TE information at multiple switchinglayers.</t> <t>TE Topologieslayers.</li> <li>TE topologies are protocol independent. Information about topological elements may belearntlearned via link-state protocols, but the topology can exist without being dependent on any particularprotocol.</t> <t>TE Topologyprotocol.</li> <li>The TE topology may not be congruenttowith the routing topology in a given TESystem.system. The routing topology is constructed based on routing adjacencies. There isn't always a one-to-one association between aTE-linkTE link and a routing adjacency. For example, the presence of a TE link between a pair of nodes doesn't necessarily imply the existence of arouting-adjacencyrouting adjacency between these nodes. To learn more, see <xreftarget="I-D.ietf-teas-te-topo-and-tunnel-modeling"/>target="I-D.ietf-teas-te-topo-and-tunnel-modeling" format="default"/> and <xreftarget="I-D.ietf-teas-yang-l3-te-topo"/>.</t> <t>Eachtarget="YANG-L3" format="default"/>.</li> <li>Each TETopologicaltopological element has at least one information source associated with it. In some scenarios, there could be more than one information source associated with any given topologicalelement.</t> <t>TE Topologieselement.</li> <li>TE topologies can be hierarchical. Each node and link of a given TETopologytopology can be associated with a respective underlay topology. This means that each node and link of a given TETopologytopology can be associated with an independent stack of supporting TETopologies.</t> <t>TE Topologiestopologies.</li> <li>TE topologies can be customized. TE topologies of a given network presented by the network provider to its client could be customized onper-client requesta per-client-request basis. This customization could be performed by the provider, byclientthe client, or byprovider/clientprovider&wj;/client negotiation. The relationship between a customized topology and the provider's native topology could be captured as hierarchical(overlay-underlay),(overlay/underlay), but otherwise the two topologies are decoupled from each other. A customized topology is presented to the client, while the provider's native topology is known in its entirety to the provideritself.</t> </list> </t>itself.</li> </ul> </section> <sectiontitle="Modelinganchor="sect-3" numbered="true" toc="default"> <name>Modeling Abstractions andTransformations" anchor="sect-3"><figure title="TE Topology Modeling Abstractions" anchor="fig1"><artwork><![CDATA[ | +---+ __ | | | TE Node \/ TTP o LTP | +---+ | | ----- TE Link | ***** Node Connectivity Matrix, | TTP Local Link Connectivity | @@@@@ TE Tunnel o---------------------------------- Node-1 Node-3 +------------+ +------------+ | TTP-1 | | TTP-1 | |LTP __ | TE-Tunel-1 | __ | |-6 \/@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@\/ | o * * oLTP-1 Node-2 LTP-6o * * o | * * | +------------+ | * * | | * TTP-2* | | | | * TTP-2* | | * __ * |LTP-2 LTP-6| |LTP-1 LTP-5| * __ * | o* \/ *o-----------o************o-----------o* \/ *o |LTP * * | Link-12 | * | Link-23 | * * | |-5 * * | LTP-5| * |LTP-2 | * * | +--o------o--+ o************o +--o------o--+ LTP-4 LTP-3 | * * * | LTP-4 LTP-3 | ** * | +--o------o--+ LTP-4 LTP-3 ]]></artwork> </figure>Transformations</name> <sectiontitle="TE Topology" anchor="sect-3.1"><t>anchor="sect-3.1" numbered="true" toc="default"> <name>TE Topology</name> <t> A TE topology is atraffic engineeringTraffic Engineering representation of one or more layers of network topologies. A TE topology is comprised of TE nodes (TE graph vertices) interconnected via TE links (TE graph edges). A TE topology is mapped to a TE graph.</t> </section> <sectiontitle="TE Node" anchor="sect-3.2"><t>anchor="sect-3.2" numbered="true" toc="default"> <name>TE Node</name> <t> A TE node is an element of a TE topology, presented as a vertex on a TE graph. A TE node represents one or several nodes, or a fraction of a node, which can be a switch or router that is physical or virtual. A TE node belongs to and is fully defined in exactly one TE topology. A TE node is assigned a unique ID within the TE topology scope. TE node attributes include information related to thedata planedata&nbhy;plane aspects of the associated node(s)(e.g.(e.g., connectivity matrix), as well as configuration data (such as the TE node name). A given TE node can be reached on the TE graph over one of the TE links terminated by the TE node.</t> <t> Multi-layer TE nodes providing switching functions at multiple network layers are an example where a physical node can be decomposed into multiple logical TE nodes, which are fractions of the physical node. Some of these (logical) TE nodes may reside in theclient layerclient-layer TEtopologytopology, while the remaining TE nodes belong to theserver layerserver-layer TE topology.</t> <t> In <xreftarget="fig1"/>,target="fig1" format="default"/>, Node-1, Node-2, and Node-3 are TE nodes.</t> <figure anchor="fig1"> <name>TE Topology Modeling Abstractions</name> <artwork name="" type="" align="left" alt=""><![CDATA[ | +---+ __ | | | TE Node \/ TTP o LTP | +---+ | | ----- TE Link | ***** Node Connectivity Matrix, | TTP Local Link Connectivity | @@@@@ TE Tunnel o---------------------------------- Node-1 Node-3 +------------+ +------------+ | TTP-1 | | TTP-1 | |LTP __ | TE-Tunnel-1 | __ | |-6 \/@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@\/ | o * * oLTP-1 Node-2 LTP-6o * * o | * * | +------------+ | * * | | * TTP-2* | | | | * TTP-2* | | * __ * |LTP-2 LTP-6| |LTP-1 LTP-5| * __ * | o* \/ *o-----------o************o-----------o* \/ *o |LTP * * | Link-12 | * | Link-23 | * * | |-5 * * | LTP-5| * |LTP-2 | * * | +--o------o--+ o************o +--o------o--+ LTP-4 LTP-3 | * * * | LTP-4 LTP-3 | ** * | +--o------o--+ LTP-4 LTP-3 LTP: Link Termination Point TTP: Tunnel Termination Point]]></artwork> </figure> </section> <sectiontitle="TE Link" anchor="sect-3.3"><t>anchor="sect-3.3" numbered="true" toc="default"> <name>TE Link</name> <t> A TE link is an element of a TE topology, presented as an edge on a TE graph. The arrows on an edge indicate one or both directions of the TE link. When there are a pair of parallel links of opposite directions, an edge without arrows is also used. A TE link represents one or several (physical) links or a fraction of a link. A TE link belongs to and is fully defined in exactly one TE topology. A TE link is assigned a unique ID within the TE topology scope. TE link attributes include parameters related to thedata planedata-plane aspects of the associated link(s)(e.g. unreserved(unreserved bandwidth, resourcemaps/pools,maps / resource pools, etc.), as well as the configuration data(such as remote node/link IDs, SRLGs,(remote node IDs / link IDs, Shared Risk Link Groups (SRLGs), administrative colors, etc.). A TE link is connected to a TE node, terminating the TE link via exactly one TElink termination pointLink Termination Point (LTP).</t> <t> In <xreftarget="fig1"/>,target="fig1" format="default"/>, Link-12 and Link-23 are TE links.</t> </section> <sectiontitle="Transitionalanchor="sect-3.4" numbered="true" toc="default"> <name>Transitional TE Link forMulti-Layer Topologies" anchor="sect-3.4"><t>Multi-layer Topologies</name> <t> Networks are typically composed of multiple network layers where one or multiple signals in theclient layerclient-layer network can be multiplexed and encapsulated into aserver layerserver-layer signal <xreftarget="RFC5212"/>target="RFC5212" format="default"/> <xreftarget="G.805"/>.target="G.805" format="default"/>. Theserver layerserver-layer signal can be carried in theserver layerserver-layer network across multiple nodes until theserver layerserver-layer signal is terminated and theclient layerclient-layer signals reappear in the node that terminates theserver layerserver-layer signal. Examples of multi-layer networksare: IPinclude (1) IP over MPLS overEthernet, low orderEthernet and (2) low-order Optical Data Unit-k (ODUk) signals multiplexed into ahigh orderhigh-order ODUl (l>k) carried over an Optical Channel (OCh) signal in anoptical transport networkOptical Transport Network (OTN) as defined in <xreftarget="G.872"/>target="G.872" format="default"/> and <xreftarget="G.709"/>.</t>target="G.709" format="default"/>.</t> <t> TE links as defined in <xreftarget="sect-3.3"/>.target="sect-3.3" format="default"/> can be used to represent links within a network layer. In the case of a multi-layer network, TE nodes and TE links only allow the representation of each network layer as a separate TE topology. Each of thesesingle layersingle-layer TE topologies would be isolated from their client and theirserver layerserver-layer TE topology, if present. The highest network layer and the lowest network layer in the hierarchy only have a single adjacent layer below or above, respectively. Multiplexingof client layerclient-layer signals and encapsulating them into aserver layerserver-layer signalrequiresrequire a function that is provided inside a node (typically realized in hardware). This function is also calledlayer transition.</t>"layer transition".</t> <t> One of the key requirements for path computation is to be able to calculate a path between two endpoints across a multi-layer network based on the TE topology representing this multi-layer network. This means that an additional TE construct is needed that represents potential layer transitions in the multi-layerTE-topologyTE topology that connects theTE-topologiesTE topologies representing each separate network layer. The so-called transitional TE link is such aconstructconstruct, and it represents the layer transition function residing inside a node that is decomposed into multiple logical nodes that are represented as TE nodes(see also(also see <xref target="G.8080" format="default"/> for the definition of a transitional linkdefinition in <xref target="G.8080"/>for theoptical transport network).OTN). Hence, a transitional TE link connects aclient layerclient-layer node with aserver layerserver-layer node. A TE link as defined in3.3.<xref target="sect-3.3"/> has LTPs of exactly the same kind on each linkendend, whereas the transitional TE link hasclient layerclient-layer LTPs on the client side of the transitional linkandand, in mostcasescases, a singleserver layerserver-layer LTP on the server side. It should be noted that transitional links are a helper construct in the multi-layer TE topology and they only exist as long as they are not in use, as they represent potential connectivity. When theserver layerserver-layer trail has been established between theserver layerserver-layer LTP of two transitional links in theserver layerserver-layer network, the resultingclient layerclient-layer link in the data plane will be represented as a normal TE link in theclient layerclient-layer topology. The transitional TE links willre-appearreappear when theserver layerserver-layer trail has been torn down.</t> <figuretitle="Modelinganchor="fig2"> <name>Modeling aMulti-LayerMulti-layer Node(Dual-Layer Example)" anchor="fig2"> <artwork><![CDATA[(Dual-layer Example)</name> <artwork name="" type="" align="left" alt=""><![CDATA[ | | | +---+ --- | | | TE Node \ / Transitional | +---+ | Link | | -----Client LayerClient-Layer Link | =====Server LayerServer-Layer Link | ***** Layer Boundary o----------------------------------+------------------++-------------------+ |+------++-------+ |+------+ -----|Client|------++-------+ -----|Client-|------+ |Client -----|Client|Client- -----|Client-| | |Layer |---+ | | Layer |Layer |-----|Switch|-+-----|Switch |-+ | | | Links -----|Node | |+------++------ + | | | |+------++-------+ | | | | | Client | | | | | | ---_| Layer --- ---***|**********|*|***|***********|*| \ /*|***************************\ /*\ /**** | --- | | Server Transitional | | | Layer \ / | | Layer Links | | | Term. | | | | | | | | | | | |+------++-------+ |+------+ =============|Server|===== Server ====|Server|====+-------+ =============|Server-|===== Server- ====|Server-|==== | |Layer | | Layer |Layer |=============|Switch|==================|Switch |===== Links ====|Node |==== |+------++-------+ |+------+ +------------------++-------+ +-------------------+ Physical Node ViewTE-Topology View ]]></artwork>TE Topology View]]></artwork> </figure> </section> <sectiontitle="TEanchor="sect-3.5" numbered="true" toc="default"> <name>TE Link Termination Point(LTP)" anchor="sect-3.5"><t>(LTP)</name> <t> A TElink termination pointLink Termination Point (LTP) is a conceptual point of connection of a TE node to one of the TE links, terminated by the TE node. Cardinality between an LTP and the associated TE link is 1:0..1.</t> <t> In <xreftarget="fig1"/>,target="fig1" format="default"/>, Node-2 has six LTPs: LTP-1tothrough LTP-6.</t> </section> <sectiontitle="TEanchor="sect-3.6" numbered="true" toc="default"> <name>TE Tunnel Termination Point(TTP)" anchor="sect-3.6"><t>(TTP)</name> <t> A TEtunnel termination pointTunnel Termination Point (TTP) is an element of a TE topology representing one or severalofpotential transport service termination points(i.e.(i.e., service client adaptationpointspoints, such as a WDM/OCh transponder). ("WDM" stands for "Wavelength Division Multiplexing".) A TTP is associated with (hosted by) exactly one TE node. A TTP is assigned a unique ID within the TE node scope. Depending on the TE node's internal constraints, a given TTP hosted by the TE node could be accessed via one,severalseveral, or all TE links terminated by the TE node.</t> <t> In <xreftarget="fig1"/>,target="fig1" format="default"/>, Node-1 has two TTPs: TTP-1 and TTP-2.</t> </section> <sectiontitle="TEanchor="sect-3.7" numbered="true" toc="default"> <name>TE Node ConnectivityMatrix" anchor="sect-3.7"><t>Matrix</name> <t> A TE node connectivity matrix is a TE node's attribute describing the TE node's switching limitations inathe form of valid switching combinations of the TE node's LTPs (see below). From the point of view of a potential TE path arriving at the TE node at a given inbound LTP, the node's connectivity matrix describes valid (permissible) outbound LTPsforfrom which the TE pathtocan leave the TEnode from.</t> <!--[rfced] id2xml converted to artwork, please review --> <figure><artwork><![CDATA[ In Figure 1,node.</t> <t>In <xref target="fig1"/>, the connectivity matrix on Node-2is: {<LTP-6, LTP-1>, <LTP-5, LTP-2>, <LTP-5, LTP-4>, <LTP-4, LTP-1>, <LTP-3, LTP-2>} ]]></artwork> </figure>is as follows:</t> <t>{<LTP-6, LTP-1>, <LTP-5, LTP-2>, <LTP-5, LTP-4>, <LTP-4, LTP-1>, <LTP-3, LTP-2>}</t> </section> <sectiontitle="TTPanchor="sect-3.8" numbered="true" toc="default"> <name>TTP Local Link Connectivity List(LLCL)" anchor="sect-3.8"><t>(LLCL)</name> <t> A TTP Local Link Connectivity List (LLCL) is aListlist of TE links terminated by theTTP hostingTE node(i.e. list of the TE link LTPs),hosting a TTP, to which the TTP could beconnected to.connected. From the point of view ofathe potential TEpath,path of a connection, an LLCL provides a list of valid TE links the TE path needs to start/stop on for theconnection, taking the TE path,connection to be successfully terminated onthe TTP in question.</t> <!--[rfced] id2xml converted to artwork, please review --> <figure><artwork><![CDATA[ In Figure 1,a TTP.</t> <t>In <xref target="fig1"/>, the LLCL on Node-1is: {<TTP-1, LTP-5>, <TTP-1, LTP-2>, <TTP-2, LTP-3>, <TTP-2, LTP4>} ]]></artwork> </figure>is as follows:</t> <t>{<TTP-1, LTP-5>, <TTP-1, LTP-2>, <TTP-2, LTP-3>, <TTP-2, LTP-4>}</t> </section> <sectiontitle="TE Path" anchor="sect-3.9"><t>anchor="sect-3.9" numbered="true" toc="default"> <name>TE Path</name> <t> A TE path is an ordered list of TE links and/or TE nodes on the TE topologygraph, inter-connectinggraph; this path interconnects a pair of TTPs to betakenused by a potential connection.TE paths, forFor example, TE paths could be a product of successful path computation performed for a given transport service.</t><!--[rfced] id2xml converted to artwork, please review --> <figure><artwork><![CDATA[ In Figure 1,<t>In <xref target="fig1"/>, the TEPathpath for TE-Tunnel-1is: {Node-1:TTP-1,is as follows:</t> <t>{Node-1:TTP-1, Link-12, Node-2, Link-23,Node-3:TTP1} ]]></artwork> </figure>Node-3:TTP-1}</t> </section> <sectiontitle="TE Inter-Layer Lock" anchor="sect-3.10"><t>anchor="sect-3.10" numbered="true" toc="default"> <name>TE Inter-layer Lock</name> <t>A TE inter-layer lock is a modeling concept describingclient-server layeradaptation relationships between the client layer and the server layer and hence is important forthemulti-layertraffic engineering.Traffic Engineering. It is an association of Mclient layerclient-layer LTPs and Nserver layerserver-layer TTPs, within which data arriving at any of theclient layerclient-layer LTPs could be adopted onto any of theserver layerserver-layer TTPs. A TE inter-layer lock is identified by an inter-layer lock ID, which is unique across all TE topologies provided by the same provider. Theclient layerclient-layer LTPs and theserver layerserver-layer TTPs associated within a given TE inter-layer lock are annotated with the same inter-layer lock ID attribute.</t><figure title="TE Inter-Layer Lock ID Associations" anchor="fig3"><artwork><![CDATA[ | +---+ __ | | | TE Node \/ TTP o LTP | +---+ | | ----- TE Link | ***** TTP Local Link Connectivity o---------------------------------- (IL-1) C-LTP-1 +------------+ C-LTP-2 (IL-1) --------O (IL-1) O-------- (IL-1) C-LTP-3 | S-TTP-1 | C-LTP-4 (IL-1) --------O __ 0-------- (IL-1) C-LTP-5 | *\/* | C-LTP-5 (IL-1) --------O * * O-------- | *(IL-1)* | S-LTP-3 | * S-TTP-2* | S-LTP-4 --------o* __ *o-------- | *\/* | | * * | +--o------o--+ S-LTP-1 | | S-LTP-2 ]]></artwork> </figure><t>On the picture aboveIn <xref target="fig3"/>, a TE inter-layer lock withIL_1an ID of IL-1 associates6 client layersix client-layer LTPs (C-LTP-1-through C-LTP-6) with twoserver layerserver-layer TTPs (S-TTP-1 and S-TTP-2). They all have the same attribute--- TE inter-layer lockID:ID IL-1, which is the only thing that indicates the association. A given LTP may have0, 1zero, one, or more inter-layer lock IDs. In the lattercasecase, this means that the data arriving at the LTP may be adopted onto any of the TTPs associated with all specified inter-layer locks. For example, C-LTP-1 could have two inter-layer lock IDs- IL- 1-- IL-1 and IL-2. This would mean that C-LTP-1 for adaptation purposes could use not just the TTPs associated with inter-layer lock IL-1(i.e.</t> <t>(i.e., S-TTP-1 and S-TTP-2onin thepicture),figure) but any of the TTPs associated with inter-layer lock IL-2 as well. Likewise, a given TTP may have one or more inter-layer lock IDs, meaning that it can offer the adaptation service to any ofclient layerthe client-layer LTPs with an inter-layer lock ID matching one of its own. Additionally, each TTP has anattribute - Unreserved Adaptation Bandwidth,unreserved adaptation bandwidth attribute, which announces its remaining adaptation resources that are sharable between all potentialclientclient-layer LTPs.</t> <figure anchor="fig3"> <name>TE Inter-layer Lock ID Associations</name> <artwork name="" type="" align="left" alt=""><![CDATA[ | +---+ __ | | | TE Node \/ TTP o LTP | +---+ | | ----- TE Link | ***** TTP Local Link Connectivity o---------------------------------- (IL-1) C-LTP-1 +------------+ C-LTP-2 (IL-1) --------O (IL-1) O-------- (IL-1) C-LTP-3 | S-TTP-1 | C-LTP-4 (IL-1) --------O __ 0-------- (IL-1) C-LTP-5 | *\/* | C-LTP-6 (IL-1) --------O * * O-------- | *(IL-1)* | S-LTP-3 | * S-TTP-2* | S-LTP-4 --------o* __ *o-------- | *\/* | | * * | +--o------o--+ S-LTP-1 | | S-LTP-2]]></artwork> </figure> <t> LTPs and TTPs associated within the same TE inter-layer lock may be hosted by the same (hybrid, multi-layer) TE node or multiple TE nodes located in the same or separate TE topologies. The latter case is especiallyimportantimportant, since TE topologies of different layer networks could be modeled by separate augmentations of the basic (common to all layers) TE topology model.</t> </section> <sectiontitle="Underlayanchor="sect-3.11" numbered="true" toc="default"> <name>Underlay TEtopology" anchor="sect-3.11"><t> UnderlayTopology</name> <t> An underlay TE topology is a TE topology that serves as a base forconstructingthe construction of overlay TEtopologies</t>topologies.</t> </section> <sectiontitle="Overlayanchor="sect-3.12" numbered="true" toc="default"> <name>Overlay TEtopology" anchor="sect-3.12"><t> OverlayTopology</name> <t> An overlay TE topology is a TE topology that is constructed based on one or more underlay TE topologies. Each TE node of the overlay TE topology represents an arbitrary segment of an underlay TE topology; each TE link of the overlay TE topology represents an arbitrary TE path in one of the underlay TE topologies. The overlay TE topology and the supporting underlay TE topologies may represent distinct layer networks(e.g.(e.g., OTN/ODUk andWDM/OChWDM/OCh, respectively) or the same layer network.</t> </section> <sectiontitle="Abstractanchor="sect-3.13" numbered="true" toc="default"> <name>Abstract TEtopology" anchor="sect-3.13"><t> AbstractTopology</name> <t> An abstract TE topology is a topology that contains abstract topological elements (nodes, links,tunnel termination points). AbstractTTPs). An abstract TE topology is an overlay TE topology created by a topology provider and customized for a topology provider's client based on one or more of the provider'snativeNative TE topologies (underlay TE topologies), the provider'spoliciespolicies, and the client's preferences. For example, afirst levelfirst-level topology provider (such asDomain Controller)a domain controller) can create an abstract TE topology for its client(e.g. Multi-Domain Service Coordinator)(e.g., a multi-domain service coordinator) based onthe provider'sone or morenativeof the provider's Native TE topologies, localpolicies/profilespolicies/profiles, and the client's TE topology configurationrequests</t>requests.</t> <t><xreftarget="fig4"/>target="fig4" format="default"/> shows an example of an abstract TE topology.</t> <figuretitle="Abstractanchor="fig4"> <name>Abstract TETopology" anchor="fig4"><artwork><![CDATA[Topology</name> <artwork name="" type="" align="left" alt=""><![CDATA[ | +---+ | | | TE Node | +---+ | ----- TE Link o---------------------------------- +---+ +---+|s31|--------------|S5|S3 | |S5 | +---+\ / +---+ \ / \ / \+---+/ +---+ /|AN1|\----------------|S8 | / +---+ \ +---+ +---+ / \ +---+ |S9|-------------|S11|| |S11| +---+ +---+ Abstract TE Topology +---+ +---+ |S1 |--------------------|S2 | +---+ +---+ / \ / \ +---+ / +---+ \ +---+|s3|S3 |--------------------|S4 |---------|S5 | +---+\ +---+ +---+ \ \ \ \ \ \ \+---+ +---+ +---+ /|S6 |\ |S7 |---------|S8 | / +---+ \ +---+\ /+---+ +---+ / \ +---+ +---+ / |S9 |-------------|S10|--------------|S11|/ +---+ +---+ +---+ Native TETopology ]]></artwork>Topology]]></artwork> </figure> </section> </section> <sectiontitle="Model Applicability" anchor="sect-4"><section title="Nativeanchor="sect-4" numbered="true" toc="default"> <name>Model Applicability</name> <section anchor="sect-4.1" numbered="true" toc="default"> <name>Native TETopologies" anchor="sect-4.1"><t>Topologies</name> <t> The model discussed in thisdraftdocument can be used to represent and retrievenativeNative TE topologies on a given TE system.</t> <t> Consider the network topology depicted in <xref target="fig5" format="default"/>. R1 .. R9 are nodes representing routers. An implementation <bcp14>MAY</bcp14> choose to construct a Native TE topology using all nodes and links present in the given TED as depicted in <xref target="fig6" format="default"/>. The data model defined in this document can be used to represent and retrieve this TE topology.</t> <figuretitle="Exampleanchor="fig5"> <name>Example NetworkTopology" anchor="fig5"><artwork><![CDATA[Topology</name> <artwork name="" type="" align="left" alt=""><![CDATA[ | +---+ | | | TE Node | +---+ | ----- TE Link o---------------------------------- +---+ +---+ +---+ +---+ +---+ | R1|-------| R2|--------| R3|---------| R4|---------| R5| +---+ +---+ +---+ +---+ +---+ | / \ / \ / | / \ / \ / | / \ / \ / | / \ / \ / | / \ / \ / +---+ +---+ +---+ +---+ | R6|-------------| R7| | R8|---------| R9| +---+ +---+ +---++---+ ]]></artwork>+---+]]></artwork> </figure><t> Consider the network topology depicted in <xref target="fig5"/>. R1 .. R9 are nodes representing routers. An implementation MAY choose to construct a native TE Topology using all nodes and links present in the given TED as depicted in <xref target="fig6"/>. The data model proposed in this document can be used to retrieve/represent this TE topology.</t><figuretitle="Nativeanchor="fig6"> <name>Native TE Topology asseenSeen on NodeR3" anchor="fig6"><artwork><![CDATA[R3</name> <artwork name="" type="" align="left" alt=""><![CDATA[ --------------- | Native | | [ ] TE Node |TE-TopologyTE Topology | | +++ TE Link --------------- o-------------- [R1] ++++ [R2] ++++ [R3] ++++ [R4] ++++ [R5] + + + + + + + + + + + + + + ++ ++ [R6] +++++++++ [R7] [R8] ++++[R9] ]]></artwork>[R9]]]></artwork> </figure> <t> Consider the caseofwhere the topologybeingis split in a way that some nodes participate in OSPF-TE while others participate in ISIS-TE (<xreftarget="fig7"/>).target="fig7" format="default"/>). An implementationMAY<bcp14>MAY</bcp14> choose to construct separate TETopologiestopologies based on the information source. ThenativeNative TETopologiestopologies constructed using only nodes and links that werelearntlearned via a specific information source are depicted in <xreftarget="fig8"/>.target="fig8" format="default"/>. The data modelproposeddefined in this document can be used toretrieve/represent these TE topologies.</t> <t> Similarly, the data model can be used to represent/retrieve a TE Topology that is constructed using only nodesrepresent andlinks that belong to a particular technology layer. The data model is flexible enough toretrieveand represent many such nativethese TETopologies.</t>topologies.</t> <figuretitle="Exampleanchor="fig7"> <name>Example Split NetworkTopology" anchor="fig7"><artwork><![CDATA[Topology</name> <artwork name="" type="" align="left" alt=""><![CDATA[ : TEinfo distributedInfo Distributed via ISIS-TE : TEinfo distributedInfo Distributed via OSPF-TE : +---+ +---+ +---+ +---+ +---+ | R1|-------| R2|--------| R3|---------| R4|---------| R5| +---+ +---+ +---+ +---+ +---+ | / : \ / \ / | / : \ / \ / | / : \ / \ / | / : \ / \ / | / : \ / \ / +---+ +---+ : +---+ +---+ | R6|-------------| R7| : | R8|---------| R9| +---+ +---+ : +---+ +---+: ]]></artwork>:]]></artwork> </figure> <figuretitle="Nativeanchor="fig8"> <name>Native TE Topologies asseenSeen on NodeR3" anchor="fig8"><artwork><![CDATA[R3</name> <artwork name="" type="" align="left" alt=""><![CDATA[ ----------------------- : ----------------------- |Native TE Topology | : |Native TE Topology | |Info-Source: ISIS-TE | : |Info-Source: OSPF-TE | ----------------------- : ----------------------- : [R1] ++++ [R2] ++++ [R3] : [R3'] ++++ [R4] ++++ [R5] + + : + + + + + + : + + + + + + : ++ ++ [R6] +++++++++ [R7] : [R8] ++++[R9] ]]></artwork>[R9]]]></artwork> </figure> <t>Similarly, the data model can be used to represent and retrieve a TE topology that is constructed using only nodes and links that belong to a particular technology layer. The data model is flexible enough to represent and retrieve many such Native TE topologies.</t> </section> <sectiontitle="Customizedanchor="sect-4.2" numbered="true" toc="default"> <name>Customized TETopologies" anchor="sect-4.2"><t>Topologies</name> <t> A Customized TE topology is a topology that was modified by the provider to honor a particular client's requirements or preferences. The model discussed in thisdraftdocument can be used to represent,retrieveretrieve, and manipulatecustomizedCustomized TETopologies.topologies. The model allows the provider to present the network in abstract TETermsterms on aper clientper&nbhy;client basis. These customized topologies contain sufficient information for thepath computingclient to compute and select paths according to its policies.</t><figure title="Example<t> Consider the network topology depicted in <xref target="fig9" format="default"/>. This is a typical packet opticaltopology" anchor="fig9"><artwork><![CDATA[transport deployment scenario where the WDM-layer network domain serves as a server network domain providing transport connectivity to the packet-layer network domain (client network domain). Nodes R1, R2, R3, and R4 are IP routers that are connected to an optical WDM transport network. A, B, C, D, E, and F are WDM nodes that constitute the server network domain.</t> <figure anchor="fig9"> <name>Example Packet Optical Topology</name> <artwork name="" type="" align="left" alt=""><![CDATA[ | +---+ /-\ | | | Router ( ) WDM | +---+ Node \-/nodeNode | o---------------------------- +---+ /-\ /-\ /-\ +---+ | R1|-------( A )--------( C )---------( E )---------| R3| +---+ \-/ \-/ \-/ +---+ / \ / \ / \ / \ / \ / \ / \ / \ / \ / \ +---+ /-\ /-\ /-\ +---+ | R2|---------( B )---------( D )---------( F )---------| R4| +---+ \-/ \-/ \-/+---+ ]]></artwork>+---+]]></artwork> </figure> <t>ConsiderThe goal here is to augment thenetworkclient's TE topologydepicted in <xref target="fig9"/>. This iswith atypical packet optical transport deployment scenario whereCustomized TE topology provided by the WDMlayer network domain serves as a Server Network Domain providing transport connectivity tonetwork. Given thepacket layer network Domain (Client Network Domain). Nodes R1, R2, R3availability of the paths A-E, B-F, andR4 are IP routers that are connectedB-E (<xref target="fig10" format="default"/>), a Customized TE topology as depicted in <xref target="fig11" format="default"/> is provided toan Optical WDM transport network. A, B, C, D, Ethe client. This Customized TE topology is merged with the client's Native TE topology, andF are WDM nodes that constitutetheServer Network Domain.</t>resulting topology is depicted in <xref target="fig12" format="default"/>.</t> <figuretitle="Pathsanchor="fig10"> <name>Paths within theprovider domain" anchor="fig10"><artwork><![CDATA[Provider Domain</name> <artwork name="" type="" align="left" alt=""><![CDATA[ | ***** B-F WDM Path | @@@@@ B-E WDM Path | $$$$$ A-E WDM Path o-------------------- +---+ /-\ $$$$$$$$ /-\ $$$$$$$$$ /-\ +---+ | R1|-------( A )--------( C )---------( E )---------| R3| +---+ \-/ @\-/ @@@@@@@@@ \-/ +---+ @/ \ / \ @/ \ / \ @/ \ / \ @/ \ / \ @/ \ / \ +---+ /-\ ********* /-\ ********* /-\ +---+ | R2|---------( B )---------( D )---------( F )---------| R4| +---+ \-/ \-/ \-/+---+ ]]></artwork>+---+]]></artwork> </figure> <figuretitle="Customizedanchor="fig11"> <name>Customized TE TopologyprovidedProvided to theClient" anchor="fig11"><artwork><![CDATA[Client</name> <artwork name="" type="" align="left" alt=""><![CDATA[ ++++++++ [A] ++++++++++++++++++++ [E] +++++++++ +++++ ++++ ++++ ++++ ++++ ++++++++ [B] ++++++++++++++++++++ [F]+++++++++ ]]></artwork>+++++++++]]></artwork> </figure><t> The goal here is to augment the Client TE Topology with a customized TE Topology provided by the WDM network. Given the availability of the paths A-E, B-F and B-E (<xref target="fig10"/>), a customized TE Topology as depicted in <xref target="fig11"/> is provided to the Client. This customized TE Topology is merged with the Client's Native TE Topology and the resulting topology is depicted in <xref target="fig12"/>.</t><figuretitle="Customizedanchor="fig12"> <name>Customized TE TopologymergedMerged withthe Client's Native TE Topology" anchor="fig12"><artwork><![CDATA[the Client's Native TE Topology</name> <artwork name="" type="" align="left" alt=""><![CDATA[ [R1] ++++++++ [A] ++++++++++++++++++++ [E] +++++++++ [R3] +++++ ++++ ++++ ++++ ++++ [R2] ++++++++ [B] ++++++++++++++++++++ [F] +++++++++[R4] ]]></artwork>[R4]]]></artwork> </figure> <t> The data modelproposeddefined in this document can be used toretrieve/represent/manipulaterepresent, retrieve, and manipulate thecustomizedCustomized TETopologytopology depicted in <xreftarget="fig11"/>.</t>target="fig11" format="default"/>.</t> <t> AcustomizedCustomized TE topology is not necessarily an abstract TE topology. The provider may produce, for example, an abstract TE topology of a certain type(e.g.(a single-abstract-node-with-connectivity-matrix topology, a border-nodes-connected-via-mesh-of-abstract-links topology, etc.) and expose it toall/someall or some clients in the expectation that the clients will use it without customization. On the other hand, a client may request a customized version of the provider'snativeNative TE topology(e.g.(e.g., by requesting the removal of TE linkswhichthat belong to certain layers, are too slow, are notprotectedprotected, and/or have a certain affinity). Note that the resulting TE topology will not be abstract (because it will not contain abstractelements),elements) but will be customized (modified upon the client's instructions).</t> <t> The client ID field in the TE topology identifier (<xreftarget="sect-5.4"/>. )target="sect-5.4" format="default"/>) indicates which client the TE topology is customized for. Although an authorized clientMAY<bcp14>MAY</bcp14> receive a TE topology with the client ID field matching some other client, the client can customize only TE topologies with the client ID field either set to 0 or matching the ID of the client in question. If the client starts the reconfiguration of atopologytopology, its client ID will be automatically set in the topology ID field for all future configurations and updateswrt.with regard to the topology in question.</t> <t> Theprovider MAY tell the client that a given TE topology cannot be re-negotiated,provider, by setting its own(provider's)ID in the client ID field of the topologyID.</t>ID, <bcp14>MAY</bcp14> tell the client that a given TE topology cannot be renegotiated.</t> <t> Even though this data model allowstothe access of TE topology information across clients, implementationsMAY<bcp14>MAY</bcp14> restrict access for particular clients to particular data fields. The Network Configuration Access Control Model (NACM) <xreftarget="RFC8341"/>target="RFC8341" format="default"/> provides such a mechanism.</t> </section> <sectiontitle="Merginganchor="sect-4.3" numbered="true" toc="default"> <name>Merging TE Topologies Provided by MultipleProviders" anchor="sect-4.3"><t>Providers</name> <t> A client may receive TE topologies provided by multiple providers, each of whichmanagingmanages a separate domain of a multi-domain network. In order to make use of said topologies, the client is expected to merge the provided TE topologies into one or moreclient's nativeof its own Native TE topologies, each of which homogeneouslyrepresentingrepresents the multi-domain network. This makes it possible for the client to select end-to-end TE paths for its services traversing multiple domains.</t> <t> In particular, the process of merging TE topologies includes:</t><t><list style="symbols"> <t>Identifying<ul spacing="normal"> <li>Identifying neighboring domains and locking their topologies horizontally by connecting their inter-domain open-ended TElinks;</t> <t>Renaminglinks.</li> <li>Renaming TEnode, link,node IDs, link IDs, and SRLG IDs toonesIDs allocated from a separatename space;namespace; this is necessary because all TE topologies are considered to be, generally speaking,independent with a possibility ofindependent, and clashes among TEnode,node IDs, link IDs, or SRLGIDs;</t> <t>Locking,IDs are possible.</li> <li>Locking, vertically, TE topologies associated with different layer networks, according to provided topology inter-layer locks; this is done to facilitate inter-layer path computations across multiple TE topologies provided by the same topologyprovider.</t> </list> </t>provider.</li> </ul> <t> <xref target="fig13" format="default"/> illustrates the process whereby the client merges the TE topologies furnished by its providers.</t> <figuretitle="Merginganchor="fig13"> <name>Merging Domain TETopologies" anchor="fig13"><artwork><![CDATA[Topologies: An Example</name> <artwork name="" type="" align="left" alt=""><![CDATA[ /---\ +---+ +---+ +---+ +---+ /---\|s3 |------|S13|----|S15|------|S23|----|S25|------|C21||C11|------|S13|----|S15|------|S23|----|S25|------|C21| \---/ +---+\ +---+ +---+ /+---+ \---/ \ / \ / \+---+ +---+/ +---+ /---\ |S18|------|S24| |S28|------|C22| +---+ +---+\ /+---+ \---/ \/ /\ /---\ +---+ +---+ +---+/ \+---+ /---\ |C12|------|S19|----|S17|------|S29|----|S27|------|C23| \---/ +---+ +---+ +---+ +---+ \---/ Domain 1 TE Topology Domain 2 TE Topology +---+ +---+ +---+ +---+ -----|S13|----|S15|---- ----|S23|----|S25|---- +---+\ +---+ +---+ /+---+ \ / \ / \+---+ +---+/ +---+ |S18|---- ----|S24| |S28|---- +---+ +---+\ /+---+ \/ /\ +---+ +---+ +---+/ \+---+ -----|S19|----|S17|---- ----|S29|----|S27|---- +---+ +---+ +---++---+ ]]></artwork>+---+]]></artwork> </figure><t><t>In <xreftarget="fig13"/> illustrates the process of merging, by the client, of TE topologies provided by the client's providers. In the Figure,target="fig13"/>, each of the two providers caters to the client (abstract ornative)Native) TE topology, describing the network domain under the respective provider's control. The client, by consultingthesuch attributes of the inter-domain TE links- suchas inter-domain plug IDs or remote TEnode/link IDsnode IDs / link IDs (as defined by the TETopology model) -topology model), is able to determine that:</t><t><list style="format (%c)"> <t>the<ol spacing="normal" type="1"> <li>the two domains are adjacent and areinter-connectedinterconnected via three inter-domain TE links,and; </t> <t>and</li> <li> each domain is connected to a separate customer site, connecting theleftdomain on the left in theFigurefigure to customer devicesC-11C11 andC-12,C12, and therightdomain on the right to customer devicesC-21, C-22C21, C22, andC-23. </t> </list> </t>C23.</li> </ol> <t> Therefore, the clientinter-connectsinterconnects the open-ended TE links, as shown on the upper part of theFigure.</t>figure.</t> <t> Asmentioned,mentioned previously, one way tointer-connectinterconnect the open-ended inter-domain TE links of neighboring domains is to mandate that the providerstospecify a remotenodeID/linkIDnode ID / link ID attribute in the provided inter-domain TE links.This, however,However, this may prove not to benotflexible. For example, the providers may not know the respective remotenodeIDs/ linkIDs.node IDs / link IDs. More importantly, this option does not allowforthe client tomix-n-matchmix and match multiple topologies (more thanone) topologiesone topology) catered by the same providers (see below).Another, more flexible,Another optionto resolve(which is more flexible) for resolving the open-ended inter-domain TE links isby annotatingto annotate them with the inter-domain plug ID attribute.Inter-domainThe inter-domain plug ID is a network-wide unique number that identifies on the network aconnectivity supportingconnection that supports a given inter-domain TE link. Instead of specifying a remote nodeID/linkID / link ID, an inter-domain TE link may provide a non-zero inter-domain plug ID. It is expected that two neighboring domain TE topologies (provided by separate providers) willhaveeach have at least one open-ended inter-domain TE link with an inter-domain plug ID matchingto onean ID provided by its neighbor. For example, the inter-domain TE link originating from node S15 of the Domain 1 TE topology (<xreftarget="fig13"/>)target="fig13" format="default"/>) and the inter-domain TE link coming from node S23 of the Domain 2 TE topology may specify a matching inter-domain plug ID(e.g.(e.g., 175344). This allowsforthe client to identify adjacent nodes in the separate neighboring TE topologies and resolve the inter-domain TE links connectingthemthem, regardless of their respectivenodeIDs/linkIDsnode IDs / link IDs (which, asmentioned,mentioned previously, could be allocated from independentname spaces).namespaces). Inter-domain plug IDs may be assigned and managed by a central network authority. Alternatively, inter-domain plug IDs could be dynamicallyauto-discovered (e.g.autodiscovered (e.g., viaLMP protocol).</t>the Link Management Protocol (LMP)).</t> <t> Furthermore, the client renames the TE nodes,linkslinks, and SRLGs offered in the abstract TE topologies by assigning to them IDs allocated from a separatename spacenamespace managed by the client. Such renaming is necessary, because the two abstract TE topologies may have their ownname spaces,namespaces, generally speaking, independent one from another; hence, ID overlaps/clashes are possible. For example, both TE topologies have TE nodes named S7, which, after renaming, appear in the merged TE topology as S17 and S27, respectively.</t> <t> Once the merging process is complete, the client can use the merged TE topology for path computations across bothdomains,domains -- for example, to compute a TE path connectingC-11C11 toC-23.</t>C23.</t> </section> <sectiontitle="Dealinganchor="sect-4.4" numbered="true" toc="default"> <name>Dealing with Multiple Abstract TE Topologies Provided by the SameProvider" anchor="sect-4.4"> <figure title="Merging Domain TE Topologies" anchor="fig14"><artwork><![CDATA[ Domain 1 Abstract TE Topology 1 Domain 2 Abstract TE Topology 1 +---+ +---+ +---+ +---+ -----|S13|----|S15|---- ----|S23|----|S25|---- +---+\ +---+ +---+ /+---+ \ / \ / \+---+ +---+/ +---+ |S18|---- ----|S24| |S28|---- +---+ +---+\ /+---+ \/ /\ +---+ +---+ +---+/ \+---+ -----|S19|----|S17|---- ----|S29|----|S27|---- +---+ +---+ +---+ +---+ Domain 1 Abstract TE Topology 1 Domain 2 Abstract TE Topology 1 +------------+ +------------+ -----| |---- ----| |---- | | | | | AN1 |---- ----| AN1 |---- | | | | -----| |---- ----| |---- +------------+ +------------+ ]]></artwork> </figure>Provider</name> <t> Based on local configuration,templatestemplates, and/or policies pushed by the client, a given provider may expose more than one abstract TE topology to the client. For example, one abstract TE topology could be optimized based on a lowest-cost criterion, while another one could be based on best possible delay metrics, while yet another one could be based on maximum bandwidth availability for the client services. Furthermore, the client may request all or some providers to expose additional abstract TE topologies, possibly of a different type and/or optimized differently, as compared to already-provided TE topologies. In any case, the client should be prepared for a provider to offer to the client more than one abstract TE topology.</t> <t> It should be up to the client (based on the client's local configuration and/or policies conveyed to the client by the client's clients) to decide how tomix-and-matchmix and match multiple abstract TE topologies provided by each or some of the providers, as well as how to merge them into the client'snativeNative TE topologies. The client also decides how many such merged TE topologies it needs to produce and maintain. For example, in addition to the merged TE topology depicted in the upper part of <xreftarget="fig13"/>,target="fig13" format="default"/>, the client may merge the abstract TE topologies received from the two providers, as shown in <xreftarget="fig14"/>,target="fig14" format="default"/>, into the client's additionalnativeNative TE topologies, as shown in <xreftarget="fig15"/>.</t> <t> Note that allowing for the client mix-n-matching of multipletarget="fig15" format="default"/>.</t> <figure anchor="fig14"> <name>Merging Domain TEtopologies assumes that inter-domain plug IDs (rather than remote nodeID/linkID) option is used for identifying neighboring domains and inter-domainTopologies: Another Example</name> <artwork name="" type="" align="left" alt=""><![CDATA[ Domain 1 Abstract TElink resolution.</t>Topology 1 Domain 2 Abstract TE Topology 1 +---+ +---+ +---+ +---+ -----|S13|----|S15|---- ----|S23|----|S25|---- +---+\ +---+ +---+ /+---+ \ / \ / \+---+ +---+/ +---+ |S18|---- ----|S24| |S28|---- +---+ +---+\ /+---+ \/ /\ +---+ +---+ +---+/ \+---+ -----|S19|----|S17|---- ----|S29|----|S27|---- +---+ +---+ +---+ +---+ Domain 1 Abstract TE Topology 2 Domain 2 Abstract TE Topology 2 +------------+ +------------+ -----| |---- ----| |---- | | | | | AN1 |---- ----| AN1 |---- | | | | -----| |---- ----| |---- +------------+ +------------+]]></artwork> </figure> <figuretitle="Multipleanchor="fig15"> <name>Multiple Native (Merged) Client's TETopologies" anchor="fig15"><artwork><![CDATA[Topologies</name> <artwork name="" type="" align="left" alt=""><![CDATA[ Client's Merged TE Topology 2 /---\ +------------+ +------------+ /---\|s3 |------||C11|------| |------| |------|C21| \---/ | | | | \---/ | | | | | | | | | | | | /---\ | AN11 |------| AN21 |------|C22| | | | | \---/ | | | | | | | | /---\ | | | | /---\ |C12|------| |------| |------|C23| \---/ +------------+ +------------+ \---/ Client's Merged TE Topology 3 /---\ +------------+ +---+ +---+ /---\|s3 |------||C11|------| |------|S23|----|S25|------|C21| \---/ | | +---+ /+---+ \---/ | | / | | / | | +---+/ +---+ /---\ | AN11 |------|S24| |S28|------|C22| | | +---+\ /+---+ \---/ | | \/ | | /\ /---\ | | +---+/ \+---+ /---\ |C12|------| |------|S29|----|S27|------|C23| \---/ +------------+ +---+ +---+\---/ ]]></artwork>\---/]]></artwork> </figure> <t> Note that allowing the client to mix and match multiple TE topologies assumes that inter-domain plug IDs (rather than a remote node ID / link ID) are used as the option for identifying neighboring domains and inter-domain TE link resolution.</t> <t> It is important to note that each of the threenativeNative (merged) TE topologies could be used by the client for computing TE paths for any of the multi-domain services. The choiceas toof which topology to use for a given service depends on the serviceparameters/requirements andparameters/requirements, the topology'sstyle,style and optimizationcriteriacriteria, and the level ofdetails.</t>detail.</t> </section> </section> <sectiontitle="Modeling Considerations" anchor="sect-5"><section title="Network topology building blocks" anchor="sect-5.1"><t>anchor="sect-5" numbered="true" toc="default"> <name>Modeling Considerations</name> <section anchor="sect-5.1" numbered="true" toc="default"> <name>Network Topology Building Blocks</name> <t> The network topology building blocks are discussed in <xreftarget="RFC8345"/>.target="RFC8345" format="default"/>. The TETopologytopology modelproposeddefined in this document augments and uses theietf-network-topology"ietf-network-topology" module defined in <xreftarget="RFC8345"/>.</t>target="RFC8345" format="default"/>.</t> <figuretitle="Augmentinganchor="fig16"> <name>Augmenting the Network TopologyModel" anchor="fig16"><artwork><![CDATA[Model</name> <artwork name="" type="" align="left" alt=""><![CDATA[ +------------------------+ || |Network Topology Model | | (ietf-network-topology)| +------------------------+ | | | V +------------------------+ | TE Topology | | Model || | +------------------------+ ]]></artwork>+------------------------+]]></artwork> </figure> </section> <sectiontitle="Technology agnosticanchor="sect-5.2" numbered="true" toc="default"> <name>Technology-Agnostic TE Topologymodel" anchor="sect-5.2"><t>Model</name> <t> The TETopologytopology modelproposeddefined in this document is meant to be network technology agnostic. Othertechnology specifictechnology-specific TETopologytopology models can augment and use the building blocks provided bythe proposed model.</t>this model, as illustrated in <xref target="fig17"/>.</t> <figuretitle="Augmentinganchor="fig17"> <name>Augmenting theTechnology agnosticTechnology-Agnostic TE Topologymodel" anchor="fig17"><artwork><![CDATA[Model</name> <artwork name="" type="" align="left" alt=""><![CDATA[ +-----------------------------+ | TE Topology Model || (Defined in This Document) |+-----------------------------+ | +-------------+-------------+-------------+ | | | | V V V V+------------+ +------------++-------------+ +-------------+ |TechnologyTechnology- | |TechnologyTechnology- | | Specific | ...................... | Specific | | TETopology|Topology | | TETopology|Topology | | Model 1 | | Model n |+------------+ +------------+ ]]></artwork>+-------------+ +-------------+]]></artwork> </figure> </section> <sectiontitle="Model Structure" anchor="sect-5.3"><t>anchor="sect-5.3" numbered="true" toc="default"> <name>Model Structure</name> <t> The high-level model structureproposeddefined by this document is as shown below:</t><figure><artwork><![CDATA[<sourcecode name="" type="yangtree"><![CDATA[ module: ietf-te-topology augment /nw:networks/nw:network/nw:network-types: +--rw te-topology! augment /nw:networks: +--rw te! +--rw templates +--rw node-template* [name] {template}? | ............ +--rw link-template* [name] {template}? ............ augment /nw:networks/nw:network: +--rw te-topology-identifier | +--rw provider-id? te-global-id | +--rw client-id? te-global-id | +--rw topology-id? te-topology-id +--rw te! | ............ augment /nw:networks/nw:network/nw:node: +--rw te-node-id? te-types:te-node-id +--rw te! | ............ +--rw tunnel-termination-point* [tunnel-tp-id] +--rw tunnel-tp-id binary | ............ +--rw supporting-tunnel-termination-point* [node-reftunnel- tp-ref]tunnel-tp-ref] | ............ augment /nw:networks/nw:network/nt:link: +--rw te! | .......... augment /nw:networks/nw:network/nw:node/nt:termination-point: +--rw te-tp-id? te-types:te-tp-id +--rw te! |............ ]]></artwork> </figure>............]]></sourcecode> </section> <sectiontitle="Topology Identifiers" anchor="sect-5.4"><t>anchor="sect-5.4" numbered="true" toc="default"> <name>Topology Identifiers</name> <t> TheTE-TopologyTE topology is uniquely identified by a key that has3three constituents- topology-id, provider-id-- "topology-id", "provider-id", andclient-id."client-id". The combination ofprovider-id"provider-id" andtopology-id"topology-id" uniquely identifies anativeNative TETopologytopology on a given provider.The client-id "client-id" is used only when Customized TETopologiestopologies come into play; a "client-id" value of "0" is usedas the client-idfornativeNative TETopologies.</t> <figure><artwork><![CDATA[topologies.</t> <sourcecode name="" type="yangtree"><![CDATA[ augment /nw:networks/nw:network: +--rw te-topology-identifier | +--rw provider-id? te-global-id | +--rw client-id? te-global-id | +--rw topology-id? te-topology-id +--rw te! |............ ]]></artwork> </figure>............]]></sourcecode> </section> <sectiontitle="Genericanchor="sect-5.5" numbered="true" toc="default"> <name>Generic TE LinkAttributes" anchor="sect-5.5"><t>Attributes</name> <t> The model covers the definitions for generic TELinklink attributes--- bandwidth,adminadministrative groups, SRLGs, switching capabilities, TE metricextensionsextensions, etc.</t><figure><artwork><![CDATA[<sourcecode name="" type="yangtree"><![CDATA[ +--rw te-link-attributes ..................... +--rw admin-status? te-admin-status | ..................... +--rw link-index? uint64 +--rw administrative-group? te-types:admin-groups +--rw link-protection-type? enumeration +--rw max-link-bandwidth? te-bandwidth +--rw max-resv-link-bandwidth? te-bandwidth +--rw unreserved-bandwidth* [priority] | ..................... +--rw te-default-metric? uint32 | ..................... +--rw te-srlgs +--rw te-nsrlgs {nsrlg}?..................... ]]></artwork> </figure>.....................]]></sourcecode> </section> <sectiontitle="Genericanchor="sect-5.6" numbered="true" toc="default"> <name>Generic TE NodeAttributes" anchor="sect-5.6"><t>Attributes</name> <t> The model covers the definitions for generic TENodenode attributes.</t> <t>The definition of a generic connectivity matrix is shown below:</t><figure><artwork><![CDATA[<sourcecode name="" type="yangtree"><![CDATA[ +--rw te-node-attributes ........... +--rw connectivity-matrices ........... | +--rw connectivity-matrix* [id] | | +--rw id uint32 | | +--rw from | | | +--rw tp-ref? leafref | | | +--rw label-restrictions | | +--rw to | | | +--rw tp-ref? leafref | | | +--rw label-restrictions | | +--rw is-allowed? boolean ........... | | +--rw underlay! {te-topology-hierarchy}? ........... | | +--rw path-constraints ........... | | +--rw optimizations ........... | | +--ro path-properties........... ]]></artwork> </figure>...........]]></sourcecode> <t>The definition of a TTP Local Link Connectivity List is shown below:</t><figure><artwork><![CDATA[<sourcecode name="" type="yangtree"><![CDATA[ +--rw tunnel-termination-point* [tunnel-tp-id] +--rw tunnel-tp-id binary +--rw admin-status? te-types:te-admin-status +--rw name? string +--rw switching-capability? identityref +--rw encoding? identityref +--rw inter-layer-lock-id* uint32 +--rw protection-type?Identityrefidentityref +--rw client-layer-adaptation ........... +--rw local-link-connectivities ........... | +--rw local-link-connectivity* [link-tp-ref] | +--rw link-tp-ref leafref | +--rw label-restrictions ........... | +--rw is-allowed? boolean | +--rw underlay {te-topology-hierarchy}? ........... | +--rw path-constraints ........... | +--rw optimizations ........... | +--ro path-properties ........... +--rw supporting-tunnel-termination-point* [node-reftunnel-tp- ref]tunnel-tp-ref] +--rw node-ref inet:uri +--rw tunnel-tp-refbinary ]]></artwork> </figure>binary]]></sourcecode> <t> The attributes directly under containerconnectivity-matrices"connectivity-matrices" are the default attributes for allconnectivity-matrixconnectivity matrix entries when theper entryper&nbhy;entry corresponding attribute is not specified. When aper entryper-entry attribute is specified, it overrides the corresponding attribute directly under the containerconnectivity-matrices."connectivity-matrices". The same rule applies to the attributes directly under containerlocal-link-connectivities.</t>"local&nbhy;link&nbhy;connectivities".</t> <t> Each TTP(Tunnel Termination Point) MAY<bcp14>MAY</bcp14> be supported by one or more supporting TTPs. If the TE node hosting the TTP in question refers to a supporting TE node, then the supporting TTPs are hosted by the supporting TE node. If the TE node refers to an underlay TE topology, the supporting TTPs are hosted by one or more specified TE nodes of the underlay TE topology.</t> </section> <sectiontitle="TEDanchor="sect-5.7" numbered="true" toc="default"> <name>TED InformationSources" anchor="sect-5.7"><t>Sources</name> <t> The model allows each TE topological element to have multiple TE information sources (OSPF-TE, ISIS-TE,BGP-LS, User-Configured, System-Processed, Other).Border Gateway Protocol - Link State (BGP-LS), user-configured, system-processed, other). Each information source is associated with a credibility preference to indicate precedence. In scenarios where acustomizedCustomized TETopologytopology is merged into aClient's nativeclient's Native TETopology,topology, the merged topological elements would point to the correspondingcustomizedCustomized TETopologytopology as its information source.</t><figure><artwork><![CDATA[<sourcecode name="" type="yangtree"><![CDATA[ augment /nw:networks/nw:network/nw:node: +--rw te! ........... +--ro information-source? te-info-source +--ro information-source-instance? string +--ro information-source-state | +--ro credibility-preference? uint16 | +--ro logical-network-element? string | +--ro network-instance? string | +--ro topology | +--ro node-ref? leafref | +--ro network-ref? leafref +--ro information-source-entry* | [information-source information-source-instance] | +--ro information-source te-info-source | +--ro information-source-instance string ............ augment /nw:networks/nw:network/nt:link: +--rw te! ........... +--ro information-source? te-info-source +--ro information-source-instance? string +--ro information-source-state | +--ro credibility-preference? uint16 | +--ro logical-network-element? string | +--ro network-instance? string | +--ro topology | +--ro link-ref? leafref | +--ro network-ref? leafref +--ro information-source-entry* | [information-source information-source-instance] | +--ro information-source te-info-source | +--ro information-source-instance string............ ]]></artwork> </figure>............]]></sourcecode> </section> <sectiontitle="Overlay/Underlay Relationship" anchor="sect-5.8"><t>anchor="sect-5.8" numbered="true" toc="default"> <name>Overlay/Underlay Relationship</name> <t> The model captures the overlay and underlay relationship for TE nodes/links. Forexample -example, in networks where multiple TETopologiestopologies are built hierarchically, this model allows the user to start from a specific topological element in thetop mosttopmost topology and traverse all the way down to the supporting topological elements in thebottom mostbottommost topology.</t> <t> This relationship is captured via the "underlay-topology" field for the node and via the "underlay" field for the link. The use of these fields isoptionaloptional, and this functionality is tagged as a "feature" ("te-topology-hierarchy").</t><figure><artwork><![CDATA[<sourcecode name="" type="yangtree"><![CDATA[ augment /nw:networks/nw:network/nw:node: +--rw te-node-id? te-types:te-node-id +--rw te! +--rw te-node-template* leafref {template}? +--rw te-node-attributes | +--rw admin-status? te-types:te-admin-status | | .................... | +--rw underlay-topology {te-topology-hierarchy}? | +--rw network-ref? leafref augment /nw:networks/nw:network/nt:link: +--rw te! +--rw te-link-attributes | .................... | +--rw underlay {te-topology-hierarchy}? | | +--rw enabled? boolean | | +--rw primary-path | | | +--rw network-ref? leafref | | | .................... | | +--rw backup-path* [index] | | | +--rw index uint32 | | | +--rw network-ref? leafref | | | .................... | | +--rw protection-type? identityref | | +--rw tunnel-termination-points | | | +--rw source? binary | | | +--rw destination? binary | | +--rw tunnels | | |.................... ]]></artwork> </figure>....................]]></sourcecode> </section> <sectiontitle="Templates" anchor="sect-5.9"><t>anchor="sect-5.9" numbered="true" toc="default"> <name>Templates</name> <t> The data model providestheusers with the ability to define templates and apply them to link and node configurations. The use of the "template" configuration isoptionaloptional, and this functionality is tagged as a "feature" ("template").</t><figure><artwork><![CDATA[<sourcecode name="" type="yangtree"><![CDATA[ augment /nw:networks/nw:network/nw:node: +--rw te-node-id? te-types:te-node-id +--rw te! +--rw te-node-template* | -> ../../../../te/templates/node-template/name | {template}? augment /nw:networks/nw:network/nt:link: +--rw te! +--rw te-link-template* | -> ../../../../te/templates/link-template/name | {template}? augment /nw:networks: +--rw te! +--rw templates +--rw node-template* [name] {template}? | +--rw name | | te-types:te-template-name | +--rw priority? uint16 | +--rw reference-change-policy? enumeration | +--rw te-node-attributes .......... +--rw link-template* [name] {template}? +--rw name | te-types:te-template-name +--rw priority? uint16 +--rw reference-change-policy? enumeration +--rw te-link-attributes.......... ]]></artwork> </figure>..........]]></sourcecode> <t> Multiple templates can be specifiedtofor a configuration element. When two or more templates specify values for the same configuration field, the value from the template with the highest priority is used. The range of the priority is from 0 to 65535, with a lower number indicating a higher priority. Thereference-change-policy"reference-change-policy" parameter specifies the action that needs to be taken when the template changes on a configuration element that has a reference to this template. The choices of action include taking no action, rejecting the change to thetemplatetemplate, and applying the change to the corresponding configuration.</t> </section> <sectiontitle="Scheduling Parameters" anchor="sect-5.10"><t>anchor="sect-5.10" numbered="true" toc="default"> <name>Scheduling Parameters</name> <t> The model allowstime schedulingtime-scheduling parameters to be specified for each topological element or for the topology as a whole. These parameters allow the provider to present different topological views to the client at different time slots. The use of"scheduling parameters"time-scheduling parameters is optional.</t> <t> The YANG data model for configuration scheduling is defined in <xreftarget="I-D.liu-netmod-yang-schedule"/>,target="YANG-CFG-SCHED" format="default"/>, which allows specifying configuration schedules without altering this data model.</t> </section> <sectiontitle="Notifications" anchor="sect-5.11"><t>anchor="sect-5.11" numbered="true" toc="default"> <name>Notifications</name> <t> Notifications are a key component of any topology data model.</t> <t> <xreftarget="I-D.ietf-netconf-subscribed-notifications"/>target="RFC8639" format="default"/> and <xreftarget="I-D.ietf-netconf-yang-push"/>target="RFC8641"/> define a subscription mechanism and a push mechanism for YANG datastores.This mechanismThese mechanisms currentlyallowsallow the user to:</t><t><list style="symbols"><t>Subscribe<ul spacing="normal"> <li>Subscribe to notifications on aper client basis</t> <t>Specifyper-client basis.</li> <li>Specify subtree filters orxpathXML Path Language (XPath) filters so that onlyinterestedcontents of interest will besent.</t> <t>Specifysent.</li> <li>Specify either periodic or on-demandnotifications.</t> </list> </t>notifications.</li> </ul> </section> </section> <sectiontitle="Guidanceanchor="sect-6" numbered="true" toc="default"> <name>Guidance for WritingTechnology SpecificTechnology-Specific TE TopologyAugmentations" anchor="sect-6"><t>Augmentations</name> <t> The TE topology model defined in this document is technologyagnosticagnostic, as it defines concepts,abstractionsabstractions, and attributes that are common across multiple network technologies. It is envisioned that this base model will be widely used when definingtechnology specifictechnology-specific TE topology models for various layer networks. <xreftarget="I-D.ietf-ccamp-wson-yang"/>,target="YANG-WSON" format="default"/>, <xreftarget="I-D.ietf-ccamp-otn-topo-yang"/>,target="YANG-OTN" format="default"/>, and <xreftarget="I-D.ietf-teas-yang-l3-te-topo"/>target="YANG-L3" format="default"/> are some examples oftechnology specifictechnology-specific TETopologytopology models. Writers of such models are encouraged to augment the basic TE topology model's containers, such as those for TETopology,topologies, TENode,nodes, TELink,links, Link TerminationPoint (LTP),Points (LTPs), Tunnel TerminationPoint (TTP), BandwidthPoints (TTPs), bandwidth, andLabellabels, with thelayer specificlayer-specific attributes instead of defining new containers.</t> <t> Consider the followingtechnology specifictechnology-specific example-topology model:</t><figure><artwork><![CDATA[<sourcecode name="" type="yangtree"><![CDATA[ module: example-topology augment /nw:networks/nw:network/nw:network-types/tet:te-topology: +--rw example-topology! augment /nw:networks/nw:network/tet:te: +--rw attributes +--rw attribute-1? uint8 augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes: +--rw attributes +--rw attribute-2? uint8 augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices: +--rw attributes +--rw attribute-3? uint8 augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices /tet:connectivity-matrix: +--rw attributes +--rw attribute-3? uint8 augment /nw:networks/nw:network/nw:node/tet:te /tet:tunnel-termination-point: +--rw attributes +--rw attribute-4? uint8 augment /nw:networks/nw:network/nw:node/nt:termination-point /tet:te: +--rw attributes +--rw attribute-5? uint8 augment /nw:networks/nw:network/nt:link/tet:te /tet:te-link-attributes: +--rw attributes +--rw attribute-6?uint8 ]]></artwork> </figure>uint8]]></sourcecode> <t> Thetechnology specifictechnology-specific TE bandwidth for this example topology can be specified using the following augment statements:</t><figure><artwork><![CDATA[<sourcecode name="" type="yangtree"><![CDATA[ augment /nw:networks/tet:te/tet:templates/tet:link-template /tet:te-link-attributes /tet:interface-switching-capability/tet:max-lsp-bandwidth /tet:te-bandwidth/tet:technology: +--:(example) +--rw example +--rw bandwidth-1? uint32 augment /nw:networks/tet:te/tet:templates/tet:link-template /tet:te-link-attributes/tet:max-link-bandwidth /tet:te-bandwidth/tet:technology: +--:(example) +--rw example +--rw bandwidth-1? uint32 augment /nw:networks/tet:te/tet:templates/tet:link-template /tet:te-link-attributes/tet:max-resv-link-bandwidth /tet:te-bandwidth/tet:technology: +--:(example) +--rw example +--rw bandwidth-1? uint32 augment /nw:networks/tet:te/tet:templates/tet:link-template /tet:te-link-attributes/tet:unreserved-bandwidth /tet:te-bandwidth/tet:technology: +--:(example) +--rw example +--rw bandwidth-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices /tet:path-constraints/tet:te-bandwidth/tet:technology: +--:(example) +--rw example +--rw bandwidth-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices /tet:connectivity-matrix/tet:path-constraints /tet:te-bandwidth/tet:technology: +--:(example) +--rw example +--rw bandwidth-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:information-source-entry/tet:connectivity-matrices /tet:path-constraints/tet:te-bandwidth/tet:technology: +--:(example) +--ro example +--ro bandwidth-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:information-source-entry/tet:connectivity-matrices /tet:connectivity-matrix/tet:path-constraints /tet:te-bandwidth/tet:technology: +--:(example) +--ro example +--ro bandwidth-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:tunnel-termination-point/tet:client-layer-adaptation /tet:switching-capability/tet:te-bandwidth /tet:technology: +--:(example) +--rw example +--rw bandwidth-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:tunnel-termination-point /tet:local-link-connectivities/tet:path-constraints /tet:te-bandwidth/tet:technology: +--:(example) +--rw example +--rw bandwidth-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:tunnel-termination-point /tet:local-link-connectivities /tet:local-link-connectivity/tet:path-constraints /tet:te-bandwidth/tet:technology: +--:(example) +--rw example +--rw bandwidth-1? uint32 augment /nw:networks/nw:network/nt:link/tet:te /tet:te-link-attributes /tet:interface-switching-capability/tet:max-lsp-bandwidth /tet:te-bandwidth/tet:technology: +--:(example) +--rw example +--rw bandwidth-1? uint32 augment /nw:networks/nw:network/nt:link/tet:te /tet:te-link-attributes/tet:max-link-bandwidth /tet:te-bandwidth/tet:technology: +--:(example) +--rw example +--rw bandwidth-1? uint32 augment /nw:networks/nw:network/nt:link/tet:te /tet:te-link-attributes/tet:max-resv-link-bandwidth /tet:te-bandwidth/tet:technology: +--:(example) +--rw example +--rw bandwidth-1? uint32 augment /nw:networks/nw:network/nt:link/tet:te /tet:information-source-entry /tet:interface-switching-capability/tet:max-lsp-bandwidth /tet:te-bandwidth/tet:technology: +--:(example) +--ro example +--ro bandwidth-1? uint32 augment /nw:networks/nw:network/nt:link/tet:te /tet:information-source-entry/tet:max-link-bandwidth /tet:te-bandwidth/tet:technology: +--:(example) +--ro example +--ro bandwidth-1? uint32 augment /nw:networks/nw:network/nt:link/tet:te /tet:information-source-entry/tet:max-resv-link-bandwidth /tet:te-bandwidth/tet:technology: +--:(example) +--ro example +--ro bandwidth-1? uint32 augment /nw:networks/nw:network/nt:link/tet:te /tet:information-source-entry/tet:unreserved-bandwidth /tet:te-bandwidth/tet:technology: +--:(example) +--ro example +--ro bandwidth-1? uint32 augment /nw:networks/nw:network/nw:node/nt:termination-point/tet:te /tet:interface-switching-capability/tet:max-lsp-bandwidth /tet:te-bandwidth/tet:technology: +--:(example) +--rw example +--rw bandwidth-1?uint32 ]]></artwork> </figure>uint32]]></sourcecode> <t> Thetechnology specifictechnology-specific TE label for this example topology can be specified using the following augment statements:</t><figure><artwork><![CDATA[<sourcecode name="" type="yangtree"><![CDATA[ augment /nw:networks/tet:te/tet:templates/tet:link-template /tet:te-link-attributes/tet:underlay/tet:primary-path /tet:path-element/tet:type/tet:label/tet:label-hop /tet:te-label/tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/tet:te/tet:templates/tet:link-template /tet:te-link-attributes/tet:underlay/tet:backup-path /tet:path-element/tet:type/tet:label/tet:label-hop /tet:te-label/tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/tet:te/tet:templates/tet:link-template /tet:te-link-attributes/tet:label-restrictions /tet:label-restriction/tet:label-start/tet:te-label /tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/tet:te/tet:templates/tet:link-template /tet:te-link-attributes/tet:label-restrictions /tet:label-restriction/tet:label-end/tet:te-label /tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices /tet:label-restrictions/tet:label-restriction /tet:label-start/tet:te-label/tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices /tet:label-restrictions/tet:label-restriction /tet:label-end/tet:te-label/tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices /tet:underlay/tet:primary-path/tet:path-element/tet:type /tet:label/tet:label-hop/tet:te-label/tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices /tet:underlay/tet:backup-path/tet:path-element/tet:type /tet:label/tet:label-hop/tet:te-label/tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices /tet:path-properties/tet:path-route-objects /tet:path-route-object/tet:type/tet:label/tet:label-hop /tet:te-label/tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices /tet:connectivity-matrix/tet:from/tet:label-restrictions /tet:label-restriction/tet:label-start/tet:te-label /tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices /tet:connectivity-matrix/tet:from/tet:label-restrictions /tet:label-restriction/tet:label-end/tet:te-label /tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices /tet:connectivity-matrix/tet:to/tet:label-restrictions /tet:label-restriction/tet:label-start/tet:te-label /tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices /tet:connectivity-matrix/tet:to/tet:label-restrictions /tet:label-restriction/tet:label-end/tet:te-label /tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices /tet:connectivity-matrix/tet:underlay/tet:primary-path /tet:path-element/tet:type/tet:label/tet:label-hop /tet:te-label/tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices /tet:connectivity-matrix/tet:underlay/tet:backup-path /tet:path-element/tet:type/tet:label/tet:label-hop /tet:te-label/tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices /tet:connectivity-matrix/tet:path-properties /tet:path-route-objects/tet:path-route-object/tet:type /tet:label/tet:label-hop/tet:te-label/tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:information-source-entry/tet:connectivity-matrices /tet:label-restrictions/tet:label-restriction /tet:label-start/tet:te-label/tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:information-source-entry/tet:connectivity-matrices /tet:label-restrictions/tet:label-restriction /tet:label-end/tet:te-label/tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:information-source-entry/tet:connectivity-matrices /tet:underlay/tet:primary-path/tet:path-element/tet:type /tet:label/tet:label-hop/tet:te-label/tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:information-source-entry/tet:connectivity-matrices /tet:underlay/tet:backup-path/tet:path-element/tet:type /tet:label/tet:label-hop/tet:te-label/tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:information-source-entry/tet:connectivity-matrices /tet:path-properties/tet:path-route-objects /tet:path-route-object/tet:type/tet:label/tet:label-hop /tet:te-label/tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:information-source-entry/tet:connectivity-matrices /tet:connectivity-matrix/tet:from/tet:label-restrictions /tet:label-restriction/tet:label-start/tet:te-label /tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:information-source-entry/tet:connectivity-matrices /tet:connectivity-matrix/tet:from/tet:label-restrictions /tet:label-restriction/tet:label-end/tet:te-label /tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:information-source-entry/tet:connectivity-matrices /tet:connectivity-matrix/tet:to/tet:label-restrictions /tet:label-restriction/tet:label-start/tet:te-label /tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:information-source-entry/tet:connectivity-matrices /tet:connectivity-matrix/tet:to/tet:label-restrictions /tet:label-restriction/tet:label-end/tet:te-label /tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:information-source-entry/tet:connectivity-matrices /tet:connectivity-matrix/tet:underlay/tet:primary-path /tet:path-element/tet:type/tet:label/tet:label-hop /tet:te-label/tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:information-source-entry/tet:connectivity-matrices /tet:connectivity-matrix/tet:underlay/tet:backup-path /tet:path-element/tet:type/tet:label/tet:label-hop /tet:te-label/tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:information-source-entry/tet:connectivity-matrices /tet:connectivity-matrix/tet:path-properties /tet:path-route-objects/tet:path-route-object/tet:type /tet:label/tet:label-hop/tet:te-label/tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:tunnel-termination-point /tet:local-link-connectivities/tet:label-restrictions /tet:label-restriction/tet:label-start/tet:te-label /tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:tunnel-termination-point /tet:local-link-connectivities/tet:label-restrictions /tet:label-restriction/tet:label-end/tet:te-label /tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:tunnel-termination-point /tet:local-link-connectivities/tet:underlay /tet:primary-path/tet:path-element/tet:type/tet:label /tet:label-hop/tet:te-label/tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:tunnel-termination-point /tet:local-link-connectivities/tet:underlay /tet:backup-path/tet:path-element/tet:type/tet:label /tet:label-hop/tet:te-label/tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:tunnel-termination-point /tet:local-link-connectivities/tet:path-properties /tet:path-route-objects/tet:path-route-object/tet:type /tet:label/tet:label-hop/tet:te-label/tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:tunnel-termination-point /tet:local-link-connectivities /tet:local-link-connectivity/tet:label-restrictions /tet:label-restriction/tet:label-start/tet:te-label /tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:tunnel-termination-point /tet:local-link-connectivities /tet:local-link-connectivity/tet:label-restrictions /tet:label-restriction/tet:label-end/tet:te-label /tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:tunnel-termination-point /tet:local-link-connectivities /tet:local-link-connectivity/tet:underlay /tet:primary-path/tet:path-element/tet:type/tet:label /tet:label-hop/tet:te-label/tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:tunnel-termination-point /tet:local-link-connectivities /tet:local-link-connectivity/tet:underlay/tet:backup-path /tet:path-element/tet:type/tet:label/tet:label-hop /tet:te-label/tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:tunnel-termination-point /tet:local-link-connectivities /tet:local-link-connectivity/tet:path-properties /tet:path-route-objects/tet:path-route-object/tet:type /tet:label/tet:label-hop/tet:te-label/tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nt:link/tet:te /tet:te-link-attributes/tet:label-restrictions /tet:label-restriction/tet:label-start/tet:te-label /tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nt:link/tet:te /tet:te-link-attributes/tet:label-restrictions /tet:label-restriction/tet:label-end/tet:te-label /tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nt:link/tet:te /tet:te-link-attributes/tet:underlay/tet:primary-path /tet:path-element/tet:type/tet:label/tet:label-hop /tet:te-label/tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nt:link/tet:te /tet:te-link-attributes/tet:underlay/tet:backup-path /tet:path-element/tet:type/tet:label/tet:label-hop /tet:te-label/tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nt:link/tet:te /tet:information-source-entry/tet:label-restrictions /tet:label-restriction/tet:label-start/tet:te-label /tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nt:link/tet:te /tet:information-source-entry/tet:label-restrictions /tet:label-restriction/tet:label-end/tet:te-label /tet:technology: +--:(example) +--ro example +--ro label-1?uint32 ]]></artwork> </figure>uint32]]></sourcecode> <t> The example YANG moduleto implementthat implements the above example topologycan be seenis provided inAppendix C.</t><xref target="append-c"/>.</t> </section> <sectiontitle="TEanchor="sect-7" numbered="true" toc="default"> <name>TE Topology YANGModule" anchor="sect-7"><t>Module</name> <t> This module references[<xref target="RFC1195"/>], [<xref target="RFC3209"/>], [<xref target="RFC3272"/>], [<xref target="RFC3471"/>], [<xref target="RFC3630"/>], [<xref target="RFC3785"/>], [<xref target="RFC4201"/>], [<xref target="RFC4202"/>], [<xref target="RFC4203"/>], [<xref target="RFC4206"/>], [<xref target="RFC4872"/>], [<xref target="RFC5152"/>], [<xref target="RFC5212"/>], [<xref target="RFC5305"/>], [<xref target="RFC5316"/>], [<xref target="RFC5329"/>], [<xref target="RFC5392"/>], [<xref target="RFC6001"/>], [<xref target="RFC6241"/>], [<xref target="RFC6991"/>], [<xref target="RFC7308"/>], [<xref target="RFC7471"/>], [<xref target="RFC7579"/>], [<xref target="RFC7752"/>], [<xref target="RFC8345"/>], and [<xref target="I-D.ietf-teas-yang-te-types"/>].</t> <figure><artwork><![CDATA[ <CODE BEGINS> file "ietf-te-topology@2019-02-07.yang"<xref target="RFC1195" format="default"/>, <xref target="RFC3209" format="default"/>, <xref target="RFC3272" format="default"/>, <xref target="RFC3471" format="default"/>, <xref target="RFC3630" format="default"/>, <xref target="RFC3785" format="default"/>, <xref target="RFC4201" format="default"/>, <xref target="RFC4202" format="default"/>, <xref target="RFC4203" format="default"/>, <xref target="RFC4206" format="default"/>, <xref target="RFC4872" format="default"/>, <xref target="RFC5152" format="default"/>, <xref target="RFC5212" format="default"/>, <xref target="RFC5305" format="default"/>, <xref target="RFC5316" format="default"/>, <xref target="RFC5392" format="default"/>, <xref target="RFC6001" format="default"/>, <xref target="RFC6241" format="default"/>, <xref target="RFC6991" format="default"/>, <xref target="RFC7308" format="default"/>, <xref target="RFC7471" format="default"/>, <xref target="RFC7579" format="default"/>, <xref target="RFC7752" format="default"/>, <xref target="RFC8345" format="default"/>, and <xref target="RFC8776"/>.</t> <sourcecode name="ietf-te-topology@2020-06-29.yang" type="yang" markers="true"><![CDATA[ module ietf-te-topology { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-te-topology"; prefix"tet";tet; import ietf-yang-types { prefix"yang";yang; reference "RFC 6991: Common YANG Data Types"; } import ietf-inet-types { prefix"inet";inet; reference "RFC 6991: Common YANG Data Types"; } import ietf-te-types { prefix"te-types";te-types; reference"I-D.ietf-teas-yang-te-types: Traffic Engineering"RFC 8776: Common YANGTypes";Data Types for Traffic Engineering"; } import ietf-network { prefix"nw";nw; reference "RFC 8345: A YANG Data Model for Network Topologies"; } import ietf-network-topology { prefix"nt";nt; reference "RFC 8345: A YANG Data Model for Network Topologies"; } organization "IETF Traffic Engineering Architecture and Signaling (TEAS) Working Group"; contact "WG Web:<http://tools.ietf.org/wg/teas/><https://datatracker.ietf.org/wg/teas/> WG List: <mailto:teas@ietf.org> Editor: Xufeng Liu <mailto:xufeng.liu.ietf@gmail.com> Editor: Igor Bryskin<mailto:Igor.Bryskin@huawei.com><mailto:i_bryskin@yahoo.com> Editor: Vishnu Pavan Beeram <mailto:vbeeram@juniper.net> Editor: Tarek Saad <mailto:tsaad@juniper.net> Editor: Himanshu Shah <mailto:hshah@ciena.com> Editor: Oscar GonzalezDede Dios <mailto:oscar.gonzalezdedios@telefonica.com>"; description"TE"This YANG module defines a TE topology model forrepresentingrepresenting, retrieving, and manipulatingtechnology agnostictechnology-agnostic TETopologies.topologies. Copyright (c)20192020 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 Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents(http://trustee.ietf.org/license-info).(https://trustee.ietf.org/license-info). This version of this YANG module is part of RFCXXXX;8795; see the RFC itself for full legal notices."; revision"2019-02-07"2020-06-29 { description "Initialrevision";revision."; reference "RFCXXXX:8795: YANG Data Model forTETraffic Engineering (TE) Topologies";// RFC Ed.: replace XXXX with actual RFC number and remove // this note} /* * Features */ feature nsrlg { description "This feature indicates that the system supportsNSRLG (Not SharingNSRLGs (Non-Shared Risk LinkGroup).";Groups)."; } feature te-topology-hierarchy { description "This feature indicates that the system allows an underlay and/or overlay TE topology hierarchy."; } feature template { description "This feature indicates that the system supports template configuration."; } /* * Typedefs */ typedef geographic-coordinate-degree { type decimal64 { fraction-digits 8; } description "Decimal degree (DD) used to express latitude and longitude geographic coordinates."; } // geographic-coordinate-degree typedef te-info-source { type enumeration { enum"unknown"unknown { description "The source is unknown."; } enum"locally-configured"locally-configured { description "Configured entity."; } enum"ospfv2"ospfv2 { description "OSPFv2."; } enum"ospfv3"ospfv3 { description "OSPFv3."; } enum"isis"isis { description"ISIS.";"IS-IS."; } enum"bgp-ls"bgp-ls { description "BGP-LS."; reference "RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP"; } enum"system-processed"system-processed { description"System processed"System-processed entity."; } enum"other"other { description "Other source."; } } description"Describining"Describes the type of source that has provided the related information, and thesourcesource's credibility."; } // te-info-source /* * Groupings */ grouping connectivity-matrix-entry-path-attributes { description "Attributes of a connectivity matrix entry."; leaf is-allowed { type boolean; description"true"'true' - switching isallowed, falseallowed; 'false' - switching is disallowed."; } container underlay { if-featurete-topology-hierarchy;"te-topology-hierarchy"; description "Attributes of thete-linkTE link underlay."; reference "RFC 4206: Label Switched Paths (LSP) Hierarchy with Generalized Multi-Protocol Label Switching (GMPLS) Traffic Engineering (TE)"; uses te-link-underlay-attributes; }// underlayuses te-types:generic-path-constraints; uses te-types:generic-path-optimization; uses te-types:generic-path-properties; } // connectivity-matrix-entry-path-attributes grouping geolocation-container { description"A container containing"Contains a GPS location."; containergeolocation{geolocation { config false; description"A container containing"Contains a GPS location."; leaf altitude { type int64; unitsmillimeter;"millimeters"; description "Distance abovethesea level."; } leaf latitude { type geographic-coordinate-degree { range "-90..90"; } description "Relative position north or south on the Earth's surface."; } leaf longitude { type geographic-coordinate-degree { range "-180..180"; } description "Angular distance east or west on the Earth's surface."; } } //gps-locationgeolocation } // geolocation-container grouping information-source-state-attributes { description "The attributes identifying the source that has provided the related information, and thesourcesource's credibility."; leaf credibility-preference { type uint16; description "The preference valueto calculatefor calculating thetraffic engineeringTraffic Engineering database credibility value used for tie-break selection between different information-source values.HigherA higher value ismorepreferable."; } leaf logical-network-element { type string; description "When applicable, this is the name of a logical network element from which the information is learned."; }// logical-network-elementleaf network-instance { type string; description "When applicable, this is the name of anetwork-instancenetwork instance from which the information is learned."; }// network-instance} // information-source-state-attributes grouping information-source-per-link-attributes { description"Per node"Per-node container of the attributes identifying the source that has provided the related information, and thesourcesource's credibility."; leaf information-source { type te-info-source; config false; description "Indicates the type oftheinformation source."; } leaf information-source-instance { type string; config false; description "The name indicating the instance of the information source."; } container information-source-state { config false; description"The container contains"Contains state attributes related to the information source."; uses information-source-state-attributes; container topology { description "When the information is processed by the system, the attributes in this container indicate which topology is used toprocess togenerate the result information."; uses nt:link-ref; }// topology}// information-source-state} // information-source-per-link-attributes grouping information-source-per-node-attributes { description"Per node"Per-node container of the attributes identifying the source that has provided the related information, and thesourcesource's credibility."; leaf information-source { type te-info-source; config false; description "Indicates the type oftheinformation source."; } leaf information-source-instance { type string; config false; description "The name indicating the instance of the information source."; } container information-source-state { config false; description"The container contains"Contains state attributes related to the information source."; uses information-source-state-attributes; container topology { description "When the information is processed by the system, the attributes in this container indicate which topology is used toprocess togenerate the result information."; uses nw:node-ref; }// topology}// information-source-state} // information-source-per-node-attributes grouping interface-switching-capability-list { description "List of Interface SwitchingCapabilitiesCapability Descriptors(ISCD)";(ISCDs)."; list interface-switching-capability { key "switching-capability encoding"; description "List ofInterface Switching Capabilities Descriptors (ISCD)ISCDs for this link."; reference "RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS) Signaling FunctionalDescription.Description RFC 4203: OSPF Extensions in Support of Generalized Multi-Protocol Label Switching(GMPLS).";(GMPLS)"; leaf switching-capability { type identityref { base te-types:switching-capabilities; } description "SwitchingCapabilitycapability for this interface."; } leaf encoding { type identityref { base te-types:lsp-encoding-types; } description "Encoding supported by this interface."; } uses te-link-iscd-attributes; } // interface-switching-capability } // interface-switching-capability-list grouping statistics-per-link { description "Statistics attributes per TE link."; leaf discontinuity-time { type yang:date-and-time; description "The timeonof the most recent occasion at which any one or more of this interface's counters suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this node contains the time the local management subsystem re-initialized itself."; } /* Administrative attributes */ leaf disables { type yang:counter32; description "Number of times that a link was disabled."; } leaf enables { type yang:counter32; description "Number of times that a link was enabled."; } leaf maintenance-clears { type yang:counter32; description "Number of times that a link wasputtaken out of maintenance."; } leaf maintenance-sets { type yang:counter32; description "Number of times that a link was put in maintenance."; } leaf modifies { type yang:counter32; description "Number of times that a link was modified."; } /* Operational attributes */ leaf downs { type yang:counter32; description "Number of times that a link was set to an operationaldown.";state of 'down'."; } leaf ups { type yang:counter32; description "Number of times that a link was set to an operationalup.";state of 'up'."; } /* Recovery attributes */ leaf fault-clears { type yang:counter32; description "Number of times that a link experiencedfault cleara fault-clear event."; } leaf fault-detects { type yang:counter32; description "Number of times that a link experienced fault detection."; } leaf protection-switches { type yang:counter32; description "Number of times that a link experienced protection switchover."; } leaf protection-reverts { type yang:counter32; description "Number of times that a link experienced protection reversion."; } leaf restoration-failures { type yang:counter32; description "Number of times that a link experienced restoration failure."; } leaf restoration-starts { type yang:counter32; description "Number of times that a link experienced restoration start."; } leaf restoration-successes { type yang:counter32; description "Number of times that a link experienced restoration success."; } leaf restoration-reversion-failures { type yang:counter32; description "Number of times that a link experienced restoration reversion failure."; } leaf restoration-reversion-starts { type yang:counter32; description "Number of times that a link experienced restoration reversion start."; } leaf restoration-reversion-successes { type yang:counter32; description "Number of times that a link experienced restoration reversion success."; } } // statistics-per-link grouping statistics-per-node { description "Statistics attributes per TE node."; leaf discontinuity-time { type yang:date-and-time; description "The timeonof the most recent occasion at which any one or more of this interface's counters suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this node contains the time the local management subsystem re-initialized itself."; } container node { description"Containing"Contains statistics attributes at the TE nodelevel statistics attributes.";level."; leaf disables { type yang:counter32; description "Number of times that a node was disabled."; } leaf enables { type yang:counter32; description "Number of times that a node was enabled."; } leaf maintenance-sets { type yang:counter32; description "Number of times that a node was put in maintenance."; } leaf maintenance-clears { type yang:counter32; description "Number of times that a node wasputtaken out of maintenance."; } leaf modifies { type yang:counter32; description "Number of times that a node was modified."; } } // node container connectivity-matrix-entry { description"Containing"Contains statistics attributes at the level of a connectivity matrixentry level statistics attributes.";entry."; leaf creates { type yang:counter32; description "Number of times that a connectivity matrix entry was created."; reference "RFC6241.6241: Network Configuration Protocol (NETCONF), Section7.2 for7.2, 'create'operation. ";operation"; } leaf deletes { type yang:counter32; description "Number of times that a connectivity matrix entry was deleted."; reference "RFC6241.6241: Network Configuration Protocol (NETCONF), Section7.2 for7.2, 'delete'operation. ";operation"; } leaf disables { type yang:counter32; description "Number of times that a connectivity matrix entry was disabled."; } leaf enables { type yang:counter32; description "Number of times that a connectivity matrix entry was enabled."; } leaf modifies { type yang:counter32; description "Number of times that a connectivity matrix entry was modified."; } } // connectivity-matrix-entry } // statistics-per-node grouping statistics-per-ttp { description "Statistics attributes per TE TTP (Tunnel Termination Point)."; leaf discontinuity-time { type yang:date-and-time; description "The timeonof the most recent occasion at which any one or more of this interface's counters suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this node contains the time the local management subsystem re-initialized itself."; } container tunnel-termination-point { description"Containing"Contains statistics attributes at the TE TTP(Tunnel Termination Point) level statistics attributes.";level."; /* Administrative attributes */ leaf disables { type yang:counter32; description "Number of times that a TTP was disabled."; } leaf enables { type yang:counter32; description "Number of times that a TTP was enabled."; } leaf maintenance-clears { type yang:counter32; description "Number of times that a TTP wasputtaken out of maintenance."; } leaf maintenance-sets { type yang:counter32; description "Number of times that a TTP was put in maintenance."; } leaf modifies { type yang:counter32; description "Number of times that a TTP was modified."; } /* Operational attributes */ leaf downs { type yang:counter32; description "Number of times that a TTP was set to an operationaldown.";state of 'down'."; } leaf ups { type yang:counter32; description "Number of times that a TTP was set to an operationalup.";state of 'up'."; } leaf in-service-clears { type yang:counter32; description "Number of times that a TTP was taken out of service (TE tunnel was released)."; } leaf in-service-sets { type yang:counter32; description "Number of times that a TTP was put in service by a TE tunnel (TE tunnel was set up)."; } } // tunnel-termination-point container local-link-connectivity { description"Containing"Contains statistics attributes at the TE LLCL (Local Link Connectivity List)level statistics attributes.";level."; leaf creates { type yang:counter32; description "Number of times that an LLCL entry was created."; reference "RFC6241.6241: Network Configuration Protocol (NETCONF), Section7.2 for7.2, 'create'operation.";operation"; } leaf deletes { type yang:counter32; description "Number of times that an LLCL entry was deleted."; reference "RFC6241.6241: Network Configuration Protocol (NETCONF), Section7.2 for7.2, 'delete'operation.";operation"; } leaf disables { type yang:counter32; description "Number of times that an LLCL entry was disabled."; } leaf enables { type yang:counter32; description "Number of times that an LLCL entry was enabled."; } leaf modifies { type yang:counter32; description "Number of times that an LLCL entry was modified."; } } // local-link-connectivity } // statistics-per-ttp grouping te-link-augment { description "Augmentation for a TE link."; uses te-link-config; uses te-link-state-derived; container statistics { config false; description "Statistics data."; uses statistics-per-link; }// statistics} // te-link-augment grouping te-link-config { description "TE link configuration grouping."; choice bundle-stack-level { description "The TE link can be partitioned into bundledlinks,links or component links."; case bundle { container bundled-links { description "A set of bundled links."; reference "RFC 4201: Link Bundling in MPLS Traffic Engineering(TE).";(TE)"; list bundled-link { key "sequence"; description"Specify"Specifies a bundled interface that is further partitioned."; leaf sequence { type uint32; description"Identify"Identifies the sequence in the bundle."; } }// list bundled-link} } case component { container component-links { description "A set of componentlinks";links."; list component-link { key "sequence"; description"Specify"Specifies a component interface that is sufficient to unambiguously identify the appropriateresources";resources."; leaf sequence { type uint32; description"Identify"Identifies the sequence in the bundle."; } leaf src-interface-ref { type string; description "Reference to a component link interface on the source node."; } leaf des-interface-ref { type string; description "Reference to a component link interface on thedestinatioindestination node."; } } } } } // bundle-stack-level leaf-list te-link-template { if-featuretemplate;"template"; type leafref { path "../../../../te/templates/link-template/name"; } description "The reference to a TE link template."; } uses te-link-config-attributes; } // te-link-config grouping te-link-config-attributes { description "Link configuration attributes in a TE topology."; container te-link-attributes { description "Link attributes in a TE topology."; leaf access-type { type te-types:te-link-access-type; description "Link access type, which can be point-to-point or multi-access."; } container external-domain { description "For an inter-domain link,specifyspecifies the attributes of the remote end of the link, to facilitate thesignallingsignaling at the local end."; uses nw:network-ref; leaf remote-te-node-id { type te-types:te-node-id; description "Remote TE node identifier, used together withremote-te-link-id'remote-te-link-tp-id' to identify the remotelink termination pointLink Termination Point (LTP) in a different domain."; } leaf remote-te-link-tp-id { type te-types:te-tp-id; description "Remote TElink termination pointLTP identifier, used together withremote-te-node-id'remote-te-node-id' to identify the remotelink termination pointLTP in a different domain."; } } leaf is-abstract { type empty; description "Present if the link is abstract."; } leaf name { type string; description "LinkName.";name."; } container underlay { if-featurete-topology-hierarchy;"te-topology-hierarchy"; description "Attributes of thete-linkTE link underlay."; reference "RFC 4206: Label Switched Paths (LSP) Hierarchy with Generalized Multi-Protocol Label Switching (GMPLS) Traffic Engineering (TE)"; uses te-link-underlay-attributes; }// underlayleaf admin-status { type te-types:te-admin-status; description "The administrative state of the link."; } uses te-link-info-attributes; } // te-link-attributes } // te-link-config-attributes grouping te-link-info-attributes { description "Advertised TE information attributes."; leaf link-index { type uint64; description "The link identifier. If OSPF is used, this object represents an ospfLsdbID. If IS-IS is used, this object represents an isisLSPID. If a locally configured link is used, this object represents a unique value, which is locally defined in a router."; } leaf administrative-group { type te-types:admin-groups; description "Administrative group or color of the link. This attribute covers both administrativegroupgroups (defined inRFC 3630, RFC 5305RFCs 3630 andRFC 5329),5305) andextended administrative groupExtended Administrative Groups (defined in RFC 7308)."; reference "RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2 RFC 5305: IS-IS Extensions for Traffic Engineering RFC 7308: Extended Administrative Groups in MPLS Traffic Engineering (MPLS-TE)"; } uses interface-switching-capability-list; uses te-types:label-set-info; leaf link-protection-type { type identityref { base te-types:link-protection-type; } description "Link Protection Type desired for this link."; reference "RFC 4202: Routing Extensions in Support of Generalized Multi-Protocol Label Switching(GMPLS).";(GMPLS)"; } container max-link-bandwidth { uses te-types:te-bandwidth; description "Maximum bandwidth that can be seen on this link in this direction. Units are in bytes per second."; reference "RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version2.2 RFC 5305: IS-IS Extensions for TrafficEngineering.";Engineering"; } container max-resv-link-bandwidth { uses te-types:te-bandwidth; description "Maximum amount of bandwidth that can be reserved in this direction in this link. Units are in bytes per second."; reference "RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version2.2 RFC 5305: IS-IS Extensions for TrafficEngineering.";Engineering"; } list unreserved-bandwidth { key "priority"; max-elements"8";8; description "Unreserved bandwidth for0-7prioritylevels.levels 0-7. Units are in bytes per second."; reference "RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version2.2 RFC 5305: IS-IS Extensions for TrafficEngineering.";Engineering"; leaf priority { type uint8 { range "0..7"; } description "Priority."; } uses te-types:te-bandwidth; } leaf te-default-metric { type uint32; description "TrafficengineeringEngineering metric."; reference "RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version2.2 RFC 5305: IS-IS Extensions for TrafficEngineering.";Engineering"; } leaf te-delay-metric { type uint32; description "TrafficengineeringEngineering delay metric."; reference "RFC 7471: OSPF Traffic Engineering (TE) MetricExtensions.";Extensions"; } leaf te-igp-metric { type uint32; description "IGP metric used fortraffic engineering.";Traffic Engineering."; reference "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric as aSecondsecond MPLS Traffic Engineering (TE)Metric.";Metric"; } container te-srlgs { description"Containing"Contains a list ofSLRGs.";SRLGs."; leaf-list value { type te-types:srlg; description "SRLG value."; reference "RFC 4202: Routing Extensions in Support of Generalized Multi-Protocol Label Switching(GMPLS).";(GMPLS)"; } } container te-nsrlgs { if-featurensrlg;"nsrlg"; description"Containing"Contains a list of NSRLGs(Not Sharing(Non-Shared Risk Link Groups). When an abstract TE link is configured, this list specifies the request that underlay TE paths need to be mutually disjoint with other TE links in the same groups."; leaf-list id { type uint32; description "NSRLG ID, uniquely configured within a topology."; reference "RFC 4872: RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery"; } } } // te-link-info-attributes grouping te-link-iscd-attributes { description "TE link ISCD(Interface Switching Capability Descriptor)attributes."; reference"Sec 1.4, RFC"RFC 4203: OSPF Extensions in Support of Generalized Multi-Protocol Label Switching(GMPLS).(GMPLS), Section1.4.";1.4"; list max-lsp-bandwidth { key "priority"; max-elements"8";8; description "MaximumLSP BandwidthLabel Switched Path (LSP) bandwidth at priorities 0-7."; leaf priority { type uint8 { range "0..7"; } description "Priority."; } uses te-types:te-bandwidth; } } // te-link-iscd-attributes grouping te-link-state-derived { description "Link state attributes in a TE topology."; leaf oper-status { type te-types:te-oper-status; config false; description "The current operational state of the link."; } leaf is-transitional { type empty; config false; description "Present if the link istransitional,transitional; used as an alternative approach in lieu ofinter-layer-lock-id'inter-layer-lock-id' for path computation in a TE topology covering multiple layers or multiple regions."; reference "RFC 5212: Requirements for GMPLS-Based Multi-Region and Multi-Layer Networks(MRN/MLN).(MRN/MLN) RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks(MLN/MRN).";(MLN/MRN)"; } uses information-source-per-link-attributes; list information-source-entry { key "information-source information-source-instance"; config false; description "A list of information sources learned, including theonesource that is used."; uses information-source-per-link-attributes; uses te-link-info-attributes; } container recovery { config false; description "Status of the recovery process."; leaf restoration-status { type te-types:te-recovery-status; description "Restoration status."; } leaf protection-status { type te-types:te-recovery-status; description "Protection status."; } } container underlay { if-featurete-topology-hierarchy;"te-topology-hierarchy"; config false; description "State attributes forte-linkthe TE link underlay."; leaf dynamic { type boolean; description"true"'true' if the underlay is dynamically created."; } leaf committed { type boolean; description"true"'true' if the underlay is committed."; } } } // te-link-state-derived grouping te-link-underlay-attributes { description "Attributes forte-linkthe TE link underlay."; reference "RFC 4206: Label Switched Paths (LSP) Hierarchy with Generalized Multi-Protocol Label Switching (GMPLS) Traffic Engineering (TE)"; leaf enabled { type boolean; description "'true' if the underlay is enabled. 'false' if the underlay is disabled."; } container primary-path { description "The service path on the underlay topology that supports this link."; uses nw:network-ref; list path-element { key "path-element-id"; description "A list of path elements describing the service path."; leaf path-element-id { type uint32; description "To identify the element in a path."; } uses te-path-element; } } // primary-path list backup-path { key "index"; description "A list of backup service paths on the underlay topology that protect the underlay primary path. If the primary path is not protected, the list contains zero elements. If the primary path is protected, the list contains one or more elements."; leaf index { type uint32; description "A sequence number to identify a backup path."; } uses nw:network-ref; list path-element { key "path-element-id"; description "A list of path elements describing the backup servicepath";path."; leaf path-element-id { type uint32; description "To identify the element in a path."; } uses te-path-element; } } //underlay-backup-pathbackup-path leaf protection-type { type identityref { base te-types:lsp-protection-type; } description "Underlay protection type desired for this link."; } container tunnel-termination-points { description "UnderlayTTP(Tunnel Termination Points)TTPs desired for this link."; leaf source { type binary; description "Sourcetunnel termination pointTTP identifier."; } leaf destination { type binary; description "Destinationtunnel termination pointTTP identifier."; } } container tunnels { description "Underlay TE tunnels supporting this TE link."; leaf sharing { type boolean; defaulttrue;"true"; description "'true' if the underlay tunnel can be shared with other TE links; 'false' if the underlay tunnel is dedicated to this TE link. This leaf is the default option for all TEtunnels,tunnels and may be overridden by theper TE tunnelper-TE-tunnel value."; } list tunnel { key "tunnel-name"; description "Zero,oneone, or more underlay TE tunnels that support this TE link."; leaf tunnel-name { type string; description "A tunnel name uniquely identifies an underlay TE tunnel, used together with thesource-node of this link. The detailed information of'source-node' value for thistunnel can be retrieved from the ietf-te model.";link."; reference "RFC3209";3209: RSVP-TE: Extensions to RSVP for LSP Tunnels"; } leaf sharing { type boolean; description "'true' if the underlay tunnel can be shared with other TE links; 'false' if the underlay tunnel is dedicated to this TE link."; } } // tunnel } // tunnels } // te-link-underlay-attributes grouping te-node-augment { description "Augmentation for a TE node."; uses te-node-config; uses te-node-state-derived; container statistics { config false; description "Statistics data."; uses statistics-per-node; }// statisticslist tunnel-termination-point { key "tunnel-tp-id"; description "A termination point can terminate a tunnel."; leaf tunnel-tp-id { type binary; description"Tunnel termination point"TTP identifier."; } uses te-node-tunnel-termination-point-config; leaf oper-status { type te-types:te-oper-status; config false; description "The current operational state of thetunnel termination point.";TTP."; } uses geolocation-container; container statistics { config false; description "Statistics data."; uses statistics-per-ttp; } //statistics // RelationsRelationship to othertunnel termination pointsTTPs list supporting-tunnel-termination-point { key "node-ref tunnel-tp-ref"; description "Identifies thetunnel termination points, thatTTPs on which thistunnel termination point is depending on.";TTP depends."; leaf node-ref { type inet:uri; description "This leaf identifies the node in which the supportingtunnel termination pointTTP is present. This node is either the supporting node or a node in an underlay topology."; } leaf tunnel-tp-ref { type binary; description "Reference to atunnel terminiation point, whichTTP that iseitherin either the supporting node or a node in an underlay topology."; } } // supporting-tunnel-termination-point } // tunnel-termination-point } // te-node-augment grouping te-node-config { description "TE node configuration grouping."; leaf-list te-node-template { if-featuretemplate;"template"; type leafref { path "../../../../te/templates/node-template/name"; } description "The reference to a TE node template."; } uses te-node-config-attributes; } // te-node-config grouping te-node-config-attributes { description "Configuration node attributes in a TE topology."; container te-node-attributes { description"Containing"Contains node attributes in a TE topology."; leaf admin-status { type te-types:te-admin-status; description "The administrative state of the link."; } uses te-node-connectivity-matrices; uses te-node-info-attributes; }// te-node-attributes} // te-node-config-attributes grouping te-node-config-attributes-template { description "Configuration node attributes for a template in a TE topology."; container te-node-attributes { description"Containing"Contains node attributes in a TE topology."; leaf admin-status { type te-types:te-admin-status; description "The administrative state of the link."; } uses te-node-info-attributes; }// te-node-attributes} // te-node-config-attributes-template grouping te-node-connectivity-matrices { description "Connectivity matrix on a TE node."; container connectivity-matrices { description"Containing"Contains a connectivity matrix on a TE node."; leaf number-of-entries { type uint16; description "The number of connectivity matrix entries. If this number is specified in the configuration request, the number is the requested number of entries, which may not all be listed in the list; if this number is reported in the state data, the number is the current number of operational entries."; } uses te-types:label-set-info; uses connectivity-matrix-entry-path-attributes; list connectivity-matrix { key "id"; description "Represents a node's switching limitations,i.e.i.e., limitations in the interconnecting network TE links across the node."; reference "RFC 7579: General Network Element Constraint Encoding for GMPLS-ControlledNetworks.";Networks"; leaf id { type uint32; description "Identifies theconnectivity-matrixconnectivity matrix entry."; } } // connectivity-matrix } // connectivity-matrices } // te-node-connectivity-matrices grouping te-node-connectivity-matrix-attributes { description "Termination point references of a connectivity matrix entry."; container from { description "Reference to a sourcelink termination point.";LTP."; leaf tp-ref { type leafref { path "../../../../../../nt:termination-point/nt:tp-id"; } description "Relative reference to a termination point."; } uses te-types:label-set-info; } container to { description "Reference to a destinationlink termination point.";LTP."; leaf tp-ref { type leafref { path "../../../../../../nt:termination-point/nt:tp-id"; } description "Relative reference to a termination point."; } uses te-types:label-set-info; } uses connectivity-matrix-entry-path-attributes; } // te-node-connectivity-matrix-attributes grouping te-node-info-attributes { description "Advertised TE information attributes."; leaf domain-id { type uint32; description "Identifies the domainthatto which this node belongs. This attribute is used to support inter-domain links."; reference "RFC 5152: A Per-Domain Path Computation Method for Establishing Inter-Domain Traffic Engineering (TE) Label Switched Paths(LSPs).(LSPs) RFC5392: OSPF5316: ISIS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS TrafficEngineering.Engineering RFC5316: ISIS5392: OSPF Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS TrafficEngineering.";Engineering"; } leaf is-abstract { type empty; description "Present if the node isabstract,abstract; not present if the node is actual."; } leaf name { type string; description "Node name."; } leaf-list signaling-address { type inet:ip-address; description"Node"The node's signaling address."; } container underlay-topology { if-featurete-topology-hierarchy;"te-topology-hierarchy"; description "When an abstract node encapsulates a topology, the attributes in this container point to said topology."; uses nw:network-ref; } } // te-node-info-attributes grouping te-node-state-derived { description "Node state attributes in a TE topology."; leaf oper-status { type te-types:te-oper-status; config false; description "The current operational state of the node."; } uses geolocation-container; leaf is-multi-access-dr { type empty; config false; description "The presence of this attribute indicates that this TE node is a pseudonode elected as a designated router."; reference "RFC3630: Traffic Engineering (TE) Extensions to OSPF Version 2. RFC1195: Use of OSI IS-IS for Routing in TCP/IP and DualEnvironments.";Environments RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2"; } uses information-source-per-node-attributes; list information-source-entry { key "information-source information-source-instance"; config false; description "A list of information sources learned, including theonesource that is used."; uses information-source-per-node-attributes; uses te-node-connectivity-matrices; uses te-node-info-attributes; } } // te-node-state-derived grouping te-node-tunnel-termination-point-config { description "Termination capability of atunnel termination pointTTP on a TE node."; uses te-node-tunnel-termination-point-config-attributes; container local-link-connectivities { description"Containing local link connectivity list"Contains an LLCL for atunnel termination pointTTP on a TE node."; leaf number-of-entries { type uint16; description "The number oflocal link connectivity listLLCL entries. If this number is specified in the configuration request, the number is the requested number of entries, which may not all be listed in the list; if this number is reported in the state data, the number is the current number of operational entries."; } uses te-types:label-set-info; uses connectivity-matrix-entry-path-attributes; }// local-link-connectivities} // te-node-tunnel-termination-point-config grouping te-node-tunnel-termination-point-config-attributes { description "Configuration attributes of atunnel termination pointTTP on a TE node."; leaf admin-status { type te-types:te-admin-status; description "The administrative state of thetunnel termination point.";TTP."; } leaf name { type string; description "A descriptive name for thetunnel termination point.";TTP."; } leaf switching-capability { type identityref { base te-types:switching-capabilities; } description "SwitchingCapabilitycapability for this interface."; } leaf encoding { type identityref { base te-types:lsp-encoding-types; } description "Encoding supported by this interface."; } leaf-list inter-layer-lock-id { type uint32; description"Inter layer"Inter-layer lock ID, used for path computation in a TE topology covering multiple layers or multiple regions."; reference "RFC 5212: Requirements for GMPLS-Based Multi-Region and Multi-Layer Networks(MRN/MLN).(MRN/MLN) RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks(MLN/MRN).";(MLN/MRN)"; } leaf protection-type { type identityref { base te-types:lsp-protection-type; } description "The protection type that thistunnel termination pointTTP is capable of."; } container client-layer-adaptation { description"Containing"Contains capability information to support aclient layer adaptionclient-layer adaptation in a multi-layer topology."; list switching-capability { key "switching-capability encoding"; description "List of supported switchingcapabilities";capabilities."; reference "RFC 4202: Routing Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS) RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks(MLN/MRN). RFC 4202: Routing Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS).";(MLN/MRN)"; leaf switching-capability { type identityref { base te-types:switching-capabilities; } description "SwitchingCapabilitycapability for theclient layer adaption.";client-layer adaptation."; } leaf encoding { type identityref { base te-types:lsp-encoding-types; } description "Encoding supported by theclient layer adaption.";client-layer adaptation."; } uses te-types:te-bandwidth; } } } // te-node-tunnel-termination-point-config-attributes grouping te-node-tunnel-termination-point-llc-list { description"Local link connectivity list"LLCL of atunnel termination pointTTP on a TE node."; list local-link-connectivity { key "link-tp-ref"; description "The termination capabilities betweentunnel-termination-pointthe TTP andlink termination-point. Thethe LTP. This capability information can be used to compute the tunnel path. The Interface Adjustment Capability Descriptors(IACD)(IACDs) (defined in RFC 6001) on eachlink-tpLTP can be derived from thislocal-link-connectivitylist."; reference "RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks(MLN/MRN).";(MLN/MRN)"; leaf link-tp-ref { type leafref { path "../../../../../nt:termination-point/nt:tp-id"; } description"Link termination point.";"LTP."; } uses te-types:label-set-info; uses connectivity-matrix-entry-path-attributes; }// local-link-connectivity} //te-node-tunnel-termination-point-configte-node-tunnel-termination-point-llc-list grouping te-path-element { description "A group of attributes defining an element in a TEpathpath, such as a TE node, TE link, TE atomicresourceresource, or label."; uses te-types:explicit-route-hop; } // te-path-element grouping te-termination-point-augment { description "Augmentation for a TE termination point."; leaf te-tp-id { type te-types:te-tp-id; description "An identifiertothat uniquelyidentifyidentifies a TE termination point."; } container te { must"../te-tp-id";'../te-tp-id'; presence "TEsupport.";support"; description "Indicates TE support."; uses te-termination-point-config; leaf oper-status { type te-types:te-oper-status; config false; description "The current operational state of thelink termination point.";LTP."; } uses geolocation-container; }// te} // te-termination-point-augment grouping te-termination-point-config { description "TE termination point configuration grouping."; leaf admin-status { type te-types:te-admin-status; description "The administrative state of thelink termination point.";LTP."; } leaf name { type string; description "A descriptive name for thelink termination point.";LTP."; } uses interface-switching-capability-list; leaf inter-domain-plug-id { type binary; description "Atopology-widenetwork-wide unique number that identifies on the network aconnectivity supportingconnection that supports a given inter-domain TE link. This is a more flexible alternative to specifyingremote-te-node-id'remote-te-node-id' andremote-te-link-tp-id'remote-te-link-tp-id' on a TElink,link when the provider either does not knowremote-te-node-id'remote-te-node-id' andremote-te-link-tp-id'remote-te-link-tp-id' orneedneeds to give the client the flexibility tomix-n-matchmix and match multiple topologies."; } leaf-list inter-layer-lock-id { type uint32; description"Inter layer"Inter-layer lock ID, used for path computation in a TE topology covering multiple layers or multiple regions."; reference "RFC 5212: Requirements for GMPLS-Based Multi-Region and Multi-Layer Networks(MRN/MLN).(MRN/MLN) RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks(MLN/MRN).";(MLN/MRN)"; } } // te-termination-point-config grouping te-topologies-augment { description "Augmentation for TE topologies."; container te { presence "TEsupport.";support"; description "Indicates TE support."; container templates { description "Configuration parameters for templates used for a TE topology."; list node-template { if-featuretemplate;"template"; key "name"; leaf name { type te-types:te-template-name; description "The name to identify a TE node template."; } description "The list of TE node templates used to define sharable and reusable TE node attributes."; uses template-attributes; uses te-node-config-attributes-template; } // node-template list link-template { if-featuretemplate;"template"; key "name"; leaf name { type te-types:te-template-name; description "The name to identify a TE link template."; } description "The list of TE link templates used to define sharable and reusable TE link attributes."; uses template-attributes; uses te-link-config-attributes; } // link-template } // templates } // te } // te-topologies-augment grouping te-topology-augment { description "Augmentation for a TE topology."; uses te-types:te-topology-identifier; container te { must"../te-topology-identifier/provider-id"'../te-topology-identifier/provider-id' +"' and../te-topology-identifier/client-id"../te-topology-identifier/client-id' +"' and../te-topology-identifier/topology-id";../te-topology-identifier/topology-id'; presence "TEsupport.";support"; description "Indicates TE support."; uses te-topology-config; uses geolocation-container; }// te} // te-topology-augment grouping te-topology-config { description "TE topology configuration grouping."; leaf name { type string; description "Name of the TE topology. This attribute is optional and can be specified by the operator to describe the TE topology, which can be useful whennetwork-id'network-id' (RFC 8345) is not descriptive and not modifiable because of being generated by the system."; reference "RFC 8345: A YANG Data Model for Network Topologies"; } leaf preference { type uint8 { range "1..255"; } description "Specifies a preference for this topology. A lower number indicates a higher preference."; } leaf optimization-criterion { type identityref { base te-types:objective-function-type; } description "Optimization criterion applied to this topology."; reference "RFC 3272: Overview and Principles of Internet TrafficEngineering.";Engineering"; } list nsrlg { if-featurensrlg;"nsrlg"; key "id"; description "List of NSRLGs(Not Sharing(Non-Shared Risk Link Groups)."; reference "RFC 4872: RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery"; leaf id { type uint32; description"Identify"Identifies the NSRLG entry."; } leaf disjointness { type te-types:te-path-disjointness; description "The type of resource disjointness."; } } // nsrlg } // te-topology-config grouping template-attributes { description "Common attributes for all templates."; leaf priority { type uint16; description "The preference valueto resolvefor resolving conflicts between different templates. When two or more templates specify values for one configuration attribute, the value from the template with the highest priority is used. A lower number indicates a higher priority. The highest priority is 0."; } leaf reference-change-policy { type enumeration { enum no-action { description "When an attribute changes in this template, the configuration node referring to this template does not take any action."; } enum not-allowed { description "When any configuration object has a reference to this template, changing this template is not allowed."; } enum cascade { description "When an attribute changes in this template, the configuration object referring to this template applies the new attribute value to the corresponding configuration."; } } description "This attribute specifies the action takentofor a configuration node that has a reference to this template."; } } // template-attributes /* * Data nodes */ augment "/nw:networks/nw:network/nw:network-types" { description"Introduce"Introduces a new network type for a TE topology."; container te-topology { presence "Indicates a TEtopology.";topology"; description "Its presence identifies the TE topology type."; } } augment "/nw:networks" { description "Augmentation parameters for TE topologies."; uses te-topologies-augment; } augment "/nw:networks/nw:network" { when"nw:network-types/tet:te-topology"'nw:network-types/tet:te-topology' { description "Augmentation parameters apply only for networks with a TE topology type."; } description "Configuration parameters for a TE topology."; uses te-topology-augment; } augment "/nw:networks/nw:network/nw:node" { when"../nw:network-types/tet:te-topology"'../nw:network-types/tet:te-topology' { description "Augmentation parameters apply only for networks with a TE topology type."; } description "Configuration parameters for TE at the node level."; leaf te-node-id { type te-types:te-node-id; description "The identifier of a node in the TE topology. A node is specific to a topology to which it belongs."; } container te { must"../te-node-id"'../te-node-id' { description"te-node-id"'te-node-id' is mandatory."; } must"count(../nw:supporting-node)<=1"'count(../nw:supporting-node)<=1' { description "For a node in a TE topology, there cannot be more than1one supporting node. If multiple nodes are abstracted, theunderlay-topology'underlay-topology' field is used."; } presence "TEsupport.";support"; description "Indicates TE support."; uses te-node-augment; }// te} augment "/nw:networks/nw:network/nt:link" { when"../nw:network-types/tet:te-topology"'../nw:network-types/tet:te-topology' { description "Augmentation parameters apply only for networks with a TE topology type."; } description "Configuration parameters for TE at the link level."; container te { must"count(../nt:supporting-link)<=1"'count(../nt:supporting-link)<=1' { description "For a link in a TE topology, there cannot be more than1one supporting link. If one or more link paths are abstracted, the underlay is used."; } presence "TEsupport.";support"; description "Indicates TE support."; uses te-link-augment; }// te} augment "/nw:networks/nw:network/nw:node/" + "nt:termination-point" { when"../../nw:network-types/tet:te-topology"'../../nw:network-types/tet:te-topology' { description "Augmentation parameters apply only for networks with a TE topology type."; } description "Configuration parameters for TE at the termination point level."; uses te-termination-point-augment; } augment "/nw:networks/nw:network/nt:link/te/bundle-stack-level/" + "bundle/bundled-links/bundled-link" { when"../../../../nw:network-types/tet:te-topology"'../../../../nw:network-types/tet:te-topology' { description "Augmentation parameters apply only for networks with a TE topology type."; } description"Augment"Augmentation for a TElinkbundled link."; leaf src-tp-ref { type leafref { path "../../../../../nw:node[nw:node-id = " + "current()/../../../../nt:source/" + "nt:source-node]/" + "nt:termination-point/nt:tp-id"; require-instance true; } description "Reference to another TE termination point on the same source node."; } leaf des-tp-ref { type leafref { path "../../../../../nw:node[nw:node-id = " + "current()/../../../../nt:destination/" + "nt:dest-node]/" + "nt:termination-point/nt:tp-id"; require-instance true; } description "Reference to another TE termination point on the same destination node."; } } augment "/nw:networks/nw:network/nw:node/te/" + "information-source-entry/connectivity-matrices/" + "connectivity-matrix" { when"../../../../../nw:network-types/tet:te-topology"'../../../../../nw:network-types/tet:te-topology' { description "Augmentation parameters apply only for networks with a TE topology type."; } description"Augment"Augmentation for the TE nodeconnectivity-matrix.";connectivity matrix."; uses te-node-connectivity-matrix-attributes; } augment "/nw:networks/nw:network/nw:node/te/te-node-attributes/" + "connectivity-matrices/connectivity-matrix" { when"../../../../../nw:network-types/tet:te-topology"'../../../../../nw:network-types/tet:te-topology' { description "Augmentation parameters apply only for networks with a TE topology type."; } description"Augment"Augmentation for the TE nodeconnectivity-matrix.";connectivity matrix."; uses te-node-connectivity-matrix-attributes; } augment "/nw:networks/nw:network/nw:node/te/" + "tunnel-termination-point/local-link-connectivities" { when"../../../../nw:network-types/tet:te-topology"'../../../../nw:network-types/tet:te-topology' { description "Augmentation parameters apply only for networks with a TE topology type."; } description"Augment"Augmentation for TE nodetunnel termination pointTTP LLCs (Local Link Connectivities)."; uses te-node-tunnel-termination-point-llc-list; }} <CODE ENDS> ]]></artwork> </figure>}]]></sourcecode> </section> <sectiontitle="Security Considerations" anchor="sect-8"><t>anchor="sect-8" numbered="true" toc="default"> <name>Security Considerations</name> <t> The YANG module specified in this document defines a schema for data that is designed to be accessed via network management protocols such as NETCONF <xreftarget="RFC6241"/>target="RFC6241" format="default"/> or RESTCONF <xreftarget="RFC8040"/>.target="RFC8040" format="default"/>. The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) <xreftarget="RFC6242"/>.target="RFC6242" format="default"/>. The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS <xreftarget="RFC8446"/>.</t>target="RFC8446" format="default"/>.</t> <t> The Network Configuration Access Control Model (NACM) <xreftarget="RFC8341"/>target="RFC8341" format="default"/> 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> There are a number of data nodes defined in this YANG module that are writable/creatable/deletable (i.e., config true, which is the default). These data nodes may be considered sensitive or vulnerable in some network environments. Write operations (e.g., edit-config) to these data nodes without proper protection can have a negative effect on network operations. These are the subtrees and data nodes and their sensitivity/vulnerability:</t><t><list style="symbols"><ul spacing="normal"> <li> <t>/nw:networks/nw:network/nw:network-types/tet:te-topology<vspace /></t> <t> This subtree specifies the TE topology type. Modifying the configurations canmakerender the TE topology type invalid. By making such modifications, a malicious attacker may disable the TE capabilities on the related networks and cause traffic to be disrupted or misrouted.</t> </li> <li> <t>/nw:networks/tet:te<vspace /></t> <t> This subtree specifies the TE node templates and TE link templates. Modifying the configurations in this subtree will change the related future TE configurations. By making such modifications, a malicious attacker may changetheTE capabilities scheduled at a futuretime, totime and cause traffic to be disrupted or misrouted.</t> </li> <li> <t>/nw:networks/nw:network<vspace /></t> <t> This subtree specifies the topology-wide configurations, including the TE topology ID and topology-wide policies. Modifying the configurations in this subtree can add, remove, or modify TE topologies. By adding a TE topology, a malicious attacker may create an unauthorized traffic network. By removing or modifying a TE topology, a malicious attacker may cause traffic to be disabled or misrouted in the specified TE topology. Such traffic changes may also affect the traffic in the connected TE topologies.</t> </li> <li> <t>/nw:networks/nw:network/nw:node<vspace /></t> <t> This subtree specifies the configurations for TE nodes. Modifying the configurations in this subtree can add, remove, or modify TE nodes. By adding a TE node, a malicious attacker may create an unauthorized traffic path. By removing or modifying a TE node, a malicious attacker may cause traffic to be disabled or misrouted in the specified TE node. Such traffic changes may also affect the traffic on the surrounding TE nodes and TE links in this TE topology and the connected TE topologies.</t> </li> <li> <t>/nw:networks/nw:network/nt:link/tet:te<vspace /></t> <t> This subtree specifies the configurations for TE links. Modifying the configurations in this subtree can add, remove, or modify TE links. By adding a TE link, a malicious attacker may create an unauthorized traffic path. By removing or modifying a TE link, a malicious attacker may cause traffic to be disabled or misrouted on the specified TE link. Such traffic changes may also affect the traffic on the surrounding TE nodes and TE links in this TE topology and the connected TE topologies.</t> </li> <li> <t>/nw:networks/nw:network/nw:node/nt:termination-point<vspace /></t> <t> This subtree specifies the configurations of TElink termination points.LTPs. Modifying the configurations in this subtree can add, remove, or modify TElink termination points.LTPs. By adding a TElink termination point,LTP, a malicious attacker may create an unauthorized traffic path. By removing or modifying a TElink termination point,LTP, a malicious attacker may cause traffic to be disabled or misrouted on the specified TElink termination point.LTP. Such traffic changes may also affect the traffic on the surrounding TE nodes and TE links in this TE topology and the connected TE topologies.</t></list> </t></li> </ul> <t> Some of the readable data nodes in this YANG module may be considered sensitive or vulnerable in some network environments. It is thus important to control read access (e.g., via get, get-config, or notification) to these data nodes. These are the subtrees and data nodes and their sensitivity/vulnerability:</t><t><list style="symbols"><ul spacing="normal"> <li> <t>/nw:networks/nw:network/nw:network-types/tet:te-topology<vspace /></t> <t> Unauthorized access to this subtree can disclose the TE topology type.</t> </li> <li> <t>/nw:networks/tet:te<vspace /></t> <t> Unauthorized access to this subtree can disclose the TE node templates and TE link templates.</t> </li> <li> <t>/nw:networks/nw:network<vspace /></t> <t> Unauthorized access to this subtree can disclose the topology-wide configurations, including the TE topology ID, the topology-wide policies, and the topology geolocation.</t> </li> <li> <t>/nw:networks/nw:network/nw:node<vspace /></t> <t> Unauthorized access to this subtree can disclose the operational state information of TE nodes.</t> </li> <li> <t>/nw:networks/nw:network/nt:link/tet:te<vspace /></t> <t> Unauthorized access to this subtree can disclose the operational state information of TE links.</t> </li> <li> <t>/nw:networks/nw:network/nw:node/nt:termination-point<vspace /></t> <t> Unauthorized access to this subtree can disclose the operational state information of TElink termination points.</t> </list> </t>LTPs.</t> </li> </ul> </section> <sectiontitle="IANA Considerations" anchor="sect-9"><t> This document registersanchor="sect-9" numbered="true" toc="default"> <name>IANA Considerations</name> <t> IANA has registered the following URIs in theIETF XML registry <xref target="RFC3688"/>. Following"ns" subregistry within theformat in"IETF XML Registry" <xreftarget="RFC3688"/>, the following registration is requested to be made.</t> <figure><artwork><![CDATA[ URI: urn:ietf:params:xml:ns:yang:ietf-te-topology Registrant Contact: The IESG. XML: N/A,target="RFC3688" format="default"/>. </t> <dl newline="false" spacing="compact"> <dt>URI:</dt><dd>urn:ietf:params:xml:ns:yang:ietf-te-topology</dd> <dt>Registrant Contact:</dt><dd>The IESG.</dd> <dt>XML:</dt><dd>N/A; the requested URI is an XMLnamespace. URI: urn:ietf:params:xml:ns:yang:ietf-te-topology-state Registrant Contact: The IESG. XML: N/A,namespace.</dd> </dl> <dl newline="false" spacing="compact"> <dt>URI:</dt><dd>urn:ietf:params:xml:ns:yang:ietf-te-topology-state</dd> <dt>Registrant Contact:</dt><dd>The IESG.</dd> <dt>XML:</dt><dd>N/A; the requested URI is an XMLnamespace. ]]></artwork> </figure>namespace.</dd> </dl> <t>This document registers aIANA has registered the following YANGmodulemodules in theYANG"YANG ModuleNames registryNames" subregistry <xreftarget="RFC7950"/>.</t> <figure><artwork><![CDATA[ name: ietf-te-topology namespace: urn:ietf:params:xml:ns:yang:ietf-te-topology prefix: tet reference: RFC XXXX name: ietf-te-topology-state namespace: urn:ietf:params:xml:ns:yang:ietf-te-topology-state prefix: tet-s reference: RFC XXXX ]]></artwork> </figure>target="RFC6020" format="default"/> within the "YANG Parameters" registry. </t> <dl newline="false" spacing="compact"> <dt>Name:</dt><dd>ietf-te-topology</dd> <dt>Namespace:</dt><dd>urn:ietf:params:xml:ns:yang:ietf-te-topology</dd> <dt>Prefix:</dt><dd>tet</dd> <dt>Reference:</dt><dd>RFC 8795</dd> </dl> <dl newline="false" spacing="compact"> <dt>Name:</dt><dd>ietf-te-topology-state</dd> <dt>Namespace:</dt><dd>urn:ietf:params:xml:ns:yang:ietf-te-topology-state</dd> <dt>Prefix:</dt><dd>tet-s</dd> <dt>Reference:</dt><dd>RFC 8795</dd> </dl> </section> </middle> <back><references title="Normative References"> &RFC2119; &RFC3688; &RFC3945; &RFC6241; &RFC6242; &RFC6991; &RFC7926; &RFC7950; &RFC8040; &RFC8174; &RFC8341; &RFC8342; &RFC8345; &RFC8446; &I-D.ietf-teas-yang-te-types;<displayreference target="I-D.ietf-teas-te-topo-and-tunnel-modeling" to="TEAS-TOPO"/> <references> <name>References</name> <references> <name>Normative References</name> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3688.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3945.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6020.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6241.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6242.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6991.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7926.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7950.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8040.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8341.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8342.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8345.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8446.xml"/> <!-- draft-ietf-teas-yang-te-types (RFC 8776) (PUB 6/10/2020) --> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8776.xml"/> </references><references title="Informative References"><references> <name>Informative References</name> <referenceanchor="G.709"><front>anchor="G.709" target="https://www.itu.int/rec/T-REC-G.709/"> <front> <title>Interfaces for the optical transport network</title> <seriesInfo name="ITU-T" value="Recommendation G.709"/> <author> <organization>ITU-T</organization> </author> <date month="June"year="2016"/>year="2020"/> </front><seriesInfo name="ITU-T" value="Recommendation G.709"/></reference> <referenceanchor="G.805"><front>anchor="G.805" target="https://www.itu.int/rec/T-REC-G.805/en"> <front> <title>Generic functional architecture of transport networks</title> <seriesInfo name="ITU-T" value="Recommendation G.805"/> <author> <organization>ITU-T</organization> </author> <date month="March" year="2000"/> </front><seriesInfo name="ITU-T" value="Recommendation G.805"/></reference> <referenceanchor="G.872"><front>anchor="G.872" target="https://www.itu.int/rec/T-REC-G.872/en"> <front> <title>Architecture of optical transport networks</title> <seriesInfo name="ITU-T" value="Recommendation G.872"/> <author> <organization>ITU-T</organization> </author> <datemonth="January" year="2017"/>month="December" year="2019"/> </front><seriesInfo name="ITU-T" value="Recommendation G.872"/></reference> <referenceanchor="G.8080"><front>anchor="G.8080" target="https://www.itu.int/rec/T-REC-G.8080/en"> <front> <title>Architecture for the automatically switched optical network</title> <seriesInfo name="ITU-T" value="Recommendation G.8080"/> <author> <organization>ITU-T</organization> </author> <date month="February" year="2012"/> </front> </reference> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.1195.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2702.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3209.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3272.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3471.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3630.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3785.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4201.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4202.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4203.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4206.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4872.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5152.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5212.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5305.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5316.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5392.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6001.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7308.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7471.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7579.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7752.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8340.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8639.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8641.xml"/> <!-- draft-liu-netmod-yang-schedule (Expired) --> <!-- Long way; surname for "Gonzalez de Dios" in repository is wrong. --> <reference anchor="YANG-CFG-SCHED" target="https://tools.ietf.org/html/draft-liu-netmod-yang-schedule-05"> <front> <title>A YANG Data Model for Configuration Scheduling</title> <author initials='X' surname='Liu' fullname='Xufeng Liu'> <organization /> </author> <author initials='I' surname='Bryskin' fullname='Igor Bryskin'> <organization /> </author> <author initials='V' surname='Beeram' fullname='Vishnu Beeram'> <organization /> </author> <author initials='T' surname='Saad' fullname='Tarek Saad'> <organization /> </author> <author initials='H' surname='Shah' fullname='Himanshu Shah'> <organization /> </author> <author initials='O' surname='Gonzalez de Dios' fullname='Oscar Gonzalez de Dios'> <organization /> </author> <date month='March' day='1' year='2018' /> </front> <seriesInfoname="ITU-T" value="Recommendation G.8080"/>name='Work in Progress, Internet-Draft,' value='draft-liu-netmod-yang-schedule-05' /> </reference> <!-- draft-ietf-ccamp-wson-yang (I-D Exists) --> <!-- Long way; surname for V. Lopez in repository file is different from how it's listed in the document itself. --> <reference anchor='YANG-WSON' target="https://tools.ietf.org/html/draft-ietf-ccamp-wson-yang-25"> <front> <title>A YANG Data Model for WSON (Wavelength Switched Optical Networks)</title> <author initials='H' surname='Zheng' fullname='Haomian Zheng'> <organization /> </author> <author initials='Y' surname='Lee' fullname='Young Lee'> <organization /> </author> <author initials='A' surname='Guo' fullname='Aihua Guo'> <organization /> </author> <author initials='V' surname='Lopez' fullname='Victor Lopez'> <organization /> </author> <author initials='D' surname='King' fullname='Daniel King'> <organization /> </author> <date month='May' day='19' year='2020' /> </front> <seriesInfo name='Work in Progress, Internet-Draft,' value='draft-ietf-ccamp-wson-yang-25' /> </reference> <!-- draft-ietf-ccamp-otn-topo-yang (I-D Exists) --> <!-- Long way; surname for "Gonzalez de Dios" in repository is wrong. --> <reference anchor='YANG-OTN' target="https://tools.ietf.org/html/draft-ietf-ccamp-otn-topo-yang-10"> <front> <title>A YANG Data Model for Optical Transport Network Topology</title> <author initials='H' surname='Zheng' fullname='Haomian Zheng'> <organization /> </author> <author initials='I' surname='Busi' fullname='Italo Busi'> <organization /> </author> <author initials='X' surname='Liu' fullname='Xufeng Liu'> <organization /> </author> <author initials='S' surname='Belotti' fullname='Sergio Belotti'> <organization /> </author> <author initials='O' surname='Gonzalez de Dios' fullname='Oscar Gonzalez de Dios'> <organization /> </author> <date month='March' day='9' year='2020' /> </front> <seriesInfo name='Work in Progress, Internet-Draft,' value='draft-ietf-ccamp-otn-topo-yang-10' /> </reference> <!-- draft-ietf-teas-yang-l3-te-topo (I-D Exists) --> <!-- Long way; surname for "Gonzalez de Dios" in repository is wrong. --> <reference anchor="YANG-L3" target="https://tools.ietf.org/html/draft-ietf-teas-yang-l3-te-topo-08"> <front> <title>YANG Data Model for Layer 3 TE Topologies</title> <author initials='X' surname='Liu' fullname='Xufeng Liu'> <organization /> </author> <author initials='I' surname='Bryskin' fullname='Igor Bryskin'> <organization /> </author> <author initials='V' surname='Beeram' fullname='Vishnu Beeram'> <organization /> </author> <author initials='T' surname='Saad' fullname='Tarek Saad'> <organization /> </author> <author initials='H' surname='Shah' fullname='Himanshu Shah'> <organization /> </author> <author initials='O' surname='Gonzalez de Dios' fullname='Oscar Gonzalez de Dios'> <organization /> </author> <date month='July' day='12' year='2020' /> </front> <seriesInfo name='Work in Progress, Internet-Draft,' value='draft-ietf-teas-yang-l3-te-topo-08' /> </reference>&RFC1195; &RFC2702; &RFC3209; &RFC3272; &RFC3471; &RFC3630; &RFC3785; &RFC4201; &RFC4202; &RFC4203; &RFC4206; &RFC4872; &RFC5152; &RFC5212; &RFC5305; &RFC5316; &RFC5329; &RFC5392; &RFC6001; &RFC7308; &RFC7471; &RFC7579; &RFC7752; &RFC8340; &I-D.ietf-netconf-subscribed-notifications; &I-D.ietf-netconf-yang-push; &I-D.liu-netmod-yang-schedule; &I-D.ietf-ccamp-wson-yang; &I-D.ietf-ccamp-otn-topo-yang; &I-D.ietf-teas-yang-l3-te-topo; &I-D.ietf-teas-te-topo-and-tunnel-modeling;<!-- draft-ietf-teas-te-topo-and-tunnel-modeling (I-D Exists) --> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ietf-teas-te-topo-and-tunnel-modeling-06.xml"/> </references> </references> <sectiontitle="Completeanchor="append-a" numbered="true" toc="default"> <name>Complete Model TreeStructure" anchor="append-a"><figure><artwork><![CDATA[Structure</name> <sourcecode name="" type="yangtree"><![CDATA[ module: ietf-te-topology augment /nw:networks/nw:network/nw:network-types: +--rw te-topology! augment /nw:networks: +--rw te! +--rw templates +--rw node-template* [name] {template}? | +--rw name | | te-types:te-template-name | +--rw priority? uint16 | +--rw reference-change-policy? enumeration | +--rw te-node-attributes | +--rw admin-status? te-types:te-admin-status | +--rw domain-id? uint32 | +--rw is-abstract? empty | +--rw name? string | +--rw signaling-address* inet:ip-address | +--rw underlay-topology {te-topology-hierarchy}? | +--rw network-ref? | -> /nw:networks/network/network-id +--rw link-template* [name] {template}? +--rw name | te-types:te-template-name +--rw priority? uint16 +--rw reference-change-policy? enumeration +--rw te-link-attributes +--rw access-type? | te-types:te-link-access-type +--rw external-domain | +--rw network-ref? | | -> /nw:networks/network/network-id | +--rw remote-te-node-id? te-types:te-node-id | +--rw remote-te-link-tp-id? te-types:te-tp-id +--rw is-abstract? empty +--rw name? string +--rw underlay {te-topology-hierarchy}? | +--rw enabled? boolean | +--rw primary-path | | +--rw network-ref? | | | -> /nw:networks/network/network-id | | +--rw path-element* [path-element-id] | | +--rw path-element-id uint32 | | +--rw (type)? | | +--:(numbered-node-hop) | | | +--rw numbered-node-hop | | | +--rw node-id te-node-id | | | +--rw hop-type? te-hop-type | | +--:(numbered-link-hop) | | | +--rw numbered-link-hop | | | +--rw link-tp-id te-tp-id | | | +--rw hop-type? te-hop-type | | | +--rw direction? | | | te-link-direction | | +--:(unnumbered-link-hop) | | | +--rw unnumbered-link-hop | | | +--rw link-tp-id te-tp-id | | | +--rw node-id te-node-id | | | +--rw hop-type? te-hop-type | | | +--rw direction? | | | te-link-direction | | +--:(as-number) | | | +--rw as-number-hop | | | +--rw as-number inet:as-number | | | +--rw hop-type? te-hop-type | | +--:(label) | | +--rw label-hop | | +--rw te-label | | +--rw (technology)? | | | +--:(generic) | | | +--rw generic? | | | rt- types:generalized-label | | +--rw direction? | | te-label-direction | +--rw backup-path* [index] | | +--rw index uint32 | | +--rw network-ref? | | | -> /nw:networks/network/network-id | | +--rw path-element* [path-element-id] | | +--rw path-element-id uint32 | | +--rw (type)? | | +--:(numbered-node-hop) | | | +--rw numbered-node-hop | | | +--rw node-id te-node-id | | | +--rw hop-type? te-hop-type | | +--:(numbered-link-hop) | | | +--rw numbered-link-hop | | | +--rw link-tp-id te-tp-id | | | +--rw hop-type? te-hop-type | | | +--rw direction? | | | te-link-direction | | +--:(unnumbered-link-hop) | | | +--rw unnumbered-link-hop | | | +--rw link-tp-id te-tp-id | | | +--rw node-id te-node-id | | | +--rw hop-type? te-hop-type | | | +--rw direction? | | | te-link-direction | | +--:(as-number) | | | +--rw as-number-hop | | | +--rw as-number inet:as-number | | | +--rw hop-type? te-hop-type | | +--:(label) | | +--rw label-hop | | +--rw te-label | | +--rw (technology)? | | | +--:(generic) | | | +--rw generic? | | | rt- types:generalized-label | | +--rw direction? | | te-label-direction | +--rw protection-type? identityref | +--rw tunnel-termination-points | | +--rw source? binary | | +--rw destination? binary | +--rw tunnels | +--rw sharing? boolean | +--rw tunnel* [tunnel-name] | +--rw tunnel-name string | +--rw sharing? boolean +--rw admin-status? | te-types:te-admin-status +--rw link-index? uint64 +--rw administrative-group? | te-types:admin-groups +--rw interface-switching-capability* | [switching-capability encoding] | +--rw switching-capability identityref | +--rw encoding identityref | +--rw max-lsp-bandwidth* [priority] | +--rw priority uint8 | +--rw te-bandwidth | +--rw (technology)? | +--:(generic) | +--rw generic? te-bandwidth +--rw label-restrictions | +--rw label-restriction* [index] | +--rw restriction? enumeration | +--rw index uint32 | +--rw label-start | | +--rw te-label | | +--rw (technology)? | | | +--:(generic) | | | +--rw generic? | | | rt-types:generalized-label | | +--rw direction? te-label-direction | +--rw label-end | | +--rw te-label | | +--rw (technology)? | | | +--:(generic) | | | +--rw generic? | | | rt-types:generalized-label | | +--rw direction? te-label-direction | +--rw label-step | | +--rw (technology)? | | +--:(generic) | | +--rw generic? int32 | +--rw range-bitmap? yang:hex-string +--rw link-protection-type? identityref +--rw max-link-bandwidth | +--rw te-bandwidth | +--rw (technology)? | +--:(generic) | +--rw generic? te-bandwidth +--rw max-resv-link-bandwidth | +--rw te-bandwidth | +--rw (technology)? | +--:(generic) | +--rw generic? te-bandwidth +--rw unreserved-bandwidth* [priority] | +--rw priority uint8 | +--rw te-bandwidth | +--rw (technology)? | +--:(generic) | +--rw generic? te-bandwidth +--rw te-default-metric? uint32 +--rw te-delay-metric? uint32 +--rw te-igp-metric? uint32 +--rw te-srlgs | +--rw value* te-types:srlg +--rw te-nsrlgs {nsrlg}? +--rw id* uint32 augment /nw:networks/nw:network: +--rw te-topology-identifier | +--rw provider-id? te-global-id | +--rw client-id? te-global-id | +--rw topology-id? te-topology-id +--rw te! +--rw name? string +--rw preference? uint8 +--rw optimization-criterion? identityref +--rw nsrlg* [id] {nsrlg}? | +--rw id uint32 | +--rw disjointness? te-types:te-path-disjointness +--ro geolocation +--ro altitude? int64 +--ro latitude? geographic-coordinate-degree +--ro longitude? geographic-coordinate-degree augment /nw:networks/nw:network/nw:node: +--rw te-node-id? te-types:te-node-id +--rw te! +--rw te-node-template* | -> ../../../../te/templates/node-template/name | {template}? +--rw te-node-attributes | +--rw admin-status? te-types:te-admin-status | +--rw connectivity-matrices | | +--rw number-of-entries? uint16 | | +--rw label-restrictions | | | +--rw label-restriction* [index] | | | +--rw restriction? enumeration | | | +--rw index uint32 | | | +--rw label-start | | | | +--rw te-label | | | | +--rw (technology)? | | | | | +--:(generic) | | | | | +--rw generic? | | | | | rt-types:generalized-label | | | | +--rw direction? te-label-direction | | | +--rw label-end | | | | +--rw te-label | | | | +--rw (technology)? | | | | | +--:(generic) | | | | | +--rw generic? | | | | | rt-types:generalized-label | | | | +--rw direction? te-label-direction | | | +--rw label-step | | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? int32 | | | +--rw range-bitmap? yang:hex-string | | +--rw is-allowed? boolean | | +--rw underlay {te-topology-hierarchy}? | | | +--rw enabled? boolean | | | +--rw primary-path | | | | +--rw network-ref? | | | | | -> /nw:networks/network/network-id | | | | +--rw path-element* [path-element-id] | | | | +--rw path-element-id uint32 | | | | +--rw (type)? | | | | +--:(numbered-node-hop) | | | | | +--rw numbered-node-hop | | | | | +--rw node-id te-node-id | | | | | +--rw hop-type? te-hop-type | | | | +--:(numbered-link-hop) | | | | | +--rw numbered-link-hop | | | | | +--rw link-tp-id te-tp-id | | | | | +--rw hop-type? te-hop-type | | | | | +--rw direction? te-link-direction | | | | +--:(unnumbered-link-hop) | | | | | +--rw unnumbered-link-hop | | | | | +--rw link-tp-id te-tp-id | | | | | +--rw node-id te-node-id | | | | | +--rw hop-type? te-hop-type | | | | | +--rw direction? te-link-direction | | | | +--:(as-number) | | | | | +--rw as-number-hop | | | | | +--rw as-number inet:as-number | | | | | +--rw hop-type? te-hop-type | | | | +--:(label) | | | | +--rw label-hop | | | | +--rw te-label | | | | +--rw (technology)? | | | | | +--:(generic) | | | | | +--rw generic? | | | | | rt-types:generalized- label | | | | +--rw direction? | | | | te-label-direction | | | +--rw backup-path* [index] | | | | +--rw index uint32 | | | | +--rw network-ref? | | | | | -> /nw:networks/network/network-id | | | | +--rw path-element* [path-element-id] | | | | +--rw path-element-id uint32 | | | | +--rw (type)? | | | | +--:(numbered-node-hop) | | | | | +--rw numbered-node-hop | | | | | +--rw node-id te-node-id | | | | | +--rw hop-type? te-hop-type | | | | +--:(numbered-link-hop) | | | | | +--rw numbered-link-hop | | | | | +--rw link-tp-id te-tp-id | | | | | +--rw hop-type? te-hop-type | | | | | +--rw direction? te-link-direction | | | | +--:(unnumbered-link-hop) | | | | | +--rw unnumbered-link-hop | | | | | +--rw link-tp-id te-tp-id | | | | | +--rw node-id te-node-id | | | | | +--rw hop-type? te-hop-type | | | | | +--rw direction? te-link-direction | | | | +--:(as-number) | | | | | +--rw as-number-hop | | | | | +--rw as-number inet:as-number | | | | | +--rw hop-type? te-hop-type | | | | +--:(label) | | | | +--rw label-hop | | | | +--rw te-label | | | | +--rw (technology)? | | | | | +--:(generic) | | | | | +--rw generic? | | | | | rt-types:generalized- label | | | | +--rw direction? | | | | te-label-direction | | | +--rw protection-type? identityref | | | +--rw tunnel-termination-points | | | | +--rw source? binary | | | | +--rw destination? binary | | | +--rw tunnels | | | +--rw sharing? boolean | | | +--rw tunnel* [tunnel-name] | | | +--rw tunnel-name string | | | +--rw sharing? boolean | | +--rw path-constraints | | | +--rw te-bandwidth | | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? te-bandwidth | | | +--rw link-protection? identityref | | | +--rw setup-priority? uint8 | | | +--rw hold-priority? uint8 | | | +--rw signaling-type? identityref | | | +--rw path-metric-bounds | | | | +--rw path-metric-bound* [metric-type] | | | | +--rw metric-type identityref | | | | +--rw upper-bound? uint64 | | | +--rw path-affinities-values | | | | +--rw path-affinities-value* [usage] | | | | +--rw usage identityref | | | | +--rw value? admin-groups | | | +--rw path-affinity-names | | | | +--rw path-affinity-name* [usage] | | | | +--rw usage identityref | | | | +--rw affinity-name* [name] | | | | +--rw name string | | | +--rw path-srlgs-lists | | | | +--rw path-srlgs-list* [usage] | | | | +--rw usage identityref | | | | +--rw values* srlg | | | +--rw path-srlgs-names | | | | +--rw path-srlgs-name* [usage] | | | | +--rw usage identityref | | | | +--rw names* string | | | +--rw disjointness? te-path-disjointness | | +--rw optimizations | | | +--rw (algorithm)? | | | +--:(metric) {path-optimization-metric}? | | | | +--rw optimization-metric* [metric-type] | | | | | +--rw metric-type | | | | | | identityref | | | | | +--rw weight? | | | | | | uint8 | | | | | +--rw explicit-route-exclude-objects | | | | | | +--rw route-object-exclude-object* | | | | | | [index] | | | | | | +--rw index | | | | | | | uint32 | | | | | | +--rw (type)? | | | | | | +--:(numbered-node-hop) | | | | | | | +--rw numbered-node-hop | | | | | | | +--rw node-id te-node-id | | | | | | | +--rw hop-type? te-hop-type | | | | | | +--:(numbered-link-hop) | | | | | | | +--rw numbered-link-hop | | | | | | | +--rw link-tp-id te-tp-id | | | | | | | +--rw hop-type? | | | | | | | | te-hop-type | | | | | | | +--rw direction? | | | | | | | te-link-direction | | | | | | +--:(unnumbered-link-hop) | | | | | | | +--rw unnumbered-link-hop | | | | | | | +--rw link-tp-id te-tp-id | | | | | | | +--rw node-id | | | | | | | | te-node-id | | | | | | | +--rw hop-type? | | | | | | | | te-hop-type | | | | | | | +--rw direction? | | | | | | | te-link-direction | | | | | | +--:(as-number) | | | | | | | +--rw as-number-hop | | | | | | | +--rw as-number | | | | | | | | inet:as-number | | | | | | | +--rw hop-type? | | | | | | | te-hop-type | | | | | | +--:(label) | | | | | | | +--rw label-hop | | | | | | | +--rw te-label | | | | | | | +--rw (technology)? | | | | | | | | +--:(generic) | | | | | | | | +--rw generic? | | | | | | | | rt- types:generalized-label | | | | | | | +--rw direction? | | | | | | | te-label-direction | | | | | | +--:(srlg) | | | | | | +--rw srlg | | | | | | +--rw srlg? uint32 | | | | | +--rw explicit-route-include-objects | | | | | +--rw route-object-include-object* | | | | | [index] | | | | | +--rw index | | | | | | uint32 | | | | | +--rw (type)? | | | | | +--:(numbered-node-hop) | | | | | | +--rw numbered-node-hop | | | | | | +--rw node-id te-node-id | | | | | | +--rw hop-type? te-hop-type | | | | | +--:(numbered-link-hop) | | | | | | +--rw numbered-link-hop | | | | | | +--rw link-tp-id te-tp-id | | | | | | +--rw hop-type? | | | | | | | te-hop-type | | | | | | +--rw direction? | | | | | | te-link-direction | | | | | +--:(unnumbered-link-hop) | | | | | | +--rw unnumbered-link-hop | | | | | | +--rw link-tp-id te-tp-id | | | | | | +--rw node-id | | | | | | | te-node-id | | | | | | +--rw hop-type? | | | | | | | te-hop-type | | | | | | +--rw direction? | | | | | | te-link-direction | | | | | +--:(as-number) | | | | | | +--rw as-number-hop | | | | | | +--rw as-number | | | | | | | inet:as-number | | | | | | +--rw hop-type? | | | | | | te-hop-type | | | | | +--:(label) | | | | | +--rw label-hop | | | | | +--rw te-label | | | | | +--rw (technology)? | | | | | | +--:(generic) | | | | | | +--rw generic? | | | | | | rt- types:generalized-label | | | | | +--rw direction? | | | | | te-label-direction | | | | +--rw tiebreakers | | | | +--rw tiebreaker* [tiebreaker-type] | | | | +--rw tiebreaker-type identityref | | | +--:(objective-function) | | | {path-optimization-objective-function}? | | | +--rw objective-function | | | +--rw objective-function-type? identityref | | +--ro path-properties | | | +--ro path-metric* [metric-type] | | | | +--ro metric-type identityref | | | | +--ro accumulative-value? uint64 | | | +--ro path-affinities-values | | | | +--ro path-affinities-value* [usage] | | | | +--ro usage identityref | | | | +--ro value? admin-groups | | | +--ro path-affinity-names | | | | +--ro path-affinity-name* [usage] | | | | +--ro usage identityref | | | | +--ro affinity-name* [name] | | | | +--ro name string | | | +--ro path-srlgs-lists | | | | +--ro path-srlgs-list* [usage] | | | | +--ro usage identityref | | | | +--ro values* srlg | | | +--ro path-srlgs-names | | | | +--ro path-srlgs-name* [usage] | | | | +--ro usage identityref | | | | +--ro names* string | | | +--ro path-route-objects | | | +--ro path-route-object* [index] | | | +--ro index uint32 | | | +--ro (type)? | | | +--:(numbered-node-hop) | | | | +--ro numbered-node-hop | | | | +--ro node-id te-node-id | | | | +--ro hop-type? te-hop-type | | | +--:(numbered-link-hop) | | | | +--ro numbered-link-hop | | | | +--ro link-tp-id te-tp-id | | | | +--ro hop-type? te-hop-type | | | | +--ro direction? te-link-direction | | | +--:(unnumbered-link-hop) | | | | +--ro unnumbered-link-hop | | | | +--ro link-tp-id te-tp-id | | | | +--ro node-id te-node-id | | | | +--ro hop-type? te-hop-type | | | | +--ro direction? te-link-direction | | | +--:(as-number) | | | | +--ro as-number-hop | | | | +--ro as-number inet:as-number | | | | +--ro hop-type? te-hop-type | | | +--:(label) | | | +--ro label-hop | | | +--ro te-label | | | +--ro (technology)? | | | | +--:(generic) | | | | +--ro generic? | | | | rt-types:generalized- label | | | +--ro direction? | | | te-label-direction | | +--rw connectivity-matrix* [id] | | +--rw id uint32 | | +--rw from | | | +--rw tp-ref? leafref | | | +--rw label-restrictions | | | +--rw label-restriction* [index] | | | +--rw restriction? enumeration | | | +--rw index uint32 | | | +--rw label-start | | | | +--rw te-label | | | | +--rw (technology)? | | | | | +--:(generic) | | | | | +--rw generic? | | | | | rt-types:generalized- label | | | | +--rw direction? | | | | te-label-direction | | | +--rw label-end | | | | +--rw te-label | | | | +--rw (technology)? | | | | | +--:(generic) | | | | | +--rw generic? | | | | | rt-types:generalized- label | | | | +--rw direction? | | | | te-label-direction | | | +--rw label-step | | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? int32 | | | +--rw range-bitmap? yang:hex-string | | +--rw to | | | +--rw tp-ref? leafref | | | +--rw label-restrictions | | | +--rw label-restriction* [index] | | | +--rw restriction? enumeration | | | +--rw index uint32 | | | +--rw label-start | | | | +--rw te-label | | | | +--rw (technology)? | | | | | +--:(generic) | | | | | +--rw generic? | | | | | rt-types:generalized- label | | | | +--rw direction? | | | | te-label-direction | | | +--rw label-end | | | | +--rw te-label | | | | +--rw (technology)? | | | | | +--:(generic) | | | | | +--rw generic? | | | | | rt-types:generalized- label | | | | +--rw direction? | | | | te-label-direction | | | +--rw label-step | | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? int32 | | | +--rw range-bitmap? yang:hex-string | | +--rw is-allowed? boolean | | +--rw underlay {te-topology-hierarchy}? | | | +--rw enabled? boolean | | | +--rw primary-path | | | | +--rw network-ref? | | | | | -> /nw:networks/network/network-id | | | | +--rw path-element* [path-element-id] | | | | +--rw path-element-id uint32 | | | | +--rw (type)? | | | | +--:(numbered-node-hop) | | | | | +--rw numbered-node-hop | | | | | +--rw node-id te-node-id | | | | | +--rw hop-type? te-hop-type | | | | +--:(numbered-link-hop) | | | | | +--rw numbered-link-hop | | | | | +--rw link-tp-id te-tp-id | | | | | +--rw hop-type? te-hop-type | | | | | +--rw direction? | | | | | te-link-direction | | | | +--:(unnumbered-link-hop) | | | | | +--rw unnumbered-link-hop | | | | | +--rw link-tp-id te-tp-id | | | | | +--rw node-id te-node-id | | | | | +--rw hop-type? te-hop-type | | | | | +--rw direction? | | | | | te-link-direction | | | | +--:(as-number) | | | | | +--rw as-number-hop | | | | | +--rw as-number inet:as-number | | | | | +--rw hop-type? te-hop-type | | | | +--:(label) | | | | +--rw label-hop | | | | +--rw te-label | | | | +--rw (technology)? | | | | | +--:(generic) | | | | | +--rw generic? | | | | | rt- types:generalized-label | | | | +--rw direction? | | | | te-label-direction | | | +--rw backup-path* [index] | | | | +--rw index uint32 | | | | +--rw network-ref? | | | | | -> /nw:networks/network/network-id | | | | +--rw path-element* [path-element-id] | | | | +--rw path-element-id uint32 | | | | +--rw (type)? | | | | +--:(numbered-node-hop) | | | | | +--rw numbered-node-hop | | | | | +--rw node-id te-node-id | | | | | +--rw hop-type? te-hop-type | | | | +--:(numbered-link-hop) | | | | | +--rw numbered-link-hop | | | | | +--rw link-tp-id te-tp-id | | | | | +--rw hop-type? te-hop-type | | | | | +--rw direction? | | | | | te-link-direction | | | | +--:(unnumbered-link-hop) | | | | | +--rw unnumbered-link-hop | | | | | +--rw link-tp-id te-tp-id | | | | | +--rw node-id te-node-id | | | | | +--rw hop-type? te-hop-type | | | | | +--rw direction? | | | | | te-link-direction | | | | +--:(as-number) | | | | | +--rw as-number-hop | | | | | +--rw as-number inet:as-number | | | | | +--rw hop-type? te-hop-type | | | | +--:(label) | | | | +--rw label-hop | | | | +--rw te-label | | | | +--rw (technology)? | | | | | +--:(generic) | | | | | +--rw generic? | | | | | rt- types:generalized-label | | | | +--rw direction? | | | | te-label-direction | | | +--rw protection-type? identityref | | | +--rw tunnel-termination-points | | | | +--rw source? binary | | | | +--rw destination? binary | | | +--rw tunnels | | | +--rw sharing? boolean | | | +--rw tunnel* [tunnel-name] | | | +--rw tunnel-name string | | | +--rw sharing? boolean | | +--rw path-constraints | | | +--rw te-bandwidth | | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? te-bandwidth | | | +--rw link-protection? identityref | | | +--rw setup-priority? uint8 | | | +--rw hold-priority? uint8 | | | +--rw signaling-type? identityref | | | +--rw path-metric-bounds | | | | +--rw path-metric-bound* [metric-type] | | | | +--rw metric-type identityref | | | | +--rw upper-bound? uint64 | | | +--rw path-affinities-values | | | | +--rw path-affinities-value* [usage] | | | | +--rw usage identityref | | | | +--rw value? admin-groups | | | +--rw path-affinity-names | | | | +--rw path-affinity-name* [usage] | | | | +--rw usage identityref | | | | +--rw affinity-name* [name] | | | | +--rw name string | | | +--rw path-srlgs-lists | | | | +--rw path-srlgs-list* [usage] | | | | +--rw usage identityref | | | | +--rw values* srlg | | | +--rw path-srlgs-names | | | | +--rw path-srlgs-name* [usage] | | | | +--rw usage identityref | | | | +--rw names* string | | | +--rw disjointness? | | | te-path-disjointness | | +--rw optimizations | | | +--rw (algorithm)? | | | +--:(metric) {path-optimization-metric}? | | | | +--rw optimization-metric* [metric-type] | | | | | +--rw metric-type | | | | | | identityref | | | | | +--rw weight? | | | | | | uint8 | | | | | +--rw explicit-route-exclude-objects | | | | | | +--rw route-object-exclude-object* | | | | | | [index] | | | | | | +--rw index | | | | | | | uint32 | | | | | | +--rw (type)? | | | | | | +--:(numbered-node-hop) | | | | | | | +--rw numbered-node-hop | | | | | | | +--rw node-id | | | | | | | | te-node-id | | | | | | | +--rw hop-type? | | | | | | | te-hop-type | | | | | | +--:(numbered-link-hop) | | | | | | | +--rw numbered-link-hop | | | | | | | +--rw link-tp-id | | | | | | | | te-tp-id | | | | | | | +--rw hop-type? | | | | | | | | te-hop-type | | | | | | | +--rw direction? | | | | | | | te-link-direction | | | | | | +--:(unnumbered-link-hop) | | | | | | | +--rw unnumbered-link-hop | | | | | | | +--rw link-tp-id | | | | | | | | te-tp-id | | | | | | | +--rw node-id | | | | | | | | te-node-id | | | | | | | +--rw hop-type? | | | | | | | | te-hop-type | | | | | | | +--rw direction? | | | | | | | te-link-direction | | | | | | +--:(as-number) | | | | | | | +--rw as-number-hop | | | | | | | +--rw as-number | | | | | | | | inet:as-number | | | | | | | +--rw hop-type? | | | | | | | te-hop-type | | | | | | +--:(label) | | | | | | | +--rw label-hop | | | | | | | +--rw te-label | | | | | | | +--rw (technology)? | | | | | | | | +--:(generic) | | | | | | | | +--rw generic? | | | | | | | | rt- types:generalized-label | | | | | | | +--rw direction? | | | | | | | te-label- direction | | | | | | +--:(srlg) | | | | | | +--rw srlg | | | | | | +--rw srlg? uint32 | | | | | +--rw explicit-route-include-objects | | | | | +--rw route-object-include-object* | | | | | [index] | | | | | +--rw index | | | | | | uint32 | | | | | +--rw (type)? | | | | | +--:(numbered-node-hop) | | | | | | +--rw numbered-node-hop | | | | | | +--rw node-id | | | | | | | te-node-id | | | | | | +--rw hop-type? | | | | | | te-hop-type | | | | | +--:(numbered-link-hop) | | | | | | +--rw numbered-link-hop | | | | | | +--rw link-tp-id | | | | | | | te-tp-id | | | | | | +--rw hop-type? | | | | | | | te-hop-type | | | | | | +--rw direction? | | | | | | te-link-direction | | | | | +--:(unnumbered-link-hop) | | | | | | +--rw unnumbered-link-hop | | | | | | +--rw link-tp-id | | | | | | | te-tp-id | | | | | | +--rw node-id | | | | | | | te-node-id | | | | | | +--rw hop-type? | | | | | | | te-hop-type | | | | | | +--rw direction? | | | | | | te-link-direction | | | | | +--:(as-number) | | | | | | +--rw as-number-hop | | | | | | +--rw as-number | | | | | | | inet:as-number | | | | | | +--rw hop-type? | | | | | | te-hop-type | | | | | +--:(label) | | | | | +--rw label-hop | | | | | +--rw te-label | | | | | +--rw (technology)? | | | | | | +--:(generic) | | | | | | +--rw generic? | | | | | | rt- types:generalized-label | | | | | +--rw direction? | | | | | te-label- direction | | | | +--rw tiebreakers | | | | +--rw tiebreaker* [tiebreaker-type] | | | | +--rw tiebreaker-type identityref | | | +--:(objective-function) | | | {path-optimization-objective- function}? | | | +--rw objective-function | | | +--rw objective-function-type? | | | identityref | | +--ro path-properties | | +--ro path-metric* [metric-type] | | | +--ro metric-type identityref | | | +--ro accumulative-value? uint64 | | +--ro path-affinities-values | | | +--ro path-affinities-value* [usage] | | | +--ro usage identityref | | | +--ro value? admin-groups | | +--ro path-affinity-names | | | +--ro path-affinity-name* [usage] | | | +--ro usage identityref | | | +--ro affinity-name* [name] | | | +--ro name string | | +--ro path-srlgs-lists | | | +--ro path-srlgs-list* [usage] | | | +--ro usage identityref | | | +--ro values* srlg | | +--ro path-srlgs-names | | | +--ro path-srlgs-name* [usage] | | | +--ro usage identityref | | | +--ro names* string | | +--ro path-route-objects | | +--ro path-route-object* [index] | | +--ro index uint32 | | +--ro (type)? | | +--:(numbered-node-hop) | | | +--ro numbered-node-hop | | | +--ro node-id te-node-id | | | +--ro hop-type? te-hop-type | | +--:(numbered-link-hop) | | | +--ro numbered-link-hop | | | +--ro link-tp-id te-tp-id | | | +--ro hop-type? te-hop-type | | | +--ro direction? | | | te-link-direction | | +--:(unnumbered-link-hop) | | | +--ro unnumbered-link-hop | | | +--ro link-tp-id te-tp-id | | | +--ro node-id te-node-id | | | +--ro hop-type? te-hop-type | | | +--ro direction? | | | te-link-direction | | +--:(as-number) | | | +--ro as-number-hop | | | +--ro as-number inet:as-number | | | +--ro hop-type? te-hop-type | | +--:(label) | | +--ro label-hop | | +--ro te-label | | +--ro (technology)? | | | +--:(generic) | | | +--ro generic? | | | rt- types:generalized-label | | +--ro direction? | | te-label-direction | +--rw domain-id? uint32 | +--rw is-abstract? empty | +--rw name? string | +--rw signaling-address* inet:ip-address | +--rw underlay-topology {te-topology-hierarchy}? | +--rw network-ref? -> /nw:networks/network/network-id +--ro oper-status? te-types:te-oper-status +--ro geolocation | +--ro altitude? int64 | +--ro latitude? geographic-coordinate-degree | +--ro longitude? geographic-coordinate-degree +--ro is-multi-access-dr? empty +--ro information-source? te-info-source +--ro information-source-instance? string +--ro information-source-state | +--ro credibility-preference? uint16 | +--ro logical-network-element? string | +--ro network-instance? string | +--ro topology | +--ro node-ref? leafref | +--ro network-ref? -> /nw:networks/network/network-id +--ro information-source-entry* | [information-source information-source-instance] | +--ro information-source te-info-source | +--ro information-source-instance string | +--ro information-source-state | | +--ro credibility-preference? uint16 | | +--ro logical-network-element? string | | +--ro network-instance? string | | +--ro topology | | +--ro node-ref? leafref | | +--ro network-ref? | | -> /nw:networks/network/network-id | +--ro connectivity-matrices | | +--ro number-of-entries? uint16 | | +--ro label-restrictions | | | +--ro label-restriction* [index] | | | +--ro restriction? enumeration | | | +--ro index uint32 | | | +--ro label-start | | | | +--ro te-label | | | | +--ro (technology)? | | | | | +--:(generic) | | | | | +--ro generic? | | | | | rt-types:generalized-label | | | | +--ro direction? te-label-direction | | | +--ro label-end | | | | +--ro te-label | | | | +--ro (technology)? | | | | | +--:(generic) | | | | | +--ro generic? | | | | | rt-types:generalized-label | | | | +--ro direction? te-label-direction | | | +--ro label-step | | | | +--ro (technology)? | | | | +--:(generic) | | | | +--ro generic? int32 | | | +--ro range-bitmap? yang:hex-string | | +--ro is-allowed? boolean | | +--ro underlay {te-topology-hierarchy}? | | | +--ro enabled? boolean | | | +--ro primary-path | | | | +--ro network-ref? | | | | | -> /nw:networks/network/network-id | | | | +--ro path-element* [path-element-id] | | | | +--ro path-element-id uint32 | | | | +--ro (type)? | | | | +--:(numbered-node-hop) | | | | | +--ro numbered-node-hop | | | | | +--ro node-id te-node-id | | | | | +--ro hop-type? te-hop-type | | | | +--:(numbered-link-hop) | | | | | +--ro numbered-link-hop | | | | | +--ro link-tp-id te-tp-id | | | | | +--ro hop-type? te-hop-type | | | | | +--ro direction? te-link-direction | | | | +--:(unnumbered-link-hop) | | | | | +--ro unnumbered-link-hop | | | | | +--ro link-tp-id te-tp-id | | | | | +--ro node-id te-node-id | | | | | +--ro hop-type? te-hop-type | | | | | +--ro direction? te-link-direction | | | | +--:(as-number) | | | | | +--ro as-number-hop | | | | | +--ro as-number inet:as-number | | | | | +--ro hop-type? te-hop-type | | | | +--:(label) | | | | +--ro label-hop | | | | +--ro te-label | | | | +--ro (technology)? | | | | | +--:(generic) | | | | | +--ro generic? | | | | | rt-types:generalized- label | | | | +--ro direction? | | | | te-label-direction | | | +--ro backup-path* [index] | | | | +--ro index uint32 | | | | +--ro network-ref? | | | | | -> /nw:networks/network/network-id | | | | +--ro path-element* [path-element-id] | | | | +--ro path-element-id uint32 | | | | +--ro (type)? | | | | +--:(numbered-node-hop) | | | | | +--ro numbered-node-hop | | | | | +--ro node-id te-node-id | | | | | +--ro hop-type? te-hop-type | | | | +--:(numbered-link-hop) | | | | | +--ro numbered-link-hop | | | | | +--ro link-tp-id te-tp-id | | | | | +--ro hop-type? te-hop-type | | | | | +--ro direction? te-link-direction | | | | +--:(unnumbered-link-hop) | | | | | +--ro unnumbered-link-hop | | | | | +--ro link-tp-id te-tp-id | | | | | +--ro node-id te-node-id | | | | | +--ro hop-type? te-hop-type | | | | | +--ro direction? te-link-direction | | | | +--:(as-number) | | | | | +--ro as-number-hop | | | | | +--ro as-number inet:as-number | | | | | +--ro hop-type? te-hop-type | | | | +--:(label) | | | | +--ro label-hop | | | | +--ro te-label | | | | +--ro (technology)? | | | | | +--:(generic) | | | | | +--ro generic? | | | | | rt-types:generalized- label | | | | +--ro direction? | | | | te-label-direction | | | +--ro protection-type? identityref | | | +--ro tunnel-termination-points | | | | +--ro source? binary | | | | +--ro destination? binary | | | +--ro tunnels | | | +--ro sharing? boolean | | | +--ro tunnel* [tunnel-name] | | | +--ro tunnel-name string | | | +--ro sharing? boolean | | +--ro path-constraints | | | +--ro te-bandwidth | | | | +--ro (technology)? | | | | +--:(generic) | | | | +--ro generic? te-bandwidth | | | +--ro link-protection? identityref | | | +--ro setup-priority? uint8 | | | +--ro hold-priority? uint8 | | | +--ro signaling-type? identityref | | | +--ro path-metric-bounds | | | | +--ro path-metric-bound* [metric-type] | | | | +--ro metric-type identityref | | | | +--ro upper-bound? uint64 | | | +--ro path-affinities-values | | | | +--ro path-affinities-value* [usage] | | | | +--ro usage identityref | | | | +--ro value? admin-groups | | | +--ro path-affinity-names | | | | +--ro path-affinity-name* [usage] | | | | +--ro usage identityref | | | | +--ro affinity-name* [name] | | | | +--ro name string | | | +--ro path-srlgs-lists | | | | +--ro path-srlgs-list* [usage] | | | | +--ro usage identityref | | | | +--ro values* srlg | | | +--ro path-srlgs-names | | | | +--ro path-srlgs-name* [usage] | | | | +--ro usage identityref | | | | +--ro names* string | | | +--ro disjointness? te-path-disjointness | | +--ro optimizations | | | +--ro (algorithm)? | | | +--:(metric) {path-optimization-metric}? | | | | +--ro optimization-metric* [metric-type] | | | | | +--ro metric-type | | | | | | identityref | | | | | +--ro weight? | | | | | | uint8 | | | | | +--ro explicit-route-exclude-objects | | | | | | +--ro route-object-exclude-object* | | | | | | [index] | | | | | | +--ro index | | | | | | | uint32 | | | | | | +--ro (type)? | | | | | | +--:(numbered-node-hop) | | | | | | | +--ro numbered-node-hop | | | | | | | +--ro node-id te-node-id | | | | | | | +--ro hop-type? te-hop-type | | | | | | +--:(numbered-link-hop) | | | | | | | +--ro numbered-link-hop | | | | | | | +--ro link-tp-id te-tp-id | | | | | | | +--ro hop-type? | | | | | | | | te-hop-type | | | | | | | +--ro direction? | | | | | | | te-link-direction | | | | | | +--:(unnumbered-link-hop) | | | | | | | +--ro unnumbered-link-hop | | | | | | | +--ro link-tp-id te-tp-id | | | | | | | +--ro node-id | | | | | | | | te-node-id | | | | | | | +--ro hop-type? | | | | | | | | te-hop-type | | | | | | | +--ro direction? | | | | | | | te-link-direction | | | | | | +--:(as-number) | | | | | | | +--ro as-number-hop | | | | | | | +--ro as-number | | | | | | | | inet:as-number | | | | | | | +--ro hop-type? | | | | | | | te-hop-type | | | | | | +--:(label) | | | | | | | +--ro label-hop | | | | | | | +--ro te-label | | | | | | | +--ro (technology)? | | | | | | | | +--:(generic) | | | | | | | | +--ro generic? | | | | | | | | rt- types:generalized-label | | | | | | | +--ro direction? | | | | | | | te-label-direction | | | | | | +--:(srlg) | | | | | | +--ro srlg | | | | | | +--ro srlg? uint32 | | | | | +--ro explicit-route-include-objects | | | | | +--ro route-object-include-object* | | | | | [index] | | | | | +--ro index | | | | | | uint32 | | | | | +--ro (type)? | | | | | +--:(numbered-node-hop) | | | | | | +--ro numbered-node-hop | | | | | | +--ro node-id te-node-id | | | | | | +--ro hop-type? te-hop-type | | | | | +--:(numbered-link-hop) | | | | | | +--ro numbered-link-hop | | | | | | +--ro link-tp-id te-tp-id | | | | | | +--ro hop-type? | | | | | | | te-hop-type | | | | | | +--ro direction? | | | | | | te-link-direction | | | | | +--:(unnumbered-link-hop) | | | | | | +--ro unnumbered-link-hop | | | | | | +--ro link-tp-id te-tp-id | | | | | | +--ro node-id | | | | | | | te-node-id | | | | | | +--ro hop-type? | | | | | | | te-hop-type | | | | | | +--ro direction? | | | | | | te-link-direction | | | | | +--:(as-number) | | | | | | +--ro as-number-hop | | | | | | +--ro as-number | | | | | | | inet:as-number | | | | | | +--ro hop-type? | | | | | | te-hop-type | | | | | +--:(label) | | | | | +--ro label-hop | | | | | +--ro te-label | | | | | +--ro (technology)? | | | | | | +--:(generic) | | | | | | +--ro generic? | | | | | | rt- types:generalized-label | | | | | +--ro direction? | | | | | te-label-direction | | | | +--ro tiebreakers | | | | +--ro tiebreaker* [tiebreaker-type] | | | | +--ro tiebreaker-type identityref | | | +--:(objective-function) | | | {path-optimization-objective-function}? | | | +--ro objective-function | | | +--ro objective-function-type? identityref | | +--ro path-properties | | | +--ro path-metric* [metric-type] | | | | +--ro metric-type identityref | | | | +--ro accumulative-value? uint64 | | | +--ro path-affinities-values | | | | +--ro path-affinities-value* [usage] | | | | +--ro usage identityref | | | | +--ro value? admin-groups | | | +--ro path-affinity-names | | | | +--ro path-affinity-name* [usage] | | | | +--ro usage identityref | | | | +--ro affinity-name* [name] | | | | +--ro name string | | | +--ro path-srlgs-lists | | | | +--ro path-srlgs-list* [usage] | | | | +--ro usage identityref | | | | +--ro values* srlg | | | +--ro path-srlgs-names | | | | +--ro path-srlgs-name* [usage] | | | | +--ro usage identityref | | | | +--ro names* string | | | +--ro path-route-objects | | | +--ro path-route-object* [index] | | | +--ro index uint32 | | | +--ro (type)? | | | +--:(numbered-node-hop) | | | | +--ro numbered-node-hop | | | | +--ro node-id te-node-id | | | | +--ro hop-type? te-hop-type | | | +--:(numbered-link-hop) | | | | +--ro numbered-link-hop | | | | +--ro link-tp-id te-tp-id | | | | +--ro hop-type? te-hop-type | | | | +--ro direction? te-link-direction | | | +--:(unnumbered-link-hop) | | | | +--ro unnumbered-link-hop | | | | +--ro link-tp-id te-tp-id | | | | +--ro node-id te-node-id | | | | +--ro hop-type? te-hop-type | | | | +--ro direction? te-link-direction | | | +--:(as-number) | | | | +--ro as-number-hop | | | | +--ro as-number inet:as-number | | | | +--ro hop-type? te-hop-type | | | +--:(label) | | | +--ro label-hop | | | +--ro te-label | | | +--ro (technology)? | | | | +--:(generic) | | | | +--ro generic? | | | | rt-types:generalized- label | | | +--ro direction? | | | te-label-direction | | +--ro connectivity-matrix* [id] | | +--ro id uint32 | | +--ro from | | | +--ro tp-ref? leafref | | | +--ro label-restrictions | | | +--ro label-restriction* [index] | | | +--ro restriction? enumeration | | | +--ro index uint32 | | | +--ro label-start | | | | +--ro te-label | | | | +--ro (technology)? | | | | | +--:(generic) | | | | | +--ro generic? | | | | | rt-types:generalized- label | | | | +--ro direction? | | | | te-label-direction | | | +--ro label-end | | | | +--ro te-label | | | | +--ro (technology)? | | | | | +--:(generic) | | | | | +--ro generic? | | | | | rt-types:generalized- label | | | | +--ro direction? | | | | te-label-direction | | | +--ro label-step | | | | +--ro (technology)? | | | | +--:(generic) | | | | +--ro generic? int32 | | | +--ro range-bitmap? yang:hex-string | | +--ro to | | | +--ro tp-ref? leafref | | | +--ro label-restrictions | | | +--ro label-restriction* [index] | | | +--ro restriction? enumeration | | | +--ro index uint32 | | | +--ro label-start | | | | +--ro te-label | | | | +--ro (technology)? | | | | | +--:(generic) | | | | | +--ro generic? | | | | | rt-types:generalized- label | | | | +--ro direction? | | | | te-label-direction | | | +--ro label-end | | | | +--ro te-label | | | | +--ro (technology)? | | | | | +--:(generic) | | | | | +--ro generic? | | | | | rt-types:generalized- label | | | | +--ro direction? | | | | te-label-direction | | | +--ro label-step | | | | +--ro (technology)? | | | | +--:(generic) | | | | +--ro generic? int32 | | | +--ro range-bitmap? yang:hex-string | | +--ro is-allowed? boolean | | +--ro underlay {te-topology-hierarchy}? | | | +--ro enabled? boolean | | | +--ro primary-path | | | | +--ro network-ref? | | | | | -> /nw:networks/network/network-id | | | | +--ro path-element* [path-element-id] | | | | +--ro path-element-id uint32 | | | | +--ro (type)? | | | | +--:(numbered-node-hop) | | | | | +--ro numbered-node-hop | | | | | +--ro node-id te-node-id | | | | | +--ro hop-type? te-hop-type | | | | +--:(numbered-link-hop) | | | | | +--ro numbered-link-hop | | | | | +--ro link-tp-id te-tp-id | | | | | +--ro hop-type? te-hop-type | | | | | +--ro direction? | | | | | te-link-direction | | | | +--:(unnumbered-link-hop) | | | | | +--ro unnumbered-link-hop | | | | | +--ro link-tp-id te-tp-id | | | | | +--ro node-id te-node-id | | | | | +--ro hop-type? te-hop-type | | | | | +--ro direction? | | | | | te-link-direction | | | | +--:(as-number) | | | | | +--ro as-number-hop | | | | | +--ro as-number inet:as-number | | | | | +--ro hop-type? te-hop-type | | | | +--:(label) | | | | +--ro label-hop | | | | +--ro te-label | | | | +--ro (technology)? | | | | | +--:(generic) | | | | | +--ro generic? | | | | | rt- types:generalized-label | | | | +--ro direction? | | | | te-label-direction | | | +--ro backup-path* [index] | | | | +--ro index uint32 | | | | +--ro network-ref? | | | | | -> /nw:networks/network/network-id | | | | +--ro path-element* [path-element-id] | | | | +--ro path-element-id uint32 | | | | +--ro (type)? | | | | +--:(numbered-node-hop) | | | | | +--ro numbered-node-hop | | | | | +--ro node-id te-node-id | | | | | +--ro hop-type? te-hop-type | | | | +--:(numbered-link-hop) | | | | | +--ro numbered-link-hop | | | | | +--ro link-tp-id te-tp-id | | | | | +--ro hop-type? te-hop-type | | | | | +--ro direction? | | | | | te-link-direction | | | | +--:(unnumbered-link-hop) | | | | | +--ro unnumbered-link-hop | | | | | +--ro link-tp-id te-tp-id | | | | | +--ro node-id te-node-id | | | | | +--ro hop-type? te-hop-type | | | | | +--ro direction? | | | | | te-link-direction | | | | +--:(as-number) | | | | | +--ro as-number-hop | | | | | +--ro as-number inet:as-number | | | | | +--ro hop-type? te-hop-type | | | | +--:(label) | | | | +--ro label-hop | | | | +--ro te-label | | | | +--ro (technology)? | | | | | +--:(generic) | | | | | +--ro generic? | | | | | rt- types:generalized-label | | | | +--ro direction? | | | | te-label-direction | | | +--ro protection-type? identityref | | | +--ro tunnel-termination-points | | | | +--ro source? binary | | | | +--ro destination? binary | | | +--ro tunnels | | | +--ro sharing? boolean | | | +--ro tunnel* [tunnel-name] | | | +--ro tunnel-name string | | | +--ro sharing? boolean | | +--ro path-constraints | | | +--ro te-bandwidth | | | | +--ro (technology)? | | | | +--:(generic) | | | | +--ro generic? te-bandwidth | | | +--ro link-protection? identityref | | | +--ro setup-priority? uint8 | | | +--ro hold-priority? uint8 | | | +--ro signaling-type? identityref | | | +--ro path-metric-bounds | | | | +--ro path-metric-bound* [metric-type] | | | | +--ro metric-type identityref | | | | +--ro upper-bound? uint64 | | | +--ro path-affinities-values | | | | +--ro path-affinities-value* [usage] | | | | +--ro usage identityref | | | | +--ro value? admin-groups | | | +--ro path-affinity-names | | | | +--ro path-affinity-name* [usage] | | | | +--ro usage identityref | | | | +--ro affinity-name* [name] | | | | +--ro name string | | | +--ro path-srlgs-lists | | | | +--ro path-srlgs-list* [usage] | | | | +--ro usage identityref | | | | +--ro values* srlg | | | +--ro path-srlgs-names | | | | +--ro path-srlgs-name* [usage] | | | | +--ro usage identityref | | | | +--ro names* string | | | +--ro disjointness? | | | te-path-disjointness | | +--ro optimizations | | | +--ro (algorithm)? | | | +--:(metric) {path-optimization-metric}? | | | | +--ro optimization-metric* [metric-type] | | | | | +--ro metric-type | | | | | | identityref | | | | | +--ro weight? | | | | | | uint8 | | | | | +--ro explicit-route-exclude-objects | | | | | | +--ro route-object-exclude-object* | | | | | | [index] | | | | | | +--ro index | | | | | | | uint32 | | | | | | +--ro (type)? | | | | | | +--:(numbered-node-hop) | | | | | | | +--ro numbered-node-hop | | | | | | | +--ro node-id | | | | | | | | te-node-id | | | | | | | +--ro hop-type? | | | | | | | te-hop-type | | | | | | +--:(numbered-link-hop) | | | | | | | +--ro numbered-link-hop | | | | | | | +--ro link-tp-id | | | | | | | | te-tp-id | | | | | | | +--ro hop-type? | | | | | | | | te-hop-type | | | | | | | +--ro direction? | | | | | | | te-link-direction | | | | | | +--:(unnumbered-link-hop) | | | | | | | +--ro unnumbered-link-hop | | | | | | | +--ro link-tp-id | | | | | | | | te-tp-id | | | | | | | +--ro node-id | | | | | | | | te-node-id | | | | | | | +--ro hop-type? | | | | | | | | te-hop-type | | | | | | | +--ro direction? | | | | | | | te-link-direction | | | | | | +--:(as-number) | | | | | | | +--ro as-number-hop | | | | | | | +--ro as-number | | | | | | | | inet:as-number | | | | | | | +--ro hop-type? | | | | | | | te-hop-type | | | | | | +--:(label) | | | | | | | +--ro label-hop | | | | | | | +--ro te-label | | | | | | | +--ro (technology)? | | | | | | | | +--:(generic) | | | | | | | | +--ro generic? | | | | | | | | rt- types:generalized-label | | | | | | | +--ro direction? | | | | | | | te-label- direction | | | | | | +--:(srlg) | | | | | | +--ro srlg | | | | | | +--ro srlg? uint32 | | | | | +--ro explicit-route-include-objects | | | | | +--ro route-object-include-object* | | | | | [index] | | | | | +--ro index | | | | | | uint32 | | | | | +--ro (type)? | | | | | +--:(numbered-node-hop) | | | | | | +--ro numbered-node-hop | | | | | | +--ro node-id | | | | | | | te-node-id | | | | | | +--ro hop-type? | | | | | | te-hop-type | | | | | +--:(numbered-link-hop) | | | | | | +--ro numbered-link-hop | | | | | | +--ro link-tp-id | | | | | | | te-tp-id | | | | | | +--ro hop-type? | | | | | | | te-hop-type | | | | | | +--ro direction? | | | | | | te-link-direction | | | | | +--:(unnumbered-link-hop) | | | | | | +--ro unnumbered-link-hop | | | | | | +--ro link-tp-id | | | | | | | te-tp-id | | | | | | +--ro node-id | | | | | | | te-node-id | | | | | | +--ro hop-type? | | | | | | | te-hop-type | | | | | | +--ro direction? | | | | | | te-link-direction | | | | | +--:(as-number) | | | | | | +--ro as-number-hop | | | | | | +--ro as-number | | | | | | | inet:as-number | | | | | | +--ro hop-type? | | | | | | te-hop-type | | | | | +--:(label) | | | | | +--ro label-hop | | | | | +--ro te-label | | | | | +--ro (technology)? | | | | | | +--:(generic) | | | | | | +--ro generic? | | | | | | rt- types:generalized-label | | | | | +--ro direction? | | | | | te-label- direction | | | | +--ro tiebreakers | | | | +--ro tiebreaker* [tiebreaker-type] | | | | +--ro tiebreaker-type identityref | | | +--:(objective-function) | | | {path-optimization-objective- function}? | | | +--ro objective-function | | | +--ro objective-function-type? | | | identityref | | +--ro path-properties | | +--ro path-metric* [metric-type] | | | +--ro metric-type identityref | | | +--ro accumulative-value? uint64 | | +--ro path-affinities-values | | | +--ro path-affinities-value* [usage] | | | +--ro usage identityref | | | +--ro value? admin-groups | | +--ro path-affinity-names | | | +--ro path-affinity-name* [usage] | | | +--ro usage identityref | | | +--ro affinity-name* [name] | | | +--ro name string | | +--ro path-srlgs-lists | | | +--ro path-srlgs-list* [usage] | | | +--ro usage identityref | | | +--ro values* srlg | | +--ro path-srlgs-names | | | +--ro path-srlgs-name* [usage] | | | +--ro usage identityref | | | +--ro names* string | | +--ro path-route-objects | | +--ro path-route-object* [index] | | +--ro index uint32 | | +--ro (type)? | | +--:(numbered-node-hop) | | | +--ro numbered-node-hop | | | +--ro node-id te-node-id | | | +--ro hop-type? te-hop-type | | +--:(numbered-link-hop) | | | +--ro numbered-link-hop | | | +--ro link-tp-id te-tp-id | | | +--ro hop-type? te-hop-type | | | +--ro direction? | | | te-link-direction | | +--:(unnumbered-link-hop) | | | +--ro unnumbered-link-hop | | | +--ro link-tp-id te-tp-id | | | +--ro node-id te-node-id | | | +--ro hop-type? te-hop-type | | | +--ro direction? | | | te-link-direction | | +--:(as-number) | | | +--ro as-number-hop | | | +--ro as-number inet:as-number | | | +--ro hop-type? te-hop-type | | +--:(label) | | +--ro label-hop | | +--ro te-label | | +--ro (technology)? | | | +--:(generic) | | | +--ro generic? | | | rt- types:generalized-label | | +--ro direction? | | te-label-direction | +--ro domain-id? uint32 | +--ro is-abstract? empty | +--ro name? string | +--ro signaling-address* inet:ip-address | +--ro underlay-topology {te-topology-hierarchy}? | +--ro network-ref? -> /nw:networks/network/network-id +--ro statistics | +--ro discontinuity-time? yang:date-and-time | +--ro node | | +--ro disables? yang:counter32 | | +--ro enables? yang:counter32 | | +--ro maintenance-sets? yang:counter32 | | +--ro maintenance-clears? yang:counter32 | | +--ro modifies? yang:counter32 | +--ro connectivity-matrix-entry | +--ro creates? yang:counter32 | +--ro deletes? yang:counter32 | +--ro disables? yang:counter32 | +--ro enables? yang:counter32 | +--ro modifies? yang:counter32 +--rw tunnel-termination-point* [tunnel-tp-id] +--rw tunnel-tp-id binary +--rw admin-status? | te-types:te-admin-status +--rw name? string +--rw switching-capability? identityref +--rw encoding? identityref +--rw inter-layer-lock-id* uint32 +--rw protection-type? identityref +--rw client-layer-adaptation | +--rw switching-capability* | [switching-capability encoding] | +--rw switching-capability identityref | +--rw encoding identityref | +--rw te-bandwidth | +--rw (technology)? | +--:(generic) | +--rw generic? te-bandwidth +--rw local-link-connectivities | +--rw number-of-entries? uint16 | +--rw label-restrictions | | +--rw label-restriction* [index] | | +--rw restriction? enumeration | | +--rw index uint32 | | +--rw label-start | | | +--rw te-label | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? | | | | rt-types:generalized-label | | | +--rw direction? te-label-direction | | +--rw label-end | | | +--rw te-label | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? | | | | rt-types:generalized-label | | | +--rw direction? te-label-direction | | +--rw label-step | | | +--rw (technology)? | | | +--:(generic) | | | +--rw generic? int32 | | +--rw range-bitmap? yang:hex-string | +--rw is-allowed? boolean | +--rw underlay {te-topology-hierarchy}? | | +--rw enabled? boolean | | +--rw primary-path | | | +--rw network-ref? | | | | -> /nw:networks/network/network-id | | | +--rw path-element* [path-element-id] | | | +--rw path-element-id uint32 | | | +--rw (type)? | | | +--:(numbered-node-hop) | | | | +--rw numbered-node-hop | | | | +--rw node-id te-node-id | | | | +--rw hop-type? te-hop-type | | | +--:(numbered-link-hop) | | | | +--rw numbered-link-hop | | | | +--rw link-tp-id te-tp-id | | | | +--rw hop-type? te-hop-type | | | | +--rw direction? te-link-direction | | | +--:(unnumbered-link-hop) | | | | +--rw unnumbered-link-hop | | | | +--rw link-tp-id te-tp-id | | | | +--rw node-id te-node-id | | | | +--rw hop-type? te-hop-type | | | | +--rw direction? te-link-direction | | | +--:(as-number) | | | | +--rw as-number-hop | | | | +--rw as-number inet:as-number | | | | +--rw hop-type? te-hop-type | | | +--:(label) | | | +--rw label-hop | | | +--rw te-label | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? | | | | rt-types:generalized- label | | | +--rw direction? | | | te-label-direction | | +--rw backup-path* [index] | | | +--rw index uint32 | | | +--rw network-ref? | | | | -> /nw:networks/network/network-id | | | +--rw path-element* [path-element-id] | | | +--rw path-element-id uint32 | | | +--rw (type)? | | | +--:(numbered-node-hop) | | | | +--rw numbered-node-hop | | | | +--rw node-id te-node-id | | | | +--rw hop-type? te-hop-type | | | +--:(numbered-link-hop) | | | | +--rw numbered-link-hop | | | | +--rw link-tp-id te-tp-id | | | | +--rw hop-type? te-hop-type | | | | +--rw direction? te-link-direction | | | +--:(unnumbered-link-hop) | | | | +--rw unnumbered-link-hop | | | | +--rw link-tp-id te-tp-id | | | | +--rw node-id te-node-id | | | | +--rw hop-type? te-hop-type | | | | +--rw direction? te-link-direction | | | +--:(as-number) | | | | +--rw as-number-hop | | | | +--rw as-number inet:as-number | | | | +--rw hop-type? te-hop-type | | | +--:(label) | | | +--rw label-hop | | | +--rw te-label | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? | | | | rt-types:generalized- label | | | +--rw direction? | | | te-label-direction | | +--rw protection-type? identityref | | +--rw tunnel-termination-points | | | +--rw source? binary | | | +--rw destination? binary | | +--rw tunnels | | +--rw sharing? boolean | | +--rw tunnel* [tunnel-name] | | +--rw tunnel-name string | | +--rw sharing? boolean | +--rw path-constraints | | +--rw te-bandwidth | | | +--rw (technology)? | | | +--:(generic) | | | +--rw generic? te-bandwidth | | +--rw link-protection? identityref | | +--rw setup-priority? uint8 | | +--rw hold-priority? uint8 | | +--rw signaling-type? identityref | | +--rw path-metric-bounds | | | +--rw path-metric-bound* [metric-type] | | | +--rw metric-type identityref | | | +--rw upper-bound? uint64 | | +--rw path-affinities-values | | | +--rw path-affinities-value* [usage] | | | +--rw usage identityref | | | +--rw value? admin-groups | | +--rw path-affinity-names | | | +--rw path-affinity-name* [usage] | | | +--rw usage identityref | | | +--rw affinity-name* [name] | | | +--rw name string | | +--rw path-srlgs-lists | | | +--rw path-srlgs-list* [usage] | | | +--rw usage identityref | | | +--rw values* srlg | | +--rw path-srlgs-names | | | +--rw path-srlgs-name* [usage] | | | +--rw usage identityref | | | +--rw names* string | | +--rw disjointness? te-path-disjointness | +--rw optimizations | | +--rw (algorithm)? | | +--:(metric) {path-optimization-metric}? | | | +--rw optimization-metric* [metric-type] | | | | +--rw metric-type | | | | | identityref | | | | +--rw weight? | | | | | uint8 | | | | +--rw explicit-route-exclude-objects | | | | | +--rw route-object-exclude-object* | | | | | [index] | | | | | +--rw index | | | | | | uint32 | | | | | +--rw (type)? | | | | | +--:(numbered-node-hop) | | | | | | +--rw numbered-node-hop | | | | | | +--rw node-id te-node-id | | | | | | +--rw hop-type? te-hop-type | | | | | +--:(numbered-link-hop) | | | | | | +--rw numbered-link-hop | | | | | | +--rw link-tp-id te-tp-id | | | | | | +--rw hop-type? | | | | | | | te-hop-type | | | | | | +--rw direction? | | | | | | te-link-direction | | | | | +--:(unnumbered-link-hop) | | | | | | +--rw unnumbered-link-hop | | | | | | +--rw link-tp-id te-tp-id | | | | | | +--rw node-id | | | | | | | te-node-id | | | | | | +--rw hop-type? | | | | | | | te-hop-type | | | | | | +--rw direction? | | | | | | te-link-direction | | | | | +--:(as-number) | | | | | | +--rw as-number-hop | | | | | | +--rw as-number | | | | | | | inet:as-number | | | | | | +--rw hop-type? | | | | | | te-hop-type | | | | | +--:(label) | | | | | | +--rw label-hop | | | | | | +--rw te-label | | | | | | +--rw (technology)? | | | | | | | +--:(generic) | | | | | | | +--rw generic? | | | | | | | rt- types:generalized-label | | | | | | +--rw direction? | | | | | | te-label-direction | | | | | +--:(srlg) | | | | | +--rw srlg | | | | | +--rw srlg? uint32 | | | | +--rw explicit-route-include-objects | | | | +--rw route-object-include-object* | | | | [index] | | | | +--rw index | | | | | uint32 | | | | +--rw (type)? | | | | +--:(numbered-node-hop) | | | | | +--rw numbered-node-hop | | | | | +--rw node-id te-node-id | | | | | +--rw hop-type? te-hop-type | | | | +--:(numbered-link-hop) | | | | | +--rw numbered-link-hop | | | | | +--rw link-tp-id te-tp-id | | | | | +--rw hop-type? | | | | | | te-hop-type | | | | | +--rw direction? | | | | | te-link-direction | | | | +--:(unnumbered-link-hop) | | | | | +--rw unnumbered-link-hop | | | | | +--rw link-tp-id te-tp-id | | | | | +--rw node-id | | | | | | te-node-id | | | | | +--rw hop-type? | | | | | | te-hop-type | | | | | +--rw direction? | | | | | te-link-direction | | | | +--:(as-number) | | | | | +--rw as-number-hop | | | | | +--rw as-number | | | | | | inet:as-number | | | | | +--rw hop-type? | | | | | te-hop-type | | | | +--:(label) | | | | +--rw label-hop | | | | +--rw te-label | | | | +--rw (technology)? | | | | | +--:(generic) | | | | | +--rw generic? | | | | | rt- types:generalized-label | | | | +--rw direction? | | | | te-label-direction | | | +--rw tiebreakers | | | +--rw tiebreaker* [tiebreaker-type] | | | +--rw tiebreaker-type identityref | | +--:(objective-function) | | {path-optimization-objective-function}? | | +--rw objective-function | | +--rw objective-function-type? identityref | +--ro path-properties | | +--ro path-metric* [metric-type] | | | +--ro metric-type identityref | | | +--ro accumulative-value? uint64 | | +--ro path-affinities-values | | | +--ro path-affinities-value* [usage] | | | +--ro usage identityref | | | +--ro value? admin-groups | | +--ro path-affinity-names | | | +--ro path-affinity-name* [usage] | | | +--ro usage identityref | | | +--ro affinity-name* [name] | | | +--ro name string | | +--ro path-srlgs-lists | | | +--ro path-srlgs-list* [usage] | | | +--ro usage identityref | | | +--ro values* srlg | | +--ro path-srlgs-names | | | +--ro path-srlgs-name* [usage] | | | +--ro usage identityref | | | +--ro names* string | | +--ro path-route-objects | | +--ro path-route-object* [index] | | +--ro index uint32 | | +--ro (type)? | | +--:(numbered-node-hop) | | | +--ro numbered-node-hop | | | +--ro node-id te-node-id | | | +--ro hop-type? te-hop-type | | +--:(numbered-link-hop) | | | +--ro numbered-link-hop | | | +--ro link-tp-id te-tp-id | | | +--ro hop-type? te-hop-type | | | +--ro direction? te-link-direction | | +--:(unnumbered-link-hop) | | | +--ro unnumbered-link-hop | | | +--ro link-tp-id te-tp-id | | | +--ro node-id te-node-id | | | +--ro hop-type? te-hop-type | | | +--ro direction? te-link-direction | | +--:(as-number) | | | +--ro as-number-hop | | | +--ro as-number inet:as-number | | | +--ro hop-type? te-hop-type | | +--:(label) | | +--ro label-hop | | +--ro te-label | | +--ro (technology)? | | | +--:(generic) | | | +--ro generic? | | | rt-types:generalized- label | | +--ro direction? | | te-label-direction | +--rw local-link-connectivity* [link-tp-ref] | +--rw link-tp-ref | | -> ../../../../../nt:termination-point/tp-id | +--rw label-restrictions | | +--rw label-restriction* [index] | | +--rw restriction? enumeration | | +--rw index uint32 | | +--rw label-start | | | +--rw te-label | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? | | | | rt-types:generalized-label | | | +--rw direction? te-label-direction | | +--rw label-end | | | +--rw te-label | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? | | | | rt-types:generalized-label | | | +--rw direction? te-label-direction | | +--rw label-step | | | +--rw (technology)? | | | +--:(generic) | | | +--rw generic? int32 | | +--rw range-bitmap? yang:hex-string | +--rw is-allowed? boolean | +--rw underlay {te-topology-hierarchy}? | | +--rw enabled? boolean | | +--rw primary-path | | | +--rw network-ref? | | | | -> /nw:networks/network/network-id | | | +--rw path-element* [path-element-id] | | | +--rw path-element-id uint32 | | | +--rw (type)? | | | +--:(numbered-node-hop) | | | | +--rw numbered-node-hop | | | | +--rw node-id te-node-id | | | | +--rw hop-type? te-hop-type | | | +--:(numbered-link-hop) | | | | +--rw numbered-link-hop | | | | +--rw link-tp-id te-tp-id | | | | +--rw hop-type? te-hop-type | | | | +--rw direction? | | | | te-link-direction | | | +--:(unnumbered-link-hop) | | | | +--rw unnumbered-link-hop | | | | +--rw link-tp-id te-tp-id | | | | +--rw node-id te-node-id | | | | +--rw hop-type? te-hop-type | | | | +--rw direction? | | | | te-link-direction | | | +--:(as-number) | | | | +--rw as-number-hop | | | | +--rw as-number inet:as-number | | | | +--rw hop-type? te-hop-type | | | +--:(label) | | | +--rw label-hop | | | +--rw te-label | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? | | | | rt- types:generalized-label | | | +--rw direction? | | | te-label-direction | | +--rw backup-path* [index] | | | +--rw index uint32 | | | +--rw network-ref? | | | | -> /nw:networks/network/network-id | | | +--rw path-element* [path-element-id] | | | +--rw path-element-id uint32 | | | +--rw (type)? | | | +--:(numbered-node-hop) | | | | +--rw numbered-node-hop | | | | +--rw node-id te-node-id | | | | +--rw hop-type? te-hop-type | | | +--:(numbered-link-hop) | | | | +--rw numbered-link-hop | | | | +--rw link-tp-id te-tp-id | | | | +--rw hop-type? te-hop-type | | | | +--rw direction? | | | | te-link-direction | | | +--:(unnumbered-link-hop) | | | | +--rw unnumbered-link-hop | | | | +--rw link-tp-id te-tp-id | | | | +--rw node-id te-node-id | | | | +--rw hop-type? te-hop-type | | | | +--rw direction? | | | | te-link-direction | | | +--:(as-number) | | | | +--rw as-number-hop | | | | +--rw as-number inet:as-number | | | | +--rw hop-type? te-hop-type | | | +--:(label) | | | +--rw label-hop | | | +--rw te-label | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? | | | | rt- types:generalized-label | | | +--rw direction? | | | te-label-direction | | +--rw protection-type? identityref | | +--rw tunnel-termination-points | | | +--rw source? binary | | | +--rw destination? binary | | +--rw tunnels | | +--rw sharing? boolean | | +--rw tunnel* [tunnel-name] | | +--rw tunnel-name string | | +--rw sharing? boolean | +--rw path-constraints | | +--rw te-bandwidth | | | +--rw (technology)? | | | +--:(generic) | | | +--rw generic? te-bandwidth | | +--rw link-protection? identityref | | +--rw setup-priority? uint8 | | +--rw hold-priority? uint8 | | +--rw signaling-type? identityref | | +--rw path-metric-bounds | | | +--rw path-metric-bound* [metric-type] | | | +--rw metric-type identityref | | | +--rw upper-bound? uint64 | | +--rw path-affinities-values | | | +--rw path-affinities-value* [usage] | | | +--rw usage identityref | | | +--rw value? admin-groups | | +--rw path-affinity-names | | | +--rw path-affinity-name* [usage] | | | +--rw usage identityref | | | +--rw affinity-name* [name] | | | +--rw name string | | +--rw path-srlgs-lists | | | +--rw path-srlgs-list* [usage] | | | +--rw usage identityref | | | +--rw values* srlg | | +--rw path-srlgs-names | | | +--rw path-srlgs-name* [usage] | | | +--rw usage identityref | | | +--rw names* string | | +--rw disjointness? | | te-path-disjointness | +--rw optimizations | | +--rw (algorithm)? | | +--:(metric) {path-optimization-metric}? | | | +--rw optimization-metric* [metric-type] | | | | +--rw metric-type | | | | | identityref | | | | +--rw weight? | | | | | uint8 | | | | +--rw explicit-route-exclude-objects | | | | | +--rw route-object-exclude-object* | | | | | [index] | | | | | +--rw index | | | | | | uint32 | | | | | +--rw (type)? | | | | | +--:(numbered-node-hop) | | | | | | +--rw numbered-node-hop | | | | | | +--rw node-id | | | | | | | te-node-id | | | | | | +--rw hop-type? | | | | | | te-hop-type | | | | | +--:(numbered-link-hop) | | | | | | +--rw numbered-link-hop | | | | | | +--rw link-tp-id | | | | | | | te-tp-id | | | | | | +--rw hop-type? | | | | | | | te-hop-type | | | | | | +--rw direction? | | | | | | te-link-direction | | | | | +--:(unnumbered-link-hop) | | | | | | +--rw unnumbered-link-hop | | | | | | +--rw link-tp-id | | | | | | | te-tp-id | | | | | | +--rw node-id | | | | | | | te-node-id | | | | | | +--rw hop-type? | | | | | | | te-hop-type | | | | | | +--rw direction? | | | | | | te-link-direction | | | | | +--:(as-number) | | | | | | +--rw as-number-hop | | | | | | +--rw as-number | | | | | | | inet:as-number | | | | | | +--rw hop-type? | | | | | | te-hop-type | | | | | +--:(label) | | | | | | +--rw label-hop | | | | | | +--rw te-label | | | | | | +--rw (technology)? | | | | | | | +--:(generic) | | | | | | | +--rw generic? | | | | | | | rt- types:generalized-label | | | | | | +--rw direction? | | | | | | te-label- direction | | | | | +--:(srlg) | | | | | +--rw srlg | | | | | +--rw srlg? uint32 | | | | +--rw explicit-route-include-objects | | | | +--rw route-object-include-object* | | | | [index] | | | | +--rw index | | | | | uint32 | | | | +--rw (type)? | | | | +--:(numbered-node-hop) | | | | | +--rw numbered-node-hop | | | | | +--rw node-id | | | | | | te-node-id | | | | | +--rw hop-type? | | | | | te-hop-type | | | | +--:(numbered-link-hop) | | | | | +--rw numbered-link-hop | | | | | +--rw link-tp-id | | | | | | te-tp-id | | | | | +--rw hop-type? | | | | | | te-hop-type | | | | | +--rw direction? | | | | | te-link-direction | | | | +--:(unnumbered-link-hop) | | | | | +--rw unnumbered-link-hop | | | | | +--rw link-tp-id | | | | | | te-tp-id | | | | | +--rw node-id | | | | | | te-node-id | | | | | +--rw hop-type? | | | | | | te-hop-type | | | | | +--rw direction? | | | | | te-link-direction | | | | +--:(as-number) | | | | | +--rw as-number-hop | | | | | +--rw as-number | | | | | | inet:as-number | | | | | +--rw hop-type? | | | | | te-hop-type | | | | +--:(label) | | | | +--rw label-hop | | | | +--rw te-label | | | | +--rw (technology)? | | | | | +--:(generic) | | | | | +--rw generic? | | | | | rt- types:generalized-label | | | | +--rw direction? | | | | te-label- direction | | | +--rw tiebreakers | | | +--rw tiebreaker* [tiebreaker-type] | | | +--rw tiebreaker-type identityref | | +--:(objective-function) | | {path-optimization-objective- function}? | | +--rw objective-function | | +--rw objective-function-type? | | identityref | +--ro path-properties | +--ro path-metric* [metric-type] | | +--ro metric-type identityref | | +--ro accumulative-value? uint64 | +--ro path-affinities-values | | +--ro path-affinities-value* [usage] | | +--ro usage identityref | | +--ro value? admin-groups | +--ro path-affinity-names | | +--ro path-affinity-name* [usage] | | +--ro usage identityref | | +--ro affinity-name* [name] | | +--ro name string | +--ro path-srlgs-lists | | +--ro path-srlgs-list* [usage] | | +--ro usage identityref | | +--ro values* srlg | +--ro path-srlgs-names | | +--ro path-srlgs-name* [usage] | | +--ro usage identityref | | +--ro names* string | +--ro path-route-objects | +--ro path-route-object* [index] | +--ro index uint32 | +--ro (type)? | +--:(numbered-node-hop) | | +--ro numbered-node-hop | | +--ro node-id te-node-id | | +--ro hop-type? te-hop-type | +--:(numbered-link-hop) | | +--ro numbered-link-hop | | +--ro link-tp-id te-tp-id | | +--ro hop-type? te-hop-type | | +--ro direction? | | te-link-direction | +--:(unnumbered-link-hop) | | +--ro unnumbered-link-hop | | +--ro link-tp-id te-tp-id | | +--ro node-id te-node-id | | +--ro hop-type? te-hop-type | | +--ro direction? | | te-link-direction | +--:(as-number) | | +--ro as-number-hop | | +--ro as-number inet:as-number | | +--ro hop-type? te-hop-type | +--:(label) | +--ro label-hop | +--ro te-label | +--ro (technology)? | | +--:(generic) | | +--ro generic? | | rt- types:generalized-label | +--ro direction? | te-label-direction +--ro oper-status? | te-types:te-oper-status +--ro geolocation | +--ro altitude? int64 | +--ro latitude? geographic-coordinate-degree | +--ro longitude? geographic-coordinate-degree +--ro statistics | +--ro discontinuity-time? yang:date-and-time | +--ro tunnel-termination-point | | +--ro disables? yang:counter32 | | +--ro enables? yang:counter32 | | +--ro maintenance-clears? yang:counter32 | | +--ro maintenance-sets? yang:counter32 | | +--ro modifies? yang:counter32 | | +--ro downs? yang:counter32 | | +--ro ups? yang:counter32 | | +--ro in-service-clears? yang:counter32 | | +--ro in-service-sets? yang:counter32 | +--ro local-link-connectivity | +--ro creates? yang:counter32 | +--ro deletes? yang:counter32 | +--ro disables? yang:counter32 | +--ro enables? yang:counter32 | +--ro modifies? yang:counter32 +--rw supporting-tunnel-termination-point* [node-ref tunnel-tp-ref] +--rw node-ref inet:uri +--rw tunnel-tp-ref binary augment /nw:networks/nw:network/nt:link: +--rw te! +--rw (bundle-stack-level)? | +--:(bundle) | | +--rw bundled-links | | +--rw bundled-link* [sequence] | | +--rw sequence uint32 | | +--rw src-tp-ref? leafref | | +--rw des-tp-ref? leafref | +--:(component) | +--rw component-links | +--rw component-link* [sequence] | +--rw sequence uint32 | +--rw src-interface-ref? string | +--rw des-interface-ref? string +--rw te-link-template* | -> ../../../../te/templates/link-template/name | {template}? +--rw te-link-attributes | +--rw access-type? | | te-types:te-link-access-type | +--rw external-domain | | +--rw network-ref? | | | -> /nw:networks/network/network-id | | +--rw remote-te-node-id? te-types:te-node-id | | +--rw remote-te-link-tp-id? te-types:te-tp-id | +--rw is-abstract? empty | +--rw name? string | +--rw underlay {te-topology-hierarchy}? | | +--rw enabled? boolean | | +--rw primary-path | | | +--rw network-ref? | | | | -> /nw:networks/network/network-id | | | +--rw path-element* [path-element-id] | | | +--rw path-element-id uint32 | | | +--rw (type)? | | | +--:(numbered-node-hop) | | | | +--rw numbered-node-hop | | | | +--rw node-id te-node-id | | | | +--rw hop-type? te-hop-type | | | +--:(numbered-link-hop) | | | | +--rw numbered-link-hop | | | | +--rw link-tp-id te-tp-id | | | | +--rw hop-type? te-hop-type | | | | +--rw direction? te-link-direction | | | +--:(unnumbered-link-hop) | | | | +--rw unnumbered-link-hop | | | | +--rw link-tp-id te-tp-id | | | | +--rw node-id te-node-id | | | | +--rw hop-type? te-hop-type | | | | +--rw direction? te-link-direction | | | +--:(as-number) | | | | +--rw as-number-hop | | | | +--rw as-number inet:as-number | | | | +--rw hop-type? te-hop-type | | | +--:(label) | | | +--rw label-hop | | | +--rw te-label | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? | | | | rt-types:generalized- label | | | +--rw direction? | | | te-label-direction | | +--rw backup-path* [index] | | | +--rw index uint32 | | | +--rw network-ref? | | | | -> /nw:networks/network/network-id | | | +--rw path-element* [path-element-id] | | | +--rw path-element-id uint32 | | | +--rw (type)? | | | +--:(numbered-node-hop) | | | | +--rw numbered-node-hop | | | | +--rw node-id te-node-id | | | | +--rw hop-type? te-hop-type | | | +--:(numbered-link-hop) | | | | +--rw numbered-link-hop | | | | +--rw link-tp-id te-tp-id | | | | +--rw hop-type? te-hop-type | | | | +--rw direction? te-link-direction | | | +--:(unnumbered-link-hop) | | | | +--rw unnumbered-link-hop | | | | +--rw link-tp-id te-tp-id | | | | +--rw node-id te-node-id | | | | +--rw hop-type? te-hop-type | | | | +--rw direction? te-link-direction | | | +--:(as-number) | | | | +--rw as-number-hop | | | | +--rw as-number inet:as-number | | | | +--rw hop-type? te-hop-type | | | +--:(label) | | | +--rw label-hop | | | +--rw te-label | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? | | | | rt-types:generalized- label | | | +--rw direction? | | | te-label-direction | | +--rw protection-type? identityref | | +--rw tunnel-termination-points | | | +--rw source? binary | | | +--rw destination? binary | | +--rw tunnels | | +--rw sharing? boolean | | +--rw tunnel* [tunnel-name] | | +--rw tunnel-name string | | +--rw sharing? boolean | +--rw admin-status? | | te-types:te-admin-status | +--rw link-index? uint64 | +--rw administrative-group? | | te-types:admin-groups | +--rw interface-switching-capability* | | [switching-capability encoding] | | +--rw switching-capability identityref | | +--rw encoding identityref | | +--rw max-lsp-bandwidth* [priority] | | +--rw priority uint8 | | +--rw te-bandwidth | | +--rw (technology)? | | +--:(generic) | | +--rw generic? te-bandwidth | +--rw label-restrictions | | +--rw label-restriction* [index] | | +--rw restriction? enumeration | | +--rw index uint32 | | +--rw label-start | | | +--rw te-label | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? | | | | rt-types:generalized-label | | | +--rw direction? te-label-direction | | +--rw label-end | | | +--rw te-label | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? | | | | rt-types:generalized-label | | | +--rw direction? te-label-direction | | +--rw label-step | | | +--rw (technology)? | | | +--:(generic) | | | +--rw generic? int32 | | +--rw range-bitmap? yang:hex-string | +--rw link-protection-type? identityref | +--rw max-link-bandwidth | | +--rw te-bandwidth | | +--rw (technology)? | | +--:(generic) | | +--rw generic? te-bandwidth | +--rw max-resv-link-bandwidth | | +--rw te-bandwidth | | +--rw (technology)? | | +--:(generic) | | +--rw generic? te-bandwidth | +--rw unreserved-bandwidth* [priority] | | +--rw priority uint8 | | +--rw te-bandwidth | | +--rw (technology)? | | +--:(generic) | | +--rw generic? te-bandwidth | +--rw te-default-metric? uint32 | +--rw te-delay-metric? uint32 | +--rw te-igp-metric? uint32 | +--rw te-srlgs | | +--rw value* te-types:srlg | +--rw te-nsrlgs {nsrlg}? | +--rw id* uint32 +--ro oper-status? te-types:te-oper-status +--ro is-transitional? empty +--ro information-source? te-info-source +--ro information-source-instance? string +--ro information-source-state | +--ro credibility-preference? uint16 | +--ro logical-network-element? string | +--ro network-instance? string | +--ro topology | +--ro link-ref? leafref | +--ro network-ref? -> /nw:networks/network/network-id +--ro information-source-entry* | [information-source information-source-instance] | +--ro information-source te-info-source | +--ro information-source-instance string | +--ro information-source-state | | +--ro credibility-preference? uint16 | | +--ro logical-network-element? string | | +--ro network-instance? string | | +--ro topology | | +--ro link-ref? leafref | | +--ro network-ref? | | -> /nw:networks/network/network-id | +--ro link-index? uint64 | +--ro administrative-group? | | te-types:admin-groups | +--ro interface-switching-capability* | | [switching-capability encoding] | | +--ro switching-capability identityref | | +--ro encoding identityref | | +--ro max-lsp-bandwidth* [priority] | | +--ro priority uint8 | | +--ro te-bandwidth | | +--ro (technology)? | | +--:(generic) | | +--ro generic? te-bandwidth | +--ro label-restrictions | | +--ro label-restriction* [index] | | +--ro restriction? enumeration | | +--ro index uint32 | | +--ro label-start | | | +--ro te-label | | | +--ro (technology)? | | | | +--:(generic) | | | | +--ro generic? | | | | rt-types:generalized-label | | | +--ro direction? te-label-direction | | +--ro label-end | | | +--ro te-label | | | +--ro (technology)? | | | | +--:(generic) | | | | +--ro generic? | | | | rt-types:generalized-label | | | +--ro direction? te-label-direction | | +--ro label-step | | | +--ro (technology)? | | | +--:(generic) | | | +--ro generic? int32 | | +--ro range-bitmap? yang:hex-string | +--ro link-protection-type? identityref | +--ro max-link-bandwidth | | +--ro te-bandwidth | | +--ro (technology)? | | +--:(generic) | | +--ro generic? te-bandwidth | +--ro max-resv-link-bandwidth | | +--ro te-bandwidth | | +--ro (technology)? | | +--:(generic) | | +--ro generic? te-bandwidth | +--ro unreserved-bandwidth* [priority] | | +--ro priority uint8 | | +--ro te-bandwidth | | +--ro (technology)? | | +--:(generic) | | +--ro generic? te-bandwidth | +--ro te-default-metric? uint32 | +--ro te-delay-metric? uint32 | +--ro te-igp-metric? uint32 | +--ro te-srlgs | | +--ro value* te-types:srlg | +--ro te-nsrlgs {nsrlg}? | +--ro id* uint32 +--ro recovery | +--ro restoration-status? te-types:te-recovery-status | +--ro protection-status? te-types:te-recovery-status +--ro underlay {te-topology-hierarchy}? | +--ro dynamic? boolean | +--ro committed? boolean +--ro statistics +--ro discontinuity-time? yang:date-and-time +--ro disables? yang:counter32 +--ro enables? yang:counter32 +--ro maintenance-clears? yang:counter32 +--ro maintenance-sets? yang:counter32 +--ro modifies? yang:counter32 +--ro downs? yang:counter32 +--ro ups? yang:counter32 +--ro fault-clears? yang:counter32 +--ro fault-detects? yang:counter32 +--ro protection-switches? yang:counter32 +--ro protection-reverts? yang:counter32 +--ro restoration-failures? yang:counter32 +--ro restoration-starts? yang:counter32 +--ro restoration-successes? yang:counter32 +--ro restoration-reversion-failures? yang:counter32 +--ro restoration-reversion-starts? yang:counter32 +--ro restoration-reversion-successes? yang:counter32 augment /nw:networks/nw:network/nw:node/nt:termination-point: +--rw te-tp-id? te-types:te-tp-id +--rw te! +--rw admin-status? | te-types:te-admin-status +--rw name? string +--rw interface-switching-capability* | [switching-capability encoding] | +--rw switching-capability identityref | +--rw encoding identityref | +--rw max-lsp-bandwidth* [priority] | +--rw priority uint8 | +--rw te-bandwidth | +--rw (technology)? | +--:(generic) | +--rw generic? te-bandwidth +--rw inter-domain-plug-id? binary +--rw inter-layer-lock-id* uint32 +--ro oper-status? | te-types:te-oper-status +--ro geolocation +--ro altitude? int64 +--ro latitude? geographic-coordinate-degree +--ro longitude?geographic-coordinate-degree ]]></artwork> </figure>geographic-coordinate-degree]]></sourcecode> </section> <sectiontitle="Companionanchor="append-b" numbered="true" toc="default"> <name>Companion YANG Data Model forNon-NMDA Compliant Implementations" anchor="append-b"><t>Non-NMDA-Compliant Implementations</name> <t> The YANG moduleietf-te-topology"ietf-te-topology" defined inthis document<xref target="sect-7"/> is designed to be used in conjunction with implementations that support the Network Management Datastore Architecture (NMDA) defined in <xreftarget="RFC8342"/>.target="RFC8342" format="default"/>. In order to allow implementations to use the model even in caseswhenwhere NMDA is not supported, the following companionmodule ietf-te-topology-statemodule, "ietf-te-topology-state", is defined as a statemodel, whichmodel that mirrors the moduleietf-te-topology defined earlier in this document."ietf-te-topology". However, all data nodes inthethis "ietf-te-topology-state" companion module arenon-configurable,non-configurable; they are provided to represent the applied configuration or the derived operational states.</t> <t>TheThis companionmodule, ietf-te-topology-state,module is redundant andSHOULD NOT<bcp14>SHOULD NOT</bcp14> be supported by implementations that supportNMDA.</t>NMDA; therefore, we define it below rather than in the main body of this document.</t> <t> As the structure of the moduleietf-te-topology-state"ietf-te-topology-state" mirrors that of the moduleietf-te-topology. The"ietf-te-topology", the YANG tree of the moduleietf-te-topology-state"ietf&nbhy;te-topology-state" is not depicted separately.</t> <sectiontitle="TEanchor="append-b1" numbered="true" toc="default"> <name>TE Topology State YANGModule" anchor="append-b1"><t>Module</name> <t> This module references <xreftarget="RFC6001"/>,target="RFC6001" format="default"/>, <xreftarget="RFC8345"/>,target="RFC8345" format="default"/>, and[I-D.ietf-teas-yang-te-types].</t> <figure><artwork><![CDATA[ <CODE BEGINS> file "ietf-te-topology-state@2019-02-07.yang"<xref target="RFC8776"/>.</t> <sourcecode name="ietf-te-topology-state@2020-06-29.yang" type="yang" markers="true"><![CDATA[ module ietf-te-topology-state { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-te-topology-state"; prefix"tet-s";tet-s; import ietf-te-types { prefix"te-types";te-types; reference"I-D.ietf-teas-yang-te-types: Traffic Engineering"RFC 8776: Common YANGTypes";Data Types for Traffic Engineering"; } import ietf-te-topology { prefix"tet";tet; reference "RFC 8795: YANG Data Model for Traffic Engineering (TE) Topologies"; } import ietf-network-state { prefix"nw-s";nw-s; reference "RFC 8345: A YANG Data Model for Network Topologies"; } import ietf-network-topology-state { prefix"nt-s";nt-s; reference "RFC 8345: A YANG Data Model for Network Topologies"; } organization "IETF Traffic Engineering Architecture and Signaling (TEAS) Working Group"; contact "WG Web:<http://tools.ietf.org/wg/teas/><https://datatracker.ietf.org/wg/teas/> WG List: <mailto:teas@ietf.org> Editor: Xufeng Liu <mailto:xufeng.liu.ietf@gmail.com> Editor: Igor Bryskin<mailto:Igor.Bryskin@huawei.com><mailto:i_bryskin@yahoo.com> Editor: Vishnu Pavan Beeram <mailto:vbeeram@juniper.net> Editor: Tarek Saad <mailto:tsaad@juniper.net> Editor: Himanshu Shah <mailto:hshah@ciena.com> Editor: Oscar GonzalezDede Dios <mailto:oscar.gonzalezdedios@telefonica.com>"; description"TE"This YANG module defines a TE topology state model. Copyright (c)20192020 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 Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents(http://trustee.ietf.org/license-info).(https://trustee.ietf.org/license-info). This version of this YANG module is part of RFCXXXX;8795; see the RFC itself for full legal notices."; revision"2019-02-07"2020-06-29 { description "Initialrevision";revision."; reference "RFCXXXX:8795: YANG Data Model forTETraffic Engineering (TE) Topologies";// RFC Ed.: replace XXXX with actual RFC number and remove // this note} /* * Groupings */ grouping te-node-connectivity-matrix-attributes { description "Termination point references of a connectivity matrix entry."; container from { description "Reference to a sourcelink termination point.";Link Termination Point (LTP)."; leaf tp-ref { type leafref { path "../../../../../../nt-s:termination-point/nt-s:tp-id"; } description "Relative reference to a termination point."; } uses te-types:label-set-info; } container to { description "Reference to a destinationlink termination point.";LTP."; leaf tp-ref { type leafref { path "../../../../../../nt-s:termination-point/nt-s:tp-id"; } description "Relative reference to a termination point."; } uses te-types:label-set-info; } uses tet:connectivity-matrix-entry-path-attributes; } // te-node-connectivity-matrix-attributes grouping te-node-tunnel-termination-point-llc-list { description "Locallink connectivity listLink Connectivity List (LLCL) of atunnel termination pointTunnel Termination Point (TTP) on a TE node."; list local-link-connectivity { key "link-tp-ref"; description "The termination capabilities betweentunnel-termination-pointthe TTP andlink termination-point. Thethe LTP. This capability information can be used to compute the tunnel path. The Interface Adjustment Capability Descriptors(IACD)(IACDs) (defined in RFC 6001) on eachlink-tpLTP can be derived from thislocal-link-connectivitylist."; reference "RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks(MLN/MRN).";(MLN/MRN)"; leaf link-tp-ref { type leafref { path "../../../../../nt-s:termination-point/nt-s:tp-id"; } description"Link termination point.";"LTP."; } uses te-types:label-set-info; uses tet:connectivity-matrix-entry-path-attributes; } // local-link-connectivity } //te-node-tunnel-termination-point-configte-node-tunnel-termination-point-llc-list /* * Data nodes */ augment "/nw-s:networks/nw-s:network/nw-s:network-types" { description"Introduce"Introduces a new network type for a TE topology."; container te-topology { presence "Indicates a TEtopology.";topology"; description "Its presence identifies the TE topology type."; } } augment "/nw-s:networks" { description "Augmentation parameters for TE topologies."; uses tet:te-topologies-augment; } augment "/nw-s:networks/nw-s:network" { when"nw-s:network-types/tet-s:te-topology"'nw-s:network-types/tet-s:te-topology' { description "Augmentation parameters apply only for networks with a TE topology type."; } description "Configuration parameters for a TE topology."; uses tet:te-topology-augment; } augment "/nw-s:networks/nw-s:network/nw-s:node" { when"../nw-s:network-types/tet-s:te-topology"'../nw-s:network-types/tet-s:te-topology' { description "Augmentation parameters apply only for networks with a TE topology type."; } description "Configuration parameters for TE at the node level."; leaf te-node-id { type te-types:te-node-id; description "The identifier of a node in the TE topology. A node is specific to a topology to which it belongs."; } container te { must"../te-node-id"'../te-node-id' { description"te-node-id"'te-node-id' is mandatory."; } must"count(../nw-s:supporting-node)<=1"'count(../nw-s:supporting-node)<=1' { description "For a node in a TE topology, there cannot be more than1one supporting node. If multiple nodes are abstracted, theunderlay-topology'underlay-topology' field is used."; } presence "TEsupport.";support"; description "Indicates TE support."; uses tet:te-node-augment; }// te} augment "/nw-s:networks/nw-s:network/nt-s:link" { when"../nw-s:network-types/tet-s:te-topology"'../nw-s:network-types/tet-s:te-topology' { description "Augmentation parameters apply only for networks with a TE topology type."; } description "Configuration parameters for TE at the link level."; container te { must"count(../nt-s:supporting-link)<=1"'count(../nt-s:supporting-link)<=1' { description "For a link in a TE topology, there cannot be more than1one supporting link. If one or more link paths are abstracted, the underlay is used."; } presence "TEsupport.";support"; description "Indicates TE support."; uses tet:te-link-augment; }// te} augment "/nw-s:networks/nw-s:network/nw-s:node/" + "nt-s:termination-point" { when"../../nw-s:network-types/tet-s:te-topology"'../../nw-s:network-types/tet-s:te-topology' { description "Augmentation parameters apply only for networks with a TE topology type."; } description "Configuration parameters for TE at the termination point level."; uses tet:te-termination-point-augment; } augment"/nw-s:networks/nw-s:network/nt-s:link/te/bundle-stack-level/""/nw-s:networks/nw-s:network/nt-s:link/te/" +"bundle/bundled-links/bundled-link""bundle-stack-level/bundle/bundled-links/bundled-link" { when"../../../../nw-s:network-types/tet-s:te-topology"'../../../../nw-s:network-types/tet-s:te-topology' { description "Augmentation parameters apply only for networks with a TE topology type."; } description"Augment"Augmentation for a TElinkbundled link."; leaf src-tp-ref { type leafref { path "../../../../../nw-s:node[nw-s:node-id = " + "current()/../../../../nt-s:source/" + "nt-s:source-node]/" + "nt-s:termination-point/nt-s:tp-id"; require-instance true; } description "Reference to another TE termination point on the same source node."; } leaf des-tp-ref { type leafref { path "../../../../../nw-s:node[nw-s:node-id = " + "current()/../../../../nt-s:destination/" + "nt-s:dest-node]/" + "nt-s:termination-point/nt-s:tp-id"; require-instance true; } description "Reference to another TE termination point on the same destination node."; } } augment "/nw-s:networks/nw-s:network/nw-s:node/te/" + "information-source-entry/connectivity-matrices/" + "connectivity-matrix" { when"../../../../../nw-s:network-types/tet-s:te-topology"'../../../../../nw-s:network-types/tet-s:te-topology' { description "Augmentation parameters apply only for networks with a TE topology type."; } description"Augment"Augmentation for the TE nodeconnectivity-matrix.";connectivity matrix."; uses te-node-connectivity-matrix-attributes; } augment"/nw-s:networks/nw-s:network/nw-s:node/te/te-node-attributes/""/nw-s:networks/nw-s:network/nw-s:node/te/" +"connectivity-matrices/connectivity-matrix""te-node-attributes/connectivity-matrices/" + "connectivity-matrix" { when"../../../../../nw-s:network-types/tet-s:te-topology"'../../../../../nw-s:network-types/tet-s:te-topology' { description "Augmentation parameters apply only for networks with a TE topology type."; } description"Augment"Augmentation for the TE nodeconnectivity-matrix.";connectivity matrix."; uses te-node-connectivity-matrix-attributes; } augment "/nw-s:networks/nw-s:network/nw-s:node/te/" + "tunnel-termination-point/local-link-connectivities" { when"../../../../nw-s:network-types/tet-s:te-topology"'../../../../nw-s:network-types/tet-s:te-topology' { description "Augmentation parameters apply only for networks with a TE topology type."; } description"Augment"Augmentation for TE nodetunnel termination pointTTP LLCs (Local Link Connectivities)."; uses te-node-tunnel-termination-point-llc-list; }} <CODE ENDS> ]]></artwork> </figure>}]]></sourcecode> </section> </section> <sectiontitle="Example:anchor="append-c" numbered="true" toc="default"> <name>Example: YANG Data Model forTechnology Specific Augmentations" anchor="append-c"><t>Technology-Specific Augmentations</name> <t> Thissectionappendix provides an example YANG moduleto definethat defines atechnology specifictechnology-specific TE topology model for the example-topology model described in <xreftarget="sect-6"/>.</t> <figure><artwork><![CDATA[target="sect-6" format="default"/>.</t> <t>This module references <xref target="RFC8345"/>.</t> <sourcecode name="" type="yang"><![CDATA[ module example-topology { yang-version 1.1; namespace"http://example.com/example-topology";"https://example.com/example-topology"; prefix"ex-topo";ex-topo; import ietf-network { prefix"nw";nw; reference "RFC 8345: A YANG Data Model for Network Topologies"; } import ietf-network-topology { prefix"nt";nt; reference "RFC 8345: A YANG Data Model for Network Topologies"; } import ietf-te-topology { prefix"tet";tet; reference "RFC 8795: YANG Data Model for Traffic Engineering (TE) Topologies"; } organization "Example Organization"; contact "Editor: Example Author"; description "This module defines a topology data model for the example technology."; revision2018-06-152020-06-29 { description "Initial revision."; reference "Examplereference.";reference"; } /* * Data nodes */ augment "/nw:networks/nw:network/nw:network-types/" + "tet:te-topology" { description"Augment"Augmentation for network types to define an example topology type."; container example-topology { presence"Introduce"Introduces a new network type for an exampletopology.";topology"; description "Its presence identifies the example topology type."; } } augment "/nw:networks/nw:network/tet:te" { when"../nw:network-types/tet:te-topology/"'../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } description"Augment"Augmentation for the network topology."; container attributes { description "Attributes for the example technology."; leaf attribute-1 { type uint8; description "Attribute 1 for the example technology."; } } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes" { when"../../nw:network-types/tet:te-topology/"'../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } description"Augment"Augmentation for node attributes."; container attributes { description "Attributes for the example technology."; leaf attribute-2 { type uint8; description "Attribute 2 for the example technology."; } } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices" { when"../../../../nw:network-types/tet:te-topology/"'../../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } description"Augment"Augmentation for node connectivity matrices."; container attributes { description "Attributes for the example technology."; leaf attribute-3 { type uint8; description "Attribute 3 for the example technology."; } } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix" { when"../../../../../nw:network-types/tet:te-topology/"'../../../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } description"Augment"Augmentation for the node connectivity matrix."; container attributes { description "Attributes for the example technology."; leaf attribute-3 { type uint8; description "Attribute 3 for the example technology."; } } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point" { when"../../../nw:network-types/tet:te-topology/"'../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } description"Augment tunnel termination point.";"Augmentation for a TTP."; container attributes { description "Attributes for the example technology."; leaf attribute-4 { type uint8; description "Attribute 4 for the example technology."; } } } augment "/nw:networks/nw:network/nw:node/nt:termination-point/" + "tet:te" { when"../../../nw:network-types/tet:te-topology/"'../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } description"Augment link termination point.";"Augmentation for an LTP."; container attributes { description "Attributes for the example technology."; leaf attribute-5 { type uint8; description "Attribute 5 for the example technology."; } } } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:te-link-attributes" { when"../../../nw:network-types/tet:te-topology/"'../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } description"Augment"Augmentation for link attributes."; container attributes { description "Attributes for the example technology."; leaf attribute-6 { type uint8; description "Attribute 6 for the example technology."; } } } /* *AugmentAugmentations for TE bandwidth. */ augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" + "tet:interface-switching-capability/tet:max-lsp-bandwidth/" + "tet:te-bandwidth/tet:technology" { case"example"example { container example { description "Attributes for the example technology."; leaf bandwidth-1 { type uint32; description "Bandwidth 1 for the example technology."; } } } description"Augment"Augmentation for TE bandwidth."; } augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" + "tet:max-link-bandwidth/" + "tet:te-bandwidth/tet:technology" { case"example"example { container example { description "Attributes for the example technology."; leaf bandwidth-1 { type uint32; description "Bandwidth 1 for the example technology."; } } } description"Augment"Augmentation for TE bandwidth."; } augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" + "tet:max-resv-link-bandwidth/" + "tet:te-bandwidth/tet:technology" { case"example"example { container example { description "Attributes for the example technology."; leaf bandwidth-1 { type uint32; description "Bandwidth 1 for the example technology."; } } } description"Augment"Augmentation for TE bandwidth."; } augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" + "tet:unreserved-bandwidth/" + "tet:te-bandwidth/tet:technology" { case"example"example { container example { description "Attributes for the example technology."; leaf bandwidth-1 { type uint32; description "Bandwidth 1 for the example technology."; } } } description"Augment"Augmentation for TE bandwidth."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:path-constraints/tet:te-bandwidth/tet:technology" { when"../../../../../../../nw:network-types/tet:te-topology/"'../../../../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf bandwidth-1 { type uint32; description "Bandwidth 1 for the example technology."; } } } description"Augment"Augmentation for TE bandwidth."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:path-constraints/tet:te-bandwidth/tet:technology" { when"../../../../../../../nw:network-types/tet:te-topology/"'../../../../../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf bandwidth-1 { type uint32; description "Bandwidth 1 for the example technology."; } } } description"Augment"Augmentation for TE bandwidth."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:path-constraints/tet:te-bandwidth/tet:technology" { when"../../../../../../../nw:network-types/tet:te-topology/"'../../../../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf bandwidth-1 { type uint32; description "Bandwidth 1 for the example technology."; } } } description"Augment"Augmentation for TE bandwidth."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:path-constraints/tet:te-bandwidth/tet:technology" { when"../../../../../../../nw:network-types/tet:te-topology/"'../../../../../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf bandwidth-1 { type uint32; description "Bandwidth 1 for the example technology."; } } } description"Augment"Augmentation for TE bandwidth."; } augment "/nw:networks/nw:network/nw:node/tet:te/" +"tet:tunnel-termination-point/tet:client-layer-adaptation/""tet:tunnel-termination-point/" + "tet:client-layer-adaptation/tet:switching-capability/" +"tet:switching-capability/tet:te-bandwidth/tet:technology""tet:te-bandwidth/tet:technology" { when"../../../../../../../nw:network-types/tet:te-topology/"'../../../../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf bandwidth-1 { type uint32; description "Bandwidth 1 for the example technology."; } } } description"Augment"Augmentation for TE bandwidth."; } augment "/nw:networks/nw:network/nw:node/tet:te/" +"tet:tunnel-termination-point/tet:local-link-connectivities/""tet:tunnel-termination-point/" +"tet:path-constraints/tet:te-bandwidth/tet:technology""tet:local-link-connectivities/tet:path-constraints/" + "tet:te-bandwidth/tet:technology" { when"../../../../../../../nw:network-types/tet:te-topology/"'../../../../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf bandwidth-1 { type uint32; description "Bandwidth 1 for the example technology."; } } } description"Augment"Augmentation for TE bandwidth."; } augment "/nw:networks/nw:network/nw:node/tet:te/" +"tet:tunnel-termination-point/tet:local-link-connectivities/""tet:tunnel-termination-point/" +"tet:local-link-connectivity/""tet:local-link-connectivities/" +"tet:path-constraints/tet:te-bandwidth/tet:technology""tet:local-link-connectivity/tet:path-constraints/" + "tet:te-bandwidth/tet:technology" { when"../../../../../../../../nw:network-types/tet:te-topology/"'../../../../../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf bandwidth-1 { type uint32; description "Bandwidth 1 for the example technology."; } } } description"Augment"Augmentation for TE bandwidth."; } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:te-link-attributes/" + "tet:interface-switching-capability/tet:max-lsp-bandwidth/" + "tet:te-bandwidth/tet:technology" { when"../../../../../../../../nw:network-types/tet:te-topology/"'../../../../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf bandwidth-1 { type uint32; description "Bandwidth 1 for the example technology."; } } } description"Augment"Augmentation for TE bandwidth."; } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:te-link-attributes/" + "tet:max-link-bandwidth/" + "tet:te-bandwidth/tet:technology" { when"../../../../../../nw:network-types/tet:te-topology/"'../../../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf bandwidth-1 { type uint32; description "Bandwidth 1 for the example technology."; } } } description"Augment"Augmentation for TE bandwidth."; } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:te-link-attributes/" + "tet:max-resv-link-bandwidth/" + "tet:te-bandwidth/tet:technology" { when"../../../../../../nw:network-types/tet:te-topology/"'../../../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf bandwidth-1 { type uint32; description "Bandwidth 1 for the example technology."; } } } description"Augment"Augmentation for TE bandwidth."; } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:information-source-entry/" + "tet:interface-switching-capability/tet:max-lsp-bandwidth/" + "tet:te-bandwidth/tet:technology" { when"../../../../../../../../nw:network-types/tet:te-topology/"'../../../../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf bandwidth-1 { type uint32; description "Bandwidth 1 for the example technology."; } } } description"Augment"Augmentation for TE bandwidth."; } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:information-source-entry/" + "tet:max-link-bandwidth/" + "tet:te-bandwidth/tet:technology" { when"../../../../../../nw:network-types/tet:te-topology/"'../../../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf bandwidth-1 { type uint32; description "Bandwidth 1 for the example technology."; } } } description"Augment"Augmentation for TE bandwidth."; } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:information-source-entry/" + "tet:max-resv-link-bandwidth/" + "tet:te-bandwidth/tet:technology" { when"../../../../../../nw:network-types/tet:te-topology/"'../../../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf bandwidth-1 { type uint32; description "Bandwidth 1 for the example technology."; } } } description"Augment"Augmentation for TE bandwidth."; } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:information-source-entry/" + "tet:unreserved-bandwidth/" + "tet:te-bandwidth/tet:technology" { when"../../../../../../../nw:network-types/tet:te-topology/"'../../../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf bandwidth-1 { type uint32; description "Bandwidth 1 for the example technology."; } } } description"Augment"Augmentation for TE bandwidth."; } augment "/nw:networks/nw:network/nw:node/nt:termination-point/" +"tet:te/" + "tet:interface-switching-capability/tet:max-lsp-bandwidth/""tet:te/tet:interface-switching-capability/" +"tet:te-bandwidth/tet:technology""tet:max-lsp-bandwidth/tet:te-bandwidth/tet:technology" { when"../../../../../../../../nw:network-types/tet:te-topology/"'../../../../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf bandwidth-1 { type uint32; description "Bandwidth 1 for the example technology."; } } } description"Augment"Augmentation for TE bandwidth."; } /* *AugmentAugmentations for the TE label. */ augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" + "tet:underlay/tet:primary-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" + "tet:underlay/tet:backup-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" +"tet:label-restrictions/tet:label-restriction/tet:label-start/""tet:label-restrictions/tet:label-restriction/" +"tet:te-label/tet:technology""tet:label-start/tet:te-label/tet:technology" { case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" +"tet:label-restrictions/tet:label-restriction/tet:label-end/""tet:label-restrictions/tet:label-restriction/" +"tet:te-label/tet:technology""tet:label-end/tet:te-label/tet:technology" { case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } /* Under te-node-attributes/connectivity-matrices */ augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" +"tet:label-restrictions/tet:label-restriction/tet:label-start/""tet:label-restrictions/tet:label-restriction/" +"tet:te-label/tet:technology""tet:label-start/tet:te-label/tet:technology" { when"../../../../../../../../nw:network-types/tet:te-topology/"'../../../../../../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" +"tet:label-restrictions/tet:label-restriction/tet:label-end/""tet:label-restrictions/tet:label-restriction/" +"tet:te-label/tet:technology""tet:label-end/tet:te-label/tet:technology" { when"../../../../../../../../nw:network-types/tet:te-topology/"'../../../../../../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:underlay/tet:primary-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when"../../../../../../../../../../../../nw:network-types/"'../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:underlay/tet:backup-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when"../../../../../../../../../../../../nw:network-types/"'../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:path-properties/tet:path-route-objects/" + "tet:path-route-object/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when"../../../../../../../../../../../../nw:network-types/"'../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } /* Under te-node-attributes/.../connectivity-matrix */ augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" +"tet:connectivity-matrix/tet:from/""tet:connectivity-matrix/tet:from/tet:label-restrictions/" +"tet:label-restrictions/tet:label-restriction/tet:label-start/""tet:label-restriction/tet:label-start/" + "tet:te-label/tet:technology" { when"../../../../../../../../../../nw:network-types/"'../../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/tet:from/" +"tet:label-restrictions/tet:label-restriction/tet:label-end/""tet:label-restrictions/tet:label-restriction/" +"tet:te-label/tet:technology""tet:label-end/tet:te-label/tet:technology" { when"../../../../../../../../../../nw:network-types/"'../../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" +"tet:connectivity-matrix/tet:to/""tet:connectivity-matrix/tet:to/tet:label-restrictions/" +"tet:label-restrictions/tet:label-restriction/tet:label-start/""tet:label-restriction/tet:label-start/" + "tet:te-label/tet:technology" { when"../../../../../../../../../../nw:network-types/"'../../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/tet:to/" +"tet:label-restrictions/tet:label-restriction/tet:label-end/""tet:label-restrictions/tet:label-restriction/" +"tet:te-label/tet:technology""tet:label-end/tet:te-label/tet:technology" { when"../../../../../../../../../../nw:network-types/"'../../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:underlay/tet:primary-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when"../../../../../../../../../../../../../nw:network-types/"'../../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:underlay/tet:backup-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when"../../../../../../../../../../../../nw:network-types/"'../../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:path-properties/tet:path-route-objects/" + "tet:path-route-object/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when"../../../../../../../../../../../../../nw:network-types/"'../../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } /* Under information-source-entry/connectivity-matrices */ augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" +"tet:label-restrictions/tet:label-restriction/tet:label-start/""tet:label-restrictions/tet:label-restriction/" +"tet:te-label/tet:technology""tet:label-start/tet:te-label/tet:technology" { when"../../../../../../../../nw:network-types/tet:te-topology/"'../../../../../../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" +"tet:label-restrictions/tet:label-restriction/tet:label-end/""tet:label-restrictions/tet:label-restriction/" +"tet:te-label/tet:technology""tet:label-end/tet:te-label/tet:technology" { when"../../../../../../../../nw:network-types/tet:te-topology/"'../../../../../../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:underlay/tet:primary-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when"../../../../../../../../../../../../nw:network-types/"'../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:underlay/tet:backup-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when"../../../../../../../../../../../../nw:network-types/"'../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:path-properties/tet:path-route-objects/" + "tet:path-route-object/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when"../../../../../../../../../../../../nw:network-types/"'../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } /* Under information-source-entry/.../connectivity-matrix */ augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/tet:from/" +"tet:label-restrictions/tet:label-restriction/tet:label-start/""tet:label-restrictions/tet:label-restriction/" +"tet:te-label/tet:technology""tet:label-start/tet:te-label/tet:technology" { when"../../../../../../../../../../nw:network-types/"'../../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/tet:from/" +"tet:label-restrictions/tet:label-restriction/tet:label-end/""tet:label-restrictions/tet:label-restriction/" +"tet:te-label/tet:technology""tet:label-end/tet:te-label/tet:technology" { when"../../../../../../../../../../nw:network-types/"'../../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/tet:to/" +"tet:label-restrictions/tet:label-restriction/tet:label-start/""tet:label-restrictions/tet:label-restriction/" +"tet:te-label/tet:technology""tet:label-start/tet:te-label/tet:technology" { when"../../../../../../../../../../nw:network-types/"'../../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/tet:to/" +"tet:label-restrictions/tet:label-restriction/tet:label-end/""tet:label-restrictions/tet:label-restriction/" +"tet:te-label/tet:technology""tet:label-end/tet:te-label/tet:technology" { when"../../../../../../../../../../nw:network-types/"'../../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:underlay/tet:primary-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when"../../../../../../../../../../../../../nw:network-types/"'../../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:underlay/tet:backup-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when"../../../../../../../../../../../../nw:network-types/"'../../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:path-properties/tet:path-route-objects/" + "tet:path-route-object/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when"../../../../../../../../../../../../../nw:network-types/"'../../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } /* Under tunnel-termination-point/local-link-connectivities */ augment "/nw:networks/nw:network/nw:node/tet:te/" +"tet:tunnel-termination-point/tet:local-link-connectivities/""tet:tunnel-termination-point/" +"tet:label-restrictions/tet:label-restriction/tet:label-start/""tet:local-link-connectivities/tet:label-restrictions/" +"tet:te-label/tet:technology""tet:label-restriction/tet:label-start/tet:te-label/" + "tet:technology" { when"../../../../../../../../nw:network-types/tet:te-topology/"'../../../../../../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" +"tet:tunnel-termination-point/tet:local-link-connectivities/""tet:tunnel-termination-point/" + "tet:local-link-connectivities/tet:label-restrictions/" +"tet:label-restrictions/tet:label-restriction/tet:label-end/""tet:label-restriction/tet:label-end/" + "tet:te-label/tet:technology" { when"../../../../../../../../nw:network-types/tet:te-topology/"'../../../../../../../../nw:network-types/tet:te-topology/' +"ex-topo:example-topology"'ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" +"tet:tunnel-termination-point/tet:local-link-connectivities/""tet:tunnel-termination-point/" +"tet:underlay/tet:primary-path/tet:path-element/tet:type/""tet:local-link-connectivities/tet:underlay/" + "tet:primary-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when"../../../../../../../../../../../../nw:network-types/"'../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" +"tet:tunnel-termination-point/tet:local-link-connectivities/""tet:tunnel-termination-point/" +"tet:underlay/tet:backup-path/tet:path-element/tet:type/""tet:local-link-connectivities/tet:underlay/" + "tet:backup-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when"../../../../../../../../../../../../nw:network-types/"'../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" +"tet:tunnel-termination-point/tet:local-link-connectivities/""tet:tunnel-termination-point/" +"tet:path-properties/tet:path-route-objects/""tet:local-link-connectivities/tet:path-properties/" +"tet:path-route-object/tet:type/""tet:path-route-objects/tet:path-route-object/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when"../../../../../../../../../../../../nw:network-types/"'../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } /* Under tunnel-termination-point/.../local-link-connectivity */ augment "/nw:networks/nw:network/nw:node/tet:te/" +"tet:tunnel-termination-point/tet:local-link-connectivities/""tet:tunnel-termination-point/" +"tet:local-link-connectivity/""tet:local-link-connectivities/" +"tet:label-restrictions/tet:label-restriction/tet:label-start/""tet:local-link-connectivity/tet:label-restrictions/" + "tet:label-restriction/tet:label-start/" + "tet:te-label/tet:technology" { when"../../../../../../../../../nw:network-types/"'../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" +"tet:tunnel-termination-point/tet:local-link-connectivities/""tet:tunnel-termination-point/" +"tet:local-link-connectivity/""tet:local-link-connectivities/" +"tet:label-restrictions/tet:label-restriction/tet:label-end/""tet:local-link-connectivity/tet:label-restrictions/" + "tet:label-restriction/tet:label-end/" + "tet:te-label/tet:technology" { when"../../../../../../../../../nw:network-types/"'../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" +"tet:tunnel-termination-point/tet:local-link-connectivities/""tet:tunnel-termination-point/" +"tet:local-link-connectivity/""tet:local-link-connectivities/" +"tet:underlay/tet:primary-path/tet:path-element/tet:type/""tet:local-link-connectivity/tet:underlay/" + "tet:primary-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when"../../../../../../../../../../../../../nw:network-types/"'../../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" +"tet:tunnel-termination-point/tet:local-link-connectivities/""tet:tunnel-termination-point/" +"tet:local-link-connectivity/""tet:local-link-connectivities/" +"tet:underlay/tet:backup-path/tet:path-element/tet:type/""tet:local-link-connectivity/tet:underlay/" + "tet:backup-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when"../../../../../../../../../../../../nw:network-types/"'../../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" +"tet:tunnel-termination-point/tet:local-link-connectivities/""tet:tunnel-termination-point/" +"tet:local-link-connectivity/""tet:local-link-connectivities/" +"tet:path-properties/tet:path-route-objects/""tet:local-link-connectivity/tet:path-properties/" +"tet:path-route-object/tet:type/""tet:path-route-objects/tet:path-route-object/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when"../../../../../../../../../../../../../nw:network-types/"'../../../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } /* Under te-link-attributes */ augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:te-link-attributes/" +"tet:label-restrictions/tet:label-restriction/tet:label-start/""tet:label-restrictions/tet:label-restriction/" +"tet:te-label/tet:technology""tet:label-start/tet:te-label/tet:technology" { when"../../../../../../../nw:network-types/"'../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nt:link/tet:te/" +"tet:te-link-attributes/""tet:te-link-attributes/tet:label-restrictions/" +"tet:label-restrictions/tet:label-restriction/tet:label-end/""tet:label-restriction/tet:label-end/" + "tet:te-label/tet:technology" { when"../../../../../../../nw:network-types/"'../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nt:link/tet:te/" +"tet:te-link-attributes/""tet:te-link-attributes/tet:underlay/" +"tet:underlay/tet:primary-path/tet:path-element/tet:type/""tet:primary-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when"../../../../../../../../../../../nw:network-types/"'../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nt:link/tet:te/" +"tet:te-link-attributes/""tet:te-link-attributes/tet:underlay/" +"tet:underlay/tet:backup-path/tet:path-element/tet:type/""tet:backup-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when"../../../../../../../../../../nw:network-types/"'../../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } /* Underte-linkTE link information-source-entry */ augment "/nw:networks/nw:network/nt:link/tet:te/" +"tet:information-source-entry/""tet:information-source-entry/tet:label-restrictions/" +"tet:label-restrictions/tet:label-restriction/tet:label-start/""tet:label-restriction/tet:label-start/" + "tet:te-label/tet:technology" { when"../../../../../../../nw:network-types/"'../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; } augment "/nw:networks/nw:network/nt:link/tet:te/" +"tet:information-source-entry/""tet:information-source-entry/tet:label-restrictions/" +"tet:label-restrictions/tet:label-restriction/tet:label-end/""tet:label-restriction/tet:label-end/" + "tet:te-label/tet:technology" { when"../../../../../../../nw:network-types/"'../../../../../../../nw:network-types/' +"tet:te-topology/ex-topo:example-topology"'tet:te-topology/ex-topo:example-topology' { description "Augmentation parameters apply only for networks with an example topology type."; } case"example"example { container example { description "Attributes for the example technology."; leaf label-1 { type uint32; description "Label 1 for the example technology."; } } } description"Augment"Augmentation for the TE label."; }} ]]></artwork> </figure>}]]></sourcecode> </section> <sectiontitle="Acknowledgments"anchor="sect-a"numbered="no"><t>numbered="false" toc="default"> <name>Acknowledgments</name> <t> The authors would like to thankLou Berger, Sue Hares, Mazen Khaddam, Cyril Margaria and Zafar Ali<contact fullname="Lou Berger"/>, <contact fullname="Sue Hares"/>, <contact fullname="Mazen Khaddam"/>, <contact fullname="Cyril Margaria"/>, and <contact fullname="Zafar Ali"/> for participating in design discussions and providing valuable insights.</t> </section> <sectiontitle="Contributors" numbered="no" anchor="contributors"><figure><artwork><![CDATA[ Sergio Belotti Nokia Email: sergio.belotti@nokia.com Dieter Beller Nokia Email: Dieter.Beller@nokia.com Carlo Perocchio Ericsson Email: carlo.perocchio@ericsson.com Italo Busi Huawei Technologies Email: Italo.Busi@huawei.com ]]></artwork> </figure>numbered="false" anchor="contributors" toc="default"> <name>Contributors</name> <contact fullname="Sergio Belotti"> <organization>Nokia</organization> <address> <email>sergio.belotti@nokia.com</email> </address> </contact> <contact fullname="Dieter Beller"> <organization>Nokia</organization> <address> <email>Dieter.Beller@nokia.com</email> </address> </contact> <contact fullname="Carlo Perocchio"> <organization>Ericsson</organization> <address> <email>carlo.perocchio@ericsson.com</email> </address> </contact> <contact fullname="Italo Busi"> <organization>Huawei Technologies</organization> <address> <email>Italo.Busi@huawei.com</email> </address> </contact> </section> </back> </rfc>