draft-ietf-teas-yang-te-topo-22.txt   rfc8795.txt 
TEAS Working Group Xufeng Liu
Internet Draft Volta Networks
Intended status: Standards Track Igor Bryskin
Huawei Technologies
Vishnu Pavan Beeram
Tarek Saad
Juniper Networks
Himanshu Shah
Ciena
Oscar Gonzalez De Dios
Telefonica
Expires: December 19, 2019 June 19, 2019
YANG Data Model for Traffic Engineering (TE) Topologies Internet Engineering Task Force (IETF) X. Liu
draft-ietf-teas-yang-te-topo-22 Request for Comments: 8795 Volta Networks
Category: Standards Track I. Bryskin
ISSN: 2070-1721 Futurewei Technologies, Inc.
V. Beeram
T. Saad
Juniper Networks
H. Shah
Ciena
O. Gonzalez de Dios
Telefonica
August 2020
Status of this Memo YANG Data Model for Traffic Engineering (TE) Topologies
This Internet-Draft is submitted in full conformance with the Abstract
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This document defines a YANG data model for representing, retrieving,
Task Force (IETF), its areas, and its working groups. Note that and manipulating Traffic Engineering (TE) Topologies. The model
other groups may also distribute working documents as Internet- serves as a base model that other technology-specific TE topology
Drafts. models can augment.
Internet-Drafts are draft documents valid for a maximum of six months Status of This Memo
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at This is an Internet Standards Track document.
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at This document is a product of the Internet Engineering Task Force
http://www.ietf.org/shadow.html (IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on December 19, 2019. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8795.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Abstract
This document defines a YANG data model for representing, retrieving
and manipulating Traffic Engineering (TE) Topologies. The model
serves as a base model that other technology specific TE Topology
models can augment.
Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
Table of Contents Table of Contents
1. Introduction...................................................3 1. Introduction
1.1. Terminology...............................................4 1.1. Terminology
1.2. Tree Structure............................................4 1.2. Tree Structure
1.3. Prefixes in Data Node Names...............................5 1.3. Prefixes in Data Node Names
2. Characterizing TE Topologies...................................5 2. Characterizing TE Topologies
3. Modeling Abstractions and Transformations......................7 3. Modeling Abstractions and Transformations
3.1. TE Topology...............................................7 3.1. TE Topology
3.2. TE Node...................................................7 3.2. TE Node
3.3. TE Link...................................................8 3.3. TE Link
3.4. Transitional TE Link for Multi-Layer Topologies...........8 3.4. Transitional TE Link for Multi-layer Topologies
3.5. TE Link Termination Point (LTP)..........................10 3.5. TE Link Termination Point (LTP)
3.6. TE Tunnel Termination Point (TTP)........................10 3.6. TE Tunnel Termination Point (TTP)
3.7. TE Node Connectivity Matrix..............................11 3.7. TE Node Connectivity Matrix
3.8. TTP Local Link Connectivity List (LLCL)..................11 3.8. TTP Local Link Connectivity List (LLCL)
3.9. TE Path..................................................11 3.9. TE Path
3.10. TE Inter-Layer Lock.....................................12 3.10. TE Inter-layer Lock
3.11. Underlay TE topology....................................13 3.11. Underlay TE Topology
3.12. Overlay TE topology.....................................13 3.12. Overlay TE Topology
3.13. Abstract TE topology....................................13 3.13. Abstract TE Topology
4. Model Applicability...........................................14 4. Model Applicability
4.1. Native TE Topologies.....................................14 4.1. Native TE Topologies
4.2. Customized TE Topologies.................................16 4.2. Customized TE Topologies
4.3. Merging TE Topologies Provided by Multiple Providers.....19 4.3. Merging TE Topologies Provided by Multiple Providers
4.4. Dealing with Multiple Abstract TE Topologies Provided by the 4.4. Dealing with Multiple Abstract TE Topologies Provided by
Same Provider.................................................22 the Same Provider
5. Modeling Considerations.......................................25 5. Modeling Considerations
5.1. Network topology building blocks.........................25 5.1. Network Topology Building Blocks
5.2. Technology agnostic TE Topology model....................25 5.2. Technology-Agnostic TE Topology Model
5.3. Model Structure..........................................26 5.3. Model Structure
5.4. Topology Identifiers.....................................27 5.4. Topology Identifiers
5.5. Generic TE Link Attributes...............................27 5.5. Generic TE Link Attributes
5.6. Generic TE Node Attributes...............................28 5.6. Generic TE Node Attributes
5.7. TED Information Sources..................................29 5.7. TED Information Sources
5.8. Overlay/Underlay Relationship............................30 5.8. Overlay/Underlay Relationship
5.9. Templates................................................31 5.9. Templates
5.10. Scheduling Parameters...................................32 5.10. Scheduling Parameters
5.11. Notifications...........................................33 5.11. Notifications
6. Guidance for Writing Technology Specific TE Topology Augmentations 6. Guidance for Writing Technology-Specific TE Topology
.................................................................33 Augmentations
7. TE Topology YANG Module.......................................46 7. TE Topology YANG Module
8. Security Considerations.......................................92 8. Security Considerations
9. IANA Considerations...........................................94 9. IANA Considerations
10. References...................................................95 10. References
10.1. Normative References....................................95 10.1. Normative References
10.2. Informative References..................................96 10.2. Informative References
11. Acknowledgments.............................................100 Appendix A. Complete Model Tree Structure
Appendix A. Complete Model Tree Structure.......................101 Appendix B. Companion YANG Data Model for Non-NMDA-Compliant
Appendix B. Companion YANG Model for Non-NMDA Compliant Implementations
Implementations.................................................163 B.1. TE Topology State YANG Module
Appendix C. Example: YANG Model for Technology Specific Augmentations Appendix C. Example: YANG Data Model for Technology-Specific
................................................................172 Augmentations
Contributors....................................................210 Acknowledgments
Authors' Addresses..............................................210 Contributors
Authors' Addresses
1. Introduction 1. Introduction
The Traffic Engineering Database (TED) is an essential component of The Traffic Engineering Database (TED) is an essential component of
Traffic Engineered (TE) systems that are based on MPLS-TE [RFC2702] Traffic Engineered (TE) systems that are based on MPLS-TE [RFC2702]
and GMPLS [RFC3945]. The TED is a collection of all TE information and GMPLS [RFC3945]. The TED is a collection of all TE information
about all TE nodes and TE links in the network. The TE Topology is a about all TE nodes and TE links in the network. The TE topology is a
schematic arrangement of TE nodes and TE links present in a given schematic arrangement of TE nodes and TE links present in a given
TED. There could be one or more TE Topologies present in a given TED. There could be one or more TE topologies present in a given TE
Traffic Engineered system. A TE Topology is the topology on which system. A TE topology is the topology on which path computational
path computational algorithms are run to compute Traffic Engineered algorithms are run to compute TE paths.
Paths (TE Paths).
This document defines a YANG [RFC7950] data model for representing This document defines a YANG data model [RFC7950] for representing,
and manipulating TE Topologies. This model contains technology retrieving, and manipulating TE topologies. This model contains
agnostic TE Topology building blocks that can be augmented and used technology-agnostic TE topology building blocks that can be augmented
by other technology-specific TE Topology models. and used by other technology-specific TE topology models.
1.1. Terminology 1.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in
14 [RFC2119] [RFC8174] when, and only when, they appear in all BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
The reader is assumed to be familiar with general body of work We assume that the reader is familiar with the general body of work
captured in currently available TE related RFCs. [RFC7926] serves as captured in currently available RFCs related to Traffic Engineering.
a good starting point for those who may be less familiar with Traffic [RFC7926] serves as a good starting point for those who may be less
Engineering related RFCs. familiar with RFCs related to Traffic Engineering.
Some of the key terms used in this document are: Some of the key terms used in this document are as follows:
TED: The Traffic Engineering Database is a collection of all TE TED: The Traffic Engineering Database (TED) is a collection of all
information about all TE nodes and TE links in a given network. TE information about all TE nodes and TE links in a given network.
TE-Topology: The TE Topology is a schematic arrangement of TE nodes TE topology: The TE topology is a schematic arrangement of TE nodes
and TE links in a given TED. It forms the basis for a graph suitable and TE links in a given TED. It forms the basis for a graph
for TE path computations. suitable for TE path computations.
Native TE Topology: Native TE Topology is a topology that is native Native TE topology: A Native TE topology is a topology that is
to a given provider network. Native TE topology could be discovered native to a given provider network. A Native TE topology could be
via various routing protocols and/or subscribe/publish techniques. discovered via various routing protocols and/or subscribe/publish
This is the topology on which path computational algorithms are run techniques. This is the topology on which path computational
to compute TE Paths. algorithms are run to compute TE paths.
Customized TE Topology: Customized TE Topology is a custom topology Customized TE topology: A Customized TE topology is a custom
that is produced by a provider for a given client. This topology topology that is produced by a provider for a given client. This
typically makes abstractions on the provider's Native TE Topology, topology typically makes abstractions on the provider's Native TE
and is provided to the client. The client receives the Customized TE topology and is provided to the client. The client receives the
Topology, and merges it into the client's Native TE Topology. The Customized TE topology and merges it into the client's Native TE
client's path computational algorithms aren't typically run on the topology. The client's path computational algorithms aren't
Customized TE Topology; they are run on the client's Native TE typically run on the Customized TE topology; they are run on the
Topology after the merge. client's Native TE topology after the merge.
1.2. Tree Structure 1.2. Tree Structure
A simplified graphical representation of the data model is presented A simplified graphical representation of the data model is presented
in Appendix A. of this document. The tree format defined in [RFC8340] in Appendix A of this document. The tree format defined in [RFC8340]
is used for the YANG data model tree representation. is used for the YANG data model tree representation.
1.3. Prefixes in Data Node Names 1.3. Prefixes in Data Node Names
In this document, names of data nodes and other data model objects In this document, names of data nodes and other data model objects
are prefixed using the standard prefix associated with the are prefixed using the standard prefix associated with the
corresponding YANG imported modules, as shown in Table 1. corresponding YANG imported modules, as shown in Table 1.
+----------+-----------------------+-------------------------+ +==========+=======================+===========+
| Prefix | YANG module | Reference | | Prefix | YANG Module | Reference |
+----------+-----------------------+-------------------------+ +==========+=======================+===========+
| yang | ietf-yang-types | [RFC6991] | | yang | ietf-yang-types | [RFC6991] |
| inet | ietf-inet-types | [RFC6991] | +----------+-----------------------+-----------+
| nw | ietf-network | [RFC6991] | | inet | ietf-inet-types | [RFC6991] |
| nt | ietf-network-topology | [RFC8345] | +----------+-----------------------+-----------+
| te-types | ietf-te-types | [I-D.ietf-teas-yang-te | | nw | ietf-network | [RFC8345] |
| | | -types] | +----------+-----------------------+-----------+
+----------+-----------------------+-------------------------+ | nt | ietf-network-topology | [RFC8345] |
+----------+-----------------------+-----------+
| te-types | ietf-te-types | [RFC8776] |
+----------+-----------------------+-----------+
Table 1: Prefixes and corresponding YANG modules Table 1: Prefixes and Corresponding YANG Modules
2. Characterizing TE Topologies 2. Characterizing TE Topologies
The data model proposed by this document takes the following The data model defined by this document takes the following
characteristics of TE Topologies into account: characteristics of TE topologies into account:
- TE Topology is an abstract control-plane representation of the * The TE topology is an abstract control-plane representation of the
data-plane topology. Hence attributes specific to the data-plane data-plane topology. Hence, attributes specific to the data plane
must make their way into the corresponding TE Topology modeling. must make their way into the corresponding TE topology modeling.
The TE Topology comprises of dynamic auto-discovered data as well The TE topology is comprised of dynamic autodiscovered data as
as fairly static data associated with data-plane nodes and links. well as fairly static data associated with data-plane nodes and
The dynamic data may change frequently, such as unreserved links. The dynamic data, such as unreserved bandwidth available
bandwidth available on data-plane links. The static data rarely on data-plane links, may change frequently. The static data, such
changes, such as layer network identification, switching and as layer network identification, switching and adaptation
adaptation capabilities and limitations, fate sharing, and capabilities and limitations, fate-sharing, and administrative
administrative colors. It is possible for a single TE Topology to colors, rarely changes. It is possible for a single TE topology
encompass TE information at multiple switching layers. to encompass TE information at multiple switching layers.
- TE Topologies are protocol independent. Information about * TE topologies are protocol independent. Information about
topological elements may be learnt via link-state protocols, but topological elements may be learned via link-state protocols, but
the topology can exist without being dependent on any particular the topology can exist without being dependent on any particular
protocol. protocol.
- TE Topology may not be congruent to the routing topology in a * The TE topology may not be congruent with the routing topology in
given TE System. The routing topology is constructed based on a given TE system. The routing topology is constructed based on
routing adjacencies. There isn't always a one-to-one association routing adjacencies. There isn't always a one-to-one association
between a TE-link and a routing adjacency. For example, the between a TE link and a routing adjacency. For example, the
presence of a TE link between a pair of nodes doesn't necessarily presence of a TE link between a pair of nodes doesn't necessarily
imply the existence of a routing-adjacency between these nodes. To imply the existence of a routing adjacency between these nodes.
learn more, see [I-D.ietf-teas-te-topo-and-tunnel-modeling] and To learn more, see [TEAS-TOPO] and [YANG-L3].
[I-D.ietf-teas-yang-l3-te-topo].
- Each TE Topological element has at least one information source * Each TE topological element has at least one information source
associated with it. In some scenarios, there could be more than associated with it. In some scenarios, there could be more than
one information source associated with any given topological one information source associated with any given topological
element. element.
- TE Topologies can be hierarchical. Each node and link of a given * TE topologies can be hierarchical. Each node and link of a given
TE Topology can be associated with respective underlay topology. TE topology can be associated with a respective underlay topology.
This means that each node and link of a given TE Topology can be This means that each node and link of a given TE topology can be
associated with an independent stack of supporting TE Topologies. associated with an independent stack of supporting TE topologies.
- TE Topologies can be customized. TE topologies of a given network * TE topologies can be customized. TE topologies of a given network
presented by the network provider to its client could be presented by the network provider to its client could be
customized on per-client request basis. This customization could customized on a per-client-request basis. This customization
be performed by provider, by client or by provider/client could be performed by the provider, by the client, or by
negotiation. The relationship between a customized topology and provider/client negotiation. The relationship between a
provider's native topology could be captured as hierarchical customized topology and the provider's native topology could be
(overlay-underlay), but otherwise the two topologies are decoupled captured as hierarchical (overlay/underlay), but otherwise the two
from each other. A customized topology is presented to the client, topologies are decoupled from each other. A customized topology
while provider's native topology is known in its entirety to the is presented to the client, while the provider's native topology
provider itself. is known in its entirety to the provider itself.
3. Modeling Abstractions and Transformations 3. Modeling Abstractions and Transformations
3.1. TE Topology
A TE topology is a Traffic 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.
3.2. TE Node
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 the
data-plane aspects of the associated node(s) (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.
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 the client-
layer TE topology, while the remaining TE nodes belong to the server-
layer TE topology.
In Figure 1, Node-1, Node-2, and Node-3 are TE nodes.
| +---+ __ | +---+ __
| | | TE Node \/ TTP o LTP | | | TE Node \/ TTP o LTP
| +---+ | +---+
| |
| ----- TE Link | ----- TE Link
| ***** Node Connectivity Matrix, | ***** Node Connectivity Matrix,
| TTP Local Link Connectivity | TTP Local Link Connectivity
| @@@@@ TE Tunnel | @@@@@ TE Tunnel
o---------------------------------- o----------------------------------
Node-1 Node-3 Node-1 Node-3
+------------+ +------------+ +------------+ +------------+
| TTP-1 | | TTP-1 | | TTP-1 | | TTP-1 |
|LTP __ | TE-Tunel-1 | __ | |LTP __ | TE-Tunnel-1 | __ |
|-6 \/@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@\/ | |-6 \/@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@\/ |
o * * oLTP-1 Node-2 LTP-6o * * o o * * oLTP-1 Node-2 LTP-6o * * o
| * * | +------------+ | * * | | * * | +------------+ | * * |
| * TTP-2* | | | | * TTP-2* | | * TTP-2* | | | | * TTP-2* |
| * __ * |LTP-2 LTP-6| |LTP-1 LTP-5| * __ * | | * __ * |LTP-2 LTP-6| |LTP-1 LTP-5| * __ * |
o* \/ *o-----------o************o-----------o* \/ *o o* \/ *o-----------o************o-----------o* \/ *o
|LTP * * | Link-12 | * | Link-23 | * * | |LTP * * | Link-12 | * | Link-23 | * * |
|-5 * * | LTP-5| * |LTP-2 | * * | |-5 * * | LTP-5| * |LTP-2 | * * |
+--o------o--+ o************o +--o------o--+ +--o------o--+ o************o +--o------o--+
LTP-4 LTP-3 | * * * | LTP-4 LTP-3 LTP-4 LTP-3 | * * * | LTP-4 LTP-3
| ** * | | ** * |
+--o------o--+ +--o------o--+
LTP-4 LTP-3 LTP-4 LTP-3
Figure 1: TE Topology Modeling Abstractions LTP: Link Termination Point
TTP: Tunnel Termination Point
3.1. TE Topology
TE topology is a traffic engineering representation of one or more
layers of network topologies. 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.
3.2. TE Node
TE node is an element of a TE topology, presented as a vertex on TE
graph. 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. TE
node belongs to and is fully defined in exactly one TE topology. TE
node is assigned a unique ID within the TE topology scope. TE node
attributes include information related to the data plane aspects of
the associated node(s) (e.g. connectivity matrix), as well as
configuration data (such as TE node name). A given TE node can be
reached on the TE graph over one of TE links terminated by the TE
node.
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 the client layer
TE topology while the remaining TE nodes belong to the server layer
TE topology.
In Figure 1, Node-1, Node-2, and Node-3 are TE nodes. Figure 1: TE Topology Modeling Abstractions
3.3. TE Link 3.3. TE Link
TE link is an element of a TE topology, presented as an edge on TE A TE link is an element of a TE topology, presented as an edge on a
graph. The arrows on an edge indicate one or both directions of the TE graph. The arrows on an edge indicate one or both directions of
TE link. When there are a pair of parallel links of opposite the TE link. When there are a pair of parallel links of opposite
directions, an edge without arrows is also used. TE link represents directions, an edge without arrows is also used. A TE link
one or several (physical) links or a fraction of a link. TE link represents one or several (physical) links or a fraction of a link.
belongs to and is fully defined in exactly one TE topology. TE link A TE link belongs to and is fully defined in exactly one TE topology.
is assigned a unique ID within the TE topology scope. TE link A TE link is assigned a unique ID within the TE topology scope. TE
attributes include parameters related to the data plane aspects of link attributes include parameters related to the data-plane aspects
the associated link(s) (e.g. unreserved bandwidth, resource of the associated link(s) (unreserved bandwidth, resource maps /
maps/pools, etc.), as well as the configuration data (such as remote resource pools, etc.), as well as the configuration data (remote
node/link IDs, SRLGs, administrative colors, etc.). TE link is node IDs / link IDs, Shared Risk Link Groups (SRLGs), administrative
connected to TE node, terminating the TE link via exactly one TE link colors, etc.). A TE link is connected to a TE node, terminating the
termination point (LTP). TE link via exactly one TE Link Termination Point (LTP).
In Figure 1, Link-12 and Link-23 are TE links. In Figure 1, Link-12 and Link-23 are TE links.
3.4. Transitional TE Link for Multi-Layer Topologies 3.4. Transitional TE Link for Multi-layer Topologies
Networks are typically composed of multiple network layers where one Networks are typically composed of multiple network layers where one
or multiple signals in the client layer network can be multiplexed or multiple signals in the client-layer network can be multiplexed
and encapsulated into a server layer signal [RFC5212] [G.805]. The and encapsulated into a server-layer signal [RFC5212] [G.805]. The
server layer signal can be carried in the server layer network across server-layer signal can be carried in the server-layer network across
multiple nodes until the server layer signal is terminated and the multiple nodes until the server-layer signal is terminated and the
client layer signals reappear in the node that terminates the server client-layer signals reappear in the node that terminates the server-
layer signal. Examples of multi-layer networks are: IP over MPLS over layer signal. Examples of multi-layer networks include (1) IP over
Ethernet, low order Optical Data Unit-k (ODUk) signals multiplexed MPLS over Ethernet and (2) low-order Optical Data Unit-k (ODUk)
into a high order ODUl (l>k) carried over an Optical Channel (OCh) signals multiplexed into a high-order ODUl (l>k) carried over an
signal in an optical transport network as defined in [G.872] and Optical Channel (OCh) signal in an Optical Transport Network (OTN) as
[G.709]. defined in [G.872] and [G.709].
TE links as defined in Section 3.3. can be used to represent links TE links as defined in Section 3.3 can be used to represent links
within a network layer. In case of a multi-layer network, TE nodes within a network layer. In the case of a multi-layer network, TE
and TE links only allow representation of each network layer as a nodes and TE links only allow the representation of each network
separate TE topology. Each of these single layer TE topologies would layer as a separate TE topology. Each of these single-layer TE
be isolated from their client and their server layer TE topology, if topologies would be isolated from their client and their server-layer
present. The highest and the lowest network layer in the hierarchy TE topology, if present. The highest network layer and the lowest
only have a single adjacent layer below or above, respectively. network layer in the hierarchy only have a single adjacent layer
Multiplexing of client layer signals and encapsulating them into a below or above, respectively. Multiplexing client-layer signals and
server layer signal requires a function that is provided inside a encapsulating them into a server-layer signal require a function that
node (typically realized in hardware). This function is also called is provided inside a node (typically realized in hardware). This
layer transition. function is also called "layer transition".
One of the key requirements for path computation is to be able to One of the key requirements for path computation is to be able to
calculate a path between two endpoints across a multi-layer network calculate a path between two endpoints across a multi-layer network
based on the TE topology representing this multi-layer network. This based on the TE topology representing this multi-layer network. This
means that an additional TE construct is needed that represents means that an additional TE construct is needed that represents
potential layer transitions in the multi-layer TE-topology that potential layer transitions in the multi-layer TE topology that
connects the TE-topologies representing each separate network layer. connects the TE topologies representing each separate network layer.
The so-called transitional TE link is such a construct and it The so-called transitional TE link is such a construct, and it
represents the layer transition function residing inside a node that represents the layer transition function residing inside a node that
is decomposed into multiple logical nodes that are represented as TE is decomposed into multiple logical nodes that are represented as TE
nodes (see also the transitional link definition in [G.8080] for the nodes (also see [G.8080] for the definition of a transitional link
optical transport network). Hence, a transitional TE link connects a for the OTN). Hence, a transitional TE link connects a client-layer
client layer node with a server layer node. A TE link as defined in node with a server-layer node. A TE link as defined in Section 3.3
3.3. has LTPs of exactly the same kind on each link end whereas the has LTPs of exactly the same kind on each link end, whereas the
transitional TE link has client layer LTPs on the client side of the transitional TE link has client-layer LTPs on the client side of the
transitional link and in most cases a single server layer LTP on the transitional link and, in most cases, a single server-layer LTP on
server side. It should be noted that transitional links are a helper the server side. It should be noted that transitional links are a
construct in the multi-layer TE topology and they only exist as long helper construct in the multi-layer TE topology and they only exist
as they are not in use, as they represent potential connectivity. as long as they are not in use, as they represent potential
When the server layer trail has been established between the server connectivity. When the server-layer trail has been established
layer LTP of two transitional links in the server layer network, the between the server-layer LTP of two transitional links in the server-
resulting client layer link in the data plane will be represented as layer network, the resulting client-layer link in the data plane will
a normal TE link in the client layer topology. The transitional TE be represented as a normal TE link in the client-layer topology. The
links will re-appear when the server layer trail has been torn down. transitional TE links will reappear when the server-layer trail has
been torn down.
| | | |
| +---+ --- | +---+ ---
| | | TE Node \ / Transitional | | | TE Node \ / Transitional
| +---+ | Link | +---+ | Link
| |
| ----- Client Layer Link | ----- Client-Layer Link
| ===== Server Layer Link | ===== Server-Layer Link
| ***** Layer Boundary | ***** Layer Boundary
o---------------------------------- o----------------------------------
+------------------+ +-------------------+
| +------+ | +------+ | +-------+ | +-------+
-----|Client|------+ | Client -----|Client| -----|Client-|------+ | Client- -----|Client-|
| |Layer |---+ | | Layer |Layer | | |Layer |---+ | | Layer |Layer |
-----|Switch|-+ | | | Links -----|Node | -----|Switch |-+ | | | Links -----|Node |
| +------+ | | | | +------+ | +------ + | | | | +-------+
| | | | | Client | | | | | | | | Client | | |
| | | ---_| Layer --- --- | | | ---_| Layer --- ---
***|**********|*| \ /*|***************************\ /*\ /**** ***|***********|*| \ /*|***************************\ /*\ /****
| --- | | Server Transitional | | | --- | | Server Transitional | |
| Layer \ / | | Layer Links | | | Layer \ / | | Layer Links | |
| Term. | | | | | | Term. | | | | |
| | | | | | | | | | | |
| +------+ | +------+ | +-------+ | +-------+
=============|Server|===== Server ====|Server|==== =============|Server-|===== Server- ====|Server-|====
| |Layer | | Layer |Layer | | |Layer | | Layer |Layer |
=============|Switch|===== Links ====|Node |==== =============|Switch |===== Links ====|Node |====
| +------+ | +------+ | +-------+ | +-------+
+------------------+ +-------------------+
Physical Node View TE-Topology View Physical Node View TE Topology View
Figure 2: Modeling a Multi-Layer Node (Dual-Layer Example) Figure 2: Modeling a Multi-layer Node (Dual-layer Example)
3.5. TE Link Termination Point (LTP) 3.5. TE Link Termination Point (LTP)
TE link termination point (LTP) is a conceptual point of connection A TE Link Termination Point (LTP) is a conceptual point of connection
of a TE node to one of the TE links, terminated by the TE node. 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. Cardinality between an LTP and the associated TE link is 1:0..1.
In Figure 1, Node-2 has six LTPs: LTP-1 to LTP-6. In Figure 1, Node-2 has six LTPs: LTP-1 through LTP-6.
3.6. TE Tunnel Termination Point (TTP) 3.6. TE Tunnel Termination Point (TTP)
TE tunnel termination point (TTP) is an element of TE topology A TE Tunnel Termination Point (TTP) is an element of a TE topology
representing one or several of potential transport service representing one or several potential transport service termination
termination points (i.e. service client adaptation points such as points (i.e., service client adaptation points, such as a WDM/OCh
WDM/OCh transponder). TTP is associated with (hosted by) exactly one transponder). ("WDM" stands for "Wavelength Division Multiplexing".)
TE node. TTP is assigned a unique ID within the TE node scope. A TTP is associated with (hosted by) exactly one TE node. A TTP is
Depending on the TE node's internal constraints, a given TTP hosted assigned a unique ID within the TE node scope. Depending on the TE
by the TE node could be accessed via one, several or all TE links node's internal constraints, a given TTP hosted by the TE node could
terminated by the TE node. be accessed via one, several, or all TE links terminated by the TE
node.
In Figure 1, Node-1 has two TTPs: TTP-1 and TTP-2. In Figure 1, Node-1 has two TTPs: TTP-1 and TTP-2.
3.7. TE Node Connectivity Matrix 3.7. TE Node Connectivity Matrix
TE node connectivity matrix is a TE node's attribute describing the A TE node connectivity matrix is a TE node's attribute describing the
TE node's switching limitations in a form of valid switching TE node's switching limitations in the form of valid switching
combinations of the TE node's LTPs (see below). From the point of 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 view of a potential TE path arriving at the TE node at a given
inbound LTP, the node's connectivity matrix describes valid inbound LTP, the node's connectivity matrix describes valid
(permissible) outbound LTPs for the TE path to leave the TE node (permissible) outbound LTPs from which the TE path can leave the TE
from. node.
In Figure 1, the connectivity matrix on Node-2 is as follows:
In Figure 1, the connectivity matrix on Node-2 is:
{<LTP-6, LTP-1>, <LTP-5, LTP-2>, <LTP-5, LTP-4>, <LTP-4, LTP-1>, {<LTP-6, LTP-1>, <LTP-5, LTP-2>, <LTP-5, LTP-4>, <LTP-4, LTP-1>,
<LTP-3, LTP-2>} <LTP-3, LTP-2>}
3.8. TTP Local Link Connectivity List (LLCL) 3.8. TTP Local Link Connectivity List (LLCL)
TTP Local Link Connectivity List (LLCL) is a List of TE links A TTP Local Link Connectivity List (LLCL) is a list of TE links
terminated by the TTP hosting TE node (i.e. list of the TE link terminated by the TE node hosting a TTP, to which the TTP could be
LTPs), which the TTP could be connected to. From the point of view of connected. From the point of view of the potential TE path of a
a potential TE path, LLCL provides a list of valid TE links the TE connection, an LLCL provides a list of valid TE links the TE path
path needs to start/stop on for the connection, taking the TE path, needs to start/stop on for the connection to be successfully
to be successfully terminated on the TTP in question. terminated on a TTP.
In Figure 1, the LLCL on Node-1 is: In Figure 1, the LLCL on Node-1 is as follows:
{<TTP-1, LTP-5>, <TTP-1, LTP-2>, <TTP-2, LTP-3>, <TTP-2, LTP4>}
3.9. TE Path {<TTP-1, LTP-5>, <TTP-1, LTP-2>, <TTP-2, LTP-3>, <TTP-2, LTP-4>}
TE path is an ordered list of TE links and/or TE nodes on the TE 3.9. TE Path
topology graph, inter-connecting a pair of TTPs to be taken by a
potential connection. TE paths, for example, could be a product of A TE path is an ordered list of TE links and/or TE nodes on the TE
topology graph; this path interconnects a pair of TTPs to be used by
a potential connection. For example, TE paths could be a product of
successful path computation performed for a given transport service. successful path computation performed for a given transport service.
In Figure 1, the TE Path for TE-Tunnel-1 is: In Figure 1, the TE path for TE-Tunnel-1 is as follows:
{Node-1:TTP-1, Link-12, Node-2, Link-23, Node-3:TTP1}
3.10. TE Inter-Layer Lock {Node-1:TTP-1, Link-12, Node-2, Link-23, Node-3:TTP-1}
TE inter-layer lock is a modeling concept describing client-server 3.10. TE Inter-layer Lock
layer adaptation relationships and hence important for the multi-
layer traffic engineering. It is an association of M client layer A TE inter-layer lock is a modeling concept describing adaptation
LTPs and N server layer TTPs, within which data arriving at any of relationships between the client layer and the server layer and hence
the client layer LTPs could be adopted onto any of the server layer is important for multi-layer Traffic Engineering. It is an
TTPs. TE inter-layer lock is identified by inter-layer lock ID, which association of M client-layer LTPs and N server-layer TTPs, within
is unique across all TE topologies provided by the same provider. The which data arriving at any of the client-layer LTPs could be adopted
client layer LTPs and the server layer TTPs associated within a given onto any of the server-layer TTPs. A TE inter-layer lock is
TE inter-layer lock are annotated with the same inter-layer lock ID identified by an inter-layer lock ID, which is unique across all TE
attribute. topologies provided by the same provider. The client-layer LTPs and
the server-layer TTPs associated within a given TE inter-layer lock
are annotated with the same inter-layer lock ID attribute.
In Figure 3, a TE inter-layer lock with an ID of IL-1 associates six
client-layer LTPs (C-LTP-1 through C-LTP-6) with two server-layer
TTPs (S-TTP-1 and S-TTP-2). They all have the same attribute -- TE
inter-layer lock ID IL-1, which is the only thing that indicates the
association. A given LTP may have zero, one, or more inter-layer
lock IDs. In the latter case, 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 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., S-TTP-1 and S-TTP-2 in the 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 of the
client-layer LTPs with an inter-layer lock ID matching one of its
own. Additionally, each TTP has an unreserved adaptation bandwidth
attribute, which announces its remaining adaptation resources that
are sharable between all potential client-layer LTPs.
| +---+ __ | +---+ __
| | | TE Node \/ TTP o LTP | | | TE Node \/ TTP o LTP
| +---+ | +---+
| |
| ----- TE Link | ----- TE Link
| ***** TTP Local Link Connectivity | ***** TTP Local Link Connectivity
o---------------------------------- o----------------------------------
(IL-1) C-LTP-1 +------------+ C-LTP-2 (IL-1) (IL-1) C-LTP-1 +------------+ C-LTP-2 (IL-1)
--------O (IL-1) O-------- --------O (IL-1) O--------
(IL-1) C-LTP-3 | S-TTP-1 | C-LTP-4 (IL-1) (IL-1) C-LTP-3 | S-TTP-1 | C-LTP-4 (IL-1)
--------O __ 0-------- --------O __ 0--------
(IL-1) C-LTP-5 | *\/* | C-LTP-5 (IL-1) (IL-1) C-LTP-5 | *\/* | C-LTP-6 (IL-1)
--------O * * O-------- --------O * * O--------
| *(IL-1)* | | *(IL-1)* |
S-LTP-3 | * S-TTP-2* | S-LTP-4 S-LTP-3 | * S-TTP-2* | S-LTP-4
--------o* __ *o-------- --------o* __ *o--------
| *\/* | | *\/* |
| * * | | * * |
+--o------o--+ +--o------o--+
S-LTP-1 | | S-LTP-2 S-LTP-1 | | S-LTP-2
Figure 3: TE Inter-Layer Lock ID Associations Figure 3: TE Inter-layer Lock ID Associations
On the picture above a TE inter-layer lock with IL_1 ID associates 6
client layer LTPs (C-LTP-1 - C-LTP-6) with two server layer TTPs (S-
TTP-1 and S-TTP-2). They all have the same attribute - TE inter-layer
lock ID: IL-1, which is the only thing that indicates the
association. A given LTP may have 0, 1 or more inter-layer lock IDs.
In the latter case this means that the data arriving at the LTP may
be adopted onto any of TTPs associated with all specified inter-layer
locks. For example, C-LTP-1 could have two inter-layer lock IDs - IL-
1 and IL-2. This would mean that C-LTP-1 for adaptation purposes
could use not just TTPs associated with inter-layer lock IL-1 (i.e.
S-TTP-1 and S-TTP-2 on the picture), but any of 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 of client layer LTPs with inter-layer lock ID matching
one of its own. Additionally, each TTP has an attribute - Unreserved
Adaptation Bandwidth, which announces its remaining adaptation
resources sharable between all potential client LTPs.
LTPs and TTPs associated within the same TE inter-layer lock may be 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 hosted by the same (hybrid, multi-layer) TE node or multiple TE nodes
located in the same or separate TE topologies. The latter is located in the same or separate TE topologies. The latter case is
especially important since TE topologies of different layer networks especially important, since TE topologies of different layer networks
could be modeled by separate augmentations of the basic (common to could be modeled by separate augmentations of the basic (common to
all layers) TE topology model. all layers) TE topology model.
3.11. Underlay TE topology 3.11. Underlay TE Topology
Underlay TE topology is a TE topology that serves as a base for An underlay TE topology is a TE topology that serves as a base for
constructing of overlay TE topologies the construction of overlay TE topologies.
3.12. Overlay TE topology 3.12. Overlay TE Topology
Overlay TE topology is a TE topology constructed based on one or more An overlay TE topology is a TE topology that is constructed based on
underlay TE topologies. Each TE node of the overlay TE topology one or more underlay TE topologies. Each TE node of the overlay TE
represents an arbitrary segment of an underlay TE topology; each TE topology represents an arbitrary segment of an underlay TE topology;
link of the overlay TE topology represents an arbitrary TE path in each TE link of the overlay TE topology represents an arbitrary TE
one of the underlay TE topologies. The overlay TE topology and the path in one of the underlay TE topologies. The overlay TE topology
supporting underlay TE topologies may represent distinct layer and the supporting underlay TE topologies may represent distinct
networks (e.g. OTN/ODUk and WDM/OCh respectively) or the same layer layer networks (e.g., OTN/ODUk and WDM/OCh, respectively) or the same
network. layer network.
3.13. Abstract TE topology 3.13. Abstract TE Topology
Abstract TE topology is a topology that contains abstract topological An abstract TE topology is a topology that contains abstract
elements (nodes, links, tunnel termination points). Abstract TE topological elements (nodes, links, TTPs). An abstract TE topology
topology is an overlay TE topology created by a topology provider and is an overlay TE topology created by a topology provider and
customized for a topology provider's client based on one or more of customized for a topology provider's client based on one or more of
the provider's native TE topologies (underlay TE topologies), the the provider's Native TE topologies (underlay TE topologies), the
provider's policies and the client's preferences. For example, a provider's policies, and the client's preferences. For example, a
first level topology provider (such as Domain Controller) can create first-level topology provider (such as a domain controller) can
an abstract TE topology for its client (e.g. Multi-Domain Service create an abstract TE topology for its client (e.g., a multi-domain
Coordinator) based on the provider's one or more native TE service coordinator) based on one or more of the provider's Native TE
topologies, local policies/profiles and the client's TE topology topologies, local policies/profiles, and the client's TE topology
configuration requests configuration requests.
Figure 4 shows an example of abstract TE topology. Figure 4 shows an example of an abstract TE topology.
| +---+ | +---+
| | | TE Node | | | TE Node
| +---+ | +---+
| ----- TE Link | ----- TE Link
o---------------------------------- o----------------------------------
+---+ +---+ +---+ +---+
|s31|--------------|S5 | |S3 | |S5 |
+---+\ / +---+ +---+\ / +---+
\ / \ /
\ / \ /
\+---+/ +---+ \+---+/ +---+
/|AN1|\----------------|S8 | /|AN1|\----------------|S8 |
/ +---+ \ +---+ / +---+ \ +---+
+---+ / \ +---+ +---+ / \ +---+
|S9 |-------------|S11| |S9 | |S11|
+---+ +---+ +---+ +---+
Abstract TE Topology Abstract TE Topology
+---+ +---+ +---+ +---+
|S1 |--------------------|S2 | |S1 |--------------------|S2 |
+---+ +---+ +---+ +---+
/ \ / \
/ \ / \
+---+ / +---+ \ +---+ +---+ / +---+ \ +---+
|s3 |--------------------|S4 |---------|S5 | |S3 |--------------------|S4 |---------|S5 |
+---+\ +---+ +---+ +---+\ +---+ +---+
\ \ \ \ \ \
\ \ \ \ \ \
\+---+ +---+ +---+ \+---+ +---+ +---+
/|S6 |\ |S7 |---------|S8 | /|S6 |\ |S7 |---------|S8 |
/ +---+ \ +---+\ /+---+ / +---+ \ +---+\ /+---+
+---+ / \ +---+ +---+ / +---+ / \ +---+ +---+ /
|S9 |-------------|S10|--------------|S11|/ |S9 |-------------|S10|--------------|S11|/
+---+ +---+ +---+ +---+ +---+ +---+
Native TE Topology Native TE Topology
Figure 4: Abstract TE Topology Figure 4: Abstract TE Topology
4. Model Applicability 4. Model Applicability
4.1. Native TE Topologies 4.1. Native TE Topologies
The model discussed in this draft can be used to represent and The model discussed in this document can be used to represent and
retrieve native TE topologies on a given TE system. retrieve Native TE topologies on a given TE system.
Consider the network topology depicted in Figure 5. 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 Figure 6. The data model defined in
this document can be used to represent and retrieve this TE topology.
| +---+ | +---+
| | | TE Node | | | TE Node
| +---+ | +---+
| ----- TE Link | ----- TE Link
o---------------------------------- o----------------------------------
+---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+
| R1|-------| R2|--------| R3|---------| R4|---------| R5| | R1|-------| R2|--------| R3|---------| R4|---------| R5|
+---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+
| / \ / \ / | / \ / \ /
| / \ / \ / | / \ / \ /
| / \ / \ / | / \ / \ /
| / \ / \ / | / \ / \ /
| / \ / \ / | / \ / \ /
+---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+
| R6|-------------| R7| | R8|---------| R9| | R6|-------------| R7| | R8|---------| R9|
+---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+
Figure 5a: Example Network Topology Figure 5: Example Network Topology
Consider the network topology depicted in Figure 5a. 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 Figure 5b. The data model proposed in this
document can be used to retrieve/represent this TE topology.
--------------- ---------------
| Native | | [ ] TE Node | Native | | [ ] TE Node
| TE-Topology | | +++ TE Link | TE Topology | | +++ TE Link
--------------- o-------------- --------------- o--------------
[R1] ++++ [R2] ++++ [R3] ++++ [R4] ++++ [R5] [R1] ++++ [R2] ++++ [R3] ++++ [R4] ++++ [R5]
+ + + + + + + + + + + +
+ + + + + + + + + + + +
+ + ++ ++ + + ++ ++
[R6] +++++++++ [R7] [R8] ++++ [R9] [R6] +++++++++ [R7] [R8] ++++ [R9]
Figure 5b: Native TE Topology as seen on Node R3 Figure 6: Native TE Topology as Seen on Node R3
Consider the case of the topology being split in a way that some Consider the case where the topology is split in a way that some
nodes participate in OSPF-TE while others participate in ISIS-TE nodes participate in OSPF-TE while others participate in ISIS-TE
(Figure 6a). An implementation MAY choose to construct separate TE (Figure 7). An implementation MAY choose to construct separate TE
Topologies based on the information source. The native TE Topologies topologies based on the information source. The Native TE topologies
constructed using only nodes and links that were learnt via a constructed using only nodes and links that were learned via a
specific information source are depicted in Figure 6b. The data model specific information source are depicted in Figure 8. The data model
proposed in this document can be used to retrieve/represent these TE defined in this document can be used to represent and retrieve these
topologies. TE topologies.
Similarly, the data model can be used to represent/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 retrieve and represent many such native TE Topologies.
: :
TE info distributed via ISIS-TE : TE info distributed via OSPF-TE TE Info Distributed via ISIS-TE : TE Info Distributed via OSPF-TE
: :
+---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+
| R1|-------| R2|--------| R3|---------| R4|---------| R5| | R1|-------| R2|--------| R3|---------| R4|---------| R5|
+---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+
| / : \ / \ / | / : \ / \ /
| / : \ / \ / | / : \ / \ /
| / : \ / \ / | / : \ / \ /
| / : \ / \ / | / : \ / \ /
| / : \ / \ / | / : \ / \ /
+---+ +---+ : +---+ +---+ +---+ +---+ : +---+ +---+
| R6|-------------| R7| : | R8|---------| R9| | R6|-------------| R7| : | R8|---------| R9|
+---+ +---+ : +---+ +---+ +---+ +---+ : +---+ +---+
: :
Figure 6a: Example Network Topology Figure 7: Example Split Network Topology
----------------------- : ----------------------- ----------------------- : -----------------------
|Native TE Topology | : |Native TE Topology | |Native TE Topology | : |Native TE Topology |
|Info-Source: ISIS-TE | : |Info-Source: OSPF-TE | |Info-Source: ISIS-TE | : |Info-Source: OSPF-TE |
----------------------- : ----------------------- ----------------------- : -----------------------
: :
[R1] ++++ [R2] ++++ [R3] : [R3'] ++++ [R4] ++++ [R5] [R1] ++++ [R2] ++++ [R3] : [R3'] ++++ [R4] ++++ [R5]
+ + : + + + + + + : + + + +
+ + : + + + + + + : + + + +
+ + : ++ ++ + + : ++ ++
[R6] +++++++++ [R7] : [R8] ++++ [R9] [R6] +++++++++ [R7] : [R8] ++++ [R9]
Figure 6b: Native TE Topologies as seen on Node R3 Figure 8: Native TE Topologies as Seen on Node R3
4.2. Customized TE Topologies 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.
Customized TE topology is a topology that was modified by the 4.2. Customized TE Topologies
A Customized TE topology is a topology that was modified by the
provider to honor a particular client's requirements or preferences. provider to honor a particular client's requirements or preferences.
The model discussed in this draft can be used to represent, retrieve The model discussed in this document can be used to represent,
and manipulate customized TE Topologies. The model allows the retrieve, and manipulate Customized TE topologies. The model allows
provider to present the network in abstract TE Terms on a per client the provider to present the network in abstract TE terms on a
basis. These customized topologies contain sufficient information for per-client basis. These customized topologies contain sufficient
the path computing client to select paths according to its policies. information for the client to compute and select paths according to
its policies.
Consider the network topology depicted in Figure 9. This is a
typical packet optical 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.
| +---+ /-\ | +---+ /-\
| | | Router ( ) WDM | | | Router ( ) WDM
| +---+ Node \-/ node | +---+ Node \-/ Node
| |
o---------------------------- o----------------------------
+---+ /-\ /-\ /-\ +---+ +---+ /-\ /-\ /-\ +---+
| R1|-------( A )--------( C )---------( E )---------| R3| | R1|-------( A )--------( C )---------( E )---------| R3|
+---+ \-/ \-/ \-/ +---+ +---+ \-/ \-/ \-/ +---+
/ \ / \ / \ / \
/ \ / \ / \ / \
/ \ / \ / \ / \
/ \ / \ / \ / \
/ \ / \ / \ / \
+---+ /-\ /-\ /-\ +---+ +---+ /-\ /-\ /-\ +---+
| R2|---------( B )---------( D )---------( F )---------| R4| | R2|---------( B )---------( D )---------( F )---------| R4|
+---+ \-/ \-/ \-/ +---+ +---+ \-/ \-/ \-/ +---+
Figure 7: Example packet optical topology Figure 9: Example Packet Optical Topology
Consider the network topology depicted in Figure 7. This is a typical The goal here is to augment the client's TE topology with a
packet optical transport deployment scenario where the WDM layer Customized TE topology provided by the WDM network. Given the
network domain serves as a Server Network Domain providing transport availability of the paths A-E, B-F, and B-E (Figure 10), a Customized
connectivity to the packet layer network Domain (Client Network TE topology as depicted in Figure 11 is provided to the client. This
Domain). Nodes R1, R2, R3 and R4 are IP routers that are connected to Customized TE topology is merged with the client's Native TE
an Optical WDM transport network. A, B, C, D, E and F are WDM nodes topology, and the resulting topology is depicted in Figure 12.
that constitute the Server Network Domain.
| ***** B-F WDM Path | ***** B-F WDM Path
| @@@@@ B-E WDM Path | @@@@@ B-E WDM Path
| $$$$$ A-E WDM Path | $$$$$ A-E WDM Path
o-------------------- o--------------------
+---+ /-\ $$$$$$$$ /-\ $$$$$$$$$ /-\ +---+ +---+ /-\ $$$$$$$$ /-\ $$$$$$$$$ /-\ +---+
| R1|-------( A )--------( C )---------( E )---------| R3| | R1|-------( A )--------( C )---------( E )---------| R3|
+---+ \-/ @\-/ @@@@@@@@@ \-/ +---+ +---+ \-/ @\-/ @@@@@@@@@ \-/ +---+
@/ \ / \ @/ \ / \
@/ \ / \ @/ \ / \
@/ \ / \ @/ \ / \
@/ \ / \ @/ \ / \
@/ \ / \ @/ \ / \
+---+ /-\ ********* /-\ ********* /-\ +---+ +---+ /-\ ********* /-\ ********* /-\ +---+
| R2|---------( B )---------( D )---------( F )---------| R4| | R2|---------( B )---------( D )---------( F )---------| R4|
+---+ \-/ \-/ \-/ +---+ +---+ \-/ \-/ \-/ +---+
Figure 8a: Paths within the provider domain
Figure 10: Paths within the Provider Domain
++++++++ [A] ++++++++++++++++++++ [E] +++++++++ ++++++++ [A] ++++++++++++++++++++ [E] +++++++++
+++++ +++++
++++ ++++
++++ ++++
++++ ++++
++++ ++++
++++++++ [B] ++++++++++++++++++++ [F] +++++++++ ++++++++ [B] ++++++++++++++++++++ [F] +++++++++
Figure 8b: Customized TE Topology provided to the Client Figure 11: Customized TE Topology Provided to the Client
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 (Figure 8a), a customized TE Topology as
depicted in Figure 8b 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 Figure 8c.
[R1] ++++++++ [A] ++++++++++++++++++++ [E] +++++++++ [R3] [R1] ++++++++ [A] ++++++++++++++++++++ [E] +++++++++ [R3]
+++++ +++++
++++ ++++
++++ ++++
++++ ++++
++++ ++++
[R2] ++++++++ [B] ++++++++++++++++++++ [F] +++++++++ [R4] [R2] ++++++++ [B] ++++++++++++++++++++ [F] +++++++++ [R4]
Figure 8c: Customized TE Topology merged with the Client's Native TE Figure 12: Customized TE Topology Merged with
Topology the Client's Native TE Topology
The data model proposed in this document can be used to The data model defined in this document can be used to represent,
retrieve/represent/manipulate the customized TE Topology depicted in retrieve, and manipulate the Customized TE topology depicted in
Figure 8b. Figure 11.
A customized TE topology is not necessarily an abstract TE topology. A Customized TE topology is not necessarily an abstract TE topology.
The provider may produce, for example, an abstract TE topology of The provider may produce, for example, an abstract TE topology of a
certain type (e.g. single-abstract-node-with-connectivity-matrix certain type (a single-abstract-node-with-connectivity-matrix
topology, a border-nodes-connected-via-mesh-of-abstract-links topology, a border-nodes-connected-via-mesh-of-abstract-links
topology, etc.) and expose it to all/some clients in expectation that topology, etc.) and expose it to all or some clients in the
the clients will use it without customization. expectation that the clients will use it without customization. On
On the other hand, a client may request a customized version of the the other hand, a client may request a customized version of the
provider's native TE topology (e.g. by requesting removal of TE links provider's Native TE topology (e.g., by requesting the removal of TE
which belong to certain layers, are too slow, not protected and/or links that belong to certain layers, are too slow, are not protected,
have a certain affinity). Note that the resulting TE topology will and/or have a certain affinity). Note that the resulting TE topology
not be abstract (because it will not contain abstract elements), but will not be abstract (because it will not contain abstract elements)
customized (modified upon client's instructions). but will be customized (modified upon the client's instructions).
The client ID field in the TE topology identifier (Section 5.4. ) The client ID field in the TE topology identifier (Section 5.4)
indicates which client the TE topology is customized for. Although an indicates which client the TE topology is customized for. Although
authorized client MAY receive a TE topology with the client ID field an authorized client MAY receive a TE topology with the client ID
matching some other client, the client can customize only TE field matching some other client, the client can customize only TE
topologies with the client ID field either 0 or matching the ID of topologies with the client ID field either set to 0 or matching the
the client in question. If the client starts reconfiguration of a ID of the client in question. If the client starts the
topology its client ID will be automatically set in the topology ID reconfiguration of a topology, its client ID will be automatically
field for all future configurations and updates wrt. the topology in set in the topology ID field for all future configurations and
question. updates with regard to the topology in question.
The provider MAY tell the client that a given TE topology cannot be The provider, by setting its own ID in the client ID field of the
re-negotiated, by setting its own (provider's) ID in the client ID topology ID, MAY tell the client that a given TE topology cannot be
field of the topology ID. renegotiated.
Even though this data model allows to access TE topology information Even though this data model allows the access of TE topology
across clients, implementations MAY restrict access for particular information across clients, implementations MAY restrict access for
clients to particular data fields. The Network Configuration Access particular clients to particular data fields. The Network
Control Model (NACM) [RFC8341] provides such a mechanism. Configuration Access Control Model (NACM) [RFC8341] provides such a
mechanism.
4.3. Merging TE Topologies Provided by Multiple Providers 4.3. Merging TE Topologies Provided by Multiple Providers
A client may receive TE topologies provided by multiple providers, A client may receive TE topologies provided by multiple providers,
each of which managing a separate domain of multi-domain network. In each of which manages a separate domain of a multi-domain network.
order to make use of said topologies, the client is expected to merge In order to make use of said topologies, the client is expected to
the provided TE topologies into one or more client's native TE merge the provided TE topologies into one or more of its own Native
topologies, each of which homogeneously representing the multi-domain TE topologies, each of which homogeneously represents the multi-
network. This makes it possible for the client to select end-to-end domain network. This makes it possible for the client to select end-
TE paths for its services traversing multiple domains. to-end TE paths for its services traversing multiple domains.
In particular, the process of merging TE topologies includes: In particular, the process of merging TE topologies includes:
- Identifying neighboring domains and locking their topologies * Identifying neighboring domains and locking their topologies
horizontally by connecting their inter-domain open-ended TE links; horizontally by connecting their inter-domain open-ended TE links.
- Renaming TE node, link, and SRLG IDs to ones allocated from a
separate name space; this is necessary because all TE topologies * Renaming TE node IDs, link IDs, and SRLG IDs to IDs allocated from
are considered to be, generally speaking, independent with a a separate namespace; this is necessary because all TE topologies
possibility of clashes among TE node, link or SRLG IDs; are considered to be, generally speaking, independent, and clashes
- Locking, vertically, TE topologies associated with different layer among TE node IDs, link IDs, or SRLG IDs are possible.
networks, according to provided topology inter-layer locks; this is
to facilitate inter-layer path computations across multiple TE * Locking, vertically, TE topologies associated with different layer
topologies provided by the same topology provider. 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 topology provider.
Figure 13 illustrates the process whereby the client merges the TE
topologies furnished by its providers.
/---\ +---+ +---+ +---+ +---+ /---\ /---\ +---+ +---+ +---+ +---+ /---\
|s3 |------|S13|----|S15|------|S23|----|S25|------|C21| |C11|------|S13|----|S15|------|S23|----|S25|------|C21|
\---/ +---+\ +---+ +---+ /+---+ \---/ \---/ +---+\ +---+ +---+ /+---+ \---/
\ / \ /
\ / \ /
\+---+ +---+/ +---+ /---\ \+---+ +---+/ +---+ /---\
|S18|------|S24| |S28|------|C22| |S18|------|S24| |S28|------|C22|
+---+ +---+\ /+---+ \---/ +---+ +---+\ /+---+ \---/
\/ \/
/\ /\
/---\ +---+ +---+ +---+/ \+---+ /---\ /---\ +---+ +---+ +---+/ \+---+ /---\
|C12|------|S19|----|S17|------|S29|----|S27|------|C23| |C12|------|S19|----|S17|------|S29|----|S27|------|C23|
\---/ +---+ +---+ +---+ +---+ \---/ \---/ +---+ +---+ +---+ +---+ \---/
Domain 1 TE Topology Domain 2 TE Topology Domain 1 TE Topology Domain 2 TE Topology
+---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+
-----|S13|----|S15|---- ----|S23|----|S25|---- -----|S13|----|S15|---- ----|S23|----|S25|----
+---+\ +---+ +---+ /+---+ +---+\ +---+ +---+ /+---+
\ / \ /
\ / \ /
\+---+ +---+/ +---+ \+---+ +---+/ +---+
|S18|---- ----|S24| |S28|---- |S18|---- ----|S24| |S28|----
+---+ +---+\ /+---+ +---+ +---+\ /+---+
\/ \/
/\ /\
+---+ +---+ +---+/ \+---+ +---+ +---+ +---+/ \+---+
-----|S19|----|S17|---- ----|S29|----|S27|---- -----|S19|----|S17|---- ----|S29|----|S27|----
+---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+
Figure 9: Merging Domain TE Topologies Figure 13: Merging Domain TE Topologies: An Example
Figure 9 illustrates the process of merging, by the client, of TE In Figure 13, each of the two providers caters to the client
topologies provided by the client's providers. In the Figure, each of (abstract or Native) TE topology, describing the network domain under
the two providers caters to the client (abstract or native) TE the respective provider's control. The client, by consulting such
topology, describing the network domain under the respective attributes of the inter-domain TE links as inter-domain plug IDs or
provider's control. The client, by consulting the attributes of the remote TE node IDs / link IDs (as defined by the TE topology model),
inter-domain TE links - such as inter-domain plug IDs or remote TE is able to determine that:
node/link IDs (as defined by the TE Topology model) - is able to
determine that:
a) the two domains are adjacent and are inter-connected via three 1. the two domains are adjacent and are interconnected via three
inter-domain TE links, and; inter-domain TE links, and
b) each domain is connected to a separate customer site, connecting 2. each domain is connected to a separate customer site, connecting
the left domain in the Figure to customer devices C-11 and C-12, the domain on the left in the figure to customer devices C11 and
and the right domain to customer devices C-21, C-22 and C-23. C12, and the domain on the right to customer devices C21, C22,
and C23.
Therefore, the client inter-connects the open-ended TE links, as Therefore, the client interconnects the open-ended TE links, as shown
shown on the upper part of the Figure. on the upper part of the figure.
As mentioned, one way to inter-connect the open-ended inter-domain TE As mentioned previously, one way to interconnect the open-ended
links of neighboring domains is to mandate the providers to specify inter-domain TE links of neighboring domains is to mandate that the
remote nodeID/linkID attribute in the provided inter-domain TE links. providers specify a remote node ID / link ID attribute in the
This, however, may prove to be not flexible. For example, the provided inter-domain TE links. However, this may prove not to be
providers may not know the respective remote nodeIDs/ linkIDs. More flexible. For example, the providers may not know the respective
importantly, this option does not allow for the client to mix-n-match remote node IDs / link IDs. More importantly, this option does not
multiple (more than one) topologies catered by the same providers allow the client to mix and match multiple topologies (more than one
(see below). Another, more flexible, option to resolve the open-ended topology) catered by the same providers (see below). Another option
inter-domain TE links is by annotating them with the inter-domain (which is more flexible) for resolving the open-ended inter-domain TE
plug ID attribute. Inter-domain plug ID is a network-wide unique links is to annotate them with the inter-domain plug ID attribute.
number that identifies on the network a connectivity supporting a The inter-domain plug ID is a network-wide unique number that
given inter-domain TE link. Instead of specifying remote node ID/link identifies on the network a connection that supports a given inter-
ID, an inter-domain TE link may provide a non-zero inter-domain plug domain TE link. Instead of specifying a remote node ID / link ID, an
ID. It is expected that two neighboring domain TE topologies inter-domain TE link may provide a non-zero inter-domain plug ID. It
(provided by separate providers) will have each at least one open- is expected that two neighboring domain TE topologies (provided by
ended inter-domain TE link with an inter-domain plug ID matching to separate providers) will each have at least one open-ended inter-
one provided by its neighbor. For example, the inter-domain TE link domain TE link with an inter-domain plug ID matching an ID provided
originating from node S15 of the Domain 1 TE topology (Figure 9) and by its neighbor. For example, the inter-domain TE link originating
the inter-domain TE link coming from node S23 of Domain 2 TE topology from node S15 of the Domain 1 TE topology (Figure 13) and the inter-
may specify matching inter-domain plug ID (e.g. 175344). This allows domain TE link coming from node S23 of the Domain 2 TE topology may
for the client to identify adjacent nodes in the separate neighboring specify a matching inter-domain plug ID (e.g., 175344). This allows
TE topologies and resolve the inter-domain TE links connecting them the client to identify adjacent nodes in the separate neighboring TE
regardless of their respective nodeIDs/linkIDs (which, as mentioned, topologies and resolve the inter-domain TE links connecting them,
could be allocated from independent name spaces). Inter-domain plug regardless of their respective node IDs / link IDs (which, as
IDs may be assigned and managed by a central network authority. mentioned previously, could be allocated from independent
Alternatively, inter-domain plug IDs could be dynamically auto- namespaces). Inter-domain plug IDs may be assigned and managed by a
discovered (e.g. via LMP protocol). central network authority. Alternatively, inter-domain plug IDs
could be dynamically autodiscovered (e.g., via the Link Management
Protocol (LMP)).
Furthermore, the client renames the TE nodes, links and SRLGs offered Furthermore, the client renames the TE nodes, links, and SRLGs
in the abstract TE topologies by assigning to them IDs allocated from offered in the abstract TE topologies by assigning to them IDs
a separate name space managed by the client. Such renaming is allocated from a separate namespace managed by the client. Such
necessary, because the two abstract TE topologies may have their own renaming is necessary, because the two abstract TE topologies may
name spaces, generally speaking, independent one from another; hence, have their own namespaces, generally speaking, independent one from
ID overlaps/clashes are possible. For example, both TE topologies another; hence, ID overlaps/clashes are possible. For example, both
have TE nodes named S7, which, after renaming, appear in the merged TE topologies have TE nodes named S7, which, after renaming, appear
TE topology as S17 and S27, respectively. in the merged TE topology as S17 and S27, respectively.
Once the merging process is complete, the client can use the merged Once the merging process is complete, the client can use the merged
TE topology for path computations across both domains, for example, TE topology for path computations across both domains -- for example,
to compute a TE path connecting C-11 to C-23. to compute a TE path connecting C11 to C23.
4.4. Dealing with Multiple Abstract TE Topologies Provided by the Same 4.4. Dealing with Multiple Abstract TE Topologies Provided by the Same
Provider Provider
Domain 1 Abstract TE Topology 1 Domain 2 Abstract TE Topology 1 Based on local configuration, templates, 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.
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 to mix and match multiple abstract TE
topologies provided by each or some of the providers, as well as how
to merge them into the client's Native 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 Figure 13, the client may merge the
abstract TE topologies received from the two providers, as shown in
Figure 14, into the client's additional Native TE topologies, as
shown in Figure 15.
Domain 1 Abstract TE Topology 1 Domain 2 Abstract TE Topology 1
+---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+
-----|S13|----|S15|---- ----|S23|----|S25|---- -----|S13|----|S15|---- ----|S23|----|S25|----
+---+\ +---+ +---+ /+---+ +---+\ +---+ +---+ /+---+
\ / \ /
\ / \ /
\+---+ +---+/ +---+ \+---+ +---+/ +---+
|S18|---- ----|S24| |S28|---- |S18|---- ----|S24| |S28|----
+---+ +---+\ /+---+ +---+ +---+\ /+---+
\/ \/
/\ /\
+---+ +---+ +---+/ \+---+ +---+ +---+ +---+/ \+---+
-----|S19|----|S17|---- ----|S29|----|S27|---- -----|S19|----|S17|---- ----|S29|----|S27|----
+---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+
Domain 1 Abstract TE Topology 1 Domain 2 Abstract TE Topology 1 Domain 1 Abstract TE Topology 2 Domain 2 Abstract TE Topology 2
+------------+ +------------+ +------------+ +------------+
-----| |---- ----| |---- -----| |---- ----| |----
| | | | | | | |
| AN1 |---- ----| AN1 |---- | AN1 |---- ----| AN1 |----
| | | | | | | |
-----| |---- ----| |---- -----| |---- ----| |----
+------------+ +------------+ +------------+ +------------+
Figure 10: Merging Domain TE Topologies Figure 14: Merging Domain TE Topologies: Another Example
Based on local configuration, templates 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.
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 to mix-and-match multiple abstract TE
topologies provided by each or some of the providers, as well as how
to merge them into the client's native 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 Figure 9, the client may merge the abstract TE
topologies received from the two providers, as shown in Figure 10,
into the client's additional native TE topologies, as shown in Figure
11.
Note that allowing for the client mix-n-matching of multiple TE
topologies assumes that inter-domain plug IDs (rather than remote
nodeID/linkID) option is used for identifying neighboring domains and
inter-domain TE link resolution.
Client's Merged TE Topology 2 Client's Merged TE Topology 2
/---\ +------------+ +------------+ /---\ /---\ +------------+ +------------+ /---\
|s3 |------| |------| |------|C21| |C11|------| |------| |------|C21|
\---/ | | | | \---/ \---/ | | | | \---/
| | | | | | | |
| | | | | | | |
| | | | /---\ | | | | /---\
| AN11 |------| AN21 |------|C22| | AN11 |------| AN21 |------|C22|
| | | | \---/ | | | | \---/
| | | | | | | |
| | | | | | | |
/---\ | | | | /---\ /---\ | | | | /---\
|C12|------| |------| |------|C23| |C12|------| |------| |------|C23|
\---/ +------------+ +------------+ \---/ \---/ +------------+ +------------+ \---/
Client's Merged TE Topology 3 Client's Merged TE Topology 3
/---\ +------------+ +---+ +---+ /---\ /---\ +------------+ +---+ +---+ /---\
|s3 |------| |------|S23|----|S25|------|C21| |C11|------| |------|S23|----|S25|------|C21|
\---/ | | +---+ /+---+ \---/ \---/ | | +---+ /+---+ \---/
| | / | | /
| | / | | /
| | +---+/ +---+ /---\ | | +---+/ +---+ /---\
| AN11 |------|S24| |S28|------|C22| | AN11 |------|S24| |S28|------|C22|
| | +---+\ /+---+ \---/ | | +---+\ /+---+ \---/
| | \/ | | \/
| | /\ | | /\
/---\ | | +---+/ \+---+ /---\ /---\ | | +---+/ \+---+ /---\
|C12|------| |------|S29|----|S27|------|C23| |C12|------| |------|S29|----|S27|------|C23|
\---/ +------------+ +---+ +---+ \---/ \---/ +------------+ +---+ +---+ \---/
Figure 11: Multiple Native (Merged) Client's TE Topologies Figure 15: Multiple Native (Merged) Client's TE Topologies
It is important to note that each of the three native (merged) TE 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.
It is important to note that each of the three Native (merged) TE
topologies could be used by the client for computing TE paths for any topologies could be used by the client for computing TE paths for any
of the multi-domain services. The choice as to which topology to use of the multi-domain services. The choice of which topology to use
for a given service depends on the service parameters/requirements for a given service depends on the service parameters/requirements,
and the topology's style, optimization criteria and the level of the topology's style and optimization criteria, and the level of
details. detail.
5. Modeling Considerations 5. Modeling Considerations
5.1. Network topology building blocks 5.1. Network Topology Building Blocks
The network topology building blocks are discussed in [RFC8345]. The The network topology building blocks are discussed in [RFC8345]. The
TE Topology model proposed in this document augments and uses the TE topology model defined in this document augments and uses the
ietf-network-topology module defined in [RFC8345]. "ietf-network-topology" module defined in [RFC8345].
+------------------------+ +------------------------+
| | | Network Topology Model |
| Network Topology Model | | (ietf-network-topology)|
| (ietf-network-topology)| +------------------------+
+------------------------+ |
| |
| |
| V
V +------------------------+
+------------------------+ | TE Topology |
| TE Topology | | Model |
| Model | +------------------------+
| |
+------------------------+
Figure 12: Augmenting the Network Topology Model Figure 16: Augmenting the Network Topology Model
5.2. Technology agnostic TE Topology model 5.2. Technology-Agnostic TE Topology Model
The TE Topology model proposed in this document is meant to be The TE topology model defined in this document is meant to be network
network technology agnostic. Other technology specific TE Topology technology agnostic. Other technology-specific TE topology models
models can augment and use the building blocks provided by the can augment and use the building blocks provided by this model, as
proposed model. illustrated in Figure 17.
+-----------------------------+ +-----------------------------+
| TE Topology Model | | TE Topology Model |
| (Defined in This Document) | +-----------------------------+
+-----------------------------+ |
| +-------------+-------------+-------------+
+-------------+-------------+-------------+ | | | |
| | | | V V V V
V V V V +-------------+ +-------------+
+------------+ +------------+ | Technology- | | Technology- |
| Technology | | Technology | | Specific | ...................... | Specific |
| Specific | ...................... | Specific | | TE Topology | | TE Topology |
| TE Topology| | TE Topology| | Model 1 | | Model n |
| Model 1 | | Model n | +-------------+ +-------------+
+------------+ +------------+
Figure 13: Augmenting the Technology agnostic TE Topology model Figure 17: Augmenting the Technology-Agnostic TE Topology Model
5.3. Model Structure 5.3. Model Structure
The high-level model structure proposed by this document is as shown The high-level model structure defined by this document is as shown
below: below:
module: ietf-te-topology module: ietf-te-topology
augment /nw:networks/nw:network/nw:network-types: augment /nw:networks/nw:network/nw:network-types:
+--rw te-topology! +--rw te-topology!
augment /nw:networks: augment /nw:networks:
+--rw te! +--rw te!
+--rw templates +--rw templates
+--rw node-template* [name] {template}? +--rw node-template* [name] {template}?
| ............ | ............
+--rw link-template* [name] {template}? +--rw link-template* [name] {template}?
............ ............
augment /nw:networks/nw:network: augment /nw:networks/nw:network:
+--rw te-topology-identifier +--rw te-topology-identifier
| +--rw provider-id? te-global-id | +--rw provider-id? te-global-id
| +--rw client-id? te-global-id | +--rw client-id? te-global-id
| +--rw topology-id? te-topology-id | +--rw topology-id? te-topology-id
+--rw te! +--rw te!
| ............ | ............
augment /nw:networks/nw:network/nw:node: augment /nw:networks/nw:network/nw:node:
+--rw te-node-id? te-types:te-node-id +--rw te-node-id? te-types:te-node-id
+--rw te! +--rw te!
| ............ | ............
+--rw tunnel-termination-point* [tunnel-tp-id] +--rw tunnel-termination-point* [tunnel-tp-id]
+--rw tunnel-tp-id binary +--rw tunnel-tp-id binary
| ............ | ............
+--rw supporting-tunnel-termination-point* [node-ref tunnel- +--rw supporting-tunnel-termination-point*
tp-ref] [node-ref tunnel-tp-ref]
| ............ | ............
augment /nw:networks/nw:network/nt:link: augment /nw:networks/nw:network/nt:link:
+--rw te! +--rw te!
| .......... | ..........
augment /nw:networks/nw:network/nw:node/nt:termination-point: augment /nw:networks/nw:network/nw:node/nt:termination-point:
+--rw te-tp-id? te-types:te-tp-id +--rw te-tp-id? te-types:te-tp-id
+--rw te! +--rw te!
| ............ | ............
5.4. Topology Identifiers 5.4. Topology Identifiers
The TE-Topology is uniquely identified by a key that has 3 The TE topology is uniquely identified by a key that has three
constituents - topology-id, provider-id and client-id. The constituents -- "topology-id", "provider-id", and "client-id". The
combination of provider-id and topology-id uniquely identifies a combination of "provider-id" and "topology-id" uniquely identifies a
native TE Topology on a given provider. The client-id is used only Native TE topology on a given provider. "client-id" is used only
when Customized TE Topologies come into play; a value of "0" is used when Customized TE topologies come into play; a "client-id" value of
as the client-id for native TE Topologies. "0" is used for Native TE topologies.
augment /nw:networks/nw:network: augment /nw:networks/nw:network:
+--rw te-topology-identifier +--rw te-topology-identifier
| +--rw provider-id? te-global-id | +--rw provider-id? te-global-id
| +--rw client-id? te-global-id | +--rw client-id? te-global-id
| +--rw topology-id? te-topology-id | +--rw topology-id? te-topology-id
+--rw te! +--rw te!
| ............ | ............
5.5. Generic TE Link Attributes 5.5. Generic TE Link Attributes
The model covers the definitions for generic TE Link attributes - The model covers the definitions for generic TE link attributes --
bandwidth, admin groups, SRLGs, switching capabilities, TE metric bandwidth, administrative groups, SRLGs, switching capabilities, TE
extensions etc. metric extensions, etc.
+--rw te-link-attributes +--rw te-link-attributes
..................... .....................
+--rw admin-status? te-admin-status +--rw admin-status? te-admin-status
| ..................... | .....................
+--rw link-index? uint64 +--rw link-index? uint64
+--rw administrative-group? te-types:admin-groups +--rw administrative-group? te-types:admin-groups
+--rw link-protection-type? enumeration +--rw link-protection-type? enumeration
+--rw max-link-bandwidth? te-bandwidth +--rw max-link-bandwidth? te-bandwidth
+--rw max-resv-link-bandwidth? te-bandwidth +--rw max-resv-link-bandwidth? te-bandwidth
+--rw unreserved-bandwidth* [priority] +--rw unreserved-bandwidth* [priority]
| ..................... | .....................
+--rw te-default-metric? uint32 +--rw te-default-metric? uint32
| ..................... | .....................
+--rw te-srlgs +--rw te-srlgs
+--rw te-nsrlgs {nsrlg}? ..................... +--rw te-nsrlgs {nsrlg}? .....................
5.6. Generic TE Node Attributes 5.6. Generic TE Node Attributes
The model covers the definitions for generic TE Node attributes. The model covers the definitions for generic TE node attributes.
The definition of a generic connectivity matrix is shown below: The definition of a generic connectivity matrix is shown below:
+--rw te-node-attributes +--rw te-node-attributes
........... ...........
+--rw connectivity-matrices +--rw connectivity-matrices
........... ...........
| +--rw connectivity-matrix* [id] | +--rw connectivity-matrix* [id]
| | +--rw id uint32 | | +--rw id uint32
| | +--rw from | | +--rw from
skipping to change at page 29, line 4 skipping to change at line 1208
The definition of a TTP Local Link Connectivity List is shown below: The definition of a TTP Local Link Connectivity List is shown below:
+--rw tunnel-termination-point* [tunnel-tp-id] +--rw tunnel-termination-point* [tunnel-tp-id]
+--rw tunnel-tp-id binary +--rw tunnel-tp-id binary
+--rw admin-status? te-types:te-admin-status +--rw admin-status? te-types:te-admin-status
+--rw name? string +--rw name? string
+--rw switching-capability? identityref +--rw switching-capability? identityref
+--rw encoding? identityref +--rw encoding? identityref
+--rw inter-layer-lock-id* uint32 +--rw inter-layer-lock-id* uint32
+--rw protection-type? Identityref +--rw protection-type? identityref
+--rw client-layer-adaptation +--rw client-layer-adaptation
........... ...........
+--rw local-link-connectivities +--rw local-link-connectivities
........... ...........
| +--rw local-link-connectivity* [link-tp-ref] | +--rw local-link-connectivity* [link-tp-ref]
| +--rw link-tp-ref leafref | +--rw link-tp-ref leafref
| +--rw label-restrictions | +--rw label-restrictions
........... ...........
| +--rw is-allowed? boolean | +--rw is-allowed? boolean
| +--rw underlay {te-topology-hierarchy}? | +--rw underlay {te-topology-hierarchy}?
........... ...........
| +--rw path-constraints | +--rw path-constraints
........... ...........
| +--rw optimizations | +--rw optimizations
........... ...........
| +--ro path-properties | +--ro path-properties
........... ...........
+--rw supporting-tunnel-termination-point* [node-ref tunnel-tp- +--rw supporting-tunnel-termination-point*
ref] [node-ref tunnel-tp-ref]
+--rw node-ref inet:uri +--rw node-ref inet:uri
+--rw tunnel-tp-ref binary +--rw tunnel-tp-ref binary
The attributes directly under container connectivity-matrices are the The attributes directly under container "connectivity-matrices" are
default attributes for all connectivity-matrix entries when the per the default attributes for all connectivity matrix entries when the
entry corresponding attribute is not specified. When a per entry per-entry corresponding attribute is not specified. When a per-entry
attribute is specified, it overrides the corresponding attribute attribute is specified, it overrides the corresponding attribute
directly under the container connectivity-matrices. The same rule directly under the container "connectivity-matrices". The same rule
applies to the attributes directly under container local-link- applies to the attributes directly under container
connectivities. "local-link-connectivities".
Each TTP (Tunnel Termination Point) MAY be supported by one or more Each TTP MAY be supported by one or more supporting TTPs. If the TE
supporting TTPs. If the TE node hosting the TTP in question refers to node hosting the TTP in question refers to a supporting TE node, then
a supporting TE node, then the supporting TTPs are hosted by the the supporting TTPs are hosted by the supporting TE node. If the TE
supporting TE node. If the TE node refers to an underlay TE topology, node refers to an underlay TE topology, the supporting TTPs are
the supporting TTPs are hosted by one or more specified TE nodes of hosted by one or more specified TE nodes of the underlay TE topology.
the underlay TE topology.
5.7. TED Information Sources 5.7. TED Information Sources
The model allows each TE topological element to have multiple TE The model allows each TE topological element to have multiple TE
information sources (OSPF-TE, ISIS-TE, BGP-LS, User-Configured, information sources (OSPF-TE, ISIS-TE, Border Gateway Protocol - Link
System-Processed, Other). Each information source is associated with State (BGP-LS), user-configured, system-processed, other). Each
a credibility preference to indicate precedence. In scenarios where a information source is associated with a credibility preference to
customized TE Topology is merged into a Client's native TE Topology, indicate precedence. In scenarios where a Customized TE topology is
the merged topological elements would point to the corresponding merged into a client's Native TE topology, the merged topological
customized TE Topology as its information source. elements would point to the corresponding Customized TE topology as
its information source.
augment /nw:networks/nw:network/nw:node: augment /nw:networks/nw:network/nw:node:
+--rw te! +--rw te!
........... ...........
+--ro information-source? te-info-source +--ro information-source? te-info-source
+--ro information-source-instance? string +--ro information-source-instance? string
+--ro information-source-state +--ro information-source-state
| +--ro credibility-preference? uint16 | +--ro credibility-preference? uint16
| +--ro logical-network-element? string | +--ro logical-network-element? string
| +--ro network-instance? string | +--ro network-instance? string
| +--ro topology | +--ro topology
| +--ro node-ref? leafref | +--ro node-ref? leafref
| +--ro network-ref? leafref | +--ro network-ref? leafref
+--ro information-source-entry* +--ro information-source-entry*
| [information-source information-source-instance] | [information-source information-source-instance]
| +--ro information-source te-info-source | +--ro information-source te-info-source
| +--ro information-source-instance string | +--ro information-source-instance string
............ ............
augment /nw:networks/nw:network/nt:link: augment /nw:networks/nw:network/nt:link:
+--rw te! +--rw te!
........... ...........
+--ro information-source? te-info-source +--ro information-source? te-info-source
+--ro information-source-instance? string +--ro information-source-instance? string
+--ro information-source-state +--ro information-source-state
| +--ro credibility-preference? uint16 | +--ro credibility-preference? uint16
| +--ro logical-network-element? string | +--ro logical-network-element? string
| +--ro network-instance? string | +--ro network-instance? string
| +--ro topology | +--ro topology
| +--ro link-ref? leafref | +--ro link-ref? leafref
| +--ro network-ref? leafref | +--ro network-ref? leafref
+--ro information-source-entry* +--ro information-source-entry*
| [information-source information-source-instance] | [information-source information-source-instance]
| +--ro information-source te-info-source | +--ro information-source te-info-source
| +--ro information-source-instance string | +--ro information-source-instance string
............ ............
5.8. Overlay/Underlay Relationship 5.8. Overlay/Underlay Relationship
The model captures overlay and underlay relationship for TE The model captures the overlay and underlay relationship for TE
nodes/links. For example - in networks where multiple TE Topologies nodes/links. For example, in networks where multiple TE topologies
are built hierarchically, this model allows the user to start from a are built hierarchically, this model allows the user to start from a
specific topological element in the top most topology and traverse specific topological element in the topmost topology and traverse all
all the way down to the supporting topological elements in the bottom the way down to the supporting topological elements in the bottommost
most topology. topology.
This relationship is captured via the "underlay-topology" field for This relationship is captured via the "underlay-topology" field for
the node and via the "underlay" field for the link. The use of these the node and via the "underlay" field for the link. The use of these
fields is optional and this functionality is tagged as a "feature" fields is optional, and this functionality is tagged as a "feature"
("te-topology-hierarchy"). ("te-topology-hierarchy").
augment /nw:networks/nw:network/nw:node: augment /nw:networks/nw:network/nw:node:
+--rw te-node-id? te-types:te-node-id +--rw te-node-id? te-types:te-node-id
+--rw te! +--rw te!
+--rw te-node-template* leafref {template}? +--rw te-node-template* leafref {template}?
+--rw te-node-attributes +--rw te-node-attributes
| +--rw admin-status? te-types:te-admin-status | +--rw admin-status? te-types:te-admin-status
| | .................... | | ....................
| +--rw underlay-topology {te-topology-hierarchy}? | +--rw underlay-topology {te-topology-hierarchy}?
| +--rw network-ref? leafref | +--rw network-ref? leafref
augment /nw:networks/nw:network/nt:link: augment /nw:networks/nw:network/nt:link:
+--rw te! +--rw te!
+--rw te-link-attributes +--rw te-link-attributes
| .................... | ....................
| +--rw underlay {te-topology-hierarchy}? | +--rw underlay {te-topology-hierarchy}?
| | +--rw enabled? boolean | | +--rw enabled? boolean
| | +--rw primary-path | | +--rw primary-path
| | | +--rw network-ref? leafref | | | +--rw network-ref? leafref
| | | .................... | | | ....................
| | +--rw backup-path* [index] | | +--rw backup-path* [index]
| | | +--rw index uint32 | | | +--rw index uint32
| | | +--rw network-ref? leafref | | | +--rw network-ref? leafref
| | | .................... | | | ....................
| | +--rw protection-type? identityref | | +--rw protection-type? identityref
| | +--rw tunnel-termination-points | | +--rw tunnel-termination-points
| | | +--rw source? binary | | | +--rw source? binary
| | | +--rw destination? binary | | | +--rw destination? binary
| | +--rw tunnels | | +--rw tunnels
| | | .................... | | | ....................
5.9. Templates 5.9. Templates
The data model provides the users with the ability to define The data model provides users with the ability to define templates
templates and apply them to link and node configurations. The use of and apply them to link and node configurations. The use of the
"template" configuration is optional and this functionality is tagged "template" configuration is optional, and this functionality is
as a "feature" ("template"). tagged as a "feature" ("template").
augment /nw:networks/nw:network/nw:node: augment /nw:networks/nw:network/nw:node:
+--rw te-node-id? te-types:te-node-id +--rw te-node-id? te-types:te-node-id
+--rw te! +--rw te!
+--rw te-node-template* +--rw te-node-template*
| -> ../../../../te/templates/node-template/name | -> ../../../../te/templates/node-template/name
| {template}? | {template}?
augment /nw:networks/nw:network/nt:link: augment /nw:networks/nw:network/nt:link:
+--rw te! +--rw te!
+--rw te-link-template* +--rw te-link-template*
| -> ../../../../te/templates/link-template/name | -> ../../../../te/templates/link-template/name
| {template}? | {template}?
augment /nw:networks: augment /nw:networks:
+--rw te! +--rw te!
+--rw templates +--rw templates
+--rw node-template* [name] {template}? +--rw node-template* [name] {template}?
| +--rw name | +--rw name
| | te-types:te-template-name | | te-types:te-template-name
| +--rw priority? uint16 | +--rw priority? uint16
| +--rw reference-change-policy? enumeration | +--rw reference-change-policy? enumeration
| +--rw te-node-attributes | +--rw te-node-attributes
.......... ..........
+--rw link-template* [name] {template}? +--rw link-template* [name] {template}?
+--rw name +--rw name
| te-types:te-template-name | te-types:te-template-name
+--rw priority? uint16 +--rw priority? uint16
+--rw reference-change-policy? enumeration +--rw reference-change-policy? enumeration
+--rw te-link-attributes +--rw te-link-attributes
.......... ..........
Multiple templates can be specified to a configuration element. When Multiple templates can be specified for a configuration element.
two or more templates specify values for the same configuration When two or more templates specify values for the same configuration
field, the value from the template with the highest priority is used. 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 The range of the priority is from 0 to 65535, with a lower number
indicating a higher priority. The reference-change-policy specifies indicating a higher priority. The "reference-change-policy"
the action that needs to be taken when the template changes on a parameter specifies the action that needs to be taken when the
configuration element that has a reference to this template. The template changes on a configuration element that has a reference to
choices of action include taking no action, rejecting the change to this template. The choices of action include taking no action,
the template and applying the change to the corresponding rejecting the change to the template, and applying the change to the
configuration. corresponding configuration.
5.10. Scheduling Parameters 5.10. Scheduling Parameters
The model allows time scheduling parameters to be specified for each The model allows time-scheduling parameters to be specified for each
topological element or for the topology as a whole. These parameters topological element or for the topology as a whole. These parameters
allow the provider to present different topological views to the allow the provider to present different topological views to the
client at different time slots. The use of "scheduling parameters" is client at different time slots. The use of time-scheduling
optional. parameters is optional.
The YANG data model for configuration scheduling is defined in The YANG data model for configuration scheduling is defined in
[I-D.liu-netmod-yang-schedule], which allows specifying configuration [YANG-CFG-SCHED], which allows specifying configuration schedules
schedules without altering this data model. without altering this data model.
5.11. Notifications 5.11. Notifications
Notifications are a key component of any topology data model. Notifications are a key component of any topology data model.
[I-D.ietf-netconf-subscribed-notifications] and [RFC8639] and [RFC8641] define a subscription mechanism and a push
[I-D.ietf-netconf-yang-push] define a subscription and push mechanism mechanism for YANG datastores. These mechanisms currently allow the
for YANG datastores. This mechanism currently allows the user to: user to:
- Subscribe notifications on a per client basis * Subscribe to notifications on a per-client basis.
- Specify subtree filters or xpath filters so that only interested
contents will be sent.
- Specify either periodic or on-demand notifications.
6. Guidance for Writing Technology Specific TE Topology Augmentations * Specify subtree filters or XML Path Language (XPath) filters so
that only contents of interest will be sent.
The TE topology model defined in this document is technology agnostic * Specify either periodic or on-demand notifications.
as it defines concepts, abstractions and attributes that are common
across multiple network technologies. It is envisioned that this base
model will be widely used when defining technology specific TE
topology models for various layer networks.
[I-D.ietf-ccamp-wson-yang], [I-D.ietf-ccamp-otn-topo-yang], and
[I-D.ietf-teas-yang-l3-te-topo] are some examples of technology
specific TE Topology models. Writers of such models are encouraged to
augment the basic TE topology model's containers, such as TE
Topology, TE Node, TE Link, Link Termination Point (LTP), Tunnel
Termination Point (TTP), Bandwidth and Label with the layer specific
attributes instead of defining new containers.
Consider the following technology specific example-topology model: 6. Guidance for Writing Technology-Specific TE Topology Augmentations
The TE topology model defined in this document is technology
agnostic, as it defines concepts, abstractions, and attributes that
are common across multiple network technologies. It is envisioned
that this base model will be widely used when defining technology-
specific TE topology models for various layer networks. [YANG-WSON],
[YANG-OTN], and [YANG-L3] are some examples of technology-specific TE
topology models. Writers of such models are encouraged to augment
the basic TE topology model's containers, such as those for TE
topologies, TE nodes, TE links, Link Termination Points (LTPs),
Tunnel Termination Points (TTPs), bandwidth, and labels, with the
layer-specific attributes instead of defining new containers.
Consider the following technology-specific example-topology model:
module: example-topology module: example-topology
augment /nw:networks/nw:network/nw:network-types/tet:te-topology: augment /nw:networks/nw:network/nw:network-types/tet:te-topology:
+--rw example-topology! +--rw example-topology!
augment /nw:networks/nw:network/tet:te: augment /nw:networks/nw:network/tet:te:
+--rw attributes +--rw attributes
+--rw attribute-1? uint8 +--rw attribute-1? uint8
augment /nw:networks/nw:network/nw:node/tet:te augment /nw:networks/nw:network/nw:node/tet:te
/tet:te-node-attributes: /tet:te-node-attributes:
+--rw attributes +--rw attributes
skipping to change at page 34, line 21 skipping to change at line 1460
+--rw attribute-4? uint8 +--rw attribute-4? uint8
augment /nw:networks/nw:network/nw:node/nt:termination-point augment /nw:networks/nw:network/nw:node/nt:termination-point
/tet:te: /tet:te:
+--rw attributes +--rw attributes
+--rw attribute-5? uint8 +--rw attribute-5? uint8
augment /nw:networks/nw:network/nt:link/tet:te augment /nw:networks/nw:network/nt:link/tet:te
/tet:te-link-attributes: /tet:te-link-attributes:
+--rw attributes +--rw attributes
+--rw attribute-6? uint8 +--rw attribute-6? uint8
The technology specific TE bandwidth for this example topology can be The technology-specific TE bandwidth for this example topology can be
specified using the following augment statements: specified using the following augment statements:
augment /nw:networks/tet:te/tet:templates/tet:link-template augment /nw:networks/tet:te/tet:templates/tet:link-template
/tet:te-link-attributes /tet:te-link-attributes
/tet:interface-switching-capability/tet:max-lsp-bandwidth /tet:interface-switching-capability/tet:max-lsp-bandwidth
/tet:te-bandwidth/tet:technology: /tet:te-bandwidth/tet:technology:
+--:(example) +--:(example)
+--rw example +--rw example
+--rw bandwidth-1? uint32 +--rw bandwidth-1? uint32
augment /nw:networks/tet:te/tet:templates/tet:link-template augment /nw:networks/tet:te/tet:templates/tet:link-template
skipping to change at page 37, line 27 skipping to change at line 1587
+--:(example) +--:(example)
+--ro example +--ro example
+--ro bandwidth-1? uint32 +--ro bandwidth-1? uint32
augment /nw:networks/nw:network/nw:node/nt:termination-point/tet:te augment /nw:networks/nw:network/nw:node/nt:termination-point/tet:te
/tet:interface-switching-capability/tet:max-lsp-bandwidth /tet:interface-switching-capability/tet:max-lsp-bandwidth
/tet:te-bandwidth/tet:technology: /tet:te-bandwidth/tet:technology:
+--:(example) +--:(example)
+--rw example +--rw example
+--rw bandwidth-1? uint32 +--rw bandwidth-1? uint32
The technology specific TE label for this example topology can be The technology-specific TE label for this example topology can be
specified using the following augment statements: specified using the following augment statements:
augment /nw:networks/tet:te/tet:templates/tet:link-template augment /nw:networks/tet:te/tet:templates/tet:link-template
/tet:te-link-attributes/tet:underlay/tet:primary-path /tet:te-link-attributes/tet:underlay/tet:primary-path
/tet:path-element/tet:type/tet:label/tet:label-hop /tet:path-element/tet:type/tet:label/tet:label-hop
/tet:te-label/tet:technology: /tet:te-label/tet:technology:
+--:(example) +--:(example)
+--rw example +--rw example
+--rw label-1? uint32 +--rw label-1? uint32
augment /nw:networks/tet:te/tet:templates/tet:link-template augment /nw:networks/tet:te/tet:templates/tet:link-template
skipping to change at page 45, line 42 skipping to change at line 1930
+--ro example +--ro example
+--ro label-1? uint32 +--ro label-1? uint32
augment /nw:networks/nw:network/nt:link/tet:te augment /nw:networks/nw:network/nt:link/tet:te
/tet:information-source-entry/tet:label-restrictions /tet:information-source-entry/tet:label-restrictions
/tet:label-restriction/tet:label-end/tet:te-label /tet:label-restriction/tet:label-end/tet:te-label
/tet:technology: /tet:technology:
+--:(example) +--:(example)
+--ro example +--ro example
+--ro label-1? uint32 +--ro label-1? uint32
The YANG module to implement the above example topology can be seen The example YANG module that implements the above example topology is
in Appendix C. provided in Appendix C.
7. TE Topology YANG Module 7. TE Topology YANG Module
This module references [RFC1195], [RFC3209], [RFC3272], [RFC3471], This module references [RFC1195], [RFC3209], [RFC3272], [RFC3471],
[RFC3630], [RFC3785], [RFC4201], [RFC4202], [RFC4203], [RFC4206], [RFC3630], [RFC3785], [RFC4201], [RFC4202], [RFC4203], [RFC4206],
[RFC4872], [RFC5152], [RFC5212], [RFC5305], [RFC5316], [RFC5329], [RFC4872], [RFC5152], [RFC5212], [RFC5305], [RFC5316], [RFC5392],
[RFC5392], [RFC6001], [RFC6241], [RFC6991], [RFC7308], [RFC7471], [RFC6001], [RFC6241], [RFC6991], [RFC7308], [RFC7471], [RFC7579],
[RFC7579], [RFC7752], [RFC8345], and [I-D.ietf-teas-yang-te-types]. [RFC7752], [RFC8345], and [RFC8776].
<CODE BEGINS> file "ietf-te-topology@2019-02-07.yang" <CODE BEGINS> file "ietf-te-topology@2020-08-06.yang"
module ietf-te-topology { module ietf-te-topology {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-te-topology"; namespace "urn:ietf:params:xml:ns:yang:ietf-te-topology";
prefix tet;
prefix "tet";
import ietf-yang-types { import ietf-yang-types {
prefix "yang"; prefix yang;
reference "RFC 6991: Common YANG Data Types"; reference
"RFC 6991: Common YANG Data Types";
} }
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix inet;
reference "RFC 6991: Common YANG Data Types"; reference
"RFC 6991: Common YANG Data Types";
} }
import ietf-te-types { import ietf-te-types {
prefix "te-types"; prefix te-types;
reference reference
"I-D.ietf-teas-yang-te-types: Traffic Engineering Common YANG "RFC 8776: Common YANG Data Types for Traffic Engineering";
Types";
} }
import ietf-network { import ietf-network {
prefix "nw"; prefix nw;
reference "RFC 8345: A YANG Data Model for Network Topologies"; reference
"RFC 8345: A YANG Data Model for Network Topologies";
} }
import ietf-network-topology { import ietf-network-topology {
prefix "nt"; prefix nt;
reference "RFC 8345: A YANG Data Model for Network Topologies"; reference
"RFC 8345: A YANG Data Model for Network Topologies";
} }
organization organization
"IETF Traffic Engineering Architecture and Signaling (TEAS) "IETF Traffic Engineering Architecture and Signaling (TEAS)
Working Group"; Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/teas/> "WG Web: <https://datatracker.ietf.org/wg/teas/>
WG List: <mailto:teas@ietf.org> WG List: <mailto:teas@ietf.org>
Editor: Xufeng Liu Editor: Xufeng Liu
<mailto:xufeng.liu.ietf@gmail.com> <mailto:xufeng.liu.ietf@gmail.com>
Editor: Igor Bryskin Editor: Igor Bryskin
<mailto:Igor.Bryskin@huawei.com> <mailto:i_bryskin@yahoo.com>
Editor: Vishnu Pavan Beeram Editor: Vishnu Pavan Beeram
<mailto:vbeeram@juniper.net> <mailto:vbeeram@juniper.net>
Editor: Tarek Saad Editor: Tarek Saad
<mailto:tsaad@juniper.net> <mailto:tsaad@juniper.net>
Editor: Himanshu Shah Editor: Himanshu Shah
<mailto:hshah@ciena.com> <mailto:hshah@ciena.com>
Editor: Oscar Gonzalez De Dios Editor: Oscar Gonzalez de Dios
<mailto:oscar.gonzalezdedios@telefonica.com>"; <mailto:oscar.gonzalezdedios@telefonica.com>";
description description
"TE topology model for representing and manipulating technology "This YANG module defines a TE topology model for representing,
agnostic TE Topologies. retrieving, and manipulating technology-agnostic TE topologies.
Copyright (c) 2019 IETF Trust and the persons identified as Copyright (c) 2020 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents 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 RFC XXXX; see the This version of this YANG module is part of RFC 8795; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
revision "2019-02-07" { revision 2020-08-06 {
description "Initial revision"; description
reference "RFC XXXX: YANG Data Model for TE Topologies"; "Initial revision.";
// RFC Ed.: replace XXXX with actual RFC number and remove reference
// this note "RFC 8795: YANG Data Model for Traffic Engineering (TE)
Topologies";
} }
/* /*
* Features * Features
*/ */
feature nsrlg { feature nsrlg {
description description
"This feature indicates that the system supports NSRLG "This feature indicates that the system supports NSRLGs
(Not Sharing Risk Link Group)."; (Non-Shared Risk Link Groups).";
} }
feature te-topology-hierarchy { feature te-topology-hierarchy {
description description
"This feature indicates that the system allows underlay "This feature indicates that the system allows an underlay
and/or overlay TE topology hierarchy."; and/or overlay TE topology hierarchy.";
} }
feature template { feature template {
description description
"This feature indicates that the system supports "This feature indicates that the system supports
template configuration."; template configuration.";
} }
/* /*
skipping to change at page 48, line 37 skipping to change at line 2047
feature template { feature template {
description description
"This feature indicates that the system supports "This feature indicates that the system supports
template configuration."; template configuration.";
} }
/* /*
* Typedefs * Typedefs
*/ */
typedef geographic-coordinate-degree { typedef geographic-coordinate-degree {
type decimal64 { type decimal64 {
fraction-digits 8; fraction-digits 8;
} }
description description
"Decimal degree (DD) used to express latitude and longitude "Decimal degree (DD) used to express latitude and longitude
geographic coordinates."; geographic coordinates.";
} // geographic-coordinate-degree }
// geographic-coordinate-degree
typedef te-info-source { typedef te-info-source {
type enumeration { type enumeration {
enum "unknown" { enum unknown {
description "The source is unknown."; description
"The source is unknown.";
} }
enum "locally-configured" { enum locally-configured {
description "Configured entity."; description
"Configured entity.";
} }
enum "ospfv2" { enum ospfv2 {
description "OSPFv2."; description
"OSPFv2.";
} }
enum "ospfv3" { enum ospfv3 {
description "OSPFv3."; description
"OSPFv3.";
} }
enum "isis" { enum isis {
description "ISIS."; description
"IS-IS.";
} }
enum "bgp-ls" { enum bgp-ls {
description "BGP-LS."; description
"BGP-LS.";
reference reference
"RFC 7752: North-Bound Distribution of Link-State and "RFC 7752: North-Bound Distribution of Link-State and
Traffic Engineering (TE) Information Using BGP"; Traffic Engineering (TE) Information Using BGP";
} }
enum "system-processed" { enum system-processed {
description "System processed entity."; description
"System-processed entity.";
} }
enum "other" { enum other {
description "Other source."; description
"Other source.";
} }
} }
description description
"Describining the type of source that has provided the "Describes the type of source that has provided the
related information, and the source credibility."; related information, and the source's credibility.";
} // te-info-source }
// te-info-source
/* /*
* Groupings * Groupings
*/ */
grouping connectivity-matrix-entry-path-attributes { grouping connectivity-matrix-entry-path-attributes {
description description
"Attributes of connectivity matrix entry."; "Attributes of a connectivity matrix entry.";
leaf is-allowed { leaf is-allowed {
type boolean; type boolean;
description description
"true - switching is allowed, "'true' - switching is allowed;
false - switching is disallowed."; 'false' - switching is disallowed.";
} }
container underlay { container underlay {
if-feature te-topology-hierarchy; if-feature "te-topology-hierarchy";
description "Attributes of the te-link underlay."; description
"Attributes of the TE link underlay.";
reference reference
"RFC 4206: Label Switched Paths (LSP) Hierarchy with "RFC 4206: Label Switched Paths (LSP) Hierarchy with
Generalized Multi-Protocol Label Switching (GMPLS) Generalized Multi-Protocol Label Switching (GMPLS)
Traffic Engineering (TE)"; Traffic Engineering (TE)";
uses te-link-underlay-attributes; uses te-link-underlay-attributes;
} // underlay }
uses te-types:generic-path-constraints; uses te-types:generic-path-constraints;
uses te-types:generic-path-optimization; uses te-types:generic-path-optimization;
uses te-types:generic-path-properties; uses te-types:generic-path-properties;
} // connectivity-matrix-entry-path-attributes }
// connectivity-matrix-entry-path-attributes
grouping geolocation-container { grouping geolocation-container {
description description
"A container containing a GPS location."; "Contains a GPS location.";
container geolocation{ container geolocation {
config false; config false;
description description
"A container containing a GPS location."; "Contains a GPS location.";
leaf altitude { leaf altitude {
type int64; type int64;
units millimeter; units "millimeters";
description description
"Distance above the sea level."; "Distance above sea level.";
} }
leaf latitude { leaf latitude {
type geographic-coordinate-degree { type geographic-coordinate-degree {
range "-90..90"; range "-90..90";
} }
description description
"Relative position north or south on the Earth's surface."; "Relative position north or south on the Earth's surface.";
} }
leaf longitude { leaf longitude {
type geographic-coordinate-degree { type geographic-coordinate-degree {
range "-180..180"; range "-180..180";
} }
description description
"Angular distance east or west on the Earth's surface."; "Angular distance east or west on the Earth's surface.";
} }
} // gps-location }
} // geolocation-container // geolocation
}
// geolocation-container
grouping information-source-state-attributes { grouping information-source-state-attributes {
description description
"The attributes identifying source that has provided the "The attributes identifying the source that has provided the
related information, and the source credibility."; related information, and the source's credibility.";
leaf credibility-preference { leaf credibility-preference {
type uint16; type uint16;
description description
"The preference value to calculate the traffic "The preference value for calculating the Traffic
engineering database credibility value used for Engineering database credibility value used for
tie-break selection between different tie-break selection between different information-source
information-source values. values. A higher value is preferable.";
Higher value is more preferable.";
} }
leaf logical-network-element { leaf logical-network-element {
type string; type string;
description description
"When applicable, this is the name of a logical network "When applicable, this is the name of a logical network
element from which the information is learned."; element from which the information is learned.";
} // logical-network-element }
leaf network-instance { leaf network-instance {
type string; type string;
description description
"When applicable, this is the name of a network-instance "When applicable, this is the name of a network instance
from which the information is learned."; from which the information is learned.";
} // network-instance }
} // information-source-state-attributes }
// information-source-state-attributes
grouping information-source-per-link-attributes { grouping information-source-per-link-attributes {
description description
"Per node container of the attributes identifying source that "Per-node container of the attributes identifying the source
has provided the related information, and the source that has provided the related information, and the source's
credibility."; credibility.";
leaf information-source { leaf information-source {
type te-info-source; type te-info-source;
config false; config false;
description description
"Indicates the type of the information source."; "Indicates the type of information source.";
} }
leaf information-source-instance { leaf information-source-instance {
type string; type string;
config false; config false;
description description
"The name indicating the instance of the information "The name indicating the instance of the information
source."; source.";
} }
container information-source-state { container information-source-state {
config false; config false;
description description
"The container contains state attributes related to "Contains state attributes related to the information
the information source."; source.";
uses information-source-state-attributes; uses information-source-state-attributes;
container topology { container topology {
description description
"When the information is processed by the system, "When the information is processed by the system,
the attributes in this container indicate which topology the attributes in this container indicate which topology
is used to process to generate the result information."; is used to generate the result information.";
uses nt:link-ref; uses nt:link-ref;
} // topology }
} // information-source-state }
} // information-source-per-link-attributes }
// information-source-per-link-attributes
grouping information-source-per-node-attributes { grouping information-source-per-node-attributes {
description description
"Per node container of the attributes identifying source that "Per-node container of the attributes identifying the source
has provided the related information, and the source that has provided the related information, and the source's
credibility."; credibility.";
leaf information-source { leaf information-source {
type te-info-source; type te-info-source;
config false; config false;
description description
"Indicates the type of the information source."; "Indicates the type of information source.";
} }
leaf information-source-instance { leaf information-source-instance {
type string; type string;
config false; config false;
description description
"The name indicating the instance of the information "The name indicating the instance of the information
source."; source.";
} }
container information-source-state { container information-source-state {
config false; config false;
description description
"The container contains state attributes related to "Contains state attributes related to the information
the information source."; source.";
uses information-source-state-attributes; uses information-source-state-attributes;
container topology { container topology {
description description
"When the information is processed by the system, "When the information is processed by the system,
the attributes in this container indicate which topology the attributes in this container indicate which topology
is used to process to generate the result information."; is used to generate the result information.";
uses nw:node-ref; uses nw:node-ref;
} // topology }
} // information-source-state }
} // information-source-per-node-attributes }
// information-source-per-node-attributes
grouping interface-switching-capability-list { grouping interface-switching-capability-list {
description description
"List of Interface Switching Capabilities Descriptors (ISCD)"; "List of Interface Switching Capability Descriptors (ISCDs).";
list interface-switching-capability { list interface-switching-capability {
key "switching-capability encoding"; key "switching-capability encoding";
description description
"List of Interface Switching Capabilities Descriptors (ISCD) "List of ISCDs for this link.";
for this link.";
reference reference
"RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS) "RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description. Signaling Functional Description
RFC 4203: OSPF Extensions in Support of Generalized RFC 4203: OSPF Extensions in Support of Generalized
Multi-Protocol Label Switching (GMPLS)."; Multi-Protocol Label Switching (GMPLS)";
leaf switching-capability { leaf switching-capability {
type identityref { type identityref {
base te-types:switching-capabilities; base te-types:switching-capabilities;
} }
description description
"Switching Capability for this interface."; "Switching capability for this interface.";
} }
leaf encoding { leaf encoding {
type identityref { type identityref {
base te-types:lsp-encoding-types; base te-types:lsp-encoding-types;
} }
description description
"Encoding supported by this interface."; "Encoding supported by this interface.";
} }
uses te-link-iscd-attributes; uses te-link-iscd-attributes;
} // interface-switching-capability }
} // interface-switching-capability-list // interface-switching-capability
}
// interface-switching-capability-list
grouping statistics-per-link { grouping statistics-per-link {
description description
"Statistics attributes per TE link."; "Statistics attributes per TE link.";
leaf discontinuity-time { leaf discontinuity-time {
type yang:date-and-time; type yang:date-and-time;
description description
"The time on the most recent occasion at which any one or "The time of the most recent occasion at which any one or
more of this interface's counters suffered a more of this interface's counters suffered a
discontinuity. If no such discontinuities have occurred discontinuity. If no such discontinuities have occurred
since the last re-initialization of the local management since the last re-initialization of the local management
subsystem, then this node contains the time the local subsystem, then this node contains the time the local
management subsystem re-initialized itself."; management subsystem re-initialized itself.";
} }
/* Administrative attributes */ /* Administrative attributes */
leaf disables { leaf disables {
type yang:counter32; type yang:counter32;
description description
"Number of times that link was disabled."; "Number of times that a link was disabled.";
} }
leaf enables { leaf enables {
type yang:counter32; type yang:counter32;
description description
"Number of times that link was enabled."; "Number of times that a link was enabled.";
} }
leaf maintenance-clears { leaf maintenance-clears {
type yang:counter32; type yang:counter32;
description description
"Number of times that link was put out of maintenance."; "Number of times that a link was taken out of maintenance.";
} }
leaf maintenance-sets { leaf maintenance-sets {
type yang:counter32; type yang:counter32;
description description
"Number of times that link was put in maintenance."; "Number of times that a link was put in maintenance.";
} }
leaf modifies { leaf modifies {
type yang:counter32; type yang:counter32;
description description
"Number of times that link was modified."; "Number of times that a link was modified.";
} }
/* Operational attributes */ /* Operational attributes */
leaf downs { leaf downs {
type yang:counter32; type yang:counter32;
description description
"Number of times that link was set to operational down."; "Number of times that a link was set to an operational state
of 'down'.";
} }
leaf ups { leaf ups {
type yang:counter32; type yang:counter32;
description description
"Number of times that link was set to operational up."; "Number of times that a link was set to an operational state
of 'up'.";
} }
/* Recovery attributes */ /* Recovery attributes */
leaf fault-clears { leaf fault-clears {
type yang:counter32; type yang:counter32;
description description
"Number of times that link experienced fault clear event."; "Number of times that a link experienced a fault-clear
event.";
} }
leaf fault-detects { leaf fault-detects {
type yang:counter32; type yang:counter32;
description description
"Number of times that link experienced fault detection."; "Number of times that a link experienced fault detection.";
} }
leaf protection-switches { leaf protection-switches {
type yang:counter32; type yang:counter32;
description description
"Number of times that link experienced protection "Number of times that a link experienced protection
switchover."; switchover.";
} }
leaf protection-reverts { leaf protection-reverts {
type yang:counter32; type yang:counter32;
description description
"Number of times that link experienced protection "Number of times that a link experienced protection
reversion."; reversion.";
} }
leaf restoration-failures { leaf restoration-failures {
type yang:counter32; type yang:counter32;
description description
"Number of times that link experienced restoration "Number of times that a link experienced restoration
failure."; failure.";
} }
leaf restoration-starts { leaf restoration-starts {
type yang:counter32; type yang:counter32;
description description
"Number of times that link experienced restoration "Number of times that a link experienced restoration
start."; start.";
} }
leaf restoration-successes { leaf restoration-successes {
type yang:counter32; type yang:counter32;
description description
"Number of times that link experienced restoration "Number of times that a link experienced restoration
success."; success.";
} }
leaf restoration-reversion-failures { leaf restoration-reversion-failures {
type yang:counter32; type yang:counter32;
description description
"Number of times that link experienced restoration reversion "Number of times that a link experienced restoration
failure."; reversion failure.";
} }
leaf restoration-reversion-starts { leaf restoration-reversion-starts {
type yang:counter32; type yang:counter32;
description description
"Number of times that link experienced restoration reversion "Number of times that a link experienced restoration
start."; reversion start.";
} }
leaf restoration-reversion-successes { leaf restoration-reversion-successes {
type yang:counter32; type yang:counter32;
description description
"Number of times that link experienced restoration reversion "Number of times that a link experienced restoration
success."; reversion success.";
} }
} // statistics-per-link }
// statistics-per-link
grouping statistics-per-node { grouping statistics-per-node {
description description
"Statistics attributes per TE node."; "Statistics attributes per TE node.";
leaf discontinuity-time { leaf discontinuity-time {
type yang:date-and-time; type yang:date-and-time;
description description
"The time on the most recent occasion at which any one or "The time of the most recent occasion at which any one or
more of this interface's counters suffered a more of this interface's counters suffered a
discontinuity. If no such discontinuities have occurred discontinuity. If no such discontinuities have occurred
since the last re-initialization of the local management since the last re-initialization of the local management
subsystem, then this node contains the time the local subsystem, then this node contains the time the local
management subsystem re-initialized itself."; management subsystem re-initialized itself.";
} }
container node { container node {
description description
"Containing TE node level statistics attributes."; "Contains statistics attributes at the TE node level.";
leaf disables { leaf disables {
type yang:counter32; type yang:counter32;
description description
"Number of times that node was disabled."; "Number of times that a node was disabled.";
} }
leaf enables { leaf enables {
type yang:counter32; type yang:counter32;
description description
"Number of times that node was enabled."; "Number of times that a node was enabled.";
} }
leaf maintenance-sets { leaf maintenance-sets {
type yang:counter32; type yang:counter32;
description description
"Number of times that node was put in maintenance."; "Number of times that a node was put in maintenance.";
} }
leaf maintenance-clears { leaf maintenance-clears {
type yang:counter32; type yang:counter32;
description description
"Number of times that node was put out of maintenance."; "Number of times that a node was taken out of
maintenance.";
} }
leaf modifies { leaf modifies {
type yang:counter32; type yang:counter32;
description description
"Number of times that node was modified."; "Number of times that a node was modified.";
} }
} // node }
// node
container connectivity-matrix-entry { container connectivity-matrix-entry {
description description
"Containing connectivity matrix entry level statistics "Contains statistics attributes at the level of a
attributes."; connectivity matrix entry.";
leaf creates { leaf creates {
type yang:counter32; type yang:counter32;
description description
"Number of times that a connectivity matrix entry was "Number of times that a connectivity matrix entry was
created."; created.";
reference reference
"RFC 6241. Section 7.2 for 'create' operation. "; "RFC 6241: Network Configuration Protocol (NETCONF),
Section 7.2, 'create' operation";
} }
leaf deletes { leaf deletes {
type yang:counter32; type yang:counter32;
description description
"Number of times that a connectivity matrix entry was "Number of times that a connectivity matrix entry was
deleted."; deleted.";
reference reference
"RFC 6241. Section 7.2 for 'delete' operation. "; "RFC 6241: Network Configuration Protocol (NETCONF),
Section 7.2, 'delete' operation";
} }
leaf disables { leaf disables {
type yang:counter32; type yang:counter32;
description description
"Number of times that a connectivity matrix entry was "Number of times that a connectivity matrix entry was
disabled."; disabled.";
} }
leaf enables { leaf enables {
type yang:counter32; type yang:counter32;
description description
skipping to change at page 59, line 4 skipping to change at line 2490
type yang:counter32; type yang:counter32;
description description
"Number of times that a connectivity matrix entry was "Number of times that a connectivity matrix entry was
enabled."; enabled.";
} }
leaf modifies { leaf modifies {
type yang:counter32; type yang:counter32;
description description
"Number of times that a connectivity matrix entry was "Number of times that a connectivity matrix entry was
modified."; modified.";
} }
} // connectivity-matrix-entry }
} // statistics-per-node // connectivity-matrix-entry
}
// statistics-per-node
grouping statistics-per-ttp { grouping statistics-per-ttp {
description description
"Statistics attributes per TE TTP (Tunnel Termination Point)."; "Statistics attributes per TE TTP (Tunnel Termination Point).";
leaf discontinuity-time { leaf discontinuity-time {
type yang:date-and-time; type yang:date-and-time;
description description
"The time on the most recent occasion at which any one or "The time of the most recent occasion at which any one or
more of this interface's counters suffered a more of this interface's counters suffered a
discontinuity. If no such discontinuities have occurred discontinuity. If no such discontinuities have occurred
since the last re-initialization of the local management since the last re-initialization of the local management
subsystem, then this node contains the time the local subsystem, then this node contains the time the local
management subsystem re-initialized itself."; management subsystem re-initialized itself.";
} }
container tunnel-termination-point { container tunnel-termination-point {
description description
"Containing TE TTP (Tunnel Termination Point) level "Contains statistics attributes at the TE TTP level.";
statistics attributes.";
/* Administrative attributes */ /* Administrative attributes */
leaf disables { leaf disables {
type yang:counter32; type yang:counter32;
description description
"Number of times that TTP was disabled."; "Number of times that a TTP was disabled.";
} }
leaf enables { leaf enables {
type yang:counter32; type yang:counter32;
description description
"Number of times that TTP was enabled."; "Number of times that a TTP was enabled.";
} }
leaf maintenance-clears { leaf maintenance-clears {
type yang:counter32; type yang:counter32;
description description
"Number of times that TTP was put out of maintenance."; "Number of times that a TTP was taken out of maintenance.";
} }
leaf maintenance-sets { leaf maintenance-sets {
type yang:counter32; type yang:counter32;
description description
"Number of times that TTP was put in maintenance."; "Number of times that a TTP was put in maintenance.";
} }
leaf modifies { leaf modifies {
type yang:counter32; type yang:counter32;
description description
"Number of times that TTP was modified."; "Number of times that a TTP was modified.";
} }
/* Operational attributes */ /* Operational attributes */
leaf downs { leaf downs {
type yang:counter32; type yang:counter32;
description description
"Number of times that TTP was set to operational down."; "Number of times that a TTP was set to an operational state
of 'down'.";
} }
leaf ups { leaf ups {
type yang:counter32; type yang:counter32;
description description
"Number of times that TTP was set to operational up."; "Number of times that a TTP was set to an operational state
of 'up'.";
} }
leaf in-service-clears { leaf in-service-clears {
type yang:counter32; type yang:counter32;
description description
"Number of times that TTP was taken out of service "Number of times that a TTP was taken out of service
(TE tunnel was released)."; (TE tunnel was released).";
} }
leaf in-service-sets { leaf in-service-sets {
type yang:counter32; type yang:counter32;
description description
"Number of times that TTP was put in service by a TE "Number of times that a TTP was put in service by a TE
tunnel (TE tunnel was set up)."; tunnel (TE tunnel was set up).";
} }
} // tunnel-termination-point }
// tunnel-termination-point
container local-link-connectivity { container local-link-connectivity {
description description
"Containing TE LLCL (Local Link Connectivity List) level "Contains statistics attributes at the TE LLCL (Local Link
statistics attributes."; Connectivity List) level.";
leaf creates { leaf creates {
type yang:counter32; type yang:counter32;
description description
"Number of times that an LLCL entry was created."; "Number of times that an LLCL entry was created.";
reference reference
"RFC 6241. Section 7.2 for 'create' operation."; "RFC 6241: Network Configuration Protocol (NETCONF),
Section 7.2, 'create' operation";
} }
leaf deletes { leaf deletes {
type yang:counter32; type yang:counter32;
description description
"Number of times that an LLCL entry was deleted."; "Number of times that an LLCL entry was deleted.";
reference reference
"RFC 6241. Section 7.2 for 'delete' operation."; "RFC 6241: Network Configuration Protocol (NETCONF),
Section 7.2, 'delete' operation";
} }
leaf disables { leaf disables {
type yang:counter32; type yang:counter32;
description description
"Number of times that an LLCL entry was disabled."; "Number of times that an LLCL entry was disabled.";
} }
leaf enables { leaf enables {
type yang:counter32; type yang:counter32;
description description
"Number of times that an LLCL entry was enabled."; "Number of times that an LLCL entry was enabled.";
} }
leaf modifies { leaf modifies {
type yang:counter32; type yang:counter32;
description description
"Number of times that an LLCL entry was modified."; "Number of times that an LLCL entry was modified.";
} }
} // local-link-connectivity }
} // statistics-per-ttp // local-link-connectivity
}
// statistics-per-ttp
grouping te-link-augment { grouping te-link-augment {
description description
"Augmentation for TE link."; "Augmentation for a TE link.";
uses te-link-config; uses te-link-config;
uses te-link-state-derived; uses te-link-state-derived;
container statistics { container statistics {
config false; config false;
description description
"Statistics data."; "Statistics data.";
uses statistics-per-link; uses statistics-per-link;
} // statistics }
} // te-link-augment }
// te-link-augment
grouping te-link-config { grouping te-link-config {
description description
"TE link configuration grouping."; "TE link configuration grouping.";
choice bundle-stack-level { choice bundle-stack-level {
description description
"The TE link can be partitioned into bundled "The TE link can be partitioned into bundled links or
links, or component links."; component links.";
case bundle { case bundle {
container bundled-links { container bundled-links {
description description
"A set of bundled links."; "A set of bundled links.";
reference reference
"RFC 4201: Link Bundling in MPLS Traffic Engineering "RFC 4201: Link Bundling in MPLS Traffic
(TE)."; Engineering (TE)";
list bundled-link { list bundled-link {
key "sequence"; key "sequence";
description description
"Specify a bundled interface that is "Specifies a bundled interface that is
further partitioned."; further partitioned.";
leaf sequence { leaf sequence {
type uint32; type uint32;
description description
"Identify the sequence in the bundle."; "Identifies the sequence in the bundle.";
} }
} // list bundled-link }
} }
} }
case component { case component {
container component-links { container component-links {
description description
"A set of component links"; "A set of component links.";
list component-link { list component-link {
key "sequence"; key "sequence";
description description
"Specify a component interface that is "Specifies a component interface that is
sufficient to unambiguously identify the sufficient to unambiguously identify the
appropriate resources"; appropriate resources.";
leaf sequence { leaf sequence {
type uint32; type uint32;
description description
"Identify the sequence in the bundle."; "Identifies the sequence in the bundle.";
} }
leaf src-interface-ref { leaf src-interface-ref {
type string; type string;
description description
"Reference to component link interface on the "Reference to a component link interface on the
source node."; source node.";
} }
leaf des-interface-ref { leaf des-interface-ref {
type string; type string;
description description
"Reference to component link interface on the "Reference to a component link interface on the
destinatioin node."; destination node.";
} }
} }
} }
} }
} // bundle-stack-level }
// bundle-stack-level
leaf-list te-link-template { leaf-list te-link-template {
if-feature template; if-feature "template";
type leafref { type leafref {
path "../../../../te/templates/link-template/name"; path "../../../../te/templates/link-template/name";
} }
description description
"The reference to a TE link template."; "The reference to a TE link template.";
} }
uses te-link-config-attributes; uses te-link-config-attributes;
} // te-link-config }
// te-link-config
grouping te-link-config-attributes { grouping te-link-config-attributes {
description description
"Link configuration attributes in a TE topology."; "Link configuration attributes in a TE topology.";
container te-link-attributes { container te-link-attributes {
description "Link attributes in a TE topology."; description
"Link attributes in a TE topology.";
leaf access-type { leaf access-type {
type te-types:te-link-access-type; type te-types:te-link-access-type;
description description
"Link access type, which can be point-to-point or "Link access type, which can be point-to-point or
multi-access."; multi-access.";
} }
container external-domain { container external-domain {
description description
"For an inter-domain link, specify the attributes of "For an inter-domain link, specifies the attributes of
the remote end of link, to facilitate the signalling at the remote end of the link, to facilitate the signaling at
local end."; the local end.";
uses nw:network-ref; uses nw:network-ref;
leaf remote-te-node-id { leaf remote-te-node-id {
type te-types:te-node-id; type te-types:te-node-id;
description description
"Remote TE node identifier, used together with "Remote TE node identifier, used together with
remote-te-link-id to identify the remote link 'remote-te-link-tp-id' to identify the remote Link
termination point in a different domain."; Termination Point (LTP) in a different domain.";
} }
leaf remote-te-link-tp-id { leaf remote-te-link-tp-id {
type te-types:te-tp-id; type te-types:te-tp-id;
description description
"Remote TE link termination point identifier, used "Remote TE LTP identifier, used together with
together with remote-te-node-id to identify the remote 'remote-te-node-id' to identify the remote LTP in a
link termination point in a different domain."; different domain.";
} }
} }
leaf is-abstract { leaf is-abstract {
type empty; type empty;
description "Present if the link is abstract."; description
"Present if the link is abstract.";
} }
leaf name { leaf name {
type string; type string;
description "Link Name."; description
"Link name.";
} }
container underlay { container underlay {
if-feature te-topology-hierarchy; if-feature "te-topology-hierarchy";
description "Attributes of the te-link underlay."; description
"Attributes of the TE link underlay.";
reference reference
"RFC 4206: Label Switched Paths (LSP) Hierarchy with "RFC 4206: Label Switched Paths (LSP) Hierarchy with
Generalized Multi-Protocol Label Switching (GMPLS) Generalized Multi-Protocol Label Switching (GMPLS)
Traffic Engineering (TE)"; Traffic Engineering (TE)";
uses te-link-underlay-attributes; uses te-link-underlay-attributes;
} // underlay }
leaf admin-status { leaf admin-status {
type te-types:te-admin-status; type te-types:te-admin-status;
description description
"The administrative state of the link."; "The administrative state of the link.";
} }
uses te-link-info-attributes; uses te-link-info-attributes;
} // te-link-attributes }
} // te-link-config-attributes // te-link-attributes
}
// te-link-config-attributes
grouping te-link-info-attributes { grouping te-link-info-attributes {
description description
"Advertised TE information attributes."; "Advertised TE information attributes.";
leaf link-index { leaf link-index {
type uint64; type uint64;
description description
"The link identifier. If OSPF is used, this represents an "The link identifier. If OSPF is used, this object
ospfLsdbID. If IS-IS is used, this represents an isisLSPID. represents an ospfLsdbID. If IS-IS is used, this object
If a locally configured link is used, this object represents represents an isisLSPID. If a locally configured link is
a unique value, which is locally defined in a router."; used, this object represents a unique value, which is
locally defined in a router.";
} }
leaf administrative-group { leaf administrative-group {
type te-types:admin-groups; type te-types:admin-groups;
description description
"Administrative group or color of the link. "Administrative group or color of the link.
This attribute covers both administrative group (defined in This attribute covers both administrative groups (defined
RFC 3630, RFC 5305 and RFC 5329), and extended in RFCs 3630 and 5305) and Extended Administrative Groups
administrative group (defined in RFC 7308)."; (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 interface-switching-capability-list;
uses te-types:label-set-info; uses te-types:label-set-info;
leaf link-protection-type { leaf link-protection-type {
type identityref { type identityref {
base te-types:link-protection-type; base te-types:link-protection-type;
} }
description description
"Link Protection Type desired for this link."; "Link Protection Type desired for this link.";
reference reference
"RFC 4202: Routing Extensions in Support of "RFC 4202: Routing Extensions in Support of
Generalized Multi-Protocol Label Switching (GMPLS)."; Generalized Multi-Protocol Label Switching (GMPLS)";
} }
container max-link-bandwidth { container max-link-bandwidth {
uses te-types:te-bandwidth; uses te-types:te-bandwidth;
description description
"Maximum bandwidth that can be seen on this link in this "Maximum bandwidth that can be seen on this link in this
direction. Units in bytes per second."; direction. Units are in bytes per second.";
reference reference
"RFC 3630: Traffic Engineering (TE) Extensions to OSPF "RFC 3630: Traffic Engineering (TE) Extensions to OSPF
Version 2. Version 2
RFC 5305: IS-IS Extensions for Traffic Engineering."; RFC 5305: IS-IS Extensions for Traffic Engineering";
} }
container max-resv-link-bandwidth { container max-resv-link-bandwidth {
uses te-types:te-bandwidth; uses te-types:te-bandwidth;
description description
"Maximum amount of bandwidth that can be reserved in this "Maximum amount of bandwidth that can be reserved in this
direction in this link. Units in bytes per second."; direction in this link. Units are in bytes per second.";
reference reference
"RFC 3630: Traffic Engineering (TE) Extensions to OSPF "RFC 3630: Traffic Engineering (TE) Extensions to OSPF
Version 2. Version 2
RFC 5305: IS-IS Extensions for Traffic Engineering."; RFC 5305: IS-IS Extensions for Traffic Engineering";
} }
list unreserved-bandwidth { list unreserved-bandwidth {
key "priority"; key "priority";
max-elements "8"; max-elements 8;
description description
"Unreserved bandwidth for 0-7 priority levels. Units in "Unreserved bandwidth for priority levels 0-7. Units are in
bytes per second."; bytes per second.";
reference reference
"RFC 3630: Traffic Engineering (TE) Extensions to OSPF "RFC 3630: Traffic Engineering (TE) Extensions to OSPF
Version 2. Version 2
RFC 5305: IS-IS Extensions for Traffic Engineering."; RFC 5305: IS-IS Extensions for Traffic Engineering";
leaf priority { leaf priority {
type uint8 { type uint8 {
range "0..7"; range "0..7";
} }
description "Priority."; description
"Priority.";
} }
uses te-types:te-bandwidth; uses te-types:te-bandwidth;
} }
leaf te-default-metric { leaf te-default-metric {
type uint32; type uint32;
description description
"Traffic engineering metric."; "Traffic Engineering metric.";
reference reference
"RFC 3630: Traffic Engineering (TE) Extensions to OSPF "RFC 3630: Traffic Engineering (TE) Extensions to OSPF
Version 2. Version 2
RFC 5305: IS-IS Extensions for Traffic Engineering."; RFC 5305: IS-IS Extensions for Traffic Engineering";
} }
leaf te-delay-metric { leaf te-delay-metric {
type uint32; type uint32;
description description
"Traffic engineering delay metric."; "Traffic Engineering delay metric.";
reference reference
"RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions."; "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions";
} }
leaf te-igp-metric { leaf te-igp-metric {
type uint32; type uint32;
description description
"IGP metric used for traffic engineering."; "IGP metric used for Traffic Engineering.";
reference reference
"RFC 3785: Use of Interior Gateway Protocol (IGP) Metric as a "RFC 3785: Use of Interior Gateway Protocol (IGP) Metric as a
Second MPLS Traffic Engineering (TE) Metric."; second MPLS Traffic Engineering (TE) Metric";
} }
container te-srlgs { container te-srlgs {
description description
"Containing a list of SLRGs."; "Contains a list of SRLGs.";
leaf-list value { leaf-list value {
type te-types:srlg; type te-types:srlg;
description "SRLG value."; description
"SRLG value.";
reference reference
"RFC 4202: Routing Extensions in Support of "RFC 4202: Routing Extensions in Support of
Generalized Multi-Protocol Label Switching (GMPLS)."; Generalized Multi-Protocol Label Switching (GMPLS)";
} }
} }
container te-nsrlgs { container te-nsrlgs {
if-feature nsrlg; if-feature "nsrlg";
description description
"Containing a list of NSRLGs (Not Sharing Risk Link "Contains a list of NSRLGs (Non-Shared Risk Link Groups).
Groups).
When an abstract TE link is configured, this list specifies When an abstract TE link is configured, this list specifies
the request that underlay TE paths need to be mutually the request that underlay TE paths need to be mutually
disjoint with other TE links in the same groups."; disjoint with other TE links in the same groups.";
leaf-list id { leaf-list id {
type uint32; type uint32;
description description
"NSRLG ID, uniquely configured within a topology."; "NSRLG ID, uniquely configured within a topology.";
reference reference
"RFC 4872: RSVP-TE Extensions in Support of End-to-End "RFC 4872: RSVP-TE Extensions in Support of End-to-End
Generalized Multi-Protocol Label Switching (GMPLS) Generalized Multi-Protocol Label Switching (GMPLS)
Recovery"; Recovery";
} }
} }
} // te-link-info-attributes }
// te-link-info-attributes
grouping te-link-iscd-attributes { grouping te-link-iscd-attributes {
description description
"TE link ISCD (Interface Switching Capability Descriptor) "TE link ISCD attributes.";
attributes.";
reference reference
"Sec 1.4, RFC 4203: OSPF Extensions in Support of Generalized "RFC 4203: OSPF Extensions in Support of Generalized
Multi-Protocol Label Switching (GMPLS). Section 1.4."; Multi-Protocol Label Switching (GMPLS), Section 1.4";
list max-lsp-bandwidth { list max-lsp-bandwidth {
key "priority"; key "priority";
max-elements "8"; max-elements 8;
description description
"Maximum LSP Bandwidth at priorities 0-7."; "Maximum Label Switched Path (LSP) bandwidth at
priorities 0-7.";
leaf priority { leaf priority {
type uint8 { type uint8 {
range "0..7"; range "0..7";
} }
description "Priority."; description
"Priority.";
} }
uses te-types:te-bandwidth; uses te-types:te-bandwidth;
} }
} // te-link-iscd-attributes }
// te-link-iscd-attributes
grouping te-link-state-derived { grouping te-link-state-derived {
description description
"Link state attributes in a TE topology."; "Link state attributes in a TE topology.";
leaf oper-status { leaf oper-status {
type te-types:te-oper-status; type te-types:te-oper-status;
config false; config false;
description description
"The current operational state of the link."; "The current operational state of the link.";
} }
leaf is-transitional { leaf is-transitional {
type empty; type empty;
config false; config false;
description description
"Present if the link is transitional, used as an "Present if the link is transitional; used as an
alternative approach in lieu of inter-layer-lock-id alternative approach in lieu of 'inter-layer-lock-id'
for path computation in a TE topology covering multiple for path computation in a TE topology covering multiple
layers or multiple regions."; layers or multiple regions.";
reference reference
"RFC 5212: Requirements for GMPLS-Based Multi-Region and "RFC 5212: Requirements for GMPLS-Based Multi-Region and
Multi-Layer Networks (MRN/MLN). Multi-Layer Networks (MRN/MLN)
RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions
for Multi-Layer and Multi-Region Networks (MLN/MRN)."; for Multi-Layer and Multi-Region Networks (MLN/MRN)";
} }
uses information-source-per-link-attributes; uses information-source-per-link-attributes;
list information-source-entry { list information-source-entry {
key "information-source information-source-instance"; key "information-source information-source-instance";
config false; config false;
description description
"A list of information sources learned, including the one "A list of information sources learned, including the source
used."; that is used.";
uses information-source-per-link-attributes; uses information-source-per-link-attributes;
uses te-link-info-attributes; uses te-link-info-attributes;
} }
container recovery { container recovery {
config false; config false;
description description
"Status of the recovery process."; "Status of the recovery process.";
leaf restoration-status { leaf restoration-status {
type te-types:te-recovery-status; type te-types:te-recovery-status;
description description
"Restoration status."; "Restoration status.";
} }
leaf protection-status { leaf protection-status {
type te-types:te-recovery-status; type te-types:te-recovery-status;
description description
"Protection status."; "Protection status.";
} }
} }
container underlay { container underlay {
if-feature te-topology-hierarchy; if-feature "te-topology-hierarchy";
config false; config false;
description "State attributes for te-link underlay."; description
"State attributes for the TE link underlay.";
leaf dynamic { leaf dynamic {
type boolean; type boolean;
description description
"true if the underlay is dynamically created."; "'true' if the underlay is dynamically created.";
} }
leaf committed { leaf committed {
type boolean; type boolean;
description description
"true if the underlay is committed."; "'true' if the underlay is committed.";
} }
} }
} // te-link-state-derived }
// te-link-state-derived
grouping te-link-underlay-attributes { grouping te-link-underlay-attributes {
description "Attributes for te-link underlay."; description
"Attributes for the TE link underlay.";
reference reference
"RFC 4206: Label Switched Paths (LSP) Hierarchy with "RFC 4206: Label Switched Paths (LSP) Hierarchy with
Generalized Multi-Protocol Label Switching (GMPLS) Generalized Multi-Protocol Label Switching (GMPLS)
Traffic Engineering (TE)"; Traffic Engineering (TE)";
leaf enabled { leaf enabled {
type boolean; type boolean;
description description
"'true' if the underlay is enabled. "'true' if the underlay is enabled.
'false' if the underlay is disabled."; 'false' if the underlay is disabled.";
} }
skipping to change at page 70, line 42 skipping to change at line 3002
description description
"The service path on the underlay topology that "The service path on the underlay topology that
supports this link."; supports this link.";
uses nw:network-ref; uses nw:network-ref;
list path-element { list path-element {
key "path-element-id"; key "path-element-id";
description description
"A list of path elements describing the service path."; "A list of path elements describing the service path.";
leaf path-element-id { leaf path-element-id {
type uint32; type uint32;
description "To identify the element in a path."; description
"To identify the element in a path.";
} }
uses te-path-element; uses te-path-element;
} }
} // primary-path }
// primary-path
list backup-path { list backup-path {
key "index"; key "index";
description description
"A list of backup service paths on the underlay topology that "A list of backup service paths on the underlay topology that
protect the underlay primary path. If the primary path is protect the underlay primary path. If the primary path is
not protected, the list contains zero elements. If the not protected, the list contains zero elements. If the
primary path is protected, the list contains one or more primary path is protected, the list contains one or more
elements."; elements.";
leaf index { leaf index {
type uint32; type uint32;
description description
"A sequence number to identify a backup path."; "A sequence number to identify a backup path.";
} }
uses nw:network-ref; uses nw:network-ref;
list path-element { list path-element {
key "path-element-id"; key "path-element-id";
description description
"A list of path elements describing the backup service "A list of path elements describing the backup service
path"; path.";
leaf path-element-id { leaf path-element-id {
type uint32; type uint32;
description "To identify the element in a path."; description
"To identify the element in a path.";
} }
uses te-path-element; uses te-path-element;
} }
} // underlay-backup-path }
// backup-path
leaf protection-type { leaf protection-type {
type identityref { type identityref {
base te-types:lsp-protection-type; base te-types:lsp-protection-type;
} }
description description
"Underlay protection type desired for this link."; "Underlay protection type desired for this link.";
} }
container tunnel-termination-points { container tunnel-termination-points {
description description
"Underlay TTP(Tunnel Termination Points) desired for this "Underlay TTPs desired for this link.";
link.";
leaf source { leaf source {
type binary; type binary;
description description
"Source tunnel termination point identifier."; "Source TTP identifier.";
} }
leaf destination { leaf destination {
type binary; type binary;
description description
"Destination tunnel termination point identifier."; "Destination TTP identifier.";
} }
} }
container tunnels { container tunnels {
description description
"Underlay TE tunnels supporting this TE link."; "Underlay TE tunnels supporting this TE link.";
leaf sharing { leaf sharing {
type boolean; type boolean;
default true; default "true";
description description
"'true' if the underlay tunnel can be shared with other "'true' if the underlay tunnel can be shared with other
TE links; TE links;
'false' if the underlay tunnel is dedicated to this 'false' if the underlay tunnel is dedicated to this
TE link. TE link.
This leaf is the default option for all TE tunnels, This leaf is the default option for all TE tunnels
and may be overridden by the per TE tunnel value."; and may be overridden by the per-TE-tunnel value.";
} }
list tunnel { list tunnel {
key "tunnel-name"; key "tunnel-name";
description description
"Zero, one or more underlay TE tunnels that support this TE "Zero, one, or more underlay TE tunnels that support this
link."; TE link.";
leaf tunnel-name { leaf tunnel-name {
type string; type string;
description description
"A tunnel name uniquely identifies an underlay TE tunnel, "A tunnel name uniquely identifies an underlay TE tunnel,
used together with the source-node of this link. used together with the 'source-node' value for this
The detailed information of this tunnel can be retrieved link.";
from the ietf-te model."; reference
reference "RFC 3209"; "RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels";
} }
leaf sharing { leaf sharing {
type boolean; type boolean;
description description
"'true' if the underlay tunnel can be shared with other "'true' if the underlay tunnel can be shared with other
TE links; TE links;
'false' if the underlay tunnel is dedicated to this 'false' if the underlay tunnel is dedicated to this
TE link."; TE link.";
} }
} // tunnel }
} // tunnels // tunnel
} // te-link-underlay-attributes }
// tunnels
}
// te-link-underlay-attributes
grouping te-node-augment { grouping te-node-augment {
description description
"Augmentation for TE node."; "Augmentation for a TE node.";
uses te-node-config; uses te-node-config;
uses te-node-state-derived; uses te-node-state-derived;
container statistics { container statistics {
config false; config false;
description description
"Statistics data."; "Statistics data.";
uses statistics-per-node; uses statistics-per-node;
} // statistics }
list tunnel-termination-point { list tunnel-termination-point {
key "tunnel-tp-id"; key "tunnel-tp-id";
description description
"A termination point can terminate a tunnel."; "A termination point can terminate a tunnel.";
leaf tunnel-tp-id { leaf tunnel-tp-id {
type binary; type binary;
description description
"Tunnel termination point identifier."; "TTP identifier.";
} }
uses te-node-tunnel-termination-point-config; uses te-node-tunnel-termination-point-config;
leaf oper-status { leaf oper-status {
type te-types:te-oper-status; type te-types:te-oper-status;
config false; config false;
description description
"The current operational state of the tunnel "The current operational state of the TTP.";
termination point.";
} }
uses geolocation-container; uses geolocation-container;
container statistics { container statistics {
config false; config false;
description description
"Statistics data."; "Statistics data.";
uses statistics-per-ttp; uses statistics-per-ttp;
} // statistics }
// Relationship to other TTPs
// Relations to other tunnel termination points
list supporting-tunnel-termination-point { list supporting-tunnel-termination-point {
key "node-ref tunnel-tp-ref"; key "node-ref tunnel-tp-ref";
description description
"Identifies the tunnel termination points, that this "Identifies the TTPs on which this TTP depends.";
tunnel termination point is depending on.";
leaf node-ref { leaf node-ref {
type inet:uri; type inet:uri;
description description
"This leaf identifies the node in which the supporting "This leaf identifies the node in which the supporting
tunnel termination point is present. TTP is present.
This node is either the supporting node or a node in This node is either the supporting node or a node in
an underlay topology."; an underlay topology.";
} }
leaf tunnel-tp-ref { leaf tunnel-tp-ref {
type binary; type binary;
description description
"Reference to a tunnel terminiation point, which is "Reference to a TTP that is in either the supporting node
either in the supporting node or a node in an or a node in an underlay topology.";
underlay topology.";
} }
} // supporting-tunnel-termination-point }
} // tunnel-termination-point // supporting-tunnel-termination-point
} // te-node-augment }
// tunnel-termination-point
}
// te-node-augment
grouping te-node-config { grouping te-node-config {
description "TE node configuration grouping."; description
"TE node configuration grouping.";
leaf-list te-node-template { leaf-list te-node-template {
if-feature template; if-feature "template";
type leafref { type leafref {
path "../../../../te/templates/node-template/name"; path "../../../../te/templates/node-template/name";
} }
description description
"The reference to a TE node template."; "The reference to a TE node template.";
} }
uses te-node-config-attributes; uses te-node-config-attributes;
}
} // te-node-config // te-node-config
grouping te-node-config-attributes { grouping te-node-config-attributes {
description "Configuration node attributes in a TE topology."; description
"Configuration node attributes in a TE topology.";
container te-node-attributes { container te-node-attributes {
description "Containing node attributes in a TE topology."; description
"Contains node attributes in a TE topology.";
leaf admin-status { leaf admin-status {
type te-types:te-admin-status; type te-types:te-admin-status;
description description
"The administrative state of the link."; "The administrative state of the link.";
} }
uses te-node-connectivity-matrices; uses te-node-connectivity-matrices;
uses te-node-info-attributes; uses te-node-info-attributes;
} // te-node-attributes }
} // te-node-config-attributes }
// te-node-config-attributes
grouping te-node-config-attributes-template { grouping te-node-config-attributes-template {
description description
"Configuration node attributes for template in a TE topology."; "Configuration node attributes for a template in a TE
topology.";
container te-node-attributes { container te-node-attributes {
description "Containing node attributes in a TE topology."; description
"Contains node attributes in a TE topology.";
leaf admin-status { leaf admin-status {
type te-types:te-admin-status; type te-types:te-admin-status;
description description
"The administrative state of the link."; "The administrative state of the link.";
} }
uses te-node-info-attributes; uses te-node-info-attributes;
} // te-node-attributes }
} // te-node-config-attributes-template }
// te-node-config-attributes-template
grouping te-node-connectivity-matrices { grouping te-node-connectivity-matrices {
description "Connectivity matrix on a TE node."; description
"Connectivity matrix on a TE node.";
container connectivity-matrices { container connectivity-matrices {
description description
"Containing connectivity matrix on a TE node."; "Contains a connectivity matrix on a TE node.";
leaf number-of-entries { leaf number-of-entries {
type uint16; type uint16;
description description
"The number of connectivity matrix entries. "The number of connectivity matrix entries.
If this number is specified in the configuration request, If this number is specified in the configuration request,
the number is requested number of entries, which may not the number is the requested number of entries, which may
all be listed in the list; not all be listed in the list;
if this number is reported in the state data, if this number is reported in the state data,
the number is the current number of operational entries."; the number is the current number of operational entries.";
} }
uses te-types:label-set-info; uses te-types:label-set-info;
uses connectivity-matrix-entry-path-attributes; uses connectivity-matrix-entry-path-attributes;
list connectivity-matrix { list connectivity-matrix {
key "id"; key "id";
description description
"Represents node's switching limitations, i.e. limitations "Represents a node's switching limitations, i.e.,
in interconnecting network TE links across the node."; limitations in the interconnecting network TE links
across the node.";
reference reference
"RFC 7579: General Network Element Constraint Encoding "RFC 7579: General Network Element Constraint Encoding
for GMPLS-Controlled Networks."; for GMPLS-Controlled Networks";
leaf id { leaf id {
type uint32; type uint32;
description "Identifies the connectivity-matrix entry."; description
"Identifies the connectivity matrix entry.";
} }
} // connectivity-matrix }
} // connectivity-matrices // connectivity-matrix
} // te-node-connectivity-matrices }
// connectivity-matrices
}
// te-node-connectivity-matrices
grouping te-node-connectivity-matrix-attributes { grouping te-node-connectivity-matrix-attributes {
description description
"Termination point references of a connectivity matrix entry."; "Termination point references of a connectivity matrix entry.";
container from { container from {
description description
"Reference to source link termination point."; "Reference to a source LTP.";
leaf tp-ref { leaf tp-ref {
type leafref { type leafref {
path "../../../../../../nt:termination-point/nt:tp-id"; path "../../../../../../nt:termination-point/nt:tp-id";
} }
description description
"Relative reference to a termination point."; "Relative reference to a termination point.";
} }
uses te-types:label-set-info; uses te-types:label-set-info;
} }
container to { container to {
description description
"Reference to destination link termination point."; "Reference to a destination LTP.";
leaf tp-ref { leaf tp-ref {
type leafref { type leafref {
path "../../../../../../nt:termination-point/nt:tp-id"; path "../../../../../../nt:termination-point/nt:tp-id";
} }
description description
"Relative reference to a termination point."; "Relative reference to a termination point.";
} }
uses te-types:label-set-info; uses te-types:label-set-info;
} }
uses connectivity-matrix-entry-path-attributes; uses connectivity-matrix-entry-path-attributes;
} // te-node-connectivity-matrix-attributes }
// te-node-connectivity-matrix-attributes
grouping te-node-info-attributes { grouping te-node-info-attributes {
description description
"Advertised TE information attributes."; "Advertised TE information attributes.";
leaf domain-id { leaf domain-id {
type uint32; type uint32;
description description
"Identifies the domain that this node belongs. "Identifies the domain to which this node belongs.
This attribute is used to support inter-domain links."; This attribute is used to support inter-domain links.";
reference reference
"RFC 5152: A Per-Domain Path Computation Method for "RFC 5152: A Per-Domain Path Computation Method for
Establishing Inter-Domain Traffic Engineering (TE) Establishing Inter-Domain Traffic Engineering (TE)
Label Switched Paths (LSPs). Label Switched Paths (LSPs)
RFC 5392: OSPF Extensions in Support of Inter-Autonomous
System (AS) MPLS and GMPLS Traffic Engineering.
RFC 5316: ISIS Extensions in Support of Inter-Autonomous RFC 5316: ISIS Extensions in Support of Inter-Autonomous
System (AS) MPLS and GMPLS Traffic Engineering."; System (AS) MPLS and GMPLS Traffic Engineering
RFC 5392: OSPF Extensions in Support of Inter-Autonomous
System (AS) MPLS and GMPLS Traffic Engineering";
} }
leaf is-abstract { leaf is-abstract {
type empty; type empty;
description description
"Present if the node is abstract, not present if the node "Present if the node is abstract; not present if the node
is actual."; is actual.";
} }
leaf name { leaf name {
type string; type string;
description "Node name."; description
"Node name.";
} }
leaf-list signaling-address { leaf-list signaling-address {
type inet:ip-address; type inet:ip-address;
description "Node signaling address."; description
"The node's signaling address.";
} }
container underlay-topology { container underlay-topology {
if-feature te-topology-hierarchy; if-feature "te-topology-hierarchy";
description description
"When an abstract node encapsulates a topology, "When an abstract node encapsulates a topology, the
the attributes in this container point to said topology."; attributes in this container point to said topology.";
uses nw:network-ref; uses nw:network-ref;
} }
} // te-node-info-attributes }
// te-node-info-attributes
grouping te-node-state-derived { grouping te-node-state-derived {
description "Node state attributes in a TE topology."; description
"Node state attributes in a TE topology.";
leaf oper-status { leaf oper-status {
type te-types:te-oper-status; type te-types:te-oper-status;
config false; config false;
description description
"The current operational state of the node."; "The current operational state of the node.";
} }
uses geolocation-container; uses geolocation-container;
leaf is-multi-access-dr { leaf is-multi-access-dr {
type empty; type empty;
config false; config false;
description description
"The presence of this attribute indicates that this TE node "The presence of this attribute indicates that this TE node
is a pseudonode elected as a designated router."; is a pseudonode elected as a designated router.";
reference reference
"RFC 3630: Traffic Engineering (TE) Extensions to OSPF "RFC 1195: Use of OSI IS-IS for Routing in TCP/IP and Dual
Version 2. Environments
RFC 1195: Use of OSI IS-IS for Routing in TCP/IP and Dual RFC 3630: Traffic Engineering (TE) Extensions to OSPF
Environments."; Version 2";
} }
uses information-source-per-node-attributes; uses information-source-per-node-attributes;
list information-source-entry { list information-source-entry {
key "information-source information-source-instance"; key "information-source information-source-instance";
config false; config false;
description description
"A list of information sources learned, including the one "A list of information sources learned, including the source
used."; that is used.";
uses information-source-per-node-attributes; uses information-source-per-node-attributes;
uses te-node-connectivity-matrices; uses te-node-connectivity-matrices;
uses te-node-info-attributes; uses te-node-info-attributes;
} }
} // te-node-state-derived }
// te-node-state-derived
grouping te-node-tunnel-termination-point-config { grouping te-node-tunnel-termination-point-config {
description description
"Termination capability of a tunnel termination point on a "Termination capability of a TTP on a TE node.";
TE node.";
uses te-node-tunnel-termination-point-config-attributes; uses te-node-tunnel-termination-point-config-attributes;
container local-link-connectivities { container local-link-connectivities {
description description
"Containing local link connectivity list for "Contains an LLCL for a TTP on a TE node.";
a tunnel termination point on a TE node.";
leaf number-of-entries { leaf number-of-entries {
type uint16; type uint16;
description description
"The number of local link connectivity list entries. "The number of LLCL entries.
If this number is specified in the configuration request, If this number is specified in the configuration request,
the number is requested number of entries, which may not the number is the requested number of entries, which may
all be listed in the list; not all be listed in the list;
if this number is reported in the state data, if this number is reported in the state data,
the number is the current number of operational entries."; the number is the current number of operational entries.";
} }
uses te-types:label-set-info; uses te-types:label-set-info;
uses connectivity-matrix-entry-path-attributes; uses connectivity-matrix-entry-path-attributes;
} // local-link-connectivities }
} // te-node-tunnel-termination-point-config }
// te-node-tunnel-termination-point-config
grouping te-node-tunnel-termination-point-config-attributes { grouping te-node-tunnel-termination-point-config-attributes {
description description
"Configuration attributes of a tunnel termination point on a "Configuration attributes of a TTP on a TE node.";
TE node.";
leaf admin-status { leaf admin-status {
type te-types:te-admin-status; type te-types:te-admin-status;
description description
"The administrative state of the tunnel termination point."; "The administrative state of the TTP.";
} }
leaf name { leaf name {
type string; type string;
description description
"A descriptive name for the tunnel termination point."; "A descriptive name for the TTP.";
} }
leaf switching-capability { leaf switching-capability {
type identityref { type identityref {
base te-types:switching-capabilities; base te-types:switching-capabilities;
} }
description description
"Switching Capability for this interface."; "Switching capability for this interface.";
} }
leaf encoding { leaf encoding {
type identityref { type identityref {
base te-types:lsp-encoding-types; base te-types:lsp-encoding-types;
} }
description description
"Encoding supported by this interface."; "Encoding supported by this interface.";
} }
leaf-list inter-layer-lock-id { leaf-list inter-layer-lock-id {
type uint32; type uint32;
description description
"Inter layer lock ID, used for path computation in a TE "Inter-layer lock ID, used for path computation in a TE
topology covering multiple layers or multiple regions."; topology covering multiple layers or multiple regions.";
reference reference
"RFC 5212: Requirements for GMPLS-Based Multi-Region and "RFC 5212: Requirements for GMPLS-Based Multi-Region and
Multi-Layer Networks (MRN/MLN). Multi-Layer Networks (MRN/MLN)
RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions
for Multi-Layer and Multi-Region Networks (MLN/MRN)."; for Multi-Layer and Multi-Region Networks (MLN/MRN)";
} }
leaf protection-type { leaf protection-type {
type identityref { type identityref {
base te-types:lsp-protection-type; base te-types:lsp-protection-type;
} }
description description
"The protection type that this tunnel termination point "The protection type that this TTP is capable of.";
is capable of.";
} }
container client-layer-adaptation { container client-layer-adaptation {
description description
"Containing capability information to support a client layer "Contains capability information to support a client-layer
adaption in multi-layer topology."; adaptation in a multi-layer topology.";
list switching-capability { list switching-capability {
key "switching-capability encoding"; key "switching-capability encoding";
description description
"List of supported switching capabilities"; "List of supported switching capabilities.";
reference reference
"RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions "RFC 4202: Routing Extensions in Support of
for Multi-Layer and Multi-Region Networks (MLN/MRN). Generalized Multi-Protocol Label Switching (GMPLS)
RFC 4202: Routing Extensions in Support of RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions
Generalized Multi-Protocol Label Switching (GMPLS)."; for Multi-Layer and Multi-Region Networks (MLN/MRN)";
leaf switching-capability { leaf switching-capability {
type identityref { type identityref {
base te-types:switching-capabilities; base te-types:switching-capabilities;
} }
description description
"Switching Capability for the client layer adaption."; "Switching capability for the client-layer adaptation.";
} }
leaf encoding { leaf encoding {
type identityref { type identityref {
base te-types:lsp-encoding-types; base te-types:lsp-encoding-types;
} }
description description
"Encoding supported by the client layer adaption."; "Encoding supported by the client-layer adaptation.";
} }
uses te-types:te-bandwidth; uses te-types:te-bandwidth;
} }
} }
} // te-node-tunnel-termination-point-config-attributes }
// te-node-tunnel-termination-point-config-attributes
grouping te-node-tunnel-termination-point-llc-list { grouping te-node-tunnel-termination-point-llc-list {
description description
"Local link connectivity list of a tunnel termination "LLCL of a TTP on a TE node.";
point on a TE node.";
list local-link-connectivity { list local-link-connectivity {
key "link-tp-ref"; key "link-tp-ref";
description description
"The termination capabilities between "The termination capabilities between the TTP and the LTP.
tunnel-termination-point and link termination-point. This capability information can be used to compute
The capability information can be used to compute
the tunnel path. the tunnel path.
The Interface Adjustment Capability Descriptors (IACD) The Interface Adjustment Capability Descriptors (IACDs)
(defined in RFC 6001) on each link-tp can be derived from (defined in RFC 6001) on each LTP can be derived from
this local-link-connectivity list."; this list.";
reference reference
"RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions "RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions
for Multi-Layer and Multi-Region Networks (MLN/MRN)."; for Multi-Layer and Multi-Region Networks (MLN/MRN)";
leaf link-tp-ref { leaf link-tp-ref {
type leafref { type leafref {
path "../../../../../nt:termination-point/nt:tp-id"; path "../../../../../nt:termination-point/nt:tp-id";
} }
description description
"Link termination point."; "LTP.";
} }
uses te-types:label-set-info; uses te-types:label-set-info;
uses connectivity-matrix-entry-path-attributes; uses connectivity-matrix-entry-path-attributes;
} // local-link-connectivity }
} // te-node-tunnel-termination-point-config }
// te-node-tunnel-termination-point-llc-list
grouping te-path-element { grouping te-path-element {
description description
"A group of attributes defining an element in a TE path "A group of attributes defining an element in a TE path,
such as TE node, TE link, TE atomic resource or label."; such as a TE node, TE link, TE atomic resource, or label.";
uses te-types:explicit-route-hop; uses te-types:explicit-route-hop;
} // te-path-element }
// te-path-element
grouping te-termination-point-augment { grouping te-termination-point-augment {
description description
"Augmentation for TE termination point."; "Augmentation for a TE termination point.";
leaf te-tp-id { leaf te-tp-id {
type te-types:te-tp-id; type te-types:te-tp-id;
description description
"An identifier to uniquely identify a TE termination "An identifier that uniquely identifies a TE termination
point."; point.";
} }
container te { container te {
must "../te-tp-id"; must '../te-tp-id';
presence "TE support."; presence "TE support";
description description
"Indicates TE support."; "Indicates TE support.";
uses te-termination-point-config; uses te-termination-point-config;
leaf oper-status { leaf oper-status {
type te-types:te-oper-status; type te-types:te-oper-status;
config false; config false;
description description
"The current operational state of the link termination "The current operational state of the LTP.";
point.";
} }
uses geolocation-container; uses geolocation-container;
} // te }
} // te-termination-point-augment }
// te-termination-point-augment
grouping te-termination-point-config { grouping te-termination-point-config {
description description
"TE termination point configuration grouping."; "TE termination point configuration grouping.";
leaf admin-status { leaf admin-status {
type te-types:te-admin-status; type te-types:te-admin-status;
description description
"The administrative state of the link termination point."; "The administrative state of the LTP.";
} }
leaf name { leaf name {
type string; type string;
description description
"A descriptive name for the link termination point."; "A descriptive name for the LTP.";
} }
uses interface-switching-capability-list; uses interface-switching-capability-list;
leaf inter-domain-plug-id { leaf inter-domain-plug-id {
type binary; type binary;
description description
"A topology-wide unique number that identifies on the "A network-wide unique number that identifies on the
network a connectivity supporting a given inter-domain network a connection that supports a given inter-domain
TE link. This is more flexible alternative to specifying TE link. This is a more flexible alternative to specifying
remote-te-node-id and remote-te-link-tp-id on a TE link, 'remote-te-node-id' and 'remote-te-link-tp-id' on a TE link
when the provider does not know remote-te-node-id and when the provider either does not know 'remote-te-node-id'
remote-te-link-tp-id or need to give client the and 'remote-te-link-tp-id' or needs to give the client the
flexibility to mix-n-match multiple topologies."; flexibility to mix and match multiple topologies.";
} }
leaf-list inter-layer-lock-id { leaf-list inter-layer-lock-id {
type uint32; type uint32;
description description
"Inter layer lock ID, used for path computation in a TE "Inter-layer lock ID, used for path computation in a TE
topology covering multiple layers or multiple regions."; topology covering multiple layers or multiple regions.";
reference reference
"RFC 5212: Requirements for GMPLS-Based Multi-Region and "RFC 5212: Requirements for GMPLS-Based Multi-Region and
Multi-Layer Networks (MRN/MLN). Multi-Layer Networks (MRN/MLN)
RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions
for Multi-Layer and Multi-Region Networks (MLN/MRN)."; for Multi-Layer and Multi-Region Networks (MLN/MRN)";
} }
} // te-termination-point-config }
// te-termination-point-config
grouping te-topologies-augment { grouping te-topologies-augment {
description description
"Augmentation for TE topologies."; "Augmentation for TE topologies.";
container te { container te {
presence "TE support."; presence "TE support";
description description
"Indicates TE support."; "Indicates TE support.";
container templates { container templates {
description description
"Configuration parameters for templates used for TE "Configuration parameters for templates used for a TE
topology."; topology.";
list node-template { list node-template {
if-feature template; if-feature "template";
key "name"; key "name";
leaf name { leaf name {
type te-types:te-template-name; type te-types:te-template-name;
description description
"The name to identify a TE node template."; "The name to identify a TE node template.";
} }
description description
"The list of TE node templates used to define sharable "The list of TE node templates used to define sharable
and reusable TE node attributes."; and reusable TE node attributes.";
uses template-attributes; uses template-attributes;
uses te-node-config-attributes-template; uses te-node-config-attributes-template;
} // node-template }
// node-template
list link-template { list link-template {
if-feature template; if-feature "template";
key "name"; key "name";
leaf name { leaf name {
type te-types:te-template-name; type te-types:te-template-name;
description description
"The name to identify a TE link template."; "The name to identify a TE link template.";
} }
description description
"The list of TE link templates used to define sharable "The list of TE link templates used to define sharable
and reusable TE link attributes."; and reusable TE link attributes.";
uses template-attributes; uses template-attributes;
uses te-link-config-attributes; uses te-link-config-attributes;
} // link-template }
} // templates // link-template
} // te }
} // te-topologies-augment // templates
}
// te
}
// te-topologies-augment
grouping te-topology-augment { grouping te-topology-augment {
description description
"Augmentation for TE topology."; "Augmentation for a TE topology.";
uses te-types:te-topology-identifier; uses te-types:te-topology-identifier;
container te { container te {
must "../te-topology-identifier/provider-id" must '../te-topology-identifier/provider-id'
+ " and ../te-topology-identifier/client-id" + ' and ../te-topology-identifier/client-id'
+ " and ../te-topology-identifier/topology-id"; + ' and ../te-topology-identifier/topology-id';
presence "TE support."; presence "TE support";
description description
"Indicates TE support."; "Indicates TE support.";
uses te-topology-config; uses te-topology-config;
uses geolocation-container; uses geolocation-container;
} // te }
} // te-topology-augment }
// te-topology-augment
grouping te-topology-config { grouping te-topology-config {
description description
"TE topology configuration grouping."; "TE topology configuration grouping.";
leaf name { leaf name {
type string; type string;
description description
"Name of the TE topology. This attribute is optional and can "Name of the TE topology. This attribute is optional and can
be specified by the operator to describe the TE topology, be specified by the operator to describe the TE topology,
which can be useful when network-id is not descriptive which can be useful when 'network-id' (RFC 8345) is not
and not modifiable because of being generated by the descriptive and not modifiable because of being generated
system."; by the system.";
reference
"RFC 8345: A YANG Data Model for Network Topologies";
} }
leaf preference { leaf preference {
type uint8 { type uint8 {
range "1..255"; range "1..255";
} }
description description
"Specifies a preference for this topology. A lower number "Specifies a preference for this topology. A lower number
indicates a higher preference."; indicates a higher preference.";
} }
leaf optimization-criterion { leaf optimization-criterion {
type identityref { type identityref {
base te-types:objective-function-type; base te-types:objective-function-type;
} }
description description
"Optimization criterion applied to this topology."; "Optimization criterion applied to this topology.";
reference reference
"RFC 3272: Overview and Principles of Internet Traffic "RFC 3272: Overview and Principles of Internet Traffic
Engineering."; Engineering";
} }
list nsrlg { list nsrlg {
if-feature nsrlg; if-feature "nsrlg";
key "id"; key "id";
description description
"List of NSRLGs (Not Sharing Risk Link Groups)."; "List of NSRLGs (Non-Shared Risk Link Groups).";
reference reference
"RFC 4872: RSVP-TE Extensions in Support of End-to-End "RFC 4872: RSVP-TE Extensions in Support of End-to-End
Generalized Multi-Protocol Label Switching (GMPLS) Generalized Multi-Protocol Label Switching (GMPLS)
Recovery"; Recovery";
leaf id { leaf id {
type uint32; type uint32;
description description
"Identify the NSRLG entry."; "Identifies the NSRLG entry.";
} }
leaf disjointness { leaf disjointness {
type te-types:te-path-disjointness; type te-types:te-path-disjointness;
description description
"The type of resource disjointness."; "The type of resource disjointness.";
} }
} // nsrlg }
} // te-topology-config // nsrlg
}
// te-topology-config
grouping template-attributes { grouping template-attributes {
description description
"Common attributes for all templates."; "Common attributes for all templates.";
leaf priority { leaf priority {
type uint16; type uint16;
description description
"The preference value to resolve conflicts between different "The preference value for resolving conflicts between
templates. When two or more templates specify values for different templates. When two or more templates specify
one configuration attribute, the value from the template values for one configuration attribute, the value from the
with the highest priority is used. template with the highest priority is used.
A lower number indicates a higher priority. The highest A lower number indicates a higher priority. The highest
priority is 0."; priority is 0.";
} }
leaf reference-change-policy { leaf reference-change-policy {
type enumeration { type enumeration {
enum no-action { enum no-action {
description description
"When an attribute changes in this template, the "When an attribute changes in this template, the
configuration node referring to this template does configuration node referring to this template does
not take any action."; not take any action.";
} }
skipping to change at page 87, line 37 skipping to change at line 3717
} }
enum cascade { enum cascade {
description description
"When an attribute changes in this template, the "When an attribute changes in this template, the
configuration object referring to this template applies configuration object referring to this template applies
the new attribute value to the corresponding the new attribute value to the corresponding
configuration."; configuration.";
} }
} }
description description
"This attribute specifies the action taken to a configuration "This attribute specifies the action taken for a
node that has a reference to this template."; configuration node that has a reference to this template.";
} }
} // template-attributes }
// template-attributes
/* /*
* Data nodes * Data nodes
*/ */
augment "/nw:networks/nw:network/nw:network-types" { augment "/nw:networks/nw:network/nw:network-types" {
description description
"Introduce new network type for TE topology."; "Introduces a new network type for a TE topology.";
container te-topology { container te-topology {
presence "Indicates TE topology."; presence "Indicates a TE topology";
description description
"Its presence identifies the TE topology type."; "Its presence identifies the TE topology type.";
} }
} }
augment "/nw:networks" { augment "/nw:networks" {
description description
"Augmentation parameters for TE topologies."; "Augmentation parameters for TE topologies.";
uses te-topologies-augment; uses te-topologies-augment;
} }
augment "/nw:networks/nw:network" { augment "/nw:networks/nw:network" {
when "nw:network-types/tet:te-topology" { when 'nw:network-types/tet:te-topology' {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with a
TE topology type."; TE topology type.";
} }
description description
"Configuration parameters for TE topology."; "Configuration parameters for a TE topology.";
uses te-topology-augment; uses te-topology-augment;
} }
augment "/nw:networks/nw:network/nw:node" { augment "/nw:networks/nw:network/nw:node" {
when "../nw:network-types/tet:te-topology" { when '../nw:network-types/tet:te-topology' {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with a
TE topology type."; TE topology type.";
} }
description description
"Configuration parameters for TE at node level."; "Configuration parameters for TE at the node level.";
leaf te-node-id { leaf te-node-id {
type te-types:te-node-id; type te-types:te-node-id;
description description
"The identifier of a node in the TE topology. "The identifier of a node in the TE topology.
A node is specific to a topology to which it belongs."; A node is specific to a topology to which it belongs.";
} }
container te { container te {
must "../te-node-id" { must '../te-node-id' {
description description
"te-node-id is mandatory."; "'te-node-id' is mandatory.";
} }
must "count(../nw:supporting-node)<=1" { must 'count(../nw:supporting-node)<=1' {
description description
"For a node in a TE topology, there cannot be more "For a node in a TE topology, there cannot be more
than 1 supporting node. If multiple nodes are abstracted, than one supporting node. If multiple nodes are
the underlay-topology is used."; abstracted, the 'underlay-topology' field is used.";
} }
presence "TE support."; presence "TE support";
description description
"Indicates TE support."; "Indicates TE support.";
uses te-node-augment; uses te-node-augment;
} // te }
} }
augment "/nw:networks/nw:network/nt:link" { augment "/nw:networks/nw:network/nt:link" {
when "../nw:network-types/tet:te-topology" { when '../nw:network-types/tet:te-topology' {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with a
TE topology type."; TE topology type.";
} }
description description
"Configuration parameters for TE at link level."; "Configuration parameters for TE at the link level.";
container te { container te {
must "count(../nt:supporting-link)<=1" { must 'count(../nt:supporting-link)<=1' {
description description
"For a link in a TE topology, there cannot be more "For a link in a TE topology, there cannot be more
than 1 supporting link. If one or more link paths are than one supporting link. If one or more link paths are
abstracted, the underlay is used."; abstracted, the underlay is used.";
} }
presence "TE support."; presence "TE support";
description description
"Indicates TE support."; "Indicates TE support.";
uses te-link-augment; uses te-link-augment;
} // te }
} }
augment "/nw:networks/nw:network/nw:node/" augment "/nw:networks/nw:network/nw:node/"
+ "nt:termination-point" { + "nt:termination-point" {
when '../../nw:network-types/tet:te-topology' {
when "../../nw:network-types/tet:te-topology" {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with a
TE topology type."; TE topology type.";
} }
description description
"Configuration parameters for TE at termination point level."; "Configuration parameters for TE at the termination point
level.";
uses te-termination-point-augment; uses te-termination-point-augment;
} }
augment augment "/nw:networks/nw:network/nt:link/te/bundle-stack-level/"
"/nw:networks/nw:network/nt:link/te/bundle-stack-level/" + "bundle/bundled-links/bundled-link" {
+ "bundle/bundled-links/bundled-link" { when '../../../../nw:network-types/tet:te-topology' {
when "../../../../nw:network-types/tet:te-topology" {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with a
TE topology type."; TE topology type.";
} }
description description
"Augment TE link bundled link."; "Augmentation for a TE bundled link.";
leaf src-tp-ref { leaf src-tp-ref {
type leafref { type leafref {
path "../../../../../nw:node[nw:node-id = " path "../../../../../nw:node[nw:node-id = "
+ "current()/../../../../nt:source/" + "current()/../../../../nt:source/"
+ "nt:source-node]/" + "nt:source-node]/"
+ "nt:termination-point/nt:tp-id"; + "nt:termination-point/nt:tp-id";
require-instance true; require-instance true;
} }
description description
"Reference to another TE termination point on the "Reference to another TE termination point on the
same source node."; same source node.";
} }
leaf des-tp-ref { leaf des-tp-ref {
type leafref { type leafref {
path "../../../../../nw:node[nw:node-id = " path "../../../../../nw:node[nw:node-id = "
+ "current()/../../../../nt:destination/" + "current()/../../../../nt:destination/"
+ "nt:dest-node]/" + "nt:dest-node]/"
+ "nt:termination-point/nt:tp-id"; + "nt:termination-point/nt:tp-id";
require-instance true; require-instance true;
} }
description description
"Reference to another TE termination point on the "Reference to another TE termination point on the
same destination node."; same destination node.";
} }
} }
augment augment "/nw:networks/nw:network/nw:node/te/"
"/nw:networks/nw:network/nw:node/te/" + "information-source-entry/connectivity-matrices/"
+ "information-source-entry/connectivity-matrices/" + "connectivity-matrix" {
+ "connectivity-matrix" { when '../../../../../nw:network-types/tet:te-topology' {
when "../../../../../nw:network-types/tet:te-topology" {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with a
TE topology type."; TE topology type.";
} }
description description
"Augment TE node connectivity-matrix."; "Augmentation for the TE node connectivity matrix.";
uses te-node-connectivity-matrix-attributes; uses te-node-connectivity-matrix-attributes;
} }
augment augment "/nw:networks/nw:network/nw:node/te/te-node-attributes/"
"/nw:networks/nw:network/nw:node/te/te-node-attributes/" + "connectivity-matrices/connectivity-matrix" {
+ "connectivity-matrices/connectivity-matrix" { when '../../../../../nw:network-types/tet:te-topology' {
when "../../../../../nw:network-types/tet:te-topology" {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with a
TE topology type."; TE topology type.";
} }
description description
"Augment TE node connectivity-matrix."; "Augmentation for the TE node connectivity matrix.";
uses te-node-connectivity-matrix-attributes; uses te-node-connectivity-matrix-attributes;
} }
augment augment "/nw:networks/nw:network/nw:node/te/"
"/nw:networks/nw:network/nw:node/te/" + "tunnel-termination-point/local-link-connectivities" {
+ "tunnel-termination-point/local-link-connectivities" { when '../../../../nw:network-types/tet:te-topology' {
when "../../../../nw:network-types/tet:te-topology" {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with a
TE topology type."; TE topology type.";
} }
description description
"Augment TE node tunnel termination point LLCs "Augmentation for TE node TTP LLCs (Local Link
(Local Link Connectivities)."; Connectivities).";
uses te-node-tunnel-termination-point-llc-list; uses te-node-tunnel-termination-point-llc-list;
} }
} }
<CODE ENDS> <CODE ENDS>
8. Security Considerations 8. Security Considerations
The YANG module specified in this document defines a schema for data The YANG module specified in this document defines a schema for data
that is designed to be accessed via network management protocols such that is designed to be accessed via network management protocols such
as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer
is the secure transport layer, and the mandatory-to-implement secure is the secure transport layer, and the mandatory-to-implement secure
transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
is HTTPS, and the mandatory-to-implement secure transport is TLS is HTTPS, and the mandatory-to-implement secure transport is TLS
[RFC8446]. [RFC8446].
The Network Configuration Access Control Model (NACM) [RFC8341] The Network Configuration Access Control Model (NACM) [RFC8341]
provides the means to restrict access for particular NETCONF or provides the means to restrict access for particular NETCONF or
RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or
RESTCONF protocol operations and content. RESTCONF protocol operations and content.
There are a number of data nodes defined in this YANG module that are There are a number of data nodes defined in this YANG module that are
writable/creatable/deletable (i.e., config true, which is the writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., edit-config) to in some network environments. Write operations (e.g., edit-config)
these data nodes without proper protection can have a negative effect to these data nodes without proper protection can have a negative
on network operations. These are the subtrees and data nodes and effect on network operations. These are the subtrees and data nodes
their sensitivity/vulnerability: and their sensitivity/vulnerability:
o /nw:networks/nw:network/nw:network-types/tet:te-topology * /nw:networks/nw:network/nw:network-types/tet:te-topology
This subtree specifies the TE topology type. Modifying the
configurations can make TE topology type invalid. By such This subtree specifies the TE topology type. Modifying the
modifications, a malicious attacker may disable the TE configurations can render the TE topology type invalid. By making
capabilities on the related networks and cause traffic disrupted such modifications, a malicious attacker may disable the TE
or misrouted. capabilities on the related networks and cause traffic to be
disrupted or misrouted.
* /nw:networks/tet:te
o /nw:networks/tet:te
This subtree specifies the TE node templates and TE link This subtree specifies the TE node templates and TE link
templates. Modifying the configurations in this subtree will templates. Modifying the configurations in this subtree will
change the related future TE configurations. By such change the related future TE configurations. By making such
modifications, a malicious attacker may change the TE capabilities modifications, a malicious attacker may change TE capabilities
scheduled at a future time, to cause traffic disrupted or scheduled at a future time and cause traffic to be disrupted or
misrouted. misrouted.
o /nw:networks/nw:network * /nw:networks/nw:network
This subtree specifies the topology-wide configurations, including This subtree specifies the topology-wide configurations, including
the TE topology ID and topology-wide policies. Modifying the the TE topology ID and topology-wide policies. Modifying the
configurations in this subtree can add, remove, or modify TE configurations in this subtree can add, remove, or modify TE
topologies. By adding a TE topology, a malicious attacker may topologies. By adding a TE topology, a malicious attacker may
create an unauthorized traffic network. By removing or modifying a create an unauthorized traffic network. By removing or modifying
TE topology, a malicious attacker may cause traffic disabled or a TE topology, a malicious attacker may cause traffic to be
misrouted in the specified TE topology. Such traffic changes may disabled or misrouted in the specified TE topology. Such traffic
also affect the traffic in the connected TE topologies. changes may also affect the traffic in the connected TE
topologies.
o /nw:networks/nw:network/nw:node * /nw:networks/nw:network/nw:node
This subtree specifies the configurations for TE nodes. Modifying
This subtree specifies the configurations for TE nodes. Modifying
the configurations in this subtree can add, remove, or modify TE the configurations in this subtree can add, remove, or modify TE
nodes. By adding a TE node, a malicious attacker may create an nodes. By adding a TE node, a malicious attacker may create an
unauthorized traffic path. By removing or modifying a TE node, a unauthorized traffic path. By removing or modifying a TE node, a
malicious attacker may cause traffic disabled or misrouted in the malicious attacker may cause traffic to be disabled or misrouted
specified TE node. Such traffic changes may also affect the in the specified TE node. Such traffic changes may also affect
traffic on the surrounding TE nodes and TE links in this TE the traffic on the surrounding TE nodes and TE links in this TE
topology and the connected TE topologies. topology and the connected TE topologies.
o /nw:networks/nw:network/nt:link/tet:te * /nw:networks/nw:network/nt:link/tet:te
This subtree specifies the configurations for TE links. Modifying
This subtree specifies the configurations for TE links. Modifying
the configurations in this subtree can add, remove, or modify TE the configurations in this subtree can add, remove, or modify TE
links. By adding a TE link, a malicious attacker may create an links. By adding a TE link, a malicious attacker may create an
unauthorized traffic path. By removing or modifying a TE link, a unauthorized traffic path. By removing or modifying a TE link, a
malicious attacker may cause traffic disabled or misrouted on the malicious attacker may cause traffic to be disabled or misrouted
specified TE link. Such traffic changes may also affect the on the specified TE link. Such traffic changes may also affect
traffic on the surrounding TE nodes and TE links in this TE the traffic on the surrounding TE nodes and TE links in this TE
topology and the connected TE topologies. topology and the connected TE topologies.
o /nw:networks/nw:network/nw:node/nt:termination-point * /nw:networks/nw:network/nw:node/nt:termination-point
This subtree specifies the configurations of TE link termination
points. Modifying the configurations in this subtree can add, This subtree specifies the configurations of TE LTPs. Modifying
remove, or modify TE link termination points. By adding a TE link the configurations in this subtree can add, remove, or modify TE
termination point, a malicious attacker may create an unauthorized LTPs. By adding a TE LTP, a malicious attacker may create an
traffic path. By removing or modifying a TE link termination unauthorized traffic path. By removing or modifying a TE LTP, a
point, a malicious attacker may cause traffic disabled or malicious attacker may cause traffic to be disabled or misrouted
misrouted on the specified TE link termination point. Such traffic on the specified TE LTP. Such traffic changes may also affect the
changes may also affect the traffic on the surrounding TE nodes traffic on the surrounding TE nodes and TE links in this TE
and TE links in this TE topology and the connected TE topologies. topology and the connected TE topologies.
Some of the readable data nodes in this YANG module may be considered Some of the readable data nodes in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus sensitive or vulnerable in some network environments. It is thus
important to control read access (e.g., via get, get-config, or important to control read access (e.g., via get, get-config, or
notification) to these data nodes. These are the subtrees and data notification) to these data nodes. These are the subtrees and data
nodes and their sensitivity/vulnerability: nodes and their sensitivity/vulnerability:
o /nw:networks/nw:network/nw:network-types/tet:te-topology * /nw:networks/nw:network/nw:network-types/tet:te-topology
Unauthorized access to this subtree can disclose the TE topology Unauthorized access to this subtree can disclose the TE topology
type. type.
o /nw:networks/tet:te * /nw:networks/tet:te
Unauthorized access to this subtree can disclose the TE node Unauthorized access to this subtree can disclose the TE node
templates and TE link templates. templates and TE link templates.
o /nw:networks/nw:network * /nw:networks/nw:network
Unauthorized access to this subtree can disclose the topology-wide Unauthorized access to this subtree can disclose the topology-wide
configurations, including the TE topology ID, the topology-wide configurations, including the TE topology ID, the topology-wide
policies, and the topology geolocation. policies, and the topology geolocation.
o /nw:networks/nw:network/nw:node * /nw:networks/nw:network/nw:node
Unauthorized access to this subtree can disclose the operational Unauthorized access to this subtree can disclose the operational
state information of TE nodes. state information of TE nodes.
o /nw:networks/nw:network/nt:link/tet:te * /nw:networks/nw:network/nt:link/tet:te
Unauthorized access to this subtree can disclose the operational Unauthorized access to this subtree can disclose the operational
state information of TE links. state information of TE links.
o /nw:networks/nw:network/nw:node/nt:termination-point * /nw:networks/nw:network/nw:node/nt:termination-point
Unauthorized access to this subtree can disclose the operational Unauthorized access to this subtree can disclose the operational
state information of TE link termination points. state information of TE LTPs.
9. IANA Considerations 9. IANA Considerations
This document registers the following URIs in the IETF XML registry IANA has registered the following URIs in the "ns" subregistry within
[RFC3688]. Following the format in [RFC3688], the following the "IETF XML Registry" [RFC3688].
registration is requested to be made.
URI: urn:ietf:params:xml:ns:yang:ietf-te-topology URI: urn:ietf:params:xml:ns:yang:ietf-te-topology
Registrant Contact: The IESG. Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace. XML: N/A; the requested URI is an XML namespace.
URI: urn:ietf:params:xml:ns:yang:ietf-te-topology-state URI: urn:ietf:params:xml:ns:yang:ietf-te-topology-state
Registrant Contact: The IESG. Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace. XML: N/A; the requested URI is an XML namespace.
This document registers a YANG module in the YANG Module Names IANA has registered the following YANG modules in the "YANG Module
registry [RFC7950]. Names" subregistry [RFC6020] within the "YANG Parameters" registry.
name: ietf-te-topology Name: ietf-te-topology
namespace: urn:ietf:params:xml:ns:yang:ietf-te-topology Namespace: urn:ietf:params:xml:ns:yang:ietf-te-topology
prefix: tet Prefix: tet
reference: RFC XXXX Reference: RFC 8795
name: ietf-te-topology-state
namespace: urn:ietf:params:xml:ns:yang:ietf-te-topology-state
prefix: tet-s
reference: RFC XXXX
10. References Name: ietf-te-topology-state
Namespace: urn:ietf:params:xml:ns:yang:ietf-te-topology-state
Prefix: tet-s
Reference: RFC 8795
10.1. Normative References 10. References
10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC3945] Mannie, E., Ed., "Generalized Multi-Protocol Label [RFC3945] Mannie, E., Ed., "Generalized Multi-Protocol Label
Switching (GMPLS) Architecture", RFC 3945, Switching (GMPLS) Architecture", RFC 3945,
DOI 10.17487/RFC3945, October 2004, DOI 10.17487/RFC3945, October 2004,
<https://www.rfc-editor.org/info/rfc3945>. <https://www.rfc-editor.org/info/rfc3945>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/info/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/info/rfc6242>. <https://www.rfc-editor.org/info/rfc6242>.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
skipping to change at page 96, line 14 skipping to change at line 4100
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>. <https://www.rfc-editor.org/info/rfc8040>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341, DOI Access Control Model", STD 91, RFC 8341,
10.17487/RFC8341, March 2018, <https://www.rfc- DOI 10.17487/RFC8341, March 2018,
editor.org/info/rfc8341>. <https://www.rfc-editor.org/info/rfc8341>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>. <https://www.rfc-editor.org/info/rfc8342>.
[RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N., [RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N.,
Ananthakrishnan, H., and X. Liu, "A YANG Data Model for Ananthakrishnan, H., and X. Liu, "A YANG Data Model for
Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March
2018, <https://www.rfc-editor.org/info/rfc8345>. 2018, <https://www.rfc-editor.org/info/rfc8345>.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
2018, <https://www.rfc-editor.org/info/rfc8446>. <https://www.rfc-editor.org/info/rfc8446>.
[I-D.ietf-teas-yang-te-types] [RFC8776] Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,
Saad, T., Gandhi, R., Liu, X., Beeram, V., and "Common YANG Data Types for Traffic Engineering",
I. Bryskin, "Traffic Engineering Common YANG Types", RFC 8776, DOI 10.17487/RFC8776, June 2020,
draft-ietf-teas-yang-te-types-08 (work in progress), <https://www.rfc-editor.org/info/rfc8776>.
April 2019.
10.2. Informative References 10.2. Informative References
[G.709] ITU-T, "Interfaces for the optical transport network", [G.709] ITU-T, "Interfaces for the optical transport network",
ITU-T Recommendation G.709, June 2016. ITU-T Recommendation G.709, June 2020,
<https://www.itu.int/rec/T-REC-G.709/>.
[G.805] ITU-T, "Generic functional architecture of transport [G.805] ITU-T, "Generic functional architecture of transport
networks", ITU-T Recommendation G.805, March 2000. networks", ITU-T Recommendation G.805, March 2000,
<https://www.itu.int/rec/T-REC-G.805/en>.
[G.872] ITU-T, "Architecture of optical transport networks", ITU-T [G.8080] ITU-T, "Architecture for the automatically switched
Recommendation G.872, January 2017. optical network", ITU-T Recommendation G.8080, February
2012, <https://www.itu.int/rec/T-REC-G.8080/en>.
[G.8080] ITU-T, "Architecture for the automatically switched [G.872] ITU-T, "Architecture of optical transport networks",
optical network", ITU-T Recommendation G.8080, February ITU-T Recommendation G.872, December 2019,
2012. <https://www.itu.int/rec/T-REC-G.872/en>.
[RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and [RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and
dual environments", RFC 1195, DOI 10.17487/RFC1195, dual environments", RFC 1195, DOI 10.17487/RFC1195,
December 1990, <https://www.rfc-editor.org/info/rfc1195>. December 1990, <https://www.rfc-editor.org/info/rfc1195>.
[RFC2702] Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., and J. [RFC2702] Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., and J.
McManus, "Requirements for Traffic Engineering Over MPLS", McManus, "Requirements for Traffic Engineering Over MPLS",
RFC 2702, DOI 10.17487/RFC2702, September 1999, RFC 2702, DOI 10.17487/RFC2702, September 1999,
<https://www.rfc-editor.org/info/rfc2702>. <https://www.rfc-editor.org/info/rfc2702>.
skipping to change at page 98, line 13 skipping to change at line 4197
Support of Generalized Multi-Protocol Label Switching Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 4203, DOI 10.17487/RFC4203, October 2005, (GMPLS)", RFC 4203, DOI 10.17487/RFC4203, October 2005,
<https://www.rfc-editor.org/info/rfc4203>. <https://www.rfc-editor.org/info/rfc4203>.
[RFC4206] Kompella, K. and Y. Rekhter, "Label Switched Paths (LSP) [RFC4206] Kompella, K. and Y. Rekhter, "Label Switched Paths (LSP)
Hierarchy with Generalized Multi-Protocol Label Switching Hierarchy with Generalized Multi-Protocol Label Switching
(GMPLS) Traffic Engineering (TE)", RFC 4206, (GMPLS) Traffic Engineering (TE)", RFC 4206,
DOI 10.17487/RFC4206, October 2005, DOI 10.17487/RFC4206, October 2005,
<https://www.rfc-editor.org/info/rfc4206>. <https://www.rfc-editor.org/info/rfc4206>.
[RFC4872] Lang, J., Ed., Rekhter, Y., Ed., and D. Papadimitriou, [RFC4872] Lang, J.P., Ed., Rekhter, Y., Ed., and D. Papadimitriou,
Ed., "RSVP-TE Extensions in Support of End-to-End Ed., "RSVP-TE Extensions in Support of End-to-End
Generalized Multi-Protocol Label Switching (GMPLS) Generalized Multi-Protocol Label Switching (GMPLS)
Recovery", RFC 4872, DOI 10.17487/RFC4872, May 2007, Recovery", RFC 4872, DOI 10.17487/RFC4872, May 2007,
<https://www.rfc-editor.org/info/rfc4872>. <https://www.rfc-editor.org/info/rfc4872>.
[RFC5152] Vasseur, JP., Ed., Ayyangar, A., Ed., and R. Zhang, "A [RFC5152] Vasseur, JP., Ed., Ayyangar, A., Ed., and R. Zhang, "A
Per-Domain Path Computation Method for Establishing Inter- Per-Domain Path Computation Method for Establishing Inter-
Domain Traffic Engineering (TE) Label Switched Paths Domain Traffic Engineering (TE) Label Switched Paths
(LSPs)", RFC 5152, DOI 10.17487/RFC5152, February 2008, (LSPs)", RFC 5152, DOI 10.17487/RFC5152, February 2008,
<https://www.rfc-editor.org/info/rfc5152>. <https://www.rfc-editor.org/info/rfc5152>.
skipping to change at page 98, line 40 skipping to change at line 4224
[RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic
Engineering", RFC 5305, DOI 10.17487/RFC5305, October Engineering", RFC 5305, DOI 10.17487/RFC5305, October
2008, <https://www.rfc-editor.org/info/rfc5305>. 2008, <https://www.rfc-editor.org/info/rfc5305>.
[RFC5316] Chen, M., Zhang, R., and X. Duan, "ISIS Extensions in [RFC5316] Chen, M., Zhang, R., and X. Duan, "ISIS Extensions in
Support of Inter-Autonomous System (AS) MPLS and GMPLS Support of Inter-Autonomous System (AS) MPLS and GMPLS
Traffic Engineering", RFC 5316, DOI 10.17487/RFC5316, Traffic Engineering", RFC 5316, DOI 10.17487/RFC5316,
December 2008, <https://www.rfc-editor.org/info/rfc5316>. December 2008, <https://www.rfc-editor.org/info/rfc5316>.
[RFC5329] Ishiguro, K., Manral, V., Davey, A., and A. Lindem, Ed.,
"Traffic Engineering Extensions to OSPF Version 3",
RFC 5329, DOI 10.17487/RFC5329, September 2008,
<https://www.rfc-editor.org/info/rfc5329>.
[RFC5392] Chen, M., Zhang, R., and X. Duan, "OSPF Extensions in [RFC5392] Chen, M., Zhang, R., and X. Duan, "OSPF Extensions in
Support of Inter-Autonomous System (AS) MPLS and GMPLS Support of Inter-Autonomous System (AS) MPLS and GMPLS
Traffic Engineering", RFC 5392, DOI 10.17487/RFC5392, Traffic Engineering", RFC 5392, DOI 10.17487/RFC5392,
January 2009, <https://www.rfc-editor.org/info/rfc5392>. January 2009, <https://www.rfc-editor.org/info/rfc5392>.
[RFC6001] Papadimitriou, D., Vigoureux, M., Shiomoto, K., Brungard, [RFC6001] Papadimitriou, D., Vigoureux, M., Shiomoto, K., Brungard,
D., and JL. Le Roux, "Generalized MPLS (GMPLS) Protocol D., and JL. Le Roux, "Generalized MPLS (GMPLS) Protocol
Extensions for Multi-Layer and Multi-Region Networks (MLN/ Extensions for Multi-Layer and Multi-Region Networks (MLN/
MRN)", RFC 6001, DOI 10.17487/RFC6001, October 2010, MRN)", RFC 6001, DOI 10.17487/RFC6001, October 2010,
<https://www.rfc-editor.org/info/rfc6001>. <https://www.rfc-editor.org/info/rfc6001>.
skipping to change at page 99, line 35 skipping to change at line 4261
[RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and [RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and
S. Ray, "North-Bound Distribution of Link-State and S. Ray, "North-Bound Distribution of Link-State and
Traffic Engineering (TE) Information Using BGP", RFC 7752, Traffic Engineering (TE) Information Using BGP", RFC 7752,
DOI 10.17487/RFC7752, March 2016, DOI 10.17487/RFC7752, March 2016,
<https://www.rfc-editor.org/info/rfc7752>. <https://www.rfc-editor.org/info/rfc7752>.
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>. <https://www.rfc-editor.org/info/rfc8340>.
[I-D.ietf-netconf-subscribed-notifications] [RFC8639] Voit, E., Clemm, A., Gonzalez Prieto, A., Nilsen-Nygaard,
Voit, E., Clemm, A., Prieto, A., Nilsen-Nygaard, E., and E., and A. Tripathy, "Subscription to YANG Notifications",
A. Tripathy, "Customized Subscriptions to a Publisher's RFC 8639, DOI 10.17487/RFC8639, September 2019,
Event Streams", draft-ietf-netconf-subscribed- <https://www.rfc-editor.org/info/rfc8639>.
notifications-23 (work in progress), February 2019.
[I-D.ietf-netconf-yang-push]
Clemm, A., Voit, E., Prieto, A., Tripathy, A., Nilsen-
Nygaard, E., Bierman, A., and B. Lengyel, "YANG Datastore
Subscription", draft-ietf-netconf-yang-push-22 (work in
progress), February 2019.
[I-D.liu-netmod-yang-schedule]
Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and
O. Dios, "A YANG Data Model for Configuration Scheduling",
draft-liu-netmod-yang-schedule-05 (work in progress),
March 2018.
[I-D.ietf-ccamp-wson-yang] [RFC8641] Clemm, A. and E. Voit, "Subscription to YANG Notifications
Lee, Y., Dhody, D., Zhang, X., Guo, A., Lopezalvarez, V., for Datastore Updates", RFC 8641, DOI 10.17487/RFC8641,
King, D., Yoon, B., and R. Vilata, "A Yang Data Model for September 2019, <https://www.rfc-editor.org/info/rfc8641>.
WSON Optical Networks", draft-ietf-ccamp-wson-yang-20
(work in progress), March 2019.
[I-D.ietf-ccamp-otn-topo-yang] [TEAS-TOPO]
zhenghaomian@huawei.com, z., Guo, A., Busi, I., Sharma, Bryskin, I., Beeram, V., Saad, T., and X. Liu, "TE
A., Liu, X., Belotti, S., Xu, Y., Wang, L., and O. Dios, Topology and Tunnel Modeling for Transport Networks", Work
"A YANG Data Model for Optical Transport Network in Progress, Internet-Draft, draft-ietf-teas-te-topo-and-
Topology", draft-ietf-ccamp-otn-topo-yang-06 (work in tunnel-modeling-06, 12 July 2020,
progress), February 2019. <https://tools.ietf.org/html/draft-ietf-teas-te-topo-and-
tunnel-modeling-06>.
[I-D.ietf-teas-yang-l3-te-topo] [YANG-CFG-SCHED]
Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and
O. Dios, "YANG Data Model for Layer 3 TE Topologies", O. Gonzalez de Dios, "A YANG Data Model for Configuration
draft-ietf-teas-yang-l3-te-topo-04 (work in progress), Scheduling", Work in Progress, Internet-Draft, draft-liu-
March 2019. netmod-yang-schedule-05, 1 March 2018,
<https://tools.ietf.org/html/draft-liu-netmod-yang-
schedule-05>.
[I-D.ietf-teas-te-topo-and-tunnel-modeling] [YANG-L3] Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and
Bryskin, I., Beeram, V., Saad, T., and X. Liu, "TE O. Gonzalez de Dios, "YANG Data Model for Layer 3 TE
Topology and Tunnel Modeling for Transport Networks", Topologies", Work in Progress, Internet-Draft, draft-ietf-
draft-ietf-teas-te-topo-and-tunnel-modeling-03 (work in teas-yang-l3-te-topo-08, 12 July 2020,
progress), October 2018. <https://tools.ietf.org/html/draft-ietf-teas-yang-l3-te-
topo-08>.
11. Acknowledgments [YANG-OTN] Zheng, H., Busi, I., Liu, X., Belotti, S., and O. Gonzalez
de Dios, "A YANG Data Model for Optical Transport Network
Topology", Work in Progress, Internet-Draft, draft-ietf-
ccamp-otn-topo-yang-10, 9 March 2020,
<https://tools.ietf.org/html/draft-ietf-ccamp-otn-topo-
yang-10>.
The authors would like to thank Lou Berger, Sue Hares, Mazen Khaddam, [YANG-WSON]
Cyril Margaria and Zafar Ali for participating in design discussions Zheng, H., Lee, Y., Guo, A., Lopez, V., and D. King, "A
and providing valuable insights. YANG Data Model for WSON (Wavelength Switched Optical
Networks)", Work in Progress, Internet-Draft, draft-ietf-
ccamp-wson-yang-25, 19 May 2020,
<https://tools.ietf.org/html/draft-ietf-ccamp-wson-yang-
25>.
Appendix A. Complete Model Tree Structure Appendix A. Complete Model Tree Structure
module: ietf-te-topology module: ietf-te-topology
augment /nw:networks/nw:network/nw:network-types: augment /nw:networks/nw:network/nw:network-types:
+--rw te-topology! +--rw te-topology!
augment /nw:networks: augment /nw:networks:
+--rw te! +--rw te!
+--rw templates +--rw templates
+--rw node-template* [name] {template}? +--rw node-template* [name] {template}?
| +--rw name | +--rw name
| | te-types:te-template-name | | te-types:te-template-name
skipping to change at page 163, line 5 skipping to change at line 6819
| +--rw generic? te-bandwidth | +--rw generic? te-bandwidth
+--rw inter-domain-plug-id? binary +--rw inter-domain-plug-id? binary
+--rw inter-layer-lock-id* uint32 +--rw inter-layer-lock-id* uint32
+--ro oper-status? +--ro oper-status?
| te-types:te-oper-status | te-types:te-oper-status
+--ro geolocation +--ro geolocation
+--ro altitude? int64 +--ro altitude? int64
+--ro latitude? geographic-coordinate-degree +--ro latitude? geographic-coordinate-degree
+--ro longitude? geographic-coordinate-degree +--ro longitude? geographic-coordinate-degree
Appendix B. Companion YANG Model for Non-NMDA Compliant Implementations Appendix B. Companion YANG Data Model for Non-NMDA-Compliant
Implementations
The YANG module ietf-te-topology defined in this document is designed The YANG module "ietf-te-topology" defined in Section 7 is designed
to be used in conjunction with implementations that support the to be used in conjunction with implementations that support the
Network Management Datastore Architecture (NMDA) defined in Network Management Datastore Architecture (NMDA) defined in
[RFC8342]. In order to allow implementations to use the model even in [RFC8342]. In order to allow implementations to use the model even
cases when NMDA is not supported, the following companion module in cases where NMDA is not supported, the following companion module,
ietf-te-topology-state is defined as a state model, which mirrors the "ietf-te-topology-state", is defined as a state model that mirrors
module ietf-te-topology defined earlier in this document. However, the module "ietf-te-topology". However, all data nodes in this
all data nodes in the companion module are non-configurable, to "ietf-te-topology-state" companion module are non-configurable; they
represent the applied configuration or the derived operational are provided to represent the applied configuration or the derived
states. operational states.
The companion module, ietf-te-topology-state, is redundant and SHOULD This companion module is redundant and SHOULD NOT be supported by
NOT be supported by implementations that support NMDA. implementations that support NMDA; therefore, we define it below
rather than in the main body of this document.
As the structure of the module ietf-te-topology-state mirrors that of As the structure of the module "ietf-te-topology-state" mirrors that
the module ietf-te-topology. The YANG tree of the module ietf-te- of the module "ietf-te-topology", the YANG tree of the module
topology-state is not depicted separately. "ietf-te-topology-state" is not depicted separately.
B.1. TE Topology State YANG Module B.1. TE Topology State YANG Module
This module references [RFC6001], [RFC8345], and [I-D.ietf-teas-yang- This module references [RFC6001], [RFC8345], and [RFC8776].
te-types].
<CODE BEGINS> file "ietf-te-topology-state@2019-02-07.yang" <CODE BEGINS> file "ietf-te-topology-state@2020-08-06.yang"
module ietf-te-topology-state { module ietf-te-topology-state {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-te-topology-state"; namespace "urn:ietf:params:xml:ns:yang:ietf-te-topology-state";
prefix tet-s;
prefix "tet-s";
import ietf-te-types { import ietf-te-types {
prefix "te-types"; prefix te-types;
reference reference
"I-D.ietf-teas-yang-te-types: Traffic Engineering Common YANG "RFC 8776: Common YANG Data Types for Traffic Engineering";
Types";
} }
import ietf-te-topology { import ietf-te-topology {
prefix "tet"; prefix tet;
reference
"RFC 8795: YANG Data Model for Traffic Engineering (TE)
Topologies";
} }
import ietf-network-state { import ietf-network-state {
prefix "nw-s"; prefix nw-s;
reference "RFC 8345: A YANG Data Model for Network Topologies"; reference
"RFC 8345: A YANG Data Model for Network Topologies";
} }
import ietf-network-topology-state { import ietf-network-topology-state {
prefix "nt-s"; prefix nt-s;
reference "RFC 8345: A YANG Data Model for Network Topologies"; reference
"RFC 8345: A YANG Data Model for Network Topologies";
} }
organization organization
"IETF Traffic Engineering Architecture and Signaling (TEAS) "IETF Traffic Engineering Architecture and Signaling (TEAS)
Working Group"; Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/teas/> "WG Web: <https://datatracker.ietf.org/wg/teas/>
WG List: <mailto:teas@ietf.org> WG List: <mailto:teas@ietf.org>
Editor: Xufeng Liu Editor: Xufeng Liu
<mailto:xufeng.liu.ietf@gmail.com> <mailto:xufeng.liu.ietf@gmail.com>
Editor: Igor Bryskin Editor: Igor Bryskin
<mailto:Igor.Bryskin@huawei.com> <mailto:i_bryskin@yahoo.com>
Editor: Vishnu Pavan Beeram Editor: Vishnu Pavan Beeram
<mailto:vbeeram@juniper.net> <mailto:vbeeram@juniper.net>
Editor: Tarek Saad Editor: Tarek Saad
<mailto:tsaad@juniper.net> <mailto:tsaad@juniper.net>
Editor: Himanshu Shah Editor: Himanshu Shah
<mailto:hshah@ciena.com> <mailto:hshah@ciena.com>
Editor: Oscar Gonzalez De Dios Editor: Oscar Gonzalez de Dios
<mailto:oscar.gonzalezdedios@telefonica.com>"; <mailto:oscar.gonzalezdedios@telefonica.com>";
description description
"TE topology state model. "This YANG module defines a TE topology state model.
Copyright (c) 2019 IETF Trust and the persons identified as Copyright (c) 2020 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents 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 RFC XXXX; see the This version of this YANG module is part of RFC 8795; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
revision "2019-02-07" { revision 2020-08-06 {
description "Initial revision"; description
reference "RFC XXXX: YANG Data Model for TE Topologies"; "Initial revision.";
// RFC Ed.: replace XXXX with actual RFC number and remove reference
// this note "RFC 8795: YANG Data Model for Traffic Engineering (TE)
Topologies";
} }
/* /*
* Groupings * Groupings
*/ */
grouping te-node-connectivity-matrix-attributes { grouping te-node-connectivity-matrix-attributes {
description description
"Termination point references of a connectivity matrix entry."; "Termination point references of a connectivity matrix entry.";
container from { container from {
description description
"Reference to source link termination point."; "Reference to a source Link Termination Point (LTP).";
leaf tp-ref { leaf tp-ref {
type leafref { type leafref {
path "../../../../../../nt-s:termination-point/nt-s:tp-id"; path "../../../../../../nt-s:termination-point/nt-s:tp-id";
} }
description description
"Relative reference to a termination point."; "Relative reference to a termination point.";
} }
uses te-types:label-set-info; uses te-types:label-set-info;
} }
container to { container to {
description description
"Reference to destination link termination point."; "Reference to a destination LTP.";
leaf tp-ref { leaf tp-ref {
type leafref { type leafref {
path "../../../../../../nt-s:termination-point/nt-s:tp-id"; path "../../../../../../nt-s:termination-point/nt-s:tp-id";
} }
description description
"Relative reference to a termination point."; "Relative reference to a termination point.";
} }
uses te-types:label-set-info; uses te-types:label-set-info;
} }
uses tet:connectivity-matrix-entry-path-attributes; uses tet:connectivity-matrix-entry-path-attributes;
} // te-node-connectivity-matrix-attributes }
// te-node-connectivity-matrix-attributes
grouping te-node-tunnel-termination-point-llc-list { grouping te-node-tunnel-termination-point-llc-list {
description description
"Local link connectivity list of a tunnel termination "Local Link Connectivity List (LLCL) of a Tunnel Termination
point on a TE node."; Point (TTP) on a TE node.";
list local-link-connectivity { list local-link-connectivity {
key "link-tp-ref"; key "link-tp-ref";
description description
"The termination capabilities between "The termination capabilities between the TTP and the LTP.
tunnel-termination-point and link termination-point. This capability information can be used to compute
The capability information can be used to compute
the tunnel path. the tunnel path.
The Interface Adjustment Capability Descriptors (IACD) The Interface Adjustment Capability Descriptors (IACDs)
(defined in RFC 6001) on each link-tp can be derived from (defined in RFC 6001) on each LTP can be derived from
this local-link-connectivity list."; this list.";
reference reference
"RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions "RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions
for Multi-Layer and Multi-Region Networks (MLN/MRN)."; for Multi-Layer and Multi-Region Networks (MLN/MRN)";
leaf link-tp-ref { leaf link-tp-ref {
type leafref { type leafref {
path "../../../../../nt-s:termination-point/nt-s:tp-id"; path "../../../../../nt-s:termination-point/nt-s:tp-id";
} }
description description
"Link termination point."; "LTP.";
} }
uses te-types:label-set-info; uses te-types:label-set-info;
uses tet:connectivity-matrix-entry-path-attributes; uses tet:connectivity-matrix-entry-path-attributes;
} // local-link-connectivity }
} // te-node-tunnel-termination-point-config // local-link-connectivity
}
// te-node-tunnel-termination-point-llc-list
/* /*
* Data nodes * Data nodes
*/ */
augment "/nw-s:networks/nw-s:network/nw-s:network-types" { augment "/nw-s:networks/nw-s:network/nw-s:network-types" {
description description
"Introduce new network type for TE topology."; "Introduces a new network type for a TE topology.";
container te-topology { container te-topology {
presence "Indicates TE topology."; presence "Indicates a TE topology";
description description
"Its presence identifies the TE topology type."; "Its presence identifies the TE topology type.";
} }
} }
augment "/nw-s:networks" { augment "/nw-s:networks" {
description description
"Augmentation parameters for TE topologies."; "Augmentation parameters for TE topologies.";
uses tet:te-topologies-augment; uses tet:te-topologies-augment;
} }
augment "/nw-s:networks/nw-s:network" { augment "/nw-s:networks/nw-s:network" {
when "nw-s:network-types/tet-s:te-topology" { when 'nw-s:network-types/tet-s:te-topology' {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with a
TE topology type."; TE topology type.";
} }
description description
"Configuration parameters for TE topology."; "Configuration parameters for a TE topology.";
uses tet:te-topology-augment; uses tet:te-topology-augment;
} }
augment "/nw-s:networks/nw-s:network/nw-s:node" { augment "/nw-s:networks/nw-s:network/nw-s:node" {
when "../nw-s:network-types/tet-s:te-topology" { when '../nw-s:network-types/tet-s:te-topology' {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with a
TE topology type."; TE topology type.";
} }
description description
"Configuration parameters for TE at node level."; "Configuration parameters for TE at the node level.";
leaf te-node-id { leaf te-node-id {
type te-types:te-node-id; type te-types:te-node-id;
description description
"The identifier of a node in the TE topology. "The identifier of a node in the TE topology.
A node is specific to a topology to which it belongs."; A node is specific to a topology to which it belongs.";
} }
container te { container te {
must "../te-node-id" { must '../te-node-id' {
description description
"te-node-id is mandatory."; "'te-node-id' is mandatory.";
} }
must "count(../nw-s:supporting-node)<=1" { must 'count(../nw-s:supporting-node)<=1' {
description description
"For a node in a TE topology, there cannot be more "For a node in a TE topology, there cannot be more
than 1 supporting node. If multiple nodes are abstracted, than one supporting node. If multiple nodes are
the underlay-topology is used."; abstracted, the 'underlay-topology' field is used.";
} }
presence "TE support."; presence "TE support";
description description
"Indicates TE support."; "Indicates TE support.";
uses tet:te-node-augment; uses tet:te-node-augment;
} // te }
} }
augment "/nw-s:networks/nw-s:network/nt-s:link" { augment "/nw-s:networks/nw-s:network/nt-s:link" {
when "../nw-s:network-types/tet-s:te-topology" { when '../nw-s:network-types/tet-s:te-topology' {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with a
TE topology type."; TE topology type.";
} }
description description
"Configuration parameters for TE at link level."; "Configuration parameters for TE at the link level.";
container te { container te {
must "count(../nt-s:supporting-link)<=1" { must 'count(../nt-s:supporting-link)<=1' {
description description
"For a link in a TE topology, there cannot be more "For a link in a TE topology, there cannot be more
than 1 supporting link. If one or more link paths are than one supporting link. If one or more link paths are
abstracted, the underlay is used."; abstracted, the underlay is used.";
} }
presence "TE support."; presence "TE support";
description description
"Indicates TE support."; "Indicates TE support.";
uses tet:te-link-augment; uses tet:te-link-augment;
} // te }
} }
augment "/nw-s:networks/nw-s:network/nw-s:node/" augment "/nw-s:networks/nw-s:network/nw-s:node/"
+ "nt-s:termination-point" { + "nt-s:termination-point" {
when "../../nw-s:network-types/tet-s:te-topology" { when '../../nw-s:network-types/tet-s:te-topology' {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with a
TE topology type."; TE topology type.";
} }
description description
"Configuration parameters for TE at termination point level."; "Configuration parameters for TE at the termination point
level.";
uses tet:te-termination-point-augment; uses tet:te-termination-point-augment;
} }
augment augment "/nw-s:networks/nw-s:network/nt-s:link/te/"
"/nw-s:networks/nw-s:network/nt-s:link/te/bundle-stack-level/" + "bundle-stack-level/bundle/bundled-links/bundled-link" {
+ "bundle/bundled-links/bundled-link" { when '../../../../nw-s:network-types/tet-s:te-topology' {
when "../../../../nw-s:network-types/tet-s:te-topology" {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with a
TE topology type."; TE topology type.";
} }
description description
"Augment TE link bundled link."; "Augmentation for a TE bundled link.";
leaf src-tp-ref { leaf src-tp-ref {
type leafref { type leafref {
path "../../../../../nw-s:node[nw-s:node-id = " path "../../../../../nw-s:node[nw-s:node-id = "
+ "current()/../../../../nt-s:source/" + "current()/../../../../nt-s:source/"
+ "nt-s:source-node]/" + "nt-s:source-node]/"
+ "nt-s:termination-point/nt-s:tp-id"; + "nt-s:termination-point/nt-s:tp-id";
require-instance true; require-instance true;
} }
description description
"Reference to another TE termination point on the "Reference to another TE termination point on the
same source node."; same source node.";
} }
leaf des-tp-ref { leaf des-tp-ref {
type leafref { type leafref {
path "../../../../../nw-s:node[nw-s:node-id = " path "../../../../../nw-s:node[nw-s:node-id = "
+ "current()/../../../../nt-s:destination/" + "current()/../../../../nt-s:destination/"
+ "nt-s:dest-node]/" + "nt-s:dest-node]/"
+ "nt-s:termination-point/nt-s:tp-id"; + "nt-s:termination-point/nt-s:tp-id";
require-instance true; require-instance true;
} }
description description
"Reference to another TE termination point on the "Reference to another TE termination point on the
same destination node."; same destination node.";
} }
} }
augment augment "/nw-s:networks/nw-s:network/nw-s:node/te/"
"/nw-s:networks/nw-s:network/nw-s:node/te/" + "information-source-entry/connectivity-matrices/"
+ "information-source-entry/connectivity-matrices/" + "connectivity-matrix" {
+ "connectivity-matrix" { when '../../../../../nw-s:network-types/tet-s:te-topology' {
when "../../../../../nw-s:network-types/tet-s:te-topology" {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with a
TE topology type."; TE topology type.";
} }
description description
"Augment TE node connectivity-matrix."; "Augmentation for the TE node connectivity matrix.";
uses te-node-connectivity-matrix-attributes; uses te-node-connectivity-matrix-attributes;
} }
augment augment "/nw-s:networks/nw-s:network/nw-s:node/te/"
"/nw-s:networks/nw-s:network/nw-s:node/te/te-node-attributes/" + "te-node-attributes/connectivity-matrices/"
+ "connectivity-matrices/connectivity-matrix" { + "connectivity-matrix" {
when "../../../../../nw-s:network-types/tet-s:te-topology" { when '../../../../../nw-s:network-types/tet-s:te-topology' {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with a
TE topology type."; TE topology type.";
} }
description description
"Augment TE node connectivity-matrix."; "Augmentation for the TE node connectivity matrix.";
uses te-node-connectivity-matrix-attributes; uses te-node-connectivity-matrix-attributes;
} }
augment augment "/nw-s:networks/nw-s:network/nw-s:node/te/"
"/nw-s:networks/nw-s:network/nw-s:node/te/" + "tunnel-termination-point/local-link-connectivities" {
+ "tunnel-termination-point/local-link-connectivities" { when '../../../../nw-s:network-types/tet-s:te-topology' {
when "../../../../nw-s:network-types/tet-s:te-topology" {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with a
TE topology type."; TE topology type.";
} }
description description
"Augment TE node tunnel termination point LLCs "Augmentation for TE node TTP LLCs (Local Link
(Local Link Connectivities)."; Connectivities).";
uses te-node-tunnel-termination-point-llc-list; uses te-node-tunnel-termination-point-llc-list;
} }
} }
<CODE ENDS> <CODE ENDS>
Appendix C. Example: YANG Model for Technology Specific Augmentations Appendix C. Example: YANG Data Model for Technology-Specific
Augmentations
This section provides an example YANG module to define a technology This appendix provides an example YANG module that defines a
specific TE topology model for the example-topology described in technology-specific TE topology model for the example-topology model
Section 6. described in Section 6.
This module references [RFC8345].
module example-topology { module example-topology {
yang-version 1.1; yang-version 1.1;
namespace "https://example.com/example-topology";
namespace "http://example.com/example-topology"; prefix ex-topo;
prefix "ex-topo";
import ietf-network { import ietf-network {
prefix "nw"; prefix nw;
reference
"RFC 8345: A YANG Data Model for Network Topologies";
} }
import ietf-network-topology { import ietf-network-topology {
prefix "nt"; prefix nt;
reference
"RFC 8345: A YANG Data Model for Network Topologies";
} }
import ietf-te-topology { import ietf-te-topology {
prefix "tet"; prefix tet;
reference
"RFC 8795: YANG Data Model for Traffic Engineering (TE)
Topologies";
} }
organization organization
"Example Organization"; "Example Organization";
contact contact
"Editor: Example Author"; "Editor: Example Author";
description description
"This module defines a topology data model for the example "This module defines a topology data model for the example
technology."; technology.";
revision 2018-06-15 { revision 2020-06-29 {
description description
"Initial revision."; "Initial revision.";
reference reference
"Example reference."; "Example reference";
} }
/* /*
* Data nodes * Data nodes
*/ */
augment "/nw:networks/nw:network/nw:network-types/" augment "/nw:networks/nw:network/nw:network-types/"
+ "tet:te-topology" { + "tet:te-topology" {
description description
"Augment network types to define example topology type."; "Augmentation for network types to define an example topology
type.";
container example-topology { container example-topology {
presence presence "Introduces a new network type for an example
"Introduce new network type for example topology."; topology";
description description
"Its presence identifies the example topology type."; "Its presence identifies the example topology type.";
} }
} }
augment "/nw:networks/nw:network/tet:te" { augment "/nw:networks/nw:network/tet:te" {
when "../nw:network-types/tet:te-topology/" when '../nw:network-types/tet:te-topology/'
+ "ex-topo:example-topology" { + 'ex-topo:example-topology' {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with an
example topology type."; example topology type.";
} }
description "Augment network topology."; description
"Augmentation for the network topology.";
container attributes { container attributes {
description "Attributes for example technology."; description
"Attributes for the example technology.";
leaf attribute-1 { leaf attribute-1 {
type uint8; type uint8;
description "Attribute 1 for example technology."; description
"Attribute 1 for the example technology.";
} }
} }
} }
augment "/nw:networks/nw:network/nw:node/tet:te/" augment "/nw:networks/nw:network/nw:node/tet:te/"
+ "tet:te-node-attributes" { + "tet:te-node-attributes" {
when "../../nw:network-types/tet:te-topology/" when '../../../nw:network-types/tet:te-topology/'
+ "ex-topo:example-topology" { + 'ex-topo:example-topology' {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with an
example topology type."; example topology type.";
} }
description "Augment node attributes."; description
"Augmentation for node attributes.";
container attributes { container attributes {
description "Attributes for example technology."; description
"Attributes for the example technology.";
leaf attribute-2 { leaf attribute-2 {
type uint8; type uint8;
description "Attribute 2 for example technology."; description
"Attribute 2 for the example technology.";
} }
} }
} }
augment "/nw:networks/nw:network/nw:node/tet:te/" augment "/nw:networks/nw:network/nw:node/tet:te/"
+ "tet:te-node-attributes/tet:connectivity-matrices" { + "tet:te-node-attributes/tet:connectivity-matrices" {
when "../../../../nw:network-types/tet:te-topology/" when '../../../../nw:network-types/tet:te-topology/'
+ "ex-topo:example-topology" { + 'ex-topo:example-topology' {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with an
example topology type."; example topology type.";
} }
description "Augment node connectivity matrices."; description
"Augmentation for node connectivity matrices.";
container attributes { container attributes {
description "Attributes for example technology."; description
"Attributes for the example technology.";
leaf attribute-3 { leaf attribute-3 {
type uint8; type uint8;
description "Attribute 3 for example technology."; description
"Attribute 3 for the example technology.";
} }
} }
} }
augment "/nw:networks/nw:network/nw:node/tet:te/" augment "/nw:networks/nw:network/nw:node/tet:te/"
+ "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:te-node-attributes/tet:connectivity-matrices/"
+ "tet:connectivity-matrix" { + "tet:connectivity-matrix" {
when "../../../../../nw:network-types/tet:te-topology/" when '../../../../../nw:network-types/tet:te-topology/'
+ "ex-topo:example-topology" { + 'ex-topo:example-topology' {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with an
example topology type."; example topology type.";
} }
description "Augment node connectivity matrix."; description
"Augmentation for the node connectivity matrix.";
container attributes { container attributes {
description "Attributes for example technology."; description
"Attributes for the example technology.";
leaf attribute-3 { leaf attribute-3 {
type uint8; type uint8;
description "Attribute 3 for example technology."; description
"Attribute 3 for the example technology.";
} }
} }
} }
augment "/nw:networks/nw:network/nw:node/tet:te/" augment "/nw:networks/nw:network/nw:node/tet:te/"
+ "tet:tunnel-termination-point" { + "tet:tunnel-termination-point" {
when "../../../nw:network-types/tet:te-topology/" when '../../../nw:network-types/tet:te-topology/'
+ "ex-topo:example-topology" { + 'ex-topo:example-topology' {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with an
example topology type."; example topology type.";
} }
description "Augment tunnel termination point."; description
"Augmentation for a TTP.";
container attributes { container attributes {
description "Attributes for example technology."; description
"Attributes for the example technology.";
leaf attribute-4 { leaf attribute-4 {
type uint8; type uint8;
description "Attribute 4 for example technology."; description
"Attribute 4 for the example technology.";
} }
} }
} }
augment "/nw:networks/nw:network/nw:node/nt:termination-point/" augment "/nw:networks/nw:network/nw:node/nt:termination-point/"
+ "tet:te" { + "tet:te" {
when "../../../nw:network-types/tet:te-topology/" when '../../../nw:network-types/tet:te-topology/'
+ "ex-topo:example-topology" { + 'ex-topo:example-topology' {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with an
example topology type."; example topology type.";
} }
description "Augment link termination point."; description
"Augmentation for an LTP.";
container attributes { container attributes {
description "Attributes for example technology."; description
"Attributes for the example technology.";
leaf attribute-5 { leaf attribute-5 {
type uint8; type uint8;
description "Attribute 5 for example technology."; description
"Attribute 5 for the example technology.";
} }
} }
} }
augment "/nw:networks/nw:network/nt:link/tet:te/" augment "/nw:networks/nw:network/nt:link/tet:te/"
+ "tet:te-link-attributes" { + "tet:te-link-attributes" {
when '../../../nw:network-types/tet:te-topology/'
when "../../../nw:network-types/tet:te-topology/" + 'ex-topo:example-topology' {
+ "ex-topo:example-topology" {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with an
example topology type."; example topology type.";
} }
description "Augment link attributes."; description
"Augmentation for link attributes.";
container attributes { container attributes {
description "Attributes for example technology."; description
"Attributes for the example technology.";
leaf attribute-6 { leaf attribute-6 {
type uint8; type uint8;
description "Attribute 6 for example technology."; description
"Attribute 6 for the example technology.";
} }
} }
} }
/* /*
* Augment TE bandwidth. * Augmentations for TE bandwidth.
*/ */
augment "/nw:networks/tet:te/tet:templates/" augment "/nw:networks/tet:te/tet:templates/"
+ "tet:link-template/tet:te-link-attributes/" + "tet:link-template/tet:te-link-attributes/"
+ "tet:interface-switching-capability/tet:max-lsp-bandwidth/" + "tet:interface-switching-capability/tet:max-lsp-bandwidth/"
+ "tet:te-bandwidth/tet:technology" { + "tet:te-bandwidth/tet:technology" {
case "example" { case example {
container example { container example {
description "Attributes for example technology."; description
"Attributes for the example technology.";
leaf bandwidth-1 { leaf bandwidth-1 {
type uint32; type uint32;
description "Bandwidth 1 for example technology."; description
"Bandwidth 1 for the example technology.";
} }
} }
} }
description "Augment TE bandwidth."; description
"Augmentation for TE bandwidth.";
} }
augment "/nw:networks/tet:te/tet:templates/" augment "/nw:networks/tet:te/tet:templates/"
+ "tet:link-template/tet:te-link-attributes/" + "tet:link-template/tet:te-link-attributes/"
+ "tet:max-link-bandwidth/" + "tet:max-link-bandwidth/"
+ "tet:te-bandwidth/tet:technology" { + "tet:te-bandwidth/tet:technology" {
case "example" { case example {
container example { container example {
description "Attributes for example technology."; description
"Attributes for the example technology.";
leaf bandwidth-1 { leaf bandwidth-1 {
type uint32; type uint32;
description "Bandwidth 1 for example technology."; description
"Bandwidth 1 for the example technology.";
} }
} }
} }
description "Augment TE bandwidth."; description
"Augmentation for TE bandwidth.";
} }
augment "/nw:networks/tet:te/tet:templates/" augment "/nw:networks/tet:te/tet:templates/"
+ "tet:link-template/tet:te-link-attributes/" + "tet:link-template/tet:te-link-attributes/"
+ "tet:max-resv-link-bandwidth/" + "tet:max-resv-link-bandwidth/"
+ "tet:te-bandwidth/tet:technology" { + "tet:te-bandwidth/tet:technology" {
case "example" { case example {
container example { container example {
description "Attributes for example technology."; description
"Attributes for the example technology.";
leaf bandwidth-1 { leaf bandwidth-1 {
type uint32; type uint32;
description "Bandwidth 1 for example technology."; description
"Bandwidth 1 for the example technology.";
} }
} }
} }
description "Augment TE bandwidth."; description
"Augmentation for TE bandwidth.";
} }
augment "/nw:networks/tet:te/tet:templates/" augment "/nw:networks/tet:te/tet:templates/"
+ "tet:link-template/tet:te-link-attributes/" + "tet:link-template/tet:te-link-attributes/"
+ "tet:unreserved-bandwidth/" + "tet:unreserved-bandwidth/"
+ "tet:te-bandwidth/tet:technology" { + "tet:te-bandwidth/tet:technology" {
case "example" { case example {
container example { container example {
description "Attributes for example technology."; description
"Attributes for the example technology.";
leaf bandwidth-1 { leaf bandwidth-1 {
type uint32; type uint32;
description "Bandwidth 1 for example technology."; description
"Bandwidth 1 for the example technology.";
} }
} }
} }
description "Augment TE bandwidth."; description
"Augmentation for TE bandwidth.";
} }
augment "/nw:networks/nw:network/nw:node/tet:te/" augment "/nw:networks/nw:network/nw:node/tet:te/"
+ "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:te-node-attributes/tet:connectivity-matrices/"
+ "tet:path-constraints/tet:te-bandwidth/tet:technology" { + "tet:path-constraints/tet:te-bandwidth/tet:technology" {
when "../../../../../../../nw:network-types/tet:te-topology/" when '../../../../../../nw:network-types/tet:te-topology/'
+ "ex-topo:example-topology" { + 'ex-topo:example-topology' {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with an
example topology type."; example topology type.";
} }
case "example" { case example {
container example { container example {
description "Attributes for example technology."; description
"Attributes for the example technology.";
leaf bandwidth-1 { leaf bandwidth-1 {
type uint32; type uint32;
description "Bandwidth 1 for example technology."; description
"Bandwidth 1 for the example technology.";
} }
} }
} }
description "Augment TE bandwidth."; description
"Augmentation for TE bandwidth.";
} }
augment "/nw:networks/nw:network/nw:node/tet:te/" augment "/nw:networks/nw:network/nw:node/tet:te/"
+ "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:te-node-attributes/tet:connectivity-matrices/"
+ "tet:connectivity-matrix/" + "tet:connectivity-matrix/"
+ "tet:path-constraints/tet:te-bandwidth/tet:technology" { + "tet:path-constraints/tet:te-bandwidth/tet:technology" {
when "../../../../../../../nw:network-types/tet:te-topology/" when '../../../../../../../nw:network-types/tet:te-topology/'
+ "ex-topo:example-topology" { + 'ex-topo:example-topology' {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with an
example topology type."; example topology type.";
} }
case "example" { case example {
container example { container example {
description "Attributes for example technology."; description
"Attributes for the example technology.";
leaf bandwidth-1 { leaf bandwidth-1 {
type uint32; type uint32;
description "Bandwidth 1 for example technology."; description
"Bandwidth 1 for the example technology.";
} }
} }
} }
description "Augment TE bandwidth."; description
"Augmentation for TE bandwidth.";
} }
augment "/nw:networks/nw:network/nw:node/tet:te/" augment "/nw:networks/nw:network/nw:node/tet:te/"
+ "tet:information-source-entry/tet:connectivity-matrices/" + "tet:information-source-entry/tet:connectivity-matrices/"
+ "tet:path-constraints/tet:te-bandwidth/tet:technology" { + "tet:path-constraints/tet:te-bandwidth/tet:technology" {
when "../../../../../../../nw:network-types/tet:te-topology/" when '../../../../../../nw:network-types/tet:te-topology/'
+ "ex-topo:example-topology" { + 'ex-topo:example-topology' {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with an
example topology type."; example topology type.";
} }
case "example" { case example {
container example { container example {
description "Attributes for example technology."; description
"Attributes for the example technology.";
leaf bandwidth-1 { leaf bandwidth-1 {
type uint32; type uint32;
description "Bandwidth 1 for example technology."; description
"Bandwidth 1 for the example technology.";
} }
} }
} }
description "Augment TE bandwidth."; description
"Augmentation for TE bandwidth.";
} }
augment "/nw:networks/nw:network/nw:node/tet:te/" augment "/nw:networks/nw:network/nw:node/tet:te/"
+ "tet:information-source-entry/tet:connectivity-matrices/" + "tet:information-source-entry/tet:connectivity-matrices/"
+ "tet:connectivity-matrix/" + "tet:connectivity-matrix/"
+ "tet:path-constraints/tet:te-bandwidth/tet:technology" { + "tet:path-constraints/tet:te-bandwidth/tet:technology" {
when "../../../../../../../nw:network-types/tet:te-topology/" when '../../../../../../../nw:network-types/tet:te-topology/'
+ "ex-topo:example-topology" { + 'ex-topo:example-topology' {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with an
example topology type."; example topology type.";
} }
case "example" { case example {
container example { container example {
description "Attributes for example technology."; description
"Attributes for the example technology.";
leaf bandwidth-1 { leaf bandwidth-1 {
type uint32; type uint32;
description "Bandwidth 1 for example technology."; description
"Bandwidth 1 for the example technology.";
} }
} }
} }
description "Augment TE bandwidth."; description
"Augmentation for TE bandwidth.";
} }
augment "/nw:networks/nw:network/nw:node/tet:te/" augment "/nw:networks/nw:network/nw:node/tet:te/"
+ "tet:tunnel-termination-point/tet:client-layer-adaptation/" + "tet:tunnel-termination-point/"
+ "tet:switching-capability/tet:te-bandwidth/tet:technology" { + "tet:client-layer-adaptation/tet:switching-capability/"
when "../../../../../../../nw:network-types/tet:te-topology/" + "tet:te-bandwidth/tet:technology" {
+ "ex-topo:example-topology" { when '../../../../../../nw:network-types/tet:te-topology/'
+ 'ex-topo:example-topology' {
description description
"Augmentation parameters apply only for networks with "Augmentation parameters apply only for networks with an
example topology type."; example topology type.";
} }
case "example" { case example {
container example { container example {
description "Attributes for example technology."; description
"Attributes for the example technology.";
leaf bandwidth-1 { leaf bandwidth-1 {
type uint32; type uint32;
description "Bandwidth 1 for example technology."; description
"Bandwidth 1 for the example technology.";
} }
} }
} }
description "Augment TE bandwidth."; description
"Augmentation for TE bandwidth.";
} }
augment "/nw:networks/nw:network/nw:node/tet:te/" 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/"