draft-ietf-teas-yang-te-topo-01.txt   draft-ietf-teas-yang-te-topo-02.txt 
TEAS Working Group Xufeng Liu TEAS Working Group Xufeng Liu
Internet Draft Ericsson Internet Draft Ericsson
Intended status: Standards Track Igor Bryskin Intended status: Standards Track Igor Bryskin
ADVA Optical Networking ADVA Optical Networking
Vishnu Pavan Beeram Vishnu Pavan Beeram
Juniper Networks Juniper Networks
Tarek Saad Tarek Saad
Cisco Systems Inc Cisco Systems Inc
Himanshu Shah Himanshu Shah
Ciena Ciena
Oscar Gonzalez De Dios Oscar Gonzalez De Dios
Telefonica Telefonica
Expires: January 6, 2016 July 6, 2015 Expires: April 19, 2016 October 19, 2015
YANG Data Model for TE Topologies YANG Data Model for TE Topologies
draft-ietf-teas-yang-te-topo-01 draft-ietf-teas-yang-te-topo-02
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on January 6, 2016. This Internet-Draft will expire on April 19, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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 (http://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 carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License. warranty as described in the Simplified BSD License.
Abstract Abstract
This document defines a YANG data model for representing, retrieving This document defines a YANG data model for representing, retrieving
and manipulating TE Topologies. The model serves as a base model and manipulating TE Topologies. The model serves as a base model
that other technology specific TE Topology models can augment. that other technology specific TE Topology models can augment.
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [RFC2119]. document are to be interpreted as described in RFC-2119 [RFC2119].
Table of Contents Table of Contents
1. Introduction...................................................3 1. Introduction...................................................3
1.1. Terminology...............................................3 1.1. Terminology...............................................3
1.2. Tree Structure - Legend...................................4 1.2. Tree Structure - Legend...................................4
1.3. Prefixes in Data Node Names...............................4 1.3. Prefixes in Data Node Names...............................5
2. Characterizing TE Topologies...................................5 2. Characterizing TE Topologies...................................5
3. Model Applicability............................................6 3. Model Applicability............................................6
3.1. Native TE Topologies......................................6 3.1. Native TE Topologies......................................6
3.2. Customized TE Topologies..................................8 3.2. Customized TE Topologies..................................8
4. Modeling Considerations.......................................10 4. Modeling Considerations.......................................10
4.1. Generic extensible Model.................................10 4.1. Generic network topology building blocks.................10
4.2. Model Structure..........................................10 4.2. Technology agnostic TE Topology model....................11
4.3. Topology Identifiers.....................................11 4.3. Model Structure..........................................11
4.4. Generic TE Link Attributes...............................12 4.4. Topology Identifiers.....................................12
4.5. Generic TE Node Attributes...............................12 4.5. Generic TE Link Attributes...............................13
4.6. TED Information Sources..................................13 4.6. Generic TE Node Attributes...............................13
4.7. Overlay/Underlay Relationship............................14 4.7. TED Information Sources..................................14
4.8. Scheduling Parameters....................................15 4.8. Overlay/Underlay Relationship............................14
4.9. Templates................................................15 4.9. Scheduling Parameters....................................16
4.10. Notifications...........................................16 4.10. Templates...............................................16
4.11. Open Items..............................................17 4.11. Notifications...........................................17
5. Tree Structure................................................17 4.12. Open Items..............................................18
6. TE Topology Yang Module.......................................42
7. Security Considerations.......................................78
8. IANA Considerations...........................................78
9. References....................................................78
9.1. Normative References.....................................78
9.2. Informative References...................................79
10. Acknowledgments..............................................79
1. Introduction 5. Tree Structure................................................18
6. TE Topology Yang Module.......................................43
7. Security Considerations.......................................79
8. IANA Considerations...........................................79
9. References....................................................79
9.1. Normative References.....................................79
9.2. Informative References...................................80
10. Acknowledgments..............................................80
Appendix A - Schedule Model......................................80
A.1 Tree Structure............................................80
A.2 YANG Module...............................................81
Contributors.....................................................82
Authors' Addresses...............................................82
The Traffic Engineering Database (TED) is an essential component of 1. Introduction
Traffic Engineered (TE) systems that are based on MPLS-TE [RFC2702]
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
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
Traffic Engineered system. The TE Topology is the topology on which
path computational algorithms are run to compute Traffic Engineered
Paths (TE Paths).
This document defines a YANG [RFC6020] data model for representing The Traffic Engineering Database (TED) is an essential component of
and manipulating TE Topologies. This model contains technology Traffic Engineered (TE) systems that are based on MPLS-TE [RFC2702]
agnostic TE Topology building blocks that can be augmented and used and GMPLS [RFC3945]. The TED is a collection of all TE information
by other technology-specific TE Topology models. 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
TED. There could be one or more TE Topologies present in a given
Traffic Engineered system. The TE Topology is the topology on which
path computational algorithms are run to compute Traffic Engineered
Paths (TE Paths).
1.1. Terminology This document defines a YANG [RFC6020] data model for representing
and manipulating TE Topologies. This model contains technology
agnostic TE Topology building blocks that can be augmented and used
by other technology-specific TE Topology models.
TED: The Traffic Engineering Database is a collection of all TE 1.1. Terminology
information about all TE nodes and TE links in a given network.
TE-Topology: The TE Topology is a schematic arrangement of TE nodes TED: The Traffic Engineering Database is a collection of all TE
and TE links in a given TED. It forms the basis for a graph suitable information about all TE nodes and TE links in a given network.
for TE path computations.
Native TE Topology: Native TE Topology is a topology that is native TE-Topology: The TE Topology is a schematic arrangement of TE nodes
to a given provider network. This is the topology on which path and TE links in a given TED. It forms the basis for a graph suitable
computational algorithms are run to compute TE Paths. for TE path computations.
Customized TE Topology: Customized TE Topology is a custom topology Native TE Topology: Native TE Topology is a topology that is native
that is produced by a provider for a given Client. This topology to a given provider network. This is the topology on which path
typically augments the Client's Native TE Topology. Path computational algorithms are run to compute TE Paths.
computational algorithms aren't typically run on the Customized TE
Topology; they are run on the Client's augmented Native TE Topology.
1.2. Tree Structure - Legend Customized TE Topology: Customized TE Topology is a custom topology
that is produced by a provider for a given Client. This topology
typically augments the Client's Native TE Topology. Path
computational algorithms aren't typically run on the Customized TE
Topology; they are run on the Client's augmented Native TE Topology.
A simplified graphical representation of the data model is presented 1.2. Tree Structure - Legend
in Section 5 of this document. The following notations are used for
the YANG model data tree representation.
<status> <flags> <name> <opts> <type> A simplified graphical representation of the data model is presented
in Section 5 of this document. The following notations are used for
the YANG model data tree representation.
<status> is one of: <status> <flags> <name> <opts> <type>
+ for current
x for deprecated
o for obsolete
<flags> is one of: <status> is one of:
rw for read-write configuration data + for current
ro for read-only non-configuration data x for deprecated
-x for execution rpcs o for obsolete
-n for notifications
<name> is the name of the node <flags> is one of:
rw for read-write configuration data
ro for read-only non-configuration data
-x for execution rpcs
-n for notifications
If the node is augmented into the tree from another module, <name> is the name of the node
its name is printed as <prefix>:<name>
<opts> is one of: If the node is augmented into the tree from another module,
? for an optional leaf or node its name is printed as <prefix>:<name>
! for a presence container
* for a leaf-list or list
Brackets [<keys>] for a list's keys
Curly braces {<condition>} for optional feature that make
node conditional
Colon : for marking case nodes <opts> is one of:
Ellipses ("...") subtree contents not shown ? for an optional leaf or node
! for a presence container
* for a leaf-list or list
Brackets [<keys>] for a list's keys
Curly braces {<condition>} for optional feature that make
node conditional
Parentheses enclose choice and case nodes, and case nodes are Colon : for marking case nodes
also marked with a colon (":"). Ellipses ("...") subtree contents not shown
<type> is the name of the type for leafs and leaf-lists. Parentheses enclose choice and case nodes, and case nodes are
also marked with a colon (":").
1.3. Prefixes in Data Node Names <type> is the name of the type for leafs and leaf-lists.
In this document, names of data nodes and other data model objects 1.3. Prefixes in Data Node Names
are prefixed using the standard prefix associated with the
corresponding YANG imported modules, as shown in Table 1.
+--------+-----------------+-----------+ In this document, names of data nodes and other data model objects
| Prefix | YANG module | Reference | are prefixed using the standard prefix associated with the
+--------+-----------------+-----------+ corresponding YANG imported modules, as shown in Table 1.
| yang | ietf-yang-types | [RFC6991] |
| inet | ietf-inet-types | [RFC6991] |
+--------+-----------------+-----------+
Table 1: Prefixes and corresponding YANG modules +--------+-----------------+-----------+
| Prefix | YANG module | Reference |
+--------+-----------------+-----------+
| yang | ietf-yang-types | [RFC6991] |
| inet | ietf-inet-types | [RFC6991] |
+--------+-----------------+-----------+
2. Characterizing TE Topologies Table 1: Prefixes and corresponding YANG modules
The data model proposed by this document takes the following 2. Characterizing TE Topologies
characteristics of TE Topologies into account:
- TE Topology is an abstract control-plane representation of the The data model proposed by this document takes the following
data-plane topology. Hence attributes specific to the data-plane characteristics of TE Topologies into account:
must make their way into the corresponding TE Topology modeling.
The TE Topology comprises of dynamic auto-discovered data (data
that may change frequently - example: unreserved bandwidth
available on data-plane links) as well as fairly static data (data
that rarely changes- examples: layer network identification,
switching and adaptation capabilities and limitations, fate
sharing, administrative colors) associated with data-plane nodes
and links. It is possible for a single TE Topology to encompass TE
information at multiple switching layers.
- TE Topologies are protocol independent. Information about - TE Topology is an abstract control-plane representation of the
topological elements may be learnt via link-state protocols, but data-plane topology. Hence attributes specific to the data-plane
the topology can exist without being dependent on any particular must make their way into the corresponding TE Topology modeling.
protocol. The TE Topology comprises of dynamic auto-discovered data (data
that may change frequently - example: unreserved bandwidth
available on data-plane links) as well as fairly static data (data
that rarely changes- examples: layer network identification,
switching and adaptation capabilities and limitations, fate
sharing, administrative colors) associated with data-plane nodes
and links. It is possible for a single TE Topology to encompass TE
information at multiple switching layers.
- TE Topology may not be congruent to the routing topology (topology - TE Topologies are protocol independent. Information about
constructed based on routing adjacencies) in a given TE System. topological elements may be learnt via link-state protocols, but
There isn't always a one-to-one association between a TE-link and the topology can exist without being dependent on any particular
a routing adjacency. For example, the presence of a TE link protocol.
between a pair of nodes doesn't necessarily imply the existence of
a routing-adjacency between these nodes.
- Each TE Topological element has an information source associated - TE Topology may not be congruent to the routing topology (topology
with it. In some scenarios, there could be more than one constructed based on routing adjacencies) in a given TE System.
information source associated with each topological element. There isn't always a one-to-one association between a TE-link and
a routing adjacency. For example, the presence of a TE link
between a pair of nodes doesn't necessarily imply the existence of
a routing-adjacency between these nodes.
- TE Topologies can be hierarchical. Each node and link of a given - Each TE Topological element has an information source associated
TE Topology can be associated with respective underlay topology. with it. In some scenarios, there could be more than one
This means that each node and link of a given TE Topology can be information source associated with each topological element.
associated with an independent stack of supporting TE Topologies.
- TE Topologies can be customized. TE topologies of a given network - TE Topologies can be hierarchical. Each node and link of a given
presented by the network provider to its client could be TE Topology can be associated with respective underlay topology.
customized on per-client request basis. This customization could This means that each node and link of a given TE Topology can be
be performed by provider, by client or by provider/client associated with an independent stack of supporting TE Topologies.
negotiation. The relationship between a customized topology (as
presented to the client) and provider's native topology (as known
in its entirety to the provider itself) could be captured as
hierarchical (overlay-underlay), but otherwise the two topologies
are decoupled from each other.
3. Model Applicability - TE Topologies can be customized. TE topologies of a given network
presented by the network provider to its client could be
customized on per-client request basis. This customization could
be performed by provider, by client or by provider/client
negotiation. The relationship between a customized topology (as
presented to the client) and provider's native topology (as known
in its entirety to the provider itself) could be captured as
hierarchical (overlay-underlay), but otherwise the two topologies
are decoupled from each other.
3.1. Native TE Topologies 3. Model Applicability
The model discussed in this draft can be used to represent and 3.1. Native TE Topologies
retrieve native TE topologies on a given TE system.
+---+ +---+ +---+ +---+ +---+ The model discussed in this draft can be used to represent and
| R1|-------| R2|--------| R3|---------| R4|---------| R5| retrieve native TE topologies on a given TE system.
+---+ +---+ +---+ +---+ +---+
| / \ / \ /
| / \ / \ /
| / \ / \ /
| / \ / \ /
| / \ / \ /
+---+ +---+ +---+ +---+
| R6|-------------| R7| | R8|---------| R9|
+---+ +---+ +---+ +---+
Figure 1a: Example Network Topology +---+ +---+ +---+ +---+ +---+
| R1|-------| R2|--------| R3|---------| R4|---------| R5|
+---+ +---+ +---+ +---+ +---+
| / \ / \ /
| / \ / \ /
| / \ / \ /
| / \ / \ /
| / \ / \ /
+---+ +---+ +---+ +---+
| R6|-------------| R7| | R8|---------| R9|
+---+ +---+ +---+ +---+
--------------- Figure 1a: Example Network Topology
| Native | | [ ] TE Node
| TE-Topology | | +++ TE Link
--------------- o--------------
__________________
[R1] ++++ [R2] ++++ [R3] ++++ [R4] ++++ [R5]
+ + + + + +
+ + + + + +
+ + ++ ++
[R6] +++++++++ [R7] [R8] ++++ [R9]
Figure 1b: Native TE Topology as seen on Node R3 Consider the network topology depicted in Figure 1a (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 1b. The data model proposed in
this document can be used to retrieve/represent this TE topology.
Consider the network topology depicted in Figure 1a (R1 .. R9 are ---------------
nodes representing routers). An implementation MAY choose to | Native | | [ ] TE Node
construct a native TE Topology using all nodes and links present in | TE-Topology | | +++ TE Link
the given TED as depicted in Figure 1b. The data model proposed in --------------- o--------------
this document can be used to retrieve/represent this TE topology. __________________
[R1] ++++ [R2] ++++ [R3] ++++ [R4] ++++ [R5]
+ + + + + +
+ + + + + +
+ + ++ ++
[R6] +++++++++ [R7] [R8] ++++ [R9]
: Figure 1b: Native TE Topology as seen on Node R3
TE info distributed via ISIS-TE : TE info distributed via OSPF-TE
:
+---+ +---+ +---+ +---+ +---+
| R1|-------| R2|--------| R3|---------| R4|---------| R5|
+---+ +---+ +---+ +---+ +---+
| / : \ / \ /
| / : \ / \ /
| / : \ / \ /
| / : \ / \ /
| / : \ / \ /
+---+ +---+ : +---+ +---+
| R6|-------------| R7| : | R8|---------| R9|
+---+ +---+ : +---+ +---+
:
Figure 2a: Example Network Topology Consider the case of the topology being split in a way that some
nodes participate in OSPF-TE while others participate in ISIS-TE
(Figure 2a). An implementation MAY choose to construct separate TE
Topologies based on the information source. The native TE Topologies
constructed using only nodes and links that were learnt via a
specific information source are depicted in Figure 2b. The data
model proposed in this document can be used to retrieve/represent
these TE topologies.
----------------------- : ----------------------- Similarly, the data model can be used to represent/retrieve a TE
|Native TE Topology | : |Native TE Topology | Topology that is constructed using only nodes and links that belong
|Info-Source: ISIS-TE | : |Info-Source: OSPF-TE | to a particular technology layer. The data model is flexible enough
----------------------- : ----------------------- to retrieve and represent many such native TE Topologies.
:
[R1] ++++ [R2] ++++ [R3] : [R3'] ++++ [R4] ++++ [R5]
+ + : + + + +
+ + : + + + +
+ + : ++ ++
[R6] +++++++++ [R7] : [R8] ++++ [R9]
Figure 2b: Native TE Topologies as seen on Node R3 :
TE info distributed via ISIS-TE : TE info distributed via OSPF-TE
:
+---+ +---+ +---+ +---+ +---+
| R1|-------| R2|--------| R3|---------| R4|---------| R5|
+---+ +---+ +---+ +---+ +---+
| / : \ / \ /
| / : \ / \ /
| / : \ / \ /
| / : \ / \ /
| / : \ / \ /
+---+ +---+ : +---+ +---+
| R6|-------------| R7| : | R8|---------| R9|
+---+ +---+ : +---+ +---+
:
Consider the case of the topology being split in a way that some Figure 2a: Example Network Topology
nodes participate in OSPF-TE while others participate in ISIS-TE
(Figure 2a). An implementation MAY choose to construct separate TE
Topologies based on the information source. The native TE Topologies
constructed using only nodes and links that were learnt via a
specific information source are depicted in Figure 2b. The data
model proposed in this document can be used to retrieve/represent
these 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 |Native TE Topology | : |Native TE Topology |
to a particular technology layer. The data model is flexible enough |Info-Source: ISIS-TE | : |Info-Source: OSPF-TE |
to retrieve and represent many such native TE Topologies. ----------------------- : -----------------------
:
[R1] ++++ [R2] ++++ [R3] : [R3'] ++++ [R4] ++++ [R5]
+ + : + + + +
+ + : + + + +
+ + : ++ ++
[R6] +++++++++ [R7] : [R8] ++++ [R9]
3.2. Customized TE Topologies Figure 2b: Native TE Topologies as seen on Node R3
The model discussed in this draft can be used to represent, retrieve 3.2. Customized TE Topologies
and manipulate customized TE Topologies. The model allows the
provider to present the network in abstract TE Terms on a per client
basis. These customized topologies contain sufficient information
for the path computing client to select paths according to its
policies.
| +---+ /-\ The model discussed in this draft can be used to represent, retrieve
| | | Router ( ) WDM and manipulate customized TE Topologies. The model allows the
| +---+ Node \-/ node provider to present the network in abstract TE Terms on a per client
| basis. These customized topologies contain sufficient information
o----------------------------_____ for the path computing client to select paths according to its
__ policies.
+---+ /-\ /-\ /-\ +---+
| R1|-------( A )--------( C )---------( E )---------| R3|
+---+ \-/ \-/ \-/ +---+
/ \ / \
/ \ / \
/ \ / \
/ \ / \
/ \ / \
+---+ /-\ /-\ /-\ +---+
| R2|---------( B )---------( D )---------( F )---------| R4|
+---+ \-/ \-/ \-/ +---+
Figure 3: Example packet optical topology | +---+ /-\
| | | Router ( ) WDM
| +---+ Node \-/ node
|
o----------------------------_____
__
+---+ /-\ /-\ /-\ +---+
| R1|-------( A )--------( C )---------( E )---------| R3|
+---+ \-/ \-/ \-/ +---+
/ \ / \
/ \ / \
/ \ / \
/ \ / \
/ \ / \
+---+ /-\ /-\ /-\ +---+
| R2|---------( B )---------( D )---------( F )---------| R4|
+---+ \-/ \-/ \-/ +---+
Consider the network topology depicted in Figure 3. This is a Figure 3: Example packet optical topology
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.
| ***** B-F WDM Path Consider the network topology depicted in Figure 3. This is a
| @@@@@ B-E WDM Path typical packet optical transport deployment scenario where the WDM
| $$$$$ A-E WDM Path layer network domain serves as a Server Network Domain providing
o--------------------_ 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.
+---+ /-\ $$$$$$$$ /-\ $$$$$$$$$ /-\ +---+ | ***** B-F WDM Path
| R1|-------( A )--------( C )---------( E )---------| R3| | @@@@@ B-E WDM Path
+---+ \-/ @\-/ @@@@@@@@@ \-/ +---+ | $$$$$ A-E WDM Path
@/ \ / \ o--------------------_
@/ \ / \
@/ \ / \
@/ \ / \
@/ \ / \
+---+ /-\ ********* /-\ ********* /-\ +---+
| R2|---------( B )---------( D )---------( F )---------| R4|
+---+ \-/ \-/ \-/ +---+
Figure 4a: Paths within the provider domain +---+ /-\ $$$$$$$$ /-\ $$$$$$$$$ /-\ +---+
| R1|-------( A )--------( C )---------( E )---------| R3|
+---+ \-/ @\-/ @@@@@@@@@ \-/ +---+
@/ \ / \
@/ \ / \
@/ \ / \
@/ \ / \
@/ \ / \
+---+ /-\ ********* /-\ ********* /-\ +---+
| R2|---------( B )---------( D )---------( F )---------| R4|
+---+ \-/ \-/ \-/ +---+
++++++++ [A] ++++++++++++++++++++ [E] +++++++++ Figure 4a: Paths within the provider domain
+++++
++++
++++
++++
++++
++++++++ [B] ++++++++++++++++++++ [F] +++++++++
Figure 4b: Customized TE Topology provided to the Client ++++++++ [A] ++++++++++++++++++++ [E] +++++++++
+++++
++++
++++
++++
++++
++++++++ [B] ++++++++++++++++++++ [F] +++++++++
[R1] ++++++++ [A] ++++++++++++++++++++ [E] +++++++++ [R3] Figure 4b: Customized TE Topology provided to the Client
+++++
++++
++++
++++
++++
[R2] ++++++++ [B] ++++++++++++++++++++ [F] +++++++++ [R4]
Figure 4c: Customized TE Topology merged with the Client's Native TE The goal here is to augment the Client TE Topology with a customized
Topology TE Topology provided by the WDM network. Given the availability of
the paths A-E, B-F and B-E (Figure 4a), a customized TE Topology as
depicted in Figure 4b 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 4c.
The goal here is to augment the Client TE Topology with a customized [R1] ++++++++ [A] ++++++++++++++++++++ [E] +++++++++ [R3]
TE Topology provided by the WDM network. Given the availability of +++++
the paths A-E, B-F and B-E (Figure 4a), a customized TE Topology as ++++
depicted in Figure 4b 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 4c. ++++
[R2] ++++++++ [B] ++++++++++++++++++++ [F] +++++++++ [R4]
The data model proposed in this document can be used to Figure 4c: Customized TE Topology merged with the Client's Native TE
retrieve/represent/manipulate the customized TE Topology depicted in Topology
Figure 4b.
4. Modeling Considerations The data model proposed in this document can be used to
retrieve/represent/manipulate the customized TE Topology depicted in
Figure 4b.
4.1. Generic extensible Model 4. Modeling Considerations
The TE Topology model proposed in this document is meant to be 4.1. Generic network topology building blocks
technology agnostic. Other technology specific TE Topology models
can augment and use the building blocks provided by the proposed
model.
+-------------------+ The generic network topology building blocks are discussed in [YANG-
| Generic | NET-TOPO]. The TE Topology model proposed in this document augments
| TE Topology Model | and uses the ietf-network-topology module defined in [YANG-NET-
+-------------------+ TOPO].
|
+-------------+-------------+-------------+
| | | |
V V V V
+------------+ +------------+
| Technology | | Technology |
| Specific | ...................... | Specific |
| TE Topology| | TE Topology|
| Model 1 | | Model n |
+------------+ +------------+
Figure 5: Extending the generic model +------------------------+
| Generic |
| Network Topology Model |
| (ietf-network-topology)|
+------------------------+
|
|
|
V
+------------------------+
| TE Topology |
| Model |
| |
+------------------------+
4.2. Model Structure Figure 5: Augmenting the Generic Network Topology Model
The high-level model structure proposed by this document is as shown 4.2. Technology agnostic TE Topology model
below:
+--rw te-topologies The TE Topology model proposed in this document is meant to be
| +--rw topology* [provider-id client-id te-topology-id] technology agnostic. Other technology specific TE Topology models
| | .......... can augment and use the building blocks provided by the proposed
| | +--rw node* [te-node-id] model.
| | | ..........
| | | +--rw te-link* [te-link-id]
| | | ..........
| | +--rw link* [source-te-node-id source-te-link-id dest-te-
node-id dest-te-link-id]
| | | ..........
| +--rw node-template* [name] {template}?
| | ..........
| +--rw link-template* [name] {template}?
| | ..........
+--ro te-topologies-state
+--ro topology* [provider-id client-id te-topology-id]
| ..........
+--ro node* [te-node-id]
| | ..........
| +--ro te-node-state
| ..........
+--ro link* [source-te-node-id source-te-link-id dest-te-
node-id dest-te-link-id]
| | ..........
| +--ro te-link-state
| ..........
notifications: +-------------------+
+---n te-node-event | Generic |
| .......... | TE Topology Model |
+---n te-link-event +-------------------+
.......... |
+-------------+-------------+-------------+
| | | |
V V V V
+------------+ +------------+
| Technology | | Technology |
| Specific | ...................... | Specific |
| TE Topology| | TE Topology|
| Model 1 | | Model n |
+------------+ +------------+
4.3. Topology Identifiers Figure 6: Augmenting the Technology agnostic TE Topology model
The TE-Topology is uniquely identified by a key that has 3 4.3. Model Structure
constituents - te-topology-id, provider-id and client-id. The
combination of provider-id and te-topology-id uniquely identifies a
native TE Topology on a given provider. The client-id is used only
when Customized TE Topologies come into play; a value of "0" is used
as the client-id for native TE Topologies.
+--rw topology* [provider-id client-id te-topology-id] The high-level model structure proposed by this document is as shown
| +--rw provider-id te-global-id below:
| +--rw client-id te-global-id
| +--rw te-topology-id te-topology-id
4.4. Generic TE Link Attributes module: ietf-te-topology
augment /nw:network/nw:network-types:
+--rw te-topology!
augment /nw:network:
+--rw te!
+--rw provider-id te-global-id
+--rw client-id te-global-id
+--rw te-topology-id te-topology-id
+--rw config
| ............
+--ro state
| ............
+--rw templates
+--rw node-template* [name] {template}?
| ............
+--rw link-template* [name] {template}?
............
The model covers the definitions for generic TE Link attributes - augment /nw:network/nw:node:
bandwidth, admin groups, SRLGs, switching capabilities, TE metric +--rw te!
extensions etc. +--rw te-node-id te-node-id
+--rw config
| ............
+--ro state
............
+--rw te-link-attributes augment /nw:network/nt:link:
| .......... +--rw te!
| +--rw performance-metric-throttle {te-performance-metric}? +--rw config
| | .......... | ..........
| +--rw administrative-group? te-types:admin-groups +--ro state
| +--rw max-link-bandwidth? decimal64 ..........
| +--rw max-resv-link-bandwidth? decimal64
| +--rw unreserved-bandwidth* [priority]
| | ..........
| +--rw te-default-metric? uint32
| +--rw performance-metric {te-performance-metric}?
| | ..........
| +--rw link-protection-type? enumeration
| +--rw interface-switching-capabilities* [switching-capability]
| | ..........
| +--rw te-srlgs
| | ..........
4.5. Generic TE Node Attributes augment /nw:network/nw:node/nt:termination-point:
+--rw te!
+--rw te-tp-id te-tp-id
+--rw config
| ............
+--ro state
............
The model covers the definitions for generic TE Node attributes. The notifications:
definition of a generic connectivity matrix is shown below: +---n te-node-event
| ............
+---n te-link-event
............
+--rw te-node-attributes 4.4. Topology Identifiers
| ..........
| +--rw connectivity-matrix* [id]
| +--rw id uint32
| +--rw from-link
| | +--rw provider-id-ref? leafref
| | +--rw client-id-ref? leafref
| | +--rw topology-id-ref? leafref
| | +--rw node-ref? leafref
| | +--rw link-end-ref? leafref
| +--rw to-link
| | +--rw provider-id-ref? leafref
| | +--rw client-id-ref? leafref
| | +--rw topology-id-ref? leafref
| | +--rw node-ref? leafref
| | +--rw link-end-ref? leafref
| +--rw is-allowed? Boolean
4.6. TED Information Sources The TE-Topology is uniquely identified by a key that has 3
constituents - te-topology-id, provider-id and client-id. The
combination of provider-id and te-topology-id uniquely identifies a
native TE Topology on a given provider. The client-id is used only
when Customized TE Topologies come into play; a value of "0" is used
as the client-id for native TE Topologies.
The model allows each TE topological element to have multiple TE augment /nw:network:
information sources (OSPF-TE, ISIS-TE, BGP-LS, User-Configured, +--rw te!
System-Processed, Other). Each information source is associated with +--rw provider-id te-global-id
a credibility preference to indicate precedence. In scenarios where +--rw client-id te-global-id
a customized TE Topology is merged into a Client's native TE +--rw te-topology-id te-topology-id
Topology, the merged topological elements would point to the
corresponding customized TE Topology as its information source.
+--ro te-topologies-state 4.5. Generic TE Link Attributes
+--ro topology* [provider-id client-id te-topology-id]
| ..........
+--ro node* [te-node-id]
| ..........
| +--ro te-node-state
| +--ro information-source? enumeration
| +--ro information-source-state
| +--ro credibility-preference? uint16
| +--ro topology
| | +--ro provider-id-ref? leafref
| | +--ro client-id-ref? leafref
| | +--ro topology-id-ref? leafref
| +--ro routing-instance? string
+--ro te-topologies-state The model covers the definitions for generic TE Link attributes -
+--ro topology* [provider-id client-id te-topology-id] bandwidth, admin groups, SRLGs, switching capabilities, TE metric
| .......... extensions etc.
+--ro link* [source-te-node-id source-te-link-id dest-te-
node-id dest-te-link-id]
| ..........
| +--ro te-link-state
| +--ro information-source? enumeration
| +--ro information-source-state
| | +--ro credibility-preference? uint16
| | +--ro topology
| | | +--ro provider-id-ref? leafref
| | | +--ro client-id-ref? leafref
| | | +--ro topology-id-ref? leafref
| | +--ro routing-instance? string
| +--ro alt-information-sources* [information-source]
| +--ro information-source
enumeration
| +--ro information-source-state
| | +--ro credibility-preference? uint16
| | +--ro topology
| | | +--ro provider-id-ref? leafref
| | | +--ro client-id-ref? leafref
| | | +--ro topology-id-ref? leafref
| | +--ro routing-instance? string
| | ..........
4.7. Overlay/Underlay Relationship +--rw te-link-attributes
.....................
+--rw admin-status? te-admin-status
+--rw performance-metric-throttle {te-performance-metric}?
| .....................
+--rw link-index? uint64
+--rw administrative-group? te-types:admin-groups
+--rw max-link-bandwidth? decimal64
+--rw max-resv-link-bandwidth? decimal64
+--rw unreserved-bandwidth* [priority]
| .....................
+--rw te-default-metric? uint32
+--rw performance-metric {te-performance-metric}?
| .....................
+--rw link-protection-type? enumeration
+--rw interface-switching-capability* [switching-capability]
| .....................
+--rw te-srlgs
.....................
The model captures overlay and underlay relationship for TE 4.6. Generic TE Node Attributes
nodes/links. For example - in networks where multiple TE Topologies
are built hierarchically, this model allows the user to start from a
specific topological element in the top most topology and traverse
all the way down to the supporting topological elements in the
bottom most topology.
This relationship is captured via the "underlay-topology" field for The model covers the definitions for generic TE Node attributes. The
the node and via the "underlay" field for the link. The use of these definition of a generic connectivity matrix is shown below:
fields is optional and this functionality is tagged as a "feature"
("te-topology-hierarchy").
+--rw node* [te-node-id] +--rw te-node-attributes
| .......... ...........
| +--rw te-node-attributes +--rw connectivity-matrix* [id]
| | .......... | +--rw id uint32
| | +--rw underlay-topology {te-topology-hierarchy}? | +--rw from
| | | +--rw provider-id-ref? leafref | | +--rw tp-ref? leafref
| | | +--rw client-id-ref? leafref | | +--rw node-ref? leafref
| | | +--rw topology-id-ref? leafref | | +--rw network-ref? leafref
| +--rw to
| | +--rw tp-ref? leafref
| | +--rw node-ref? leafref
| | +--rw network-ref? leafref
| +--rw is-allowed? boolean
+--rw link* [source-te-node-id source-te-link-id dest-te-node-id 4.7. TED Information Sources
dest-te-link-id]
| ..........
| +--rw te-link-attributes
| | .......
| | +--rw underlay! {te-topology-hierarchy}?
| | | +--rw underlay-primary-path
| | | | +--rw provider-id-ref? leafref
| | | | +--rw client-id-ref? leafref
| | | | +--rw topology-id-ref? leafref
| | | | +--rw path-element* [path-element-id]
| | | | ..........
| | | +--rw underlay-backup-path* [index]
| | | | +--rw index uint32
| | | | +--rw provider-id-ref? leafref
| | | | +--rw client-id-ref? leafref
| | | | +--rw topology-id-ref? leafref
| | | | +--rw path-element* [path-element-id]
| | | | ..........
| | | +--rw underlay-protection-type? uint16
| | | +--rw underlay-trail-src
| | | ..........
| | | +--rw underlay-trail-des
| | | ..........
4.8. Scheduling Parameters The model allows each TE topological element to have multiple TE
information sources (OSPF-TE, ISIS-TE, BGP-LS, User-Configured,
System-Processed, Other). Each information source is associated with
a credibility preference to indicate precedence. In scenarios where
a customized TE Topology is merged into a Client's native TE
Topology, the merged topological elements would point to the
corresponding customized TE Topology as its information source.
The model allows time scheduling parameters to be specified for each augment /nw:network/nw:node:
topological element or for the topology as a whole. These parameters +--rw te!
allow the provider to present different topological views to the ...........
client at different time slots. The use of "scheduling parameters" +--ro state
is optional and this functionality is tagged as a "feature" ........
("configuration-schedule"). [Editor's Note: The notion of +--ro information-source-state
"scheduling parameters" has wider applicability. The expectation is +--ro credibility-preference? uint16
that this will eventually be discussed in a separate document.] +--ro topology
| +--ro provider-id-ref? leafref
| +--ro client-id-ref? leafref
| +--ro te-topology-id-ref? leafref
| +--ro network-id-ref? leafref
+--ro routing-instance? string
+--rw schedules* [schedule-id] {configuration-schedule}? augment /nw:network/nt:link:
| +--rw schedule-id uint32 +--rw te!
| +--rw start? yang:date-and-time ...........
| +--rw schedule-duration? string +--ro state
| +--rw repeat-interval? string .........
+--ro information-source? enumeration
+--ro information-source-state
| +--ro credibility-preference? uint16
| +--ro topology
| | +--ro provider-id-ref? leafref
| | +--ro client-id-ref? leafref
| | +--ro te-topology-id-ref? leafref
| | +--ro network-id-ref? leafref
| +--ro routing-instance? string
+--ro alt-information-sources* [information-source]
| ............
4.9. Templates 4.8. Overlay/Underlay Relationship
The data model provides the users with the ability to define The model captures overlay and underlay relationship for TE
templates and apply them to link and node configurations. The use of nodes/links. For example - in networks where multiple TE Topologies
"template" configuration is optional and this functionality is are built hierarchically, this model allows the user to start from a
tagged as a "feature" ("template"). specific topological element in the top most topology and traverse
all the way down to the supporting topological elements in the
bottom most topology.
+--rw topology* [provider-id client-id te-topology-id] This relationship is captured via the "underlay-topology" field for
| ........... the node and via the "underlay" field for the link. The use of these
| +--rw node* [te-node-id] fields is optional and this functionality is tagged as a "feature"
| | +--rw te-node-template? leafref {template}? ("te-topology-hierarchy").
| | ..........
| +--rw link* [source-te-node-id source-te-link-id dest-te-node-
id dest-te-link-id]
| +--rw te-link-template? leafref {template}?
| ..........
| augment /nw:network/nw:node:
+--rw node-template* [name] {template}? +--rw te!
| +--rw name te-template-name +--rw te-node-id te-node-id
| +--rw priority? uint16 +--rw config
| +--rw reference-change-policy? enumeration | +--rw te-node-template* leafref {template}?
| +--rw te-node-template* leafref | +--rw te-node-attributes
| +--rw te-node-attributes | ....................
| .......... | +--rw underlay-topology {te-topology-hierarchy}?
+--rw link-template* [name] {template}? | +--rw provider-id-ref? leafref
+--rw name te-template-name | +--rw client-id-ref? leafref
+--rw priority? uint16 | +--rw te-topology-id-ref? leafref
+--rw reference-change-policy? enumeration | +--rw network-id-ref? leafref
+--rw te-link-template* leafref
+--rw te-link-attributes
..........
A template can be constructed using multiple other templates. When augment /nw:network/nt:link:
two or more templates specify values for the same configuration +--rw te!
field, the value from the template with the highest priority is +--rw config
used. The reference-change-policy specifies the action that needs to | .........
be taken when the template changes on a configuration node that has | +--rw te-link-attributes
a reference to this template. The choices of action include taking | ....................
no action, rejecting the change to the template and applying the | +--rw underlay! {te-topology-hierarchy}?
change to the corresponding configuration. [Editor's Note: The | | +--rw underlay-primary-path
notion of "templates" has wider applicability. It is possible for | | | +--rw provider-id-ref? leafref
this to be discussed in a separate document.] | | | +--rw client-id-ref? leafref
| | | +--rw te-topology-id-ref? leafref
| | | +--rw network-id-ref? leafref
| | | +--rw path-element* [path-element-id]
| | | ...............
| | +--rw underlay-backup-path* [index]
| | | +--rw index uint32
| | | +--rw provider-id-ref? leafref
| | | +--rw client-id-ref? leafref
| | | +--rw te-topology-id-ref? leafref
| | | +--rw network-id-ref? leafref
| | | +--rw path-element* [path-element-id]
| | | ...............
| | +--rw underlay-protection-type? uint16
| | +--rw underlay-trail-src
| | | ...........
| | | +--rw network-ref? leafref
| | +--rw underlay-trail-des
| | ...........
4.10. Notifications 4.9. Scheduling Parameters
Notifications are a key component of any topology data model. The model allows time scheduling parameters to be specified for each
topological element or for the topology as a whole. These parameters
allow the provider to present different topological views to the
client at different time slots. The use of "scheduling parameters"
is optional and this functionality is tagged as a "feature"
("configuration-schedule"). [Editor's Note: The notion of
"scheduling parameters" has wider applicability. The "schedules"
module (which is imported by the TE Topology module) is discussed
separately in Appendix A. The expectation is that this will
eventually be discussed in a separate document.]
[YANG-PUSH] defines a subscription and push mechanism for YANG 4.10. Templates
datastores. This mechanism currently allows the user to:
- Subscribe notifications on a per client basis The data model provides the users with the ability to define
- Specify subtree filters or xpath filters so that only interested templates and apply them to link and node configurations. The use of
contents will be sent. "template" configuration is optional and this functionality is
- Specify either periodic or on-demand notifications. tagged as a "feature" ("template").
The authors would like to recommend the use of this mechanism for +--rw topology* [provider-id client-id te-topology-id]
the TE-Topology notifications. They would also like to suggest the | ...........
following extensions to [YANG-PUSH] | +--rw node* [te-node-id]
| | +--rw te-node-template? leafref {template}?
| | ..........
| +--rw link* [source-te-node-id source-te-link-id dest-te-node-
id dest-te-link-id]
| +--rw te-link-template? leafref {template}?
| ..........
|
+--rw node-template* [name] {template}?
| +--rw name te-template-name
| +--rw priority? uint16
| +--rw reference-change-policy? enumeration
| +--rw te-node-template* leafref
| +--rw te-node-attributes
| ..........
+--rw link-template* [name] {template}?
+--rw name te-template-name
+--rw priority? uint16
+--rw reference-change-policy? enumeration
+--rw te-link-template* leafref
+--rw te-link-attributes
..........
- Specify specific entities that will trigger the push A template can be constructed using multiple other templates. When
notifications. These entities can be specified by xpath, like the two or more templates specify values for the same configuration
way a filter is specified. field, the value from the template with the highest priority is
used. The reference-change-policy specifies the action that needs to
be taken when the template changes on a configuration node that has
a reference to this template. The choices of action include taking
no action, rejecting the change to the template and applying the
change to the corresponding configuration. [Editor's Note: The
notion of "templates" has wider applicability. It is possible for
this to be discussed in a separate document.]
- Specify or limit the triggering event type, e.g. "add", "delete", 4.11. Notifications
"modify", or "all". The system sends the push notifications only
when such events happen on the triggering entities.
- Have an option to request either "incremental" or "full" Notifications are a key component of any topology data model.
notifications for an entity. For "incremental", the notification
will contain only the changed attributes.
4.11. Open Items [YANG-PUSH] defines a subscription and push mechanism for YANG
datastores. This mechanism currently allows the user to:
- Augmenting [YANG-NET-TOPO]: The generic network topology building - Subscribe notifications on a per client basis
blocks are discussed in [YANG-NET-TOPO]. This version of the - Specify subtree filters or xpath filters so that only interested
document does not use any of those constructs. The next revision contents will be sent.
of this document should augment these constructs. - Specify either periodic or on-demand notifications.
- Coordinating changes to [YANG-PUSH]: The changes to [YANG-PUSH] The authors would like to recommend the use of this mechanism for
discussed in Section 4.10 will need to be coordinated with the the TE-Topology notifications. They would also like to suggest the
authors of that draft. following extensions to [YANG-PUSH]
5. Tree Structure - Specify specific entities that will trigger the push
notifications. These entities can be specified by xpath, like the
way a filter is specified.
module: ietf-te-topology - Specify or limit the triggering event type, e.g. "add", "delete",
+--rw te-topologies "modify", or "all". The system sends the push notifications only
| +--rw topology* [provider-id client-id te-topology-id] when such events happen on the triggering entities.
| | +--rw provider-id te-global-id
| | +--rw client-id te-global-id
| | +--rw te-topology-id te-topology-id
| | +--rw schedules* [schedule-id] {configuration-schedule}?
| | | +--rw schedule-id uint32
| | | +--rw start? yang:date-and-time
| | | +--rw schedule-duration? string
| | | +--rw repeat-interval? string
| | +--rw topology-types
| | | +--rw te-topology!
| | +--rw node* [te-node-id]
| | | +--rw te-node-id te-node-id
| | | +--rw te-node-template? leafref {template}?
| | | +--rw te-node-attributes
| | | | +--rw schedules* [schedule-id] {configuration-
schedule}?
| | | | | +--rw schedule-id uint32
| | | | | +--rw start? yang:date-and-time
| | | | | +--rw schedule-duration? string
| | | | | +--rw repeat-interval? string
| | | | +--rw name? inet:domain-name
| | | | +--rw signaling-address* inet:ip-address
| | | | +--rw flag* flag-type
| | | | +--rw is-abstract? boolean
| | | | +--rw underlay-topology {te-topology-hierarchy}?
| | | | | +--rw provider-id-ref? leafref
| | | | | +--rw client-id-ref? leafref
| | | | | +--rw topology-id-ref? leafref
| | | | +--rw connectivity-matrix* [id]
| | | | +--rw id uint32
| | | | +--rw from-link
| | | | | +--rw provider-id-ref? leafref
| | | | | +--rw client-id-ref? leafref
| | | | | +--rw topology-id-ref? leafref
| | | | | +--rw node-ref? leafref
| | | | | +--rw link-end-ref? leafref
| | | | +--rw to-link
| | | | | +--rw provider-id-ref? leafref
| | | | | +--rw client-id-ref? leafref
| | | | | +--rw topology-id-ref? leafref
| | | | | +--rw node-ref? leafref
| | | | | +--rw link-end-ref? leafref
| | | | +--rw is-allowed? boolean
| | | +--rw te-link* [te-link-id]
| | | +--rw te-link-id te-link-id
| | | +--rw (stack-level)?
| | | +--:(bundle)
| | | | +--rw bundled-links
| | | | +--rw bundled-link* [sequence]
| | | | +--rw sequence uint32
| | | | +--rw te-link-ref? leafref
| | | +--:(component)
| | | +--rw component-links
| | | +--rw component-link* [sequence]
| | | +--rw sequence uint32
| | | +--rw component-link-ref? leafref
| | +--rw link* [source-te-node-id source-te-link-id dest-te-
node-id dest-te-link-id]
| | +--rw source-te-node-id leafref
| | +--rw source-te-link-id leafref
| | +--rw dest-te-node-id leafref
| | +--rw dest-te-link-id leafref
| | +--rw te-link-template? leafref {template}?
| | +--rw te-link-attributes
| | +--rw schedules* [schedule-id] {configuration-
schedule}?
| | | +--rw schedule-id uint32
| | | +--rw start? yang:date-and-time
| | | +--rw schedule-duration? string
| | | +--rw repeat-interval? string
| | +--rw name? string
| | +--rw flag* flag-type
| | +--rw is-abstract? boolean
| | +--rw underlay! {te-topology-hierarchy}?
| | | +--rw underlay-primary-path
| | | | +--rw provider-id-ref? leafref
| | | | +--rw client-id-ref? leafref
| | | | +--rw topology-id-ref? leafref
| | | | +--rw path-element* [path-element-id]
| | | | +--rw path-element-id uint32
| | | | +--rw (type)?
| | | | +--:(ipv4-address)
| | | | | +--rw v4-address? inet:ipv4-
address
| | | | | +--rw v4-prefix-length? uint8
| | | | | +--rw v4-loose? boolean
| | | | +--:(ipv6-address)
| | | | | +--rw v6-address? inet:ipv6-
address
| | | | | +--rw v6-prefix-length? uint8
| | | | | +--rw v6-loose? boolean
| | | | +--:(as-number)
| | | | | +--rw as-number? uint16
| | | | +--:(unnumbered-link)
| | | | | +--rw router-id? inet:ip-
address
| | | | | +--rw interface-id? uint32
| | | | +--:(label)
| | | | +--rw value? uint32
| | | +--rw underlay-backup-path* [index]
| | | | +--rw index uint32
| | | | +--rw provider-id-ref? leafref
| | | | +--rw client-id-ref? leafref
| | | | +--rw topology-id-ref? leafref
| | | | +--rw path-element* [path-element-id]
| | | | +--rw path-element-id uint32
| | | | +--rw (type)?
| | | | +--:(ipv4-address)
| | | | | +--rw v4-address? inet:ipv4-
address
| | | | | +--rw v4-prefix-length? uint8
| | | | | +--rw v4-loose? boolean
| | | | +--:(ipv6-address)
| | | | | +--rw v6-address? inet:ipv6-
address
| | | | | +--rw v6-prefix-length? uint8
| | | | | +--rw v6-loose? boolean
| | | | +--:(as-number)
| | | | | +--rw as-number? uint16
| | | | +--:(unnumbered-link)
| | | | | +--rw router-id? inet:ip-
address
| | | | | +--rw interface-id? uint32
| | | | +--:(label)
| | | | +--rw value? uint32
| | | +--rw underlay-protection-type? uint16
| | | +--rw underlay-trail-src
| | | | +--rw provider-id-ref? leafref
| | | | +--rw client-id-ref? leafref
| | | | +--rw topology-id-ref? leafref
| | | | +--rw node-ref? leafref
| | | | +--rw link-end-ref? leafref
| | | +--rw underlay-trail-des
| | | +--rw provider-id-ref? leafref
| | | +--rw client-id-ref? leafref
| | | +--rw topology-id-ref? leafref
| | | +--rw node-ref? leafref
| | | +--rw link-end-ref? leafref
| | +--rw admin-status? enumeration
| | +--rw performance-metric-throttle {te-performance-
metric}?
| | | +--rw unidirectional-delay-offset?
uint32
| | | +--rw measure-interval?
uint32
| | | +--rw advertisement-interval?
uint32
| | | +--rw suppression-interval?
uint32
| | | +--rw threshold-out
| | | | +--rw unidirectional-delay?
uint32
| | | | +--rw unidirectional-min-delay?
uint32
| | | | +--rw unidirectional-max-delay?
uint32
| | | | +--rw unidirectional-delay-variation?
uint32
| | | | +--rw unidirectional-packet-loss?
decimal64
| | | | +--rw unidirectional-residual-bandwidth?
decimal64
| | | | +--rw unidirectional-available-bandwidth?
decimal64
| | | | +--rw unidirectional-utilized-bandwidth?
decimal64
| | | +--rw threshold-in
| | | | +--rw unidirectional-delay?
uint32
| | | | +--rw unidirectional-min-delay?
uint32
| | | | +--rw unidirectional-max-delay?
uint32
| | | | +--rw unidirectional-delay-variation?
uint32
| | | | +--rw unidirectional-packet-loss?
decimal64
| | | | +--rw unidirectional-residual-bandwidth?
decimal64
| | | | +--rw unidirectional-available-bandwidth?
decimal64
| | | | +--rw unidirectional-utilized-bandwidth?
decimal64
| | | +--rw threshold-accelerated-advertisement
| | | +--rw unidirectional-delay?
uint32
| | | +--rw unidirectional-min-delay?
uint32
| | | +--rw unidirectional-max-delay?
uint32
| | | +--rw unidirectional-delay-variation?
uint32
| | | +--rw unidirectional-packet-loss?
decimal64
| | | +--rw unidirectional-residual-bandwidth?
decimal64
| | | +--rw unidirectional-available-bandwidth?
decimal64
| | | +--rw unidirectional-utilized-bandwidth?
decimal64
| | +--rw link-index? uint64
| | +--rw administrative-group? te-
types:admin-groups
| | +--rw max-link-bandwidth? decimal64
| | +--rw max-resv-link-bandwidth? decimal64
| | +--rw unreserved-bandwidth* [priority]
| | | +--rw priority uint8
| | | +--rw bandwidth? decimal64
| | +--rw te-default-metric? uint32
| | +--rw performance-metric {te-performance-metric}?
| | | +--rw measurement
| | | | +--rw unidirectional-delay?
uint32
| | | | +--rw unidirectional-min-delay?
uint32
| | | | +--rw unidirectional-max-delay?
uint32
| | | | +--rw unidirectional-delay-variation?
uint32
| | | | +--rw unidirectional-packet-loss?
decimal64
| | | | +--rw unidirectional-residual-bandwidth?
decimal64
| | | | +--rw unidirectional-available-bandwidth?
decimal64
| | | | +--rw unidirectional-utilized-bandwidth?
decimal64
| | | +--rw normality
| | | +--rw unidirectional-delay?
performance-metric-normality
| | | +--rw unidirectional-min-delay?
performance-metric-normality
| | | +--rw unidirectional-max-delay?
performance-metric-normality
| | | +--rw unidirectional-delay-variation?
performance-metric-normality
| | | +--rw unidirectional-packet-loss?
performance-metric-normality
| | | +--rw unidirectional-residual-bandwidth?
performance-metric-normality
| | | +--rw unidirectional-available-bandwidth?
performance-metric-normality
| | | +--rw unidirectional-utilized-bandwidth?
performance-metric-normality
| | +--rw link-protection-type? enumeration
| | +--rw interface-switching-capabilities* [switching-
capability]
| | | +--rw switching-capability
identityref
| | | +--rw encoding?
identityref
| | | +--rw max-lsp-bandwidth* [priority]
| | | | +--rw priority uint8
| | | | +--rw bandwidth? decimal64
| | | +--rw packet-switch-capable
| | | | +--rw minimum-lsp-bandwidth? decimal64
| | | | +--rw interface-mtu? uint16
| | | +--rw time-division-multiplex-capable
| | | +--rw minimum-lsp-bandwidth? decimal64
| | | +--rw indication? enumeration
| | +--rw te-srlgs
| | +--rw values* te-types:srlg
| +--rw node-template* [name] {template}?
| | +--rw name te-template-name
| | +--rw priority? uint16
| | +--rw reference-change-policy? enumeration
| | +--rw te-node-template* leafref
| | +--rw te-node-attributes
| | | +--rw schedules* [schedule-id] {configuration-schedule}?
| | | | +--rw schedule-id uint32
| | | | +--rw start? yang:date-and-time
| | | | +--rw schedule-duration? string
| | | | +--rw repeat-interval? string
| | | +--rw name? inet:domain-name
| | | +--rw signaling-address* inet:ip-address
| | | +--rw flag* flag-type
| | | +--rw is-abstract? boolean
| | | +--rw underlay-topology {te-topology-hierarchy}?
| | | | +--rw provider-id-ref? leafref
| | | | +--rw client-id-ref? leafref
| | | | +--rw topology-id-ref? leafref
| | | +--rw connectivity-matrix* [id]
| | | +--rw id uint32
| | | +--rw from-link
| | | | +--rw provider-id-ref? leafref
| | | | +--rw client-id-ref? leafref
| | | | +--rw topology-id-ref? leafref
| | | | +--rw node-ref? leafref
| | | | +--rw link-end-ref? leafref
| | | +--rw to-link
| | | | +--rw provider-id-ref? leafref
| | | | +--rw client-id-ref? leafref
| | | | +--rw topology-id-ref? leafref
| | | | +--rw node-ref? leafref
| | | | +--rw link-end-ref? leafref
| | | +--rw is-allowed? boolean
| | +--rw te-link* [te-link-id]
| | +--rw te-link-id te-link-id
| | +--rw (stack-level)?
| | +--:(bundle)
| | | +--rw bundled-links
| | | +--rw bundled-link* [sequence]
| | | +--rw sequence uint32
| | | +--rw te-link-ref? leafref
| | +--:(component)
| | +--rw component-links
| | +--rw component-link* [sequence]
| | +--rw sequence uint32
| | +--rw component-link-ref? leafref
| +--rw link-template* [name] {template}?
| +--rw name te-template-name
| +--rw priority? uint16
| +--rw reference-change-policy? enumeration
| +--rw te-link-template* leafref
| +--rw te-link-attributes
| +--rw schedules* [schedule-id] {configuration-schedule}?
| | +--rw schedule-id uint32
| | +--rw start? yang:date-and-time
| | +--rw schedule-duration? string
| | +--rw repeat-interval? string
| +--rw name? string
| +--rw flag* flag-type
| +--rw is-abstract? boolean
| +--rw underlay! {te-topology-hierarchy}?
| | +--rw underlay-primary-path
| | | +--rw provider-id-ref? leafref
| | | +--rw client-id-ref? leafref
| | | +--rw topology-id-ref? leafref
| | | +--rw path-element* [path-element-id]
| | | +--rw path-element-id uint32
| | | +--rw (type)?
| | | +--:(ipv4-address)
| | | | +--rw v4-address? inet:ipv4-
address
| | | | +--rw v4-prefix-length? uint8
| | | | +--rw v4-loose? boolean
| | | +--:(ipv6-address)
| | | | +--rw v6-address? inet:ipv6-
address
| | | | +--rw v6-prefix-length? uint8
| | | | +--rw v6-loose? boolean
| | | +--:(as-number)
| | | | +--rw as-number? uint16
| | | +--:(unnumbered-link)
| | | | +--rw router-id? inet:ip-address
| | | | +--rw interface-id? uint32
| | | +--:(label)
| | | +--rw value? uint32
| | +--rw underlay-backup-path* [index]
| | | +--rw index uint32
| | | +--rw provider-id-ref? leafref
| | | +--rw client-id-ref? leafref
| | | +--rw topology-id-ref? leafref
| | | +--rw path-element* [path-element-id]
| | | +--rw path-element-id uint32
| | | +--rw (type)?
| | | +--:(ipv4-address)
| | | | +--rw v4-address? inet:ipv4-
address
| | | | +--rw v4-prefix-length? uint8
| | | | +--rw v4-loose? boolean
| | | +--:(ipv6-address)
| | | | +--rw v6-address? inet:ipv6-
address
| | | | +--rw v6-prefix-length? uint8
| | | | +--rw v6-loose? boolean
| | | +--:(as-number)
| | | | +--rw as-number? uint16
| | | +--:(unnumbered-link)
| | | | +--rw router-id? inet:ip-address
| | | | +--rw interface-id? uint32
| | | +--:(label)
| | | +--rw value? uint32
| | +--rw underlay-protection-type? uint16
| | +--rw underlay-trail-src
| | | +--rw provider-id-ref? leafref
| | | +--rw client-id-ref? leafref
| | | +--rw topology-id-ref? leafref
| | | +--rw node-ref? leafref
| | | +--rw link-end-ref? leafref
| | +--rw underlay-trail-des
| | +--rw provider-id-ref? leafref
| | +--rw client-id-ref? leafref
| | +--rw topology-id-ref? leafref
| | +--rw node-ref? leafref
| | +--rw link-end-ref? leafref
| +--rw admin-status? enumeration
| +--rw performance-metric-throttle {te-performance-
metric}?
| | +--rw unidirectional-delay-offset? uint32
| | +--rw measure-interval? uint32
| | +--rw advertisement-interval? uint32
| | +--rw suppression-interval? uint32
| | +--rw threshold-out
| | | +--rw unidirectional-delay? uint32
| | | +--rw unidirectional-min-delay? uint32
| | | +--rw unidirectional-max-delay? uint32
| | | +--rw unidirectional-delay-variation? uint32
| | | +--rw unidirectional-packet-loss?
decimal64
| | | +--rw unidirectional-residual-bandwidth?
decimal64
| | | +--rw unidirectional-available-bandwidth?
decimal64
| | | +--rw unidirectional-utilized-bandwidth?
decimal64
| | +--rw threshold-in
| | | +--rw unidirectional-delay? uint32
| | | +--rw unidirectional-min-delay? uint32
| | | +--rw unidirectional-max-delay? uint32
| | | +--rw unidirectional-delay-variation? uint32
| | | +--rw unidirectional-packet-loss?
decimal64
| | | +--rw unidirectional-residual-bandwidth?
decimal64
| | | +--rw unidirectional-available-bandwidth?
decimal64
| | | +--rw unidirectional-utilized-bandwidth?
decimal64
| | +--rw threshold-accelerated-advertisement
| | +--rw unidirectional-delay? uint32
| | +--rw unidirectional-min-delay? uint32
| | +--rw unidirectional-max-delay? uint32
| | +--rw unidirectional-delay-variation? uint32
| | +--rw unidirectional-packet-loss?
decimal64
| | +--rw unidirectional-residual-bandwidth?
decimal64
| | +--rw unidirectional-available-bandwidth?
decimal64
| | +--rw unidirectional-utilized-bandwidth?
decimal64
| +--rw link-index? uint64
| +--rw administrative-group? te-
types:admin-groups
| +--rw max-link-bandwidth? decimal64
| +--rw max-resv-link-bandwidth? decimal64
| +--rw unreserved-bandwidth* [priority]
| | +--rw priority uint8
| | +--rw bandwidth? decimal64
| +--rw te-default-metric? uint32
| +--rw performance-metric {te-performance-metric}?
| | +--rw measurement
| | | +--rw unidirectional-delay? uint32
| | | +--rw unidirectional-min-delay? uint32
| | | +--rw unidirectional-max-delay? uint32
| | | +--rw unidirectional-delay-variation? uint32
| | | +--rw unidirectional-packet-loss?
decimal64
| | | +--rw unidirectional-residual-bandwidth?
decimal64
| | | +--rw unidirectional-available-bandwidth?
decimal64
| | | +--rw unidirectional-utilized-bandwidth?
decimal64
| | +--rw normality
| | +--rw unidirectional-delay?
performance-metric-normality
| | +--rw unidirectional-min-delay?
performance-metric-normality
| | +--rw unidirectional-max-delay?
performance-metric-normality
| | +--rw unidirectional-delay-variation?
performance-metric-normality
| | +--rw unidirectional-packet-loss?
performance-metric-normality
| | +--rw unidirectional-residual-bandwidth?
performance-metric-normality
| | +--rw unidirectional-available-bandwidth?
performance-metric-normality
| | +--rw unidirectional-utilized-bandwidth?
performance-metric-normality
| +--rw link-protection-type? enumeration
| +--rw interface-switching-capabilities* [switching-
capability]
| | +--rw switching-capability identityref
| | +--rw encoding? identityref
| | +--rw max-lsp-bandwidth* [priority]
| | | +--rw priority uint8
| | | +--rw bandwidth? decimal64
| | +--rw packet-switch-capable
| | | +--rw minimum-lsp-bandwidth? decimal64
| | | +--rw interface-mtu? uint16
| | +--rw time-division-multiplex-capable
| | +--rw minimum-lsp-bandwidth? decimal64
| | +--rw indication? enumeration
| +--rw te-srlgs
| +--rw values* te-types:srlg
+--ro te-topologies-state
+--ro topology* [provider-id client-id te-topology-id]
+--ro provider-id te-global-id
+--ro client-id te-global-id
+--ro te-topology-id te-topology-id
+--ro server-provided? boolean
+--ro topology-types
| +--ro te-topology!
+--ro node* [te-node-id]
| +--ro te-node-id te-node-id
| +--ro te-node-template? leafref {template}?
| +--ro te-node-attributes
| | +--ro schedules* [schedule-id] {configuration-
schedule}?
| | | +--ro schedule-id uint32
| | | +--ro start? yang:date-and-time
| | | +--ro schedule-duration? string
| | | +--ro repeat-interval? string
| | +--ro name? inet:domain-name
| | +--ro signaling-address* inet:ip-address
| | +--ro flag* flag-type
| | +--ro is-abstract? boolean
| | +--ro underlay-topology {te-topology-hierarchy}?
| | | +--ro provider-id-ref? leafref
| | | +--ro client-id-ref? leafref
| | | +--ro topology-id-ref? leafref
| | +--ro connectivity-matrix* [id]
| | +--ro id uint32
| | +--ro from-link
| | | +--ro provider-id-ref? leafref
| | | +--ro client-id-ref? leafref
| | | +--ro topology-id-ref? leafref
| | | +--ro node-ref? leafref
| | | +--ro link-end-ref? leafref
| | +--ro to-link
| | | +--ro provider-id-ref? leafref
| | | +--ro client-id-ref? leafref
| | | +--ro topology-id-ref? leafref
| | | +--ro node-ref? leafref
| | | +--ro link-end-ref? leafref
| | +--ro is-allowed? boolean
| +--ro te-link* [te-link-id]
| | +--ro te-link-id te-link-id
| | +--ro (stack-level)?
| | +--:(bundle)
| | | +--ro bundled-links
| | | +--ro bundled-link* [sequence]
| | | +--ro sequence uint32
| | | +--ro te-link-ref? leafref
| | +--:(component)
| | +--ro component-links
| | +--ro component-link* [sequence]
| | +--ro sequence uint32
| | +--ro component-link-ref? leafref
| +--ro te-node-state
| +--ro information-source? enumeration
| +--ro information-source-state
| +--ro credibility-preference? uint16
| +--ro topology
| | +--ro provider-id-ref? leafref
| | +--ro client-id-ref? leafref
| | +--ro topology-id-ref? leafref
| +--ro routing-instance? string
+--ro link* [source-te-node-id source-te-link-id dest-te-
node-id dest-te-link-id]
+--ro source-te-node-id leafref
+--ro source-te-link-id leafref
+--ro dest-te-node-id leafref
+--ro dest-te-link-id leafref
+--ro te-link-template? leafref {template}?
+--ro te-link-attributes
| +--ro schedules* [schedule-id] {configuration-
schedule}?
| | +--ro schedule-id uint32
| | +--ro start? yang:date-and-time
| | +--ro schedule-duration? string
| | +--ro repeat-interval? string
| +--ro name? string
| +--ro flag* flag-type
| +--ro is-abstract? boolean
| +--ro underlay! {te-topology-hierarchy}?
| | +--ro underlay-primary-path
| | | +--ro provider-id-ref? leafref
| | | +--ro client-id-ref? leafref
| | | +--ro topology-id-ref? leafref
| | | +--ro path-element* [path-element-id]
| | | +--ro path-element-id uint32
| | | +--ro (type)?
| | | +--:(ipv4-address)
| | | | +--ro v4-address? inet:ipv4-
address
| | | | +--ro v4-prefix-length? uint8
| | | | +--ro v4-loose? boolean
| | | +--:(ipv6-address)
| | | | +--ro v6-address? inet:ipv6-
address
| | | | +--ro v6-prefix-length? uint8
| | | | +--ro v6-loose? boolean
| | | +--:(as-number)
| | | | +--ro as-number? uint16
| | | +--:(unnumbered-link)
| | | | +--ro router-id? inet:ip-
address
| | | | +--ro interface-id? uint32
| | | +--:(label)
| | | +--ro value? uint32
| | +--ro underlay-backup-path* [index]
| | | +--ro index uint32
| | | +--ro provider-id-ref? leafref
| | | +--ro client-id-ref? leafref
| | | +--ro topology-id-ref? leafref
| | | +--ro path-element* [path-element-id]
| | | +--ro path-element-id uint32
| | | +--ro (type)?
| | | +--:(ipv4-address)
| | | | +--ro v4-address? inet:ipv4-
address
| | | | +--ro v4-prefix-length? uint8
| | | | +--ro v4-loose? boolean
| | | +--:(ipv6-address)
| | | | +--ro v6-address? inet:ipv6-
address
| | | | +--ro v6-prefix-length? uint8
| | | | +--ro v6-loose? boolean
| | | +--:(as-number)
| | | | +--ro as-number? uint16
| | | +--:(unnumbered-link)
| | | | +--ro router-id? inet:ip-
address
| | | | +--ro interface-id? uint32
| | | +--:(label)
| | | +--ro value? uint32
| | +--ro underlay-protection-type? uint16
| | +--ro underlay-trail-src
| | | +--ro provider-id-ref? leafref
| | | +--ro client-id-ref? leafref
| | | +--ro topology-id-ref? leafref
| | | +--ro node-ref? leafref
| | | +--ro link-end-ref? leafref
| | +--ro underlay-trail-des
| | | +--ro provider-id-ref? leafref
| | | +--ro client-id-ref? leafref
| | | +--ro topology-id-ref? leafref
| | | +--ro node-ref? leafref
| | | +--ro link-end-ref? leafref
| | +--ro dynamic? boolean
| | +--ro committed? boolean
| +--ro admin-status? enumeration
| +--ro performance-metric-throttle {te-performance-
metric}?
| | +--ro unidirectional-delay-offset?
uint32
| | +--ro measure-interval?
uint32
| | +--ro advertisement-interval?
uint32
| | +--ro suppression-interval?
uint32
| | +--ro threshold-out
| | | +--ro unidirectional-delay?
uint32
| | | +--ro unidirectional-min-delay?
uint32
| | | +--ro unidirectional-max-delay?
uint32
| | | +--ro unidirectional-delay-variation?
uint32
| | | +--ro unidirectional-packet-loss?
decimal64
| | | +--ro unidirectional-residual-bandwidth?
decimal64
| | | +--ro unidirectional-available-bandwidth?
decimal64
| | | +--ro unidirectional-utilized-bandwidth?
decimal64
| | +--ro threshold-in
| | | +--ro unidirectional-delay?
uint32
| | | +--ro unidirectional-min-delay?
uint32
| | | +--ro unidirectional-max-delay?
uint32
| | | +--ro unidirectional-delay-variation?
uint32
| | | +--ro unidirectional-packet-loss?
decimal64
| | | +--ro unidirectional-residual-bandwidth?
decimal64
| | | +--ro unidirectional-available-bandwidth?
decimal64
| | | +--ro unidirectional-utilized-bandwidth?
decimal64
| | +--ro threshold-accelerated-advertisement
| | +--ro unidirectional-delay?
uint32
| | +--ro unidirectional-min-delay?
uint32
| | +--ro unidirectional-max-delay?
uint32
| | +--ro unidirectional-delay-variation?
uint32
| | +--ro unidirectional-packet-loss?
decimal64
| | +--ro unidirectional-residual-bandwidth?
decimal64
| | +--ro unidirectional-available-bandwidth?
decimal64
| | +--ro unidirectional-utilized-bandwidth?
decimal64
| +--ro link-index? uint64
| +--ro administrative-group? te-
types:admin-groups
| +--ro max-link-bandwidth? decimal64
| +--ro max-resv-link-bandwidth? decimal64
| +--ro unreserved-bandwidth* [priority]
| | +--ro priority uint8
| | +--ro bandwidth? decimal64
| +--ro te-default-metric? uint32
| +--ro performance-metric {te-performance-metric}?
| | +--ro measurement
| | | +--ro unidirectional-delay?
uint32
| | | +--ro unidirectional-min-delay?
uint32
| | | +--ro unidirectional-max-delay?
uint32
| | | +--ro unidirectional-delay-variation?
uint32
| | | +--ro unidirectional-packet-loss?
decimal64
| | | +--ro unidirectional-residual-bandwidth?
decimal64
| | | +--ro unidirectional-available-bandwidth?
decimal64
| | | +--ro unidirectional-utilized-bandwidth?
decimal64
| | +--ro normality
| | +--ro unidirectional-delay?
performance-metric-normality
| | +--ro unidirectional-min-delay?
performance-metric-normality
| | +--ro unidirectional-max-delay?
performance-metric-normality
| | +--ro unidirectional-delay-variation?
performance-metric-normality
| | +--ro unidirectional-packet-loss?
performance-metric-normality
| | +--ro unidirectional-residual-bandwidth?
performance-metric-normality
| | +--ro unidirectional-available-bandwidth?
performance-metric-normality
| | +--ro unidirectional-utilized-bandwidth?
performance-metric-normality
| +--ro link-protection-type? enumeration
| +--ro interface-switching-capabilities* [switching-
capability]
| | +--ro switching-capability
identityref
| | +--ro encoding?
identityref
| | +--ro max-lsp-bandwidth* [priority]
| | | +--ro priority uint8
| | | +--ro bandwidth? decimal64
| | +--ro packet-switch-capable
| | | +--ro minimum-lsp-bandwidth? decimal64
| | | +--ro interface-mtu? uint16
| | +--ro time-division-multiplex-capable
| | +--ro minimum-lsp-bandwidth? decimal64
| | +--ro indication? enumeration
| +--ro te-srlgs
| +--ro values* te-types:srlg
+--ro te-link-state
+--ro oper-status? enumeration
+--ro information-source? enumeration
+--ro information-source-state
| +--ro credibility-preference? uint16
| +--ro topology
| | +--ro provider-id-ref? leafref
| | +--ro client-id-ref? leafref
| | +--ro topology-id-ref? leafref
| +--ro routing-instance? string
+--ro alt-information-sources* [information-source]
+--ro information-source
enumeration
+--ro information-source-state
| +--ro credibility-preference? uint16
| +--ro topology
| | +--ro provider-id-ref? leafref
| | +--ro client-id-ref? leafref
| | +--ro topology-id-ref? leafref
| +--ro routing-instance? string
+--ro link-index? uint64
+--ro administrative-group? te-
types:admin-groups
+--ro max-link-bandwidth?
decimal64
+--ro max-resv-link-bandwidth?
decimal64
+--ro unreserved-bandwidth* [priority]
| +--ro priority uint8
| +--ro bandwidth? decimal64
+--ro te-default-metric? uint32
+--ro performance-metric {te-performance-metric}?
| +--ro measurement
| | +--ro unidirectional-delay?
uint32
| | +--ro unidirectional-min-delay?
uint32
| | +--ro unidirectional-max-delay?
uint32
| | +--ro unidirectional-delay-variation?
uint32
| | +--ro unidirectional-packet-loss?
decimal64
| | +--ro unidirectional-residual-bandwidth?
decimal64
| | +--ro unidirectional-available-bandwidth?
decimal64
| | +--ro unidirectional-utilized-bandwidth?
decimal64
| +--ro normality
| +--ro unidirectional-delay?
performance-metric-normality
| +--ro unidirectional-min-delay?
performance-metric-normality
| +--ro unidirectional-max-delay?
performance-metric-normality
| +--ro unidirectional-delay-variation?
performance-metric-normality
| +--ro unidirectional-packet-loss?
performance-metric-normality
| +--ro unidirectional-residual-bandwidth?
performance-metric-normality
| +--ro unidirectional-available-bandwidth?
performance-metric-normality
| +--ro unidirectional-utilized-bandwidth?
performance-metric-normality
+--ro link-protection-type?
enumeration
+--ro interface-switching-capabilities*
[switching-capability]
| +--ro switching-capability
identityref
| +--ro encoding?
identityref
| +--ro max-lsp-bandwidth* [priority]
| | +--ro priority uint8
| | +--ro bandwidth? decimal64
| +--ro packet-switch-capable
| | +--ro minimum-lsp-bandwidth? decimal64
| | +--ro interface-mtu? uint16
| +--ro time-division-multiplex-capable
| +--ro minimum-lsp-bandwidth? decimal64
| +--ro indication? enumeration
+--ro te-srlgs
+--ro values* te-types:srlg
notifications:
+---n te-node-event
| +--ro event-type? te-topology-event-type
| +--ro provider-id-ref? leafref
| +--ro client-id-ref? leafref
| +--ro topology-id-ref? leafref
| +--ro node-ref? leafref
| +--ro te-topology!
| +--ro te-node-attributes
| | +--ro schedules* [schedule-id] {configuration-schedule}?
| | | +--ro schedule-id uint32
| | | +--ro start? yang:date-and-time
| | | +--ro schedule-duration? string
| | | +--ro repeat-interval? string
| | +--ro name? inet:domain-name
| | +--ro signaling-address* inet:ip-address
| | +--ro flag* flag-type
| | +--ro is-abstract? boolean
| | +--ro underlay-topology {te-topology-hierarchy}?
| | | +--ro provider-id-ref? leafref
| | | +--ro client-id-ref? leafref
| | | +--ro topology-id-ref? leafref
| | +--ro connectivity-matrix* [id]
| | +--ro id uint32
| | +--ro from-link
| | | +--ro provider-id-ref? leafref
| | | +--ro client-id-ref? leafref
| | | +--ro topology-id-ref? leafref
| | | +--ro node-ref? leafref
| | | +--ro link-end-ref? leafref
| | +--ro to-link
| | | +--ro provider-id-ref? leafref
| | | +--ro client-id-ref? leafref
| | | +--ro topology-id-ref? leafref
| | | +--ro node-ref? leafref
| | | +--ro link-end-ref? leafref
| | +--ro is-allowed? boolean
| +--ro te-link* [te-link-id]
| | +--ro te-link-id te-link-id
| | +--ro (stack-level)?
| | +--:(bundle)
| | | +--ro bundled-links
| | | +--ro bundled-link* [sequence]
| | | +--ro sequence uint32
| | | +--ro te-link-ref? leafref
| | +--:(component)
| | +--ro component-links
| | +--ro component-link* [sequence]
| | +--ro sequence uint32
| | +--ro component-link-ref? leafref
| +--ro te-node-state
| +--ro information-source? enumeration
| +--ro information-source-state
| +--ro credibility-preference? uint16
| +--ro topology
| | +--ro provider-id-ref? leafref
| | +--ro client-id-ref? leafref
| | +--ro topology-id-ref? leafref
| +--ro routing-instance? string
+---n te-link-event
+--ro event-type? te-topology-event-type
+--ro provider-id-ref? leafref
+--ro client-id-ref? leafref
+--ro topology-id-ref? leafref
+--ro source-te-node-id-ref? leafref
+--ro source-te-link-id-ref? leafref
+--ro dest-te-node-id-ref? leafref
+--ro dest-te-link-id-ref? leafref
+--ro te-topology!
+--ro te-link-attributes
| +--ro schedules* [schedule-id] {configuration-schedule}?
| | +--ro schedule-id uint32
| | +--ro start? yang:date-and-time
| | +--ro schedule-duration? string
| | +--ro repeat-interval? string
| +--ro name? string
| +--ro flag* flag-type
| +--ro is-abstract? boolean
| +--ro underlay! {te-topology-hierarchy}?
| | +--ro underlay-primary-path
| | | +--ro provider-id-ref? leafref
| | | +--ro client-id-ref? leafref
| | | +--ro topology-id-ref? leafref
| | | +--ro path-element* [path-element-id]
| | | +--ro path-element-id uint32
| | | +--ro (type)?
| | | +--:(ipv4-address)
| | | | +--ro v4-address? inet:ipv4-address
| | | | +--ro v4-prefix-length? uint8
| | | | +--ro v4-loose? boolean
| | | +--:(ipv6-address)
| | | | +--ro v6-address? inet:ipv6-address
| | | | +--ro v6-prefix-length? uint8
| | | | +--ro v6-loose? boolean
| | | +--:(as-number)
| | | | +--ro as-number? uint16
| | | +--:(unnumbered-link)
| | | | +--ro router-id? inet:ip-address
| | | | +--ro interface-id? uint32
| | | +--:(label)
| | | +--ro value? uint32
| | +--ro underlay-backup-path* [index]
| | | +--ro index uint32
| | | +--ro provider-id-ref? leafref
| | | +--ro client-id-ref? leafref
| | | +--ro topology-id-ref? leafref
| | | +--ro path-element* [path-element-id]
| | | +--ro path-element-id uint32
| | | +--ro (type)?
| | | +--:(ipv4-address)
| | | | +--ro v4-address? inet:ipv4-address
| | | | +--ro v4-prefix-length? uint8
| | | | +--ro v4-loose? boolean
| | | +--:(ipv6-address)
| | | | +--ro v6-address? inet:ipv6-address
| | | | +--ro v6-prefix-length? uint8
| | | | +--ro v6-loose? boolean
| | | +--:(as-number)
| | | | +--ro as-number? uint16
| | | +--:(unnumbered-link)
| | | | +--ro router-id? inet:ip-address
| | | | +--ro interface-id? uint32
| | | +--:(label)
| | | +--ro value? uint32
| | +--ro underlay-protection-type? uint16
| | +--ro underlay-trail-src
| | | +--ro provider-id-ref? leafref
| | | +--ro client-id-ref? leafref
| | | +--ro topology-id-ref? leafref
| | | +--ro node-ref? leafref
| | | +--ro link-end-ref? leafref
| | +--ro underlay-trail-des
| | | +--ro provider-id-ref? leafref
| | | +--ro client-id-ref? leafref
| | | +--ro topology-id-ref? leafref
| | | +--ro node-ref? leafref
| | | +--ro link-end-ref? leafref
| | +--ro dynamic? boolean
| | +--ro committed? boolean
| +--ro admin-status? enumeration
| +--ro performance-metric-throttle {te-performance-metric}?
| | +--ro unidirectional-delay-offset? uint32
| | +--ro measure-interval? uint32
| | +--ro advertisement-interval? uint32
| | +--ro suppression-interval? uint32
| | +--ro threshold-out
| | | +--ro unidirectional-delay? uint32
| | | +--ro unidirectional-min-delay? uint32
| | | +--ro unidirectional-max-delay? uint32
| | | +--ro unidirectional-delay-variation? uint32
| | | +--ro unidirectional-packet-loss? decimal64
| | | +--ro unidirectional-residual-bandwidth? decimal64
| | | +--ro unidirectional-available-bandwidth? decimal64
| | | +--ro unidirectional-utilized-bandwidth? decimal64
| | +--ro threshold-in
| | | +--ro unidirectional-delay? uint32
| | | +--ro unidirectional-min-delay? uint32
| | | +--ro unidirectional-max-delay? uint32
| | | +--ro unidirectional-delay-variation? uint32
| | | +--ro unidirectional-packet-loss? decimal64
| | | +--ro unidirectional-residual-bandwidth? decimal64
| | | +--ro unidirectional-available-bandwidth? decimal64
| | | +--ro unidirectional-utilized-bandwidth? decimal64
| | +--ro threshold-accelerated-advertisement
| | +--ro unidirectional-delay? uint32
| | +--ro unidirectional-min-delay? uint32
| | +--ro unidirectional-max-delay? uint32
| | +--ro unidirectional-delay-variation? uint32
| | +--ro unidirectional-packet-loss? decimal64
| | +--ro unidirectional-residual-bandwidth? decimal64
| | +--ro unidirectional-available-bandwidth? decimal64
| | +--ro unidirectional-utilized-bandwidth? decimal64
| +--ro link-index? uint64
| +--ro administrative-group? te-types:admin-
groups
| +--ro max-link-bandwidth? decimal64
| +--ro max-resv-link-bandwidth? decimal64
| +--ro unreserved-bandwidth* [priority]
| | +--ro priority uint8
| | +--ro bandwidth? decimal64
| +--ro te-default-metric? uint32
| +--ro performance-metric {te-performance-metric}?
| | +--ro measurement
| | | +--ro unidirectional-delay? uint32
| | | +--ro unidirectional-min-delay? uint32
| | | +--ro unidirectional-max-delay? uint32
| | | +--ro unidirectional-delay-variation? uint32
| | | +--ro unidirectional-packet-loss? decimal64
| | | +--ro unidirectional-residual-bandwidth? decimal64
| | | +--ro unidirectional-available-bandwidth? decimal64
| | | +--ro unidirectional-utilized-bandwidth? decimal64
| | +--ro normality
| | +--ro unidirectional-delay?
performance-metric-normality
| | +--ro unidirectional-min-delay?
performance-metric-normality
| | +--ro unidirectional-max-delay?
performance-metric-normality
| | +--ro unidirectional-delay-variation?
performance-metric-normality
| | +--ro unidirectional-packet-loss?
performance-metric-normality
| | +--ro unidirectional-residual-bandwidth?
performance-metric-normality
| | +--ro unidirectional-available-bandwidth?
performance-metric-normality
| | +--ro unidirectional-utilized-bandwidth?
performance-metric-normality
| +--ro link-protection-type? enumeration
| +--ro interface-switching-capabilities* [switching-
capability]
| | +--ro switching-capability identityref
| | +--ro encoding? identityref
| | +--ro max-lsp-bandwidth* [priority]
| | | +--ro priority uint8
| | | +--ro bandwidth? decimal64
| | +--ro packet-switch-capable
| | | +--ro minimum-lsp-bandwidth? decimal64
| | | +--ro interface-mtu? uint16
| | +--ro time-division-multiplex-capable
| | +--ro minimum-lsp-bandwidth? decimal64
| | +--ro indication? enumeration
| +--ro te-srlgs
| +--ro values* te-types:srlg
+--ro te-link-state
+--ro oper-status? enumeration
+--ro information-source? enumeration
+--ro information-source-state
| +--ro credibility-preference? uint16
| +--ro topology
| | +--ro provider-id-ref? leafref
| | +--ro client-id-ref? leafref
| | +--ro topology-id-ref? leafref
| +--ro routing-instance? string
+--ro alt-information-sources* [information-source]
+--ro information-source enumeration
+--ro information-source-state
| +--ro credibility-preference? uint16
| +--ro topology
| | +--ro provider-id-ref? leafref
| | +--ro client-id-ref? leafref
| | +--ro topology-id-ref? leafref
| +--ro routing-instance? string
+--ro link-index? uint64
+--ro administrative-group? te-
types:admin-groups
+--ro max-link-bandwidth? decimal64
+--ro max-resv-link-bandwidth? decimal64
+--ro unreserved-bandwidth* [priority]
| +--ro priority uint8
| +--ro bandwidth? decimal64
+--ro te-default-metric? uint32
+--ro performance-metric {te-performance-metric}?
| +--ro measurement
| | +--ro unidirectional-delay? uint32
| | +--ro unidirectional-min-delay? uint32
| | +--ro unidirectional-max-delay? uint32
| | +--ro unidirectional-delay-variation? uint32
| | +--ro unidirectional-packet-loss?
decimal64
| | +--ro unidirectional-residual-bandwidth?
decimal64
| | +--ro unidirectional-available-bandwidth?
decimal64
| | +--ro unidirectional-utilized-bandwidth?
decimal64
| +--ro normality
| +--ro unidirectional-delay?
performance-metric-normality
| +--ro unidirectional-min-delay?
performance-metric-normality
| +--ro unidirectional-max-delay?
performance-metric-normality
| +--ro unidirectional-delay-variation?
performance-metric-normality
| +--ro unidirectional-packet-loss?
performance-metric-normality
| +--ro unidirectional-residual-bandwidth?
performance-metric-normality
| +--ro unidirectional-available-bandwidth?
performance-metric-normality
| +--ro unidirectional-utilized-bandwidth?
performance-metric-normality
+--ro link-protection-type? enumeration
+--ro interface-switching-capabilities* [switching-
capability]
| +--ro switching-capability identityref
| +--ro encoding? identityref
| +--ro max-lsp-bandwidth* [priority]
| | +--ro priority uint8
| | +--ro bandwidth? decimal64
| +--ro packet-switch-capable
| | +--ro minimum-lsp-bandwidth? decimal64
| | +--ro interface-mtu? uint16
| +--ro time-division-multiplex-capable
| +--ro minimum-lsp-bandwidth? decimal64
| +--ro indication? enumeration
+--ro te-srlgs
+--ro values* te-types:srlg
6. TE Topology Yang Module - Have an option to request either "incremental" or "full"
notifications for an entity. For "incremental", the notification
will contain only the changed attributes.
<CODE BEGINS> 4.12. Open Items
module ietf-te-topology { - Coordinating changes to [YANG-PUSH]: The changes to [YANG-PUSH]
yang-version 1; discussed in Section 4.10 will need to be coordinated with the
namespace "urn:ietf:params:xml:ns:yang:ietf-te-topology"; authors of that draft.
// replace with IANA namespace when assigned
prefix "tet"; 5. Tree Structure
import ietf-yang-types { module: ietf-te-topology
prefix "yang"; augment /nw:network/nw:network-types:
} +--rw te-topology!
augment /nw:network:
+--rw te!
+--rw provider-id te-global-id
+--rw client-id te-global-id
+--rw te-topology-id te-topology-id
+--rw config
| +--rw schedules
| +--rw schedule* [schedule-id]
| +--rw schedule-id uint32
| +--rw start? yang:date-and-time
| +--rw schedule-duration? string
| +--rw repeat-interval? string
+--ro state
| +--ro schedules
| +--ro schedule* [schedule-id]
| +--ro schedule-id uint32
| +--ro start? yang:date-and-time
| +--ro schedule-duration? string
| +--ro repeat-interval? string
+--rw templates
+--rw node-template* [name] {template}?
| +--rw name te-template-name
| +--rw priority? uint16
| +--rw reference-change-policy? enumeration
| +--rw te-node-attributes
| +--rw schedules
| | +--rw schedule* [schedule-id]
| | +--rw schedule-id uint32
| | +--rw start? yang:date-and-time
| | +--rw schedule-duration? string
| | +--rw repeat-interval? string
| +--rw admin-status? te-admin-status
| +--rw connectivity-matrix* [id]
| | +--rw id uint32
| | +--rw from
| | | +--rw tp-ref? leafref
| | | +--rw node-ref? leafref
| | | +--rw network-ref? leafref
| | +--rw to
| | | +--rw tp-ref? leafref
| | | +--rw node-ref? leafref
| | | +--rw network-ref? leafref
| | +--rw is-allowed? boolean
| +--rw domain-id? uint32
| +--rw flag* te-node-flag
| +--rw is-abstract? empty
| +--rw name? inet:domain-name
| +--rw signaling-address* inet:ip-address
| +--rw underlay-topology {te-topology-hierarchy}?
| +--rw provider-id-ref? leafref
| +--rw client-id-ref? leafref
| +--rw te-topology-id-ref? leafref
| +--rw network-id-ref? leafref
+--rw link-template* [name] {template}?
+--rw name te-template-name
+--rw priority? uint16
+--rw reference-change-policy? enumeration
+--rw te-link-attributes
+--rw schedules
| +--rw schedule* [schedule-id]
| +--rw schedule-id uint32
| +--rw start? yang:date-and-time
| +--rw schedule-duration? string
| +--rw repeat-interval? string
+--rw access-type? te-link-
access-type
+--rw flag* te-link-flag
+--rw is-abstract? empty
+--rw name? string
+--rw underlay! {te-topology-hierarchy}?
| +--rw underlay-primary-path
| | +--rw provider-id-ref? leafref
| | +--rw client-id-ref? leafref
| | +--rw te-topology-id-ref? leafref
| | +--rw network-id-ref? leafref
| | +--rw path-element* [path-element-id]
| | +--rw path-element-id uint32
| | +--rw (type)?
| | +--:(ipv4-address)
| | | +--rw v4-address? inet:ipv4-
address
| | | +--rw v4-prefix-length? uint8
| | | +--rw v4-loose? boolean
| | +--:(ipv6-address)
| | | +--rw v6-address? inet:ipv6-
address
| | | +--rw v6-prefix-length? uint8
| | | +--rw v6-loose? boolean
| | +--:(as-number)
| | | +--rw as-number? uint16
| | +--:(unnumbered-link)
| | | +--rw router-id? inet:ip-
address
| | | +--rw interface-id? uint32
| | +--:(label)
| | +--rw value? uint32
| +--rw underlay-backup-path* [index]
| | +--rw index uint32
| | +--rw provider-id-ref? leafref
| | +--rw client-id-ref? leafref
| | +--rw te-topology-id-ref? leafref
| | +--rw network-id-ref? leafref
| | +--rw path-element* [path-element-id]
| | +--rw path-element-id uint32
| | +--rw (type)?
| | +--:(ipv4-address)
| | | +--rw v4-address? inet:ipv4-
address
| | | +--rw v4-prefix-length? uint8
| | | +--rw v4-loose? boolean
| | +--:(ipv6-address)
| | | +--rw v6-address? inet:ipv6-
address
| | | +--rw v6-prefix-length? uint8
| | | +--rw v6-loose? boolean
| | +--:(as-number)
| | | +--rw as-number? uint16
| | +--:(unnumbered-link)
| | | +--rw router-id? inet:ip-
address
| | | +--rw interface-id? uint32
| | +--:(label)
| | +--rw value? uint32
| +--rw underlay-protection-type? uint16
| +--rw underlay-trail-src
| | +--rw tp-ref? leafref
| | +--rw node-ref? leafref
| | +--rw network-ref? leafref
| +--rw underlay-trail-des
| +--rw tp-ref? leafref
| +--rw node-ref? leafref
| +--rw network-ref? leafref
+--rw admin-status? te-admin-
status
+--rw performance-metric-throttle {te-performance-
metric}?
| +--rw unidirectional-delay-offset?
uint32
| +--rw measure-interval?
uint32
| +--rw advertisement-interval?
uint32
| +--rw suppression-interval?
uint32
| +--rw threshold-out
| | +--rw unidirectional-delay?
uint32
| | +--rw unidirectional-min-delay?
uint32
| | +--rw unidirectional-max-delay?
uint32
| | +--rw unidirectional-delay-variation?
uint32
| | +--rw unidirectional-packet-loss?
decimal64
| | +--rw unidirectional-residual-bandwidth?
decimal64
| | +--rw unidirectional-available-bandwidth?
decimal64
| | +--rw unidirectional-utilized-bandwidth?
decimal64
| +--rw threshold-in
| | +--rw unidirectional-delay?
uint32
| | +--rw unidirectional-min-delay?
uint32
| | +--rw unidirectional-max-delay?
uint32
| | +--rw unidirectional-delay-variation?
uint32
| | +--rw unidirectional-packet-loss?
decimal64
| | +--rw unidirectional-residual-bandwidth?
decimal64
| | +--rw unidirectional-available-bandwidth?
decimal64
| | +--rw unidirectional-utilized-bandwidth?
decimal64
| +--rw threshold-accelerated-advertisement
| +--rw unidirectional-delay?
uint32
| +--rw unidirectional-min-delay?
uint32
| +--rw unidirectional-max-delay?
uint32
| +--rw unidirectional-delay-variation?
uint32
| +--rw unidirectional-packet-loss?
decimal64
| +--rw unidirectional-residual-bandwidth?
decimal64
| +--rw unidirectional-available-bandwidth?
decimal64
| +--rw unidirectional-utilized-bandwidth?
decimal64
+--rw link-index? uint64
+--rw administrative-group? te-
types:admin-groups
+--rw max-link-bandwidth? decimal64
+--rw max-resv-link-bandwidth? decimal64
+--rw unreserved-bandwidth* [priority]
| +--rw priority uint8
| +--rw bandwidth? decimal64
+--rw te-default-metric? uint32
+--rw performance-metric {te-performance-metric}?
| +--rw measurement
| | +--rw unidirectional-delay?
uint32
| | +--rw unidirectional-min-delay?
uint32
| | +--rw unidirectional-max-delay?
uint32
| | +--rw unidirectional-delay-variation?
uint32
| | +--rw unidirectional-packet-loss?
decimal64
| | +--rw unidirectional-residual-bandwidth?
decimal64
| | +--rw unidirectional-available-bandwidth?
decimal64
| | +--rw unidirectional-utilized-bandwidth?
decimal64
| +--rw normality
| +--rw unidirectional-delay?
performance-metric-normality
| +--rw unidirectional-min-delay?
performance-metric-normality
| +--rw unidirectional-max-delay?
performance-metric-normality
| +--rw unidirectional-delay-variation?
performance-metric-normality
| +--rw unidirectional-packet-loss?
performance-metric-normality
| +--rw unidirectional-residual-bandwidth?
performance-metric-normality
| +--rw unidirectional-available-bandwidth?
performance-metric-normality
| +--rw unidirectional-utilized-bandwidth?
performance-metric-normality
+--rw link-protection-type? enumeration
+--rw interface-switching-capability* [switching-
capability]
| +--rw switching-capability
identityref
| +--rw encoding?
identityref
| +--rw max-lsp-bandwidth* [priority]
| | +--rw priority uint8
| | +--rw bandwidth? decimal64
| +--rw packet-switch-capable
| | +--rw minimum-lsp-bandwidth? decimal64
| | +--rw interface-mtu? uint16
| +--rw time-division-multiplex-capable
| | +--rw minimum-lsp-bandwidth? decimal64
| | +--rw indication? enumeration
| +--rw interface-adjustment-capability* [upper-sc]
| +--rw upper-sc identityref
| +--rw upper-encoding? identityref
| +--rw max-lsp-bandwidth* [priority]
| +--rw priority uint8
| +--rw bandwidth? decimal64
+--rw te-srlgs
+--rw values* te-types:srlg
augment /nw:network/nw:node:
import ietf-inet-types { +--rw te!
prefix "inet"; +--rw te-node-id te-node-id
} +--rw config
| +--rw te-node-template* leafref {template}?
| +--rw te-node-attributes
| +--rw schedules
| | +--rw schedule* [schedule-id]
| | +--rw schedule-id uint32
| | +--rw start? yang:date-and-time
| | +--rw schedule-duration? string
| | +--rw repeat-interval? string
| +--rw admin-status? te-admin-status
| +--rw connectivity-matrix* [id]
| | +--rw id uint32
| | +--rw from
| | | +--rw tp-ref? leafref
| | | +--rw node-ref? leafref
| | | +--rw network-ref? leafref
| | +--rw to
| | | +--rw tp-ref? leafref
| | | +--rw node-ref? leafref
| | | +--rw network-ref? leafref
| | +--rw is-allowed? boolean
| +--rw domain-id? uint32
| +--rw flag* te-node-flag
| +--rw is-abstract? empty
| +--rw name? inet:domain-name
| +--rw signaling-address* inet:ip-address
| +--rw underlay-topology {te-topology-hierarchy}?
| +--rw provider-id-ref? leafref
| +--rw client-id-ref? leafref
| +--rw te-topology-id-ref? leafref
| +--rw network-id-ref? leafref
+--ro state
+--ro te-node-template* leafref {template}?
+--ro te-node-attributes
| +--ro schedules
| | +--ro schedule* [schedule-id]
| | +--ro schedule-id uint32
| | +--ro start? yang:date-and-time
| | +--ro schedule-duration? string
| | +--ro repeat-interval? string
| +--ro admin-status? te-admin-status
| +--ro connectivity-matrix* [id]
| | +--ro id uint32
| | +--ro from
| | | +--ro tp-ref? leafref
| | | +--ro node-ref? leafref
| | | +--ro network-ref? leafref
| | +--ro to
| | | +--ro tp-ref? leafref
| | | +--ro node-ref? leafref
| | | +--ro network-ref? leafref
| | +--ro is-allowed? boolean
| +--ro domain-id? uint32
| +--ro flag* te-node-flag
| +--ro is-abstract? empty
| +--ro name? inet:domain-name
| +--ro signaling-address* inet:ip-address
| +--ro underlay-topology {te-topology-hierarchy}?
| +--ro provider-id-ref? leafref
| +--ro client-id-ref? leafref
| +--ro te-topology-id-ref? leafref
| +--ro network-id-ref? leafref
+--ro oper-status? te-oper-status
+--ro is-multi-access-dr? empty
+--ro information-source? enumeration
+--ro information-source-state
+--ro credibility-preference? uint16
+--ro topology
| +--ro provider-id-ref? leafref
| +--ro client-id-ref? leafref
| +--ro te-topology-id-ref? leafref
| +--ro network-id-ref? leafref
+--ro routing-instance? string
augment /nw:network/nt:link:
+--rw te!
+--rw config
| +--rw (bundle-stack-level)?
| | +--:(bundle)
| | | +--rw bundled-links
| | | +--rw bundled-link* [sequence]
| | | +--rw sequence uint32
| | | +--rw src-tp-ref? leafref
| | | +--rw des-tp-ref? leafref
| | +--:(component)
| | +--rw component-links
| | +--rw component-link* [sequence]
| | +--rw sequence uint32
| | +--rw src-interface-ref? string
| | +--rw des-interface-ref? string
| +--rw te-link-template* leafref {template}?
| +--rw te-link-attributes
| +--rw schedules
| | +--rw schedule* [schedule-id]
| | +--rw schedule-id uint32
| | +--rw start? yang:date-and-time
| | +--rw schedule-duration? string
| | +--rw repeat-interval? string
| +--rw access-type? te-link-access-
type
| +--rw flag* te-link-flag
| +--rw is-abstract? empty
| +--rw name? string
| +--rw underlay! {te-topology-hierarchy}?
| | +--rw underlay-primary-path
| | | +--rw provider-id-ref? leafref
| | | +--rw client-id-ref? leafref
| | | +--rw te-topology-id-ref? leafref
| | | +--rw network-id-ref? leafref
| | | +--rw path-element* [path-element-id]
| | | +--rw path-element-id uint32
| | | +--rw (type)?
| | | +--:(ipv4-address)
| | | | +--rw v4-address? inet:ipv4-
address
| | | | +--rw v4-prefix-length? uint8
| | | | +--rw v4-loose? boolean
| | | +--:(ipv6-address)
| | | | +--rw v6-address? inet:ipv6-
address
| | | | +--rw v6-prefix-length? uint8
| | | | +--rw v6-loose? boolean
| | | +--:(as-number)
| | | | +--rw as-number? uint16
| | | +--:(unnumbered-link)
| | | | +--rw router-id? inet:ip-address
| | | | +--rw interface-id? uint32
| | | +--:(label)
| | | +--rw value? uint32
| | +--rw underlay-backup-path* [index]
| | | +--rw index uint32
| | | +--rw provider-id-ref? leafref
| | | +--rw client-id-ref? leafref
| | | +--rw te-topology-id-ref? leafref
| | | +--rw network-id-ref? leafref
| | | +--rw path-element* [path-element-id]
| | | +--rw path-element-id uint32
| | | +--rw (type)?
| | | +--:(ipv4-address)
| | | | +--rw v4-address? inet:ipv4-
address
| | | | +--rw v4-prefix-length? uint8
| | | | +--rw v4-loose? boolean
| | | +--:(ipv6-address)
| | | | +--rw v6-address? inet:ipv6-
address
| | | | +--rw v6-prefix-length? uint8
| | | | +--rw v6-loose? boolean
| | | +--:(as-number)
| | | | +--rw as-number? uint16
| | | +--:(unnumbered-link)
| | | | +--rw router-id? inet:ip-address
| | | | +--rw interface-id? uint32
| | | +--:(label)
| | | +--rw value? uint32
| | +--rw underlay-protection-type? uint16
| | +--rw underlay-trail-src
| | | +--rw tp-ref? leafref
| | | +--rw node-ref? leafref
| | | +--rw network-ref? leafref
| | +--rw underlay-trail-des
| | +--rw tp-ref? leafref
| | +--rw node-ref? leafref
| | +--rw network-ref? leafref
| +--rw admin-status? te-admin-status
| +--rw performance-metric-throttle {te-performance-
metric}?
| | +--rw unidirectional-delay-offset? uint32
| | +--rw measure-interval? uint32
| | +--rw advertisement-interval? uint32
| | +--rw suppression-interval? uint32
| | +--rw threshold-out
| | | +--rw unidirectional-delay? uint32
| | | +--rw unidirectional-min-delay? uint32
| | | +--rw unidirectional-max-delay? uint32
| | | +--rw unidirectional-delay-variation? uint32
| | | +--rw unidirectional-packet-loss?
decimal64
| | | +--rw unidirectional-residual-bandwidth?
decimal64
| | | +--rw unidirectional-available-bandwidth?
decimal64
| | | +--rw unidirectional-utilized-bandwidth?
decimal64
| | +--rw threshold-in
| | | +--rw unidirectional-delay? uint32
| | | +--rw unidirectional-min-delay? uint32
| | | +--rw unidirectional-max-delay? uint32
| | | +--rw unidirectional-delay-variation? uint32
| | | +--rw unidirectional-packet-loss?
decimal64
| | | +--rw unidirectional-residual-bandwidth?
decimal64
| | | +--rw unidirectional-available-bandwidth?
decimal64
| | | +--rw unidirectional-utilized-bandwidth?
decimal64
| | +--rw threshold-accelerated-advertisement
| | +--rw unidirectional-delay? uint32
| | +--rw unidirectional-min-delay? uint32
| | +--rw unidirectional-max-delay? uint32
| | +--rw unidirectional-delay-variation? uint32
| | +--rw unidirectional-packet-loss?
decimal64
| | +--rw unidirectional-residual-bandwidth?
decimal64
| | +--rw unidirectional-available-bandwidth?
decimal64
| | +--rw unidirectional-utilized-bandwidth?
decimal64
| +--rw link-index? uint64
| +--rw administrative-group? te-types:admin-
groups
| +--rw max-link-bandwidth? decimal64
| +--rw max-resv-link-bandwidth? decimal64
| +--rw unreserved-bandwidth* [priority]
| | +--rw priority uint8
| | +--rw bandwidth? decimal64
| +--rw te-default-metric? uint32
| +--rw performance-metric {te-performance-metric}?
| | +--rw measurement
| | | +--rw unidirectional-delay? uint32
| | | +--rw unidirectional-min-delay? uint32
| | | +--rw unidirectional-max-delay? uint32
| | | +--rw unidirectional-delay-variation? uint32
| | | +--rw unidirectional-packet-loss?
decimal64
| | | +--rw unidirectional-residual-bandwidth?
decimal64
| | | +--rw unidirectional-available-bandwidth?
decimal64
| | | +--rw unidirectional-utilized-bandwidth?
decimal64
| | +--rw normality
| | +--rw unidirectional-delay?
performance-metric-normality
| | +--rw unidirectional-min-delay?
performance-metric-normality
| | +--rw unidirectional-max-delay?
performance-metric-normality
| | +--rw unidirectional-delay-variation?
performance-metric-normality
| | +--rw unidirectional-packet-loss?
performance-metric-normality
| | +--rw unidirectional-residual-bandwidth?
performance-metric-normality
| | +--rw unidirectional-available-bandwidth?
performance-metric-normality
| | +--rw unidirectional-utilized-bandwidth?
performance-metric-normality
| +--rw link-protection-type? enumeration
| +--rw interface-switching-capability* [switching-
capability]
| | +--rw switching-capability identityref
| | +--rw encoding? identityref
| | +--rw max-lsp-bandwidth* [priority]
| | | +--rw priority uint8
| | | +--rw bandwidth? decimal64
| | +--rw packet-switch-capable
| | | +--rw minimum-lsp-bandwidth? decimal64
| | | +--rw interface-mtu? uint16
| | +--rw time-division-multiplex-capable
| | | +--rw minimum-lsp-bandwidth? decimal64
| | | +--rw indication? enumeration
| | +--rw interface-adjustment-capability* [upper-sc]
| | +--rw upper-sc identityref
| | +--rw upper-encoding? identityref
| | +--rw max-lsp-bandwidth* [priority]
| | +--rw priority uint8
| | +--rw bandwidth? decimal64
| +--rw te-srlgs
| +--rw values* te-types:srlg
+--ro state
+--ro (bundle-stack-level)?
| +--:(bundle)
| | +--ro bundled-links
| | +--ro bundled-link* [sequence]
| | +--ro sequence uint32
| | +--ro src-tp-ref? leafref
| | +--ro des-tp-ref? leafref
| +--:(component)
| +--ro component-links
| +--ro component-link* [sequence]
| +--ro sequence uint32
| +--ro src-interface-ref? string
| +--ro des-interface-ref? string
+--ro te-link-template* leafref {template}?
+--ro te-link-attributes
| +--ro schedules
| | +--ro schedule* [schedule-id]
| | +--ro schedule-id uint32
| | +--ro start? yang:date-and-time
| | +--ro schedule-duration? string
| | +--ro repeat-interval? string
| +--ro access-type? te-link-access-
type
| +--ro flag* te-link-flag
| +--ro is-abstract? empty
| +--ro name? string
| +--ro underlay! {te-topology-hierarchy}?
| | +--ro underlay-primary-path
| | | +--ro provider-id-ref? leafref
| | | +--ro client-id-ref? leafref
| | | +--ro te-topology-id-ref? leafref
| | | +--ro network-id-ref? leafref
| | | +--ro path-element* [path-element-id]
| | | +--ro path-element-id uint32
| | | +--ro (type)?
| | | +--:(ipv4-address)
| | | | +--ro v4-address? inet:ipv4-
address
| | | | +--ro v4-prefix-length? uint8
| | | | +--ro v4-loose? boolean
| | | +--:(ipv6-address)
| | | | +--ro v6-address? inet:ipv6-
address
| | | | +--ro v6-prefix-length? uint8
| | | | +--ro v6-loose? boolean
| | | +--:(as-number)
| | | | +--ro as-number? uint16
| | | +--:(unnumbered-link)
| | | | +--ro router-id? inet:ip-address
| | | | +--ro interface-id? uint32
| | | +--:(label)
| | | +--ro value? uint32
| | +--ro underlay-backup-path* [index]
| | | +--ro index uint32
| | | +--ro provider-id-ref? leafref
| | | +--ro client-id-ref? leafref
| | | +--ro te-topology-id-ref? leafref
| | | +--ro network-id-ref? leafref
| | | +--ro path-element* [path-element-id]
| | | +--ro path-element-id uint32
| | | +--ro (type)?
| | | +--:(ipv4-address)
| | | | +--ro v4-address? inet:ipv4-
address
| | | | +--ro v4-prefix-length? uint8
| | | | +--ro v4-loose? boolean
| | | +--:(ipv6-address)
| | | | +--ro v6-address? inet:ipv6-
address
| | | | +--ro v6-prefix-length? uint8
| | | | +--ro v6-loose? boolean
| | | +--:(as-number)
| | | | +--ro as-number? uint16
| | | +--:(unnumbered-link)
| | | | +--ro router-id? inet:ip-address
| | | | +--ro interface-id? uint32
| | | +--:(label)
| | | +--ro value? uint32
| | +--ro underlay-protection-type? uint16
| | +--ro underlay-trail-src
| | | +--ro tp-ref? leafref
| | | +--ro node-ref? leafref
| | | +--ro network-ref? leafref
| | +--ro underlay-trail-des
| | +--ro tp-ref? leafref
| | +--ro node-ref? leafref
| | +--ro network-ref? leafref
| +--ro admin-status? te-admin-status
| +--ro performance-metric-throttle {te-performance-
metric}?
| | +--ro unidirectional-delay-offset? uint32
| | +--ro measure-interval? uint32
| | +--ro advertisement-interval? uint32
| | +--ro suppression-interval? uint32
| | +--ro threshold-out
| | | +--ro unidirectional-delay? uint32
| | | +--ro unidirectional-min-delay? uint32
| | | +--ro unidirectional-max-delay? uint32
| | | +--ro unidirectional-delay-variation? uint32
| | | +--ro unidirectional-packet-loss?
decimal64
| | | +--ro unidirectional-residual-bandwidth?
decimal64
| | | +--ro unidirectional-available-bandwidth?
decimal64
| | | +--ro unidirectional-utilized-bandwidth?
decimal64
| | +--ro threshold-in
| | | +--ro unidirectional-delay? uint32
| | | +--ro unidirectional-min-delay? uint32
| | | +--ro unidirectional-max-delay? uint32
| | | +--ro unidirectional-delay-variation? uint32
| | | +--ro unidirectional-packet-loss?
decimal64
| | | +--ro unidirectional-residual-bandwidth?
decimal64
| | | +--ro unidirectional-available-bandwidth?
decimal64
| | | +--ro unidirectional-utilized-bandwidth?
decimal64
| | +--ro threshold-accelerated-advertisement
| | +--ro unidirectional-delay? uint32
| | +--ro unidirectional-min-delay? uint32
| | +--ro unidirectional-max-delay? uint32
| | +--ro unidirectional-delay-variation? uint32
| | +--ro unidirectional-packet-loss?
decimal64
| | +--ro unidirectional-residual-bandwidth?
decimal64
| | +--ro unidirectional-available-bandwidth?
decimal64
| | +--ro unidirectional-utilized-bandwidth?
decimal64
| +--ro link-index? uint64
| +--ro administrative-group? te-types:admin-
groups
| +--ro max-link-bandwidth? decimal64
| +--ro max-resv-link-bandwidth? decimal64
| +--ro unreserved-bandwidth* [priority]
| | +--ro priority uint8
| | +--ro bandwidth? decimal64
| +--ro te-default-metric? uint32
| +--ro performance-metric {te-performance-metric}?
| | +--ro measurement
| | | +--ro unidirectional-delay? uint32
| | | +--ro unidirectional-min-delay? uint32
| | | +--ro unidirectional-max-delay? uint32
| | | +--ro unidirectional-delay-variation? uint32
| | | +--ro unidirectional-packet-loss?
decimal64
| | | +--ro unidirectional-residual-bandwidth?
decimal64
| | | +--ro unidirectional-available-bandwidth?
decimal64
| | | +--ro unidirectional-utilized-bandwidth?
decimal64
| | +--ro normality
| | +--ro unidirectional-delay?
performance-metric-normality
| | +--ro unidirectional-min-delay?
performance-metric-normality
| | +--ro unidirectional-max-delay?
performance-metric-normality
| | +--ro unidirectional-delay-variation?
performance-metric-normality
| | +--ro unidirectional-packet-loss?
performance-metric-normality
| | +--ro unidirectional-residual-bandwidth?
performance-metric-normality
| | +--ro unidirectional-available-bandwidth?
performance-metric-normality
| | +--ro unidirectional-utilized-bandwidth?
performance-metric-normality
| +--ro link-protection-type? enumeration
| +--ro interface-switching-capability* [switching-
capability]
| | +--ro switching-capability identityref
| | +--ro encoding? identityref
| | +--ro max-lsp-bandwidth* [priority]
| | | +--ro priority uint8
| | | +--ro bandwidth? decimal64
| | +--ro packet-switch-capable
| | | +--ro minimum-lsp-bandwidth? decimal64
| | | +--ro interface-mtu? uint16
| | +--ro time-division-multiplex-capable
| | | +--ro minimum-lsp-bandwidth? decimal64
| | | +--ro indication? enumeration
| | +--ro interface-adjustment-capability* [upper-sc]
| | +--ro upper-sc identityref
| | +--ro upper-encoding? identityref
| | +--ro max-lsp-bandwidth* [priority]
| | +--ro priority uint8
| | +--ro bandwidth? decimal64
| +--ro te-srlgs
| +--ro values* te-types:srlg
+--ro oper-status? te-oper-status
+--ro information-source? enumeration
+--ro information-source-state
| +--ro credibility-preference? uint16
| +--ro topology
| | +--ro provider-id-ref? leafref
| | +--ro client-id-ref? leafref
| | +--ro te-topology-id-ref? leafref
| | +--ro network-id-ref? leafref
| +--ro routing-instance? string
+--ro alt-information-sources* [information-source]
| +--ro information-source enumeration
| +--ro information-source-state
| | +--ro credibility-preference? uint16
| | +--ro topology
| | | +--ro provider-id-ref? leafref
| | | +--ro client-id-ref? leafref
| | | +--ro te-topology-id-ref? leafref
| | | +--ro network-id-ref? leafref
| | +--ro routing-instance? string
| +--ro link-index? uint64
| +--ro administrative-group? te-types:admin-
groups
| +--ro max-link-bandwidth? decimal64
| +--ro max-resv-link-bandwidth? decimal64
| +--ro unreserved-bandwidth* [priority]
| | +--ro priority uint8
| | +--ro bandwidth? decimal64
| +--ro te-default-metric? uint32
| +--ro performance-metric {te-performance-metric}?
| | +--ro measurement
| | | +--ro unidirectional-delay? uint32
| | | +--ro unidirectional-min-delay? uint32
| | | +--ro unidirectional-max-delay? uint32
| | | +--ro unidirectional-delay-variation? uint32
| | | +--ro unidirectional-packet-loss?
decimal64
| | | +--ro unidirectional-residual-bandwidth?
decimal64
| | | +--ro unidirectional-available-bandwidth?
decimal64
| | | +--ro unidirectional-utilized-bandwidth?
decimal64
| | +--ro normality
| | +--ro unidirectional-delay?
performance-metric-normality
| | +--ro unidirectional-min-delay?
performance-metric-normality
| | +--ro unidirectional-max-delay?
performance-metric-normality
| | +--ro unidirectional-delay-variation?
performance-metric-normality
| | +--ro unidirectional-packet-loss?
performance-metric-normality
| | +--ro unidirectional-residual-bandwidth?
performance-metric-normality
| | +--ro unidirectional-available-bandwidth?
performance-metric-normality
| | +--ro unidirectional-utilized-bandwidth?
performance-metric-normality
| +--ro link-protection-type? enumeration
| +--ro interface-switching-capability* [switching-
capability]
| | +--ro switching-capability identityref
| | +--ro encoding? identityref
| | +--ro max-lsp-bandwidth* [priority]
| | | +--ro priority uint8
| | | +--ro bandwidth? decimal64
| | +--ro packet-switch-capable
| | | +--ro minimum-lsp-bandwidth? decimal64
| | | +--ro interface-mtu? uint16
| | +--ro time-division-multiplex-capable
| | | +--ro minimum-lsp-bandwidth? decimal64
| | | +--ro indication? enumeration
| | +--ro interface-adjustment-capability* [upper-sc]
| | +--ro upper-sc identityref
| | +--ro upper-encoding? identityref
| | +--ro max-lsp-bandwidth* [priority]
| | +--ro priority uint8
| | +--ro bandwidth? decimal64
| +--ro te-srlgs
| +--ro values* te-types:srlg
+--ro recovery
| +--ro restoration-status? te-recovery-status
| +--ro protection-status? te-recovery-status
+--ro underlay {te-topology-hierarchy}?
+--ro dynamic? boolean
+--ro committed? boolean
augment /nw:network/nw:node/nt:termination-point:
+--rw te!
+--rw te-tp-id te-tp-id
+--rw config
| +--rw schedules
| +--rw schedule* [schedule-id]
| +--rw schedule-id uint32
| +--rw start? yang:date-and-time
| +--rw schedule-duration? string
| +--rw repeat-interval? string
+--ro state
+--ro schedules
+--ro schedule* [schedule-id]
+--ro schedule-id uint32
+--ro start? yang:date-and-time
+--ro schedule-duration? string
+--ro repeat-interval? string
notifications:
+---n te-node-event
| +--ro event-type? te-topology-event-type
| +--ro node-ref? leafref
| +--ro network-ref? leafref
| +--ro te-topology!
| +--ro te-node-attributes
| | +--ro schedules
| | | +--ro schedule* [schedule-id]
| | | +--ro schedule-id uint32
| | | +--ro start? yang:date-and-time
| | | +--ro schedule-duration? string
| | | +--ro repeat-interval? string
| | +--ro admin-status? te-admin-status
| | +--ro connectivity-matrix* [id]
| | | +--ro id uint32
| | | +--ro from
| | | | +--ro tp-ref? leafref
| | | | +--ro node-ref? leafref
| | | | +--ro network-ref? leafref
| | | +--ro to
| | | | +--ro tp-ref? leafref
| | | | +--ro node-ref? leafref
| | | | +--ro network-ref? leafref
| | | +--ro is-allowed? boolean
| | +--ro domain-id? uint32
| | +--ro flag* te-node-flag
| | +--ro is-abstract? empty
| | +--ro name? inet:domain-name
| | +--ro signaling-address* inet:ip-address
| | +--ro underlay-topology {te-topology-hierarchy}?
| | +--ro provider-id-ref? leafref
| | +--ro client-id-ref? leafref
| | +--ro te-topology-id-ref? leafref
| | +--ro network-id-ref? leafref
| +--ro oper-status? te-oper-status
| +--ro is-multi-access-dr? empty
| +--ro information-source? enumeration
| +--ro information-source-state
| +--ro credibility-preference? uint16
| +--ro topology
| | +--ro provider-id-ref? leafref
| | +--ro client-id-ref? leafref
| | +--ro te-topology-id-ref? leafref
| | +--ro network-id-ref? leafref
| +--ro routing-instance? string
+---n te-link-event
+--ro event-type? te-topology-event-type
+--ro link-ref? leafref
+--ro network-ref? leafref
+--ro te-topology!
+--ro te-link-attributes
| +--ro schedules
| | +--ro schedule* [schedule-id]
| | +--ro schedule-id uint32
| | +--ro start? yang:date-and-time
| | +--ro schedule-duration? string
| | +--ro repeat-interval? string
| +--ro access-type? te-link-access-type
| +--ro flag* te-link-flag
| +--ro is-abstract? empty
| +--ro name? string
| +--ro underlay! {te-topology-hierarchy}?
| | +--ro underlay-primary-path
| | | +--ro provider-id-ref? leafref
| | | +--ro client-id-ref? leafref
| | | +--ro te-topology-id-ref? leafref
| | | +--ro network-id-ref? leafref
| | | +--ro path-element* [path-element-id]
| | | +--ro path-element-id uint32
| | | +--ro (type)?
| | | +--:(ipv4-address)
| | | | +--ro v4-address? inet:ipv4-address
| | | | +--ro v4-prefix-length? uint8
| | | | +--ro v4-loose? boolean
| | | +--:(ipv6-address)
| | | | +--ro v6-address? inet:ipv6-address
| | | | +--ro v6-prefix-length? uint8
| | | | +--ro v6-loose? boolean
| | | +--:(as-number)
| | | | +--ro as-number? uint16
| | | +--:(unnumbered-link)
| | | | +--ro router-id? inet:ip-address
| | | | +--ro interface-id? uint32
| | | +--:(label)
| | | +--ro value? uint32
| | +--ro underlay-backup-path* [index]
| | | +--ro index uint32
| | | +--ro provider-id-ref? leafref
| | | +--ro client-id-ref? leafref
| | | +--ro te-topology-id-ref? leafref
| | | +--ro network-id-ref? leafref
| | | +--ro path-element* [path-element-id]
| | | +--ro path-element-id uint32
| | | +--ro (type)?
| | | +--:(ipv4-address)
| | | | +--ro v4-address? inet:ipv4-address
| | | | +--ro v4-prefix-length? uint8
| | | | +--ro v4-loose? boolean
| | | +--:(ipv6-address)
| | | | +--ro v6-address? inet:ipv6-address
| | | | +--ro v6-prefix-length? uint8
| | | | +--ro v6-loose? boolean
| | | +--:(as-number)
| | | | +--ro as-number? uint16
| | | +--:(unnumbered-link)
| | | | +--ro router-id? inet:ip-address
| | | | +--ro interface-id? uint32
| | | +--:(label)
| | | +--ro value? uint32
| | +--ro underlay-protection-type? uint16
| | +--ro underlay-trail-src
| | | +--ro tp-ref? leafref
| | | +--ro node-ref? leafref
| | | +--ro network-ref? leafref
| | +--ro underlay-trail-des
| | | +--ro tp-ref? leafref
| | | +--ro node-ref? leafref
| | | +--ro network-ref? leafref
| | +--ro dynamic? boolean
| | +--ro committed? boolean
| +--ro admin-status? te-admin-status
| +--ro performance-metric-throttle {te-performance-metric}?
| | +--ro unidirectional-delay-offset? uint32
| | +--ro measure-interval? uint32
| | +--ro advertisement-interval? uint32
| | +--ro suppression-interval? uint32
| | +--ro threshold-out
| | | +--ro unidirectional-delay? uint32
| | | +--ro unidirectional-min-delay? uint32
| | | +--ro unidirectional-max-delay? uint32
| | | +--ro unidirectional-delay-variation? uint32
| | | +--ro unidirectional-packet-loss? decimal64
| | | +--ro unidirectional-residual-bandwidth? decimal64
| | | +--ro unidirectional-available-bandwidth? decimal64
| | | +--ro unidirectional-utilized-bandwidth? decimal64
| | +--ro threshold-in
| | | +--ro unidirectional-delay? uint32
| | | +--ro unidirectional-min-delay? uint32
| | | +--ro unidirectional-max-delay? uint32
| | | +--ro unidirectional-delay-variation? uint32
| | | +--ro unidirectional-packet-loss? decimal64
| | | +--ro unidirectional-residual-bandwidth? decimal64
| | | +--ro unidirectional-available-bandwidth? decimal64
| | | +--ro unidirectional-utilized-bandwidth? decimal64
| | +--ro threshold-accelerated-advertisement
| | +--ro unidirectional-delay? uint32
| | +--ro unidirectional-min-delay? uint32
| | +--ro unidirectional-max-delay? uint32
| | +--ro unidirectional-delay-variation? uint32
| | +--ro unidirectional-packet-loss? decimal64
| | +--ro unidirectional-residual-bandwidth? decimal64
| | +--ro unidirectional-available-bandwidth? decimal64
| | +--ro unidirectional-utilized-bandwidth? decimal64
| +--ro link-index? uint64
| +--ro administrative-group? te-types:admin-
groups
| +--ro max-link-bandwidth? decimal64
| +--ro max-resv-link-bandwidth? decimal64
| +--ro unreserved-bandwidth* [priority]
| | +--ro priority uint8
| | +--ro bandwidth? decimal64
| +--ro te-default-metric? uint32
| +--ro performance-metric {te-performance-metric}?
| | +--ro measurement
| | | +--ro unidirectional-delay? uint32
| | | +--ro unidirectional-min-delay? uint32
| | | +--ro unidirectional-max-delay? uint32
| | | +--ro unidirectional-delay-variation? uint32
| | | +--ro unidirectional-packet-loss? decimal64
| | | +--ro unidirectional-residual-bandwidth? decimal64
| | | +--ro unidirectional-available-bandwidth? decimal64
| | | +--ro unidirectional-utilized-bandwidth? decimal64
| | +--ro normality
| | +--ro unidirectional-delay?
performance-metric-normality
| | +--ro unidirectional-min-delay?
performance-metric-normality
| | +--ro unidirectional-max-delay?
performance-metric-normality
| | +--ro unidirectional-delay-variation?
performance-metric-normality
| | +--ro unidirectional-packet-loss?
performance-metric-normality
| | +--ro unidirectional-residual-bandwidth?
performance-metric-normality
| | +--ro unidirectional-available-bandwidth?
performance-metric-normality
| | +--ro unidirectional-utilized-bandwidth?
performance-metric-normality
| +--ro link-protection-type? enumeration
| +--ro interface-switching-capability* [switching-
capability]
| | +--ro switching-capability identityref
| | +--ro encoding? identityref
| | +--ro max-lsp-bandwidth* [priority]
| | | +--ro priority uint8
| | | +--ro bandwidth? decimal64
| | +--ro packet-switch-capable
| | | +--ro minimum-lsp-bandwidth? decimal64
| | | +--ro interface-mtu? uint16
| | +--ro time-division-multiplex-capable
| | | +--ro minimum-lsp-bandwidth? decimal64
| | | +--ro indication? enumeration
| | +--ro interface-adjustment-capability* [upper-sc]
| | +--ro upper-sc identityref
| | +--ro upper-encoding? identityref
| | +--ro max-lsp-bandwidth* [priority]
| | +--ro priority uint8
| | +--ro bandwidth? decimal64
| +--ro te-srlgs
| +--ro values* te-types:srlg
+--ro oper-status? te-oper-status
+--ro information-source? enumeration
+--ro information-source-state
| +--ro credibility-preference? uint16
| +--ro topology
| | +--ro provider-id-ref? leafref
| | +--ro client-id-ref? leafref
| | +--ro te-topology-id-ref? leafref
| | +--ro network-id-ref? leafref
| +--ro routing-instance? string
+--ro alt-information-sources* [information-source]
| +--ro information-source enumeration
| +--ro information-source-state
| | +--ro credibility-preference? uint16
| | +--ro topology
| | | +--ro provider-id-ref? leafref
| | | +--ro client-id-ref? leafref
| | | +--ro te-topology-id-ref? leafref
| | | +--ro network-id-ref? leafref
| | +--ro routing-instance? string
| +--ro link-index? uint64
| +--ro administrative-group? te-types:admin-
groups
| +--ro max-link-bandwidth? decimal64
| +--ro max-resv-link-bandwidth? decimal64
| +--ro unreserved-bandwidth* [priority]
| | +--ro priority uint8
| | +--ro bandwidth? decimal64
| +--ro te-default-metric? uint32
| +--ro performance-metric {te-performance-metric}?
| | +--ro measurement
| | | +--ro unidirectional-delay? uint32
| | | +--ro unidirectional-min-delay? uint32
| | | +--ro unidirectional-max-delay? uint32
| | | +--ro unidirectional-delay-variation? uint32
| | | +--ro unidirectional-packet-loss? decimal64
| | | +--ro unidirectional-residual-bandwidth? decimal64
| | | +--ro unidirectional-available-bandwidth? decimal64
| | | +--ro unidirectional-utilized-bandwidth? decimal64
| | +--ro normality
| | +--ro unidirectional-delay?
performance-metric-normality
| | +--ro unidirectional-min-delay?
performance-metric-normality
| | +--ro unidirectional-max-delay?
performance-metric-normality
| | +--ro unidirectional-delay-variation?
performance-metric-normality
| | +--ro unidirectional-packet-loss?
performance-metric-normality
| | +--ro unidirectional-residual-bandwidth?
performance-metric-normality
| | +--ro unidirectional-available-bandwidth?
performance-metric-normality
| | +--ro unidirectional-utilized-bandwidth?
performance-metric-normality
| +--ro link-protection-type? enumeration
| +--ro interface-switching-capability* [switching-
capability]
| | +--ro switching-capability identityref
| | +--ro encoding? identityref
| | +--ro max-lsp-bandwidth* [priority]
| | | +--ro priority uint8
| | | +--ro bandwidth? decimal64
| | +--ro packet-switch-capable
| | | +--ro minimum-lsp-bandwidth? decimal64
| | | +--ro interface-mtu? uint16
| | +--ro time-division-multiplex-capable
| | | +--ro minimum-lsp-bandwidth? decimal64
| | | +--ro indication? enumeration
| | +--ro interface-adjustment-capability* [upper-sc]
| | +--ro upper-sc identityref
| | +--ro upper-encoding? identityref
| | +--ro max-lsp-bandwidth* [priority]
| | +--ro priority uint8
| | +--ro bandwidth? decimal64
| +--ro te-srlgs
| +--ro values* te-types:srlg
+--ro recovery
| +--ro restoration-status? te-recovery-status
| +--ro protection-status? te-recovery-status
+--ro underlay {te-topology-hierarchy}?
+--ro dynamic? boolean
+--ro committed? boolean
import ietf-interfaces { 6. TE Topology Yang Module
prefix "if";
}
import ietf-te-types {
prefix "te-types";
}
organization "TBD"; <CODE BEGINS>
contact "TBD";
description "TE topology model";
revision "2015-07-02" { module ietf-te-topology {
description "Initial revision"; yang-version 1;
reference "TBD"; namespace "urn:ietf:params:xml:ns:yang:ietf-te-topology";
} // replace with IANA namespace when assigned
/* prefix "tet";
* Features
*/
feature te-topology-hierarchy { import ietf-inet-types {
description prefix "inet";
"This feature indicates that the system allows underlay }
and/or overlay TE topology hierarchy.";
}
feature te-performance-metric { import ietf-schedule {
description prefix "sch";
"This feature indicates that the system supports }
TE performance metric defined in
draft-ietf-ospf-te-metric-extensions.";
}
feature configuration-schedule { import ietf-te-types {
description prefix "te-types";
"This feature indicates that the system supports }
import ietf-network {
prefix "nw";
}
import ietf-network-topology {
prefix "nt";
}
organization "TBD";
contact "TBD";
description "TE topology model";
revision "2015-10-16" {
description "Initial revision";
reference "TBD";
}
/*
* Features
*/
feature configuration-schedule {
description
"This feature indicates that the system supports
configuration scheduling."; configuration scheduling.";
} }
feature template { feature te-topology-hierarchy {
description description
"This feature indicates that the system supports "This feature indicates that the system allows underlay
and/or overlay TE topology hierarchy.";
}
feature te-performance-metric {
description
"This feature indicates that the system supports
TE performance metric defined in
RFC7471: OSPF Traffic Engineering (TE) Metric Extensions.";
}
feature template {
description
"This feature indicates that the system supports
template configuration."; template configuration.";
} }
/* /*
* Typedefs * Typedefs
*/ */
typedef performance-metric-normality {
type enumeration {
enum "unknown" {
value 0;
description
"Unknown.";
}
enum "normal" {
value 1;
description
"Normal.";
}
enum "abnormal" {
value 2;
description
"Abnormal. The anomalous bit is set.";
}
}
description
"Indicates whether a performance metric is normal, abnormal,
or unknown.";
reference
"RFC7471: OSPF Traffic Engineering (TE) Metric Extensions.";
}
typedef te-global-id { typedef te-admin-status {
type uint32; type enumeration {
description enum up {
"An identifier to uniquely identify an operator, which can be description
"Enabled.";
}
enum down {
description
"Disabled.";
}
enum testing {
description
"In some test mode.";
}
enum preparing-maintenance {
description
"Resource is disabled in the control plane to prepare for
graceful shutdown for maintenance purposes.";
reference
"RFC5817: Graceful Shutdown in MPLS and Generalized MPLS
Traffic Engineering Networks";
}
enum maintenance {
description
"Resource is disabled in the data plane for maintenance
purposes.";
}
}
description
"Defines a type representing the administrative status of
a TE resource.";
}
typedef te-global-id {
type uint32;
description
"An identifier to uniquely identify an operator, which can be
either a provider or a client. either a provider or a client.
The definition of this type is taken from RFC6370 and RFC503. The definition of this type is taken from RFC6370 and
This attribute type is used solely to provide a globally RFC5003. This attribute type is used solely to provide a
unique context for TE topologies."; globally unique context for TE topologies.";
}
typedef te-topology-id { }
type string {
pattern '/?([a-zA-Z0-9\-_.]+)(/[a-zA-Z0-9\-_.]+)*';
}
description
"An identifier for a topology.";
}
typedef te-template-name { typedef te-link-access-type {
type string { type enumeration {
pattern '/?([a-zA-Z0-9\-_.]+)(/[a-zA-Z0-9\-_.]+)*'; enum point-to-point {
} description
description "The link is point-to-point.";
"A type for the name of a TE node template or TE link }
template."; enum multi-access {
} description
"The link is multi-access, including broacast and NBMA.";
}
}
description
"Defines a type representing the access type of a TE link.";
reference
"RFC3630: Traffic Engineering (TE) Extensions to OSPF
Version 2.";
}
typedef te-node-id { typedef te-node-id {
type inet:ip-address; type inet:ip-address;
description description
"An identifier for a node in a topology. "An identifier for a node in a topology.
The identifier is represented as an IPv4 or IPv6 address. The identifier is represented as an IPv4 or IPv6 address.
The identifier SHOULD be chosen such that the same node in a This attribute is mapped to Router ID in
real network topology will always be identified through the RFC3630, RFC5329, RFC5305, and RFC 6119.";
same identifier, even if the model is instantiated in }
separate
datastores. An implementation MAY choose to capture semantics
in the identifier, for example to indicate the type of node
and/or the type of topology that the node is a part of.";
}
typedef te-link-id { typedef te-oper-status {
type union { type enumeration {
type uint32; // Unnumbered enum up {
type inet:ip-address; // IPv4 or IPv6 address description
} "Operational up.";
description }
"An identifier for a TE link on a node. enum down {
The identifier may be opaque. description
The identifier SHOULD be chosen such that the same TP in a "Operational down.";
real network topology will always be identified through the }
same identifier, even if the model is instantiated in enum testing {
separate description
datastores. An implementation MAY choose to capture semantics "In some test mode.";
in the identifier, for example to indicate the type of TP }
and/or the type of node and topology that the TP is a part enum unknown {
of."; description
} "Status cannot be determined for some reason.";
typedef te-topology-event-type { }
type enumeration { enum preparing-maintenance {
enum "add" { description
value 0; "Resource is disabled in the control plane to prepare for
description graceful shutdown for maintenance purposes.";
"A TE node or te-link has reference
been added"; "RFC5817: Graceful Shutdown in MPLS and Generalized MPLS
} Traffic Engineering Networks";
enum "remove" { }
value 1; enum maintenance {
description description
"A TE node or te-link has "Resource is disabled in the data plane for maintenance
been removed"; purposes.";
} }
enum "update" { }
value 2; description
description "Defines a type representing the operational status of
"A TE node or te-link has a TE resource.";
been updated"; }
}
}
description "TE Event type for notifications";
} // te-topology-event-type
typedef performance-metric-normality { typedef te-recovery-status {
type enumeration { type enumeration {
enum "unknown" { enum normal {
value 0; description
description "Both the recovery and working spans are fully
"Unknown"; allocated and active, data traffic is being
} transported over (or selected from) the working
enum "normal" { span, and no trigger events are reported.";
value 1; }
description enum recovery-started {
"Normal"; description
} "The recovery action has been started, but not
enum "abnormal" { completed.";
value 2; }
description enum recovery-succeeded {
"Abnormal. The anomalous bit is set."; description
} "The recovery action has succeeded. The working span has
} reported a failure/degrade condition and the user traffic
description is being transported (or selected) on the recovery
"Indicates whether a performance metric is normal, abnormal, span.";
or unknown."; }
} enum recovery-failed {
description
"The recovery action has failed.";
}
enum reversion-started {
description
"The reversion has started.";
}
enum reversion-failed {
description
"The reversion has failed.";
}
enum recovery-unavailable {
description
"The recovery is unavailable -- either as a result of an
operator Lockout command or a failure condition detected
on the recovery span.";
}
enum recovery-admin {
description
"The operator has issued a command switching the user
traffic to the recovery span.";
}
enum wait-to-restore {
description
"The recovery domain is recovering from a failuer/degrade
condition on the working span that is being controlled by
the Wait-to-Restore (WTR) timer.";
}
}
description
"Defines the status of a recovery action.";
reference
"RFC4427: Recovery (Protection and Restoration) Terminology
for Generalized Multi-Protocol Label Switching (GMPLS).
RFC6378: MPLS Transport Profile (MPLS-TP) Linear Protection";
}
/* typedef te-template-name {
* Identities type string {
*/ pattern '/?([a-zA-Z0-9\-_.]+)(/[a-zA-Z0-9\-_.]+)*';
}
description
"A type for the name of a TE node template or TE link
template.";
}
identity flag-identity { typedef te-topology-event-type {
description "Base type for flags"; type enumeration {
} enum "add" {
value 0;
description
"A TE node or te-link has been added.";
}
enum "remove" {
value 1;
description
"A TE node or te-link has been removed.";
}
enum "update" {
value 2;
description
"A TE node or te-link has been updated.";
}
}
description "TE Event type for notifications";
} // te-topology-event-type
identity undefined-flag { typedef te-topology-id {
base "flag-identity"; type string {
description "Undefined flag"; pattern '/?([a-zA-Z0-9\-_.]+)(/[a-zA-Z0-9\-_.]+)*';
} }
description
"An identifier for a topology.";
}
typedef flag-type { typedef te-tp-id {
type identityref { type union {
base "flag-identity"; type uint32; // Unnumbered
} type inet:ip-address; // IPv4 or IPv6 address
description "Type for flags"; }
} description
"An identifier for a TE link endpoint on a node.
This attribute is mapped to local or remote link identifier
in RFC3630 and RFC5305.";
}
/* /*
* Groupings * Identities
*/ */
grouping topo-ref { identity te-flag-base {
description description "Base type for flags.";
"Grouping for an absolute reference to a topology instance."; }
leaf provider-id-ref {
type leafref {
path "/tet:te-topologies/tet:topology/tet:provider-id";
}
description
"An absolute reference to a provider-id.";
}
leaf client-id-ref {
type leafref {
path "/tet:te-topologies/tet:topology/tet:client-id";
}
description
"An absolute reference to a client-id.";
}
leaf topology-id-ref {
type leafref {
path "/tet:te-topologies/tet:topology/tet:te-topology-id";
}
description
"An absolute reference to a te-topology-id.";
}
} // topo-ref
grouping link-ref { identity te-link-flag {
description base "te-flag-base";
"Grouping for an absolute reference to a link instance."; description "TE link flag.";
uses topo-ref; }
leaf source-te-node-id-ref {
type leafref {
path "/tet:te-topologies/tet:topology"
+"[tet:provider-id = current()/../provider-id-ref]"
+"[tet:client-id = current()/../client-id-ref]"
+"[tet:te-topology-id = current()/../topology-id-ref]"
+"/tet:link/tet:source-te-node-id";
}
description
"An absolute reference to a link instance.";
}
leaf source-te-link-id-ref {
type leafref {
path "/tet:te-topologies/tet:topology"
+"[tet:provider-id = current()/../provider-id-ref]"
+"[tet:client-id = current()/../client-id-ref]"
+"[tet:te-topology-id = current()/../topology-id-ref]"
+"/tet:link/tet:source-te-link-id";
}
description
"An absolute reference to a link instance.";
}
leaf dest-te-node-id-ref {
type leafref {
path "/tet:te-topologies/tet:topology"
+"[tet:provider-id = current()/../provider-id-ref]"
+"[tet:client-id = current()/../client-id-ref]"
+"[tet:te-topology-id = current()/../topology-id-ref]"
+"/tet:link/tet:dest-te-node-id";
}
description
"An absolute reference to a link instance.";
}
leaf dest-te-link-id-ref {
type leafref {
path "/tet:te-topologies/tet:topology"
+"[tet:provider-id = current()/../provider-id-ref]"
+"[tet:client-id = current()/../client-id-ref]"
+"[tet:te-topology-id = current()/../topology-id-ref]"
+"/tet:link/tet:dest-te-link-id";
}
description
"An absolute reference to a link instance.";
}
} // link-ref
grouping node-ref { identity te-node-flag {
description base "te-flag-base";
"Grouping for an absolute reference to a node instance."; description "TE node flag.";
uses topo-ref; }
leaf node-ref {
type leafref {
path "/tet:te-topologies/tet:topology"
+"[tet:provider-id = current()/../provider-id-ref]"
+"[tet:client-id = current()/../client-id-ref]"
+"[tet:te-topology-id = current()/../topology-id-ref]"
+"/tet:node/tet:te-node-id";
}
description
"An absolute reference to a node instance.";
}
} // node-ref
grouping link-end-ref { identity te-undefined-flag {
description base "te-flag-base";
"Grouping for an absolute reference to a TE link end, which is description "Undefined flag.";
the local representation of a TE link on a node."; }
uses node-ref;
leaf link-end-ref {
type leafref {
path "/tet:te-topologies/tet:topology"
+"[tet:provider-id = current()/../provider-id-ref]"
+"[tet:client-id = current()/../client-id-ref]"
+"[tet:te-topology-id = current()/../topology-id-ref]"
+"/tet:node[tet:te-node-id = current()/../node-ref]"
+"/tet:te-link/tet:te-link-id";
}
description
"Grouping for an absolute reference to a TE link end.";
}
} // link-end-ref
grouping te-topology-type { typedef te-node-flag {
description type identityref {
"Identifies the TE topology type."; base "te-node-flag";
container te-topology { }
presence "indicates TE topology"; description "Type for TE node flags.";
description }
"Its presence identifies the TE topology type.";
}
} // te-topology-type
grouping te-path-element { typedef te-link-flag {
description type identityref {
"A group of attributes defining an element in a TE path base "te-link-flag";
such as TE node, TE link, TE atomic resource or label."; }
uses te-types:explicit-route-subobject; description "Type for TE link flags.";
} // te-path-element }
grouping config-schedule-attributes { /*
description * Groupings
"A list of schedules defining when a particular */
configuration takes effect."; grouping network-ref {
list schedules { description
if-feature configuration-schedule; "Contains the information necessary to reference a network,
key "schedule-id"; for example an underlay network.";
description "A list of schedule elements."; leaf network-ref {
type leafref {
path "/nw:network/nw:network-id";
}
description
"Used to reference a network, for example an underlay
network.";
}
}
leaf schedule-id { grouping node-ref {
type uint32; description
description "Identifies the schedule element."; "Contains the information necessary to reference a node.";
} leaf node-ref {
leaf start { type leafref {
type yang:date-and-time; path "/nw:network[nw:network-id=current()/../network-ref]"+
description "Start time."; "/nw:node/nw:node-id";
}
description
"Used to reference a node.
Nodes are identified relative to the network they are
contained in.";
}
uses network-ref;
}
} grouping link-ref {
leaf schedule-duration { description
type string { "References a link in a specific network.";
pattern leaf link-ref {
'P(\d+Y)?(\d+M)?(\d+W)?(\d+D)?T(\d+H)?(\d+M)?(\d+S)?'; type leafref {
} path "/nw:network[nw:network-id=current()/../"+
description "Schedule duration in ISO 8601 format."; "network-ref]/nt:link/nt:link-id";
}
leaf repeat-interval {
type string {
pattern
'R\d*/P(\d+Y)?(\d+M)?(\d+W)?(\d+D)?T(\d+H)?(\d+M)?'
+ '(\d+S)?';
}
description "Repeat interval in ISO 8601 format.";
} }
} description
} // config-schedule-attributes "A type for an absolute reference a link instance.
(This type should not be used for relative references.
In such a case, a relative path should be used instead.)";
}
uses network-ref;
}
grouping information-source-attributes { grouping tp-ref {
description description
"The attributes identifying source that has provided the "References a termination point in a specific node.";
leaf tp-ref {
type leafref {
path "/nw:network[nw:network-id=current()/../"+
"network-ref]/nw:node[nw:node-id=current()/../"+
"node-ref]/nt:termination-point/nt:tp-id";
}
description
"A type for an absolute reference to a termination point.
(This type should not be used for relative references.
In such a case, a relative path should be used instead.)";
}
uses node-ref;
}
grouping information-source-attributes {
description
"The attributes identifying source that has provided the
related information, and the source credibility."; related information, and the source credibility.";
leaf information-source { leaf information-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 "ISIS.";
} }
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 "Indicates the source of the information.";
"Indicates the source of the information."; }
} container information-source-state {
container information-source-state { description
description "The container contains state attributes related to
"The container contains state attributes related to
the information source."; the information source.";
leaf credibility-preference { leaf credibility-preference {
type uint16; type uint16;
description description
"The preference value to calculate the traffic "The preference value to calculate 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 values. information-source values.
Higher value is more preferable."; Higher value is more preferable.";
} }
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 process to generate the result information.";
leaf provider-id-ref { uses te-topology-ref;
type leafref { } // topology
path "/tet:te-topologies/tet:topology/tet:provider-id"; leaf routing-instance {
} type string;
description description
"A reference to a provider-id."; "When applicable, this is the name of a routing instance
} from which the information is learned.";
leaf client-id-ref { } // routing-information
type leafref { }
path "/tet:te-topologies/tet:topology/tet:client-id"; } // information-source-attributes
}
description
"A reference to a client-id.";
}
leaf topology-id-ref {
type leafref {
path "/tet:te-topologies/tet:topology"
+"/tet:te-topology-id";
}
description
"A reference to a te-topology-id.";
}
} // topology
leaf routing-instance {
type string;
description
"When applicable, this is the name of a routing instance
from which the information is learned.";
} // routing-information
}
} // information-source-attributes
grouping te-node-attributes {
description "Node attributes in a TE topology.";
container te-node-attributes {
description "Node attributes in a TE topology.";
uses config-schedule-attributes;
leaf name {
type inet:domain-name;
description "Node name.";
}
leaf-list signaling-address {
type inet:ip-address;
description "Node signaling address.";
}
leaf-list flag {
type flag-type;
description "Node operational flags.";
}
leaf is-abstract {
type boolean;
description
"true if the node is abstract, false when the node is
actual.";
}
container underlay-topology {
if-feature te-topology-hierarchy;
description
"When an abstract node encapsulates a topology,
the attributes in this container point to said topology.";
leaf provider-id-ref {
type leafref {
path "/tet:te-topologies/tet:topology/tet:provider-id";
}
description
"A reference to a provider-id.";
}
leaf client-id-ref {
type leafref {
path "/tet:te-topologies/tet:topology/tet:client-id";
}
description
"A reference to a client-id.";
}
leaf topology-id-ref {
type leafref {
path "/tet:te-topologies/tet:topology"
+"/tet:te-topology-id";
}
description
"A reference to a te-topology-id.";
}
}
list connectivity-matrix {
key "id";
description
"Represents node's switching limitations, i.e. limitations
in interconnecting network TE links across the node.";
leaf id {
type uint32;
description "Identifies the connectivity-matrix entry.";
}
container from-link {
uses tet:link-end-ref;
description
"Reference to source NTP.";
}
container to-link {
uses tet:link-end-ref;
description
"Reference to destination NTP.";
}
leaf is-allowed {
type boolean;
description
"true - switching is allowed,
false - switching is disallowed.";
}
}
}
list te-link {
key "te-link-id";
description
"The local representation of a TE link, which
interconnect TE nodes.";
leaf te-link-id {
type te-link-id;
description
"TE link identifier.";
}
choice stack-level {
description
"The TE link can be partitioned into bundled
links, or component links.";
case bundle {
container bundled-links {
description
"A set of bundled links";
list bundled-link {
key "sequence";
description
"Specify a bundled interface that is
further partitioned.";
leaf sequence {
type uint32;
description
"Identify the sequence in the bundle.";
}
leaf te-link-ref {
type leafref {
path "../../../te-link-id";
require-instance true;
}
description
"Reference to TE link on this node.";
}
}
}
}
case component {
container component-links {
description
"A set of component links";
list component-link {
key "sequence";
description
"Specify a component interface that is
sufficient to unambiguously identify the
appropriate resources";
leaf sequence {
type uint32;
description
"Identify the sequence in the bundle.";
}
leaf component-link-ref {
type leafref {
path "/if:interfaces/if:interface/if:name";
require-instance false;
}
description
"Reference to component link on this
node.";
}
}
}
}
}
}
} // te-node-attributes
grouping te-node-state-attributes {
description "Node state attributes in a TE topology.";
container te-node-state {
description "Node state attributes in a TE topology.";
uses information-source-attributes;
}
} // te-node-state-attributes
grouping te-link-underlay-attributes {
description "Attributes for te-link underlay.";
container underlay-primary-path {
description
"The service path on the underlay topology that
supports this link.";
leaf provider-id-ref {
type leafref {
path "/tet:te-topologies/tet:topology/tet:provider-id";
require-instance false;
}
description
"A reference to a provider-id.";
}
leaf client-id-ref {
type leafref {
path "/tet:te-topologies/tet:topology/tet:client-id";
require-instance false;
}
description
"A reference to a client-id.";
}
leaf topology-id-ref {
type leafref {
path "/tet:te-topologies/tet:topology/tet:te-topology-id";
require-instance false;
}
description
"Identifies the topology where the path belongs.";
}
list path-element {
key "path-element-id";
description
"A list of path elements describing the service path";
leaf path-element-id {
type uint32;
description "To identify the element in a path.";
}
uses te-path-element;
}
} // underlay-primary-path
list underlay-backup-path {
key "index";
description
"A list of backup service paths on the underlay topology
that
protect the underlay primary path. If the primary path is
not protected, the list contains zero elements. If the
primary path is protected, the list contains one or more
elements.";
leaf index {
type uint32;
description
"A sequence number to identify a backup path.";
}
leaf provider-id-ref {
type leafref {
path "/tet:te-topologies/tet:topology/tet:provider-id";
require-instance false;
}
description
"A reference to a provider-id.";
}
leaf client-id-ref {
type leafref {
path "/tet:te-topologies/tet:topology/tet:client-id";
require-instance false;
}
description
"A reference to a client-id.";
}
leaf topology-id-ref {
type leafref {
path "/tet:te-topologies/tet:topology/tet:te-topology-id";
require-instance false;
}
description
"Identifies the topology where the path belongs.";
}
list path-element {
key "path-element-id";
description
"A list of path elements describing the backup service
path";
leaf path-element-id {
type uint32;
description "To identify the element in a path.";
}
uses te-path-element;
}
} // underlay-backup-path
leaf underlay-protection-type {
type uint16;
description
"Underlay protection type desired for this link";
}
container underlay-trail-src {
uses tet:link-end-ref;
description
"Source TE link of the underlay trail.";
}
container underlay-trail-des {
uses tet:link-end-ref;
description
"Destination TE link of the underlay trail.";
}
} // te-link-underlay-attributes
grouping te-link-state-underlay-attributes {
description "State attributes for te-link underlay.";
leaf dynamic {
type boolean;
description
"true if the underlay is dynamically created.";
}
leaf committed {
type boolean;
description
"true if the underlay is committed.";
}
} // te-link-state-underlay-attributes
grouping performance-metric-attributes { grouping performance-metric-attributes {
description description
"Link performance information in real time."; "Link performance information in real time.";
reference reference
"draft-ietf-ospf-te-metric-extensions."; "RFC7471: OSPF Traffic Engineering (TE) Metric Extensions.";
leaf unidirectional-delay { leaf unidirectional-delay {
type uint32 { type uint32 {
range 0..16777215; range 0..16777215;
} }
description "Delay or latency in micro seconds."; description "Delay or latency in micro seconds.";
} }
leaf unidirectional-min-delay { leaf unidirectional-min-delay {
type uint32 { type uint32 {
range 0..16777215; range 0..16777215;
} }
description "Minimum delay or latency in micro seconds."; description "Minimum delay or latency in micro seconds.";
} }
leaf unidirectional-max-delay { leaf unidirectional-max-delay {
type uint32 { type uint32 {
range 0..16777215; range 0..16777215;
} }
description "Maximum delay or latency in micro seconds."; description "Maximum delay or latency in micro seconds.";
} }
leaf unidirectional-delay-variation { leaf unidirectional-delay-variation {
type uint32 { type uint32 {
range 0..16777215; range 0..16777215;
} }
description "Delay variation in micro seconds."; description "Delay variation in micro seconds.";
} }
leaf unidirectional-packet-loss { leaf unidirectional-packet-loss {
type decimal64 { type decimal64 {
fraction-digits 6; fraction-digits 6;
range "0 .. 50.331642"; range "0 .. 50.331642";
} }
description description
"Packet loss as a percentage of the total traffic sent "Packet loss as a percentage of the total traffic sent
over a configurable interval. The finest precision is over a configurable interval. The finest precision is
0.000003%."; 0.000003%.";
} }
leaf unidirectional-residual-bandwidth { leaf unidirectional-residual-bandwidth {
type decimal64 { type decimal64 {
fraction-digits 2; fraction-digits 2;
} }
description description
"Residual bandwidth that subtracts tunnel "Residual bandwidth that subtracts tunnel
reservations from Maximum Bandwidth (or link capacity) reservations from Maximum Bandwidth (or link capacity)
[RFC3630] and provides an aggregated remainder across QoS [RFC3630] and provides an aggregated remainder across QoS
classes."; classes.";
} }
leaf unidirectional-available-bandwidth { leaf unidirectional-available-bandwidth {
type decimal64 { type decimal64 {
fraction-digits 2; fraction-digits 2;
} }
description description
"Available bandwidth that is defined to be residual "Available bandwidth that is defined to be residual
bandwidth minus the measured bandwidth used for the bandwidth minus the measured bandwidth used for the
actual forwarding of non-RSVP-TE LSP packets. For a actual forwarding of non-RSVP-TE LSP packets. For a
bundled link, available bandwidth is defined to be the bundled link, available bandwidth is defined to be the
sum of the component link available bandwidths."; sum of the component link available bandwidths.";
} }
leaf unidirectional-utilized-bandwidth { leaf unidirectional-utilized-bandwidth {
type decimal64 { type decimal64 {
fraction-digits 2; fraction-digits 2;
} }
description description
"Bandwidth utilization that represents the actual "Bandwidth utilization that represents the actual
utilization of the link (i.e. as measured in the router). utilization of the link (i.e. as measured in the router).
For a bundled link, bandwidth utilization is defined to For a bundled link, bandwidth utilization is defined to
be the sum of the component link bandwidth be the sum of the component link bandwidth
utilizations."; utilizations.";
} }
} // performance-metric-attributes } // performance-metric-attributes
grouping performance-metric-normality-attributes { grouping performance-metric-normality-attributes {
description description
"Link performance metric normality attributes."; "Link performance metric normality attributes.";
reference reference
"draft-ietf-ospf-te-metric-extensions."; "RFC7471: OSPF Traffic Engineering (TE) Metric Extensions.";
leaf unidirectional-delay { leaf unidirectional-delay {
type performance-metric-normality; type performance-metric-normality;
description "Delay normality."; description "Delay normality.";
} }
leaf unidirectional-min-delay { leaf unidirectional-min-delay {
type performance-metric-normality; type performance-metric-normality;
description "Minimum delay or latency normality."; description "Minimum delay or latency normality.";
} }
leaf unidirectional-max-delay { leaf unidirectional-max-delay {
type performance-metric-normality; type performance-metric-normality;
description "Maximum delay or latency normality."; description "Maximum delay or latency normality.";
} }
leaf unidirectional-delay-variation { leaf unidirectional-delay-variation {
type performance-metric-normality; type performance-metric-normality;
description "Delay variation normality."; description "Delay variation normality.";
} }
leaf unidirectional-packet-loss { leaf unidirectional-packet-loss {
type performance-metric-normality; type performance-metric-normality;
description "Packet loss normality."; description "Packet loss normality.";
} }
leaf unidirectional-residual-bandwidth { leaf unidirectional-residual-bandwidth {
type performance-metric-normality; type performance-metric-normality;
description "Residual bandwidth normality."; description "Residual bandwidth normality.";
} }
leaf unidirectional-available-bandwidth { leaf unidirectional-available-bandwidth {
type performance-metric-normality; type performance-metric-normality;
description "Available bandwidth normality."; description "Available bandwidth normality.";
} }
leaf unidirectional-utilized-bandwidth { leaf unidirectional-utilized-bandwidth {
type performance-metric-normality; type performance-metric-normality;
description "Bandwidth utilization normality."; description "Bandwidth utilization normality.";
} }
} // performance-metric-normality-attributes } // performance-metric-normality-attributes
grouping performance-metric-throttle-container { grouping performance-metric-throttle-container {
description description
"A container controlling performance metric throttle."; "A container controlling performance metric throttle.";
container performance-metric-throttle { container performance-metric-throttle {
if-feature te-performance-metric; if-feature te-performance-metric;
must "suppression-interval >= measure-interval" { must "suppression-interval >= measure-interval" {
error-message error-message
"suppression-interval cannot be less then "suppression-interval cannot be less then
measure-interval"; measure-interval.";
description description
"Constraint on suppression-interval and "Constraint on suppression-interval and
measure-interval."; measure-interval.";
} }
description description
"Link performance information in real time."; "Link performance information in real time.";
reference reference
"draft-ietf-ospf-te-metric-extensions."; "RFC7471: OSPF Traffic Engineering (TE) Metric Extensions.";
leaf unidirectional-delay-offset { leaf unidirectional-delay-offset {
type uint32 { type uint32 {
range 0..16777215; range 0..16777215;
} }
description description
"Offset value to be added to the measured delay value."; "Offset value to be added to the measured delay value.";
} }
leaf measure-interval { leaf measure-interval {
type uint32; type uint32;
default 30; default 30;
description description
"Interval in seconds to measure the extended metric "Interval in seconds to measure the extended metric
values."; values.";
} }
leaf advertisement-interval { leaf advertisement-interval {
type uint32; type uint32;
description description
"Interval in seconds to advertise the extended metric "Interval in seconds to advertise the extended metric
values."; values.";
} }
leaf suppression-interval { leaf suppression-interval {
type uint32 { type uint32 {
range "1 .. max"; range "1 .. max";
} }
default 120; default 120;
description description
"Interval in seconds to suppress advertising the extended "Interval in seconds to suppress advertising the extended
metric values."; metric values.";
} }
container threshold-out { container threshold-out {
uses performance-metric-attributes; uses performance-metric-attributes;
description description
"If the measured parameter falls outside an upper bound "If the measured parameter falls outside an upper bound
for all but the min delay metric (or lower bound for for all but the min delay metric (or lower bound for
min-delay metric only) and the advertised value is not min-delay metric only) and the advertised value is not
already outside that bound, anomalous announcement will be already outside that bound, anomalous announcement will
triggered."; be triggered.";
} }
container threshold-in { container threshold-in {
uses performance-metric-attributes; uses performance-metric-attributes;
description description
"If the measured parameter falls inside an upper bound "If the measured parameter falls inside an upper bound
for all but the min delay metric (or lower bound for for all but the min delay metric (or lower bound for
min-delay metric only) and the advertised value is not min-delay metric only) and the advertised value is not
already inside that bound, normal (anomalous-flag cleared) already inside that bound, normal (anomalous-flag
announcement will be triggered."; cleared) announcement will be triggered.";
} }
container threshold-accelerated-advertisement { container threshold-accelerated-advertisement {
description description
"When the difference between the last advertised value and "When the difference between the last advertised value and
current measured value exceed this threshold, anomalous current measured value exceed this threshold, anomalous
announcement will be triggered."; announcement will be triggered.";
uses performance-metric-attributes; uses performance-metric-attributes;
} }
} }
} // performance-metric-throttle-container } // performance-metric-throttle-container
grouping te-link-info-attributes { grouping te-link-augment {
description description
"Advertised TE information attributes."; "Augmentatin for TE link.";
leaf link-index {
type uint64; container te {
description presence "TE support.";
"The link identifier. If OSPF is used, this represents an description
ospfLsdbID. If IS-IS is used, this represents an isisLSPID. "Indicates TE support.";
If a locally configured link is used, this object represents
a unique value, which is locally defined in a router."; container config {
} description
leaf administrative-group { "Configuration data.";
type te-types:admin-groups; uses te-link-config;
description } // config
"Administrative group or color of the link. container state {
config false;
description
"Operational state data.";
uses te-link-config;
uses te-link-state-derived;
} // state
} // te
} // te-link-augment
grouping te-link-config {
description
"TE link configuration grouping.";
choice bundle-stack-level {
description
"The TE link can be partitioned into bundled
links, or component links.";
case bundle {
container bundled-links {
description
"A set of bundled links.";
reference
"RFC4201: Link Bundling in MPLS Traffic Engineering
(TE).";
list bundled-link {
key "sequence";
description
"Specify a bundled interface that is
further partitioned.";
leaf sequence {
type uint32;
description
"Identify the sequence in the bundle.";
}
leaf src-tp-ref {
type leafref {
path "../../../../../../nw:node[nw:node-id = "
+ "current()/../../../../../nt:source/"
+ "nt:source-node]/"
+ "nt:termination-point/nt:tp-id";
require-instance true;
}
description
"Reference to another TE termination point on the
same souruce node.";
}
leaf des-tp-ref {
type leafref {
path "../../../../../../nw:node[nw:node-id = "
+ "current()/../../../../../nt:destination/"
+ "nt:dest-node]/"
+ "nt:termination-point/nt:tp-id";
require-instance true;
}
description
"Reference to another TE termination point on the
same destination node.";
}
} // list bundled-link
}
}
case component {
container component-links {
description
"A set of component links";
list component-link {
key "sequence";
description
"Specify a component interface that is
sufficient to unambiguously identify the
appropriate resources";
leaf sequence {
type uint32;
description
"Identify the sequence in the bundle.";
}
leaf src-interface-ref {
type string;
description
"Reference to component link interface on the
source node.";
}
leaf des-interface-ref {
type string;
description
"Reference to component link interface on the
destinatioin node.";
}
}
}
}
} // bundle-stack-level
leaf-list te-link-template {
if-feature template;
type leafref {
path "../../../../te/templates/link-template/name";
}
description
"The reference to a TE link template.";