YANG Data Model for Layer 3 TE Topologies
draft-ietf-teas-yang-l3-te-topo-03
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
|
|
|---|---|---|---|
| Authors | Xufeng Liu , Igor Bryskin , Vishnu Pavan Beeram , Tarek Saad , Himanshu C. Shah , Oscar Gonzalez de Dios | ||
| Last updated | 2018-10-22 | ||
| Replaces | draft-liu-teas-yang-l3-te-topo | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews |
YANGDOCTORS Early review
(of
-04)
by Mahesh Jethanandani
On the Right Track
|
||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | I-D Exists | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-ietf-teas-yang-l3-te-topo-03
Network Working Group X. Liu
Internet-Draft Volta Networks
Intended status: Standards Track I. Bryskin
Expires: April 25, 2019 Huawei Technologies
V. Beeram
Juniper Networks
T. Saad
Cisco Systems Inc
H. Shah
Ciena
O. Gonzalez de Dios
Telefonica
October 22, 2018
YANG Data Model for Layer 3 TE Topologies
draft-ietf-teas-yang-l3-te-topo-03
Abstract
This document defines a YANG data model for layer 3 traffic
engineering topologies.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 25, 2019.
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
Liu, et al. Expires April 25, 2019 [Page 1]
Internet-Draft YANG L3 TE Topology October 2018
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3
2. Modeling Considerations for L3 TE Topologies . . . . . . . . 3
2.1. Relationship Between Layer 3 Topology and TE topology . . 3
2.2. Relationship Modeling . . . . . . . . . . . . . . . . . . 4
2.2.1. Topology Referencing . . . . . . . . . . . . . . . . 4
2.2.2. Node Referencing . . . . . . . . . . . . . . . . . . 4
2.2.3. Link Termination Point Referencing . . . . . . . . . 4
2.2.4. Link Referencing . . . . . . . . . . . . . . . . . . 5
2.3. Topology Type Modeling . . . . . . . . . . . . . . . . . 5
3. Packet Switching Technology Extensions . . . . . . . . . . . 5
3.1. Technology Specific Link Attributes . . . . . . . . . . . 5
3.2. Performance Metric . . . . . . . . . . . . . . . . . . . 6
4. Model Structure . . . . . . . . . . . . . . . . . . . . . . . 6
4.1. Layer 3 TE Topology Module . . . . . . . . . . . . . . . 6
4.2. Packet Switching TE Topology Module . . . . . . . . . . . 7
5. YANG Modules . . . . . . . . . . . . . . . . . . . . . . . . 21
5.1. Layer 3 TE Topology Module . . . . . . . . . . . . . . . 21
5.2. Packet Switching TE Topology Module . . . . . . . . . . . 26
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31
7. Security Considerations . . . . . . . . . . . . . . . . . . . 33
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 35
8.1. Normative References . . . . . . . . . . . . . . . . . . 35
8.2. Informative References . . . . . . . . . . . . . . . . . 37
Appendix A. Companion YANG Model for Non-NMDA Compliant
Implementations . . . . . . . . . . . . . . . . . . 38
A.1. Layer 3 TE Topology State Module . . . . . . . . . . . . 38
A.2. Packet Switching TE Topology State Module . . . . . . . . 41
Appendix B. Data Tree Example . . . . . . . . . . . . . . . . . 46
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 55
1. Introduction
This document defines a YANG [RFC7950] data model for describing the
relationship between a layer 3 network topology [RFC8346] and a TE
topology [I-D.ietf-teas-yang-te-topo].
Liu, et al. Expires April 25, 2019 [Page 2]
Internet-Draft YANG L3 TE Topology October 2018
When traffic engineering is enabled on a layer 3 network topology,
there will be a corresponding TE topology. The TE topology may or
may not be congruent to the layer 3 network topology. When such a
congruent TE topology exists, there will be a one-to-one association
between the one modeling element in the layer 3 topology to another
element in the TE topology. When such a congruent TE topology does
not exist, the association will not be one-to-one. This YANG data
model allows both cases.
1.1. Terminology
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14, [RFC2119].
The following terms are defined in [RFC7950] and are not redefined
here:
o augment
o data model
o data node
1.2. Tree Diagrams
Tree diagrams used in this document follow the notation defined in
[RFC8340].
2. Modeling Considerations for L3 TE Topologies
2.1. Relationship Between Layer 3 Topology and TE topology
In general, layer 3 network topology model and TE topology model can
be used independently. When traffic engineering is enabled on a
layer 3 network topology, there will be associations between objects
in layer 3 network topologies and objects in TE topologies. The
properties of these relations are:
o The associations are between objects of the same class, i.e. node
to node or link to link.
o The multiplicity of such an association is: 0..1 to 0..1. An
object in a layer 3 network may have zero or one associated object
in the corresponding TE network.
Liu, et al. Expires April 25, 2019 [Page 3]
Internet-Draft YANG L3 TE Topology October 2018
2.2. Relationship Modeling
YANG data type leafref is used to model the association relationship
between a layer 3 network topology and a TE topology. YANG must
statements are used to enforce the referenced objects are in the
topologies of proper type.
2.2.1. Topology Referencing
When TE is enabled on a layer 3 network topology, if the TE topology
is not congruent to the layer 3 network topology, the layer 3 network
topology will have a reference to the corresponding TE topology.
Such a reference is modeled as follows:
augment /nw:networks/nw:network/l3t:l3-topology-attributes:
+--rw l3-te-topology-attributes
+--rw network-ref? -> /nw:networks/network/network-id
If the TE topology is congruent to the layer 3 network topology, the
above reference can still be used to specified TE paramenters defined
in the TE topology model.
2.2.2. Node Referencing
When TE is enabled on a layer 3 network topology, if the TE topology
is not congruent to the layer 3 network topology, a layer 3 network
node may have a reference to the corresponding TE node. Such a
reference is modeled as follows:
augment /nw:networks/nw:network/nw:node/l3t:l3-node-attributes:
+--rw l3-te-node-attributes
+--rw node-ref? leafref
+--rw network-ref? -> /nw:networks/network/network-id
2.2.3. Link Termination Point Referencing
When TE is enabled on a layer 3 network topology, if the TE topology
is not congruent to the layer 3 network topology, a layer 3 link
termination point may have a reference to the corresponding TE link
termination point. Such a reference is modeled as follows:
augment /nw:networks/nw:network/nw:node/nt:termination-point
/l3t:l3-termination-point-attributes:
+--rw l3-te-tp-attributes
+--rw tp-ref? leafref
+--rw node-ref? leafref
+--rw network-ref? -> /nw:networks/network/network-id
Liu, et al. Expires April 25, 2019 [Page 4]
Internet-Draft YANG L3 TE Topology October 2018
2.2.4. Link Referencing
When TE is enabled on a layer 3 network topology, if the TE topology
is not congruent to the layer 3 network topology, a layer 3 link may
have a reference to the corresponding TE link. Such a reference is
modeled as follows:
augment /nw:networks/nw:network/nt:link/l3t:l3-link-attributes:
+--rw l3-te-link-attributes
+--rw link-ref? leafref
+--rw network-ref? -> /nw:networks/network/network-id
2.3. Topology Type Modeling
A new topology type is defined in this document, to indicate a
topology that is a layer 3 topology with TE enabled.
augment /nw:networks/nw:network/nw:network-types
/l3t:l3-unicast-topology:
+--rw l3-te!
3. Packet Switching Technology Extensions
3.1. Technology Specific Link Attributes
The technology agnostic TE Topology model is augmented with packet
switching specific link attributes:
augment /nw:networks/tet:te/tet:templates/tet:link-template
/tet:te-link-attributes
/tet:interface-switching-capability:
+--rw packet-switch-capable
+--rw minimum-lsp-bandwidth? rt-types:bandwidth-ieee-float32
+--rw interface-mtu? uint16
augment /nw:networks/nw:network/nt:link/tet:te
/tet:te-link-attributes
/tet:interface-switching-capability:
+--rw packet-switch-capable
+--rw minimum-lsp-bandwidth? rt-types:bandwidth-ieee-float32
+--rw interface-mtu? uint16
augment /nw:networks/nw:network/nt:link/tet:te
/tet:information-source-entry
/tet:interface-switching-capability:
+--ro packet-switch-capable
+--ro minimum-lsp-bandwidth? rt-types:bandwidth-ieee-float32
+--ro interface-mtu? uint16
Liu, et al. Expires April 25, 2019 [Page 5]
Internet-Draft YANG L3 TE Topology October 2018
3.2. Performance Metric
[RFC7471], [RFC7810] and [RFC7823] specify TE performance metric
parameters and their usage. The packet switching augmentations
specified in this moducment support such a capability, which can be
conditional enabled by a YANG feature "te-performance-metric".
augment /nw:networks/nw:network/nw:node/tet:te
/tet:te-node-attributes/tet:connectivity-matrices:
+--rw performance-metric
+--rw measurement
| ......
+--rw normality
| ......
+--rw throttle
......
Such an augmentation has been applied to:
o Connectivity matrices container
o Connectivity matrix entry
o Local ink connectivities container
o Local ink connectivity entry
o TE link attributes container in a TE link template
o TE link attributes container in a TE link
o Information source entry in a TE link
4. Model Structure
4.1. Layer 3 TE Topology Module
The model tree structure of the layer 3 TE topology module is as
shown below:
Liu, et al. Expires April 25, 2019 [Page 6]
Internet-Draft YANG L3 TE Topology October 2018
module: ietf-l3-te-topology
augment /nw:networks/nw:network/nw:network-types
/l3t:l3-unicast-topology:
+--rw l3-te!
augment /nw:networks/nw:network/l3t:l3-topology-attributes:
+--rw l3-te-topology-attributes
+--rw network-ref? -> /nw:networks/network/network-id
augment /nw:networks/nw:network/nw:node/l3t:l3-node-attributes:
+--rw l3-te-node-attributes
+--rw node-ref? leafref
+--rw network-ref? -> /nw:networks/network/network-id
augment /nw:networks/nw:network/nw:node/nt:termination-point
/l3t:l3-termination-point-attributes:
+--rw l3-te-tp-attributes
+--rw tp-ref? leafref
+--rw node-ref? leafref
+--rw network-ref? -> /nw:networks/network/network-id
augment /nw:networks/nw:network/nt:link/l3t:l3-link-attributes:
+--rw l3-te-link-attributes
+--rw link-ref? leafref
+--rw network-ref? -> /nw:networks/network/network-id
4.2. Packet Switching TE Topology Module
This is an augmentation to base TE topology model.
module: ietf-te-topology-packet
augment /nw:networks/nw:network/nw:node/tet:te
/tet:te-node-attributes/tet:connectivity-matrices:
+--rw 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?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--rw normality
| +--rw unidirectional-delay?
| | te-types:performance-metric-normality
| +--rw unidirectional-min-delay?
Liu, et al. Expires April 25, 2019 [Page 7]
Internet-Draft YANG L3 TE Topology October 2018
| | te-types:performance-metric-normality
| +--rw unidirectional-max-delay?
| | te-types:performance-metric-normality
| +--rw unidirectional-delay-variation?
| | te-types:performance-metric-normality
| +--rw unidirectional-packet-loss?
| | te-types:performance-metric-normality
| +--rw unidirectional-residual-bandwidth?
| | te-types:performance-metric-normality
| +--rw unidirectional-available-bandwidth?
| | te-types:performance-metric-normality
| +--rw unidirectional-utilized-bandwidth?
| te-types:performance-metric-normality
+--rw throttle
+--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?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--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?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--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
Liu, et al. Expires April 25, 2019 [Page 8]
Internet-Draft YANG L3 TE Topology October 2018
+--rw unidirectional-residual-bandwidth?
| rt-types:bandwidth-ieee-float32
+--rw unidirectional-available-bandwidth?
| rt-types:bandwidth-ieee-float32
+--rw unidirectional-utilized-bandwidth?
rt-types:bandwidth-ieee-float32
augment /nw:networks/nw:network/nw:node/tet:te
/tet:te-node-attributes/tet:connectivity-matrices
/tet:connectivity-matrix:
+--rw 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?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--rw normality
| +--rw unidirectional-delay?
| | te-types:performance-metric-normality
| +--rw unidirectional-min-delay?
| | te-types:performance-metric-normality
| +--rw unidirectional-max-delay?
| | te-types:performance-metric-normality
| +--rw unidirectional-delay-variation?
| | te-types:performance-metric-normality
| +--rw unidirectional-packet-loss?
| | te-types:performance-metric-normality
| +--rw unidirectional-residual-bandwidth?
| | te-types:performance-metric-normality
| +--rw unidirectional-available-bandwidth?
| | te-types:performance-metric-normality
| +--rw unidirectional-utilized-bandwidth?
| te-types:performance-metric-normality
+--rw throttle
+--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
Liu, et al. Expires April 25, 2019 [Page 9]
Internet-Draft YANG L3 TE Topology October 2018
| +--rw unidirectional-delay-variation? uint32
| +--rw unidirectional-packet-loss? decimal64
| +--rw unidirectional-residual-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--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?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--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?
| rt-types:bandwidth-ieee-float32
+--rw unidirectional-available-bandwidth?
| rt-types:bandwidth-ieee-float32
+--rw unidirectional-utilized-bandwidth?
rt-types:bandwidth-ieee-float32
augment /nw:networks/nw:network/nw:node/tet:te
/tet:information-source-entry/tet:connectivity-matrices:
+--ro 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?
| | rt-types:bandwidth-ieee-float32
| +--ro unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--ro unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--ro normality
Liu, et al. Expires April 25, 2019 [Page 10]
Internet-Draft YANG L3 TE Topology October 2018
| +--ro unidirectional-delay?
| | te-types:performance-metric-normality
| +--ro unidirectional-min-delay?
| | te-types:performance-metric-normality
| +--ro unidirectional-max-delay?
| | te-types:performance-metric-normality
| +--ro unidirectional-delay-variation?
| | te-types:performance-metric-normality
| +--ro unidirectional-packet-loss?
| | te-types:performance-metric-normality
| +--ro unidirectional-residual-bandwidth?
| | te-types:performance-metric-normality
| +--ro unidirectional-available-bandwidth?
| | te-types:performance-metric-normality
| +--ro unidirectional-utilized-bandwidth?
| te-types:performance-metric-normality
+--ro throttle
+--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?
| | rt-types:bandwidth-ieee-float32
| +--ro unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--ro unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--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?
| | rt-types:bandwidth-ieee-float32
| +--ro unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--ro unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--ro threshold-accelerated-advertisement
+--ro unidirectional-delay? uint32
+--ro unidirectional-min-delay? uint32
Liu, et al. Expires April 25, 2019 [Page 11]
Internet-Draft YANG L3 TE Topology October 2018
+--ro unidirectional-max-delay? uint32
+--ro unidirectional-delay-variation? uint32
+--ro unidirectional-packet-loss? decimal64
+--ro unidirectional-residual-bandwidth?
| rt-types:bandwidth-ieee-float32
+--ro unidirectional-available-bandwidth?
| rt-types:bandwidth-ieee-float32
+--ro unidirectional-utilized-bandwidth?
rt-types:bandwidth-ieee-float32
augment /nw:networks/nw:network/nw:node/tet:te
/tet:information-source-entry/tet:connectivity-matrices
/tet:connectivity-matrix:
+--ro 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?
| | rt-types:bandwidth-ieee-float32
| +--ro unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--ro unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--ro normality
| +--ro unidirectional-delay?
| | te-types:performance-metric-normality
| +--ro unidirectional-min-delay?
| | te-types:performance-metric-normality
| +--ro unidirectional-max-delay?
| | te-types:performance-metric-normality
| +--ro unidirectional-delay-variation?
| | te-types:performance-metric-normality
| +--ro unidirectional-packet-loss?
| | te-types:performance-metric-normality
| +--ro unidirectional-residual-bandwidth?
| | te-types:performance-metric-normality
| +--ro unidirectional-available-bandwidth?
| | te-types:performance-metric-normality
| +--ro unidirectional-utilized-bandwidth?
| te-types:performance-metric-normality
+--ro throttle
+--ro unidirectional-delay-offset? uint32
+--ro measure-interval? uint32
+--ro advertisement-interval? uint32
+--ro suppression-interval? uint32
+--ro threshold-out
Liu, et al. Expires April 25, 2019 [Page 12]
Internet-Draft YANG L3 TE Topology October 2018
| +--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?
| | rt-types:bandwidth-ieee-float32
| +--ro unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--ro unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--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?
| | rt-types:bandwidth-ieee-float32
| +--ro unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--ro unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--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?
| rt-types:bandwidth-ieee-float32
+--ro unidirectional-available-bandwidth?
| rt-types:bandwidth-ieee-float32
+--ro unidirectional-utilized-bandwidth?
rt-types:bandwidth-ieee-float32
augment /nw:networks/nw:network/nw:node/tet:te
/tet:tunnel-termination-point
/tet:local-link-connectivities:
+--rw 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?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-available-bandwidth?
Liu, et al. Expires April 25, 2019 [Page 13]
Internet-Draft YANG L3 TE Topology October 2018
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--rw normality
| +--rw unidirectional-delay?
| | te-types:performance-metric-normality
| +--rw unidirectional-min-delay?
| | te-types:performance-metric-normality
| +--rw unidirectional-max-delay?
| | te-types:performance-metric-normality
| +--rw unidirectional-delay-variation?
| | te-types:performance-metric-normality
| +--rw unidirectional-packet-loss?
| | te-types:performance-metric-normality
| +--rw unidirectional-residual-bandwidth?
| | te-types:performance-metric-normality
| +--rw unidirectional-available-bandwidth?
| | te-types:performance-metric-normality
| +--rw unidirectional-utilized-bandwidth?
| te-types:performance-metric-normality
+--rw throttle
+--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?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--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?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-utilized-bandwidth?
Liu, et al. Expires April 25, 2019 [Page 14]
Internet-Draft YANG L3 TE Topology October 2018
| rt-types:bandwidth-ieee-float32
+--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?
| rt-types:bandwidth-ieee-float32
+--rw unidirectional-available-bandwidth?
| rt-types:bandwidth-ieee-float32
+--rw unidirectional-utilized-bandwidth?
rt-types:bandwidth-ieee-float32
augment /nw:networks/nw:network/nw:node/tet:te
/tet:tunnel-termination-point
/tet:local-link-connectivities
/tet:local-link-connectivity:
+--rw 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?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--rw normality
| +--rw unidirectional-delay?
| | te-types:performance-metric-normality
| +--rw unidirectional-min-delay?
| | te-types:performance-metric-normality
| +--rw unidirectional-max-delay?
| | te-types:performance-metric-normality
| +--rw unidirectional-delay-variation?
| | te-types:performance-metric-normality
| +--rw unidirectional-packet-loss?
| | te-types:performance-metric-normality
| +--rw unidirectional-residual-bandwidth?
| | te-types:performance-metric-normality
| +--rw unidirectional-available-bandwidth?
| | te-types:performance-metric-normality
| +--rw unidirectional-utilized-bandwidth?
| te-types:performance-metric-normality
+--rw throttle
Liu, et al. Expires April 25, 2019 [Page 15]
Internet-Draft YANG L3 TE Topology October 2018
+--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?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--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?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--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?
| rt-types:bandwidth-ieee-float32
+--rw unidirectional-available-bandwidth?
| rt-types:bandwidth-ieee-float32
+--rw unidirectional-utilized-bandwidth?
rt-types:bandwidth-ieee-float32
augment /nw:networks/tet:te/tet:templates/tet:link-template
/tet:te-link-attributes:
+--rw performance-metric
+--rw measurement
| +--rw unidirectional-delay? uint32
| +--rw unidirectional-min-delay? uint32
| +--rw unidirectional-max-delay? uint32
| +--rw unidirectional-delay-variation? uint32
Liu, et al. Expires April 25, 2019 [Page 16]
Internet-Draft YANG L3 TE Topology October 2018
| +--rw unidirectional-packet-loss? decimal64
| +--rw unidirectional-residual-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--rw normality
| +--rw unidirectional-delay?
| | te-types:performance-metric-normality
| +--rw unidirectional-min-delay?
| | te-types:performance-metric-normality
| +--rw unidirectional-max-delay?
| | te-types:performance-metric-normality
| +--rw unidirectional-delay-variation?
| | te-types:performance-metric-normality
| +--rw unidirectional-packet-loss?
| | te-types:performance-metric-normality
| +--rw unidirectional-residual-bandwidth?
| | te-types:performance-metric-normality
| +--rw unidirectional-available-bandwidth?
| | te-types:performance-metric-normality
| +--rw unidirectional-utilized-bandwidth?
| te-types:performance-metric-normality
+--rw throttle
+--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?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--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?
Liu, et al. Expires April 25, 2019 [Page 17]
Internet-Draft YANG L3 TE Topology October 2018
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--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?
| rt-types:bandwidth-ieee-float32
+--rw unidirectional-available-bandwidth?
| rt-types:bandwidth-ieee-float32
+--rw unidirectional-utilized-bandwidth?
rt-types:bandwidth-ieee-float32
augment /nw:networks/nw:network/nt:link/tet:te
/tet:te-link-attributes:
+--rw 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?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--rw normality
| +--rw unidirectional-delay?
| | te-types:performance-metric-normality
| +--rw unidirectional-min-delay?
| | te-types:performance-metric-normality
| +--rw unidirectional-max-delay?
| | te-types:performance-metric-normality
| +--rw unidirectional-delay-variation?
| | te-types:performance-metric-normality
| +--rw unidirectional-packet-loss?
| | te-types:performance-metric-normality
| +--rw unidirectional-residual-bandwidth?
| | te-types:performance-metric-normality
| +--rw unidirectional-available-bandwidth?
| | te-types:performance-metric-normality
| +--rw unidirectional-utilized-bandwidth?
Liu, et al. Expires April 25, 2019 [Page 18]
Internet-Draft YANG L3 TE Topology October 2018
| te-types:performance-metric-normality
+--rw throttle
+--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?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--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?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--rw unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--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?
| rt-types:bandwidth-ieee-float32
+--rw unidirectional-available-bandwidth?
| rt-types:bandwidth-ieee-float32
+--rw unidirectional-utilized-bandwidth?
rt-types:bandwidth-ieee-float32
augment /nw:networks/nw:network/nt:link/tet:te
/tet:information-source-entry:
+--ro performance-metric
+--ro measurement
| +--ro unidirectional-delay? uint32
| +--ro unidirectional-min-delay? uint32
Liu, et al. Expires April 25, 2019 [Page 19]
Internet-Draft YANG L3 TE Topology October 2018
| +--ro unidirectional-max-delay? uint32
| +--ro unidirectional-delay-variation? uint32
| +--ro unidirectional-packet-loss? decimal64
| +--ro unidirectional-residual-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--ro unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--ro unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--ro normality
| +--ro unidirectional-delay?
| | te-types:performance-metric-normality
| +--ro unidirectional-min-delay?
| | te-types:performance-metric-normality
| +--ro unidirectional-max-delay?
| | te-types:performance-metric-normality
| +--ro unidirectional-delay-variation?
| | te-types:performance-metric-normality
| +--ro unidirectional-packet-loss?
| | te-types:performance-metric-normality
| +--ro unidirectional-residual-bandwidth?
| | te-types:performance-metric-normality
| +--ro unidirectional-available-bandwidth?
| | te-types:performance-metric-normality
| +--ro unidirectional-utilized-bandwidth?
| te-types:performance-metric-normality
+--ro throttle
+--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?
| | rt-types:bandwidth-ieee-float32
| +--ro unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--ro unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--ro threshold-in
| +--ro unidirectional-delay? uint32
| +--ro unidirectional-min-delay? uint32
| +--ro unidirectional-max-delay? uint32
| +--ro unidirectional-delay-variation? uint32
Liu, et al. Expires April 25, 2019 [Page 20]
Internet-Draft YANG L3 TE Topology October 2018
| +--ro unidirectional-packet-loss? decimal64
| +--ro unidirectional-residual-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--ro unidirectional-available-bandwidth?
| | rt-types:bandwidth-ieee-float32
| +--ro unidirectional-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32
+--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?
| rt-types:bandwidth-ieee-float32
+--ro unidirectional-available-bandwidth?
| rt-types:bandwidth-ieee-float32
+--ro unidirectional-utilized-bandwidth?
rt-types:bandwidth-ieee-float32
augment /nw:networks/tet:te/tet:templates/tet:link-template
/tet:te-link-attributes
/tet:interface-switching-capability:
+--rw packet-switch-capable
+--rw minimum-lsp-bandwidth? rt-types:bandwidth-ieee-float32
+--rw interface-mtu? uint16
augment /nw:networks/nw:network/nt:link/tet:te
/tet:te-link-attributes
/tet:interface-switching-capability:
+--rw packet-switch-capable
+--rw minimum-lsp-bandwidth? rt-types:bandwidth-ieee-float32
+--rw interface-mtu? uint16
augment /nw:networks/nw:network/nt:link/tet:te
/tet:information-source-entry
/tet:interface-switching-capability:
+--ro packet-switch-capable
+--ro minimum-lsp-bandwidth? rt-types:bandwidth-ieee-float32
+--ro interface-mtu? uint16
5. YANG Modules
5.1. Layer 3 TE Topology Module
This module references [RFC8345], [RFC8346], and
[I-D.ietf-teas-yang-te-topo].
<CODE BEGINS> file "ietf-l3-te-topology@2018-06-22.yang"
Liu, et al. Expires April 25, 2019 [Page 21]
Internet-Draft YANG L3 TE Topology October 2018
module ietf-l3-te-topology {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-l3-te-topology";
prefix "l3tet";
import ietf-network {
prefix "nw";
reference "RFC 8345: A YANG Data Model for Network Topologies";
}
import ietf-network-topology {
prefix "nt";
reference "RFC 8345: A YANG Data Model for Network Topologies";
}
import ietf-l3-unicast-topology {
prefix "l3t";
reference "RFC 8346: A YANG Data Model for Layer 3 Topologies";
}
import ietf-te-topology {
prefix "tet";
reference
"I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic
Engineering (TE) Topologies";
}
organization
"IETF Traffic Engineering Architecture and Signaling (TEAS)
Working Group";
contact
"WG Web: <http://tools.ietf.org/wg/teas/>
WG List: <mailto:teas@ietf.org>
Editor: Xufeng Liu
<mailto:xufeng.liu.ietf@gmail.com>
Editor: Igor Bryskin
<mailto:Igor.Bryskin@huawei.com>
Editor: Vishnu Pavan Beeram
<mailto:vbeeram@juniper.net>
Editor: Tarek Saad
<mailto:tsaad@cisco.com>
Editor: Himanshu Shah
<mailto:hshah@ciena.com>
Editor: Oscar Gonzalez De Dios
Liu, et al. Expires April 25, 2019 [Page 22]
Internet-Draft YANG L3 TE Topology October 2018
<mailto:oscar.gonzalezdedios@telefonica.com>";
description
"YANG data model for representing and manipulating Layer 3 TE
Topologies.
Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the
RFC itself for full legal notices.";
revision 2018-06-22 {
description "Initial revision";
reference "RFC XXXX: YANG Data Model for Layer 3 TE Topologies";
}
grouping l3-te-topology-type {
description
"Identifies the L3 TE topology type.";
container l3-te {
presence "indiates L3 TE Topology";
description
"Its presence identifies the L3 TE topology type.";
}
}
augment "/nw:networks/nw:network/nw:network-types/"
+ "l3t:l3-unicast-topology" {
description
"Defines the L3 TE topology type.";
uses l3-te-topology-type;
}
augment "/nw:networks/nw:network/l3t:l3-topology-attributes" {
when "../nw:network-types/l3t:l3-unicast-topology/l3tet:l3-te" {
description "Augment only for L3 TE topology";
}
description "Augment topology configuration";
uses l3-te-topology-attributes;
Liu, et al. Expires April 25, 2019 [Page 23]
Internet-Draft YANG L3 TE Topology October 2018
}
augment "/nw:networks/nw:network/nw:node/l3t:l3-node-attributes" {
when "../../nw:network-types/l3t:l3-unicast-topology/"
+ "l3tet:l3-te" {
description "Augment only for L3 TE topology";
}
description "Augment node configuration";
uses l3-te-node-attributes;
}
augment "/nw:networks/nw:network/nw:node/nt:termination-point/"
+ "l3t:l3-termination-point-attributes" {
when "../../../nw:network-types/l3t:l3-unicast-topology/"
+ "l3tet:l3-te" {
description "Augment only for L3 TE topology";
}
description "Augment termination point configuration";
uses l3-te-tp-attributes;
}
augment "/nw:networks/nw:network/nt:link/l3t:l3-link-attributes" {
when "../../nw:network-types/l3t:l3-unicast-topology/"
+ "l3tet:l3-te" {
description "Augment only for L3 TE topology";
}
description "Augment link configuration";
uses l3-te-link-attributes;
}
grouping l3-te-topology-attributes {
description "L3 TE topology scope attributes";
container l3-te-topology-attributes {
must "/nw:networks/nw:network"
+ "[nw:network-id = current()/network-ref]/nw:network-types/"
+ "tet:te-topology" {
error-message
"The referenced network must be a TE topology.";
description
"The referenced network must be a TE topology.";
}
description "Containing TE topology references";
uses nw:network-ref;
} // l3-te-topology-attributes
} // l3-te-topology-attributes
grouping l3-te-node-attributes {
description "L3 TE node scope attributes";
Liu, et al. Expires April 25, 2019 [Page 24]
Internet-Draft YANG L3 TE Topology October 2018
container l3-te-node-attributes {
must "/nw:networks/nw:network"
+ "[nw:network-id = current()/network-ref]/nw:network-types/"
+ "tet:te-topology" {
error-message
"The referenced network must be a TE topology.";
description
"The referenced network must be a TE topology.";
}
description "Containing TE node references";
uses nw:node-ref;
} // l3-te
} // l3-te-node-attributes
grouping l3-te-tp-attributes {
description "L3 TE termination point scope attributes";
container l3-te-tp-attributes {
must "/nw:networks/nw:network"
+ "[nw:network-id = current()/network-ref]/nw:network-types/"
+ "tet:te-topology" {
error-message
"The referenced network must be a TE topology.";
description
"The referenced network must be a TE topology.";
}
description "Containing TE termination point references";
uses nt:tp-ref;
} // l3-te
} // l3-te-tp-attributes
grouping l3-te-link-attributes {
description "L3 TE link scope attributes";
container l3-te-link-attributes {
must "/nw:networks/nw:network"
+ "[nw:network-id = current()/network-ref]/nw:network-types/"
+ "tet:te-topology" {
error-message
"The referenced network must be a TE topology.";
description
"The referenced network must be a TE topology.";
}
description "Containing TE link references";
uses nt:link-ref;
}
} // l3-te-link-attributes
}
<CODE ENDS>
Liu, et al. Expires April 25, 2019 [Page 25]
Internet-Draft YANG L3 TE Topology October 2018
5.2. Packet Switching TE Topology Module
This module references [RFC7471], [RFC7810], [RFC7823], [RFC8294],
[RFC8345], [RFC8346]. [I-D.ietf-teas-yang-te], and
[I-D.ietf-teas-yang-te-topo].
<CODE BEGINS> file "ietf-te-topology-packet@2018-06-22.yang"
module ietf-te-topology-packet {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-te-topology-packet";
prefix "tet-pkt";
import ietf-network {
prefix "nw";
reference "RFC 8345: A YANG Data Model for Network Topologies";
}
import ietf-network-topology {
prefix "nt";
reference "RFC 8345: A YANG Data Model for Network Topologies";
}
import ietf-routing-types {
prefix "rt-types";
reference
"RFC 8294: Common YANG Data Types for the Routing Area";
}
import ietf-te-topology {
prefix "tet";
reference
"I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic
Engineering (TE) Topologies";
}
import ietf-te-types {
prefix "te-types";
reference
"I-D.ietf-teas-yang-te: A YANG Data Model for Traffic
Engineering Tunnels and Interfaces";
}
organization
"Traffic Engineering Architecture and Signaling (TEAS)
Working Group";
Liu, et al. Expires April 25, 2019 [Page 26]
Internet-Draft YANG L3 TE Topology October 2018
contact
"WG Web: <http://tools.ietf.org/wg/teas/>
WG List: <mailto:teas@ietf.org>
Editor: Xufeng Liu
<mailto:xufeng.liu.ietf@gmail.com>
Editor: Igor Bryskin
<mailto:Igor.Bryskin@huawei.com>
Editor: Vishnu Pavan Beeram
<mailto:vbeeram@juniper.net>
Editor: Tarek Saad
<mailto:tsaad@cisco.com>
Editor: Himanshu Shah
<mailto:hshah@ciena.com>
Editor: Oscar Gonzalez De Dios
<mailto:oscar.gonzalezdedios@telefonica.com>";
description
"YANG data model for representing and manipulating PSC (Packet
Switching) TE Topologies.
Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the
RFC itself for full legal notices.";
revision 2018-06-22 {
description "Initial revision";
reference "RFC XXXX: YANG Data Model for Layer 3 TE Topologies";
}
/*
* Features
*/
Liu, et al. Expires April 25, 2019 [Page 27]
Internet-Draft YANG L3 TE Topology October 2018
feature te-performance-metric {
description
"This feature indicates that the system supports
TE performance metric.";
reference
"RFC7471: OSPF Traffic Engineering (TE) Metric Extensions.
RFC7810: IS-IS Traffic Engineering (TE) Metric Extensions.
RFC7823: Performance-Based Path Selection for Explicitly
Routed Label Switched Paths (LSPs) Using TE Metric
Extensions";
}
/*
* Groupings
*/
grouping packet-switch-capable-container {
description
"The container of packet switch capable attributes.";
container packet-switch-capable {
description
"Interface has packet-switching capabilities.";
leaf minimum-lsp-bandwidth {
type rt-types:bandwidth-ieee-float32;
description
"Minimum LSP Bandwidth. Units in bytes per second";
}
leaf interface-mtu {
type uint16;
description
"Interface MTU.";
}
}
}
/*
* Augmentations
*/
/* Augmentations to connectivity-matrix */
augment "/nw:networks/nw:network/nw:node/tet:te/"
+ "tet:te-node-attributes/tet:connectivity-matrices" {
description
"Parameters for PSC TE topology.";
uses te-types:performance-metric-container {
if-feature te-performance-metric;
}
}
augment "/nw:networks/nw:network/nw:node/tet:te/"
Liu, et al. Expires April 25, 2019 [Page 28]
Internet-Draft YANG L3 TE Topology October 2018
+ "tet:te-node-attributes/tet:connectivity-matrices/"
+ "tet:connectivity-matrix" {
description
"Parameters for PSC TE topology.";
uses te-types:performance-metric-container {
if-feature te-performance-metric;
}
}
augment "/nw:networks/nw:network/nw:node/tet:te/"
+ "tet:information-source-entry/tet:connectivity-matrices" {
description
"Parameters for PSC TE topology.";
uses te-types:performance-metric-container {
if-feature te-performance-metric;
}
}
augment "/nw:networks/nw:network/nw:node/tet:te/"
+ "tet:information-source-entry/tet:connectivity-matrices/"
+ "tet:connectivity-matrix" {
description
"Parameters for PSC TE topology.";
uses te-types:performance-metric-container {
if-feature te-performance-metric;
}
}
/* Augmentations to tunnel-termination-point */
augment "/nw:networks/nw:network/nw:node/tet:te/"
+ "tet:tunnel-termination-point/"
+ "tet:local-link-connectivities" {
description
"Parameters for PSC TE topology.";
uses te-types:performance-metric-container {
if-feature te-performance-metric;
}
}
augment "/nw:networks/nw:network/nw:node/tet:te/"
+ "tet:tunnel-termination-point/"
+ "tet:local-link-connectivities/"
+ "tet:local-link-connectivity" {
description
"Parameters for PSC TE topology.";
uses te-types:performance-metric-container {
if-feature te-performance-metric;
}
Liu, et al. Expires April 25, 2019 [Page 29]
Internet-Draft YANG L3 TE Topology October 2018
}
/* Augmentations to te-link-attributes */
augment "/nw:networks/tet:te/tet:templates/"
+ "tet:link-template/tet:te-link-attributes" {
when "tet:interface-switching-capability "
+ "[tet:switching-capability = 'te-types:switching-psc1']" {
description "Valid only for PSC";
}
description
"Parameters for PSC TE topology.";
uses te-types:performance-metric-container {
if-feature te-performance-metric;
}
}
augment "/nw:networks/nw:network/nt:link/tet:te/"
+ "tet:te-link-attributes" {
when "tet:interface-switching-capability "
+ "[tet:switching-capability = 'te-types:switching-psc1']" {
description "Valid only for PSC";
}
description
"Parameters for PSC TE topology.";
uses te-types:performance-metric-container {
if-feature te-performance-metric;
}
}
augment "/nw:networks/nw:network/nt:link/tet:te/"
+ "tet:information-source-entry" {
when "tet:interface-switching-capability "
+ "[tet:switching-capability = 'te-types:switching-psc1']" {
description "Valid only for PSC";
}
description
"Parameters for PSC TE topology.";
uses te-types:performance-metric-container {
if-feature te-performance-metric;
}
}
/* Augmentations to interface-switching-capability */
augment "/nw:networks/tet:te/tet:templates/"
+ "tet:link-template/tet:te-link-attributes/"
+ "tet:interface-switching-capability" {
when "tet:switching-capability = 'te-types:switching-psc1' " {
description "Valid only for PSC";
Liu, et al. Expires April 25, 2019 [Page 30]
Internet-Draft YANG L3 TE Topology October 2018
}
description
"Parameters for PSC TE topology.";
uses packet-switch-capable-container;
}
augment "/nw:networks/nw:network/nt:link/tet:te/"
+ "tet:te-link-attributes/"
+ "tet:interface-switching-capability" {
when "tet:switching-capability = 'te-types:switching-psc1' " {
description "Valid only for PSC";
}
description
"Parameters for PSC TE topology.";
uses packet-switch-capable-container;
}
augment "/nw:networks/nw:network/nt:link/tet:te/"
+ "tet:information-source-entry/"
+ "tet:interface-switching-capability" {
when "tet:switching-capability = 'te-types:switching-psc1' " {
description "Valid only for PSC";
}
description
"Parameters for PSC TE topology.";
uses packet-switch-capable-container;
}
}
<CODE ENDS>
6. IANA Considerations
RFC Ed.: In this section, replace all occurrences of 'XXXX' with the
actual RFC number (and remove this note).
This document registers the following namespace URIs in the IETF XML
registry [RFC3688]:
--------------------------------------------------------------------
URI: urn:ietf:params:xml:ns:yang:ietf-l3-te-topology
Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace.
--------------------------------------------------------------------
Liu, et al. Expires April 25, 2019 [Page 31]
Internet-Draft YANG L3 TE Topology October 2018
--------------------------------------------------------------------
URI: urn:ietf:params:xml:ns:yang:ietf-l3-te-topology-state
Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace.
--------------------------------------------------------------------
--------------------------------------------------------------------
URI: urn:ietf:params:xml:ns:yang:ietf-te-topology-packet
Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace.
--------------------------------------------------------------------
--------------------------------------------------------------------
URI: urn:ietf:params:xml:ns:yang:ietf-te-topology-packet-state
Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace.
--------------------------------------------------------------------
This document registers the following YANG modules in the YANG Module
Names registry [RFC6020]:
--------------------------------------------------------------------
name: ietf-l3-te-topology
namespace: urn:ietf:params:xml:ns:yang:ietf-l3-te-topology
prefix: l3te
reference: RFC XXXX
--------------------------------------------------------------------
--------------------------------------------------------------------
name: ietf-l3-te-topology-state
namespace: urn:ietf:params:xml:ns:yang:ietf-l3-te-topology-state
prefix: l3te-s
reference: RFC XXXX
--------------------------------------------------------------------
--------------------------------------------------------------------
name: ietf-te-topology-packet
namespace: urn:ietf:params:xml:ns:yang:ietf-te-topology-packet
prefix: tet-pkt
reference: RFC XXXX
--------------------------------------------------------------------
--------------------------------------------------------------------
name: ietf-te-topology-packet-state
namespace: urn:ietf:params:xml:ns:yang:ietf-te-topology-packet-state
prefix: tet-pkt-s
reference: RFC XXXX
--------------------------------------------------------------------
Liu, et al. Expires April 25, 2019 [Page 32]
Internet-Draft YANG L3 TE Topology October 2018
7. Security Considerations
The YANG module specified in this document defines a schema for data
that is designed to be accessed via network management protocols such
as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer
is the secure transport layer, and the mandatory-to-implement secure
transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
is HTTPS, and the mandatory-to-implement secure transport is TLS
[RFC5246].
The NETCONF access control model [RFC6536] provides the means to
restrict access for particular NETCONF or RESTCONF users to a
preconfigured subset of all available NETCONF or RESTCONF protocol
operations and content.
There are a number of data nodes defined in this YANG module that are
writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., edit-config)
to these data nodes without proper protection can have a negative
effect on network operations. These are the subtrees and data nodes
and their sensitivity/vulnerability:
/nw:networks/nw:network/nw:network-types/l3t:l3-unicast-topology/
l3-te
This subtree specifies the layer 3 TE topology type. Modifying
the configurations can make layer 3 TE topology type invalid and
cause interruption to all layer 3 TE networks.
/nw:networks/nw:network/l3t:l3-topology-attributes/l3-te-topology-
attributes
This subtree specifies the topology-wide configurations, including
the reference to a TE topology from a layer 3 network topolopy.
Modifying the configurations here can cause traffic disabled or
rerouted in this topology and the connected topologies.
/nw:networks/nw:network/nw:node/l3t:l3-node-attributes/l3-te-node-
attributes
This subtree specifies the configurations of layer 3 TE nodes.
Modifying the configurations in this subtree can change the
relationship between a TE node and a layer 3 node, causing traffic
disabled or rerouted in the specified nodes and the related layer
3 topologies.
/nw:networks/nw:network/nw:node/nt:termination-point//l3t:l3-
termination-point-attributes/l3-te-tp-attributes
This subtree specifies the configurations of layer 3 TE link
termination points. Modifying the configurations in this subtree
Liu, et al. Expires April 25, 2019 [Page 33]
Internet-Draft YANG L3 TE Topology October 2018
can change the relationship between a TE link termination point
and a layer 3 link termination point, causing traffic disabled or
rerouted on the related layer 3 links and the related layer 3
topologies.
/nw:networks/nw:network/nt:link/l3t:l3-link-attributes/l3-te-link-
attributes
This subtree specifies the configurations of layer 3 TE links.
Modifying the configurations in this subtree can change the
relationship between a TE link and a layer 3 link, causing traffic
disabled or rerouted on the specified layer 3 link and the related
layer 3 topologies.
performance-metric containers
The container "performance-metric" is augmented to multiple
locations of the base TE topology model, as specified in
Section 3.2. Modifying the configuration in such a container can
change the behavours of performance metric monitoring, causing
traffic disabled or rerouted on the related layer 3 links, nodes,
or topologies.
Some of the readable data nodes in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus
important to control read access (e.g., via get, get-config, or
notification) to these data nodes. These are the subtrees and data
nodes and their sensitivity/vulnerability:
/nw:networks/nw:network/nw:network-types/l3t:l3-unicast-topology/
l3-te
Unauthorized access to this subtree can disclose the layer 3 TE
topology type.
/nw:networks/nw:network/l3t:l3-topology-attributes/l3-te-topology-
attributes
Unauthorized access to this subtree can disclose the topology-wide
configurations, including the reference to a TE topology from a
layer 3 network topolopy.
/nw:networks/nw:network/nw:node/l3t:l3-node-attributes/l3-te-node-
attributes
Unauthorized access to this subtree can disclose the operational
state information of layer 3 TE nodes.
/nw:networks/nw:network/nw:node/nt:termination-point//l3t:l3-
termination-point-attributes/l3-te-tp-attributes
Unauthorized access to this subtree can disclose the operational
state information of layer 3 TE link termination points.
Liu, et al. Expires April 25, 2019 [Page 34]
Internet-Draft YANG L3 TE Topology October 2018
/nw:networks/nw:network/nt:link/l3t:l3-link-attributes/l3-te-link-
attributes
Unauthorized access to this subtree can disclose the operational
state information of layer 3 TE links.
performance-metric containers
The container "performance-metric" is augmented to multiple
locations of the base TE topology model, as specified in
Section 3.2. Unauthorized access to this subtree can disclose the
operational state information of performance metric monitoring.
8. References
8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246,
DOI 10.17487/RFC5246, August 2008,
<https://www.rfc-editor.org/info/rfc5246>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/info/rfc6242>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536,
DOI 10.17487/RFC6536, March 2012,
<https://www.rfc-editor.org/info/rfc6536>.
[RFC7471] Giacalone, S., Ward, D., Drake, J., Atlas, A., and S.
Previdi, "OSPF Traffic Engineering (TE) Metric
Extensions", RFC 7471, DOI 10.17487/RFC7471, March 2015,
<https://www.rfc-editor.org/info/rfc7471>.
[RFC7810] Previdi, S., Ed., Giacalone, S., Ward, D., Drake, J., and
Q. Wu, "IS-IS Traffic Engineering (TE) Metric Extensions",
RFC 7810, DOI 10.17487/RFC7810, May 2016,
<https://www.rfc-editor.org/info/rfc7810>.
Liu, et al. Expires April 25, 2019 [Page 35]
Internet-Draft YANG L3 TE Topology October 2018
[RFC7823] Atlas, A., Drake, J., Giacalone, S., and S. Previdi,
"Performance-Based Path Selection for Explicitly Routed
Label Switched Paths (LSPs) Using TE Metric Extensions",
RFC 7823, DOI 10.17487/RFC7823, May 2016,
<https://www.rfc-editor.org/info/rfc7823>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>.
[RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger,
"Common YANG Data Types for the Routing Area", RFC 8294,
DOI 10.17487/RFC8294, December 2017,
<https://www.rfc-editor.org/info/rfc8294>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>.
[RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N.,
Ananthakrishnan, H., and X. Liu, "A YANG Data Model for
Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March
2018, <https://www.rfc-editor.org/info/rfc8345>.
[RFC8346] Clemm, A., Medved, J., Varga, R., Liu, X.,
Ananthakrishnan, H., and N. Bahadur, "A YANG Data Model
for Layer 3 Topologies", RFC 8346, DOI 10.17487/RFC8346,
March 2018, <https://www.rfc-editor.org/info/rfc8346>.
[I-D.ietf-teas-yang-te]
Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., and
I. Bryskin, "A YANG Data Model for Traffic Engineering
Tunnels and Interfaces", draft-ietf-teas-yang-te-16 (work
in progress), July 2018.
[I-D.ietf-teas-yang-te-topo]
Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and
O. Dios, "YANG Data Model for Traffic Engineering (TE)
Topologies", draft-ietf-teas-yang-te-topo-18 (work in
progress), June 2018.
Liu, et al. Expires April 25, 2019 [Page 36]
Internet-Draft YANG L3 TE Topology October 2018
8.2. Informative References
[RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG",
RFC 7951, DOI 10.17487/RFC7951, August 2016,
<https://www.rfc-editor.org/info/rfc7951>.
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>.
Liu, et al. Expires April 25, 2019 [Page 37]
Internet-Draft YANG L3 TE Topology October 2018
Appendix A. Companion YANG Model for Non-NMDA Compliant Implementations
The YANG modules ietf-l3-te-topology and ietf-te-topology-packet
defined in this document are designed to be used in conjunction with
implementations that support the Network Management Datastore
Architecture (NMDA) defined in [RFC8342]. In order to allow
implementations to use the model even in cases when NMDA is not
supported, the following companion modules, ietf-l3-te-topology-state
and ietf-te-topology-packet-state, are defined as state models, which
mirror the modules ietf-l3-te-topology and ietf-te-topology-packet
defined earlier in this document. However, all data nodes in the
companion module are non-configurable, to represent the applied
configuration or the derived operational states.
The companion modules, ietf-l3-te-topology-state and ietf-te-
topology-packet-state, are redundant and SHOULD NOT be supported by
implementations that support NMDA.
As the structure of the companion modules mirrors that of the
coorespinding NMDA models, the YANG trees of the companion modules
are not depicted separately.
A.1. Layer 3 TE Topology State Module
This module references [RFC8345], and [RFC8346].
<CODE BEGINS> file "ietf-l3-te-topology-state@2018-06-22.yang"
module ietf-l3-te-topology-state {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-l3-te-topology-state";
prefix "l3tet-s";
import ietf-l3-te-topology {
prefix "l3tet";
}
import ietf-network-state {
prefix "nw-s";
reference "RFC 8345: A YANG Data Model for Network Topologies";
}
import ietf-network-topology-state {
prefix "nt-s";
reference "RFC 8345: A YANG Data Model for Network Topologies";
}
import ietf-l3-unicast-topology-state {
prefix "l3t-s";
reference "RFC 8346: A YANG Data Model for Layer 3 Topologies";
}
Liu, et al. Expires April 25, 2019 [Page 38]
Internet-Draft YANG L3 TE Topology October 2018
organization
"IETF Traffic Engineering Architecture and Signaling (TEAS)
Working Group";
contact
"WG Web: <http://tools.ietf.org/wg/teas/>
WG List: <mailto:teas@ietf.org>
Editor: Xufeng Liu
<mailto:xufeng.liu.ietf@gmail.com>
Editor: Igor Bryskin
<mailto:Igor.Bryskin@huawei.com>
Editor: Vishnu Pavan Beeram
<mailto:vbeeram@juniper.net>
Editor: Tarek Saad
<mailto:tsaad@cisco.com>
Editor: Himanshu Shah
<mailto:hshah@ciena.com>
Editor: Oscar Gonzalez De Dios
<mailto:oscar.gonzalezdedios@telefonica.com>";
description
"YANG data model for representing operational state information
of Layer 3 TE Topologies, when NMDA is not supported.
Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the
RFC itself for full legal notices.";
revision 2018-06-22 {
description "Initial revision";
reference "RFC XXXX: YANG Data Model for Layer 3 TE Topologies";
}
Liu, et al. Expires April 25, 2019 [Page 39]
Internet-Draft YANG L3 TE Topology October 2018
augment "/nw-s:networks/nw-s:network/nw-s:network-types/"
+ "l3t-s:l3-unicast-topology" {
description
"Defines the L3 TE topology type.";
uses l3tet:l3-te-topology-type;
}
augment "/nw-s:networks/nw-s:network/"
+ "l3t-s:l3-topology-attributes" {
when "../nw-s:network-types/l3t-s:l3-unicast-topology/"
+ "l3tet-s:l3-te" {
description "Augment only for L3 TE topology";
}
description "Augment topology configuration";
uses l3tet:l3-te-topology-attributes;
}
augment "/nw-s:networks/nw-s:network/nw-s:node/"
+ "l3t-s:l3-node-attributes" {
when "../../nw-s:network-types/l3t-s:l3-unicast-topology/"
+ "l3tet-s:l3-te" {
description "Augment only for L3 TE topology";
}
description "Augment node configuration";
uses l3tet:l3-te-node-attributes;
}
augment "/nw-s:networks/nw-s:network/nw-s:node/"
+ "nt-s:termination-point/"
+ "l3t-s:l3-termination-point-attributes" {
when "../../../nw-s:network-types/l3t-s:l3-unicast-topology/"
+ "l3tet-s:l3-te" {
description "Augment only for L3 TE topology";
}
description "Augment termination point configuration";
uses l3tet:l3-te-tp-attributes;
}
augment "/nw-s:networks/nw-s:network/nt-s:link/"
+ "l3t-s:l3-link-attributes" {
when "../../nw-s:network-types/l3t-s:l3-unicast-topology/"
+ "l3tet-s:l3-te" {
description "Augment only for L3 TE topology";
}
description "Augment link configuration";
uses l3tet:l3-te-link-attributes;
}
}
Liu, et al. Expires April 25, 2019 [Page 40]
Internet-Draft YANG L3 TE Topology October 2018
<CODE ENDS>
A.2. Packet Switching TE Topology State Module
<CODE BEGINS> file "ietf-te-topology-packet-state@2018-06-22.yang"
module ietf-te-topology-packet-state {
yang-version 1.1;
namespace
"urn:ietf:params:xml:ns:yang:ietf-te-topology-packet-state";
prefix "tet-pkt-s";
import ietf-te-topology-packet {
prefix "tet-pkt";
}
import ietf-network-state {
prefix "nw-s";
reference "RFC 8345: A YANG Data Model for Network Topologies";
}
import ietf-network-topology-state {
prefix "nt-s";
reference "RFC 8345: A YANG Data Model for Network Topologies";
}
import ietf-te-topology-state {
prefix "tet-s";
reference
"I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic
Engineering (TE) Topologies";
}
import ietf-te-types {
prefix "te-types";
reference
"I-D.ietf-teas-yang-te: A YANG Data Model for Traffic
Engineering Tunnels and Interfaces";
}
organization
"Traffic Engineering Architecture and Signaling (TEAS)
Working Group";
contact
Liu, et al. Expires April 25, 2019 [Page 41]
Internet-Draft YANG L3 TE Topology October 2018
"WG Web: <http://tools.ietf.org/wg/teas/>
WG List: <mailto:teas@ietf.org>
Editor: Xufeng Liu
<mailto:xufeng.liu.ietf@gmail.com>
Editor: Igor Bryskin
<mailto:Igor.Bryskin@huawei.com>
Editor: Vishnu Pavan Beeram
<mailto:vbeeram@juniper.net>
Editor: Tarek Saad
<mailto:tsaad@cisco.com>
Editor: Himanshu Shah
<mailto:hshah@ciena.com>
Editor: Oscar Gonzalez De Dios
<mailto:oscar.gonzalezdedios@telefonica.com>";
description
"YANG data model for representing operational state information
of PSC (Packet Switching) TE Topologies, when NMDA is not
supported.
Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the
RFC itself for full legal notices.";
revision 2018-06-22 {
description "Initial revision";
reference "RFC XXXX: YANG Data Model for Layer 3 TE Topologies";
}
/*
* Augmentations
*/
/* Augmentations to connectivity-matrix */
Liu, et al. Expires April 25, 2019 [Page 42]
Internet-Draft YANG L3 TE Topology October 2018
augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/"
+ "tet-s:te-node-attributes/tet-s:connectivity-matrices" {
description
"Parameters for PSC (Packet Switching) TE topology.";
uses te-types:performance-metric-container {
if-feature tet-pkt:te-performance-metric;
}
}
augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/"
+ "tet-s:te-node-attributes/tet-s:connectivity-matrices/"
+ "tet-s:connectivity-matrix" {
description
"Parameters for PSC TE topology.";
uses te-types:performance-metric-container {
if-feature tet-pkt:te-performance-metric;
}
}
augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/"
+ "tet-s:information-source-entry/"
+ "tet-s:connectivity-matrices" {
description
"Parameters for PSC TE topology.";
uses te-types:performance-metric-container {
if-feature tet-pkt:te-performance-metric;
}
}
augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/"
+ "tet-s:information-source-entry/"
+ "tet-s:connectivity-matrices/"
+ "tet-s:connectivity-matrix" {
description
"Parameters for PSC TE topology.";
uses te-types:performance-metric-container {
if-feature tet-pkt:te-performance-metric;
}
}
/* Augmentations to tunnel-termination-point */
augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/"
+ "tet-s:tunnel-termination-point/"
+ "tet-s:local-link-connectivities" {
description
"Parameters for PSC TE topology.";
uses te-types:performance-metric-container {
if-feature tet-pkt:te-performance-metric;
Liu, et al. Expires April 25, 2019 [Page 43]
Internet-Draft YANG L3 TE Topology October 2018
}
}
augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/"
+ "tet-s:tunnel-termination-point/"
+ "tet-s:local-link-connectivities/"
+ "tet-s:local-link-connectivity" {
description
"Parameters for PSC TE topology.";
uses te-types:performance-metric-container {
if-feature tet-pkt:te-performance-metric;
}
}
/* Augmentations to te-link-attributes */
augment "/nw-s:networks/tet-s:te/tet-s:templates/"
+ "tet-s:link-template/tet-s:te-link-attributes" {
when "tet-s:interface-switching-capability "
+ "[tet-s:switching-capability = 'te-types:switching-psc1']" {
description "Valid only for PSC";
}
description
"Parameters for PSC TE topology.";
uses te-types:performance-metric-container {
if-feature tet-pkt:te-performance-metric;
}
}
augment "/nw-s:networks/nw-s:network/nt-s:link/tet-s:te/"
+ "tet-s:te-link-attributes" {
when "tet-s:interface-switching-capability "
+ "[tet-s:switching-capability = 'te-types:switching-psc1']" {
description "Valid only for PSC";
}
description
"Parameters for PSC TE topology.";
uses te-types:performance-metric-container {
if-feature tet-pkt:te-performance-metric;
}
}
augment "/nw-s:networks/nw-s:network/nt-s:link/tet-s:te/"
+ "tet-s:information-source-entry" {
when "tet-s:interface-switching-capability "
+ "[tet-s:switching-capability = 'te-types:switching-psc1']" {
description "Valid only for PSC";
}
description
Liu, et al. Expires April 25, 2019 [Page 44]
Internet-Draft YANG L3 TE Topology October 2018
"Parameters for PSC TE topology.";
uses te-types:performance-metric-container {
if-feature tet-pkt:te-performance-metric;
}
}
/* Augmentations to interface-switching-capability */
augment "/nw-s:networks/tet-s:te/tet-s:templates/"
+ "tet-s:link-template/tet-s:te-link-attributes/"
+ "tet-s:interface-switching-capability" {
when "tet-s:switching-capability = 'te-types:switching-psc1' " {
description "Valid only for PSC";
}
description
"Parameters for PSC TE topology.";
uses tet-pkt:packet-switch-capable-container;
}
augment "/nw-s:networks/nw-s:network/nt-s:link/tet-s:te/"
+ "tet-s:te-link-attributes/"
+ "tet-s:interface-switching-capability" {
when "tet-s:switching-capability = 'te-types:switching-psc1' " {
description "Valid only for PSC";
}
description
"Parameters for PSC TE topology.";
uses tet-pkt:packet-switch-capable-container;
}
augment "/nw-s:networks/nw-s:network/nt-s:link/tet-s:te/"
+ "tet-s:information-source-entry/"
+ "tet-s:interface-switching-capability" {
when "tet-s:switching-capability = 'te-types:switching-psc1' " {
description "Valid only for PSC";
}
description
"Parameters for PSC TE topology.";
uses tet-pkt:packet-switch-capable-container;
}
}
<CODE ENDS>
Liu, et al. Expires April 25, 2019 [Page 45]
Internet-Draft YANG L3 TE Topology October 2018
Appendix B. Data Tree Example
This section contains an example of an instance data tree in the JSON
encoding [RFC7951]. The example instantiates "ietf-l3-te-topology"
for the topology that is depicted in the following diagram.
+------------+ +------------+
| D1 | | D2 |
/-\ /-\ (TE) /-\ /-\
| | 1-0-1 | |---------------->| | 2-1-1 | |
| | 1-2-1 | |<----------------| | 2-0-1 | |
\-/ 1-3-1 \-/ (TE) \-/ 2-3-1 \-/
| /----\ | | /----\ |
+---| |---+ +---| |---+
\----/ \----/
A | A |
(TE)| |(TE) (Non-TE)| |(Non-TE)
| | | |
| | +------------+ | |
| | | D3 | | |
| | /-\ /-\ | |
| +----->| | 3-1-1 | |-------+ |
+---------| | 3-2-1 | |<---------+
\-/ \-/
| |
+------------+
The corresponding instance data tree is depicted below. Note that
some lines have been wrapped to adhere to the 72-character line
limitation of RFCs.
{
"ietf-network:networks": {
"network": [
{
"network-types": {
"ietf-te-topology:te-topology": {}
},
"network-id": "example-topo-te",
"ietf-te-topology:provider-id": 200,
"ietf-te-topology:client-id": 300,
"ietf-te-topology:te-topology-id": "example-topo-te",
"ietf-te-topology:te": {
},
"node": [
{
Liu, et al. Expires April 25, 2019 [Page 46]
Internet-Draft YANG L3 TE Topology October 2018
"node-id": "D1",
"ietf-te-topology:te-node-id": "2.0.1.1",
"ietf-te-topology:te": {
"te-node-attributes": {
}
},
"ietf-network-topology:termination-point": [
{
"tp-id": "1-2-1",
"ietf-te-topology:te-tp-id": 10201,
"ietf-te-topology:te": {
"interface-switching-capability": [
{
"switching-capability": "switching-psc1",
"encoding": "lsp-encoding-ethernet"
}
]
}
},
{
"tp-id": "1-3-1",
"ietf-te-topology:te-tp-id": 10301,
"ietf-te-topology:te": {
"interface-switching-capability": [
{
"switching-capability": "switching-psc1",
"encoding": "lsp-encoding-ethernet"
}
]
}
}
]
},
{
"node-id": "D2",
"ietf-te-topology:te-node-id": "2.0.2.1",
"ietf-te-topology:te": {
"te-node-attributes": {
}
},
"ietf-network-topology:termination-point": [
{
"tp-id": "2-1-1",
"ietf-te-topology:te-tp-id": 20101,
"ietf-te-topology:te": {
"interface-switching-capability": [
{
"switching-capability": "switching-psc1",
Liu, et al. Expires April 25, 2019 [Page 47]
Internet-Draft YANG L3 TE Topology October 2018
"encoding": "lsp-encoding-ethernet"
}
]
}
}
]
},
{
"node-id": "D3",
"ietf-te-topology:te-node-id": "2.0.3.1",
"ietf-te-topology:te": {
"te-node-attributes": {
}
},
"ietf-network-topology:termination-point": [
{
"tp-id": "3-1-1",
"ietf-te-topology:te-tp-id": 30101,
"ietf-te-topology:te": {
"interface-switching-capability": [
{
"switching-capability": "switching-psc1",
"encoding": "lsp-encoding-ethernet"
}
]
}
}
]
}
],
"ietf-network-topology:link": [
{
"link-id": "D1,1-2-1,D2,2-1-1",
"source": {
"source-node": "D1",
"source-tp": "1-2-1"
},
"destination": {
"dest-node": "D2",
"dest-tp": "2-1-1"
},
"ietf-te-topology:te": {
"te-link-attributes": {
"interface-switching-capability": [
{
"switching-capability": "switching-psc1",
"encoding": "lsp-encoding-ethernet"
}
Liu, et al. Expires April 25, 2019 [Page 48]
Internet-Draft YANG L3 TE Topology October 2018
],
"max-link-bandwidth": {
"te-bandwidth": {
"generic": "0x1p+18"
}
},
"te-default-metric": 100
}
}
},
{
"link-id": "D2,2-1-1,D1,1-2-1",
"source": {
"source-node": "D2",
"source-tp": "2-1-1"
},
"destination": {
"dest-node": "D1",
"dest-tp": "1-2-1"
},
"ietf-te-topology:te": {
"te-link-attributes": {
"interface-switching-capability": [
{
"switching-capability": "switching-psc1",
"encoding": "lsp-encoding-ethernet"
}
],
"max-link-bandwidth": {
"te-bandwidth": {
"generic": "0x1p+18"
}
},
"te-default-metric": 100
}
}
},
{
"link-id": "D1,1-3-1,D3,3-1-1",
"source": {
"source-node": "D1",
"source-tp": "1-3-1"
},
"destination": {
"dest-node": "D3",
"dest-tp": "3-1-1"
},
"ietf-te-topology:te": {
Liu, et al. Expires April 25, 2019 [Page 49]
Internet-Draft YANG L3 TE Topology October 2018
"te-link-attributes": {
"interface-switching-capability": [
{
"switching-capability": "switching-psc1",
"encoding": "lsp-encoding-ethernet"
}
],
"max-link-bandwidth": {
"te-bandwidth": {
"generic": "0x1p+18"
}
},
"te-default-metric": 100
}
}
},
{
"link-id": "D3,3-1-1,D1,1-3-1",
"source": {
"source-node": "D3",
"source-tp": "3-1-1"
},
"destination": {
"dest-node": "D1",
"dest-tp": "1-3-1"
},
"ietf-te-topology:te": {
"te-link-attributes": {
"interface-switching-capability": [
{
"switching-capability": "switching-psc1",
"encoding": "lsp-encoding-ethernet"
}
],
"max-link-bandwidth": {
"te-bandwidth": {
"generic": "0x1p+18"
}
},
"te-default-metric": 100
}
}
}
]
},
{
"network-types": {
"ietf-l3-unicast-topology:l3-unicast-topology": {
Liu, et al. Expires April 25, 2019 [Page 50]
Internet-Draft YANG L3 TE Topology October 2018
"ietf-l3-te-topology:l3-te": {}
}
},
"network-id": "example-topo-l3-te",
"ietf-l3-unicast-topology:l3-topology-attributes": {
"ietf-l3-te-topology:l3-te-topology-attributes": {
"network-ref": "example-topo-te"
}
},
"node": [
{
"node-id": "D1",
"ietf-network-topology:termination-point": [
{
"tp-id": "1-0-1",
"ietf-l3-unicast-topology:l3-termination-point-attributes": {
"unnumbered-id": 101
}
},
{
"tp-id": "1-2-1",
"ietf-l3-unicast-topology:l3-termination-point-attributes": {
"unnumbered-id": 121,
"ietf-l3-te-topology:l3-te-tp-attributes": {
"tp-ref": "1-2-1"
}
}
},
{
"tp-id": "1-3-1",
"ietf-l3-unicast-topology:l3-termination-point-attributes": {
"unnumbered-id": 131,
"ietf-l3-te-topology:l3-te-tp-attributes": {
"tp-ref": "1-3-1"
}
}
}
],
"ietf-l3-unicast-topology:l3-node-attributes": {
"router-id": ["203.0.113.1"],
"prefix": [
{
"prefix": "203.0.113.1/32"
}
],
"ietf-l3-te-topology:l3-te-node-attributes": {
"node-ref": "D1"
}
Liu, et al. Expires April 25, 2019 [Page 51]
Internet-Draft YANG L3 TE Topology October 2018
}
},
{
"node-id": "D2",
"ietf-network-topology:termination-point": [
{
"tp-id": "2-0-1",
"ietf-l3-unicast-topology:l3-termination-point-attributes": {
"unnumbered-id": 201
}
},
{
"tp-id": "2-1-1",
"ietf-l3-unicast-topology:l3-termination-point-attributes": {
"unnumbered-id": 211,
"ietf-l3-te-topology:l3-te-tp-attributes": {
"tp-ref": "2-1-1"
}
}
},
{
"tp-id": "2-3-1",
"ietf-l3-unicast-topology:l3-termination-point-attributes": {
"unnumbered-id": 231
}
}
],
"ietf-l3-unicast-topology:l3-node-attributes": {
"router-id": ["203.0.113.2"],
"prefix": [
{
"prefix": "203.0.113.2/32"
}
],
"ietf-l3-te-topology:l3-te-node-attributes": {
"node-ref": "D2"
}
}
},
{
"node-id": "D3",
"ietf-network-topology:termination-point": [
{
"tp-id": "3-1-1",
"ietf-l3-unicast-topology:l3-termination-point-attributes": {
"unnumbered-id": 311,
"ietf-l3-te-topology:l3-te-tp-attributes": {
"tp-ref": "3-1-1"
Liu, et al. Expires April 25, 2019 [Page 52]
Internet-Draft YANG L3 TE Topology October 2018
}
}
},
{
"tp-id": "3-2-1",
"ietf-l3-unicast-topology:l3-termination-point-attributes": {
"unnumbered-id": 321
}
}
],
"ietf-l3-unicast-topology:l3-node-attributes": {
"router-id": ["203.0.113.3"],
"prefix": [
{
"prefix": "203.0.113.3/32"
}
],
"ietf-l3-te-topology:l3-te-node-attributes": {
"node-ref": "D3"
}
}
}
],
"ietf-network-topology:link": [
{
"link-id": "D1,1-2-1,D2,2-1-1",
"source": {
"source-node": "D1",
"source-tp": "1-2-1"
},
"destination": {
"dest-node": "D2",
"dest-tp": "2-1-1"
},
"ietf-l3-unicast-topology:l3-link-attributes": {
"metric1": "100",
"ietf-l3-te-topology:l3-te-link-attributes": {
"link-ref": "D1,1-2-1,D2,2-1-1"
}
}
},
{
"link-id": "D2,2-1-1,D1,1-2-1",
"source": {
"source-node": "D2",
"source-tp": "2-1-1"
},
"destination": {
Liu, et al. Expires April 25, 2019 [Page 53]
Internet-Draft YANG L3 TE Topology October 2018
"dest-node": "D1",
"dest-tp": "1-2-1"
},
"ietf-l3-unicast-topology:l3-link-attributes": {
"metric1": "100",
"ietf-l3-te-topology:l3-te-link-attributes": {
"link-ref": "D2,2-1-1,D1,1-2-1"
}
}
},
{
"link-id": "D1,1-3-1,D3,3-1-1",
"source": {
"source-node": "D1",
"source-tp": "1-3-1"
},
"destination": {
"dest-node": "D3",
"dest-tp": "3-1-1"
},
"ietf-l3-unicast-topology:l3-link-attributes": {
"metric1": "100",
"ietf-l3-te-topology:l3-te-link-attributes": {
"link-ref": "D1,1-3-1,D3,3-1-1"
}
}
},
{
"link-id": "D3,3-1-1,D1,1-3-1",
"source": {
"source-node": "D3",
"source-tp": "3-1-1"
},
"destination": {
"dest-node": "D1",
"dest-tp": "1-3-1"
},
"ietf-l3-unicast-topology:l3-link-attributes": {
"metric1": "100",
"ietf-l3-te-topology:l3-te-link-attributes": {
"link-ref": "D3,3-1-1,D1,1-3-1"
}
}
},
{
"link-id": "D2,2-3-1,D3,3-2-1",
"source": {
"source-node": "D2",
Liu, et al. Expires April 25, 2019 [Page 54]
Internet-Draft YANG L3 TE Topology October 2018
"source-tp": "2-3-1"
},
"destination": {
"dest-node": "D3",
"dest-tp": "3-2-1"
},
"ietf-l3-unicast-topology:l3-link-attributes": {
"metric1": "100"
}
},
{
"link-id": "D3,3-2-1,D2,2-3-1",
"source": {
"source-node": "D3",
"source-tp": "3-2-1"
},
"destination": {
"dest-node": "D2",
"dest-tp": "2-3-1"
},
"ietf-l3-unicast-topology:l3-link-attributes": {
"metric1": "100"
}
}
]
}
]
}
}
Authors' Addresses
Xufeng Liu
Volta Networks
EMail: xufeng.liu.ietf@gmail.com
Igor Bryskin
Huawei Technologies
EMail: Igor.Bryskin@huawei.com
Liu, et al. Expires April 25, 2019 [Page 55]
Internet-Draft YANG L3 TE Topology October 2018
Vishnu Pavan Beeram
Juniper Networks
EMail: vbeeram@juniper.net
Tarek Saad
Cisco Systems Inc
EMail: tsaad@cisco.com
Himanshu Shah
Ciena
EMail: hshah@ciena.com
Oscar Gonzalez de Dios
Telefonica
EMail: oscar.gonzalezdedios@telefonica.com
Liu, et al. Expires April 25, 2019 [Page 56]