idnits 2.17.1 draft-ietf-teas-yang-l3-te-topo-11.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC8776, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 12, 2021) is 1018 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Downref: Normative reference to an Informational RFC: RFC 2697 ** Downref: Normative reference to an Informational RFC: RFC 2698 ** Downref: Normative reference to an Informational RFC: RFC 4115 ** Downref: Normative reference to an Experimental RFC: RFC 4125 ** Downref: Normative reference to an Experimental RFC: RFC 4126 ** Downref: Normative reference to an Experimental RFC: RFC 4127 ** Downref: Normative reference to an Informational RFC: RFC 5481 == Outdated reference: A later version (-04) exists of draft-ietf-teas-yang-te-mpls-03 Summary: 7 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group X. Liu 3 Internet-Draft Volta Networks 4 Updates: 8776 (if approved) I. Bryskin 5 Intended status: Standards Track Individual 6 Expires: January 13, 2022 V. Beeram 7 T. Saad 8 Juniper Networks 9 H. Shah 10 Ciena 11 O. Gonzalez de Dios 12 Telefonica 13 July 12, 2021 15 YANG Data Model for Layer 3 TE Topologies 16 draft-ietf-teas-yang-l3-te-topo-11 18 Abstract 20 This document defines a YANG data model for layer 3 traffic 21 engineering topologies. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at https://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on January 13, 2022. 40 Copyright Notice 42 Copyright (c) 2021 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (https://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 58 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 59 1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3 60 2. Modeling Considerations for L3 TE Topologies . . . . . . . . 4 61 2.1. Relationship Between Layer 3 Unicast Topology and TE 62 topology . . . . . . . . . . . . . . . . . . . . . . . . 5 63 2.2. Relationship Modeling . . . . . . . . . . . . . . . . . . 6 64 2.2.1. Topology Referencing . . . . . . . . . . . . . . . . 6 65 2.2.2. Node Referencing . . . . . . . . . . . . . . . . . . 7 66 2.2.3. Link Termination Point Referencing . . . . . . . . . 8 67 2.2.4. Link Referencing . . . . . . . . . . . . . . . . . . 8 68 2.3. Topology Type Modeling . . . . . . . . . . . . . . . . . 8 69 3. Packet TE YANG Types . . . . . . . . . . . . . . . . . . . . 8 70 4. Packet Switching Technology Extensions to TE Topologies . . . 10 71 4.1. Technology Specific Link Attributes . . . . . . . . . . . 10 72 4.2. Performance Metric . . . . . . . . . . . . . . . . . . . 10 73 5. Complete Model Tree Structure . . . . . . . . . . . . . . . . 11 74 5.1. Layer 3 TE Topology Module . . . . . . . . . . . . . . . 11 75 5.2. Packet Switching TE Topology Module . . . . . . . . . . . 12 76 5.2.1. Network Types . . . . . . . . . . . . . . . . . . . . 12 77 5.2.2. Node Connectivity Matrix Attributes . . . . . . . . . 12 78 5.2.3. Node Information Source . . . . . . . . . . . . . . . 16 79 5.2.4. Node Local Link Connectivity . . . . . . . . . . . . 21 80 5.2.5. Link Template for Performance Metrics . . . . . . . . 25 81 5.2.6. Link for Performance Metrics . . . . . . . . . . . . 28 82 5.2.7. Link Information Source for Performance Metrics . . . 30 83 5.2.8. Link Template for Packet-specific Attributes . . . . 32 84 5.2.9. Link for Packet-specific Attributes . . . . . . . . . 32 85 5.2.10. Link Information Source for Packet-specific 86 Attributes . . . . . . . . . . . . . . . . . . . . . 33 87 5.2.11. TE Bandwidth for Packet-specific Technologies . . . . 33 88 6. YANG Modules . . . . . . . . . . . . . . . . . . . . . . . . 36 89 6.1. Layer 3 TE Topology Module . . . . . . . . . . . . . . . 36 90 6.2. Packet TE YANG Types Module . . . . . . . . . . . . . . . 40 91 6.3. Packet Switching TE Topology Module . . . . . . . . . . . 53 92 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 69 93 8. Security Considerations . . . . . . . . . . . . . . . . . . . 70 94 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 72 95 9.1. Normative References . . . . . . . . . . . . . . . . . . 72 96 9.2. Informative References . . . . . . . . . . . . . . . . . 75 98 Appendix A. Companion YANG Model for Non-NMDA Compliant 99 Implementations . . . . . . . . . . . . . . . . . . 76 100 A.1. Layer 3 TE Topology State Module . . . . . . . . . . . . 76 101 A.2. Packet Switching TE Topology State Module . . . . . . . . 79 102 Appendix B. Data Tree Example . . . . . . . . . . . . . . . . . 86 103 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 96 105 1. Introduction 107 This document defines a YANG [RFC7950] data model for describing the 108 relationship between a layer 3 unicast topology [RFC8346] and a 109 Traffic Engineering (TE) topology [RFC8795]. 111 When traffic engineering is enabled on a layer 3 unicast topology, 112 there will be a corresponding TE topology. The TE topology may or 113 may not be congruent with the layer 3 unicast topology. When such a 114 congruent TE topology exists, there will be a one-to-one association 115 between the one modeling element in the layer 3 unicast topology and 116 another element in the TE topology. When such a congruent TE 117 topology does not exist, the association will not be one-to-one. 118 This YANG data model supports both cases. 120 1.1. Terminology 122 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 123 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 124 "OPTIONAL" in this document are to be interpreted as described in BCP 125 14, [RFC2119] [RFC8174] when, and only when, they appear in all 126 capitals, as shown here. 128 The following terms are defined in [RFC7950] and are not redefined 129 here: 131 o augment 133 o data model 135 o data node 137 1.2. Tree Diagrams 139 Tree diagrams used in this document follow the notation defined in 140 [RFC8340]. 142 2. Modeling Considerations for L3 TE Topologies 144 A layer 3 TE topology is a layer 3 unicast topology with additional 145 TE capabilities enabled. [RFC8346] defines a YANG data model for 146 layer 3 unicast topologies, consisting of two modules: ietf-l3- 147 unicast-topology and ietf-l3-unicast-topology-state. The YANG data 148 model defined in this document augments the YANG data model defined 149 in [RFC8346]. This document specifies two YANG modules ietf-l3-te- 150 topology and ietf-l3-te-topology-state, augmenting ietf-l3-unicast- 151 topology and ietf-l3-unicast-topology-state respectively, to add 152 additional TE capabilities. Such an augmentation relationship is 153 shown in Figure 1 below. 155 +-------------------------+ 156 | Network Topology | 157 | ietf-network-topology | Defined in RFC 8345 158 +------------^------------+ 159 | 160 | augments 161 | (An "inheritance" relation) 162 | 163 +-------------^-------------+ 164 | Layer 3 Unicast Topology | 165 | ietf-l3-unicast-topology | Defined in RFC 8346 166 +-------------^-------------+ 167 | 168 | augments 169 | (An "inheritance" relation) 170 | 171 +------------^------------+ 172 | Layer 3 TE Topology | 173 | ietf-l3-te-topology | Defined in this document 174 +-------------------------+ 176 Figure 1: L3 TE Model Augmentation 178 Additionally, this document specifies two more YANG modules ietf-te- 179 topology-packet and ietf-te-topology-packet-state, augmenting ietf- 180 te-topology and ietf-te-topology-state respectively, to add 181 additional attributes for TE packet data networks, as shown in 182 Figure 2. Section 3 of this document describes these additional 183 attributes in further details. 185 +-------------------------+ 186 | Network Topology | 187 | ietf-network-topology | Defined in RFC 8345 188 +------------^------------+ 189 | 190 | augments 191 | (An "inheritance" relation) 192 | 193 +------------^------------+ 194 | TE Topology | 195 | ietf-te-topology | Defined in RFC 8795 196 +------------^------------+ 197 | 198 | augments 199 | (An "inheritance" relation) 200 | 201 +------------^------------+ 202 | TE Packet Topology | 203 | ietf-te-topology-packet | Defined in this document 204 +-------------------------+ 206 Figure 2: TE Packet Model Augmentation 208 2.1. Relationship Between Layer 3 Unicast Topology and TE topology 210 In general, the layer 3 unicast topology model specified in [RFC8346] 211 and the TE topology model specified in [RFC8795] can be used 212 independently. This document provides a method to use both together. 214 When traffic engineering is enabled on a layer 3 unicast topology, 215 there will be a resulting layer 3 TE topology, which is modeled by 216 the YANG modules defined in this document. A layer 3 TE topology 217 augments a layer 3 unicast topology, so it inherits all the objects 218 and properties of the base layer 3 unicast topology. In addition, in 219 such a layer 3 TE topology, the objects that are inherited from the 220 base layer 3 unicast topology to this layer 3 TE topology may be 221 associated with the objects in one corresponding TE topology. Such 222 associations are supported by the module ietf-l3-te-topology defined 223 in this document. 225 +----------------------------+ +----------------------+ 226 | Layer 3 Topology | | TE Topology | 227 | ietf-l3-unicast-topology | | ietf-te-topology | 228 +--------------^-------------+ +----------------------+ 229 | A 230 | augments | 231 | / 232 | / references by "leafref" 233 +------------^-----------+ / (An "association" relation) 234 | Layer 3 TE Topology |__/ 235 | ietf-l3-te-topology | 236 +------------------------+ 238 Figure 3: Model References 240 The properties of the relations between the objects in a layer 3 TE 241 topology and the objects in the corresponding TE topology are: 243 o The associations are between objects of the same class, i.e. node 244 to node or link to link. 246 o The multiplicity of such an association is: 0..1 to 0..1. An 247 object in a layer 3 TE topology modeled by ietf-l3-te-topology may 248 be associated with zero or one object in the corresponding TE 249 topology. 251 2.2. Relationship Modeling 253 YANG data type leafref is used to model the association relationship 254 between a layer 3 TE topology and a TE topology. YANG "must" 255 statements are used to enforce that the referenced objects are in a 256 topology of the proper type. 258 2.2.1. Topology Referencing 260 When TE is enabled on a layer 3 unicast topology, if the TE topology 261 is not congruent with the layer 3 unicast topology, the layer 3 TE 262 topology will have a reference to the corresponding TE topology. 263 Such a reference is modeled as follows: 265 augment /nw:networks/nw:network/l3t:l3-topology-attributes: 266 +--rw l3-te-topology-attributes 267 +--rw network-ref? -> /nw:networks/network/network-id 269 The above network-ref is a YANG data node of type leafref, used to 270 indicate the network-id of the corresponding TE topology. The 271 leafref relationship is illustrated by the simplified data instances 272 in the following diagram. 274 +-------------------------------+ +--------------------------+ 275 | ietf-l3-te-topology: | | ietf-te-topology: | 276 |+-----------------------------+| |+------------------------+| 277 || ietf-l3-unicast-topology: || || ietf-network-topology: || 278 ||+---------------------------+|| +-->|| network-id (key) || 279 ||| ietf-network-topology: ||| | || network-types: { || 280 ||| network-id (key) ||| | || te-topology || 281 ||| network-types: { ||| | || } || 282 ||| l3-unicast-topology: {||| | || || 283 ||| l3-te ||| | |+------------------------+| 284 ||| } ||| | | | 285 ||| } ||| | +--------------------------+ 286 ||| ||| | 287 ||+---------------------------+|| | 288 || || | 289 |+-----------------------------+| | 290 | network-ref |--+ 291 +-------------------------------+ 293 Figure 4: Topology Referencing 295 network-id defined in in [RFC8345] uniquely identifies a network 296 topology instance of any type. As shown in the above diagram, the 297 value of network-ref in the ietf-l3-te-topology instance matches the 298 value of network-id in the ietf-te-topology instance. To ensure that 299 the topology instance identified by this network-id is of type "te- 300 topology", a "must" statement is defined in module ietf-l3-te- 301 topology. Such "must" statements are also used in all the following 302 leafref nodes in this section. 304 If the TE topology is congruent with the layer 3 unicast topology, 305 the above reference can still be used to specified TE parameters 306 defined in the TE topology model. 308 2.2.2. Node Referencing 310 When TE is enabled on a layer 3 unicast topology, if the TE topology 311 is not congruent with the layer 3 unicast topology, a node in the 312 layer 3 TE topology may have a reference to the corresponding node in 313 the TE Topology. Such a reference is modeled as follows: 315 augment /nw:networks/nw:network/nw:node/l3t:l3-node-attributes: 316 +--rw l3-te-node-attributes 317 +--rw node-ref? leafref 318 +--rw network-ref? -> /nw:networks/network/network-id 320 2.2.3. Link Termination Point Referencing 322 When TE is enabled on a layer 3 unicast topology, if the TE topology 323 is not congruent with the layer 3 unicast topology, a link 324 termination point in the layer 3 TE topology may have a reference to 325 the corresponding link termination point in the TE Topology. Such a 326 reference is modeled as follows: 328 augment /nw:networks/nw:network/nw:node/nt:termination-point 329 /l3t:l3-termination-point-attributes: 330 +--rw l3-te-tp-attributes 331 +--rw tp-ref? leafref 332 +--rw node-ref? leafref 333 +--rw network-ref? -> /nw:networks/network/network-id 335 2.2.4. Link Referencing 337 When TE is enabled on a layer 3 unicast topology, if the TE topology 338 is not congruent with the layer 3 unicast topology, a link in the 339 layer 3 topology may have a reference to the corresponding link in 340 the TE Topology. Such a reference is modeled as follows: 342 augment /nw:networks/nw:network/nt:link/l3t:l3-link-attributes: 343 +--rw l3-te-link-attributes 344 +--rw link-ref? leafref 345 +--rw network-ref? -> /nw:networks/network/network-id 347 2.3. Topology Type Modeling 349 A new topology type is defined in this document, to indicate a 350 topology that is a layer 3 TE topology, which both inherits l3 351 unicast topology properties and is capable of TE. 353 augment /nw:networks/nw:network/nw:network-types 354 /l3t:l3-unicast-topology: 355 +--rw l3-te! 357 3. Packet TE YANG Types 359 This document updates [RFC8776] with a new revision of the module 360 ietf-te-packet-types. 362 The module ietf-te-packet-types has been updated to add the following 363 YANG identies, types and groupings which can be reused by MPLS-TE and 364 other packet technologies YANG models: 366 bandwidth-profile-type This identity defines various bandwidth 367 profiles specified by IETF and other organizations that may be 368 used to limit bandwidth utilization of MPLS-TE LSPs. 370 bandwidth-scientific-notation This types represents the bandwidth in 371 bit-per-second, using the scientific notation (e.g., 10e3). 373 te-packet-path-bandwidth This grouping defines the path bandwidth 374 information and could be used in any Packet TE topology model 375 (e.g., MPLS-TE) for the path bandwidth representation (e.g., the 376 bandwidth of an MPLS-TE LSP). All the path and LSP bandwidth 377 related sections in generic module, [RFC8776], need to be 378 augmented with this grouping for the usage of Packet TE 379 technologies. This grouping is also applicable to set up the 380 MPLS-TE tunnel. 382 The Packet TE path bandwidth can be represented by a bandwidth 383 profile as follow: 385 +--:(packet) 386 +--rw bandwidth-profile-name? string 387 +--rw bandwidth-profile-type? identityref 388 +--rw cir? uint64 389 +--rw eir? uint64 390 +--rw cbs? uint64 391 +--rw ebs? uint64 393 Other formats for the MPLS-TE path bandwidth are defined in 394 [I-D.ietf-teas-yang-te-mpls] and they could be added in a future 395 update of this document. 397 te-packet-link-bandwidth This grouping defines the link bandwidth 398 information and could be used in any Packet TE topology model 399 (e.g., MPLS-TE) for link bandwidth representation. All the link 400 bandwidth related sections in generic module, [RFC8776], need to 401 be augmented with this grouping for the usage of Packet TE 402 technologies. 404 The Packet TE link bandwidth can be represented by a bandwidth 405 expressed in scientific notation as follow: 407 +--:(packet) 408 +--rw packet-bandwidth? bandwidth-scientific-notation 410 4. Packet Switching Technology Extensions to TE Topologies 412 The technology agnostic TE Topology model is defined in [RFC8795], 413 which is extended by this document to cover the Packet Switch Capable 414 (PSC) technology [RFC3471] [RFC7074]. 416 4.1. Technology Specific Link Attributes 418 The technology agnostic TE Topology model is augmented with packet 419 switching specific link attributes: 421 augment /nw:networks/tet:te/tet:templates/tet:link-template 422 /tet:te-link-attributes 423 /tet:interface-switching-capability: 424 +--rw packet-switch-capable 425 +--rw minimum-lsp-bandwidth? rt-types:bandwidth-ieee-float32 426 +--rw interface-mtu? uint16 427 augment /nw:networks/nw:network/nt:link/tet:te 428 /tet:te-link-attributes 429 /tet:interface-switching-capability: 430 +--rw packet-switch-capable 431 +--rw minimum-lsp-bandwidth? rt-types:bandwidth-ieee-float32 432 +--rw interface-mtu? uint16 433 augment /nw:networks/nw:network/nt:link/tet:te 434 /tet:information-source-entry 435 /tet:interface-switching-capability: 436 +--ro packet-switch-capable 437 +--ro minimum-lsp-bandwidth? rt-types:bandwidth-ieee-float32 438 +--ro interface-mtu? uint16 440 4.2. Performance Metric 442 [RFC7471], [RFC8570] and [RFC7823] specify TE performance metric 443 parameters and their usage. The packet switching augmentations 444 specified in this document support such a capability, which can be 445 conditional enabled by a YANG feature "te-performance-metric". 447 augment /nw:networks/nw:network/nw:node/tet:te 448 /tet:te-node-attributes/tet:connectivity-matrices: 449 +--rw performance-metric 450 +--rw measurement 451 | ...... 452 +--rw normality 453 | ...... 454 +--rw throttle 455 ...... 457 Such an augmentation has been applied to: 459 o Connectivity matrices container 461 o Connectivity matrix entry 463 o Local link connectivities container 465 o Local link connectivity entry 467 o TE link attributes container in a TE link template 469 o TE link attributes container in a TE link 471 o Information source entry in a TE link 473 5. Complete Model Tree Structure 475 5.1. Layer 3 TE Topology Module 477 The model tree structure of the layer 3 TE topology module is as 478 shown below: 480 module: ietf-l3-te-topology 481 augment /nw:networks/nw:network/nw:network-types 482 /l3t:l3-unicast-topology: 483 +--rw l3-te! 484 augment /nw:networks/nw:network/l3t:l3-topology-attributes: 485 +--rw l3-te-topology-attributes 486 +--rw network-ref? -> /nw:networks/network/network-id 487 augment /nw:networks/nw:network/nw:node/l3t:l3-node-attributes: 488 +--rw l3-te-node-attributes 489 +--rw node-ref? leafref 490 +--rw network-ref? -> /nw:networks/network/network-id 491 augment /nw:networks/nw:network/nw:node/nt:termination-point 492 /l3t:l3-termination-point-attributes: 493 +--rw l3-te-tp-attributes 494 +--rw tp-ref? leafref 495 +--rw node-ref? leafref 496 +--rw network-ref? -> /nw:networks/network/network-id 497 augment /nw:networks/nw:network/nt:link/l3t:l3-link-attributes: 498 +--rw l3-te-link-attributes 499 +--rw link-ref? leafref 500 +--rw network-ref? -> /nw:networks/network/network-id 502 5.2. Packet Switching TE Topology Module 504 This is an augmentation to base TE topology model. 506 5.2.1. Network Types 508 This augments the network types with a new network type for TE packet 509 topologies. 511 module: ietf-te-topology-packet 512 augment /nw:networks/nw:network/nw:network-types/tet:te-topology: 513 +--rw packet! 515 5.2.2. Node Connectivity Matrix Attributes 517 This augments the node connectivity matrix attributes with 518 configuration and states for performance metrics when the network 519 type is packet. 521 augment /nw:networks/nw:network/nw:node/tet:te 522 /tet:te-node-attributes/tet:connectivity-matrices: 523 +--ro performance-metrics-one-way {te-performance-metric}? 524 | +--ro one-way-delay? uint32 525 | +--ro one-way-delay-normality? 526 | | te-types:performance-metrics-normality 527 | +--ro one-way-residual-bandwidth? 528 | | rt-types:bandwidth-ieee-float32 529 | +--ro one-way-residual-bandwidth-normality? 530 | | te-types:performance-metrics-normality 531 | +--ro one-way-available-bandwidth? 532 | | rt-types:bandwidth-ieee-float32 533 | +--ro one-way-available-bandwidth-normality? 534 | | te-types:performance-metrics-normality 535 | +--ro one-way-utilized-bandwidth? 536 | | rt-types:bandwidth-ieee-float32 537 | +--ro one-way-utilized-bandwidth-normality? 538 | | te-types:performance-metrics-normality 539 | +--ro one-way-min-delay? uint32 540 | +--ro one-way-min-delay-normality? 541 | | te-types:performance-metrics-normality 542 | +--ro one-way-max-delay? uint32 543 | +--ro one-way-max-delay-normality? 544 | | te-types:performance-metrics-normality 545 | +--ro one-way-delay-variation? uint32 546 | +--ro one-way-delay-variation-normality? 547 | | te-types:performance-metrics-normality 548 | +--ro one-way-packet-loss? decimal64 549 | +--ro one-way-packet-loss-normality? 550 | te-types:performance-metrics-normality 551 +--ro performance-metrics-two-way {te-performance-metric}? 552 | +--ro two-way-delay? uint32 553 | +--ro two-way-delay-normality? 554 | | te-types:performance-metrics-normality 555 | +--ro two-way-min-delay? uint32 556 | +--ro two-way-min-delay-normality? 557 | | te-types:performance-metrics-normality 558 | +--ro two-way-max-delay? uint32 559 | +--ro two-way-max-delay-normality? 560 | | te-types:performance-metrics-normality 561 | +--ro two-way-delay-variation? uint32 562 | +--ro two-way-delay-variation-normality? 563 | | te-types:performance-metrics-normality 564 | +--ro two-way-packet-loss? decimal64 565 | +--ro two-way-packet-loss-normality? 566 | te-types:performance-metrics-normality 567 +--rw throttle {te-performance-metric}? 568 +--rw one-way-delay-offset? uint32 569 +--rw measure-interval? uint32 570 +--rw advertisement-interval? uint32 571 +--rw suppression-interval? uint32 572 +--rw threshold-out 573 | +--rw one-way-delay? uint32 574 | +--rw one-way-residual-bandwidth? 575 | | rt-types:bandwidth-ieee-float32 576 | +--rw one-way-available-bandwidth? 577 | | rt-types:bandwidth-ieee-float32 578 | +--rw one-way-utilized-bandwidth? 579 | | rt-types:bandwidth-ieee-float32 580 | +--rw two-way-delay? uint32 581 | +--rw one-way-min-delay? uint32 582 | +--rw one-way-max-delay? uint32 583 | +--rw one-way-delay-variation? uint32 584 | +--rw one-way-packet-loss? decimal64 585 | +--rw two-way-min-delay? uint32 586 | +--rw two-way-max-delay? uint32 587 | +--rw two-way-delay-variation? uint32 588 | +--rw two-way-packet-loss? decimal64 589 +--rw threshold-in 590 | +--rw one-way-delay? uint32 591 | +--rw one-way-residual-bandwidth? 592 | | rt-types:bandwidth-ieee-float32 593 | +--rw one-way-available-bandwidth? 594 | | rt-types:bandwidth-ieee-float32 595 | +--rw one-way-utilized-bandwidth? 596 | | rt-types:bandwidth-ieee-float32 597 | +--rw two-way-delay? uint32 598 | +--rw one-way-min-delay? uint32 599 | +--rw one-way-max-delay? uint32 600 | +--rw one-way-delay-variation? uint32 601 | +--rw one-way-packet-loss? decimal64 602 | +--rw two-way-min-delay? uint32 603 | +--rw two-way-max-delay? uint32 604 | +--rw two-way-delay-variation? uint32 605 | +--rw two-way-packet-loss? decimal64 606 +--rw threshold-accelerated-advertisement 607 +--rw one-way-delay? uint32 608 +--rw one-way-residual-bandwidth? 609 | rt-types:bandwidth-ieee-float32 610 +--rw one-way-available-bandwidth? 611 | rt-types:bandwidth-ieee-float32 612 +--rw one-way-utilized-bandwidth? 613 | rt-types:bandwidth-ieee-float32 614 +--rw two-way-delay? uint32 615 +--rw one-way-min-delay? uint32 616 +--rw one-way-max-delay? uint32 617 +--rw one-way-delay-variation? uint32 618 +--rw one-way-packet-loss? decimal64 619 +--rw two-way-min-delay? uint32 620 +--rw two-way-max-delay? uint32 621 +--rw two-way-delay-variation? uint32 622 +--rw two-way-packet-loss? decimal64 623 augment /nw:networks/nw:network/nw:node/tet:te 624 /tet:te-node-attributes/tet:connectivity-matrices 625 /tet:connectivity-matrix: 626 +--ro performance-metrics-one-way {te-performance-metric}? 627 | +--ro one-way-delay? uint32 628 | +--ro one-way-delay-normality? 629 | | te-types:performance-metrics-normality 630 | +--ro one-way-residual-bandwidth? 631 | | rt-types:bandwidth-ieee-float32 632 | +--ro one-way-residual-bandwidth-normality? 633 | | te-types:performance-metrics-normality 634 | +--ro one-way-available-bandwidth? 635 | | rt-types:bandwidth-ieee-float32 636 | +--ro one-way-available-bandwidth-normality? 637 | | te-types:performance-metrics-normality 638 | +--ro one-way-utilized-bandwidth? 639 | | rt-types:bandwidth-ieee-float32 640 | +--ro one-way-utilized-bandwidth-normality? 641 | | te-types:performance-metrics-normality 642 | +--ro one-way-min-delay? uint32 643 | +--ro one-way-min-delay-normality? 644 | | te-types:performance-metrics-normality 645 | +--ro one-way-max-delay? uint32 646 | +--ro one-way-max-delay-normality? 647 | | te-types:performance-metrics-normality 648 | +--ro one-way-delay-variation? uint32 649 | +--ro one-way-delay-variation-normality? 650 | | te-types:performance-metrics-normality 651 | +--ro one-way-packet-loss? decimal64 652 | +--ro one-way-packet-loss-normality? 653 | te-types:performance-metrics-normality 654 +--ro performance-metrics-two-way {te-performance-metric}? 655 | +--ro two-way-delay? uint32 656 | +--ro two-way-delay-normality? 657 | | te-types:performance-metrics-normality 658 | +--ro two-way-min-delay? uint32 659 | +--ro two-way-min-delay-normality? 660 | | te-types:performance-metrics-normality 661 | +--ro two-way-max-delay? uint32 662 | +--ro two-way-max-delay-normality? 663 | | te-types:performance-metrics-normality 664 | +--ro two-way-delay-variation? uint32 665 | +--ro two-way-delay-variation-normality? 666 | | te-types:performance-metrics-normality 667 | +--ro two-way-packet-loss? decimal64 668 | +--ro two-way-packet-loss-normality? 669 | te-types:performance-metrics-normality 670 +--rw throttle {te-performance-metric}? 671 +--rw one-way-delay-offset? uint32 672 +--rw measure-interval? uint32 673 +--rw advertisement-interval? uint32 674 +--rw suppression-interval? uint32 675 +--rw threshold-out 676 | +--rw one-way-delay? uint32 677 | +--rw one-way-residual-bandwidth? 678 | | rt-types:bandwidth-ieee-float32 679 | +--rw one-way-available-bandwidth? 680 | | rt-types:bandwidth-ieee-float32 681 | +--rw one-way-utilized-bandwidth? 682 | | rt-types:bandwidth-ieee-float32 683 | +--rw two-way-delay? uint32 684 | +--rw one-way-min-delay? uint32 685 | +--rw one-way-max-delay? uint32 686 | +--rw one-way-delay-variation? uint32 687 | +--rw one-way-packet-loss? decimal64 688 | +--rw two-way-min-delay? uint32 689 | +--rw two-way-max-delay? uint32 690 | +--rw two-way-delay-variation? uint32 691 | +--rw two-way-packet-loss? decimal64 692 +--rw threshold-in 693 | +--rw one-way-delay? uint32 694 | +--rw one-way-residual-bandwidth? 695 | | rt-types:bandwidth-ieee-float32 696 | +--rw one-way-available-bandwidth? 697 | | rt-types:bandwidth-ieee-float32 698 | +--rw one-way-utilized-bandwidth? 699 | | rt-types:bandwidth-ieee-float32 700 | +--rw two-way-delay? uint32 701 | +--rw one-way-min-delay? uint32 702 | +--rw one-way-max-delay? uint32 703 | +--rw one-way-delay-variation? uint32 704 | +--rw one-way-packet-loss? decimal64 705 | +--rw two-way-min-delay? uint32 706 | +--rw two-way-max-delay? uint32 707 | +--rw two-way-delay-variation? uint32 708 | +--rw two-way-packet-loss? decimal64 709 +--rw threshold-accelerated-advertisement 710 +--rw one-way-delay? uint32 711 +--rw one-way-residual-bandwidth? 712 | rt-types:bandwidth-ieee-float32 713 +--rw one-way-available-bandwidth? 714 | rt-types:bandwidth-ieee-float32 715 +--rw one-way-utilized-bandwidth? 716 | rt-types:bandwidth-ieee-float32 717 +--rw two-way-delay? uint32 718 +--rw one-way-min-delay? uint32 719 +--rw one-way-max-delay? uint32 720 +--rw one-way-delay-variation? uint32 721 +--rw one-way-packet-loss? decimal64 722 +--rw two-way-min-delay? uint32 723 +--rw two-way-max-delay? uint32 724 +--rw two-way-delay-variation? uint32 725 +--rw two-way-packet-loss? decimal64 727 5.2.3. Node Information Source 729 This augments the node information source with states for performance 730 metrics when the network type is packet. 732 augment /nw:networks/nw:network/nw:node/tet:te 733 /tet:information-source-entry/tet:connectivity-matrices: 734 +--ro performance-metrics-one-way {te-performance-metric}? 735 | +--ro one-way-delay? uint32 736 | +--ro one-way-delay-normality? 737 | | te-types:performance-metrics-normality 738 | +--ro one-way-residual-bandwidth? 739 | | rt-types:bandwidth-ieee-float32 740 | +--ro one-way-residual-bandwidth-normality? 741 | | te-types:performance-metrics-normality 742 | +--ro one-way-available-bandwidth? 743 | | rt-types:bandwidth-ieee-float32 744 | +--ro one-way-available-bandwidth-normality? 745 | | te-types:performance-metrics-normality 746 | +--ro one-way-utilized-bandwidth? 747 | | rt-types:bandwidth-ieee-float32 748 | +--ro one-way-utilized-bandwidth-normality? 749 | | te-types:performance-metrics-normality 750 | +--ro one-way-min-delay? uint32 751 | +--ro one-way-min-delay-normality? 752 | | te-types:performance-metrics-normality 753 | +--ro one-way-max-delay? uint32 754 | +--ro one-way-max-delay-normality? 755 | | te-types:performance-metrics-normality 756 | +--ro one-way-delay-variation? uint32 757 | +--ro one-way-delay-variation-normality? 758 | | te-types:performance-metrics-normality 759 | +--ro one-way-packet-loss? decimal64 760 | +--ro one-way-packet-loss-normality? 761 | te-types:performance-metrics-normality 762 +--ro performance-metrics-two-way {te-performance-metric}? 763 | +--ro two-way-delay? uint32 764 | +--ro two-way-delay-normality? 765 | | te-types:performance-metrics-normality 766 | +--ro two-way-min-delay? uint32 767 | +--ro two-way-min-delay-normality? 768 | | te-types:performance-metrics-normality 769 | +--ro two-way-max-delay? uint32 770 | +--ro two-way-max-delay-normality? 771 | | te-types:performance-metrics-normality 772 | +--ro two-way-delay-variation? uint32 773 | +--ro two-way-delay-variation-normality? 774 | | te-types:performance-metrics-normality 775 | +--ro two-way-packet-loss? decimal64 776 | +--ro two-way-packet-loss-normality? 777 | te-types:performance-metrics-normality 778 +--ro throttle {te-performance-metric}? 779 +--ro one-way-delay-offset? uint32 780 +--ro measure-interval? uint32 781 +--ro advertisement-interval? uint32 782 +--ro suppression-interval? uint32 783 +--ro threshold-out 784 | +--ro one-way-delay? uint32 785 | +--ro one-way-residual-bandwidth? 786 | | rt-types:bandwidth-ieee-float32 787 | +--ro one-way-available-bandwidth? 788 | | rt-types:bandwidth-ieee-float32 789 | +--ro one-way-utilized-bandwidth? 790 | | rt-types:bandwidth-ieee-float32 791 | +--ro two-way-delay? uint32 792 | +--ro one-way-min-delay? uint32 793 | +--ro one-way-max-delay? uint32 794 | +--ro one-way-delay-variation? uint32 795 | +--ro one-way-packet-loss? decimal64 796 | +--ro two-way-min-delay? uint32 797 | +--ro two-way-max-delay? uint32 798 | +--ro two-way-delay-variation? uint32 799 | +--ro two-way-packet-loss? decimal64 800 +--ro threshold-in 801 | +--ro one-way-delay? uint32 802 | +--ro one-way-residual-bandwidth? 803 | | rt-types:bandwidth-ieee-float32 804 | +--ro one-way-available-bandwidth? 805 | | rt-types:bandwidth-ieee-float32 806 | +--ro one-way-utilized-bandwidth? 807 | | rt-types:bandwidth-ieee-float32 808 | +--ro two-way-delay? uint32 809 | +--ro one-way-min-delay? uint32 810 | +--ro one-way-max-delay? uint32 811 | +--ro one-way-delay-variation? uint32 812 | +--ro one-way-packet-loss? decimal64 813 | +--ro two-way-min-delay? uint32 814 | +--ro two-way-max-delay? uint32 815 | +--ro two-way-delay-variation? uint32 816 | +--ro two-way-packet-loss? decimal64 817 +--ro threshold-accelerated-advertisement 818 +--ro one-way-delay? uint32 819 +--ro one-way-residual-bandwidth? 820 | rt-types:bandwidth-ieee-float32 821 +--ro one-way-available-bandwidth? 822 | rt-types:bandwidth-ieee-float32 823 +--ro one-way-utilized-bandwidth? 824 | rt-types:bandwidth-ieee-float32 825 +--ro two-way-delay? uint32 826 +--ro one-way-min-delay? uint32 827 +--ro one-way-max-delay? uint32 828 +--ro one-way-delay-variation? uint32 829 +--ro one-way-packet-loss? decimal64 830 +--ro two-way-min-delay? uint32 831 +--ro two-way-max-delay? uint32 832 +--ro two-way-delay-variation? uint32 833 +--ro two-way-packet-loss? decimal64 834 augment /nw:networks/nw:network/nw:node/tet:te 835 /tet:information-source-entry/tet:connectivity-matrices 836 /tet:connectivity-matrix: 837 +--ro performance-metrics-one-way {te-performance-metric}? 838 | +--ro one-way-delay? uint32 839 | +--ro one-way-delay-normality? 840 | | te-types:performance-metrics-normality 841 | +--ro one-way-residual-bandwidth? 842 | | rt-types:bandwidth-ieee-float32 843 | +--ro one-way-residual-bandwidth-normality? 844 | | te-types:performance-metrics-normality 845 | +--ro one-way-available-bandwidth? 846 | | rt-types:bandwidth-ieee-float32 847 | +--ro one-way-available-bandwidth-normality? 848 | | te-types:performance-metrics-normality 849 | +--ro one-way-utilized-bandwidth? 850 | | rt-types:bandwidth-ieee-float32 851 | +--ro one-way-utilized-bandwidth-normality? 852 | | te-types:performance-metrics-normality 853 | +--ro one-way-min-delay? uint32 854 | +--ro one-way-min-delay-normality? 855 | | te-types:performance-metrics-normality 856 | +--ro one-way-max-delay? uint32 857 | +--ro one-way-max-delay-normality? 858 | | te-types:performance-metrics-normality 859 | +--ro one-way-delay-variation? uint32 860 | +--ro one-way-delay-variation-normality? 861 | | te-types:performance-metrics-normality 862 | +--ro one-way-packet-loss? decimal64 863 | +--ro one-way-packet-loss-normality? 864 | te-types:performance-metrics-normality 865 +--ro performance-metrics-two-way {te-performance-metric}? 866 | +--ro two-way-delay? uint32 867 | +--ro two-way-delay-normality? 868 | | te-types:performance-metrics-normality 869 | +--ro two-way-min-delay? uint32 870 | +--ro two-way-min-delay-normality? 871 | | te-types:performance-metrics-normality 872 | +--ro two-way-max-delay? uint32 873 | +--ro two-way-max-delay-normality? 874 | | te-types:performance-metrics-normality 875 | +--ro two-way-delay-variation? uint32 876 | +--ro two-way-delay-variation-normality? 877 | | te-types:performance-metrics-normality 878 | +--ro two-way-packet-loss? decimal64 879 | +--ro two-way-packet-loss-normality? 880 | te-types:performance-metrics-normality 881 +--ro throttle {te-performance-metric}? 882 +--ro one-way-delay-offset? uint32 883 +--ro measure-interval? uint32 884 +--ro advertisement-interval? uint32 885 +--ro suppression-interval? uint32 886 +--ro threshold-out 887 | +--ro one-way-delay? uint32 888 | +--ro one-way-residual-bandwidth? 889 | | rt-types:bandwidth-ieee-float32 890 | +--ro one-way-available-bandwidth? 891 | | rt-types:bandwidth-ieee-float32 892 | +--ro one-way-utilized-bandwidth? 893 | | rt-types:bandwidth-ieee-float32 894 | +--ro two-way-delay? uint32 895 | +--ro one-way-min-delay? uint32 896 | +--ro one-way-max-delay? uint32 897 | +--ro one-way-delay-variation? uint32 898 | +--ro one-way-packet-loss? decimal64 899 | +--ro two-way-min-delay? uint32 900 | +--ro two-way-max-delay? uint32 901 | +--ro two-way-delay-variation? uint32 902 | +--ro two-way-packet-loss? decimal64 903 +--ro threshold-in 904 | +--ro one-way-delay? uint32 905 | +--ro one-way-residual-bandwidth? 906 | | rt-types:bandwidth-ieee-float32 907 | +--ro one-way-available-bandwidth? 908 | | rt-types:bandwidth-ieee-float32 909 | +--ro one-way-utilized-bandwidth? 910 | | rt-types:bandwidth-ieee-float32 911 | +--ro two-way-delay? uint32 912 | +--ro one-way-min-delay? uint32 913 | +--ro one-way-max-delay? uint32 914 | +--ro one-way-delay-variation? uint32 915 | +--ro one-way-packet-loss? decimal64 916 | +--ro two-way-min-delay? uint32 917 | +--ro two-way-max-delay? uint32 918 | +--ro two-way-delay-variation? uint32 919 | +--ro two-way-packet-loss? decimal64 920 +--ro threshold-accelerated-advertisement 921 +--ro one-way-delay? uint32 922 +--ro one-way-residual-bandwidth? 923 | rt-types:bandwidth-ieee-float32 924 +--ro one-way-available-bandwidth? 925 | rt-types:bandwidth-ieee-float32 926 +--ro one-way-utilized-bandwidth? 927 | rt-types:bandwidth-ieee-float32 928 +--ro two-way-delay? uint32 929 +--ro one-way-min-delay? uint32 930 +--ro one-way-max-delay? uint32 931 +--ro one-way-delay-variation? uint32 932 +--ro one-way-packet-loss? decimal64 933 +--ro two-way-min-delay? uint32 934 +--ro two-way-max-delay? uint32 935 +--ro two-way-delay-variation? uint32 936 +--ro two-way-packet-loss? decimal64 938 5.2.4. Node Local Link Connectivity 940 This augments the node local link connectivity attributes with 941 configuration and states for performance metrics when the network 942 type is packet. 944 augment /nw:networks/nw:network/nw:node/tet:te 945 /tet:tunnel-termination-point 946 /tet:local-link-connectivities: 947 +--ro performance-metrics-one-way {te-performance-metric}? 948 | +--ro one-way-delay? uint32 949 | +--ro one-way-delay-normality? 950 | | te-types:performance-metrics-normality 951 | +--ro one-way-residual-bandwidth? 952 | | rt-types:bandwidth-ieee-float32 953 | +--ro one-way-residual-bandwidth-normality? 954 | | te-types:performance-metrics-normality 955 | +--ro one-way-available-bandwidth? 956 | | rt-types:bandwidth-ieee-float32 957 | +--ro one-way-available-bandwidth-normality? 958 | | te-types:performance-metrics-normality 959 | +--ro one-way-utilized-bandwidth? 960 | | rt-types:bandwidth-ieee-float32 961 | +--ro one-way-utilized-bandwidth-normality? 962 | | te-types:performance-metrics-normality 963 | +--ro one-way-min-delay? uint32 964 | +--ro one-way-min-delay-normality? 965 | | te-types:performance-metrics-normality 966 | +--ro one-way-max-delay? uint32 967 | +--ro one-way-max-delay-normality? 968 | | te-types:performance-metrics-normality 969 | +--ro one-way-delay-variation? uint32 970 | +--ro one-way-delay-variation-normality? 971 | | te-types:performance-metrics-normality 972 | +--ro one-way-packet-loss? decimal64 973 | +--ro one-way-packet-loss-normality? 974 | te-types:performance-metrics-normality 975 +--ro performance-metrics-two-way {te-performance-metric}? 976 | +--ro two-way-delay? uint32 977 | +--ro two-way-delay-normality? 978 | | te-types:performance-metrics-normality 979 | +--ro two-way-min-delay? uint32 980 | +--ro two-way-min-delay-normality? 981 | | te-types:performance-metrics-normality 982 | +--ro two-way-max-delay? uint32 983 | +--ro two-way-max-delay-normality? 984 | | te-types:performance-metrics-normality 985 | +--ro two-way-delay-variation? uint32 986 | +--ro two-way-delay-variation-normality? 987 | | te-types:performance-metrics-normality 988 | +--ro two-way-packet-loss? decimal64 989 | +--ro two-way-packet-loss-normality? 990 | te-types:performance-metrics-normality 991 +--rw throttle {te-performance-metric}? 992 +--rw one-way-delay-offset? uint32 993 +--rw measure-interval? uint32 994 +--rw advertisement-interval? uint32 995 +--rw suppression-interval? uint32 996 +--rw threshold-out 997 | +--rw one-way-delay? uint32 998 | +--rw one-way-residual-bandwidth? 999 | | rt-types:bandwidth-ieee-float32 1000 | +--rw one-way-available-bandwidth? 1001 | | rt-types:bandwidth-ieee-float32 1002 | +--rw one-way-utilized-bandwidth? 1003 | | rt-types:bandwidth-ieee-float32 1004 | +--rw two-way-delay? uint32 1005 | +--rw one-way-min-delay? uint32 1006 | +--rw one-way-max-delay? uint32 1007 | +--rw one-way-delay-variation? uint32 1008 | +--rw one-way-packet-loss? decimal64 1009 | +--rw two-way-min-delay? uint32 1010 | +--rw two-way-max-delay? uint32 1011 | +--rw two-way-delay-variation? uint32 1012 | +--rw two-way-packet-loss? decimal64 1013 +--rw threshold-in 1014 | +--rw one-way-delay? uint32 1015 | +--rw one-way-residual-bandwidth? 1016 | | rt-types:bandwidth-ieee-float32 1017 | +--rw one-way-available-bandwidth? 1018 | | rt-types:bandwidth-ieee-float32 1019 | +--rw one-way-utilized-bandwidth? 1020 | | rt-types:bandwidth-ieee-float32 1021 | +--rw two-way-delay? uint32 1022 | +--rw one-way-min-delay? uint32 1023 | +--rw one-way-max-delay? uint32 1024 | +--rw one-way-delay-variation? uint32 1025 | +--rw one-way-packet-loss? decimal64 1026 | +--rw two-way-min-delay? uint32 1027 | +--rw two-way-max-delay? uint32 1028 | +--rw two-way-delay-variation? uint32 1029 | +--rw two-way-packet-loss? decimal64 1030 +--rw threshold-accelerated-advertisement 1031 +--rw one-way-delay? uint32 1032 +--rw one-way-residual-bandwidth? 1033 | rt-types:bandwidth-ieee-float32 1034 +--rw one-way-available-bandwidth? 1035 | rt-types:bandwidth-ieee-float32 1036 +--rw one-way-utilized-bandwidth? 1037 | rt-types:bandwidth-ieee-float32 1038 +--rw two-way-delay? uint32 1039 +--rw one-way-min-delay? uint32 1040 +--rw one-way-max-delay? uint32 1041 +--rw one-way-delay-variation? uint32 1042 +--rw one-way-packet-loss? decimal64 1043 +--rw two-way-min-delay? uint32 1044 +--rw two-way-max-delay? uint32 1045 +--rw two-way-delay-variation? uint32 1046 +--rw two-way-packet-loss? decimal64 1047 augment /nw:networks/nw:network/nw:node/tet:te 1048 /tet:tunnel-termination-point 1049 /tet:local-link-connectivities 1050 /tet:local-link-connectivity: 1051 +--ro performance-metrics-one-way {te-performance-metric}? 1052 | +--ro one-way-delay? uint32 1053 | +--ro one-way-delay-normality? 1054 | | te-types:performance-metrics-normality 1055 | +--ro one-way-residual-bandwidth? 1056 | | rt-types:bandwidth-ieee-float32 1057 | +--ro one-way-residual-bandwidth-normality? 1058 | | te-types:performance-metrics-normality 1059 | +--ro one-way-available-bandwidth? 1060 | | rt-types:bandwidth-ieee-float32 1061 | +--ro one-way-available-bandwidth-normality? 1062 | | te-types:performance-metrics-normality 1063 | +--ro one-way-utilized-bandwidth? 1064 | | rt-types:bandwidth-ieee-float32 1065 | +--ro one-way-utilized-bandwidth-normality? 1066 | | te-types:performance-metrics-normality 1067 | +--ro one-way-min-delay? uint32 1068 | +--ro one-way-min-delay-normality? 1069 | | te-types:performance-metrics-normality 1070 | +--ro one-way-max-delay? uint32 1071 | +--ro one-way-max-delay-normality? 1072 | | te-types:performance-metrics-normality 1073 | +--ro one-way-delay-variation? uint32 1074 | +--ro one-way-delay-variation-normality? 1075 | | te-types:performance-metrics-normality 1076 | +--ro one-way-packet-loss? decimal64 1077 | +--ro one-way-packet-loss-normality? 1078 | te-types:performance-metrics-normality 1079 +--ro performance-metrics-two-way {te-performance-metric}? 1080 | +--ro two-way-delay? uint32 1081 | +--ro two-way-delay-normality? 1082 | | te-types:performance-metrics-normality 1083 | +--ro two-way-min-delay? uint32 1084 | +--ro two-way-min-delay-normality? 1085 | | te-types:performance-metrics-normality 1086 | +--ro two-way-max-delay? uint32 1087 | +--ro two-way-max-delay-normality? 1088 | | te-types:performance-metrics-normality 1089 | +--ro two-way-delay-variation? uint32 1090 | +--ro two-way-delay-variation-normality? 1091 | | te-types:performance-metrics-normality 1092 | +--ro two-way-packet-loss? decimal64 1093 | +--ro two-way-packet-loss-normality? 1094 | te-types:performance-metrics-normality 1095 +--rw throttle {te-performance-metric}? 1096 +--rw one-way-delay-offset? uint32 1097 +--rw measure-interval? uint32 1098 +--rw advertisement-interval? uint32 1099 +--rw suppression-interval? uint32 1100 +--rw threshold-out 1101 | +--rw one-way-delay? uint32 1102 | +--rw one-way-residual-bandwidth? 1103 | | rt-types:bandwidth-ieee-float32 1104 | +--rw one-way-available-bandwidth? 1105 | | rt-types:bandwidth-ieee-float32 1106 | +--rw one-way-utilized-bandwidth? 1107 | | rt-types:bandwidth-ieee-float32 1108 | +--rw two-way-delay? uint32 1109 | +--rw one-way-min-delay? uint32 1110 | +--rw one-way-max-delay? uint32 1111 | +--rw one-way-delay-variation? uint32 1112 | +--rw one-way-packet-loss? decimal64 1113 | +--rw two-way-min-delay? uint32 1114 | +--rw two-way-max-delay? uint32 1115 | +--rw two-way-delay-variation? uint32 1116 | +--rw two-way-packet-loss? decimal64 1117 +--rw threshold-in 1118 | +--rw one-way-delay? uint32 1119 | +--rw one-way-residual-bandwidth? 1120 | | rt-types:bandwidth-ieee-float32 1121 | +--rw one-way-available-bandwidth? 1122 | | rt-types:bandwidth-ieee-float32 1123 | +--rw one-way-utilized-bandwidth? 1124 | | rt-types:bandwidth-ieee-float32 1125 | +--rw two-way-delay? uint32 1126 | +--rw one-way-min-delay? uint32 1127 | +--rw one-way-max-delay? uint32 1128 | +--rw one-way-delay-variation? uint32 1129 | +--rw one-way-packet-loss? decimal64 1130 | +--rw two-way-min-delay? uint32 1131 | +--rw two-way-max-delay? uint32 1132 | +--rw two-way-delay-variation? uint32 1133 | +--rw two-way-packet-loss? decimal64 1134 +--rw threshold-accelerated-advertisement 1135 +--rw one-way-delay? uint32 1136 +--rw one-way-residual-bandwidth? 1137 | rt-types:bandwidth-ieee-float32 1138 +--rw one-way-available-bandwidth? 1139 | rt-types:bandwidth-ieee-float32 1140 +--rw one-way-utilized-bandwidth? 1141 | rt-types:bandwidth-ieee-float32 1142 +--rw two-way-delay? uint32 1143 +--rw one-way-min-delay? uint32 1144 +--rw one-way-max-delay? uint32 1145 +--rw one-way-delay-variation? uint32 1146 +--rw one-way-packet-loss? decimal64 1147 +--rw two-way-min-delay? uint32 1148 +--rw two-way-max-delay? uint32 1149 +--rw two-way-delay-variation? uint32 1150 +--rw two-way-packet-loss? decimal64 1152 5.2.5. Link Template for Performance Metrics 1154 This augments the link template attributes with configuration and 1155 states for performance metrics when the network type is packet. 1157 augment /nw:networks/tet:te/tet:templates/tet:link-template 1158 /tet:te-link-attributes: 1159 +--ro performance-metrics-one-way {te-performance-metric}? 1160 | +--ro one-way-delay? uint32 1161 | +--ro one-way-delay-normality? 1162 | | te-types:performance-metrics-normality 1163 | +--ro one-way-residual-bandwidth? 1164 | | rt-types:bandwidth-ieee-float32 1165 | +--ro one-way-residual-bandwidth-normality? 1166 | | te-types:performance-metrics-normality 1167 | +--ro one-way-available-bandwidth? 1168 | | rt-types:bandwidth-ieee-float32 1169 | +--ro one-way-available-bandwidth-normality? 1170 | | te-types:performance-metrics-normality 1171 | +--ro one-way-utilized-bandwidth? 1172 | | rt-types:bandwidth-ieee-float32 1173 | +--ro one-way-utilized-bandwidth-normality? 1174 | | te-types:performance-metrics-normality 1175 | +--ro one-way-min-delay? uint32 1176 | +--ro one-way-min-delay-normality? 1177 | | te-types:performance-metrics-normality 1178 | +--ro one-way-max-delay? uint32 1179 | +--ro one-way-max-delay-normality? 1180 | | te-types:performance-metrics-normality 1181 | +--ro one-way-delay-variation? uint32 1182 | +--ro one-way-delay-variation-normality? 1183 | | te-types:performance-metrics-normality 1184 | +--ro one-way-packet-loss? decimal64 1185 | +--ro one-way-packet-loss-normality? 1186 | te-types:performance-metrics-normality 1187 +--ro performance-metrics-two-way {te-performance-metric}? 1188 | +--ro two-way-delay? uint32 1189 | +--ro two-way-delay-normality? 1190 | | te-types:performance-metrics-normality 1191 | +--ro two-way-min-delay? uint32 1192 | +--ro two-way-min-delay-normality? 1193 | | te-types:performance-metrics-normality 1194 | +--ro two-way-max-delay? uint32 1195 | +--ro two-way-max-delay-normality? 1196 | | te-types:performance-metrics-normality 1197 | +--ro two-way-delay-variation? uint32 1198 | +--ro two-way-delay-variation-normality? 1199 | | te-types:performance-metrics-normality 1200 | +--ro two-way-packet-loss? decimal64 1201 | +--ro two-way-packet-loss-normality? 1202 | te-types:performance-metrics-normality 1203 +--rw throttle {te-performance-metric}? 1204 +--rw one-way-delay-offset? uint32 1205 +--rw measure-interval? uint32 1206 +--rw advertisement-interval? uint32 1207 +--rw suppression-interval? uint32 1208 +--rw threshold-out 1209 | +--rw one-way-delay? uint32 1210 | +--rw one-way-residual-bandwidth? 1211 | | rt-types:bandwidth-ieee-float32 1212 | +--rw one-way-available-bandwidth? 1213 | | rt-types:bandwidth-ieee-float32 1214 | +--rw one-way-utilized-bandwidth? 1215 | | rt-types:bandwidth-ieee-float32 1216 | +--rw two-way-delay? uint32 1217 | +--rw one-way-min-delay? uint32 1218 | +--rw one-way-max-delay? uint32 1219 | +--rw one-way-delay-variation? uint32 1220 | +--rw one-way-packet-loss? decimal64 1221 | +--rw two-way-min-delay? uint32 1222 | +--rw two-way-max-delay? uint32 1223 | +--rw two-way-delay-variation? uint32 1224 | +--rw two-way-packet-loss? decimal64 1225 +--rw threshold-in 1226 | +--rw one-way-delay? uint32 1227 | +--rw one-way-residual-bandwidth? 1228 | | rt-types:bandwidth-ieee-float32 1229 | +--rw one-way-available-bandwidth? 1230 | | rt-types:bandwidth-ieee-float32 1231 | +--rw one-way-utilized-bandwidth? 1232 | | rt-types:bandwidth-ieee-float32 1233 | +--rw two-way-delay? uint32 1234 | +--rw one-way-min-delay? uint32 1235 | +--rw one-way-max-delay? uint32 1236 | +--rw one-way-delay-variation? uint32 1237 | +--rw one-way-packet-loss? decimal64 1238 | +--rw two-way-min-delay? uint32 1239 | +--rw two-way-max-delay? uint32 1240 | +--rw two-way-delay-variation? uint32 1241 | +--rw two-way-packet-loss? decimal64 1242 +--rw threshold-accelerated-advertisement 1243 +--rw one-way-delay? uint32 1244 +--rw one-way-residual-bandwidth? 1245 | rt-types:bandwidth-ieee-float32 1246 +--rw one-way-available-bandwidth? 1247 | rt-types:bandwidth-ieee-float32 1248 +--rw one-way-utilized-bandwidth? 1249 | rt-types:bandwidth-ieee-float32 1250 +--rw two-way-delay? uint32 1251 +--rw one-way-min-delay? uint32 1252 +--rw one-way-max-delay? uint32 1253 +--rw one-way-delay-variation? uint32 1254 +--rw one-way-packet-loss? decimal64 1255 +--rw two-way-min-delay? uint32 1256 +--rw two-way-max-delay? uint32 1257 +--rw two-way-delay-variation? uint32 1258 +--rw two-way-packet-loss? decimal64 1260 5.2.6. Link for Performance Metrics 1262 This augments the link attributes with configuration and states for 1263 performance metrics when the network type is packet. 1265 augment /nw:networks/nw:network/nt:link/tet:te 1266 /tet:te-link-attributes: 1267 +--ro performance-metrics-one-way {te-performance-metric}? 1268 | +--ro one-way-delay? uint32 1269 | +--ro one-way-delay-normality? 1270 | | te-types:performance-metrics-normality 1271 | +--ro one-way-residual-bandwidth? 1272 | | rt-types:bandwidth-ieee-float32 1273 | +--ro one-way-residual-bandwidth-normality? 1274 | | te-types:performance-metrics-normality 1275 | +--ro one-way-available-bandwidth? 1276 | | rt-types:bandwidth-ieee-float32 1277 | +--ro one-way-available-bandwidth-normality? 1278 | | te-types:performance-metrics-normality 1279 | +--ro one-way-utilized-bandwidth? 1280 | | rt-types:bandwidth-ieee-float32 1281 | +--ro one-way-utilized-bandwidth-normality? 1282 | | te-types:performance-metrics-normality 1283 | +--ro one-way-min-delay? uint32 1284 | +--ro one-way-min-delay-normality? 1285 | | te-types:performance-metrics-normality 1286 | +--ro one-way-max-delay? uint32 1287 | +--ro one-way-max-delay-normality? 1288 | | te-types:performance-metrics-normality 1289 | +--ro one-way-delay-variation? uint32 1290 | +--ro one-way-delay-variation-normality? 1291 | | te-types:performance-metrics-normality 1292 | +--ro one-way-packet-loss? decimal64 1293 | +--ro one-way-packet-loss-normality? 1294 | te-types:performance-metrics-normality 1295 +--ro performance-metrics-two-way {te-performance-metric}? 1296 | +--ro two-way-delay? uint32 1297 | +--ro two-way-delay-normality? 1298 | | te-types:performance-metrics-normality 1299 | +--ro two-way-min-delay? uint32 1300 | +--ro two-way-min-delay-normality? 1301 | | te-types:performance-metrics-normality 1302 | +--ro two-way-max-delay? uint32 1303 | +--ro two-way-max-delay-normality? 1304 | | te-types:performance-metrics-normality 1305 | +--ro two-way-delay-variation? uint32 1306 | +--ro two-way-delay-variation-normality? 1307 | | te-types:performance-metrics-normality 1308 | +--ro two-way-packet-loss? decimal64 1309 | +--ro two-way-packet-loss-normality? 1310 | te-types:performance-metrics-normality 1311 +--rw throttle {te-performance-metric}? 1312 +--rw one-way-delay-offset? uint32 1313 +--rw measure-interval? uint32 1314 +--rw advertisement-interval? uint32 1315 +--rw suppression-interval? uint32 1316 +--rw threshold-out 1317 | +--rw one-way-delay? uint32 1318 | +--rw one-way-residual-bandwidth? 1319 | | rt-types:bandwidth-ieee-float32 1320 | +--rw one-way-available-bandwidth? 1321 | | rt-types:bandwidth-ieee-float32 1322 | +--rw one-way-utilized-bandwidth? 1323 | | rt-types:bandwidth-ieee-float32 1324 | +--rw two-way-delay? uint32 1325 | +--rw one-way-min-delay? uint32 1326 | +--rw one-way-max-delay? uint32 1327 | +--rw one-way-delay-variation? uint32 1328 | +--rw one-way-packet-loss? decimal64 1329 | +--rw two-way-min-delay? uint32 1330 | +--rw two-way-max-delay? uint32 1331 | +--rw two-way-delay-variation? uint32 1332 | +--rw two-way-packet-loss? decimal64 1333 +--rw threshold-in 1334 | +--rw one-way-delay? uint32 1335 | +--rw one-way-residual-bandwidth? 1336 | | rt-types:bandwidth-ieee-float32 1337 | +--rw one-way-available-bandwidth? 1338 | | rt-types:bandwidth-ieee-float32 1339 | +--rw one-way-utilized-bandwidth? 1340 | | rt-types:bandwidth-ieee-float32 1341 | +--rw two-way-delay? uint32 1342 | +--rw one-way-min-delay? uint32 1343 | +--rw one-way-max-delay? uint32 1344 | +--rw one-way-delay-variation? uint32 1345 | +--rw one-way-packet-loss? decimal64 1346 | +--rw two-way-min-delay? uint32 1347 | +--rw two-way-max-delay? uint32 1348 | +--rw two-way-delay-variation? uint32 1349 | +--rw two-way-packet-loss? decimal64 1350 +--rw threshold-accelerated-advertisement 1351 +--rw one-way-delay? uint32 1352 +--rw one-way-residual-bandwidth? 1353 | rt-types:bandwidth-ieee-float32 1354 +--rw one-way-available-bandwidth? 1355 | rt-types:bandwidth-ieee-float32 1356 +--rw one-way-utilized-bandwidth? 1357 | rt-types:bandwidth-ieee-float32 1358 +--rw two-way-delay? uint32 1359 +--rw one-way-min-delay? uint32 1360 +--rw one-way-max-delay? uint32 1361 +--rw one-way-delay-variation? uint32 1362 +--rw one-way-packet-loss? decimal64 1363 +--rw two-way-min-delay? uint32 1364 +--rw two-way-max-delay? uint32 1365 +--rw two-way-delay-variation? uint32 1366 +--rw two-way-packet-loss? decimal64 1368 5.2.7. Link Information Source for Performance Metrics 1370 This augments the link information source with states for performance 1371 metrics when the network type is packet. 1373 augment /nw:networks/nw:network/nt:link/tet:te 1374 /tet:information-source-entry: 1375 +--ro performance-metrics-one-way {te-performance-metric}? 1376 | +--ro one-way-delay? uint32 1377 | +--ro one-way-delay-normality? 1378 | | te-types:performance-metrics-normality 1379 | +--ro one-way-residual-bandwidth? 1380 | | rt-types:bandwidth-ieee-float32 1381 | +--ro one-way-residual-bandwidth-normality? 1382 | | te-types:performance-metrics-normality 1383 | +--ro one-way-available-bandwidth? 1384 | | rt-types:bandwidth-ieee-float32 1385 | +--ro one-way-available-bandwidth-normality? 1386 | | te-types:performance-metrics-normality 1387 | +--ro one-way-utilized-bandwidth? 1388 | | rt-types:bandwidth-ieee-float32 1389 | +--ro one-way-utilized-bandwidth-normality? 1390 | | te-types:performance-metrics-normality 1391 | +--ro one-way-min-delay? uint32 1392 | +--ro one-way-min-delay-normality? 1393 | | te-types:performance-metrics-normality 1394 | +--ro one-way-max-delay? uint32 1395 | +--ro one-way-max-delay-normality? 1396 | | te-types:performance-metrics-normality 1397 | +--ro one-way-delay-variation? uint32 1398 | +--ro one-way-delay-variation-normality? 1399 | | te-types:performance-metrics-normality 1400 | +--ro one-way-packet-loss? decimal64 1401 | +--ro one-way-packet-loss-normality? 1402 | te-types:performance-metrics-normality 1403 +--ro performance-metrics-two-way {te-performance-metric}? 1404 | +--ro two-way-delay? uint32 1405 | +--ro two-way-delay-normality? 1406 | | te-types:performance-metrics-normality 1407 | +--ro two-way-min-delay? uint32 1408 | +--ro two-way-min-delay-normality? 1409 | | te-types:performance-metrics-normality 1410 | +--ro two-way-max-delay? uint32 1411 | +--ro two-way-max-delay-normality? 1412 | | te-types:performance-metrics-normality 1413 | +--ro two-way-delay-variation? uint32 1414 | +--ro two-way-delay-variation-normality? 1415 | | te-types:performance-metrics-normality 1416 | +--ro two-way-packet-loss? decimal64 1417 | +--ro two-way-packet-loss-normality? 1418 | te-types:performance-metrics-normality 1419 +--ro throttle {te-performance-metric}? 1420 +--ro one-way-delay-offset? uint32 1421 +--ro measure-interval? uint32 1422 +--ro advertisement-interval? uint32 1423 +--ro suppression-interval? uint32 1424 +--ro threshold-out 1425 | +--ro one-way-delay? uint32 1426 | +--ro one-way-residual-bandwidth? 1427 | | rt-types:bandwidth-ieee-float32 1428 | +--ro one-way-available-bandwidth? 1429 | | rt-types:bandwidth-ieee-float32 1430 | +--ro one-way-utilized-bandwidth? 1431 | | rt-types:bandwidth-ieee-float32 1432 | +--ro two-way-delay? uint32 1433 | +--ro one-way-min-delay? uint32 1434 | +--ro one-way-max-delay? uint32 1435 | +--ro one-way-delay-variation? uint32 1436 | +--ro one-way-packet-loss? decimal64 1437 | +--ro two-way-min-delay? uint32 1438 | +--ro two-way-max-delay? uint32 1439 | +--ro two-way-delay-variation? uint32 1440 | +--ro two-way-packet-loss? decimal64 1441 +--ro threshold-in 1442 | +--ro one-way-delay? uint32 1443 | +--ro one-way-residual-bandwidth? 1444 | | rt-types:bandwidth-ieee-float32 1445 | +--ro one-way-available-bandwidth? 1446 | | rt-types:bandwidth-ieee-float32 1447 | +--ro one-way-utilized-bandwidth? 1448 | | rt-types:bandwidth-ieee-float32 1449 | +--ro two-way-delay? uint32 1450 | +--ro one-way-min-delay? uint32 1451 | +--ro one-way-max-delay? uint32 1452 | +--ro one-way-delay-variation? uint32 1453 | +--ro one-way-packet-loss? decimal64 1454 | +--ro two-way-min-delay? uint32 1455 | +--ro two-way-max-delay? uint32 1456 | +--ro two-way-delay-variation? uint32 1457 | +--ro two-way-packet-loss? decimal64 1458 +--ro threshold-accelerated-advertisement 1459 +--ro one-way-delay? uint32 1460 +--ro one-way-residual-bandwidth? 1461 | rt-types:bandwidth-ieee-float32 1462 +--ro one-way-available-bandwidth? 1463 | rt-types:bandwidth-ieee-float32 1464 +--ro one-way-utilized-bandwidth? 1465 | rt-types:bandwidth-ieee-float32 1466 +--ro two-way-delay? uint32 1467 +--ro one-way-min-delay? uint32 1468 +--ro one-way-max-delay? uint32 1469 +--ro one-way-delay-variation? uint32 1470 +--ro one-way-packet-loss? decimal64 1471 +--ro two-way-min-delay? uint32 1472 +--ro two-way-max-delay? uint32 1473 +--ro two-way-delay-variation? uint32 1474 +--ro two-way-packet-loss? decimal64 1476 5.2.8. Link Template for Packet-specific Attributes 1478 This augments the link template attributes with configuration and 1479 states for packet-specific attributes when the network type is 1480 packet. 1482 augment /nw:networks/tet:te/tet:templates/tet:link-template 1483 /tet:te-link-attributes 1484 /tet:interface-switching-capability: 1485 +--rw packet-switch-capable 1486 +--rw minimum-lsp-bandwidth? rt-types:bandwidth-ieee-float32 1487 +--rw interface-mtu? uint16 1489 5.2.9. Link for Packet-specific Attributes 1491 This augments the link attributes with configuration and states for 1492 packet-specific attributes when the network type is packet. 1494 augment /nw:networks/nw:network/nt:link/tet:te 1495 /tet:te-link-attributes 1496 /tet:interface-switching-capability: 1497 +--rw packet-switch-capable 1498 +--rw minimum-lsp-bandwidth? rt-types:bandwidth-ieee-float32 1499 +--rw interface-mtu? uint16 1501 5.2.10. Link Information Source for Packet-specific Attributes 1503 This augments the link information source with states for packet- 1504 specific attributes when the network type is packet. 1506 augment /nw:networks/nw:network/nt:link/tet:te 1507 /tet:information-source-entry 1508 /tet:interface-switching-capability: 1509 +--ro packet-switch-capable 1510 +--ro minimum-lsp-bandwidth? rt-types:bandwidth-ieee-float32 1511 +--ro interface-mtu? uint16 1513 5.2.11. TE Bandwidth for Packet-specific Technologies 1515 These augmentations specify TE bandwidth for packet-specific 1516 technologies. 1518 augment /nw:networks/nw:network/nw:node/nt:termination-point/tet:te 1519 /tet:interface-switching-capability/tet:max-lsp-bandwidth 1520 /tet:te-bandwidth/tet:technology: 1521 +--:(packet) 1522 +--rw bandwidth-profile-name? string 1523 +--rw bandwidth-profile-type? identityref 1524 +--rw cir? uint64 1525 +--rw eir? uint64 1526 +--rw cbs? uint64 1527 +--rw ebs? uint64 1528 augment /nw:networks/nw:network/nw:node/tet:te 1529 /tet:te-node-attributes/tet:connectivity-matrices 1530 /tet:path-constraints/tet:te-bandwidth/tet:technology: 1531 +--:(packet) 1532 +--rw packet-bandwidth? bandwidth-scientific-notation 1533 augment /nw:networks/nw:network/nw:node/tet:te 1534 /tet:te-node-attributes/tet:connectivity-matrices 1535 /tet:connectivity-matrix/tet:path-constraints 1536 /tet:te-bandwidth/tet:technology: 1537 +--:(packet) 1538 +--rw packet-bandwidth? bandwidth-scientific-notation 1539 augment /nw:networks/nw:network/nw:node/tet:te 1540 /tet:information-source-entry/tet:connectivity-matrices 1541 /tet:path-constraints/tet:te-bandwidth/tet:technology: 1542 +--:(packet) 1543 +--ro packet-bandwidth? bandwidth-scientific-notation 1544 augment /nw:networks/nw:network/nw:node/tet:te 1545 /tet:information-source-entry/tet:connectivity-matrices 1546 /tet:connectivity-matrix/tet:path-constraints 1547 /tet:te-bandwidth/tet:technology: 1548 +--:(packet) 1549 +--ro packet-bandwidth? bandwidth-scientific-notation 1550 augment /nw:networks/nw:network/nw:node/tet:te 1551 /tet:tunnel-termination-point/tet:client-layer-adaptation 1552 /tet:switching-capability/tet:te-bandwidth 1553 /tet:technology: 1554 +--:(packet) 1555 +--rw packet-bandwidth? bandwidth-scientific-notation 1556 augment /nw:networks/nw:network/nw:node/tet:te 1557 /tet:tunnel-termination-point 1558 /tet:local-link-connectivities/tet:path-constraints 1559 /tet:te-bandwidth/tet:technology: 1560 +--:(packet) 1561 +--rw packet-bandwidth? bandwidth-scientific-notation 1562 augment /nw:networks/nw:network/nw:node/tet:te 1563 /tet:tunnel-termination-point 1564 /tet:local-link-connectivities 1565 /tet:local-link-connectivity/tet:path-constraints 1566 /tet:te-bandwidth/tet:technology: 1567 +--:(packet) 1568 +--rw packet-bandwidth? bandwidth-scientific-notation 1569 augment /nw:networks/nw:network/nt:link/tet:te 1570 /tet:te-link-attributes 1571 /tet:interface-switching-capability/tet:max-lsp-bandwidth 1572 /tet:te-bandwidth/tet:technology: 1573 +--:(packet) 1574 +--rw bandwidth-profile-name? string 1575 +--rw bandwidth-profile-type? identityref 1576 +--rw cir? uint64 1577 +--rw eir? uint64 1578 +--rw cbs? uint64 1579 +--rw ebs? uint64 1580 augment /nw:networks/nw:network/nt:link/tet:te 1581 /tet:te-link-attributes/tet:max-link-bandwidth 1582 /tet:te-bandwidth/tet:technology: 1583 +--:(packet) 1584 +--rw packet-bandwidth? bandwidth-scientific-notation 1585 augment /nw:networks/nw:network/nt:link/tet:te 1586 /tet:te-link-attributes/tet:max-resv-link-bandwidth 1587 /tet:te-bandwidth/tet:technology: 1588 +--:(packet) 1589 +--rw packet-bandwidth? bandwidth-scientific-notation 1590 augment /nw:networks/nw:network/nt:link/tet:te 1591 /tet:te-link-attributes/tet:unreserved-bandwidth 1592 /tet:te-bandwidth/tet:technology: 1593 +--:(packet) 1594 +--rw packet-bandwidth? bandwidth-scientific-notation 1595 augment /nw:networks/nw:network/nt:link/tet:te 1596 /tet:information-source-entry 1597 /tet:interface-switching-capability/tet:max-lsp-bandwidth 1598 /tet:te-bandwidth/tet:technology: 1599 +--:(packet) 1600 +--ro bandwidth-profile-name? string 1601 +--ro bandwidth-profile-type? identityref 1602 +--ro cir? uint64 1603 +--ro eir? uint64 1604 +--ro cbs? uint64 1605 +--ro ebs? uint64 1606 augment /nw:networks/nw:network/nt:link/tet:te 1607 /tet:information-source-entry/tet:max-link-bandwidth 1608 /tet:te-bandwidth/tet:technology: 1609 +--:(packet) 1610 +--ro packet-bandwidth? bandwidth-scientific-notation 1611 augment /nw:networks/nw:network/nt:link/tet:te 1612 /tet:information-source-entry/tet:max-resv-link-bandwidth 1613 /tet:te-bandwidth/tet:technology: 1614 +--:(packet) 1615 +--ro packet-bandwidth? bandwidth-scientific-notation 1616 augment /nw:networks/nw:network/nt:link/tet:te 1617 /tet:information-source-entry/tet:unreserved-bandwidth 1618 /tet:te-bandwidth/tet:technology: 1619 +--:(packet) 1620 +--ro packet-bandwidth? bandwidth-scientific-notation 1621 augment /nw:networks/tet:te/tet:templates/tet:link-template 1622 /tet:te-link-attributes 1623 /tet:interface-switching-capability/tet:max-lsp-bandwidth 1624 /tet:te-bandwidth/tet:technology: 1625 +--:(packet) 1626 +--rw bandwidth-profile-name? string 1627 +--rw bandwidth-profile-type? identityref 1628 +--rw cir? uint64 1629 +--rw eir? uint64 1630 +--rw cbs? uint64 1631 +--rw ebs? uint64 1632 augment /nw:networks/tet:te/tet:templates/tet:link-template 1633 /tet:te-link-attributes/tet:max-link-bandwidth 1634 /tet:te-bandwidth/tet:technology: 1635 +--:(packet) 1636 +--rw packet-bandwidth? bandwidth-scientific-notation 1637 augment /nw:networks/tet:te/tet:templates/tet:link-template 1638 /tet:te-link-attributes/tet:max-resv-link-bandwidth 1639 /tet:te-bandwidth/tet:technology: 1640 +--:(packet) 1641 +--rw packet-bandwidth? bandwidth-scientific-notation 1642 augment /nw:networks/tet:te/tet:templates/tet:link-template 1643 /tet:te-link-attributes/tet:unreserved-bandwidth 1644 /tet:te-bandwidth/tet:technology: 1645 +--:(packet) 1646 +--rw packet-bandwidth? bandwidth-scientific-notation 1648 6. YANG Modules 1650 6.1. Layer 3 TE Topology Module 1652 This module references [RFC8345], [RFC8346], and [RFC8795]. 1654 file "ietf-l3-te-topology@2020-05-03.yang" 1655 module ietf-l3-te-topology { 1656 yang-version 1.1; 1657 namespace "urn:ietf:params:xml:ns:yang:ietf-l3-te-topology"; 1658 prefix "l3tet"; 1660 import ietf-network { 1661 prefix "nw"; 1662 reference "RFC 8345: A YANG Data Model for Network Topologies"; 1663 } 1664 import ietf-network-topology { 1665 prefix "nt"; 1666 reference "RFC 8345: A YANG Data Model for Network Topologies"; 1667 } 1668 import ietf-l3-unicast-topology { 1669 prefix "l3t"; 1670 reference "RFC 8346: A YANG Data Model for Layer 3 Topologies"; 1671 } 1672 import ietf-te-topology { 1673 prefix "tet"; 1674 reference 1675 "I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic 1676 Engineering (TE) Topologies"; 1677 } 1679 organization 1680 "IETF Traffic Engineering Architecture and Signaling (TEAS) 1681 Working Group"; 1683 contact 1684 "WG Web: 1685 WG List: 1687 Editor: Xufeng Liu 1688 1690 Editor: Igor Bryskin 1691 1693 Editor: Vishnu Pavan Beeram 1694 1696 Editor: Tarek Saad 1697 1699 Editor: Himanshu Shah 1700 1702 Editor: Oscar Gonzalez De Dios 1703 "; 1705 description 1706 "YANG data model for representing and manipulating Layer 3 TE 1707 Topologies. 1709 Copyright (c) 2018 IETF Trust and the persons identified as 1710 authors of the code. All rights reserved. 1712 Redistribution and use in source and binary forms, with or 1713 without modification, is permitted pursuant to, and subject to 1714 the license terms contained in, the Simplified BSD License set 1715 forth in Section 4.c of the IETF Trust's Legal Provisions 1716 Relating to IETF Documents 1717 (http://trustee.ietf.org/license-info). 1719 This version of this YANG module is part of RFC XXXX; see the 1720 RFC itself for full legal notices."; 1722 revision 2020-05-03 { 1724 description 1725 "Initial revision"; 1726 reference "RFC XXXX: YANG Data Model for Layer 3 TE Topologies"; 1727 } 1728 grouping l3-te-topology-type { 1729 description 1730 "Identifies the L3 TE topology type."; 1731 container l3-te { 1732 presence "Indicates L3 TE Topology"; 1733 description 1734 "Its presence identifies the L3 TE topology type."; 1735 } 1736 } 1738 augment "/nw:networks/nw:network/nw:network-types/" 1739 + "l3t:l3-unicast-topology" { 1740 description 1741 "Defines the L3 TE topology type."; 1742 uses l3-te-topology-type; 1743 } 1745 augment "/nw:networks/nw:network/l3t:l3-topology-attributes" { 1746 when "../nw:network-types/l3t:l3-unicast-topology/l3tet:l3-te" { 1747 description 1748 "Augment only for L3 TE topology"; 1749 } 1750 description 1751 "Augment topology configuration"; 1752 uses l3-te-topology-attributes; 1753 } 1755 augment "/nw:networks/nw:network/nw:node/l3t:l3-node-attributes" { 1756 when "../../nw:network-types/l3t:l3-unicast-topology/" 1757 + "l3tet:l3-te" { 1758 description 1759 "Augment only for L3 TE topology"; 1760 } 1761 description 1762 "Augment node configuration"; 1763 uses l3-te-node-attributes; 1764 } 1766 augment "/nw:networks/nw:network/nw:node/nt:termination-point/" 1767 + "l3t:l3-termination-point-attributes" { 1768 when "../../../nw:network-types/l3t:l3-unicast-topology/" 1769 + "l3tet:l3-te" { 1770 description 1771 "Augment only for L3 TE topology"; 1772 } 1773 description 1774 "Augment termination point configuration"; 1775 uses l3-te-tp-attributes; 1777 } 1779 augment "/nw:networks/nw:network/nt:link/l3t:l3-link-attributes" { 1780 when "../../nw:network-types/l3t:l3-unicast-topology/" 1781 + "l3tet:l3-te" { 1782 description 1783 "Augment only for L3 TE topology"; 1784 } 1785 description 1786 "Augment link configuration"; 1787 uses l3-te-link-attributes; 1788 } 1790 grouping l3-te-topology-attributes { 1791 description 1792 "L3 TE topology scope attributes"; 1793 container l3-te-topology-attributes { 1794 must "/nw:networks/nw:network" 1795 + "[nw:network-id = current()/network-ref]/nw:network-types/" 1796 + "tet:te-topology" { 1797 error-message 1798 "The referenced network must be a TE topology."; 1799 description 1800 "The referenced network must be a TE topology."; 1801 } 1802 description 1803 "Containing TE topology references"; 1804 uses nw:network-ref; 1805 } // l3-te-topology-attributes 1806 } // l3-te-topology-attributes 1808 grouping l3-te-node-attributes { 1809 description 1810 "L3 TE node scope attributes"; 1811 container l3-te-node-attributes { 1812 must "/nw:networks/nw:network" 1813 + "[nw:network-id = current()/network-ref]/nw:network-types/" 1814 + "tet:te-topology" { 1815 error-message 1816 "The referenced network must be a TE topology."; 1817 description 1818 "The referenced network must be a TE topology."; 1819 } 1820 description 1821 "Containing TE node references"; 1822 uses nw:node-ref; 1823 } // l3-te 1824 } // l3-te-node-attributes 1825 grouping l3-te-tp-attributes { 1826 description 1827 "L3 TE termination point scope attributes"; 1828 container l3-te-tp-attributes { 1829 must "/nw:networks/nw:network" 1830 + "[nw:network-id = current()/network-ref]/nw:network-types/" 1831 + "tet:te-topology" { 1832 error-message 1833 "The referenced network must be a TE topology."; 1834 description 1835 "The referenced network must be a TE topology."; 1836 } 1837 description 1838 "Containing TE termination point references"; 1839 uses nt:tp-ref; 1840 } // l3-te 1841 } // l3-te-tp-attributes 1843 grouping l3-te-link-attributes { 1844 description 1845 "L3 TE link scope attributes"; 1846 container l3-te-link-attributes { 1847 must "/nw:networks/nw:network" 1848 + "[nw:network-id = current()/network-ref]/nw:network-types/" 1849 + "tet:te-topology" { 1850 error-message 1851 "The referenced network must be a TE topology."; 1852 description 1853 "The referenced network must be a TE topology."; 1854 } 1855 description 1856 "Containing TE link references"; 1857 uses nt:link-ref; 1858 } 1859 } // l3-te-link-attributes 1860 } 1861 1863 6.2. Packet TE YANG Types Module 1865 This module references [RFC2697], [RFC2698], [RFC4115], [RFC4124], 1866 [RFC4125], [RFC4126], [RFC4127], [RFC5481], [RFC7471], [RFC7823], 1867 [RFC8570], and [RFC8776]. 1869 file "ietf-te-packet-types@2021-07-11.yang" 1870 module ietf-te-packet-types { 1871 yang-version 1.1; 1872 namespace "urn:ietf:params:xml:ns:yang:ietf-te-packet-types"; 1873 prefix te-packet-types; 1875 /* Import TE generic types */ 1877 import ietf-te-types { 1878 prefix te-types; 1879 reference 1880 "RFC 8776: Common YANG Data Types for Traffic Engineering"; 1881 } 1883 organization 1884 "IETF Traffic Engineering Architecture and Signaling (TEAS) 1885 Working Group"; 1886 contact 1887 "WG Web: 1888 WG List: 1890 Editor: Tarek Saad 1891 1893 Editor: Rakesh Gandhi 1894 1896 Editor: Vishnu Pavan Beeram 1897 1899 Editor: Xufeng Liu 1900 1902 Editor: Igor Bryskin 1903 "; 1904 description 1905 "This YANG module contains a collection of generally useful YANG 1906 data type definitions specific to MPLS TE. The model fully 1907 conforms to the Network Management Datastore Architecture 1908 (NMDA). 1910 Copyright (c) 2021 IETF Trust and the persons identified as 1911 authors of the code. All rights reserved. 1913 Redistribution and use in source and binary forms, with or 1914 without modification, is permitted pursuant to, and subject to 1915 the license terms contained in, the Simplified BSD License set 1916 forth in Section 4.c of the IETF Trust's Legal Provisions 1917 Relating to IETF Documents 1918 (https://trustee.ietf.org/license-info). 1920 This version of this YANG module is part of RFC 8776; see the 1921 RFC itself for full legal notices."; 1923 revision 2021-07-11 { 1924 description 1925 "Added common TE packet identities: 1926 - bandwidth-profile-type. 1928 Added common TE packet types: 1929 - bandwidth-scientific-notation. 1931 Added common TE packet groupings: 1932 - te-packet-path-bandwidth; 1933 - te-packet-link-bandwidth."; 1934 reference 1935 "draft-busizheng-teas-yang-te-mpls-topology"; 1936 } 1938 revision 2020-06-10 { 1939 description 1940 "Latest revision of TE MPLS types."; 1941 reference 1942 "RFC 8776: Common YANG Data Types for Traffic Engineering"; 1943 } 1945 /* 1946 * Identities 1947 */ 1949 identity bandwidth-profile-type { 1950 description 1952 "Bandwidth Profile Types"; 1953 } 1955 identity mef-10-bwp { 1956 base bandwidth-profile-type; 1957 description 1958 "MEF 10 Bandwidth Profile"; 1959 } 1961 identity rfc-2697-bwp { 1962 base bandwidth-profile-type; 1963 description 1964 "RFC 2697 Bandwidth Profile"; 1965 } 1966 identity rfc-2698-bwp { 1967 base bandwidth-profile-type; 1968 description 1969 "RFC 2698 Bandwidth Profile"; 1970 } 1972 identity rfc-4115-bwp { 1973 base bandwidth-profile-type; 1974 description 1975 "RFC 4115 Bandwidth Profile"; 1976 } 1978 /* 1979 * Typedefs 1980 */ 1982 typedef te-bandwidth-requested-type { 1983 type enumeration { 1984 enum specified { 1985 description 1986 "Bandwidth is explicitly specified."; 1987 } 1988 enum auto { 1989 description 1990 "Bandwidth is automatically computed."; 1991 } 1992 } 1993 description 1994 "Enumerated type for specifying whether bandwidth is 1995 explicitly specified or automatically computed."; 1996 } 1998 typedef te-class-type { 1999 type uint8; 2000 description 2001 "Diffserv-TE Class-Type. Defines a set of Traffic Trunks 2002 crossing a link that is governed by a specific set of 2003 bandwidth constraints. Class-Type is used for the purposes 2004 of link bandwidth allocation, constraint-based routing, and 2005 admission control."; 2006 reference 2007 "RFC 4124: Protocol Extensions for Support of Diffserv-aware 2008 MPLS Traffic Engineering"; 2009 } 2011 typedef bc-type { 2012 type uint8 { 2013 range "0..7"; 2015 } 2016 description 2017 "Diffserv-TE bandwidth constraints as defined in RFC 4124."; 2018 reference 2019 "RFC 4124: Protocol Extensions for Support of Diffserv-aware 2020 MPLS Traffic Engineering"; 2021 } 2023 typedef bandwidth-kbps { 2024 type uint64; 2025 units "Kbps"; 2026 description 2027 "Bandwidth values, expressed in kilobits per second."; 2028 } 2030 typedef bandwidth-mbps { 2031 type uint64; 2032 units "Mbps"; 2033 description 2034 "Bandwidth values, expressed in megabits per second."; 2035 } 2037 typedef bandwidth-gbps { 2038 type uint64; 2039 units "Gbps"; 2040 description 2041 "Bandwidth values, expressed in gigabits per second."; 2042 } 2044 typedef bandwidth-scientific-notation { 2045 type string; 2046 units "bps"; 2047 description 2049 "Bandwidth values, expressed using the scientific notation 2050 (e.g., 10e3) in bits per second."; 2051 } 2053 identity backup-protection-type { 2054 description 2055 "Base identity for the backup protection type."; 2056 } 2058 identity backup-protection-link { 2059 base backup-protection-type; 2060 description 2061 "Backup provides link protection only."; 2062 } 2063 identity backup-protection-node-link { 2064 base backup-protection-type; 2065 description 2066 "Backup offers node (preferred) or link protection."; 2067 } 2069 identity bc-model-type { 2070 description 2071 "Base identity for the Diffserv-TE Bandwidth Constraints 2072 Model type."; 2073 reference 2074 "RFC 4124: Protocol Extensions for Support of Diffserv-aware 2075 MPLS Traffic Engineering"; 2076 } 2078 identity bc-model-rdm { 2079 base bc-model-type; 2080 description 2081 "Russian Dolls Bandwidth Constraints Model type."; 2082 reference 2083 "RFC 4127: Russian Dolls Bandwidth Constraints Model for 2084 Diffserv-aware MPLS Traffic Engineering"; 2085 } 2087 identity bc-model-mam { 2088 base bc-model-type; 2089 description 2090 "Maximum Allocation Bandwidth Constraints Model type."; 2091 reference 2092 "RFC 4125: Maximum Allocation Bandwidth Constraints Model for 2093 Diffserv-aware MPLS Traffic Engineering"; 2094 } 2096 identity bc-model-mar { 2097 base bc-model-type; 2098 description 2099 "Maximum Allocation with Reservation Bandwidth Constraints 2100 Model type."; 2101 reference 2102 "RFC 4126: Max Allocation with Reservation Bandwidth 2103 Constraints Model for Diffserv-aware MPLS Traffic Engineering 2104 & Performance Comparisons"; 2105 } 2107 /* 2108 * Groupings 2109 */ 2111 grouping performance-metrics-attributes-packet { 2112 description 2113 "Contains PM attributes."; 2114 uses te-types:performance-metrics-attributes { 2115 augment "performance-metrics-one-way" { 2116 leaf one-way-min-delay { 2117 type uint32 { 2118 range "0..16777215"; 2119 } 2120 description 2121 "One-way minimum delay or latency in microseconds."; 2122 } 2123 leaf one-way-min-delay-normality { 2124 type te-types:performance-metrics-normality; 2125 default "normal"; 2126 description 2127 "One-way minimum delay or latency normality."; 2128 } 2129 leaf one-way-max-delay { 2130 type uint32 { 2131 range "0..16777215"; 2132 } 2133 description 2134 "One-way maximum delay or latency in microseconds."; 2135 } 2136 leaf one-way-max-delay-normality { 2137 type te-types:performance-metrics-normality; 2138 default "normal"; 2139 description 2140 "One-way maximum delay or latency normality."; 2141 } 2142 leaf one-way-delay-variation { 2143 type uint32 { 2144 range "0..16777215"; 2145 } 2146 description 2147 "One-way delay variation in microseconds."; 2148 reference 2149 "RFC 5481: Packet Delay Variation Applicability 2150 Statement, Section 4.2"; 2151 } 2152 leaf one-way-delay-variation-normality { 2153 type te-types:performance-metrics-normality; 2154 default "normal"; 2155 description 2156 "One-way delay variation normality."; 2157 reference 2158 "RFC 7471: OSPF Traffic Engineering (TE) Metric 2159 Extensions 2160 RFC 7823: Performance-Based Path Selection for 2161 Explicitly Routed Label Switched Paths (LSPs) Using 2162 TE Metric Extensions 2163 RFC 8570: IS-IS Traffic Engineering (TE) Metric 2164 Extensions"; 2165 } 2166 leaf one-way-packet-loss { 2167 type decimal64 { 2168 fraction-digits 6; 2169 range "0..50.331642"; 2170 } 2171 description 2172 "One-way packet loss as a percentage of the total traffic 2173 sent over a configurable interval. The finest precision 2174 is 0.000003%, where the maximum is 50.331642%."; 2175 reference 2176 "RFC 8570: IS-IS Traffic Engineering (TE) Metric 2177 Extensions, Section 4.4"; 2178 } 2179 leaf one-way-packet-loss-normality { 2180 type te-types:performance-metrics-normality; 2181 default "normal"; 2182 description 2183 "Packet loss normality."; 2184 reference 2185 "RFC 7471: OSPF Traffic Engineering (TE) Metric 2186 Extensions 2187 RFC 7823: Performance-Based Path Selection for 2188 Explicitly Routed Label Switched Paths (LSPs) Using 2189 TE Metric Extensions 2190 RFC 8570: IS-IS Traffic Engineering (TE) Metric 2191 Extensions"; 2192 } 2193 description 2194 "PM one-way packet-specific augmentation for a generic PM 2195 grouping."; 2196 } 2197 augment "performance-metrics-two-way" { 2198 leaf two-way-min-delay { 2199 type uint32 { 2200 range "0..16777215"; 2201 } 2202 default "0"; 2203 description 2204 "Two-way minimum delay or latency in microseconds."; 2205 } 2206 leaf two-way-min-delay-normality { 2207 type te-types:performance-metrics-normality; 2208 default "normal"; 2209 description 2210 "Two-way minimum delay or latency normality."; 2211 reference 2212 "RFC 7471: OSPF Traffic Engineering (TE) Metric 2213 Extensions 2214 RFC 7823: Performance-Based Path Selection for 2215 Explicitly Routed Label Switched Paths (LSPs) Using 2216 TE Metric Extensions 2217 RFC 8570: IS-IS Traffic Engineering (TE) Metric 2218 Extensions"; 2219 } 2220 leaf two-way-max-delay { 2221 type uint32 { 2222 range "0..16777215"; 2223 } 2224 default "0"; 2225 description 2226 "Two-way maximum delay or latency in microseconds."; 2227 } 2228 leaf two-way-max-delay-normality { 2229 type te-types:performance-metrics-normality; 2230 default "normal"; 2231 description 2232 "Two-way maximum delay or latency normality."; 2233 reference 2234 "RFC 7471: OSPF Traffic Engineering (TE) Metric 2235 Extensions 2236 RFC 7823: Performance-Based Path Selection for 2237 Explicitly Routed Label Switched Paths (LSPs) Using 2238 TE Metric Extensions 2239 RFC 8570: IS-IS Traffic Engineering (TE) Metric 2240 Extensions"; 2241 } 2242 leaf two-way-delay-variation { 2243 type uint32 { 2244 range "0..16777215"; 2245 } 2246 default "0"; 2247 description 2248 "Two-way delay variation in microseconds."; 2249 reference 2250 "RFC 5481: Packet Delay Variation Applicability 2251 Statement, Section 4.2"; 2252 } 2253 leaf two-way-delay-variation-normality { 2254 type te-types:performance-metrics-normality; 2255 default "normal"; 2256 description 2257 "Two-way delay variation normality."; 2258 reference 2259 "RFC 7471: OSPF Traffic Engineering (TE) Metric 2260 Extensions 2261 RFC 7823: Performance-Based Path Selection for 2262 Explicitly Routed Label Switched Paths (LSPs) Using 2263 TE Metric Extensions 2264 RFC 8570: IS-IS Traffic Engineering (TE) Metric 2265 Extensions"; 2266 } 2267 leaf two-way-packet-loss { 2268 type decimal64 { 2269 fraction-digits 6; 2270 range "0..50.331642"; 2271 } 2272 default "0"; 2273 description 2274 "Two-way packet loss as a percentage of the total traffic 2275 sent over a configurable interval. The finest precision 2276 is 0.000003%."; 2277 } 2278 leaf two-way-packet-loss-normality { 2279 type te-types:performance-metrics-normality; 2280 default "normal"; 2281 description 2282 "Two-way packet loss normality."; 2283 } 2284 description 2285 "PM two-way packet-specific augmentation for a generic PM 2286 grouping."; 2287 reference 2288 "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions 2289 RFC 7823: Performance-Based Path Selection for 2290 Explicitly Routed Label Switched Paths (LSPs) Using 2291 TE Metric Extensions 2292 RFC 8570: IS-IS Traffic Engineering (TE) Metric 2293 Extensions"; 2294 } 2295 } 2296 } 2298 grouping one-way-performance-metrics-packet { 2299 description 2300 "One-way packet PM throttle grouping."; 2301 leaf one-way-min-delay { 2302 type uint32 { 2303 range "0..16777215"; 2304 } 2305 default "0"; 2306 description 2307 "One-way minimum delay or latency in microseconds."; 2308 } 2309 leaf one-way-max-delay { 2310 type uint32 { 2311 range "0..16777215"; 2312 } 2313 default "0"; 2314 description 2315 "One-way maximum delay or latency in microseconds."; 2316 } 2317 leaf one-way-delay-variation { 2318 type uint32 { 2319 range "0..16777215"; 2320 } 2321 default "0"; 2322 description 2323 "One-way delay variation in microseconds."; 2324 } 2325 leaf one-way-packet-loss { 2326 type decimal64 { 2327 fraction-digits 6; 2328 range "0..50.331642"; 2329 } 2330 default "0"; 2331 description 2332 "One-way packet loss as a percentage of the total traffic 2333 sent over a configurable interval. The finest precision is 2334 0.000003%."; 2335 } 2336 } 2338 grouping two-way-performance-metrics-packet { 2339 description 2340 "Two-way packet PM throttle grouping."; 2341 leaf two-way-min-delay { 2342 type uint32 { 2343 range "0..16777215"; 2344 } 2345 default "0"; 2346 description 2347 "Two-way minimum delay or latency in microseconds."; 2348 } 2349 leaf two-way-max-delay { 2350 type uint32 { 2351 range "0..16777215"; 2352 } 2353 default "0"; 2354 description 2355 "Two-way maximum delay or latency in microseconds."; 2356 } 2357 leaf two-way-delay-variation { 2358 type uint32 { 2359 range "0..16777215"; 2360 } 2361 default "0"; 2362 description 2363 "Two-way delay variation in microseconds."; 2364 } 2365 leaf two-way-packet-loss { 2366 type decimal64 { 2367 fraction-digits 6; 2368 range "0..50.331642"; 2369 } 2370 default "0"; 2371 description 2372 "Two-way packet loss as a percentage of the total traffic 2373 sent over a configurable interval. The finest precision is 2374 0.000003%."; 2375 } 2376 } 2378 grouping performance-metrics-throttle-container-packet { 2379 description 2380 "Packet PM threshold grouping."; 2381 uses te-types:performance-metrics-throttle-container { 2382 augment "throttle/threshold-out" { 2383 uses one-way-performance-metrics-packet; 2384 uses two-way-performance-metrics-packet; 2385 description 2386 "PM threshold-out packet augmentation for a 2387 generic grouping."; 2388 } 2389 augment "throttle/threshold-in" { 2390 uses one-way-performance-metrics-packet; 2391 uses two-way-performance-metrics-packet; 2392 description 2393 "PM threshold-in packet augmentation for a 2394 generic grouping."; 2395 } 2396 augment "throttle/threshold-accelerated-advertisement" { 2397 uses one-way-performance-metrics-packet; 2398 uses two-way-performance-metrics-packet; 2399 description 2400 "PM accelerated advertisement packet augmentation for a 2401 generic grouping."; 2402 } 2403 } 2404 } 2406 grouping te-packet-path-bandwidth { 2407 description 2408 "Path bandwidth for Packet. "; 2409 leaf bandwidth-profile-name{ 2410 type string; 2411 description "Name of Bandwidth Profile."; 2412 } 2413 leaf bandwidth-profile-type { 2414 type identityref { 2415 base bandwidth-profile-type; 2416 } 2417 description "Type of Bandwidth Profile."; 2418 } 2420 leaf cir { 2421 type uint64; 2422 description 2423 "Committed Information Rate in Kbps"; 2424 } 2426 leaf eir { 2427 type uint64; 2428 /* 2429 Need to indicate that EIR is not supported by RFC 2697 2431 must 2433 '../bw-profile-type = "etht-types:mef-10-bwp" or ' + 2434 '../bw-profile-type = "etht-types:rfc-2698-bwp" or ' + 2435 '../bw-profile-type = "etht-types:rfc-4115-bwp"' 2437 must 2438 '../bw-profile-type != "etht-types:rfc-2697-bwp"' 2439 */ 2440 description 2441 "Excess Information Rate in Kbps 2442 In case of RFC 2698, PIR = CIR + EIR"; 2443 } 2445 leaf cbs { 2446 type uint64; 2447 description 2448 "Committed Burst Size in in KBytes"; 2449 } 2451 leaf ebs { 2452 type uint64; 2453 description 2454 "Excess Burst Size in KBytes. 2455 In case of RFC 2698, PBS = CBS + EBS"; 2456 } 2457 } 2459 grouping te-packet-link-bandwidth { 2460 description 2461 "Link Bandwidth for Packet. "; 2462 leaf packet-bandwidth { 2463 type bandwidth-scientific-notation; 2464 description 2465 "Available bandwith value expressed in kilobits per 2466 second"; 2467 } 2468 } 2469 } 2470 2472 6.3. Packet Switching TE Topology Module 2474 This module references [RFC7471], [RFC7823], [RFC8294], [RFC8345], 2475 [RFC8346]. [RFC8570], [RFC8776], and [RFC8795]. 2477 file "ietf-te-topology-packet@2021-07-11.yang" 2478 module ietf-te-topology-packet { 2479 yang-version 1.1; 2480 namespace "urn:ietf:params:xml:ns:yang:ietf-te-topology-packet"; 2482 prefix "tet-pkt"; 2484 import ietf-network { 2485 prefix "nw"; 2486 reference 2487 "RFC 8345: A YANG Data Model for Network Topologies"; 2488 } 2490 import ietf-network-topology { 2491 prefix "nt"; 2492 reference 2493 "RFC 8345: A YANG Data Model for Network Topologies"; 2494 } 2496 import ietf-routing-types { 2497 prefix "rt-types"; 2498 reference 2499 "RFC 8294: Common YANG Data Types for the Routing Area"; 2500 } 2502 import ietf-te-topology { 2503 prefix "tet"; 2504 reference 2505 "I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic 2506 Engineering (TE) Topologies"; 2507 } 2509 import ietf-te-types { 2510 prefix "te-types"; 2511 reference 2512 "I-D.ietf-teas-yang-te-types: Traffic Engineering Common YANG 2513 Types"; 2514 } 2516 import ietf-te-packet-types { 2517 prefix "te-packet-types"; 2518 reference 2519 "I-D.ietf-teas-yang-te-types: Traffic Engineering Common YANG 2520 Types"; 2521 } 2523 organization 2524 "Traffic Engineering Architecture and Signaling (TEAS) 2525 Working Group"; 2527 contact 2528 "WG Web: 2529 WG List: 2531 Editor: Xufeng Liu 2532 2534 Editor: Igor Bryskin 2535 2537 Editor: Vishnu Pavan Beeram 2538 2540 Editor: Tarek Saad 2541 2543 Editor: Himanshu Shah 2544 2546 Editor: Oscar Gonzalez De Dios 2547 "; 2549 description 2550 "YANG data model for representing and manipulating PSC (Packet 2551 Switching) TE Topologies. 2553 Copyright (c) 2018 IETF Trust and the persons identified as 2554 authors of the code. All rights reserved. 2556 Redistribution and use in source and binary forms, with or 2557 without modification, is permitted pursuant to, and subject to 2558 the license terms contained in, the Simplified BSD License set 2559 forth in Section 4.c of the IETF Trust's Legal Provisions 2560 Relating to IETF Documents 2561 (http://trustee.ietf.org/license-info). 2563 This version of this YANG module is part of RFC XXXX; see the 2564 RFC itself for full legal notices."; 2566 revision 2021-07-11 { 2567 description 2568 "Initial revision"; 2569 reference 2570 "RFC XXXX: YANG Data Model for Layer 3 TE Topologies"; 2571 } 2573 /* 2574 * Features 2575 */ 2577 feature te-performance-metric { 2578 description 2579 "This feature indicates that the system supports 2580 TE performance metric."; 2581 reference 2582 "RFC7471: OSPF Traffic Engineering (TE) Metric Extensions. 2583 RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions. 2584 RFC7823: Performance-Based Path Selection for Explicitly 2585 Routed Label Switched Paths (LSPs) Using TE Metric 2586 Extensions"; 2587 } 2588 /* 2589 * Groupings 2590 */ 2591 grouping packet-switch-capable-container { 2592 description 2593 "The container of packet switch capable attributes."; 2594 container packet-switch-capable { 2595 description 2596 "Interface has packet-switching capabilities."; 2597 leaf minimum-lsp-bandwidth { 2598 type rt-types:bandwidth-ieee-float32; 2599 description 2600 "Minimum LSP Bandwidth. Units in bytes per second"; 2601 } 2602 leaf interface-mtu { 2603 type uint16; 2604 description 2605 "Interface MTU."; 2606 } 2607 } 2608 } 2610 /* 2611 * Augmentations 2612 */ 2613 /* Augmentations to network-types */ 2614 augment "/nw:networks/nw:network/nw:network-types/" 2615 + "tet:te-topology" { 2616 description 2617 "Defines the packet TE topology type."; 2618 container packet { 2619 presence "Indicates packet TE topology."; 2620 description 2621 "Its presence identifies the packet TE topology type."; 2622 } 2623 } 2625 /* Augmentations to connectivity-matrix */ 2626 augment "/nw:networks/nw:network/nw:node/tet:te/" 2627 + "tet:te-node-attributes/tet:connectivity-matrices" { 2628 when "../../../../nw:network-types/tet:te-topology/" 2629 + "tet-pkt:packet" { 2630 description 2631 "Augment only for packet TE topology"; 2632 } 2633 description 2634 "Parameters for PSC TE topology."; 2635 uses te-packet-types:performance-metrics-attributes-packet { 2636 if-feature te-performance-metric; 2637 refine performance-metrics-one-way { 2638 config false; 2639 } 2640 refine performance-metrics-two-way { 2641 config false; 2642 } 2643 } 2644 uses 2645 te-packet-types:performance-metrics-throttle-container-packet { 2646 if-feature te-performance-metric; 2647 } 2648 } 2650 augment "/nw:networks/nw:network/nw:node/tet:te/" 2651 + "tet:te-node-attributes/tet:connectivity-matrices/" 2652 + "tet:connectivity-matrix" { 2653 when "../../../../../nw:network-types/tet:te-topology/" 2654 + "tet-pkt:packet" { 2655 description 2656 "Augment only for packet TE topology"; 2657 } 2658 description 2659 "Parameters for PSC TE topology."; 2660 uses te-packet-types:performance-metrics-attributes-packet { 2661 if-feature te-performance-metric; 2662 refine performance-metrics-one-way { 2663 config false; 2664 } 2665 refine performance-metrics-two-way { 2666 config false; 2667 } 2668 } 2669 uses 2670 te-packet-types:performance-metrics-throttle-container-packet { 2671 if-feature te-performance-metric; 2672 } 2673 } 2675 augment "/nw:networks/nw:network/nw:node/tet:te/" 2676 + "tet:information-source-entry/tet:connectivity-matrices" { 2677 when "../../../../nw:network-types/tet:te-topology/" 2678 + "tet-pkt:packet" { 2679 description 2680 "Augment only for packet TE topology"; 2681 } 2682 description 2683 "Parameters for PSC TE topology."; 2685 uses te-packet-types:performance-metrics-attributes-packet { 2686 if-feature te-performance-metric; 2687 } 2688 uses 2689 te-packet-types:performance-metrics-throttle-container-packet { 2690 if-feature te-performance-metric; 2691 } 2692 } 2694 augment "/nw:networks/nw:network/nw:node/tet:te/" 2695 + "tet:information-source-entry/tet:connectivity-matrices/" 2696 + "tet:connectivity-matrix" { 2697 when "../../../../../nw:network-types/tet:te-topology/" 2698 + "tet-pkt:packet" { 2699 description 2700 "Augment only for packet TE topology"; 2701 } 2702 description 2703 "Parameters for PSC TE topology."; 2704 uses te-packet-types:performance-metrics-attributes-packet { 2705 if-feature te-performance-metric; 2706 } 2707 uses 2708 te-packet-types:performance-metrics-throttle-container-packet { 2709 if-feature te-performance-metric; 2710 } 2711 } 2713 /* Augmentations to tunnel-termination-point */ 2714 augment "/nw:networks/nw:network/nw:node/tet:te/" 2715 + "tet:tunnel-termination-point/" 2716 + "tet:local-link-connectivities" { 2717 when "../../../../nw:network-types/tet:te-topology/" 2718 + "tet-pkt:packet" { 2719 description 2720 "Augment only for packet TE topology"; 2721 } 2722 description 2723 "Parameters for PSC TE topology."; 2724 uses te-packet-types:performance-metrics-attributes-packet { 2725 if-feature te-performance-metric; 2726 refine performance-metrics-one-way { 2727 config false; 2728 } 2729 refine performance-metrics-two-way { 2730 config false; 2731 } 2732 } 2733 uses 2734 te-packet-types:performance-metrics-throttle-container-packet { 2735 if-feature te-performance-metric; 2736 } 2737 } 2739 augment "/nw:networks/nw:network/nw:node/tet:te/" 2740 + "tet:tunnel-termination-point/" 2741 + "tet:local-link-connectivities/" 2742 + "tet:local-link-connectivity" { 2743 when "../../../../../nw:network-types/tet:te-topology/" 2744 + "tet-pkt:packet" { 2745 description 2746 "Augment only for packet TE topology"; 2747 } 2748 description 2749 "Parameters for PSC TE topology."; 2750 uses te-packet-types:performance-metrics-attributes-packet { 2751 if-feature te-performance-metric; 2752 refine performance-metrics-one-way { 2753 config false; 2754 } 2755 refine performance-metrics-two-way { 2756 config false; 2757 } 2758 } 2759 uses 2760 te-packet-types:performance-metrics-throttle-container-packet { 2761 if-feature te-performance-metric; 2762 } 2763 } 2765 /* Augmentations to te-link-attributes */ 2766 augment "/nw:networks/tet:te/tet:templates/" 2767 + "tet:link-template/tet:te-link-attributes" { 2768 when "tet:interface-switching-capability " 2769 + "[tet:switching-capability = 'te-types:switching-psc1']" { 2770 description 2771 "Valid only for PSC"; 2772 } 2773 description 2774 "Parameters for PSC TE topology."; 2775 uses te-packet-types:performance-metrics-attributes-packet { 2776 if-feature te-performance-metric; 2777 refine performance-metrics-one-way { 2778 config false; 2779 } 2780 refine performance-metrics-two-way { 2781 config false; 2782 } 2783 } 2784 uses 2785 te-packet-types:performance-metrics-throttle-container-packet { 2786 if-feature te-performance-metric; 2787 } 2788 } 2790 augment "/nw:networks/nw:network/nt:link/tet:te/" 2791 + "tet:te-link-attributes" { 2792 when "(../../../nw:network-types/tet:te-topology/tet-pkt:packet)" 2793 + " and (tet:interface-switching-capability " 2794 + "[tet:switching-capability = 'te-types:switching-psc1'])" { 2795 description 2796 "Valid only for PSC"; 2797 } 2798 description 2799 "Parameters for PSC TE topology."; 2800 uses te-packet-types:performance-metrics-attributes-packet { 2801 if-feature te-performance-metric; 2802 refine performance-metrics-one-way { 2803 config false; 2804 } 2805 refine performance-metrics-two-way { 2806 config false; 2807 } 2808 } 2809 uses 2810 te-packet-types:performance-metrics-throttle-container-packet { 2811 if-feature te-performance-metric; 2812 } 2813 } 2815 augment "/nw:networks/nw:network/nt:link/tet:te/" 2816 + "tet:information-source-entry" { 2817 when "(../../../nw:network-types/tet:te-topology/tet-pkt:packet)" 2818 + " and (tet:interface-switching-capability " 2819 + "[tet:switching-capability = 'te-types:switching-psc1'])" { 2820 description 2821 "Valid only for PSC"; 2822 } 2823 description 2824 "Parameters for PSC TE topology."; 2825 uses te-packet-types:performance-metrics-attributes-packet { 2826 if-feature te-performance-metric; 2827 } 2828 uses 2829 te-packet-types:performance-metrics-throttle-container-packet { 2830 if-feature te-performance-metric; 2831 } 2832 } 2834 /* Augmentations to interface-switching-capability */ 2835 augment "/nw:networks/tet:te/tet:templates/" 2836 + "tet:link-template/tet:te-link-attributes/" 2837 + "tet:interface-switching-capability" { 2838 when "tet:switching-capability = 'te-types:switching-psc1' " { 2839 description 2840 "Valid only for PSC"; 2841 } 2842 description 2843 "Parameters for PSC TE topology."; 2844 uses packet-switch-capable-container; 2845 } 2847 augment "/nw:networks/nw:network/nt:link/tet:te/" 2848 + "tet:te-link-attributes/" 2849 + "tet:interface-switching-capability" { 2850 when "(../../../../nw:network-types/tet:te-topology/" 2851 + "tet-pkt:packet) and " 2852 + "(tet:switching-capability = 'te-types:switching-psc1')" { 2853 description 2854 "Valid only for PSC"; 2855 } 2856 description 2857 "Parameters for PSC TE topology."; 2858 uses packet-switch-capable-container; 2859 } 2861 augment "/nw:networks/nw:network/nt:link/tet:te/" 2862 + "tet:information-source-entry/" 2863 + "tet:interface-switching-capability" { 2864 when "(../../../../nw:network-types/tet:te-topology/" 2865 + "tet-pkt:packet) and " 2866 + "(tet:switching-capability = 'te-types:switching-psc1')" { 2867 description 2868 "Valid only for PSC"; 2869 } 2870 description 2871 "Parameters for PSC TE topology."; 2872 uses packet-switch-capable-container; 2873 } 2875 /* 2876 * Augment TE bandwidth 2877 */ 2879 augment "/nw:networks/nw:network/nw:node/nt:termination-point/" 2880 + "tet:te/" 2881 + "tet:interface-switching-capability/tet:max-lsp-bandwidth/" 2882 + "tet:te-bandwidth/tet:technology" { 2883 when "../../../../../../nw:network-types/tet:te-topology/" 2884 + "tet-pkt:packet" { 2885 description 2886 "Augmentation parameters apply only for networks with 2887 Packet TE topology type."; 2888 } 2889 description 2890 "Augment maximum LSP TE bandwidth for the link termination 2891 point (LTP)."; 2892 case packet { 2893 uses te-packet-types:te-packet-path-bandwidth; 2894 } 2895 } 2897 augment "/nw:networks/nw:network/nw:node/tet:te/" 2898 + "tet:te-node-attributes/tet:connectivity-matrices/" 2899 + "tet:path-constraints/tet:te-bandwidth/tet:technology" { 2900 when "../../../../../../nw:network-types/tet:te-topology/" 2901 + "tet-pkt:packet" { 2902 description 2903 "Augmentation parameters apply only for networks with 2904 Packet TE topology type."; 2905 } 2906 description 2907 "Augment TE bandwidth path constraints of the TE node 2908 connectivity matrices."; 2909 case packet { 2910 uses te-packet-types:te-packet-link-bandwidth; 2911 } 2912 } 2914 augment "/nw:networks/nw:network/nw:node/tet:te/" 2915 + "tet:te-node-attributes/tet:connectivity-matrices/" 2916 + "tet:connectivity-matrix/" 2917 + "tet:path-constraints/tet:te-bandwidth/tet:technology" { 2918 when "../../../../../../../nw:network-types/tet:te-topology/" 2919 + "tet-pkt:packet" { 2920 description 2921 "Augmentation parameters apply only for networks with 2922 Packet TE topology type."; 2923 } 2924 description 2925 "Augment TE bandwidth path constraints of the 2926 connectivity matrix entry."; 2927 case packet { 2928 uses te-packet-types:te-packet-link-bandwidth; 2929 } 2930 } 2932 augment "/nw:networks/nw:network/nw:node/tet:te/" 2933 + "tet:information-source-entry/tet:connectivity-matrices/" 2934 + "tet:path-constraints/tet:te-bandwidth/tet:technology" { 2935 when "../../../../../../nw:network-types/tet:te-topology/" 2936 + "tet-pkt:packet" { 2937 description 2938 "Augmentation parameters apply only for networks with 2939 Packet TE topology type."; 2940 } 2941 description 2942 "Augment TE bandwidth path constraints of the TE node 2943 connectivity matrices information source."; 2944 case packet { 2945 uses te-packet-types:te-packet-link-bandwidth; 2946 } 2947 } 2949 augment "/nw:networks/nw:network/nw:node/tet:te/" 2950 + "tet:information-source-entry/tet:connectivity-matrices/" 2951 + "tet:connectivity-matrix/" 2952 + "tet:path-constraints/tet:te-bandwidth/tet:technology" { 2953 when "../../../../../../../nw:network-types/tet:te-topology/" 2954 + "tet-pkt:packet" { 2955 description 2956 "Augmentation parameters apply only for networks with 2957 Packet TE topology type."; 2958 } 2959 description 2960 "Augment TE bandwidth path constraints of the 2961 connectivity matrix entry information source"; 2962 case packet { 2963 uses te-packet-types:te-packet-link-bandwidth; 2964 } 2965 } 2967 augment "/nw:networks/nw:network/nw:node/tet:te/" 2968 + "tet:tunnel-termination-point/" 2969 + "tet:client-layer-adaptation/tet:switching-capability/" 2970 + "tet:te-bandwidth/tet:technology" { 2971 when "../../../../../../nw:network-types/tet:te-topology/" 2972 + "tet-pkt:packet" { 2974 description 2975 "Augmentation parameters apply only for networks with 2976 Packet TE topology type."; 2977 } 2978 description 2979 "Augment client TE bandwidth of the tunnel termination point 2980 (TTP)"; 2981 case packet { 2982 uses te-packet-types:te-packet-link-bandwidth; 2983 } 2984 } 2986 augment "/nw:networks/nw:network/nw:node/tet:te/" 2987 + "tet:tunnel-termination-point/" 2988 + "tet:local-link-connectivities/tet:path-constraints/" 2989 + "tet:te-bandwidth/tet:technology" { 2990 when "../../../../../../nw:network-types/tet:te-topology/" 2991 + "tet-pkt:packet" { 2992 description 2993 "Augmentation parameters apply only for networks with 2994 Packet TE topology type."; 2995 } 2996 description 2997 "Augment TE bandwidth path constraints for the TTP 2998 Local Link Connectivities."; 2999 case packet { 3000 uses te-packet-types:te-packet-link-bandwidth; 3001 } 3002 } 3004 augment "/nw:networks/nw:network/nw:node/tet:te/" 3005 + "tet:tunnel-termination-point/" 3006 + "tet:local-link-connectivities/" 3007 + "tet:local-link-connectivity/tet:path-constraints/" 3008 + "tet:te-bandwidth/tet:technology" { 3009 when "../../../../../../../nw:network-types/tet:te-topology/" 3010 + "tet-pkt:packet" { 3011 description 3012 "Augmentation parameters apply only for networks with 3013 Packet TE topology type."; 3014 } 3015 description 3016 "Augment TE bandwidth path constraints for the TTP 3017 Local Link Connectivity entry."; 3018 case packet { 3019 uses te-packet-types:te-packet-link-bandwidth; 3020 } 3021 } 3022 augment "/nw:networks/nw:network/nt:link/tet:te/" 3023 + "tet:te-link-attributes/" 3024 + "tet:interface-switching-capability/tet:max-lsp-bandwidth/" 3025 + "tet:te-bandwidth/tet:technology" { 3026 when "../../../../../../nw:network-types/tet:te-topology/" 3027 + "tet-pkt:packet" { 3028 description 3029 "Augmentation parameters apply only for networks with 3030 Packet TE topology type."; 3031 } 3032 description 3033 "Augment maximum LSP TE bandwidth for the TE link."; 3034 case packet { 3035 uses te-packet-types:te-packet-path-bandwidth; 3036 } 3037 } 3039 augment "/nw:networks/nw:network/nt:link/tet:te/" 3040 + "tet:te-link-attributes/" 3041 + "tet:max-link-bandwidth/" 3042 + "tet:te-bandwidth/tet:technology" { 3043 when "../../../../../nw:network-types/tet:te-topology/" 3044 + "tet-pkt:packet" { 3045 description 3046 "Augmentation parameters apply only for networks with 3047 Packet TE topology type."; 3048 } 3049 description 3050 "Augment maximum TE bandwidth for the TE link"; 3051 case packet { 3052 uses te-packet-types:te-packet-link-bandwidth; 3053 } 3054 } 3056 augment "/nw:networks/nw:network/nt:link/tet:te/" 3057 + "tet:te-link-attributes/" 3058 + "tet:max-resv-link-bandwidth/" 3059 + "tet:te-bandwidth/tet:technology" { 3060 when "../../../../../nw:network-types/tet:te-topology/" 3061 + "tet-pkt:packet" { 3062 description 3063 "Augmentation parameters apply only for networks with 3064 Packet TE topology type."; 3065 } 3066 description 3067 "Augment maximum reservable TE bandwidth for the TE link"; 3068 case packet { 3069 uses te-packet-types:te-packet-link-bandwidth; 3071 } 3072 } 3074 augment "/nw:networks/nw:network/nt:link/tet:te/" 3075 + "tet:te-link-attributes/" 3076 + "tet:unreserved-bandwidth/" 3077 + "tet:te-bandwidth/tet:technology" { 3078 when "../../../../../nw:network-types/tet:te-topology/" 3079 + "tet-pkt:packet" { 3080 description 3081 "Augmentation parameters apply only for networks with 3082 Packet TE topology type."; 3083 } 3084 description 3085 "Augment unreserved TE bandwidth for the TE Link"; 3086 case packet { 3087 uses te-packet-types:te-packet-link-bandwidth; 3088 } 3089 } 3091 augment "/nw:networks/nw:network/nt:link/tet:te/" 3092 + "tet:information-source-entry/" 3093 + "tet:interface-switching-capability/" 3094 + "tet:max-lsp-bandwidth/" 3095 + "tet:te-bandwidth/tet:technology" { 3096 when "../../../../../../nw:network-types/tet:te-topology/" 3097 + "tet-pkt:packet" { 3098 description 3099 "Augmentation parameters apply only for networks with 3100 Packet TE topology type."; 3101 } 3102 description 3103 "Augment maximum LSP TE bandwidth for the TE link 3104 information source"; 3105 case packet { 3106 uses te-packet-types:te-packet-path-bandwidth; 3107 } 3108 } 3110 augment "/nw:networks/nw:network/nt:link/tet:te/" 3111 + "tet:information-source-entry/" 3112 + "tet:max-link-bandwidth/" 3113 + "tet:te-bandwidth/tet:technology" { 3114 when "../../../../../nw:network-types/tet:te-topology/" 3115 + "tet-pkt:packet" { 3116 description 3117 "Augmentation parameters apply only for networks with 3118 Packet TE topology type."; 3120 } 3121 description 3122 "Augment maximum TE bandwidth for the TE link 3123 information source"; 3124 case packet { 3125 uses te-packet-types:te-packet-link-bandwidth; 3126 } 3127 } 3129 augment "/nw:networks/nw:network/nt:link/tet:te/" 3130 + "tet:information-source-entry/" 3131 + "tet:max-resv-link-bandwidth/" 3132 + "tet:te-bandwidth/tet:technology" { 3133 when "../../../../../nw:network-types/tet:te-topology/" 3134 + "tet-pkt:packet" { 3135 description 3136 "Augmentation parameters apply only for networks with 3137 Packet TE topology type."; 3138 } 3139 description 3140 "Augment maximum reservable TE bandwidth for the TE link 3141 information-source"; 3142 case packet { 3143 uses te-packet-types:te-packet-link-bandwidth; 3144 } 3145 } 3147 augment "/nw:networks/nw:network/nt:link/tet:te/" 3148 + "tet:information-source-entry/" 3149 + "tet:unreserved-bandwidth/" 3150 + "tet:te-bandwidth/tet:technology" { 3151 when "../../../../../nw:network-types/tet:te-topology/" 3152 + "tet-pkt:packet" { 3153 description 3154 "Augmentation parameters apply only for networks with 3155 Packet TE topology type."; 3156 } 3157 description 3158 "Augment unreserved TE bandwidth of the TE link 3159 information source"; 3160 case packet { 3161 uses te-packet-types:te-packet-link-bandwidth; 3162 } 3163 } 3165 augment "/nw:networks/tet:te/tet:templates/" 3166 + "tet:link-template/tet:te-link-attributes/" 3167 + "tet:interface-switching-capability/" 3168 + "tet:max-lsp-bandwidth/" 3169 + "tet:te-bandwidth/tet:technology" { 3170 description 3171 "Augment maximum LSP TE bandwidth of the TE link 3172 template"; 3173 case packet { 3174 uses te-packet-types:te-packet-path-bandwidth; 3175 } 3176 } 3178 augment "/nw:networks/tet:te/tet:templates/" 3179 + "tet:link-template/tet:te-link-attributes/" 3180 + "tet:max-link-bandwidth/" 3181 + "tet:te-bandwidth/tet:technology" { 3182 description 3183 "Augment maximum TE bandwidth the TE link template"; 3184 case packet { 3185 uses te-packet-types:te-packet-link-bandwidth; 3186 } 3187 } 3189 augment "/nw:networks/tet:te/tet:templates/" 3190 + "tet:link-template/tet:te-link-attributes/" 3191 + "tet:max-resv-link-bandwidth/" 3192 + "tet:te-bandwidth/tet:technology" { 3193 description 3194 "Augment maximum reservable TE bandwidth for the TE link 3195 template."; 3196 case packet { 3197 uses te-packet-types:te-packet-link-bandwidth; 3198 } 3199 } 3201 augment "/nw:networks/tet:te/tet:templates/" 3202 + "tet:link-template/tet:te-link-attributes/" 3203 + "tet:unreserved-bandwidth/" 3204 + "tet:te-bandwidth/tet:technology" { 3205 description 3206 "Augment unreserved TE bandwidth the TE link template"; 3207 case packet { 3208 uses te-packet-types:te-packet-link-bandwidth; 3209 } 3210 } 3211 } 3212 3214 7. IANA Considerations 3216 RFC Ed.: In this section, replace all occurrences of 'XXXX' with the 3217 actual RFC number (and remove this note). 3219 This document registers the following namespace URIs in the IETF XML 3220 registry [RFC3688]: 3222 -------------------------------------------------------------------- 3223 URI: urn:ietf:params:xml:ns:yang:ietf-l3-te-topology 3224 Registrant Contact: The IESG. 3225 XML: N/A, the requested URI is an XML namespace. 3226 -------------------------------------------------------------------- 3228 -------------------------------------------------------------------- 3229 URI: urn:ietf:params:xml:ns:yang:ietf-l3-te-topology-state 3230 Registrant Contact: The IESG. 3231 XML: N/A, the requested URI is an XML namespace. 3232 -------------------------------------------------------------------- 3234 -------------------------------------------------------------------- 3235 URI: urn:ietf:params:xml:ns:yang:ietf-te-topology-packet 3236 Registrant Contact: The IESG. 3237 XML: N/A, the requested URI is an XML namespace. 3238 -------------------------------------------------------------------- 3240 -------------------------------------------------------------------- 3241 URI: urn:ietf:params:xml:ns:yang:ietf-te-topology-packet-state 3242 Registrant Contact: The IESG. 3243 XML: N/A, the requested URI is an XML namespace. 3244 -------------------------------------------------------------------- 3246 This document registers the following YANG modules in the YANG Module 3247 Names registry [RFC6020]: 3249 -------------------------------------------------------------------- 3250 name: ietf-l3-te-topology 3251 namespace: urn:ietf:params:xml:ns:yang:ietf-l3-te-topology 3252 prefix: l3tet 3253 reference: RFC XXXX 3254 -------------------------------------------------------------------- 3256 -------------------------------------------------------------------- 3257 name: ietf-l3-te-topology-state 3258 namespace: urn:ietf:params:xml:ns:yang:ietf-l3-te-topology-state 3259 prefix: l3tet-s 3260 reference: RFC XXXX 3261 -------------------------------------------------------------------- 3262 -------------------------------------------------------------------- 3263 name: ietf-te-topology-packet 3264 namespace: urn:ietf:params:xml:ns:yang:ietf-te-topology-packet 3265 prefix: tet-pkt 3266 reference: RFC XXXX 3267 -------------------------------------------------------------------- 3269 -------------------------------------------------------------------- 3270 name: ietf-te-topology-packet-state 3271 namespace: urn:ietf:params:xml:ns:yang:ietf-te-topology-packet-state 3272 prefix: tet-pkt-s 3273 reference: RFC XXXX 3274 -------------------------------------------------------------------- 3276 8. Security Considerations 3278 The YANG module specified in this document defines a schema for data 3279 that is designed to be accessed via network management protocols such 3280 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 3281 is the secure transport layer, and the mandatory-to-implement secure 3282 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 3283 is HTTPS, and the mandatory-to-implement secure transport is TLS 3284 [RFC8446]. 3286 The Network Configuration Access Control Model (NACM) [RFC8341] 3287 provides the means to restrict access for particular NETCONF or 3288 RESTCONF users to a preconfigured subset of all available NETCONF or 3289 RESTCONF protocol operations and content. 3291 There are a number of data nodes defined in this YANG module that are 3292 writable/creatable/deletable (i.e., config true, which is the 3293 default). These data nodes may be considered sensitive or vulnerable 3294 in some network environments. Write operations (e.g., edit-config) 3295 to these data nodes without proper protection can have a negative 3296 effect on network operations. These are the subtrees and data nodes 3297 and their sensitivity/vulnerability: 3299 /nw:networks/nw:network/nw:network-types/l3t:l3-unicast-topology/ 3300 l3-te 3301 This subtree specifies the layer 3 TE topology type. Modifying 3302 the configurations can make layer 3 TE topology type invalid and 3303 cause interruption to all layer 3 TE networks. 3305 /nw:networks/nw:network/l3t:l3-topology-attributes/l3-te-topology- 3306 attributes 3307 This subtree specifies the topology-wide configurations, including 3308 the reference to a TE topology from a layer 3 TE topology. 3310 Modifying the configurations here can cause traffic disabled or 3311 rerouted in this topology and the connected topologies. 3313 /nw:networks/nw:network/nw:node/l3t:l3-node-attributes/l3-te-node- 3314 attributes 3315 This subtree specifies the configurations of layer 3 TE nodes. 3316 Modifying the configurations in this subtree can change the 3317 relationship between a TE node and a node in a layer 3 TE 3318 topology, causing traffic disabled or rerouted in the specified 3319 nodes and the related layer 3 topologies. 3321 /nw:networks/nw:network/nw:node/nt:termination-point//l3t:l3- 3322 termination-point-attributes/l3-te-tp-attributes 3323 This subtree specifies the configurations of layer 3 TE link 3324 termination points. Modifying the configurations in this subtree 3325 can change the relationship between a TE link termination point 3326 and a link termination point in a layer 3 TE topology, causing 3327 traffic disabled or rerouted on the related layer 3 links and the 3328 related layer 3 topologies. 3330 /nw:networks/nw:network/nt:link/l3t:l3-link-attributes/l3-te-link- 3331 attributes 3332 This subtree specifies the configurations of layer 3 TE links. 3333 Modifying the configurations in this subtree can change the 3334 relationship between a TE link and a link in a layer 3 TE 3335 topology, causing traffic disabled or rerouted on the specified 3336 layer 3 link and the related layer 3 topologies. 3338 performance-metric containers 3339 The container "performance-metric" is augmented to multiple 3340 locations of the base TE topology model, as specified in 3341 Section 3.2. Modifying the configuration in such a container can 3342 change the behaviors of performance metric monitoring, causing 3343 traffic disabled or rerouted on the related layer 3 links, nodes, 3344 or topologies. 3346 Some of the readable data nodes in this YANG module may be considered 3347 sensitive or vulnerable in some network environments. It is thus 3348 important to control read access (e.g., via get, get-config, or 3349 notification) to these data nodes. These are the subtrees and data 3350 nodes and their sensitivity/vulnerability: 3352 /nw:networks/nw:network/nw:network-types/l3t:l3-unicast-topology/ 3353 l3-te 3354 Unauthorized access to this subtree can disclose the layer 3 TE 3355 topology type. 3357 /nw:networks/nw:network/l3t:l3-topology-attributes/l3-te-topology- 3358 attributes 3359 Unauthorized access to this subtree can disclose the topology-wide 3360 configurations, including the reference to a TE topology from a 3361 layer 3 topology. 3363 /nw:networks/nw:network/nw:node/l3t:l3-node-attributes/l3-te-node- 3364 attributes 3365 Unauthorized access to this subtree can disclose the operational 3366 state information of layer 3 TE nodes. 3368 /nw:networks/nw:network/nw:node/nt:termination-point//l3t:l3- 3369 termination-point-attributes/l3-te-tp-attributes 3370 Unauthorized access to this subtree can disclose the operational 3371 state information of layer 3 TE link termination points. 3373 /nw:networks/nw:network/nt:link/l3t:l3-link-attributes/l3-te-link- 3374 attributes 3375 Unauthorized access to this subtree can disclose the operational 3376 state information of layer 3 TE links. 3378 performance-metric containers 3379 The container "performance-metric" is augmented to multiple 3380 locations of the base TE topology model, as specified in 3381 Section 3.2. Unauthorized access to this subtree can disclose the 3382 operational state information of performance metric monitoring. 3384 9. References 3386 9.1. Normative References 3388 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3389 Requirement Levels", BCP 14, RFC 2119, 3390 DOI 10.17487/RFC2119, March 1997, 3391 . 3393 [RFC2697] Heinanen, J. and R. Guerin, "A Single Rate Three Color 3394 Marker", RFC 2697, DOI 10.17487/RFC2697, September 1999, 3395 . 3397 [RFC2698] Heinanen, J. and R. Guerin, "A Two Rate Three Color 3398 Marker", RFC 2698, DOI 10.17487/RFC2698, September 1999, 3399 . 3401 [RFC3471] Berger, L., Ed., "Generalized Multi-Protocol Label 3402 Switching (GMPLS) Signaling Functional Description", 3403 RFC 3471, DOI 10.17487/RFC3471, January 2003, 3404 . 3406 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 3407 DOI 10.17487/RFC3688, January 2004, 3408 . 3410 [RFC4115] Aboul-Magd, O. and S. Rabie, "A Differentiated Service 3411 Two-Rate, Three-Color Marker with Efficient Handling of 3412 in-Profile Traffic", RFC 4115, DOI 10.17487/RFC4115, July 3413 2005, . 3415 [RFC4124] Le Faucheur, F., Ed., "Protocol Extensions for Support of 3416 Diffserv-aware MPLS Traffic Engineering", RFC 4124, 3417 DOI 10.17487/RFC4124, June 2005, 3418 . 3420 [RFC4125] Le Faucheur, F. and W. Lai, "Maximum Allocation Bandwidth 3421 Constraints Model for Diffserv-aware MPLS Traffic 3422 Engineering", RFC 4125, DOI 10.17487/RFC4125, June 2005, 3423 . 3425 [RFC4126] Ash, J., "Max Allocation with Reservation Bandwidth 3426 Constraints Model for Diffserv-aware MPLS Traffic 3427 Engineering & Performance Comparisons", RFC 4126, 3428 DOI 10.17487/RFC4126, June 2005, 3429 . 3431 [RFC4127] Le Faucheur, F., Ed., "Russian Dolls Bandwidth Constraints 3432 Model for Diffserv-aware MPLS Traffic Engineering", 3433 RFC 4127, DOI 10.17487/RFC4127, June 2005, 3434 . 3436 [RFC5481] Morton, A. and B. Claise, "Packet Delay Variation 3437 Applicability Statement", RFC 5481, DOI 10.17487/RFC5481, 3438 March 2009, . 3440 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 3441 the Network Configuration Protocol (NETCONF)", RFC 6020, 3442 DOI 10.17487/RFC6020, October 2010, 3443 . 3445 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 3446 and A. Bierman, Ed., "Network Configuration Protocol 3447 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 3448 . 3450 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 3451 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 3452 . 3454 [RFC7074] Berger, L. and J. Meuric, "Revised Definition of the GMPLS 3455 Switching Capability and Type Fields", RFC 7074, 3456 DOI 10.17487/RFC7074, November 2013, 3457 . 3459 [RFC7471] Giacalone, S., Ward, D., Drake, J., Atlas, A., and S. 3460 Previdi, "OSPF Traffic Engineering (TE) Metric 3461 Extensions", RFC 7471, DOI 10.17487/RFC7471, March 2015, 3462 . 3464 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 3465 RFC 7950, DOI 10.17487/RFC7950, August 2016, 3466 . 3468 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 3469 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 3470 . 3472 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 3473 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 3474 May 2017, . 3476 [RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger, 3477 "Common YANG Data Types for the Routing Area", RFC 8294, 3478 DOI 10.17487/RFC8294, December 2017, 3479 . 3481 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 3482 Access Control Model", STD 91, RFC 8341, 3483 DOI 10.17487/RFC8341, March 2018, 3484 . 3486 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 3487 and R. Wilton, "Network Management Datastore Architecture 3488 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 3489 . 3491 [RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N., 3492 Ananthakrishnan, H., and X. Liu, "A YANG Data Model for 3493 Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March 3494 2018, . 3496 [RFC8346] Clemm, A., Medved, J., Varga, R., Liu, X., 3497 Ananthakrishnan, H., and N. Bahadur, "A YANG Data Model 3498 for Layer 3 Topologies", RFC 8346, DOI 10.17487/RFC8346, 3499 March 2018, . 3501 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 3502 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 3503 . 3505 [RFC8570] Ginsberg, L., Ed., Previdi, S., Ed., Giacalone, S., Ward, 3506 D., Drake, J., and Q. Wu, "IS-IS Traffic Engineering (TE) 3507 Metric Extensions", RFC 8570, DOI 10.17487/RFC8570, March 3508 2019, . 3510 [RFC8776] Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, 3511 "Common YANG Data Types for Traffic Engineering", 3512 RFC 8776, DOI 10.17487/RFC8776, June 2020, 3513 . 3515 [RFC8795] Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and 3516 O. Gonzalez de Dios, "YANG Data Model for Traffic 3517 Engineering (TE) Topologies", RFC 8795, 3518 DOI 10.17487/RFC8795, August 2020, 3519 . 3521 9.2. Informative References 3523 [RFC7823] Atlas, A., Drake, J., Giacalone, S., and S. Previdi, 3524 "Performance-Based Path Selection for Explicitly Routed 3525 Label Switched Paths (LSPs) Using TE Metric Extensions", 3526 RFC 7823, DOI 10.17487/RFC7823, May 2016, 3527 . 3529 [RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG", 3530 RFC 7951, DOI 10.17487/RFC7951, August 2016, 3531 . 3533 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 3534 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 3535 . 3537 [I-D.ietf-teas-yang-te-mpls] 3538 Saad, T., Gandhi, R., Liu, X., Beeram, V. P., and I. 3539 Bryskin, "A YANG Data Model for MPLS Traffic Engineering 3540 Tunnels", draft-ietf-teas-yang-te-mpls-03 (work in 3541 progress), March 2020. 3543 Appendix A. Companion YANG Model for Non-NMDA Compliant Implementations 3545 The YANG modules ietf-l3-te-topology and ietf-te-topology-packet 3546 defined in this document are designed to be used in conjunction with 3547 implementations that support the Network Management Datastore 3548 Architecture (NMDA) defined in [RFC8342]. In order to allow 3549 implementations to use the model even in cases when NMDA is not 3550 supported, the following companion modules, ietf-l3-te-topology-state 3551 and ietf-te-topology-packet-state, are defined as state models, which 3552 mirror the modules ietf-l3-te-topology and ietf-te-topology-packet 3553 defined earlier in this document. However, all data nodes in the 3554 companion module are non-configurable, to represent the applied 3555 configuration or the derived operational states. 3557 The companion modules, ietf-l3-te-topology-state and ietf-te- 3558 topology-packet-state, are redundant and SHOULD NOT be supported by 3559 implementations that support NMDA. 3561 As the structure of the companion modules mirrors that of the 3562 coorespinding NMDA models, the YANG trees of the companion modules 3563 are not depicted separately. 3565 A.1. Layer 3 TE Topology State Module 3567 This module references [RFC8345], and [RFC8346]. 3569 file "ietf-l3-te-topology-state@2020-05-03.yang" 3570 module ietf-l3-te-topology-state { 3571 yang-version 1.1; 3572 namespace "urn:ietf:params:xml:ns:yang:ietf-l3-te-topology-state"; 3573 prefix "l3tet-s"; 3575 import ietf-l3-te-topology { 3576 prefix "l3tet"; 3577 } 3578 import ietf-network-state { 3579 prefix "nw-s"; 3580 reference "RFC 8345: A YANG Data Model for Network Topologies"; 3581 } 3582 import ietf-network-topology-state { 3583 prefix "nt-s"; 3584 reference "RFC 8345: A YANG Data Model for Network Topologies"; 3585 } 3586 import ietf-l3-unicast-topology-state { 3587 prefix "l3t-s"; 3588 reference "RFC 8346: A YANG Data Model for Layer 3 Topologies"; 3589 } 3590 organization 3591 "IETF Traffic Engineering Architecture and Signaling (TEAS) 3592 Working Group"; 3594 contact 3595 "WG Web: 3596 WG List: 3598 Editor: Xufeng Liu 3599 3601 Editor: Igor Bryskin 3602 3604 Editor: Vishnu Pavan Beeram 3605 3607 Editor: Tarek Saad 3608 3610 Editor: Himanshu Shah 3611 3613 Editor: Oscar Gonzalez De Dios 3614 "; 3616 description 3617 "YANG data model for representing operational state information 3618 of Layer 3 TE Topologies, when NMDA is not supported. 3620 Copyright (c) 2018 IETF Trust and the persons identified as 3621 authors of the code. All rights reserved. 3623 Redistribution and use in source and binary forms, with or 3624 without modification, is permitted pursuant to, and subject to 3625 the license terms contained in, the Simplified BSD License set 3626 forth in Section 4.c of the IETF Trust's Legal Provisions 3627 Relating to IETF Documents 3628 (http://trustee.ietf.org/license-info). 3630 This version of this YANG module is part of RFC XXXX; see the 3631 RFC itself for full legal notices."; 3633 revision 2020-05-03 { 3634 description 3635 "Initial revision"; 3636 reference "RFC XXXX: YANG Data Model for Layer 3 TE Topologies"; 3637 } 3638 augment "/nw-s:networks/nw-s:network/nw-s:network-types/" 3639 + "l3t-s:l3-unicast-topology" { 3640 description 3641 "Defines the L3 TE topology type."; 3642 uses l3tet:l3-te-topology-type; 3643 } 3645 augment "/nw-s:networks/nw-s:network/" 3646 + "l3t-s:l3-topology-attributes" { 3647 when "../nw-s:network-types/l3t-s:l3-unicast-topology/" 3648 + "l3tet-s:l3-te" { 3649 description 3650 "Augment only for L3 TE topology"; 3651 } 3652 description 3653 "Augment topology configuration"; 3654 uses l3tet:l3-te-topology-attributes; 3655 } 3657 augment "/nw-s:networks/nw-s:network/nw-s:node/" 3658 + "l3t-s:l3-node-attributes" { 3659 when "../../nw-s:network-types/l3t-s:l3-unicast-topology/" 3660 + "l3tet-s:l3-te" { 3661 description 3662 "Augment only for L3 TE topology"; 3663 } 3664 description 3665 "Augment node configuration"; 3666 uses l3tet:l3-te-node-attributes; 3667 } 3669 augment "/nw-s:networks/nw-s:network/nw-s:node/" 3670 + "nt-s:termination-point/" 3671 + "l3t-s:l3-termination-point-attributes" { 3672 when "../../../nw-s:network-types/l3t-s:l3-unicast-topology/" 3673 + "l3tet-s:l3-te" { 3674 description 3675 "Augment only for L3 TE topology"; 3676 } 3677 description 3678 "Augment termination point configuration"; 3679 uses l3tet:l3-te-tp-attributes; 3680 } 3682 augment "/nw-s:networks/nw-s:network/nt-s:link/" 3683 + "l3t-s:l3-link-attributes" { 3684 when "../../nw-s:network-types/l3t-s:l3-unicast-topology/" 3685 + "l3tet-s:l3-te" { 3686 description 3687 "Augment only for L3 TE topology"; 3688 } 3689 description 3690 "Augment link configuration"; 3691 uses l3tet:l3-te-link-attributes; 3692 } 3693 } 3694 3696 A.2. Packet Switching TE Topology State Module 3698 file "ietf-te-topology-packet-state@2020-07-03.yang" 3699 module ietf-te-topology-packet-state { 3700 yang-version 1.1; 3701 namespace 3702 "urn:ietf:params:xml:ns:yang:ietf-te-topology-packet-state"; 3704 prefix "tet-pkt-s"; 3706 import ietf-te-topology-packet { 3707 prefix "tet-pkt"; 3708 } 3710 import ietf-network-state { 3711 prefix "nw-s"; 3712 reference 3713 "RFC 8345: A YANG Data Model for Network Topologies"; 3714 } 3716 import ietf-network-topology-state { 3717 prefix "nt-s"; 3718 reference 3719 "RFC 8345: A YANG Data Model for Network Topologies"; 3720 } 3722 import ietf-te-topology-state { 3723 prefix "tet-s"; 3724 reference 3725 "I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic 3726 Engineering (TE) Topologies"; 3727 } 3729 import ietf-te-types { 3730 prefix "te-types"; 3731 reference 3732 "I-D.ietf-teas-yang-te-types: Traffic Engineering Common YANG 3733 Types"; 3734 } 3736 import ietf-te-packet-types { 3737 prefix "te-packet-types"; 3738 reference 3739 "I-D.ietf-teas-yang-te-types: Traffic Engineering Common YANG 3740 Types"; 3741 } 3743 organization 3744 "Traffic Engineering Architecture and Signaling (TEAS) 3745 Working Group"; 3747 contact 3748 "WG Web: 3749 WG List: 3751 Editor: Xufeng Liu 3752 3754 Editor: Igor Bryskin 3755 3757 Editor: Vishnu Pavan Beeram 3758 3760 Editor: Tarek Saad 3761 3763 Editor: Himanshu Shah 3764 3766 Editor: Oscar Gonzalez De Dios 3767 "; 3769 description 3770 "YANG data model for representing operational state information 3771 of PSC (Packet Switching) TE Topologies, when NMDA is not 3772 supported. 3774 Copyright (c) 2018 IETF Trust and the persons identified as 3775 authors of the code. All rights reserved. 3777 Redistribution and use in source and binary forms, with or 3778 without modification, is permitted pursuant to, and subject to 3779 the license terms contained in, the Simplified BSD License set 3780 forth in Section 4.c of the IETF Trust's Legal Provisions 3781 Relating to IETF Documents 3782 (http://trustee.ietf.org/license-info). 3784 This version of this YANG module is part of RFC XXXX; see the 3785 RFC itself for full legal notices."; 3787 revision 2020-07-03 { 3788 description 3789 "Initial revision"; 3790 reference 3791 "RFC XXXX: YANG Data Model for Layer 3 TE Topologies"; 3792 } 3794 /* 3795 * Augmentations 3796 */ 3797 /* Augmentations to network-types */ 3798 augment "/nw-s:networks/nw-s:network/nw-s:network-types/" 3799 + "tet-s:te-topology" { 3800 description 3801 "Defines the packet TE topology type."; 3802 container packet { 3803 presence "Indicates packet TE topology."; 3804 description 3805 "Its presence identifies the packet TE topology type."; 3806 } 3807 } 3809 /* Augmentations to connectivity-matrix */ 3810 augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/" 3811 + "tet-s:te-node-attributes/tet-s:connectivity-matrices" { 3812 when "../../../../nw-s:network-types/tet-s:te-topology/" 3813 + "tet-pkt-s:packet" { 3814 description 3815 "Augment only for packet TE topology"; 3816 } 3817 description 3818 "Parameters for PSC (Packet Switching) TE topology."; 3819 uses te-packet-types:performance-metrics-attributes-packet { 3820 if-feature tet-pkt:te-performance-metric; 3821 } 3822 uses 3823 te-packet-types:performance-metrics-throttle-container-packet { 3824 if-feature tet-pkt:te-performance-metric; 3825 } 3826 } 3827 augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/" 3828 + "tet-s:te-node-attributes/tet-s:connectivity-matrices/" 3829 + "tet-s:connectivity-matrix" { 3830 when "../../../../../nw-s:network-types/tet-s:te-topology/" 3831 + "tet-pkt-s:packet" { 3832 description 3833 "Augment only for packet TE topology"; 3834 } 3835 description 3836 "Parameters for PSC TE topology."; 3837 uses te-packet-types:performance-metrics-attributes-packet { 3838 if-feature tet-pkt:te-performance-metric; 3839 } 3840 uses 3841 te-packet-types:performance-metrics-throttle-container-packet { 3842 if-feature tet-pkt:te-performance-metric; 3843 } 3844 } 3846 augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/" 3847 + "tet-s:information-source-entry/" 3848 + "tet-s:connectivity-matrices" { 3849 when "../../../../nw-s:network-types/tet-s:te-topology/" 3850 + "tet-pkt-s:packet" { 3851 description 3852 "Augment only for packet TE topology"; 3853 } 3854 description 3855 "Parameters for PSC TE topology."; 3856 uses te-packet-types:performance-metrics-attributes-packet { 3857 if-feature tet-pkt:te-performance-metric; 3858 } 3859 uses 3860 te-packet-types:performance-metrics-throttle-container-packet { 3861 if-feature tet-pkt:te-performance-metric; 3862 } 3863 } 3865 augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/" 3866 + "tet-s:information-source-entry/" 3867 + "tet-s:connectivity-matrices/" 3868 + "tet-s:connectivity-matrix" { 3869 when "../../../../../nw-s:network-types/tet-s:te-topology/" 3870 + "tet-pkt-s:packet" { 3871 description 3872 "Augment only for packet TE topology"; 3873 } 3874 description 3875 "Parameters for PSC TE topology."; 3876 uses te-packet-types:performance-metrics-attributes-packet { 3877 if-feature tet-pkt:te-performance-metric; 3878 } 3879 uses 3880 te-packet-types:performance-metrics-throttle-container-packet { 3881 if-feature tet-pkt:te-performance-metric; 3882 } 3883 } 3885 /* Augmentations to tunnel-termination-point */ 3886 augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/" 3887 + "tet-s:tunnel-termination-point/" 3888 + "tet-s:local-link-connectivities" { 3889 when "../../../../nw-s:network-types/tet-s:te-topology/" 3890 + "tet-pkt-s:packet" { 3891 description 3892 "Augment only for packet TE topology"; 3893 } 3894 description 3895 "Parameters for PSC TE topology."; 3896 uses te-packet-types:performance-metrics-attributes-packet { 3897 if-feature tet-pkt:te-performance-metric; 3898 } 3899 uses 3900 te-packet-types:performance-metrics-throttle-container-packet { 3901 if-feature tet-pkt:te-performance-metric; 3902 } 3903 } 3905 augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/" 3906 + "tet-s:tunnel-termination-point/" 3907 + "tet-s:local-link-connectivities/" 3908 + "tet-s:local-link-connectivity" { 3909 when "../../../../../nw-s:network-types/tet-s:te-topology/" 3910 + "tet-pkt-s:packet" { 3911 description 3912 "Augment only for packet TE topology"; 3913 } 3914 description 3915 "Parameters for PSC TE topology."; 3916 uses te-packet-types:performance-metrics-attributes-packet { 3917 if-feature tet-pkt:te-performance-metric; 3918 } 3919 uses 3920 te-packet-types:performance-metrics-throttle-container-packet { 3921 if-feature tet-pkt:te-performance-metric; 3922 } 3924 } 3926 /* Augmentations to te-link-attributes */ 3927 augment "/nw-s:networks/tet-s:te/tet-s:templates/" 3928 + "tet-s:link-template/tet-s:te-link-attributes" { 3929 when "tet-s:interface-switching-capability " 3930 + "[tet-s:switching-capability = 'te-types:switching-psc1']" { 3931 description 3932 "Valid only for PSC"; 3933 } 3934 description 3935 "Parameters for PSC TE topology."; 3936 uses te-packet-types:performance-metrics-attributes-packet { 3937 if-feature tet-pkt:te-performance-metric; 3938 } 3939 uses 3940 te-packet-types:performance-metrics-throttle-container-packet { 3941 if-feature tet-pkt:te-performance-metric; 3942 } 3943 } 3945 augment "/nw-s:networks/nw-s:network/nt-s:link/tet-s:te/" 3946 + "tet-s:te-link-attributes" { 3947 when "(../../../nw-s:network-types/tet-s:te-topology/" 3948 + "tet-pkt-s:packet) and " 3949 + "(tet-s:interface-switching-capability " 3950 + "[tet-s:switching-capability = 'te-types:switching-psc1'])" { 3951 description "Valid only for PSC"; 3952 } 3953 description 3954 "Parameters for PSC TE topology."; 3955 uses te-packet-types:performance-metrics-attributes-packet { 3956 if-feature tet-pkt:te-performance-metric; 3957 } 3958 uses 3959 te-packet-types:performance-metrics-throttle-container-packet { 3960 if-feature tet-pkt:te-performance-metric; 3961 } 3962 } 3964 augment "/nw-s:networks/nw-s:network/nt-s:link/tet-s:te/" 3965 + "tet-s:information-source-entry" { 3966 when "(../../../nw-s:network-types/tet-s:te-topology/" 3967 + "tet-pkt-s:packet) and " 3968 + "(tet-s:interface-switching-capability " 3969 + "[tet-s:switching-capability = 'te-types:switching-psc1'])" { 3970 description "Valid only for PSC"; 3971 } 3972 description 3973 "Parameters for PSC TE topology."; 3974 uses te-packet-types:performance-metrics-attributes-packet { 3975 if-feature tet-pkt:te-performance-metric; 3976 } 3977 uses 3978 te-packet-types:performance-metrics-throttle-container-packet { 3979 if-feature tet-pkt:te-performance-metric; 3980 } 3981 } 3983 /* Augmentations to interface-switching-capability */ 3984 augment "/nw-s:networks/tet-s:te/tet-s:templates/" 3985 + "tet-s:link-template/tet-s:te-link-attributes/" 3986 + "tet-s:interface-switching-capability" { 3987 when "tet-s:switching-capability = 'te-types:switching-psc1' " { 3988 description "Valid only for PSC"; 3989 } 3990 description 3991 "Parameters for PSC TE topology."; 3992 uses tet-pkt:packet-switch-capable-container; 3993 } 3995 augment "/nw-s:networks/nw-s:network/nt-s:link/tet-s:te/" 3996 + "tet-s:te-link-attributes/" 3997 + "tet-s:interface-switching-capability" { 3998 when "(../../../../nw-s:network-types/tet-s:te-topology/" 3999 + "tet-pkt-s:packet) and " 4000 + "(tet-s:switching-capability = 'te-types:switching-psc1')" { 4001 description "Valid only for PSC"; 4002 } 4003 description 4004 "Parameters for PSC TE topology."; 4005 uses tet-pkt:packet-switch-capable-container; 4006 } 4008 augment "/nw-s:networks/nw-s:network/nt-s:link/tet-s:te/" 4009 + "tet-s:information-source-entry/" 4010 + "tet-s:interface-switching-capability" { 4011 when "(../../../../nw-s:network-types/tet-s:te-topology/" 4012 + "tet-pkt-s:packet) and " 4013 + "(tet-s:switching-capability = 'te-types:switching-psc1')" { 4014 description 4015 "Valid only for PSC"; 4016 } 4017 description 4018 "Parameters for PSC TE topology."; 4019 uses tet-pkt:packet-switch-capable-container; 4021 } 4022 } 4023 4025 Appendix B. Data Tree Example 4027 This section contains an example of an instance data tree in the JSON 4028 encoding [RFC7951]. The example instantiates "ietf-l3-te-topology" 4029 for the topology that is depicted in the following diagram. 4031 +------------+ +------------+ 4032 | D1 | | D2 | 4033 /-\ /-\ (TE) /-\ /-\ 4034 | | 1-0-1 | |---------------->| | 2-1-1 | | 4035 | | 1-2-1 | |<----------------| | 2-0-1 | | 4036 \-/ 1-3-1 \-/ (TE) \-/ 2-3-1 \-/ 4037 | /----\ | | /----\ | 4038 +---| |---+ +---| |---+ 4039 \----/ \----/ 4040 A | A | 4041 (TE)| |(TE) (Non-TE)| |(Non-TE) 4042 | | | | 4043 | | +------------+ | | 4044 | | | D3 | | | 4045 | | /-\ /-\ | | 4046 | +----->| | 3-1-1 | |-------+ | 4047 +---------| | 3-2-1 | |<---------+ 4048 \-/ \-/ 4049 | | 4050 +------------+ 4052 The corresponding instance data tree is depicted below. Note that 4053 some lines have been wrapped to adhere to the 72-character line 4054 limitation of RFCs. 4056 { 4057 "ietf-network:networks": { 4058 "network": [ 4059 { 4060 "network-id":"example-topo-te", 4061 "network-types": { 4062 "ietf-te-topology:te-topology": { 4063 } 4064 }, 4065 "ietf-te-topology:te-topology-identifier": { 4066 "provider-id":200, 4067 "client-id":300, 4068 "topology-id":"example-topo-te" 4069 }, 4070 "ietf-te-topology:te": { 4071 }, 4072 "node": [ 4073 { 4074 "node-id":"D1", 4075 "ietf-te-topology:te-node-id":"2.0.1.1", 4076 "ietf-te-topology:te": { 4077 "te-node-attributes": { 4078 } 4079 }, 4080 "ietf-network-topology:termination-point": [ 4081 { 4082 "tp-id":"1-2-1", 4083 "ietf-te-topology:te-tp-id":10201, 4084 "ietf-te-topology:te": { 4085 "interface-switching-capability": [ 4086 { 4087 "switching-capability": 4088 "ietf-te-types:switching-psc1", 4089 "encoding": 4090 "ietf-te-types:lsp-encoding-ethernet" 4091 } 4092 ] 4093 } 4094 }, 4095 { 4096 "tp-id": "1-3-1", 4097 "ietf-te-topology:te-tp-id":10301, 4098 "ietf-te-topology:te": { 4099 "interface-switching-capability": [ 4100 { 4101 "switching-capability": 4102 "ietf-te-types:switching-psc1", 4103 "encoding": 4104 "ietf-te-types:lsp-encoding-ethernet" 4105 } 4106 ] 4107 } 4108 } 4109 ] 4110 }, 4111 { 4112 "node-id":"D2", 4113 "ietf-te-topology:te-node-id":"2.0.2.1", 4114 "ietf-te-topology:te": { 4115 "te-node-attributes": { 4116 } 4117 }, 4118 "ietf-network-topology:termination-point": [ 4119 { 4120 "tp-id":"2-1-1", 4121 "ietf-te-topology:te-tp-id":20101, 4122 "ietf-te-topology:te": { 4123 "interface-switching-capability": [ 4124 { 4125 "switching-capability": 4126 "ietf-te-types:switching-psc1", 4127 "encoding": 4128 "ietf-te-types:lsp-encoding-ethernet" 4129 } 4130 ] 4131 } 4132 } 4133 ] 4134 }, 4135 { 4136 "node-id":"D3", 4137 "ietf-te-topology:te-node-id":"2.0.3.1", 4138 "ietf-te-topology:te": { 4139 "te-node-attributes": { 4140 } 4141 }, 4142 "ietf-network-topology:termination-point": [ 4143 { 4144 "tp-id":"3-1-1", 4145 "ietf-te-topology:te-tp-id":30101, 4146 "ietf-te-topology:te": { 4147 "interface-switching-capability": [ 4148 { 4149 "switching-capability": 4150 "ietf-te-types:switching-psc1", 4151 "encoding": 4152 "ietf-te-types:lsp-encoding-ethernet" 4153 } 4154 ] 4155 } 4156 } 4157 ] 4158 } 4159 ], 4160 "ietf-network-topology:link": [ 4161 { 4162 "link-id":"D1,1-2-1,D2,2-1-1", 4163 "source": { 4164 "source-node":"D1", 4165 "source-tp":"1-2-1" 4166 }, 4167 "destination": { 4168 "dest-node":"D2", 4169 "dest-tp":"2-1-1" 4170 }, 4171 "ietf-te-topology:te": { 4172 "te-link-attributes": { 4173 "interface-switching-capability": [ 4174 { 4175 "switching-capability": 4176 "ietf-te-types:switching-psc1", 4177 "encoding":"ietf-te-types:lsp-encoding-ethernet" 4178 } 4179 ], 4180 "max-link-bandwidth": { 4181 "te-bandwidth": { 4182 "generic":"0x1p+18" 4183 } 4184 }, 4185 "te-default-metric":100 4186 } 4187 } 4188 }, 4189 { 4190 "link-id":"D2,2-1-1,D1,1-2-1", 4191 "source": { 4192 "source-node":"D2", 4193 "source-tp":"2-1-1" 4194 }, 4195 "destination": { 4196 "dest-node":"D1", 4197 "dest-tp":"1-2-1" 4198 }, 4199 "ietf-te-topology:te": { 4200 "te-link-attributes": { 4201 "interface-switching-capability": [ 4202 { 4203 "switching-capability": 4204 "ietf-te-types:switching-psc1", 4205 "encoding":"ietf-te-types:lsp-encoding-ethernet" 4206 } 4207 ], 4208 "max-link-bandwidth": { 4209 "te-bandwidth": { 4210 "generic":"0x1p+18" 4211 } 4212 }, 4213 "te-default-metric":100 4214 } 4215 } 4216 }, 4217 { 4218 "link-id":"D1,1-3-1,D3,3-1-1", 4219 "source": { 4220 "source-node":"D1", 4221 "source-tp":"1-3-1" 4222 }, 4223 "destination": { 4224 "dest-node":"D3", 4225 "dest-tp":"3-1-1" 4226 }, 4227 "ietf-te-topology:te": { 4228 "te-link-attributes": { 4229 "interface-switching-capability": [ 4230 { 4231 "switching-capability": 4232 "ietf-te-types:switching-psc1", 4233 "encoding":"ietf-te-types:lsp-encoding-ethernet" 4234 } 4235 ], 4236 "max-link-bandwidth": { 4237 "te-bandwidth": { 4238 "generic":"0x1p+18" 4239 } 4240 }, 4241 "te-default-metric":100 4242 } 4243 } 4244 }, 4245 { 4246 "link-id":"D3,3-1-1,D1,1-3-1", 4247 "source": { 4248 "source-node":"D3", 4249 "source-tp":"3-1-1" 4250 }, 4251 "destination": { 4252 "dest-node":"D1", 4253 "dest-tp":"1-3-1" 4254 }, 4255 "ietf-te-topology:te": { 4256 "te-link-attributes": { 4257 "interface-switching-capability": [ 4258 { 4259 "switching-capability": 4260 "ietf-te-types:switching-psc1", 4261 "encoding":"ietf-te-types:lsp-encoding-ethernet" 4262 } 4263 ], 4264 "max-link-bandwidth": { 4265 "te-bandwidth": { 4266 "generic":"0x1p+18" 4267 } 4268 }, 4269 "te-default-metric":100 4270 } 4271 } 4272 } 4273 ] 4274 }, 4275 { 4276 "network-id":"example-topo-l3-te", 4277 "network-types": { 4278 "ietf-l3-unicast-topology:l3-unicast-topology": { 4279 "ietf-l3-te-topology:l3-te": { 4280 } 4281 } 4282 }, 4283 "ietf-l3-unicast-topology:l3-topology-attributes": { 4284 "ietf-l3-te-topology:l3-te-topology-attributes": { 4285 "network-ref":"example-topo-te" 4286 } 4287 }, 4288 "node": [ 4289 { 4290 "node-id":"D1", 4291 "ietf-l3-unicast-topology:l3-node-attributes": { 4292 "router-id": [ 4293 "203.0.113.1" 4294 ], 4295 "prefix": [ 4296 { 4297 "prefix":"203.0.113.1/32" 4298 } 4299 ], 4300 "ietf-l3-te-topology:l3-te-node-attributes": { 4301 "node-ref":"D1", 4302 "network-ref":"example-topo-te" 4303 } 4304 }, 4305 "ietf-network-topology:termination-point": [ 4306 { 4307 "tp-id":"1-0-1", 4308 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 4309 "unnumbered-id":101 4310 } 4311 }, 4312 { 4313 "tp-id":"1-2-1", 4314 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 4315 "unnumbered-id":121, 4316 "ietf-l3-te-topology:l3-te-tp-attributes": { 4317 "network-ref":"example-topo-te", 4318 "tp-ref":"1-2-1" 4319 } 4320 } 4321 }, 4322 { 4323 "tp-id":"1-3-1", 4324 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 4325 "unnumbered-id":131, 4326 "ietf-l3-te-topology:l3-te-tp-attributes": { 4327 "network-ref":"example-topo-te", 4328 "tp-ref":"1-3-1" 4329 } 4330 } 4331 } 4332 ] 4333 }, 4334 { 4335 "node-id":"D2", 4336 "ietf-l3-unicast-topology:l3-node-attributes": { 4337 "router-id": [ 4338 "203.0.113.2" 4339 ], 4340 "prefix": [ 4341 { 4342 "prefix":"203.0.113.2/32" 4343 } 4344 ], 4345 "ietf-l3-te-topology:l3-te-node-attributes": { 4346 "node-ref":"D2", 4347 "network-ref":"example-topo-te" 4348 } 4349 }, 4350 "ietf-network-topology:termination-point": [ 4351 { 4352 "tp-id":"2-0-1", 4354 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 4355 "unnumbered-id":201 4356 } 4357 }, 4358 { 4359 "tp-id":"2-1-1", 4360 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 4361 "unnumbered-id":211, 4362 "ietf-l3-te-topology:l3-te-tp-attributes": { 4363 "tp-ref":"2-1-1", 4364 "network-ref":"example-topo-te" 4365 } 4366 } 4367 }, 4368 { 4369 "tp-id":"2-3-1", 4370 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 4371 "unnumbered-id":231 4372 } 4373 } 4374 ] 4375 }, 4376 { 4377 "node-id":"D3", 4378 "ietf-l3-unicast-topology:l3-node-attributes": { 4379 "router-id": [ 4380 "203.0.113.3" 4381 ], 4382 "prefix": [ 4383 { 4384 "prefix":"203.0.113.3/32" 4385 } 4386 ], 4387 "ietf-l3-te-topology:l3-te-node-attributes": { 4388 "node-ref":"D3", 4389 "network-ref":"example-topo-te" 4390 } 4391 }, 4392 "ietf-network-topology:termination-point": [ 4393 { 4394 "tp-id":"3-0-1", 4395 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 4396 "unnumbered-id":301 4397 } 4398 }, 4399 { 4400 "tp-id":"3-1-1", 4401 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 4402 "unnumbered-id":311, 4403 "ietf-l3-te-topology:l3-te-tp-attributes": { 4404 "tp-ref":"3-1-1", 4405 "network-ref":"example-topo-te" 4406 } 4407 } 4408 }, 4409 { 4410 "tp-id":"3-2-1", 4411 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 4412 "unnumbered-id":321 4413 } 4414 } 4415 ] 4416 } 4417 ], 4418 "ietf-network-topology:link": [ 4419 { 4420 "link-id":"D1,1-2-1,D2,2-1-1", 4421 "source": { 4422 "source-node":"D1", 4423 "source-tp":"1-2-1" 4424 }, 4425 "destination": { 4426 "dest-node":"D2", 4427 "dest-tp":"2-1-1" 4428 }, 4429 "ietf-l3-unicast-topology:l3-link-attributes": { 4430 "metric1":"100", 4431 "ietf-l3-te-topology:l3-te-link-attributes": { 4432 "link-ref":"D1,1-2-1,D2,2-1-1", 4433 "network-ref":"example-topo-te" 4434 } 4435 } 4436 }, 4437 { 4438 "link-id":"D2,2-1-1,D1,1-2-1", 4439 "source": { 4440 "source-node":"D2", 4441 "source-tp":"2-1-1" 4442 }, 4443 "destination": { 4444 "dest-node":"D1", 4445 "dest-tp":"1-2-1" 4446 }, 4447 "ietf-l3-unicast-topology:l3-link-attributes": { 4448 "metric1":"100", 4449 "ietf-l3-te-topology:l3-te-link-attributes": { 4450 "link-ref":"D2,2-1-1,D1,1-2-1", 4451 "network-ref":"example-topo-te" 4452 } 4453 } 4454 }, 4455 { 4456 "link-id":"D1,1-3-1,D3,3-1-1", 4457 "source": { 4458 "source-node":"D1", 4459 "source-tp":"1-3-1" 4460 }, 4461 "destination": { 4462 "dest-node":"D3", 4463 "dest-tp":"3-1-1" 4464 }, 4465 "ietf-l3-unicast-topology:l3-link-attributes": { 4466 "metric1":"100", 4467 "ietf-l3-te-topology:l3-te-link-attributes": { 4468 "link-ref":"D1,1-3-1,D3,3-1-1", 4469 "network-ref":"example-topo-te" 4470 } 4471 } 4472 }, 4473 { 4474 "link-id":"D3,3-1-1,D1,1-3-1", 4475 "source": { 4476 "source-node":"D3", 4477 "source-tp":"3-1-1" 4478 }, 4479 "destination": { 4480 "dest-node":"D1", 4481 "dest-tp":"1-3-1" 4482 }, 4483 "ietf-l3-unicast-topology:l3-link-attributes": { 4484 "metric1":"100", 4485 "ietf-l3-te-topology:l3-te-link-attributes": { 4486 "link-ref":"D3,3-1-1,D1,1-3-1", 4487 "network-ref":"example-topo-te" 4488 } 4489 } 4490 }, 4491 { 4492 "link-id":"D2,2-3-1,D3,3-2-1", 4493 "source": { 4494 "source-node":"D2", 4495 "source-tp":"2-3-1" 4496 }, 4497 "destination": { 4498 "dest-node":"D3", 4499 "dest-tp":"3-2-1" 4500 }, 4501 "ietf-l3-unicast-topology:l3-link-attributes": { 4502 "metric1":"100" 4503 } 4504 }, 4505 { 4506 "link-id":"D3,3-2-1,D2,2-3-1", 4507 "source": { 4508 "source-node":"D3", 4509 "source-tp":"3-2-1" 4510 }, 4511 "destination": { 4512 "dest-node":"D2", 4513 "dest-tp":"2-3-1" 4514 }, 4515 "ietf-l3-unicast-topology:l3-link-attributes": { 4516 "metric1":"100" 4517 } 4518 } 4519 ] 4520 } 4521 ] 4522 } 4523 } 4525 Authors' Addresses 4527 Xufeng Liu 4528 Volta Networks 4530 EMail: xufeng.liu.ietf@gmail.com 4532 Igor Bryskin 4533 Individual 4535 EMail: i_bryskin@yahoo.com 4537 Vishnu Pavan Beeram 4538 Juniper Networks 4540 EMail: vbeeram@juniper.net 4541 Tarek Saad 4542 Juniper Networks 4544 EMail: tsaad@juniper.net 4546 Himanshu Shah 4547 Ciena 4549 EMail: hshah@ciena.com 4551 Oscar Gonzalez de Dios 4552 Telefonica 4554 EMail: oscar.gonzalezdedios@telefonica.com