idnits 2.17.1 draft-ietf-teas-yang-l3-te-topo-12.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 (October 24, 2021) is 912 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: April 27, 2022 V. Beeram 7 T. Saad 8 Juniper Networks 9 H. Shah 10 Ciena 11 O. Gonzalez de Dios 12 Telefonica 13 October 24, 2021 15 YANG Data Model for Layer 3 TE Topologies 16 draft-ietf-teas-yang-l3-te-topo-12 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 April 27, 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 . . . . . . . . . . . 54 92 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 69 93 8. Security Considerations . . . . . . . . . . . . . . . . . . . 70 94 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 73 95 9.1. Normative References . . . . . . . . . . . . . . . . . . 73 96 9.2. Informative References . . . . . . . . . . . . . . . . . 76 98 Appendix A. Companion YANG Model for Non-NMDA Compliant 99 Implementations . . . . . . . . . . . . . . . . . . 77 100 A.1. Layer 3 TE Topology State Module . . . . . . . . . . . . 77 101 A.2. Packet Switching TE Topology State Module . . . . . . . . 80 102 Appendix B. Data Tree Example . . . . . . . . . . . . . . . . . 87 103 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 97 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], [RFC8776], [IEEE754], and [ISO-IEC-C99] 1869 file "ietf-te-packet-types@2020-06-10.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-10-24 { 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 1951 "Bandwidth Profile Types"; 1952 } 1954 identity mef-10-bwp { 1955 base bandwidth-profile-type; 1956 description 1957 "MEF 10 Bandwidth Profile"; 1958 } 1960 identity rfc-2697-bwp { 1961 base bandwidth-profile-type; 1962 description 1963 "RFC 2697 Bandwidth Profile"; 1964 } 1965 identity rfc-2698-bwp { 1966 base bandwidth-profile-type; 1967 description 1968 "RFC 2698 Bandwidth Profile"; 1969 } 1971 identity rfc-4115-bwp { 1972 base bandwidth-profile-type; 1973 description 1974 "RFC 4115 Bandwidth Profile"; 1975 } 1977 /* 1978 * Typedefs 1979 */ 1981 typedef te-bandwidth-requested-type { 1982 type enumeration { 1983 enum specified { 1984 description 1985 "Bandwidth is explicitly specified."; 1986 } 1987 enum auto { 1988 description 1989 "Bandwidth is automatically computed."; 1990 } 1991 } 1992 description 1993 "Enumerated type for specifying whether bandwidth is 1994 explicitly specified or automatically computed."; 1995 } 1997 typedef te-class-type { 1998 type uint8; 1999 description 2000 "Diffserv-TE Class-Type. Defines a set of Traffic Trunks 2001 crossing a link that is governed by a specific set of 2002 bandwidth constraints. Class-Type is used for the purposes 2003 of link bandwidth allocation, constraint-based routing, and 2004 admission control."; 2005 reference 2006 "RFC 4124: Protocol Extensions for Support of Diffserv-aware 2007 MPLS Traffic Engineering"; 2008 } 2010 typedef bc-type { 2011 type uint8 { 2012 range "0..7"; 2014 } 2015 description 2016 "Diffserv-TE bandwidth constraints as defined in RFC 4124."; 2017 reference 2018 "RFC 4124: Protocol Extensions for Support of Diffserv-aware 2019 MPLS Traffic Engineering"; 2020 } 2022 typedef bandwidth-kbps { 2023 type uint64; 2024 units "Kbps"; 2025 description 2026 "Bandwidth values, expressed in kilobits per second."; 2027 } 2029 typedef bandwidth-mbps { 2030 type uint64; 2031 units "Mbps"; 2032 description 2033 "Bandwidth values, expressed in megabits per second."; 2034 } 2036 typedef bandwidth-gbps { 2037 type uint64; 2038 units "Gbps"; 2039 description 2040 "Bandwidth values, expressed in gigabits per second."; 2041 } 2043 typedef bandwidth-scientific-notation { 2044 type string { 2045 pattern 2046 '0(\.0?)?([eE](\+)?0?)?|' 2047 + '[1-9](\.[0-9]{0,6})?[eE](\+)?(9[0-6]|[1-8][0-9]|0?[0-9])?'; 2048 } 2049 units "bps"; 2050 description 2051 "Bandwidth values, expressed using the scientific notation 2052 in bits per second. 2053 The encoding format is the external decimal-significant 2054 character sequences specified in IEEE 754 and ISO/IEC C99 2055 for 32-bit decimal floating-point numbers: 2056 (-1)**(S) * 10**(Exponent) * (Significant), 2057 where Significant uses 7 digits. 2058 An implementation for this representation may use decimal32 2059 or binary32. The range of the Exponent is from -95 to +96 2060 for decimal32, and from -38 to +38 for binary32. 2061 As a bandwidth value, the format is restricted to be 2062 normalized, non-negative, and non-fraction: 2063 n.dddddde{+}dd, N.DDDDDDE{+}DD, 0e0 or 0E0, 2064 where 'd' and 'D' are decimal digits; 'n' and 'N' are 2065 non-zeror decimal digits; 'e' and 'E' indicate a power of ten. 2066 Some examples are 0e0, 1e10, and 9.953e9."; 2067 reference 2068 "IEEE Std 754-2008: IEEE Standard for Floating-Point 2069 Arithmetic. 2070 ISO/IEC C99: Information technology - Programming 2071 Languages - C."; 2072 } 2074 identity backup-protection-type { 2075 description 2076 "Base identity for the backup protection type."; 2077 } 2079 identity backup-protection-link { 2080 base backup-protection-type; 2081 description 2082 "Backup provides link protection only."; 2083 } 2085 identity backup-protection-node-link { 2086 base backup-protection-type; 2087 description 2088 "Backup offers node (preferred) or link protection."; 2089 } 2091 identity bc-model-type { 2092 description 2093 "Base identity for the Diffserv-TE Bandwidth Constraints 2094 Model type."; 2095 reference 2096 "RFC 4124: Protocol Extensions for Support of Diffserv-aware 2097 MPLS Traffic Engineering"; 2098 } 2100 identity bc-model-rdm { 2101 base bc-model-type; 2102 description 2103 "Russian Dolls Bandwidth Constraints Model type."; 2104 reference 2105 "RFC 4127: Russian Dolls Bandwidth Constraints Model for 2106 Diffserv-aware MPLS Traffic Engineering"; 2107 } 2109 identity bc-model-mam { 2110 base bc-model-type; 2111 description 2112 "Maximum Allocation Bandwidth Constraints Model type."; 2113 reference 2114 "RFC 4125: Maximum Allocation Bandwidth Constraints Model for 2115 Diffserv-aware MPLS Traffic Engineering"; 2116 } 2118 identity bc-model-mar { 2119 base bc-model-type; 2120 description 2121 "Maximum Allocation with Reservation Bandwidth Constraints 2122 Model type."; 2123 reference 2124 "RFC 4126: Max Allocation with Reservation Bandwidth 2125 Constraints Model for Diffserv-aware MPLS Traffic Engineering 2126 & Performance Comparisons"; 2127 } 2129 /* 2130 * Groupings 2131 */ 2133 grouping performance-metrics-attributes-packet { 2134 description 2135 "Contains PM attributes."; 2136 uses te-types:performance-metrics-attributes { 2137 augment "performance-metrics-one-way" { 2138 leaf one-way-min-delay { 2139 type uint32 { 2140 range "0..16777215"; 2141 } 2142 description 2143 "One-way minimum delay or latency in microseconds."; 2144 } 2145 leaf one-way-min-delay-normality { 2146 type te-types:performance-metrics-normality; 2147 default "normal"; 2148 description 2149 "One-way minimum delay or latency normality."; 2150 } 2151 leaf one-way-max-delay { 2152 type uint32 { 2153 range "0..16777215"; 2154 } 2155 description 2156 "One-way maximum delay or latency in microseconds."; 2157 } 2158 leaf one-way-max-delay-normality { 2159 type te-types:performance-metrics-normality; 2160 default "normal"; 2161 description 2162 "One-way maximum delay or latency normality."; 2163 } 2164 leaf one-way-delay-variation { 2165 type uint32 { 2166 range "0..16777215"; 2167 } 2168 description 2169 "One-way delay variation in microseconds."; 2170 reference 2171 "RFC 5481: Packet Delay Variation Applicability 2172 Statement, Section 4.2"; 2173 } 2174 leaf one-way-delay-variation-normality { 2175 type te-types:performance-metrics-normality; 2176 default "normal"; 2177 description 2178 "One-way delay variation normality."; 2179 reference 2180 "RFC 7471: OSPF Traffic Engineering (TE) Metric 2181 Extensions 2182 RFC 7823: Performance-Based Path Selection for 2183 Explicitly Routed Label Switched Paths (LSPs) Using 2184 TE Metric Extensions 2185 RFC 8570: IS-IS Traffic Engineering (TE) Metric 2186 Extensions"; 2187 } 2188 leaf one-way-packet-loss { 2189 type decimal64 { 2190 fraction-digits 6; 2191 range "0..50.331642"; 2192 } 2193 description 2194 "One-way packet loss as a percentage of the total traffic 2195 sent over a configurable interval. The finest precision 2196 is 0.000003%, where the maximum is 50.331642%."; 2197 reference 2198 "RFC 8570: IS-IS Traffic Engineering (TE) Metric 2199 Extensions, Section 4.4"; 2200 } 2201 leaf one-way-packet-loss-normality { 2202 type te-types:performance-metrics-normality; 2203 default "normal"; 2204 description 2205 "Packet loss normality."; 2207 reference 2208 "RFC 7471: OSPF Traffic Engineering (TE) Metric 2209 Extensions 2210 RFC 7823: Performance-Based Path Selection for 2211 Explicitly Routed Label Switched Paths (LSPs) Using 2212 TE Metric Extensions 2213 RFC 8570: IS-IS Traffic Engineering (TE) Metric 2214 Extensions"; 2215 } 2216 description 2217 "PM one-way packet-specific augmentation for a generic PM 2218 grouping."; 2219 } 2220 augment "performance-metrics-two-way" { 2221 leaf two-way-min-delay { 2222 type uint32 { 2223 range "0..16777215"; 2224 } 2225 default "0"; 2226 description 2227 "Two-way minimum delay or latency in microseconds."; 2228 } 2229 leaf two-way-min-delay-normality { 2230 type te-types:performance-metrics-normality; 2231 default "normal"; 2232 description 2233 "Two-way minimum delay or latency normality."; 2234 reference 2235 "RFC 7471: OSPF Traffic Engineering (TE) Metric 2236 Extensions 2237 RFC 7823: Performance-Based Path Selection for 2238 Explicitly Routed Label Switched Paths (LSPs) Using 2239 TE Metric Extensions 2240 RFC 8570: IS-IS Traffic Engineering (TE) Metric 2241 Extensions"; 2242 } 2243 leaf two-way-max-delay { 2244 type uint32 { 2245 range "0..16777215"; 2246 } 2247 default "0"; 2248 description 2249 "Two-way maximum delay or latency in microseconds."; 2250 } 2251 leaf two-way-max-delay-normality { 2252 type te-types:performance-metrics-normality; 2253 default "normal"; 2254 description 2255 "Two-way maximum delay or latency normality."; 2256 reference 2257 "RFC 7471: OSPF Traffic Engineering (TE) Metric 2258 Extensions 2259 RFC 7823: Performance-Based Path Selection for 2260 Explicitly Routed Label Switched Paths (LSPs) Using 2261 TE Metric Extensions 2262 RFC 8570: IS-IS Traffic Engineering (TE) Metric 2263 Extensions"; 2264 } 2265 leaf two-way-delay-variation { 2266 type uint32 { 2267 range "0..16777215"; 2268 } 2269 default "0"; 2270 description 2271 "Two-way delay variation in microseconds."; 2272 reference 2273 "RFC 5481: Packet Delay Variation Applicability 2274 Statement, Section 4.2"; 2275 } 2276 leaf two-way-delay-variation-normality { 2277 type te-types:performance-metrics-normality; 2278 default "normal"; 2279 description 2280 "Two-way delay variation normality."; 2281 reference 2282 "RFC 7471: OSPF Traffic Engineering (TE) Metric 2283 Extensions 2284 RFC 7823: Performance-Based Path Selection for 2285 Explicitly Routed Label Switched Paths (LSPs) Using 2286 TE Metric Extensions 2287 RFC 8570: IS-IS Traffic Engineering (TE) Metric 2288 Extensions"; 2289 } 2290 leaf two-way-packet-loss { 2291 type decimal64 { 2292 fraction-digits 6; 2293 range "0..50.331642"; 2294 } 2295 default "0"; 2296 description 2297 "Two-way packet loss as a percentage of the total traffic 2298 sent over a configurable interval. The finest precision 2299 is 0.000003%."; 2300 } 2301 leaf two-way-packet-loss-normality { 2302 type te-types:performance-metrics-normality; 2303 default "normal"; 2304 description 2305 "Two-way packet loss normality."; 2306 } 2307 description 2308 "PM two-way packet-specific augmentation for a generic PM 2309 grouping."; 2310 reference 2311 "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions 2312 RFC 7823: Performance-Based Path Selection for 2313 Explicitly Routed Label Switched Paths (LSPs) Using 2314 TE Metric Extensions 2315 RFC 8570: IS-IS Traffic Engineering (TE) Metric 2316 Extensions"; 2317 } 2318 } 2319 } 2321 grouping one-way-performance-metrics-packet { 2322 description 2323 "One-way packet PM throttle grouping."; 2324 leaf one-way-min-delay { 2325 type uint32 { 2326 range "0..16777215"; 2327 } 2328 default "0"; 2329 description 2330 "One-way minimum delay or latency in microseconds."; 2331 } 2332 leaf one-way-max-delay { 2333 type uint32 { 2334 range "0..16777215"; 2335 } 2336 default "0"; 2337 description 2338 "One-way maximum delay or latency in microseconds."; 2339 } 2340 leaf one-way-delay-variation { 2341 type uint32 { 2342 range "0..16777215"; 2343 } 2344 default "0"; 2345 description 2346 "One-way delay variation in microseconds."; 2347 } 2348 leaf one-way-packet-loss { 2349 type decimal64 { 2350 fraction-digits 6; 2351 range "0..50.331642"; 2352 } 2353 default "0"; 2354 description 2355 "One-way packet loss as a percentage of the total traffic 2356 sent over a configurable interval. The finest precision is 2357 0.000003%."; 2358 } 2359 } 2361 grouping two-way-performance-metrics-packet { 2362 description 2363 "Two-way packet PM throttle grouping."; 2364 leaf two-way-min-delay { 2365 type uint32 { 2366 range "0..16777215"; 2367 } 2368 default "0"; 2369 description 2370 "Two-way minimum delay or latency in microseconds."; 2371 } 2372 leaf two-way-max-delay { 2373 type uint32 { 2374 range "0..16777215"; 2375 } 2376 default "0"; 2377 description 2378 "Two-way maximum delay or latency in microseconds."; 2379 } 2380 leaf two-way-delay-variation { 2381 type uint32 { 2382 range "0..16777215"; 2383 } 2384 default "0"; 2385 description 2386 "Two-way delay variation in microseconds."; 2387 } 2388 leaf two-way-packet-loss { 2389 type decimal64 { 2390 fraction-digits 6; 2391 range "0..50.331642"; 2392 } 2393 default "0"; 2394 description 2395 "Two-way packet loss as a percentage of the total traffic 2396 sent over a configurable interval. The finest precision is 2397 0.000003%."; 2398 } 2400 } 2402 grouping performance-metrics-throttle-container-packet { 2403 description 2404 "Packet PM threshold grouping."; 2405 uses te-types:performance-metrics-throttle-container { 2406 augment "throttle/threshold-out" { 2407 uses one-way-performance-metrics-packet; 2408 uses two-way-performance-metrics-packet; 2409 description 2410 "PM threshold-out packet augmentation for a 2411 generic grouping."; 2412 } 2413 augment "throttle/threshold-in" { 2414 uses one-way-performance-metrics-packet; 2415 uses two-way-performance-metrics-packet; 2416 description 2417 "PM threshold-in packet augmentation for a 2418 generic grouping."; 2419 } 2420 augment "throttle/threshold-accelerated-advertisement" { 2421 uses one-way-performance-metrics-packet; 2422 uses two-way-performance-metrics-packet; 2423 description 2424 "PM accelerated advertisement packet augmentation for a 2425 generic grouping."; 2426 } 2427 } 2428 } 2430 grouping te-packet-path-bandwidth { 2431 description 2432 "Path bandwidth for Packet. "; 2433 leaf bandwidth-profile-name{ 2434 type string; 2435 description "Name of Bandwidth Profile."; 2436 } 2437 leaf bandwidth-profile-type { 2438 type identityref { 2439 base bandwidth-profile-type; 2440 } 2441 description "Type of Bandwidth Profile."; 2442 } 2444 leaf cir { 2445 type uint64; 2446 description 2447 "Committed Information Rate in Kbps"; 2449 } 2451 leaf eir { 2452 type uint64; 2453 /* 2454 Need to indicate that EIR is not supported by RFC 2697 2456 must 2458 '../bw-profile-type = "etht-types:mef-10-bwp" or ' + 2459 '../bw-profile-type = "etht-types:rfc-2698-bwp" or ' + 2460 '../bw-profile-type = "etht-types:rfc-4115-bwp"' 2462 must 2463 '../bw-profile-type != "etht-types:rfc-2697-bwp"' 2464 */ 2465 description 2466 "Excess Information Rate in Kbps 2467 In case of RFC 2698, PIR = CIR + EIR"; 2468 } 2470 leaf cbs { 2471 type uint64; 2472 description 2473 "Committed Burst Size in in KBytes"; 2474 } 2476 leaf ebs { 2477 type uint64; 2478 description 2479 "Excess Burst Size in KBytes. 2480 In case of RFC 2698, PBS = CBS + EBS"; 2481 } 2482 } 2484 grouping te-packet-link-bandwidth { 2485 description 2486 "Link Bandwidth for Packet. "; 2487 leaf packet-bandwidth { 2488 type bandwidth-scientific-notation; 2489 description 2490 "Available bandwith value expressed in kilobits per 2491 second"; 2492 } 2493 } 2494 } 2495 2497 6.3. Packet Switching TE Topology Module 2499 This module references [RFC7471], [RFC7823], [RFC8294], [RFC8345], 2500 [RFC8346]. [RFC8570], [RFC8776], and [RFC8795]. 2502 file "ietf-te-topology-packet@2021-07-11.yang" 2503 module ietf-te-topology-packet { 2504 yang-version 1.1; 2505 namespace "urn:ietf:params:xml:ns:yang:ietf-te-topology-packet"; 2507 prefix "tet-pkt"; 2509 import ietf-network { 2510 prefix "nw"; 2511 reference 2512 "RFC 8345: A YANG Data Model for Network Topologies"; 2513 } 2515 import ietf-network-topology { 2516 prefix "nt"; 2517 reference 2518 "RFC 8345: A YANG Data Model for Network Topologies"; 2519 } 2521 import ietf-routing-types { 2522 prefix "rt-types"; 2523 reference 2524 "RFC 8294: Common YANG Data Types for the Routing Area"; 2525 } 2527 import ietf-te-topology { 2528 prefix "tet"; 2529 reference 2530 "I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic 2531 Engineering (TE) Topologies"; 2532 } 2534 import ietf-te-types { 2535 prefix "te-types"; 2536 reference 2537 "I-D.ietf-teas-yang-te-types: Traffic Engineering Common YANG 2538 Types"; 2539 } 2541 import ietf-te-packet-types { 2542 prefix "te-packet-types"; 2543 reference 2544 "I-D.ietf-teas-yang-te-types: Traffic Engineering Common YANG 2545 Types"; 2546 } 2548 organization 2549 "Traffic Engineering Architecture and Signaling (TEAS) 2550 Working Group"; 2552 contact 2553 "WG Web: 2554 WG List: 2556 Editor: Xufeng Liu 2557 2559 Editor: Igor Bryskin 2560 2562 Editor: Vishnu Pavan Beeram 2563 2565 Editor: Tarek Saad 2566 2568 Editor: Himanshu Shah 2569 2571 Editor: Oscar Gonzalez De Dios 2572 "; 2574 description 2575 "YANG data model for representing and manipulating PSC (Packet 2576 Switching) TE Topologies. 2578 Copyright (c) 2018 IETF Trust and the persons identified as 2579 authors of the code. All rights reserved. 2581 Redistribution and use in source and binary forms, with or 2582 without modification, is permitted pursuant to, and subject to 2583 the license terms contained in, the Simplified BSD License set 2584 forth in Section 4.c of the IETF Trust's Legal Provisions 2585 Relating to IETF Documents 2586 (http://trustee.ietf.org/license-info). 2588 This version of this YANG module is part of RFC XXXX; see the 2589 RFC itself for full legal notices."; 2591 revision 2021-07-11 { 2592 description 2593 "Initial revision"; 2594 reference 2595 "RFC XXXX: YANG Data Model for Layer 3 TE Topologies"; 2596 } 2598 /* 2599 * Features 2600 */ 2602 feature te-performance-metric { 2603 description 2604 "This feature indicates that the system supports 2605 TE performance metric."; 2606 reference 2607 "RFC7471: OSPF Traffic Engineering (TE) Metric Extensions. 2608 RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions. 2609 RFC7823: Performance-Based Path Selection for Explicitly 2610 Routed Label Switched Paths (LSPs) Using TE Metric 2611 Extensions"; 2612 } 2614 /* 2615 * Groupings 2616 */ 2617 grouping packet-switch-capable-container { 2618 description 2619 "The container of packet switch capable attributes."; 2620 container packet-switch-capable { 2621 description 2622 "Interface has packet-switching capabilities."; 2623 leaf minimum-lsp-bandwidth { 2624 type rt-types:bandwidth-ieee-float32; 2625 description 2626 "Minimum LSP Bandwidth. Units in bytes per second"; 2627 } 2628 leaf interface-mtu { 2629 type uint16; 2630 description 2631 "Interface MTU."; 2632 } 2633 } 2634 } 2636 /* 2637 * Augmentations 2638 */ 2639 /* Augmentations to network-types */ 2640 augment "/nw:networks/nw:network/nw:network-types/" 2641 + "tet:te-topology" { 2642 description 2643 "Defines the packet TE topology type."; 2644 container packet { 2645 presence "Indicates packet TE topology."; 2646 description 2647 "Its presence identifies the packet TE topology type."; 2648 } 2649 } 2651 /* Augmentations to connectivity-matrix */ 2652 augment "/nw:networks/nw:network/nw:node/tet:te/" 2653 + "tet:te-node-attributes/tet:connectivity-matrices" { 2654 when "../../../../nw:network-types/tet:te-topology/" 2655 + "tet-pkt:packet" { 2656 description 2657 "Augment only for packet TE topology"; 2658 } 2659 description 2660 "Parameters for PSC TE topology."; 2661 uses te-packet-types:performance-metrics-attributes-packet { 2662 if-feature te-performance-metric; 2663 refine performance-metrics-one-way { 2664 config false; 2665 } 2666 refine performance-metrics-two-way { 2667 config false; 2668 } 2669 } 2670 uses 2671 te-packet-types:performance-metrics-throttle-container-packet { 2672 if-feature te-performance-metric; 2673 } 2674 } 2676 augment "/nw:networks/nw:network/nw:node/tet:te/" 2677 + "tet:te-node-attributes/tet:connectivity-matrices/" 2678 + "tet:connectivity-matrix" { 2679 when "../../../../../nw:network-types/tet:te-topology/" 2680 + "tet-pkt:packet" { 2681 description 2682 "Augment only for packet TE topology"; 2683 } 2684 description 2685 "Parameters for PSC TE topology."; 2686 uses te-packet-types:performance-metrics-attributes-packet { 2687 if-feature te-performance-metric; 2688 refine performance-metrics-one-way { 2689 config false; 2690 } 2691 refine performance-metrics-two-way { 2692 config false; 2693 } 2694 } 2695 uses 2696 te-packet-types:performance-metrics-throttle-container-packet { 2697 if-feature te-performance-metric; 2698 } 2699 } 2701 augment "/nw:networks/nw:network/nw:node/tet:te/" 2702 + "tet:information-source-entry/tet:connectivity-matrices" { 2703 when "../../../../nw:network-types/tet:te-topology/" 2704 + "tet-pkt:packet" { 2705 description 2706 "Augment only for packet TE topology"; 2707 } 2708 description 2709 "Parameters for PSC TE topology."; 2710 uses te-packet-types:performance-metrics-attributes-packet { 2711 if-feature te-performance-metric; 2712 } 2713 uses 2714 te-packet-types:performance-metrics-throttle-container-packet { 2715 if-feature te-performance-metric; 2716 } 2717 } 2719 augment "/nw:networks/nw:network/nw:node/tet:te/" 2720 + "tet:information-source-entry/tet:connectivity-matrices/" 2721 + "tet:connectivity-matrix" { 2722 when "../../../../../nw:network-types/tet:te-topology/" 2723 + "tet-pkt:packet" { 2724 description 2725 "Augment only for packet TE topology"; 2726 } 2727 description 2728 "Parameters for PSC TE topology."; 2729 uses te-packet-types:performance-metrics-attributes-packet { 2730 if-feature te-performance-metric; 2731 } 2732 uses 2733 te-packet-types:performance-metrics-throttle-container-packet { 2734 if-feature te-performance-metric; 2735 } 2737 } 2739 /* Augmentations to tunnel-termination-point */ 2740 augment "/nw:networks/nw:network/nw:node/tet:te/" 2741 + "tet:tunnel-termination-point/" 2742 + "tet:local-link-connectivities" { 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 augment "/nw:networks/nw:network/nw:node/tet:te/" 2766 + "tet:tunnel-termination-point/" 2767 + "tet:local-link-connectivities/" 2768 + "tet:local-link-connectivity" { 2769 when "../../../../../nw:network-types/tet:te-topology/" 2770 + "tet-pkt:packet" { 2771 description 2772 "Augment only for packet TE topology"; 2773 } 2774 description 2775 "Parameters for PSC TE topology."; 2776 uses te-packet-types:performance-metrics-attributes-packet { 2777 if-feature te-performance-metric; 2778 refine performance-metrics-one-way { 2779 config false; 2780 } 2781 refine performance-metrics-two-way { 2782 config false; 2783 } 2784 } 2785 uses 2786 te-packet-types:performance-metrics-throttle-container-packet { 2787 if-feature te-performance-metric; 2788 } 2789 } 2791 /* Augmentations to te-link-attributes */ 2792 augment "/nw:networks/tet:te/tet:templates/" 2793 + "tet:link-template/tet:te-link-attributes" { 2794 when "tet:interface-switching-capability " 2795 + "[tet:switching-capability = 'te-types:switching-psc1']" { 2796 description 2797 "Valid only for PSC"; 2798 } 2799 description 2800 "Parameters for PSC TE topology."; 2801 uses te-packet-types:performance-metrics-attributes-packet { 2802 if-feature te-performance-metric; 2803 refine performance-metrics-one-way { 2804 config false; 2805 } 2806 refine performance-metrics-two-way { 2807 config false; 2808 } 2809 } 2810 uses 2811 te-packet-types:performance-metrics-throttle-container-packet { 2812 if-feature te-performance-metric; 2813 } 2814 } 2816 augment "/nw:networks/nw:network/nt:link/tet:te/" 2817 + "tet:te-link-attributes" { 2818 when "(../../../nw:network-types/tet:te-topology/tet-pkt:packet)" 2819 + " and (tet:interface-switching-capability " 2820 + "[tet:switching-capability = 'te-types:switching-psc1'])" { 2821 description 2822 "Valid only for PSC"; 2823 } 2824 description 2825 "Parameters for PSC TE topology."; 2826 uses te-packet-types:performance-metrics-attributes-packet { 2827 if-feature te-performance-metric; 2828 refine performance-metrics-one-way { 2829 config false; 2830 } 2831 refine performance-metrics-two-way { 2832 config false; 2834 } 2835 } 2836 uses 2837 te-packet-types:performance-metrics-throttle-container-packet { 2838 if-feature te-performance-metric; 2839 } 2840 } 2842 augment "/nw:networks/nw:network/nt:link/tet:te/" 2843 + "tet:information-source-entry" { 2844 when "(../../../nw:network-types/tet:te-topology/tet-pkt:packet)" 2845 + " and (tet:interface-switching-capability " 2846 + "[tet:switching-capability = 'te-types:switching-psc1'])" { 2847 description 2848 "Valid only for PSC"; 2849 } 2850 description 2851 "Parameters for PSC TE topology."; 2852 uses te-packet-types:performance-metrics-attributes-packet { 2853 if-feature te-performance-metric; 2854 } 2855 uses 2856 te-packet-types:performance-metrics-throttle-container-packet { 2857 if-feature te-performance-metric; 2858 } 2859 } 2861 /* Augmentations to interface-switching-capability */ 2862 augment "/nw:networks/tet:te/tet:templates/" 2863 + "tet:link-template/tet:te-link-attributes/" 2864 + "tet:interface-switching-capability" { 2865 when "tet:switching-capability = 'te-types:switching-psc1' " { 2866 description 2867 "Valid only for PSC"; 2868 } 2869 description 2870 "Parameters for PSC TE topology."; 2871 uses packet-switch-capable-container; 2872 } 2874 augment "/nw:networks/nw:network/nt:link/tet:te/" 2875 + "tet:te-link-attributes/" 2876 + "tet:interface-switching-capability" { 2877 when "(../../../../nw:network-types/tet:te-topology/" 2878 + "tet-pkt:packet) and " 2879 + "(tet:switching-capability = 'te-types:switching-psc1')" { 2880 description 2881 "Valid only for PSC"; 2883 } 2884 description 2885 "Parameters for PSC TE topology."; 2886 uses packet-switch-capable-container; 2887 } 2889 augment "/nw:networks/nw:network/nt:link/tet:te/" 2890 + "tet:information-source-entry/" 2891 + "tet:interface-switching-capability" { 2892 when "(../../../../nw:network-types/tet:te-topology/" 2893 + "tet-pkt:packet) and " 2894 + "(tet:switching-capability = 'te-types:switching-psc1')" { 2895 description 2896 "Valid only for PSC"; 2897 } 2898 description 2899 "Parameters for PSC TE topology."; 2900 uses packet-switch-capable-container; 2901 } 2903 /* 2904 * Augment TE bandwidth 2905 */ 2907 augment "/nw:networks/nw:network/nw:node/nt:termination-point/" 2908 + "tet:te/" 2909 + "tet:interface-switching-capability/tet:max-lsp-bandwidth/" 2910 + "tet:te-bandwidth/tet:technology" { 2911 when "../../../../../../nw:network-types/tet:te-topology/" 2912 + "tet-pkt:packet" { 2913 description 2914 "Augmentation parameters apply only for networks with 2915 Packet TE topology type."; 2916 } 2917 description 2918 "Augment maximum LSP TE bandwidth for the link termination 2919 point (LTP)."; 2920 case packet { 2921 uses te-packet-types:te-packet-path-bandwidth; 2922 } 2923 } 2925 augment "/nw:networks/nw:network/nw:node/tet:te/" 2926 + "tet:te-node-attributes/tet:connectivity-matrices/" 2927 + "tet:path-constraints/tet:te-bandwidth/tet:technology" { 2928 when "../../../../../../nw:network-types/tet:te-topology/" 2929 + "tet-pkt:packet" { 2930 description 2931 "Augmentation parameters apply only for networks with 2932 Packet TE topology type."; 2933 } 2934 description 2935 "Augment TE bandwidth path constraints of the TE node 2936 connectivity matrices."; 2937 case packet { 2938 uses te-packet-types:te-packet-link-bandwidth; 2939 } 2940 } 2942 augment "/nw:networks/nw:network/nw:node/tet:te/" 2943 + "tet:te-node-attributes/tet:connectivity-matrices/" 2944 + "tet:connectivity-matrix/" 2945 + "tet:path-constraints/tet:te-bandwidth/tet:technology" { 2946 when "../../../../../../../nw:network-types/tet:te-topology/" 2947 + "tet-pkt:packet" { 2948 description 2949 "Augmentation parameters apply only for networks with 2950 Packet TE topology type."; 2951 } 2952 description 2953 "Augment TE bandwidth path constraints of the 2954 connectivity matrix entry."; 2955 case packet { 2956 uses te-packet-types:te-packet-link-bandwidth; 2957 } 2958 } 2960 augment "/nw:networks/nw:network/nw:node/tet:te/" 2961 + "tet:information-source-entry/tet:connectivity-matrices/" 2962 + "tet:path-constraints/tet:te-bandwidth/tet:technology" { 2963 when "../../../../../../nw:network-types/tet:te-topology/" 2964 + "tet-pkt:packet" { 2965 description 2966 "Augmentation parameters apply only for networks with 2967 Packet TE topology type."; 2968 } 2969 description 2970 "Augment TE bandwidth path constraints of the TE node 2971 connectivity matrices information source."; 2972 case packet { 2973 uses te-packet-types:te-packet-link-bandwidth; 2974 } 2975 } 2977 augment "/nw:networks/nw:network/nw:node/tet:te/" 2978 + "tet:information-source-entry/tet:connectivity-matrices/" 2979 + "tet:connectivity-matrix/" 2980 + "tet:path-constraints/tet:te-bandwidth/tet:technology" { 2981 when "../../../../../../../nw:network-types/tet:te-topology/" 2982 + "tet-pkt:packet" { 2983 description 2984 "Augmentation parameters apply only for networks with 2985 Packet TE topology type."; 2986 } 2987 description 2988 "Augment TE bandwidth path constraints of the 2989 connectivity matrix entry information source"; 2990 case packet { 2991 uses te-packet-types:te-packet-link-bandwidth; 2992 } 2993 } 2995 augment "/nw:networks/nw:network/nw:node/tet:te/" 2996 + "tet:tunnel-termination-point/" 2997 + "tet:client-layer-adaptation/tet:switching-capability/" 2998 + "tet:te-bandwidth/tet:technology" { 2999 when "../../../../../../nw:network-types/tet:te-topology/" 3000 + "tet-pkt:packet" { 3001 description 3002 "Augmentation parameters apply only for networks with 3003 Packet TE topology type."; 3004 } 3005 description 3006 "Augment client TE bandwidth of the tunnel termination point 3007 (TTP)"; 3008 case packet { 3009 uses te-packet-types:te-packet-link-bandwidth; 3010 } 3011 } 3013 augment "/nw:networks/nw:network/nw:node/tet:te/" 3014 + "tet:tunnel-termination-point/" 3015 + "tet:local-link-connectivities/tet:path-constraints/" 3016 + "tet:te-bandwidth/tet:technology" { 3017 when "../../../../../../nw:network-types/tet:te-topology/" 3018 + "tet-pkt:packet" { 3019 description 3020 "Augmentation parameters apply only for networks with 3021 Packet TE topology type."; 3022 } 3023 description 3024 "Augment TE bandwidth path constraints for the TTP 3025 Local Link Connectivities."; 3026 case packet { 3027 uses te-packet-types:te-packet-link-bandwidth; 3028 } 3029 } 3031 augment "/nw:networks/nw:network/nw:node/tet:te/" 3032 + "tet:tunnel-termination-point/" 3033 + "tet:local-link-connectivities/" 3034 + "tet:local-link-connectivity/tet:path-constraints/" 3035 + "tet:te-bandwidth/tet:technology" { 3036 when "../../../../../../../nw:network-types/tet:te-topology/" 3037 + "tet-pkt:packet" { 3038 description 3039 "Augmentation parameters apply only for networks with 3040 Packet TE topology type."; 3041 } 3042 description 3043 "Augment TE bandwidth path constraints for the TTP 3044 Local Link Connectivity entry."; 3045 case packet { 3046 uses te-packet-types:te-packet-link-bandwidth; 3047 } 3048 } 3050 augment "/nw:networks/nw:network/nt:link/tet:te/" 3051 + "tet:te-link-attributes/" 3052 + "tet:interface-switching-capability/tet:max-lsp-bandwidth/" 3053 + "tet:te-bandwidth/tet:technology" { 3054 when "../../../../../../nw:network-types/tet:te-topology/" 3055 + "tet-pkt:packet" { 3056 description 3057 "Augmentation parameters apply only for networks with 3058 Packet TE topology type."; 3059 } 3060 description 3061 "Augment maximum LSP TE bandwidth for the TE link."; 3062 case packet { 3063 uses te-packet-types:te-packet-path-bandwidth; 3064 } 3065 } 3067 augment "/nw:networks/nw:network/nt:link/tet:te/" 3068 + "tet:te-link-attributes/" 3069 + "tet:max-link-bandwidth/" 3070 + "tet:te-bandwidth/tet:technology" { 3071 when "../../../../../nw:network-types/tet:te-topology/" 3072 + "tet-pkt:packet" { 3073 description 3074 "Augmentation parameters apply only for networks with 3075 Packet TE topology type."; 3076 } 3077 description 3078 "Augment maximum TE bandwidth for the TE link"; 3079 case packet { 3080 uses te-packet-types:te-packet-link-bandwidth; 3081 } 3082 } 3084 augment "/nw:networks/nw:network/nt:link/tet:te/" 3085 + "tet:te-link-attributes/" 3086 + "tet:max-resv-link-bandwidth/" 3087 + "tet:te-bandwidth/tet:technology" { 3088 when "../../../../../nw:network-types/tet:te-topology/" 3089 + "tet-pkt:packet" { 3090 description 3091 "Augmentation parameters apply only for networks with 3092 Packet TE topology type."; 3093 } 3094 description 3095 "Augment maximum reservable TE bandwidth for the TE link"; 3096 case packet { 3097 uses te-packet-types:te-packet-link-bandwidth; 3098 } 3099 } 3101 augment "/nw:networks/nw:network/nt:link/tet:te/" 3102 + "tet:te-link-attributes/" 3103 + "tet:unreserved-bandwidth/" 3104 + "tet:te-bandwidth/tet:technology" { 3105 when "../../../../../nw:network-types/tet:te-topology/" 3106 + "tet-pkt:packet" { 3107 description 3108 "Augmentation parameters apply only for networks with 3109 Packet TE topology type."; 3110 } 3111 description 3112 "Augment unreserved TE bandwidth for the TE Link"; 3113 case packet { 3114 uses te-packet-types:te-packet-link-bandwidth; 3115 } 3116 } 3118 augment "/nw:networks/nw:network/nt:link/tet:te/" 3119 + "tet:information-source-entry/" 3120 + "tet:interface-switching-capability/" 3121 + "tet:max-lsp-bandwidth/" 3122 + "tet:te-bandwidth/tet:technology" { 3124 when "../../../../../../nw:network-types/tet:te-topology/" 3125 + "tet-pkt:packet" { 3126 description 3127 "Augmentation parameters apply only for networks with 3128 Packet TE topology type."; 3129 } 3130 description 3131 "Augment maximum LSP TE bandwidth for the TE link 3132 information source"; 3133 case packet { 3134 uses te-packet-types:te-packet-path-bandwidth; 3135 } 3136 } 3138 augment "/nw:networks/nw:network/nt:link/tet:te/" 3139 + "tet:information-source-entry/" 3140 + "tet:max-link-bandwidth/" 3141 + "tet:te-bandwidth/tet:technology" { 3142 when "../../../../../nw:network-types/tet:te-topology/" 3143 + "tet-pkt:packet" { 3144 description 3145 "Augmentation parameters apply only for networks with 3146 Packet TE topology type."; 3147 } 3148 description 3149 "Augment maximum TE bandwidth for the TE link 3150 information source"; 3151 case packet { 3152 uses te-packet-types:te-packet-link-bandwidth; 3153 } 3154 } 3156 augment "/nw:networks/nw:network/nt:link/tet:te/" 3157 + "tet:information-source-entry/" 3158 + "tet:max-resv-link-bandwidth/" 3159 + "tet:te-bandwidth/tet:technology" { 3160 when "../../../../../nw:network-types/tet:te-topology/" 3161 + "tet-pkt:packet" { 3162 description 3163 "Augmentation parameters apply only for networks with 3164 Packet TE topology type."; 3165 } 3166 description 3167 "Augment maximum reservable TE bandwidth for the TE link 3168 information-source"; 3169 case packet { 3170 uses te-packet-types:te-packet-link-bandwidth; 3171 } 3173 } 3175 augment "/nw:networks/nw:network/nt:link/tet:te/" 3176 + "tet:information-source-entry/" 3177 + "tet:unreserved-bandwidth/" 3178 + "tet:te-bandwidth/tet:technology" { 3179 when "../../../../../nw:network-types/tet:te-topology/" 3180 + "tet-pkt:packet" { 3181 description 3182 "Augmentation parameters apply only for networks with 3183 Packet TE topology type."; 3184 } 3185 description 3186 "Augment unreserved TE bandwidth of the TE link 3187 information source"; 3188 case packet { 3189 uses te-packet-types:te-packet-link-bandwidth; 3190 } 3191 } 3193 augment "/nw:networks/tet:te/tet:templates/" 3194 + "tet:link-template/tet:te-link-attributes/" 3195 + "tet:interface-switching-capability/" 3196 + "tet:max-lsp-bandwidth/" 3197 + "tet:te-bandwidth/tet:technology" { 3198 description 3199 "Augment maximum LSP TE bandwidth of the TE link 3200 template"; 3201 case packet { 3202 uses te-packet-types:te-packet-path-bandwidth; 3203 } 3204 } 3206 augment "/nw:networks/tet:te/tet:templates/" 3207 + "tet:link-template/tet:te-link-attributes/" 3208 + "tet:max-link-bandwidth/" 3209 + "tet:te-bandwidth/tet:technology" { 3210 description 3211 "Augment maximum TE bandwidth the TE link template"; 3212 case packet { 3213 uses te-packet-types:te-packet-link-bandwidth; 3214 } 3215 } 3217 augment "/nw:networks/tet:te/tet:templates/" 3218 + "tet:link-template/tet:te-link-attributes/" 3219 + "tet:max-resv-link-bandwidth/" 3220 + "tet:te-bandwidth/tet:technology" { 3222 description 3223 "Augment maximum reservable TE bandwidth for the TE link 3224 template."; 3225 case packet { 3226 uses te-packet-types:te-packet-link-bandwidth; 3227 } 3228 } 3230 augment "/nw:networks/tet:te/tet:templates/" 3231 + "tet:link-template/tet:te-link-attributes/" 3232 + "tet:unreserved-bandwidth/" 3233 + "tet:te-bandwidth/tet:technology" { 3234 description 3235 "Augment unreserved TE bandwidth the TE link template"; 3236 case packet { 3237 uses te-packet-types:te-packet-link-bandwidth; 3238 } 3239 } 3240 } 3241 3243 7. IANA Considerations 3245 RFC Ed.: In this section, replace all occurrences of 'XXXX' with the 3246 actual RFC number (and remove this note). 3248 This document registers the following namespace URIs in the IETF XML 3249 registry [RFC3688]: 3251 -------------------------------------------------------------------- 3252 URI: urn:ietf:params:xml:ns:yang:ietf-l3-te-topology 3253 Registrant Contact: The IESG. 3254 XML: N/A, the requested URI is an XML namespace. 3255 -------------------------------------------------------------------- 3257 -------------------------------------------------------------------- 3258 URI: urn:ietf:params:xml:ns:yang:ietf-l3-te-topology-state 3259 Registrant Contact: The IESG. 3260 XML: N/A, the requested URI is an XML namespace. 3261 -------------------------------------------------------------------- 3263 -------------------------------------------------------------------- 3264 URI: urn:ietf:params:xml:ns:yang:ietf-te-topology-packet 3265 Registrant Contact: The IESG. 3266 XML: N/A, the requested URI is an XML namespace. 3267 -------------------------------------------------------------------- 3268 -------------------------------------------------------------------- 3269 URI: urn:ietf:params:xml:ns:yang:ietf-te-topology-packet-state 3270 Registrant Contact: The IESG. 3271 XML: N/A, the requested URI is an XML namespace. 3272 -------------------------------------------------------------------- 3274 This document registers the following YANG modules in the YANG Module 3275 Names registry [RFC6020]: 3277 -------------------------------------------------------------------- 3278 name: ietf-l3-te-topology 3279 namespace: urn:ietf:params:xml:ns:yang:ietf-l3-te-topology 3280 prefix: l3tet 3281 reference: RFC XXXX 3282 -------------------------------------------------------------------- 3284 -------------------------------------------------------------------- 3285 name: ietf-l3-te-topology-state 3286 namespace: urn:ietf:params:xml:ns:yang:ietf-l3-te-topology-state 3287 prefix: l3tet-s 3288 reference: RFC XXXX 3289 -------------------------------------------------------------------- 3291 -------------------------------------------------------------------- 3292 name: ietf-te-topology-packet 3293 namespace: urn:ietf:params:xml:ns:yang:ietf-te-topology-packet 3294 prefix: tet-pkt 3295 reference: RFC XXXX 3296 -------------------------------------------------------------------- 3298 -------------------------------------------------------------------- 3299 name: ietf-te-topology-packet-state 3300 namespace: urn:ietf:params:xml:ns:yang:ietf-te-topology-packet-state 3301 prefix: tet-pkt-s 3302 reference: RFC XXXX 3303 -------------------------------------------------------------------- 3305 8. Security Considerations 3307 The YANG module specified in this document defines a schema for data 3308 that is designed to be accessed via network management protocols such 3309 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 3310 is the secure transport layer, and the mandatory-to-implement secure 3311 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 3312 is HTTPS, and the mandatory-to-implement secure transport is TLS 3313 [RFC8446]. 3315 The Network Configuration Access Control Model (NACM) [RFC8341] 3316 provides the means to restrict access for particular NETCONF or 3317 RESTCONF users to a preconfigured subset of all available NETCONF or 3318 RESTCONF protocol operations and content. 3320 There are a number of data nodes defined in this YANG module that are 3321 writable/creatable/deletable (i.e., config true, which is the 3322 default). These data nodes may be considered sensitive or vulnerable 3323 in some network environments. Write operations (e.g., edit-config) 3324 to these data nodes without proper protection can have a negative 3325 effect on network operations. These are the subtrees and data nodes 3326 and their sensitivity/vulnerability: 3328 /nw:networks/nw:network/nw:network-types/l3t:l3-unicast-topology/ 3329 l3-te 3330 This subtree specifies the layer 3 TE topology type. Modifying 3331 the configurations can make layer 3 TE topology type invalid and 3332 cause interruption to all layer 3 TE networks. 3334 /nw:networks/nw:network/l3t:l3-topology-attributes/l3-te-topology- 3335 attributes 3336 This subtree specifies the topology-wide configurations, including 3337 the reference to a TE topology from a layer 3 TE topology. 3338 Modifying the configurations here can cause traffic disabled or 3339 rerouted in this topology and the connected topologies. 3341 /nw:networks/nw:network/nw:node/l3t:l3-node-attributes/l3-te-node- 3342 attributes 3343 This subtree specifies the configurations of layer 3 TE nodes. 3344 Modifying the configurations in this subtree can change the 3345 relationship between a TE node and a node in a layer 3 TE 3346 topology, causing traffic disabled or rerouted in the specified 3347 nodes and the related layer 3 topologies. 3349 /nw:networks/nw:network/nw:node/nt:termination-point//l3t:l3- 3350 termination-point-attributes/l3-te-tp-attributes 3351 This subtree specifies the configurations of layer 3 TE link 3352 termination points. Modifying the configurations in this subtree 3353 can change the relationship between a TE link termination point 3354 and a link termination point in a layer 3 TE topology, causing 3355 traffic disabled or rerouted on the related layer 3 links and the 3356 related layer 3 topologies. 3358 /nw:networks/nw:network/nt:link/l3t:l3-link-attributes/l3-te-link- 3359 attributes 3360 This subtree specifies the configurations of layer 3 TE links. 3361 Modifying the configurations in this subtree can change the 3362 relationship between a TE link and a link in a layer 3 TE 3363 topology, causing traffic disabled or rerouted on the specified 3364 layer 3 link and the related layer 3 topologies. 3366 performance-metric containers 3367 The container "performance-metric" is augmented to multiple 3368 locations of the base TE topology model, as specified in 3369 Section 3.2. Modifying the configuration in such a container can 3370 change the behaviors of performance metric monitoring, causing 3371 traffic disabled or rerouted on the related layer 3 links, nodes, 3372 or topologies. 3374 Some of the readable data nodes in this YANG module may be considered 3375 sensitive or vulnerable in some network environments. It is thus 3376 important to control read access (e.g., via get, get-config, or 3377 notification) to these data nodes. These are the subtrees and data 3378 nodes and their sensitivity/vulnerability: 3380 /nw:networks/nw:network/nw:network-types/l3t:l3-unicast-topology/ 3381 l3-te 3382 Unauthorized access to this subtree can disclose the layer 3 TE 3383 topology type. 3385 /nw:networks/nw:network/l3t:l3-topology-attributes/l3-te-topology- 3386 attributes 3387 Unauthorized access to this subtree can disclose the topology-wide 3388 configurations, including the reference to a TE topology from a 3389 layer 3 topology. 3391 /nw:networks/nw:network/nw:node/l3t:l3-node-attributes/l3-te-node- 3392 attributes 3393 Unauthorized access to this subtree can disclose the operational 3394 state information of layer 3 TE nodes. 3396 /nw:networks/nw:network/nw:node/nt:termination-point//l3t:l3- 3397 termination-point-attributes/l3-te-tp-attributes 3398 Unauthorized access to this subtree can disclose the operational 3399 state information of layer 3 TE link termination points. 3401 /nw:networks/nw:network/nt:link/l3t:l3-link-attributes/l3-te-link- 3402 attributes 3403 Unauthorized access to this subtree can disclose the operational 3404 state information of layer 3 TE links. 3406 performance-metric containers 3407 The container "performance-metric" is augmented to multiple 3408 locations of the base TE topology model, as specified in 3409 Section 3.2. Unauthorized access to this subtree can disclose the 3410 operational state information of performance metric monitoring. 3412 9. References 3414 9.1. Normative References 3416 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3417 Requirement Levels", BCP 14, RFC 2119, 3418 DOI 10.17487/RFC2119, March 1997, 3419 . 3421 [RFC2697] Heinanen, J. and R. Guerin, "A Single Rate Three Color 3422 Marker", RFC 2697, DOI 10.17487/RFC2697, September 1999, 3423 . 3425 [RFC2698] Heinanen, J. and R. Guerin, "A Two Rate Three Color 3426 Marker", RFC 2698, DOI 10.17487/RFC2698, September 1999, 3427 . 3429 [RFC3471] Berger, L., Ed., "Generalized Multi-Protocol Label 3430 Switching (GMPLS) Signaling Functional Description", 3431 RFC 3471, DOI 10.17487/RFC3471, January 2003, 3432 . 3434 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 3435 DOI 10.17487/RFC3688, January 2004, 3436 . 3438 [RFC4115] Aboul-Magd, O. and S. Rabie, "A Differentiated Service 3439 Two-Rate, Three-Color Marker with Efficient Handling of 3440 in-Profile Traffic", RFC 4115, DOI 10.17487/RFC4115, July 3441 2005, . 3443 [RFC4124] Le Faucheur, F., Ed., "Protocol Extensions for Support of 3444 Diffserv-aware MPLS Traffic Engineering", RFC 4124, 3445 DOI 10.17487/RFC4124, June 2005, 3446 . 3448 [RFC4125] Le Faucheur, F. and W. Lai, "Maximum Allocation Bandwidth 3449 Constraints Model for Diffserv-aware MPLS Traffic 3450 Engineering", RFC 4125, DOI 10.17487/RFC4125, June 2005, 3451 . 3453 [RFC4126] Ash, J., "Max Allocation with Reservation Bandwidth 3454 Constraints Model for Diffserv-aware MPLS Traffic 3455 Engineering & Performance Comparisons", RFC 4126, 3456 DOI 10.17487/RFC4126, June 2005, 3457 . 3459 [RFC4127] Le Faucheur, F., Ed., "Russian Dolls Bandwidth Constraints 3460 Model for Diffserv-aware MPLS Traffic Engineering", 3461 RFC 4127, DOI 10.17487/RFC4127, June 2005, 3462 . 3464 [RFC5481] Morton, A. and B. Claise, "Packet Delay Variation 3465 Applicability Statement", RFC 5481, DOI 10.17487/RFC5481, 3466 March 2009, . 3468 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 3469 the Network Configuration Protocol (NETCONF)", RFC 6020, 3470 DOI 10.17487/RFC6020, October 2010, 3471 . 3473 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 3474 and A. Bierman, Ed., "Network Configuration Protocol 3475 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 3476 . 3478 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 3479 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 3480 . 3482 [RFC7074] Berger, L. and J. Meuric, "Revised Definition of the GMPLS 3483 Switching Capability and Type Fields", RFC 7074, 3484 DOI 10.17487/RFC7074, November 2013, 3485 . 3487 [RFC7471] Giacalone, S., Ward, D., Drake, J., Atlas, A., and S. 3488 Previdi, "OSPF Traffic Engineering (TE) Metric 3489 Extensions", RFC 7471, DOI 10.17487/RFC7471, March 2015, 3490 . 3492 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 3493 RFC 7950, DOI 10.17487/RFC7950, August 2016, 3494 . 3496 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 3497 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 3498 . 3500 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 3501 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 3502 May 2017, . 3504 [RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger, 3505 "Common YANG Data Types for the Routing Area", RFC 8294, 3506 DOI 10.17487/RFC8294, December 2017, 3507 . 3509 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 3510 Access Control Model", STD 91, RFC 8341, 3511 DOI 10.17487/RFC8341, March 2018, 3512 . 3514 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 3515 and R. Wilton, "Network Management Datastore Architecture 3516 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 3517 . 3519 [RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N., 3520 Ananthakrishnan, H., and X. Liu, "A YANG Data Model for 3521 Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March 3522 2018, . 3524 [RFC8346] Clemm, A., Medved, J., Varga, R., Liu, X., 3525 Ananthakrishnan, H., and N. Bahadur, "A YANG Data Model 3526 for Layer 3 Topologies", RFC 8346, DOI 10.17487/RFC8346, 3527 March 2018, . 3529 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 3530 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 3531 . 3533 [RFC8570] Ginsberg, L., Ed., Previdi, S., Ed., Giacalone, S., Ward, 3534 D., Drake, J., and Q. Wu, "IS-IS Traffic Engineering (TE) 3535 Metric Extensions", RFC 8570, DOI 10.17487/RFC8570, March 3536 2019, . 3538 [RFC8776] Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, 3539 "Common YANG Data Types for Traffic Engineering", 3540 RFC 8776, DOI 10.17487/RFC8776, June 2020, 3541 . 3543 [RFC8795] Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and 3544 O. Gonzalez de Dios, "YANG Data Model for Traffic 3545 Engineering (TE) Topologies", RFC 8795, 3546 DOI 10.17487/RFC8795, August 2020, 3547 . 3549 9.2. Informative References 3551 [RFC7823] Atlas, A., Drake, J., Giacalone, S., and S. Previdi, 3552 "Performance-Based Path Selection for Explicitly Routed 3553 Label Switched Paths (LSPs) Using TE Metric Extensions", 3554 RFC 7823, DOI 10.17487/RFC7823, May 2016, 3555 . 3557 [RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG", 3558 RFC 7951, DOI 10.17487/RFC7951, August 2016, 3559 . 3561 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 3562 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 3563 . 3565 [I-D.ietf-teas-yang-te-mpls] 3566 Saad, T., Gandhi, R., Liu, X., Beeram, V. P., and I. 3567 Bryskin, "A YANG Data Model for MPLS Traffic Engineering 3568 Tunnels", draft-ietf-teas-yang-te-mpls-03 (work in 3569 progress), March 2020. 3571 [IEEE754] IEEE, "IEEE Standard for Floating-Point Arithmetic", IEEE 3572 Std 754-2008 DOI 10.1109/IEEESTD.2008.4610935, August 3573 2008. 3575 [ISO-IEC-C99] 3576 ISO/IEC, "Programming languages - C", ISO/IEC 9899: 3577 1999 /Cor.l:2001(E), September 2001. 3579 Appendix A. Companion YANG Model for Non-NMDA Compliant Implementations 3581 The YANG modules ietf-l3-te-topology and ietf-te-topology-packet 3582 defined in this document are designed to be used in conjunction with 3583 implementations that support the Network Management Datastore 3584 Architecture (NMDA) defined in [RFC8342]. In order to allow 3585 implementations to use the model even in cases when NMDA is not 3586 supported, the following companion modules, ietf-l3-te-topology-state 3587 and ietf-te-topology-packet-state, are defined as state models, which 3588 mirror the modules ietf-l3-te-topology and ietf-te-topology-packet 3589 defined earlier in this document. However, all data nodes in the 3590 companion module are non-configurable, to represent the applied 3591 configuration or the derived operational states. 3593 The companion modules, ietf-l3-te-topology-state and ietf-te- 3594 topology-packet-state, are redundant and SHOULD NOT be supported by 3595 implementations that support NMDA. 3597 As the structure of the companion modules mirrors that of the 3598 coorespinding NMDA models, the YANG trees of the companion modules 3599 are not depicted separately. 3601 A.1. Layer 3 TE Topology State Module 3603 This module references [RFC8345], and [RFC8346]. 3605 file "ietf-l3-te-topology-state@2020-05-03.yang" 3606 module ietf-l3-te-topology-state { 3607 yang-version 1.1; 3608 namespace "urn:ietf:params:xml:ns:yang:ietf-l3-te-topology-state"; 3609 prefix "l3tet-s"; 3611 import ietf-l3-te-topology { 3612 prefix "l3tet"; 3613 } 3614 import ietf-network-state { 3615 prefix "nw-s"; 3616 reference "RFC 8345: A YANG Data Model for Network Topologies"; 3617 } 3618 import ietf-network-topology-state { 3619 prefix "nt-s"; 3620 reference "RFC 8345: A YANG Data Model for Network Topologies"; 3621 } 3622 import ietf-l3-unicast-topology-state { 3623 prefix "l3t-s"; 3624 reference "RFC 8346: A YANG Data Model for Layer 3 Topologies"; 3625 } 3626 organization 3627 "IETF Traffic Engineering Architecture and Signaling (TEAS) 3628 Working Group"; 3630 contact 3631 "WG Web: 3632 WG List: 3634 Editor: Xufeng Liu 3635 3637 Editor: Igor Bryskin 3638 3640 Editor: Vishnu Pavan Beeram 3641 3643 Editor: Tarek Saad 3644 3646 Editor: Himanshu Shah 3647 3649 Editor: Oscar Gonzalez De Dios 3650 "; 3652 description 3653 "YANG data model for representing operational state information 3654 of Layer 3 TE Topologies, when NMDA is not supported. 3656 Copyright (c) 2018 IETF Trust and the persons identified as 3657 authors of the code. All rights reserved. 3659 Redistribution and use in source and binary forms, with or 3660 without modification, is permitted pursuant to, and subject to 3661 the license terms contained in, the Simplified BSD License set 3662 forth in Section 4.c of the IETF Trust's Legal Provisions 3663 Relating to IETF Documents 3664 (http://trustee.ietf.org/license-info). 3666 This version of this YANG module is part of RFC XXXX; see the 3667 RFC itself for full legal notices."; 3669 revision 2020-05-03 { 3670 description 3671 "Initial revision"; 3672 reference "RFC XXXX: YANG Data Model for Layer 3 TE Topologies"; 3673 } 3674 augment "/nw-s:networks/nw-s:network/nw-s:network-types/" 3675 + "l3t-s:l3-unicast-topology" { 3676 description 3677 "Defines the L3 TE topology type."; 3678 uses l3tet:l3-te-topology-type; 3679 } 3681 augment "/nw-s:networks/nw-s:network/" 3682 + "l3t-s:l3-topology-attributes" { 3683 when "../nw-s:network-types/l3t-s:l3-unicast-topology/" 3684 + "l3tet-s:l3-te" { 3685 description 3686 "Augment only for L3 TE topology"; 3687 } 3688 description 3689 "Augment topology configuration"; 3690 uses l3tet:l3-te-topology-attributes; 3691 } 3693 augment "/nw-s:networks/nw-s:network/nw-s:node/" 3694 + "l3t-s:l3-node-attributes" { 3695 when "../../nw-s:network-types/l3t-s:l3-unicast-topology/" 3696 + "l3tet-s:l3-te" { 3697 description 3698 "Augment only for L3 TE topology"; 3699 } 3700 description 3701 "Augment node configuration"; 3702 uses l3tet:l3-te-node-attributes; 3703 } 3705 augment "/nw-s:networks/nw-s:network/nw-s:node/" 3706 + "nt-s:termination-point/" 3707 + "l3t-s:l3-termination-point-attributes" { 3708 when "../../../nw-s:network-types/l3t-s:l3-unicast-topology/" 3709 + "l3tet-s:l3-te" { 3710 description 3711 "Augment only for L3 TE topology"; 3712 } 3713 description 3714 "Augment termination point configuration"; 3715 uses l3tet:l3-te-tp-attributes; 3716 } 3718 augment "/nw-s:networks/nw-s:network/nt-s:link/" 3719 + "l3t-s:l3-link-attributes" { 3720 when "../../nw-s:network-types/l3t-s:l3-unicast-topology/" 3721 + "l3tet-s:l3-te" { 3722 description 3723 "Augment only for L3 TE topology"; 3724 } 3725 description 3726 "Augment link configuration"; 3727 uses l3tet:l3-te-link-attributes; 3728 } 3729 } 3730 3732 A.2. Packet Switching TE Topology State Module 3734 file "ietf-te-topology-packet-state@2020-07-03.yang" 3735 module ietf-te-topology-packet-state { 3736 yang-version 1.1; 3737 namespace 3738 "urn:ietf:params:xml:ns:yang:ietf-te-topology-packet-state"; 3740 prefix "tet-pkt-s"; 3742 import ietf-te-topology-packet { 3743 prefix "tet-pkt"; 3744 } 3746 import ietf-network-state { 3747 prefix "nw-s"; 3748 reference 3749 "RFC 8345: A YANG Data Model for Network Topologies"; 3750 } 3752 import ietf-network-topology-state { 3753 prefix "nt-s"; 3754 reference 3755 "RFC 8345: A YANG Data Model for Network Topologies"; 3756 } 3758 import ietf-te-topology-state { 3759 prefix "tet-s"; 3760 reference 3761 "I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic 3762 Engineering (TE) Topologies"; 3763 } 3765 import ietf-te-types { 3766 prefix "te-types"; 3767 reference 3768 "I-D.ietf-teas-yang-te-types: Traffic Engineering Common YANG 3769 Types"; 3770 } 3772 import ietf-te-packet-types { 3773 prefix "te-packet-types"; 3774 reference 3775 "I-D.ietf-teas-yang-te-types: Traffic Engineering Common YANG 3776 Types"; 3777 } 3779 organization 3780 "Traffic Engineering Architecture and Signaling (TEAS) 3781 Working Group"; 3783 contact 3784 "WG Web: 3785 WG List: 3787 Editor: Xufeng Liu 3788 3790 Editor: Igor Bryskin 3791 3793 Editor: Vishnu Pavan Beeram 3794 3796 Editor: Tarek Saad 3797 3799 Editor: Himanshu Shah 3800 3802 Editor: Oscar Gonzalez De Dios 3803 "; 3805 description 3806 "YANG data model for representing operational state information 3807 of PSC (Packet Switching) TE Topologies, when NMDA is not 3808 supported. 3810 Copyright (c) 2018 IETF Trust and the persons identified as 3811 authors of the code. All rights reserved. 3813 Redistribution and use in source and binary forms, with or 3814 without modification, is permitted pursuant to, and subject to 3815 the license terms contained in, the Simplified BSD License set 3816 forth in Section 4.c of the IETF Trust's Legal Provisions 3817 Relating to IETF Documents 3818 (http://trustee.ietf.org/license-info). 3820 This version of this YANG module is part of RFC XXXX; see the 3821 RFC itself for full legal notices."; 3823 revision 2020-07-03 { 3824 description 3825 "Initial revision"; 3826 reference 3827 "RFC XXXX: YANG Data Model for Layer 3 TE Topologies"; 3828 } 3830 /* 3831 * Augmentations 3832 */ 3833 /* Augmentations to network-types */ 3834 augment "/nw-s:networks/nw-s:network/nw-s:network-types/" 3835 + "tet-s:te-topology" { 3836 description 3837 "Defines the packet TE topology type."; 3838 container packet { 3839 presence "Indicates packet TE topology."; 3840 description 3841 "Its presence identifies the packet TE topology type."; 3842 } 3843 } 3845 /* Augmentations to connectivity-matrix */ 3846 augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/" 3847 + "tet-s:te-node-attributes/tet-s:connectivity-matrices" { 3848 when "../../../../nw-s:network-types/tet-s:te-topology/" 3849 + "tet-pkt-s:packet" { 3850 description 3851 "Augment only for packet TE topology"; 3852 } 3853 description 3854 "Parameters for PSC (Packet Switching) TE topology."; 3855 uses te-packet-types:performance-metrics-attributes-packet { 3856 if-feature tet-pkt:te-performance-metric; 3857 } 3858 uses 3859 te-packet-types:performance-metrics-throttle-container-packet { 3860 if-feature tet-pkt:te-performance-metric; 3861 } 3862 } 3863 augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/" 3864 + "tet-s:te-node-attributes/tet-s:connectivity-matrices/" 3865 + "tet-s:connectivity-matrix" { 3866 when "../../../../../nw-s:network-types/tet-s:te-topology/" 3867 + "tet-pkt-s:packet" { 3868 description 3869 "Augment only for packet TE topology"; 3870 } 3871 description 3872 "Parameters for PSC TE topology."; 3873 uses te-packet-types:performance-metrics-attributes-packet { 3874 if-feature tet-pkt:te-performance-metric; 3875 } 3876 uses 3877 te-packet-types:performance-metrics-throttle-container-packet { 3878 if-feature tet-pkt:te-performance-metric; 3879 } 3880 } 3882 augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/" 3883 + "tet-s:information-source-entry/" 3884 + "tet-s:connectivity-matrices" { 3885 when "../../../../nw-s:network-types/tet-s:te-topology/" 3886 + "tet-pkt-s:packet" { 3887 description 3888 "Augment only for packet TE topology"; 3889 } 3890 description 3891 "Parameters for PSC TE topology."; 3892 uses te-packet-types:performance-metrics-attributes-packet { 3893 if-feature tet-pkt:te-performance-metric; 3894 } 3895 uses 3896 te-packet-types:performance-metrics-throttle-container-packet { 3897 if-feature tet-pkt:te-performance-metric; 3898 } 3899 } 3901 augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/" 3902 + "tet-s:information-source-entry/" 3903 + "tet-s:connectivity-matrices/" 3904 + "tet-s:connectivity-matrix" { 3905 when "../../../../../nw-s:network-types/tet-s:te-topology/" 3906 + "tet-pkt-s:packet" { 3907 description 3908 "Augment only for packet TE topology"; 3909 } 3910 description 3911 "Parameters for PSC TE topology."; 3912 uses te-packet-types:performance-metrics-attributes-packet { 3913 if-feature tet-pkt:te-performance-metric; 3914 } 3915 uses 3916 te-packet-types:performance-metrics-throttle-container-packet { 3917 if-feature tet-pkt:te-performance-metric; 3918 } 3919 } 3921 /* Augmentations to tunnel-termination-point */ 3922 augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/" 3923 + "tet-s:tunnel-termination-point/" 3924 + "tet-s:local-link-connectivities" { 3925 when "../../../../nw-s:network-types/tet-s:te-topology/" 3926 + "tet-pkt-s:packet" { 3927 description 3928 "Augment only for packet TE topology"; 3929 } 3930 description 3931 "Parameters for PSC TE topology."; 3932 uses te-packet-types:performance-metrics-attributes-packet { 3933 if-feature tet-pkt:te-performance-metric; 3934 } 3935 uses 3936 te-packet-types:performance-metrics-throttle-container-packet { 3937 if-feature tet-pkt:te-performance-metric; 3938 } 3939 } 3941 augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/" 3942 + "tet-s:tunnel-termination-point/" 3943 + "tet-s:local-link-connectivities/" 3944 + "tet-s:local-link-connectivity" { 3945 when "../../../../../nw-s:network-types/tet-s:te-topology/" 3946 + "tet-pkt-s:packet" { 3947 description 3948 "Augment only for packet TE topology"; 3949 } 3950 description 3951 "Parameters for PSC TE topology."; 3952 uses te-packet-types:performance-metrics-attributes-packet { 3953 if-feature tet-pkt:te-performance-metric; 3954 } 3955 uses 3956 te-packet-types:performance-metrics-throttle-container-packet { 3957 if-feature tet-pkt:te-performance-metric; 3958 } 3960 } 3962 /* Augmentations to te-link-attributes */ 3963 augment "/nw-s:networks/tet-s:te/tet-s:templates/" 3964 + "tet-s:link-template/tet-s:te-link-attributes" { 3965 when "tet-s:interface-switching-capability " 3966 + "[tet-s:switching-capability = 'te-types:switching-psc1']" { 3967 description 3968 "Valid only for PSC"; 3969 } 3970 description 3971 "Parameters for PSC TE topology."; 3972 uses te-packet-types:performance-metrics-attributes-packet { 3973 if-feature tet-pkt:te-performance-metric; 3974 } 3975 uses 3976 te-packet-types:performance-metrics-throttle-container-packet { 3977 if-feature tet-pkt:te-performance-metric; 3978 } 3979 } 3981 augment "/nw-s:networks/nw-s:network/nt-s:link/tet-s:te/" 3982 + "tet-s:te-link-attributes" { 3983 when "(../../../nw-s:network-types/tet-s:te-topology/" 3984 + "tet-pkt-s:packet) and " 3985 + "(tet-s:interface-switching-capability " 3986 + "[tet-s:switching-capability = 'te-types:switching-psc1'])" { 3987 description "Valid only for PSC"; 3988 } 3989 description 3990 "Parameters for PSC TE topology."; 3991 uses te-packet-types:performance-metrics-attributes-packet { 3992 if-feature tet-pkt:te-performance-metric; 3993 } 3994 uses 3995 te-packet-types:performance-metrics-throttle-container-packet { 3996 if-feature tet-pkt:te-performance-metric; 3997 } 3998 } 4000 augment "/nw-s:networks/nw-s:network/nt-s:link/tet-s:te/" 4001 + "tet-s:information-source-entry" { 4002 when "(../../../nw-s:network-types/tet-s:te-topology/" 4003 + "tet-pkt-s:packet) and " 4004 + "(tet-s:interface-switching-capability " 4005 + "[tet-s:switching-capability = 'te-types:switching-psc1'])" { 4006 description "Valid only for PSC"; 4007 } 4008 description 4009 "Parameters for PSC TE topology."; 4010 uses te-packet-types:performance-metrics-attributes-packet { 4011 if-feature tet-pkt:te-performance-metric; 4012 } 4013 uses 4014 te-packet-types:performance-metrics-throttle-container-packet { 4015 if-feature tet-pkt:te-performance-metric; 4016 } 4017 } 4019 /* Augmentations to interface-switching-capability */ 4020 augment "/nw-s:networks/tet-s:te/tet-s:templates/" 4021 + "tet-s:link-template/tet-s:te-link-attributes/" 4022 + "tet-s:interface-switching-capability" { 4023 when "tet-s:switching-capability = 'te-types:switching-psc1' " { 4024 description "Valid only for PSC"; 4025 } 4026 description 4027 "Parameters for PSC TE topology."; 4028 uses tet-pkt:packet-switch-capable-container; 4029 } 4031 augment "/nw-s:networks/nw-s:network/nt-s:link/tet-s:te/" 4032 + "tet-s:te-link-attributes/" 4033 + "tet-s:interface-switching-capability" { 4034 when "(../../../../nw-s:network-types/tet-s:te-topology/" 4035 + "tet-pkt-s:packet) and " 4036 + "(tet-s:switching-capability = 'te-types:switching-psc1')" { 4037 description "Valid only for PSC"; 4038 } 4039 description 4040 "Parameters for PSC TE topology."; 4041 uses tet-pkt:packet-switch-capable-container; 4042 } 4044 augment "/nw-s:networks/nw-s:network/nt-s:link/tet-s:te/" 4045 + "tet-s:information-source-entry/" 4046 + "tet-s:interface-switching-capability" { 4047 when "(../../../../nw-s:network-types/tet-s:te-topology/" 4048 + "tet-pkt-s:packet) and " 4049 + "(tet-s:switching-capability = 'te-types:switching-psc1')" { 4050 description 4051 "Valid only for PSC"; 4052 } 4053 description 4054 "Parameters for PSC TE topology."; 4055 uses tet-pkt:packet-switch-capable-container; 4057 } 4058 } 4059 4061 Appendix B. Data Tree Example 4063 This section contains an example of an instance data tree in the JSON 4064 encoding [RFC7951]. The example instantiates "ietf-l3-te-topology" 4065 for the topology that is depicted in the following diagram. 4067 +------------+ +------------+ 4068 | D1 | | D2 | 4069 /-\ /-\ (TE) /-\ /-\ 4070 | | 1-0-1 | |---------------->| | 2-1-1 | | 4071 | | 1-2-1 | |<----------------| | 2-0-1 | | 4072 \-/ 1-3-1 \-/ (TE) \-/ 2-3-1 \-/ 4073 | /----\ | | /----\ | 4074 +---| |---+ +---| |---+ 4075 \----/ \----/ 4076 A | A | 4077 (TE)| |(TE) (Non-TE)| |(Non-TE) 4078 | | | | 4079 | | +------------+ | | 4080 | | | D3 | | | 4081 | | /-\ /-\ | | 4082 | +----->| | 3-1-1 | |-------+ | 4083 +---------| | 3-2-1 | |<---------+ 4084 \-/ \-/ 4085 | | 4086 +------------+ 4088 The corresponding instance data tree is depicted below. Note that 4089 some lines have been wrapped to adhere to the 72-character line 4090 limitation of RFCs. 4092 { 4093 "ietf-network:networks": { 4094 "network": [ 4095 { 4096 "network-id":"example-topo-te", 4097 "network-types": { 4098 "ietf-te-topology:te-topology": { 4099 } 4100 }, 4101 "ietf-te-topology:te-topology-identifier": { 4102 "provider-id":200, 4103 "client-id":300, 4104 "topology-id":"example-topo-te" 4105 }, 4106 "ietf-te-topology:te": { 4107 }, 4108 "node": [ 4109 { 4110 "node-id":"D1", 4111 "ietf-te-topology:te-node-id":"2.0.1.1", 4112 "ietf-te-topology:te": { 4113 "te-node-attributes": { 4114 } 4115 }, 4116 "ietf-network-topology:termination-point": [ 4117 { 4118 "tp-id":"1-2-1", 4119 "ietf-te-topology:te-tp-id":10201, 4120 "ietf-te-topology:te": { 4121 "interface-switching-capability": [ 4122 { 4123 "switching-capability": 4124 "ietf-te-types:switching-psc1", 4125 "encoding": 4126 "ietf-te-types:lsp-encoding-ethernet" 4127 } 4128 ] 4129 } 4130 }, 4131 { 4132 "tp-id": "1-3-1", 4133 "ietf-te-topology:te-tp-id":10301, 4134 "ietf-te-topology:te": { 4135 "interface-switching-capability": [ 4136 { 4137 "switching-capability": 4138 "ietf-te-types:switching-psc1", 4139 "encoding": 4140 "ietf-te-types:lsp-encoding-ethernet" 4141 } 4142 ] 4143 } 4144 } 4145 ] 4146 }, 4147 { 4148 "node-id":"D2", 4149 "ietf-te-topology:te-node-id":"2.0.2.1", 4150 "ietf-te-topology:te": { 4151 "te-node-attributes": { 4152 } 4153 }, 4154 "ietf-network-topology:termination-point": [ 4155 { 4156 "tp-id":"2-1-1", 4157 "ietf-te-topology:te-tp-id":20101, 4158 "ietf-te-topology:te": { 4159 "interface-switching-capability": [ 4160 { 4161 "switching-capability": 4162 "ietf-te-types:switching-psc1", 4163 "encoding": 4164 "ietf-te-types:lsp-encoding-ethernet" 4165 } 4166 ] 4167 } 4168 } 4169 ] 4170 }, 4171 { 4172 "node-id":"D3", 4173 "ietf-te-topology:te-node-id":"2.0.3.1", 4174 "ietf-te-topology:te": { 4175 "te-node-attributes": { 4176 } 4177 }, 4178 "ietf-network-topology:termination-point": [ 4179 { 4180 "tp-id":"3-1-1", 4181 "ietf-te-topology:te-tp-id":30101, 4182 "ietf-te-topology:te": { 4183 "interface-switching-capability": [ 4184 { 4185 "switching-capability": 4186 "ietf-te-types:switching-psc1", 4187 "encoding": 4188 "ietf-te-types:lsp-encoding-ethernet" 4189 } 4190 ] 4191 } 4192 } 4193 ] 4194 } 4195 ], 4196 "ietf-network-topology:link": [ 4197 { 4198 "link-id":"D1,1-2-1,D2,2-1-1", 4199 "source": { 4200 "source-node":"D1", 4201 "source-tp":"1-2-1" 4202 }, 4203 "destination": { 4204 "dest-node":"D2", 4205 "dest-tp":"2-1-1" 4206 }, 4207 "ietf-te-topology:te": { 4208 "te-link-attributes": { 4209 "interface-switching-capability": [ 4210 { 4211 "switching-capability": 4212 "ietf-te-types:switching-psc1", 4213 "encoding":"ietf-te-types:lsp-encoding-ethernet" 4214 } 4215 ], 4216 "max-link-bandwidth": { 4217 "te-bandwidth": { 4218 "generic":"0x1p+18" 4219 } 4220 }, 4221 "te-default-metric":100 4222 } 4223 } 4224 }, 4225 { 4226 "link-id":"D2,2-1-1,D1,1-2-1", 4227 "source": { 4228 "source-node":"D2", 4229 "source-tp":"2-1-1" 4230 }, 4231 "destination": { 4232 "dest-node":"D1", 4233 "dest-tp":"1-2-1" 4234 }, 4235 "ietf-te-topology:te": { 4236 "te-link-attributes": { 4237 "interface-switching-capability": [ 4238 { 4239 "switching-capability": 4240 "ietf-te-types:switching-psc1", 4241 "encoding":"ietf-te-types:lsp-encoding-ethernet" 4242 } 4243 ], 4244 "max-link-bandwidth": { 4245 "te-bandwidth": { 4246 "generic":"0x1p+18" 4247 } 4248 }, 4249 "te-default-metric":100 4250 } 4251 } 4252 }, 4253 { 4254 "link-id":"D1,1-3-1,D3,3-1-1", 4255 "source": { 4256 "source-node":"D1", 4257 "source-tp":"1-3-1" 4258 }, 4259 "destination": { 4260 "dest-node":"D3", 4261 "dest-tp":"3-1-1" 4262 }, 4263 "ietf-te-topology:te": { 4264 "te-link-attributes": { 4265 "interface-switching-capability": [ 4266 { 4267 "switching-capability": 4268 "ietf-te-types:switching-psc1", 4269 "encoding":"ietf-te-types:lsp-encoding-ethernet" 4270 } 4271 ], 4272 "max-link-bandwidth": { 4273 "te-bandwidth": { 4274 "generic":"0x1p+18" 4275 } 4276 }, 4277 "te-default-metric":100 4278 } 4279 } 4280 }, 4281 { 4282 "link-id":"D3,3-1-1,D1,1-3-1", 4283 "source": { 4284 "source-node":"D3", 4285 "source-tp":"3-1-1" 4286 }, 4287 "destination": { 4288 "dest-node":"D1", 4289 "dest-tp":"1-3-1" 4290 }, 4291 "ietf-te-topology:te": { 4292 "te-link-attributes": { 4293 "interface-switching-capability": [ 4294 { 4295 "switching-capability": 4296 "ietf-te-types:switching-psc1", 4297 "encoding":"ietf-te-types:lsp-encoding-ethernet" 4298 } 4299 ], 4300 "max-link-bandwidth": { 4301 "te-bandwidth": { 4302 "generic":"0x1p+18" 4303 } 4304 }, 4305 "te-default-metric":100 4306 } 4307 } 4308 } 4309 ] 4310 }, 4311 { 4312 "network-id":"example-topo-l3-te", 4313 "network-types": { 4314 "ietf-l3-unicast-topology:l3-unicast-topology": { 4315 "ietf-l3-te-topology:l3-te": { 4316 } 4317 } 4318 }, 4319 "ietf-l3-unicast-topology:l3-topology-attributes": { 4320 "ietf-l3-te-topology:l3-te-topology-attributes": { 4321 "network-ref":"example-topo-te" 4322 } 4323 }, 4324 "node": [ 4325 { 4326 "node-id":"D1", 4327 "ietf-l3-unicast-topology:l3-node-attributes": { 4328 "router-id": [ 4329 "203.0.113.1" 4330 ], 4331 "prefix": [ 4332 { 4333 "prefix":"203.0.113.1/32" 4334 } 4335 ], 4336 "ietf-l3-te-topology:l3-te-node-attributes": { 4337 "node-ref":"D1", 4338 "network-ref":"example-topo-te" 4339 } 4340 }, 4341 "ietf-network-topology:termination-point": [ 4342 { 4343 "tp-id":"1-0-1", 4344 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 4345 "unnumbered-id":101 4346 } 4347 }, 4348 { 4349 "tp-id":"1-2-1", 4350 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 4351 "unnumbered-id":121, 4352 "ietf-l3-te-topology:l3-te-tp-attributes": { 4353 "network-ref":"example-topo-te", 4354 "tp-ref":"1-2-1" 4355 } 4356 } 4357 }, 4358 { 4359 "tp-id":"1-3-1", 4360 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 4361 "unnumbered-id":131, 4362 "ietf-l3-te-topology:l3-te-tp-attributes": { 4363 "network-ref":"example-topo-te", 4364 "tp-ref":"1-3-1" 4365 } 4366 } 4367 } 4368 ] 4369 }, 4370 { 4371 "node-id":"D2", 4372 "ietf-l3-unicast-topology:l3-node-attributes": { 4373 "router-id": [ 4374 "203.0.113.2" 4375 ], 4376 "prefix": [ 4377 { 4378 "prefix":"203.0.113.2/32" 4379 } 4380 ], 4381 "ietf-l3-te-topology:l3-te-node-attributes": { 4382 "node-ref":"D2", 4383 "network-ref":"example-topo-te" 4384 } 4385 }, 4386 "ietf-network-topology:termination-point": [ 4387 { 4388 "tp-id":"2-0-1", 4390 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 4391 "unnumbered-id":201 4392 } 4393 }, 4394 { 4395 "tp-id":"2-1-1", 4396 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 4397 "unnumbered-id":211, 4398 "ietf-l3-te-topology:l3-te-tp-attributes": { 4399 "tp-ref":"2-1-1", 4400 "network-ref":"example-topo-te" 4401 } 4402 } 4403 }, 4404 { 4405 "tp-id":"2-3-1", 4406 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 4407 "unnumbered-id":231 4408 } 4409 } 4410 ] 4411 }, 4412 { 4413 "node-id":"D3", 4414 "ietf-l3-unicast-topology:l3-node-attributes": { 4415 "router-id": [ 4416 "203.0.113.3" 4417 ], 4418 "prefix": [ 4419 { 4420 "prefix":"203.0.113.3/32" 4421 } 4422 ], 4423 "ietf-l3-te-topology:l3-te-node-attributes": { 4424 "node-ref":"D3", 4425 "network-ref":"example-topo-te" 4426 } 4427 }, 4428 "ietf-network-topology:termination-point": [ 4429 { 4430 "tp-id":"3-0-1", 4431 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 4432 "unnumbered-id":301 4433 } 4434 }, 4435 { 4436 "tp-id":"3-1-1", 4437 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 4438 "unnumbered-id":311, 4439 "ietf-l3-te-topology:l3-te-tp-attributes": { 4440 "tp-ref":"3-1-1", 4441 "network-ref":"example-topo-te" 4442 } 4443 } 4444 }, 4445 { 4446 "tp-id":"3-2-1", 4447 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 4448 "unnumbered-id":321 4449 } 4450 } 4451 ] 4452 } 4453 ], 4454 "ietf-network-topology:link": [ 4455 { 4456 "link-id":"D1,1-2-1,D2,2-1-1", 4457 "source": { 4458 "source-node":"D1", 4459 "source-tp":"1-2-1" 4460 }, 4461 "destination": { 4462 "dest-node":"D2", 4463 "dest-tp":"2-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-2-1,D2,2-1-1", 4469 "network-ref":"example-topo-te" 4470 } 4471 } 4472 }, 4473 { 4474 "link-id":"D2,2-1-1,D1,1-2-1", 4475 "source": { 4476 "source-node":"D2", 4477 "source-tp":"2-1-1" 4478 }, 4479 "destination": { 4480 "dest-node":"D1", 4481 "dest-tp":"1-2-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":"D2,2-1-1,D1,1-2-1", 4487 "network-ref":"example-topo-te" 4488 } 4489 } 4490 }, 4491 { 4492 "link-id":"D1,1-3-1,D3,3-1-1", 4493 "source": { 4494 "source-node":"D1", 4495 "source-tp":"1-3-1" 4496 }, 4497 "destination": { 4498 "dest-node":"D3", 4499 "dest-tp":"3-1-1" 4500 }, 4501 "ietf-l3-unicast-topology:l3-link-attributes": { 4502 "metric1":"100", 4503 "ietf-l3-te-topology:l3-te-link-attributes": { 4504 "link-ref":"D1,1-3-1,D3,3-1-1", 4505 "network-ref":"example-topo-te" 4506 } 4507 } 4508 }, 4509 { 4510 "link-id":"D3,3-1-1,D1,1-3-1", 4511 "source": { 4512 "source-node":"D3", 4513 "source-tp":"3-1-1" 4514 }, 4515 "destination": { 4516 "dest-node":"D1", 4517 "dest-tp":"1-3-1" 4518 }, 4519 "ietf-l3-unicast-topology:l3-link-attributes": { 4520 "metric1":"100", 4521 "ietf-l3-te-topology:l3-te-link-attributes": { 4522 "link-ref":"D3,3-1-1,D1,1-3-1", 4523 "network-ref":"example-topo-te" 4524 } 4525 } 4526 }, 4527 { 4528 "link-id":"D2,2-3-1,D3,3-2-1", 4529 "source": { 4530 "source-node":"D2", 4531 "source-tp":"2-3-1" 4532 }, 4533 "destination": { 4534 "dest-node":"D3", 4535 "dest-tp":"3-2-1" 4536 }, 4537 "ietf-l3-unicast-topology:l3-link-attributes": { 4538 "metric1":"100" 4539 } 4540 }, 4541 { 4542 "link-id":"D3,3-2-1,D2,2-3-1", 4543 "source": { 4544 "source-node":"D3", 4545 "source-tp":"3-2-1" 4546 }, 4547 "destination": { 4548 "dest-node":"D2", 4549 "dest-tp":"2-3-1" 4550 }, 4551 "ietf-l3-unicast-topology:l3-link-attributes": { 4552 "metric1":"100" 4553 } 4554 } 4555 ] 4556 } 4557 ] 4558 } 4559 } 4561 Authors' Addresses 4563 Xufeng Liu 4564 Volta Networks 4566 EMail: xufeng.liu.ietf@gmail.com 4568 Igor Bryskin 4569 Individual 4571 EMail: i_bryskin@yahoo.com 4573 Vishnu Pavan Beeram 4574 Juniper Networks 4576 EMail: vbeeram@juniper.net 4577 Tarek Saad 4578 Juniper Networks 4580 EMail: tsaad@juniper.net 4582 Himanshu Shah 4583 Ciena 4585 EMail: hshah@ciena.com 4587 Oscar Gonzalez de Dios 4588 Telefonica 4590 EMail: oscar.gonzalezdedios@telefonica.com