idnits 2.17.1 draft-ietf-teas-yang-l3-te-topo-05.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 8, 2019) is 1754 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) == Outdated reference: A later version (-13) exists of draft-ietf-teas-yang-te-types-09 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). 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 Intended status: Standards Track I. Bryskin 5 Expires: January 9, 2020 Futurewei 6 V. Beeram 7 T. Saad 8 Juniper Networks 9 H. Shah 10 Ciena 11 O. Gonzalez de Dios 12 Telefonica 13 July 8, 2019 15 YANG Data Model for Layer 3 TE Topologies 16 draft-ietf-teas-yang-l3-te-topo-05 18 Abstract 20 This document defines a YANG data model for layer 3 traffic 21 engineering topologies. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at https://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on January 9, 2020. 40 Copyright Notice 42 Copyright (c) 2019 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 . . . . . . . . . . . . . . . . . . . . . . . . 2 58 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 59 1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3 60 2. Modeling Considerations for L3 TE Topologies . . . . . . . . 3 61 2.1. Relationship Between Layer 3 Topology and TE topology . . 3 62 2.2. Relationship Modeling . . . . . . . . . . . . . . . . . . 4 63 2.2.1. Topology Referencing . . . . . . . . . . . . . . . . 4 64 2.2.2. Node Referencing . . . . . . . . . . . . . . . . . . 4 65 2.2.3. Link Termination Point Referencing . . . . . . . . . 4 66 2.2.4. Link Referencing . . . . . . . . . . . . . . . . . . 5 67 2.3. Topology Type Modeling . . . . . . . . . . . . . . . . . 5 68 3. Packet Switching Technology Extensions . . . . . . . . . . . 5 69 3.1. Technology Specific Link Attributes . . . . . . . . . . . 5 70 3.2. Performance Metric . . . . . . . . . . . . . . . . . . . 6 71 4. Complete Model Tree Structure . . . . . . . . . . . . . . . . 7 72 4.1. Layer 3 TE Topology Module . . . . . . . . . . . . . . . 7 73 4.2. Packet Switching TE Topology Module . . . . . . . . . . . 7 74 5. YANG Modules . . . . . . . . . . . . . . . . . . . . . . . . 27 75 5.1. Layer 3 TE Topology Module . . . . . . . . . . . . . . . 27 76 5.2. Packet Switching TE Topology Module . . . . . . . . . . . 32 77 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 39 78 7. Security Considerations . . . . . . . . . . . . . . . . . . . 41 79 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 43 80 8.1. Normative References . . . . . . . . . . . . . . . . . . 43 81 8.2. Informative References . . . . . . . . . . . . . . . . . 45 82 Appendix A. Companion YANG Model for Non-NMDA Compliant 83 Implementations . . . . . . . . . . . . . . . . . . 46 84 A.1. Layer 3 TE Topology State Module . . . . . . . . . . . . 46 85 A.2. Packet Switching TE Topology State Module . . . . . . . . 49 86 Appendix B. Data Tree Example . . . . . . . . . . . . . . . . . 55 87 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 65 89 1. Introduction 91 This document defines a YANG [RFC7950] data model for describing the 92 relationship between a layer 3 network topology [RFC8346] and a 93 Traffic Engineering (TE) topology [I-D.ietf-teas-yang-te-topo]. 95 When traffic engineering is enabled on a layer 3 network topology, 96 there will be a corresponding TE topology. The TE topology may or 97 may not be congruent to the layer 3 network topology. When such a 98 congruent TE topology exists, there will be a one-to-one association 99 between the one modeling element in the layer 3 topology to another 100 element in the TE topology. When such a congruent TE topology does 101 not exist, the association will not be one-to-one. This YANG data 102 model allows both cases. 104 1.1. Terminology 106 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 107 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 108 "OPTIONAL" in this document are to be interpreted as described in BCP 109 14, [RFC2119] [RFC8174] when, and only when, they appear in all 110 capitals, as shown here. 112 The following terms are defined in [RFC7950] and are not redefined 113 here: 115 o augment 117 o data model 119 o data node 121 1.2. Tree Diagrams 123 Tree diagrams used in this document follow the notation defined in 124 [RFC8340]. 126 2. Modeling Considerations for L3 TE Topologies 128 The YANG modulues ietf-l3-te-topology and ietf-l3-te-topology-state 129 model configuration and operational state of layer 3 TE network 130 topologies. These two modules augment ietf-l3-te-topology and ietf- 131 l3-te-topology-state respectively, so a layer 3 TE network topology 132 is a layer 3 network topoology with addtional TE capability enabled. 134 2.1. Relationship Between Layer 3 Topology and TE topology 136 In general, layer 3 network topology model and TE topology model can 137 be used independently. When traffic engineering is enabled on a 138 layer 3 network topology, there will be associations between objects 139 in layer 3 network topologies and objects in TE topologies. The 140 properties of these relations are: 142 o The associations are between objects of the same class, i.e. node 143 to node or link to link. 145 o The multiplicity of such an association is: 0..1 to 0..1. An 146 object in a layer 3 network may have zero or one associated object 147 in the corresponding TE network. 149 2.2. Relationship Modeling 151 YANG data type leafref is used to model the association relationship 152 between a layer 3 network topology and a TE topology. YANG must 153 statements are used to enforce that the referenced objects are in the 154 topologies of proper type. 156 2.2.1. Topology Referencing 158 When TE is enabled on a layer 3 network topology, if the TE topology 159 is not congruent to the layer 3 network topology, the layer 3 network 160 topology will have a reference to the corresponding TE topology. 161 Such a reference is modeled as follows: 163 augment /nw:networks/nw:network/l3t:l3-topology-attributes: 164 +--rw l3-te-topology-attributes 165 +--rw network-ref? -> /nw:networks/network/network-id 167 If the TE topology is congruent to the layer 3 network topology, the 168 above reference can still be used to specified TE paramenters defined 169 in the TE topology model. 171 2.2.2. Node Referencing 173 When TE is enabled on a layer 3 network topology, if the TE topology 174 is not congruent to the layer 3 network topology, a layer 3 network 175 node may have a reference to the corresponding TE node. Such a 176 reference is modeled as follows: 178 augment /nw:networks/nw:network/nw:node/l3t:l3-node-attributes: 179 +--rw l3-te-node-attributes 180 +--rw node-ref? leafref 181 +--rw network-ref? -> /nw:networks/network/network-id 183 2.2.3. Link Termination Point Referencing 185 When TE is enabled on a layer 3 network topology, if the TE topology 186 is not congruent to the layer 3 network topology, a layer 3 link 187 termination point may have a reference to the corresponding TE link 188 termination point. Such a reference is modeled as follows: 190 augment /nw:networks/nw:network/nw:node/nt:termination-point 191 /l3t:l3-termination-point-attributes: 192 +--rw l3-te-tp-attributes 193 +--rw tp-ref? leafref 194 +--rw node-ref? leafref 195 +--rw network-ref? -> /nw:networks/network/network-id 197 2.2.4. Link Referencing 199 When TE is enabled on a layer 3 network topology, if the TE topology 200 is not congruent to the layer 3 network topology, a layer 3 link may 201 have a reference to the corresponding TE link. Such a reference is 202 modeled as follows: 204 augment /nw:networks/nw:network/nt:link/l3t:l3-link-attributes: 205 +--rw l3-te-link-attributes 206 +--rw link-ref? leafref 207 +--rw network-ref? -> /nw:networks/network/network-id 209 2.3. Topology Type Modeling 211 A new topology type is defined in this document, to indicate a 212 topology that is a layer 3 topology with TE enabled. 214 augment /nw:networks/nw:network/nw:network-types 215 /l3t:l3-unicast-topology: 216 +--rw l3-te! 218 3. Packet Switching Technology Extensions 220 The technology agnostic TE Topology model is defined in 221 [I-D.ietf-teas-yang-te-topo], which is extended by this document to 222 cover the Packet Switch Capable (PSC) technology [RFC3471] [RFC7074]. 224 3.1. Technology Specific Link Attributes 226 The technology agnostic TE Topology model is augmented with packet 227 switching specific link attributes: 229 augment /nw:networks/tet:te/tet:templates/tet:link-template 230 /tet:te-link-attributes 231 /tet:interface-switching-capability: 232 +--rw packet-switch-capable 233 +--rw minimum-lsp-bandwidth? rt-types:bandwidth-ieee-float32 234 +--rw interface-mtu? uint16 235 augment /nw:networks/nw:network/nt:link/tet:te 236 /tet:te-link-attributes 237 /tet:interface-switching-capability: 238 +--rw packet-switch-capable 239 +--rw minimum-lsp-bandwidth? rt-types:bandwidth-ieee-float32 240 +--rw interface-mtu? uint16 241 augment /nw:networks/nw:network/nt:link/tet:te 242 /tet:information-source-entry 243 /tet:interface-switching-capability: 244 +--ro packet-switch-capable 245 +--ro minimum-lsp-bandwidth? rt-types:bandwidth-ieee-float32 246 +--ro interface-mtu? uint16 248 3.2. Performance Metric 250 [RFC7471], [RFC8570] and [RFC7823] specify TE performance metric 251 parameters and their usage. The packet switching augmentations 252 specified in this moducment support such a capability, which can be 253 conditional enabled by a YANG feature "te-performance-metric". 255 augment /nw:networks/nw:network/nw:node/tet:te 256 /tet:te-node-attributes/tet:connectivity-matrices: 257 +--rw performance-metric 258 +--rw measurement 259 | ...... 260 +--rw normality 261 | ...... 262 +--rw throttle 263 ...... 265 Such an augmentation has been applied to: 267 o Connectivity matrices container 269 o Connectivity matrix entry 271 o Local ink connectivities container 273 o Local ink connectivity entry 275 o TE link attributes container in a TE link template 276 o TE link attributes container in a TE link 278 o Information source entry in a TE link 280 4. Complete Model Tree Structure 282 4.1. Layer 3 TE Topology Module 284 The model tree structure of the layer 3 TE topology module is as 285 shown below: 287 module: ietf-l3-te-topology 288 augment /nw:networks/nw:network/nw:network-types 289 /l3t:l3-unicast-topology: 290 +--rw l3-te! 291 augment /nw:networks/nw:network/l3t:l3-topology-attributes: 292 +--rw l3-te-topology-attributes 293 +--rw network-ref? -> /nw:networks/network/network-id 294 augment /nw:networks/nw:network/nw:node/l3t:l3-node-attributes: 295 +--rw l3-te-node-attributes 296 +--rw node-ref? leafref 297 +--rw network-ref? -> /nw:networks/network/network-id 298 augment /nw:networks/nw:network/nw:node/nt:termination-point 299 /l3t:l3-termination-point-attributes: 300 +--rw l3-te-tp-attributes 301 +--rw tp-ref? leafref 302 +--rw node-ref? leafref 303 +--rw network-ref? -> /nw:networks/network/network-id 304 augment /nw:networks/nw:network/nt:link/l3t:l3-link-attributes: 305 +--rw l3-te-link-attributes 306 +--rw link-ref? leafref 307 +--rw network-ref? -> /nw:networks/network/network-id 309 4.2. Packet Switching TE Topology Module 311 This is an augmentation to base TE topology model. 313 module: ietf-te-topology-packet 314 augment /nw:networks/nw:network/nw:node/tet:te 315 /tet:te-node-attributes/tet:connectivity-matrices: 316 +--ro performance-metrics-one-way 317 | +--ro one-way-delay? uint32 318 | +--ro one-way-delay-normality? 319 | | te-types:performance-metrics-normality 320 | +--ro one-way-residual-bandwidth? 321 | | rt-types:bandwidth-ieee-float32 322 | +--ro one-way-residual-bandwidth-normality? 323 | | te-types:performance-metrics-normality 324 | +--ro one-way-available-bandwidth? 325 | | rt-types:bandwidth-ieee-float32 326 | +--ro one-way-available-bandwidth-normality? 327 | | te-types:performance-metrics-normality 328 | +--ro one-way-utilized-bandwidth? 329 | | rt-types:bandwidth-ieee-float32 330 | +--ro one-way-utilized-bandwidth-normality? 331 | | te-types:performance-metrics-normality 332 | +--ro one-way-min-delay? uint32 333 | +--ro one-way-min-delay-normality? 334 | | te-types:performance-metrics-normality 335 | +--ro one-way-max-delay? uint32 336 | +--ro one-way-max-delay-normality? 337 | | te-types:performance-metrics-normality 338 | +--ro one-way-delay-variation? uint32 339 | +--ro one-way-delay-variation-normality? 340 | | te-types:performance-metrics-normality 341 | +--ro one-way-packet-loss? decimal64 342 | +--ro one-way-packet-loss-normality? 343 | te-types:performance-metrics-normality 344 +--ro performance-metrics-two-way 345 | +--ro two-way-delay? uint32 346 | +--ro two-way-delay-normality? 347 | | te-types:performance-metrics-normality 348 | +--ro two-way-min-delay? uint32 349 | +--ro two-way-min-delay-normality? 350 | | te-types:performance-metrics-normality 351 | +--ro two-way-max-delay? uint32 352 | +--ro two-way-max-delay-normality? 353 | | te-types:performance-metrics-normality 354 | +--ro two-way-delay-variation? uint32 355 | +--ro two-way-delay-variation-normality? 356 | | te-types:performance-metrics-normality 357 | +--ro two-way-packet-loss? decimal64 358 | +--ro two-way-packet-loss-normality? 359 | te-types:performance-metrics-normality 360 +--rw throttle 361 +--rw one-way-delay-offset? uint32 362 +--rw measure-interval? uint32 363 +--rw advertisement-interval? uint32 364 +--rw suppression-interval? uint32 365 +--rw threshold-out 366 | +--rw one-way-delay? uint32 367 | +--rw one-way-residual-bandwidth? 368 | | rt-types:bandwidth-ieee-float32 369 | +--rw one-way-available-bandwidth? 370 | | rt-types:bandwidth-ieee-float32 371 | +--rw one-way-utilized-bandwidth? 372 | | rt-types:bandwidth-ieee-float32 373 | +--rw two-way-delay? uint32 374 | +--rw one-way-min-delay? uint32 375 | +--rw one-way-max-delay? uint32 376 | +--rw one-way-delay-variation? uint32 377 | +--rw one-way-packet-loss? decimal64 378 | +--rw two-way-min-delay? uint32 379 | +--rw two-way-max-delay? uint32 380 | +--rw two-way-delay-variation? uint32 381 | +--rw two-way-packet-loss? decimal64 382 +--rw threshold-in 383 | +--rw one-way-delay? uint32 384 | +--rw one-way-residual-bandwidth? 385 | | rt-types:bandwidth-ieee-float32 386 | +--rw one-way-available-bandwidth? 387 | | rt-types:bandwidth-ieee-float32 388 | +--rw one-way-utilized-bandwidth? 389 | | rt-types:bandwidth-ieee-float32 390 | +--rw two-way-delay? uint32 391 | +--rw one-way-min-delay? uint32 392 | +--rw one-way-max-delay? uint32 393 | +--rw one-way-delay-variation? uint32 394 | +--rw one-way-packet-loss? decimal64 395 | +--rw two-way-min-delay? uint32 396 | +--rw two-way-max-delay? uint32 397 | +--rw two-way-delay-variation? uint32 398 | +--rw two-way-packet-loss? decimal64 399 +--rw threshold-accelerated-advertisement 400 +--rw one-way-delay? uint32 401 +--rw one-way-residual-bandwidth? 402 | rt-types:bandwidth-ieee-float32 403 +--rw one-way-available-bandwidth? 404 | rt-types:bandwidth-ieee-float32 405 +--rw one-way-utilized-bandwidth? 406 | rt-types:bandwidth-ieee-float32 407 +--rw two-way-delay? uint32 408 +--rw one-way-min-delay? uint32 409 +--rw one-way-max-delay? uint32 410 +--rw one-way-delay-variation? uint32 411 +--rw one-way-packet-loss? decimal64 412 +--rw two-way-min-delay? uint32 413 +--rw two-way-max-delay? uint32 414 +--rw two-way-delay-variation? uint32 415 +--rw two-way-packet-loss? decimal64 417 augment /nw:networks/nw:network/nw:node/tet:te 418 /tet:te-node-attributes/tet:connectivity-matrices 419 /tet:connectivity-matrix: 420 +--ro performance-metrics-one-way 421 | +--ro one-way-delay? uint32 422 | +--ro one-way-delay-normality? 423 | | te-types:performance-metrics-normality 424 | +--ro one-way-residual-bandwidth? 425 | | rt-types:bandwidth-ieee-float32 426 | +--ro one-way-residual-bandwidth-normality? 427 | | te-types:performance-metrics-normality 428 | +--ro one-way-available-bandwidth? 429 | | rt-types:bandwidth-ieee-float32 430 | +--ro one-way-available-bandwidth-normality? 431 | | te-types:performance-metrics-normality 432 | +--ro one-way-utilized-bandwidth? 433 | | rt-types:bandwidth-ieee-float32 434 | +--ro one-way-utilized-bandwidth-normality? 435 | | te-types:performance-metrics-normality 436 | +--ro one-way-min-delay? uint32 437 | +--ro one-way-min-delay-normality? 438 | | te-types:performance-metrics-normality 439 | +--ro one-way-max-delay? uint32 440 | +--ro one-way-max-delay-normality? 441 | | te-types:performance-metrics-normality 442 | +--ro one-way-delay-variation? uint32 443 | +--ro one-way-delay-variation-normality? 444 | | te-types:performance-metrics-normality 445 | +--ro one-way-packet-loss? decimal64 446 | +--ro one-way-packet-loss-normality? 447 | te-types:performance-metrics-normality 448 +--ro performance-metrics-two-way 449 | +--ro two-way-delay? uint32 450 | +--ro two-way-delay-normality? 451 | | te-types:performance-metrics-normality 452 | +--ro two-way-min-delay? uint32 453 | +--ro two-way-min-delay-normality? 454 | | te-types:performance-metrics-normality 455 | +--ro two-way-max-delay? uint32 456 | +--ro two-way-max-delay-normality? 457 | | te-types:performance-metrics-normality 458 | +--ro two-way-delay-variation? uint32 459 | +--ro two-way-delay-variation-normality? 460 | | te-types:performance-metrics-normality 461 | +--ro two-way-packet-loss? decimal64 462 | +--ro two-way-packet-loss-normality? 463 | te-types:performance-metrics-normality 464 +--rw throttle 465 +--rw one-way-delay-offset? uint32 466 +--rw measure-interval? uint32 467 +--rw advertisement-interval? uint32 468 +--rw suppression-interval? uint32 469 +--rw threshold-out 470 | +--rw one-way-delay? uint32 471 | +--rw one-way-residual-bandwidth? 472 | | rt-types:bandwidth-ieee-float32 473 | +--rw one-way-available-bandwidth? 474 | | rt-types:bandwidth-ieee-float32 475 | +--rw one-way-utilized-bandwidth? 476 | | rt-types:bandwidth-ieee-float32 477 | +--rw two-way-delay? uint32 478 | +--rw one-way-min-delay? uint32 479 | +--rw one-way-max-delay? uint32 480 | +--rw one-way-delay-variation? uint32 481 | +--rw one-way-packet-loss? decimal64 482 | +--rw two-way-min-delay? uint32 483 | +--rw two-way-max-delay? uint32 484 | +--rw two-way-delay-variation? uint32 485 | +--rw two-way-packet-loss? decimal64 486 +--rw threshold-in 487 | +--rw one-way-delay? uint32 488 | +--rw one-way-residual-bandwidth? 489 | | rt-types:bandwidth-ieee-float32 490 | +--rw one-way-available-bandwidth? 491 | | rt-types:bandwidth-ieee-float32 492 | +--rw one-way-utilized-bandwidth? 493 | | rt-types:bandwidth-ieee-float32 494 | +--rw two-way-delay? uint32 495 | +--rw one-way-min-delay? uint32 496 | +--rw one-way-max-delay? uint32 497 | +--rw one-way-delay-variation? uint32 498 | +--rw one-way-packet-loss? decimal64 499 | +--rw two-way-min-delay? uint32 500 | +--rw two-way-max-delay? uint32 501 | +--rw two-way-delay-variation? uint32 502 | +--rw two-way-packet-loss? decimal64 503 +--rw threshold-accelerated-advertisement 504 +--rw one-way-delay? uint32 505 +--rw one-way-residual-bandwidth? 506 | rt-types:bandwidth-ieee-float32 507 +--rw one-way-available-bandwidth? 508 | rt-types:bandwidth-ieee-float32 509 +--rw one-way-utilized-bandwidth? 510 | rt-types:bandwidth-ieee-float32 511 +--rw two-way-delay? uint32 512 +--rw one-way-min-delay? uint32 513 +--rw one-way-max-delay? uint32 514 +--rw one-way-delay-variation? uint32 515 +--rw one-way-packet-loss? decimal64 516 +--rw two-way-min-delay? uint32 517 +--rw two-way-max-delay? uint32 518 +--rw two-way-delay-variation? uint32 519 +--rw two-way-packet-loss? decimal64 520 augment /nw:networks/nw:network/nw:node/tet:te 521 /tet:information-source-entry/tet:connectivity-matrices: 522 +--ro performance-metrics-one-way 523 | +--ro one-way-delay? uint32 524 | +--ro one-way-delay-normality? 525 | | te-types:performance-metrics-normality 526 | +--ro one-way-residual-bandwidth? 527 | | rt-types:bandwidth-ieee-float32 528 | +--ro one-way-residual-bandwidth-normality? 529 | | te-types:performance-metrics-normality 530 | +--ro one-way-available-bandwidth? 531 | | rt-types:bandwidth-ieee-float32 532 | +--ro one-way-available-bandwidth-normality? 533 | | te-types:performance-metrics-normality 534 | +--ro one-way-utilized-bandwidth? 535 | | rt-types:bandwidth-ieee-float32 536 | +--ro one-way-utilized-bandwidth-normality? 537 | | te-types:performance-metrics-normality 538 | +--ro one-way-min-delay? uint32 539 | +--ro one-way-min-delay-normality? 540 | | te-types:performance-metrics-normality 541 | +--ro one-way-max-delay? uint32 542 | +--ro one-way-max-delay-normality? 543 | | te-types:performance-metrics-normality 544 | +--ro one-way-delay-variation? uint32 545 | +--ro one-way-delay-variation-normality? 546 | | te-types:performance-metrics-normality 547 | +--ro one-way-packet-loss? decimal64 548 | +--ro one-way-packet-loss-normality? 549 | te-types:performance-metrics-normality 550 +--ro performance-metrics-two-way 551 | +--ro two-way-delay? uint32 552 | +--ro two-way-delay-normality? 553 | | te-types:performance-metrics-normality 554 | +--ro two-way-min-delay? uint32 555 | +--ro two-way-min-delay-normality? 556 | | te-types:performance-metrics-normality 557 | +--ro two-way-max-delay? uint32 558 | +--ro two-way-max-delay-normality? 559 | | te-types:performance-metrics-normality 560 | +--ro two-way-delay-variation? uint32 561 | +--ro two-way-delay-variation-normality? 562 | | te-types:performance-metrics-normality 563 | +--ro two-way-packet-loss? decimal64 564 | +--ro two-way-packet-loss-normality? 565 | te-types:performance-metrics-normality 566 +--ro throttle 567 +--ro one-way-delay-offset? uint32 568 +--ro measure-interval? uint32 569 +--ro advertisement-interval? uint32 570 +--ro suppression-interval? uint32 571 +--ro threshold-out 572 | +--ro one-way-delay? uint32 573 | +--ro one-way-residual-bandwidth? 574 | | rt-types:bandwidth-ieee-float32 575 | +--ro one-way-available-bandwidth? 576 | | rt-types:bandwidth-ieee-float32 577 | +--ro one-way-utilized-bandwidth? 578 | | rt-types:bandwidth-ieee-float32 579 | +--ro two-way-delay? uint32 580 | +--ro one-way-min-delay? uint32 581 | +--ro one-way-max-delay? uint32 582 | +--ro one-way-delay-variation? uint32 583 | +--ro one-way-packet-loss? decimal64 584 | +--ro two-way-min-delay? uint32 585 | +--ro two-way-max-delay? uint32 586 | +--ro two-way-delay-variation? uint32 587 | +--ro two-way-packet-loss? decimal64 588 +--ro threshold-in 589 | +--ro one-way-delay? uint32 590 | +--ro one-way-residual-bandwidth? 591 | | rt-types:bandwidth-ieee-float32 592 | +--ro one-way-available-bandwidth? 593 | | rt-types:bandwidth-ieee-float32 594 | +--ro one-way-utilized-bandwidth? 595 | | rt-types:bandwidth-ieee-float32 596 | +--ro two-way-delay? uint32 597 | +--ro one-way-min-delay? uint32 598 | +--ro one-way-max-delay? uint32 599 | +--ro one-way-delay-variation? uint32 600 | +--ro one-way-packet-loss? decimal64 601 | +--ro two-way-min-delay? uint32 602 | +--ro two-way-max-delay? uint32 603 | +--ro two-way-delay-variation? uint32 604 | +--ro two-way-packet-loss? decimal64 605 +--ro threshold-accelerated-advertisement 606 +--ro one-way-delay? uint32 607 +--ro one-way-residual-bandwidth? 608 | rt-types:bandwidth-ieee-float32 609 +--ro one-way-available-bandwidth? 610 | rt-types:bandwidth-ieee-float32 611 +--ro one-way-utilized-bandwidth? 612 | rt-types:bandwidth-ieee-float32 613 +--ro two-way-delay? uint32 614 +--ro one-way-min-delay? uint32 615 +--ro one-way-max-delay? uint32 616 +--ro one-way-delay-variation? uint32 617 +--ro one-way-packet-loss? decimal64 618 +--ro two-way-min-delay? uint32 619 +--ro two-way-max-delay? uint32 620 +--ro two-way-delay-variation? uint32 621 +--ro two-way-packet-loss? decimal64 622 augment /nw:networks/nw:network/nw:node/tet:te 623 /tet:information-source-entry/tet:connectivity-matrices 624 /tet:connectivity-matrix: 625 +--ro performance-metrics-one-way 626 | +--ro one-way-delay? uint32 627 | +--ro one-way-delay-normality? 628 | | te-types:performance-metrics-normality 629 | +--ro one-way-residual-bandwidth? 630 | | rt-types:bandwidth-ieee-float32 631 | +--ro one-way-residual-bandwidth-normality? 632 | | te-types:performance-metrics-normality 633 | +--ro one-way-available-bandwidth? 634 | | rt-types:bandwidth-ieee-float32 635 | +--ro one-way-available-bandwidth-normality? 636 | | te-types:performance-metrics-normality 637 | +--ro one-way-utilized-bandwidth? 638 | | rt-types:bandwidth-ieee-float32 639 | +--ro one-way-utilized-bandwidth-normality? 640 | | te-types:performance-metrics-normality 641 | +--ro one-way-min-delay? uint32 642 | +--ro one-way-min-delay-normality? 643 | | te-types:performance-metrics-normality 644 | +--ro one-way-max-delay? uint32 645 | +--ro one-way-max-delay-normality? 646 | | te-types:performance-metrics-normality 647 | +--ro one-way-delay-variation? uint32 648 | +--ro one-way-delay-variation-normality? 649 | | te-types:performance-metrics-normality 650 | +--ro one-way-packet-loss? decimal64 651 | +--ro one-way-packet-loss-normality? 652 | te-types:performance-metrics-normality 653 +--ro performance-metrics-two-way 654 | +--ro two-way-delay? uint32 655 | +--ro two-way-delay-normality? 656 | | te-types:performance-metrics-normality 657 | +--ro two-way-min-delay? uint32 658 | +--ro two-way-min-delay-normality? 659 | | te-types:performance-metrics-normality 660 | +--ro two-way-max-delay? uint32 661 | +--ro two-way-max-delay-normality? 662 | | te-types:performance-metrics-normality 663 | +--ro two-way-delay-variation? uint32 664 | +--ro two-way-delay-variation-normality? 665 | | te-types:performance-metrics-normality 666 | +--ro two-way-packet-loss? decimal64 667 | +--ro two-way-packet-loss-normality? 668 | te-types:performance-metrics-normality 669 +--ro throttle 670 +--ro one-way-delay-offset? uint32 671 +--ro measure-interval? uint32 672 +--ro advertisement-interval? uint32 673 +--ro suppression-interval? uint32 674 +--ro threshold-out 675 | +--ro one-way-delay? uint32 676 | +--ro one-way-residual-bandwidth? 677 | | rt-types:bandwidth-ieee-float32 678 | +--ro one-way-available-bandwidth? 679 | | rt-types:bandwidth-ieee-float32 680 | +--ro one-way-utilized-bandwidth? 681 | | rt-types:bandwidth-ieee-float32 682 | +--ro two-way-delay? uint32 683 | +--ro one-way-min-delay? uint32 684 | +--ro one-way-max-delay? uint32 685 | +--ro one-way-delay-variation? uint32 686 | +--ro one-way-packet-loss? decimal64 687 | +--ro two-way-min-delay? uint32 688 | +--ro two-way-max-delay? uint32 689 | +--ro two-way-delay-variation? uint32 690 | +--ro two-way-packet-loss? decimal64 691 +--ro threshold-in 692 | +--ro one-way-delay? uint32 693 | +--ro one-way-residual-bandwidth? 694 | | rt-types:bandwidth-ieee-float32 695 | +--ro one-way-available-bandwidth? 696 | | rt-types:bandwidth-ieee-float32 697 | +--ro one-way-utilized-bandwidth? 698 | | rt-types:bandwidth-ieee-float32 699 | +--ro two-way-delay? uint32 700 | +--ro one-way-min-delay? uint32 701 | +--ro one-way-max-delay? uint32 702 | +--ro one-way-delay-variation? uint32 703 | +--ro one-way-packet-loss? decimal64 704 | +--ro two-way-min-delay? uint32 705 | +--ro two-way-max-delay? uint32 706 | +--ro two-way-delay-variation? uint32 707 | +--ro two-way-packet-loss? decimal64 708 +--ro threshold-accelerated-advertisement 709 +--ro one-way-delay? uint32 710 +--ro one-way-residual-bandwidth? 711 | rt-types:bandwidth-ieee-float32 712 +--ro one-way-available-bandwidth? 713 | rt-types:bandwidth-ieee-float32 714 +--ro one-way-utilized-bandwidth? 715 | rt-types:bandwidth-ieee-float32 716 +--ro two-way-delay? uint32 717 +--ro one-way-min-delay? uint32 718 +--ro one-way-max-delay? uint32 719 +--ro one-way-delay-variation? uint32 720 +--ro one-way-packet-loss? decimal64 721 +--ro two-way-min-delay? uint32 722 +--ro two-way-max-delay? uint32 723 +--ro two-way-delay-variation? uint32 724 +--ro two-way-packet-loss? decimal64 725 augment /nw:networks/nw:network/nw:node/tet:te 726 /tet:tunnel-termination-point 727 /tet:local-link-connectivities: 728 +--ro performance-metrics-one-way 729 | +--ro one-way-delay? uint32 730 | +--ro one-way-delay-normality? 731 | | te-types:performance-metrics-normality 732 | +--ro one-way-residual-bandwidth? 733 | | rt-types:bandwidth-ieee-float32 734 | +--ro one-way-residual-bandwidth-normality? 735 | | te-types:performance-metrics-normality 736 | +--ro one-way-available-bandwidth? 737 | | rt-types:bandwidth-ieee-float32 738 | +--ro one-way-available-bandwidth-normality? 739 | | te-types:performance-metrics-normality 740 | +--ro one-way-utilized-bandwidth? 741 | | rt-types:bandwidth-ieee-float32 742 | +--ro one-way-utilized-bandwidth-normality? 743 | | te-types:performance-metrics-normality 744 | +--ro one-way-min-delay? uint32 745 | +--ro one-way-min-delay-normality? 746 | | te-types:performance-metrics-normality 747 | +--ro one-way-max-delay? uint32 748 | +--ro one-way-max-delay-normality? 749 | | te-types:performance-metrics-normality 750 | +--ro one-way-delay-variation? uint32 751 | +--ro one-way-delay-variation-normality? 752 | | te-types:performance-metrics-normality 753 | +--ro one-way-packet-loss? decimal64 754 | +--ro one-way-packet-loss-normality? 755 | te-types:performance-metrics-normality 756 +--ro performance-metrics-two-way 757 | +--ro two-way-delay? uint32 758 | +--ro two-way-delay-normality? 759 | | te-types:performance-metrics-normality 760 | +--ro two-way-min-delay? uint32 761 | +--ro two-way-min-delay-normality? 762 | | te-types:performance-metrics-normality 763 | +--ro two-way-max-delay? uint32 764 | +--ro two-way-max-delay-normality? 765 | | te-types:performance-metrics-normality 766 | +--ro two-way-delay-variation? uint32 767 | +--ro two-way-delay-variation-normality? 768 | | te-types:performance-metrics-normality 769 | +--ro two-way-packet-loss? decimal64 770 | +--ro two-way-packet-loss-normality? 771 | te-types:performance-metrics-normality 772 +--rw throttle 773 +--rw one-way-delay-offset? uint32 774 +--rw measure-interval? uint32 775 +--rw advertisement-interval? uint32 776 +--rw suppression-interval? uint32 777 +--rw threshold-out 778 | +--rw one-way-delay? uint32 779 | +--rw one-way-residual-bandwidth? 780 | | rt-types:bandwidth-ieee-float32 781 | +--rw one-way-available-bandwidth? 782 | | rt-types:bandwidth-ieee-float32 783 | +--rw one-way-utilized-bandwidth? 784 | | rt-types:bandwidth-ieee-float32 785 | +--rw two-way-delay? uint32 786 | +--rw one-way-min-delay? uint32 787 | +--rw one-way-max-delay? uint32 788 | +--rw one-way-delay-variation? uint32 789 | +--rw one-way-packet-loss? decimal64 790 | +--rw two-way-min-delay? uint32 791 | +--rw two-way-max-delay? uint32 792 | +--rw two-way-delay-variation? uint32 793 | +--rw two-way-packet-loss? decimal64 794 +--rw threshold-in 795 | +--rw one-way-delay? uint32 796 | +--rw one-way-residual-bandwidth? 797 | | rt-types:bandwidth-ieee-float32 798 | +--rw one-way-available-bandwidth? 799 | | rt-types:bandwidth-ieee-float32 800 | +--rw one-way-utilized-bandwidth? 801 | | rt-types:bandwidth-ieee-float32 802 | +--rw two-way-delay? uint32 803 | +--rw one-way-min-delay? uint32 804 | +--rw one-way-max-delay? uint32 805 | +--rw one-way-delay-variation? uint32 806 | +--rw one-way-packet-loss? decimal64 807 | +--rw two-way-min-delay? uint32 808 | +--rw two-way-max-delay? uint32 809 | +--rw two-way-delay-variation? uint32 810 | +--rw two-way-packet-loss? decimal64 811 +--rw threshold-accelerated-advertisement 812 +--rw one-way-delay? uint32 813 +--rw one-way-residual-bandwidth? 814 | rt-types:bandwidth-ieee-float32 815 +--rw one-way-available-bandwidth? 816 | rt-types:bandwidth-ieee-float32 817 +--rw one-way-utilized-bandwidth? 818 | rt-types:bandwidth-ieee-float32 819 +--rw two-way-delay? uint32 820 +--rw one-way-min-delay? uint32 821 +--rw one-way-max-delay? uint32 822 +--rw one-way-delay-variation? uint32 823 +--rw one-way-packet-loss? decimal64 824 +--rw two-way-min-delay? uint32 825 +--rw two-way-max-delay? uint32 826 +--rw two-way-delay-variation? uint32 827 +--rw two-way-packet-loss? decimal64 828 augment /nw:networks/nw:network/nw:node/tet:te 829 /tet:tunnel-termination-point 830 /tet:local-link-connectivities 831 /tet:local-link-connectivity: 832 +--ro performance-metrics-one-way 833 | +--ro one-way-delay? uint32 834 | +--ro one-way-delay-normality? 835 | | te-types:performance-metrics-normality 836 | +--ro one-way-residual-bandwidth? 837 | | rt-types:bandwidth-ieee-float32 838 | +--ro one-way-residual-bandwidth-normality? 839 | | te-types:performance-metrics-normality 840 | +--ro one-way-available-bandwidth? 841 | | rt-types:bandwidth-ieee-float32 842 | +--ro one-way-available-bandwidth-normality? 843 | | te-types:performance-metrics-normality 844 | +--ro one-way-utilized-bandwidth? 845 | | rt-types:bandwidth-ieee-float32 846 | +--ro one-way-utilized-bandwidth-normality? 847 | | te-types:performance-metrics-normality 848 | +--ro one-way-min-delay? uint32 849 | +--ro one-way-min-delay-normality? 850 | | te-types:performance-metrics-normality 851 | +--ro one-way-max-delay? uint32 852 | +--ro one-way-max-delay-normality? 853 | | te-types:performance-metrics-normality 854 | +--ro one-way-delay-variation? uint32 855 | +--ro one-way-delay-variation-normality? 856 | | te-types:performance-metrics-normality 857 | +--ro one-way-packet-loss? decimal64 858 | +--ro one-way-packet-loss-normality? 859 | te-types:performance-metrics-normality 860 +--ro performance-metrics-two-way 861 | +--ro two-way-delay? uint32 862 | +--ro two-way-delay-normality? 863 | | te-types:performance-metrics-normality 864 | +--ro two-way-min-delay? uint32 865 | +--ro two-way-min-delay-normality? 866 | | te-types:performance-metrics-normality 867 | +--ro two-way-max-delay? uint32 868 | +--ro two-way-max-delay-normality? 869 | | te-types:performance-metrics-normality 870 | +--ro two-way-delay-variation? uint32 871 | +--ro two-way-delay-variation-normality? 872 | | te-types:performance-metrics-normality 873 | +--ro two-way-packet-loss? decimal64 874 | +--ro two-way-packet-loss-normality? 875 | te-types:performance-metrics-normality 876 +--rw throttle 877 +--rw one-way-delay-offset? uint32 878 +--rw measure-interval? uint32 879 +--rw advertisement-interval? uint32 880 +--rw suppression-interval? uint32 881 +--rw threshold-out 882 | +--rw one-way-delay? uint32 883 | +--rw one-way-residual-bandwidth? 884 | | rt-types:bandwidth-ieee-float32 885 | +--rw one-way-available-bandwidth? 886 | | rt-types:bandwidth-ieee-float32 887 | +--rw one-way-utilized-bandwidth? 888 | | rt-types:bandwidth-ieee-float32 889 | +--rw two-way-delay? uint32 890 | +--rw one-way-min-delay? uint32 891 | +--rw one-way-max-delay? uint32 892 | +--rw one-way-delay-variation? uint32 893 | +--rw one-way-packet-loss? decimal64 894 | +--rw two-way-min-delay? uint32 895 | +--rw two-way-max-delay? uint32 896 | +--rw two-way-delay-variation? uint32 897 | +--rw two-way-packet-loss? decimal64 898 +--rw threshold-in 899 | +--rw one-way-delay? uint32 900 | +--rw one-way-residual-bandwidth? 901 | | rt-types:bandwidth-ieee-float32 902 | +--rw one-way-available-bandwidth? 903 | | rt-types:bandwidth-ieee-float32 904 | +--rw one-way-utilized-bandwidth? 905 | | rt-types:bandwidth-ieee-float32 906 | +--rw two-way-delay? uint32 907 | +--rw one-way-min-delay? uint32 908 | +--rw one-way-max-delay? uint32 909 | +--rw one-way-delay-variation? uint32 910 | +--rw one-way-packet-loss? decimal64 911 | +--rw two-way-min-delay? uint32 912 | +--rw two-way-max-delay? uint32 913 | +--rw two-way-delay-variation? uint32 914 | +--rw two-way-packet-loss? decimal64 915 +--rw threshold-accelerated-advertisement 916 +--rw one-way-delay? uint32 917 +--rw one-way-residual-bandwidth? 918 | rt-types:bandwidth-ieee-float32 919 +--rw one-way-available-bandwidth? 920 | rt-types:bandwidth-ieee-float32 921 +--rw one-way-utilized-bandwidth? 922 | rt-types:bandwidth-ieee-float32 923 +--rw two-way-delay? uint32 924 +--rw one-way-min-delay? uint32 925 +--rw one-way-max-delay? uint32 926 +--rw one-way-delay-variation? uint32 927 +--rw one-way-packet-loss? decimal64 928 +--rw two-way-min-delay? uint32 929 +--rw two-way-max-delay? uint32 930 +--rw two-way-delay-variation? uint32 931 +--rw two-way-packet-loss? decimal64 932 augment /nw:networks/tet:te/tet:templates/tet:link-template 933 /tet:te-link-attributes: 934 +--ro performance-metrics-one-way 935 | +--ro one-way-delay? uint32 936 | +--ro one-way-delay-normality? 937 | | te-types:performance-metrics-normality 938 | +--ro one-way-residual-bandwidth? 939 | | rt-types:bandwidth-ieee-float32 940 | +--ro one-way-residual-bandwidth-normality? 941 | | te-types:performance-metrics-normality 942 | +--ro one-way-available-bandwidth? 943 | | rt-types:bandwidth-ieee-float32 944 | +--ro one-way-available-bandwidth-normality? 945 | | te-types:performance-metrics-normality 946 | +--ro one-way-utilized-bandwidth? 947 | | rt-types:bandwidth-ieee-float32 948 | +--ro one-way-utilized-bandwidth-normality? 949 | | te-types:performance-metrics-normality 950 | +--ro one-way-min-delay? uint32 951 | +--ro one-way-min-delay-normality? 952 | | te-types:performance-metrics-normality 953 | +--ro one-way-max-delay? uint32 954 | +--ro one-way-max-delay-normality? 955 | | te-types:performance-metrics-normality 956 | +--ro one-way-delay-variation? uint32 957 | +--ro one-way-delay-variation-normality? 958 | | te-types:performance-metrics-normality 959 | +--ro one-way-packet-loss? decimal64 960 | +--ro one-way-packet-loss-normality? 961 | te-types:performance-metrics-normality 962 +--ro performance-metrics-two-way 963 | +--ro two-way-delay? uint32 964 | +--ro two-way-delay-normality? 965 | | te-types:performance-metrics-normality 966 | +--ro two-way-min-delay? uint32 967 | +--ro two-way-min-delay-normality? 968 | | te-types:performance-metrics-normality 969 | +--ro two-way-max-delay? uint32 970 | +--ro two-way-max-delay-normality? 971 | | te-types:performance-metrics-normality 972 | +--ro two-way-delay-variation? uint32 973 | +--ro two-way-delay-variation-normality? 974 | | te-types:performance-metrics-normality 975 | +--ro two-way-packet-loss? decimal64 976 | +--ro two-way-packet-loss-normality? 977 | te-types:performance-metrics-normality 978 +--rw throttle 979 +--rw one-way-delay-offset? uint32 980 +--rw measure-interval? uint32 981 +--rw advertisement-interval? uint32 982 +--rw suppression-interval? uint32 983 +--rw threshold-out 984 | +--rw one-way-delay? uint32 985 | +--rw one-way-residual-bandwidth? 986 | | rt-types:bandwidth-ieee-float32 987 | +--rw one-way-available-bandwidth? 988 | | rt-types:bandwidth-ieee-float32 989 | +--rw one-way-utilized-bandwidth? 990 | | rt-types:bandwidth-ieee-float32 991 | +--rw two-way-delay? uint32 992 | +--rw one-way-min-delay? uint32 993 | +--rw one-way-max-delay? uint32 994 | +--rw one-way-delay-variation? uint32 995 | +--rw one-way-packet-loss? decimal64 996 | +--rw two-way-min-delay? uint32 997 | +--rw two-way-max-delay? uint32 998 | +--rw two-way-delay-variation? uint32 999 | +--rw two-way-packet-loss? decimal64 1000 +--rw threshold-in 1001 | +--rw one-way-delay? uint32 1002 | +--rw one-way-residual-bandwidth? 1003 | | rt-types:bandwidth-ieee-float32 1004 | +--rw one-way-available-bandwidth? 1005 | | rt-types:bandwidth-ieee-float32 1006 | +--rw one-way-utilized-bandwidth? 1007 | | rt-types:bandwidth-ieee-float32 1008 | +--rw two-way-delay? uint32 1009 | +--rw one-way-min-delay? uint32 1010 | +--rw one-way-max-delay? uint32 1011 | +--rw one-way-delay-variation? uint32 1012 | +--rw one-way-packet-loss? decimal64 1013 | +--rw two-way-min-delay? uint32 1014 | +--rw two-way-max-delay? uint32 1015 | +--rw two-way-delay-variation? uint32 1016 | +--rw two-way-packet-loss? decimal64 1017 +--rw threshold-accelerated-advertisement 1018 +--rw one-way-delay? uint32 1019 +--rw one-way-residual-bandwidth? 1020 | rt-types:bandwidth-ieee-float32 1021 +--rw one-way-available-bandwidth? 1022 | rt-types:bandwidth-ieee-float32 1023 +--rw one-way-utilized-bandwidth? 1024 | rt-types:bandwidth-ieee-float32 1025 +--rw two-way-delay? uint32 1026 +--rw one-way-min-delay? uint32 1027 +--rw one-way-max-delay? uint32 1028 +--rw one-way-delay-variation? uint32 1029 +--rw one-way-packet-loss? decimal64 1030 +--rw two-way-min-delay? uint32 1031 +--rw two-way-max-delay? uint32 1032 +--rw two-way-delay-variation? uint32 1033 +--rw two-way-packet-loss? decimal64 1034 augment /nw:networks/nw:network/nt:link/tet:te 1035 /tet:te-link-attributes: 1036 +--ro performance-metrics-one-way 1037 | +--ro one-way-delay? uint32 1038 | +--ro one-way-delay-normality? 1039 | | te-types:performance-metrics-normality 1040 | +--ro one-way-residual-bandwidth? 1041 | | rt-types:bandwidth-ieee-float32 1042 | +--ro one-way-residual-bandwidth-normality? 1043 | | te-types:performance-metrics-normality 1044 | +--ro one-way-available-bandwidth? 1045 | | rt-types:bandwidth-ieee-float32 1046 | +--ro one-way-available-bandwidth-normality? 1047 | | te-types:performance-metrics-normality 1048 | +--ro one-way-utilized-bandwidth? 1049 | | rt-types:bandwidth-ieee-float32 1050 | +--ro one-way-utilized-bandwidth-normality? 1051 | | te-types:performance-metrics-normality 1052 | +--ro one-way-min-delay? uint32 1053 | +--ro one-way-min-delay-normality? 1054 | | te-types:performance-metrics-normality 1055 | +--ro one-way-max-delay? uint32 1056 | +--ro one-way-max-delay-normality? 1057 | | te-types:performance-metrics-normality 1058 | +--ro one-way-delay-variation? uint32 1059 | +--ro one-way-delay-variation-normality? 1060 | | te-types:performance-metrics-normality 1061 | +--ro one-way-packet-loss? decimal64 1062 | +--ro one-way-packet-loss-normality? 1063 | te-types:performance-metrics-normality 1064 +--ro performance-metrics-two-way 1065 | +--ro two-way-delay? uint32 1066 | +--ro two-way-delay-normality? 1067 | | te-types:performance-metrics-normality 1068 | +--ro two-way-min-delay? uint32 1069 | +--ro two-way-min-delay-normality? 1070 | | te-types:performance-metrics-normality 1071 | +--ro two-way-max-delay? uint32 1072 | +--ro two-way-max-delay-normality? 1073 | | te-types:performance-metrics-normality 1074 | +--ro two-way-delay-variation? uint32 1075 | +--ro two-way-delay-variation-normality? 1076 | | te-types:performance-metrics-normality 1077 | +--ro two-way-packet-loss? decimal64 1078 | +--ro two-way-packet-loss-normality? 1079 | te-types:performance-metrics-normality 1080 +--rw throttle 1081 +--rw one-way-delay-offset? uint32 1082 +--rw measure-interval? uint32 1083 +--rw advertisement-interval? uint32 1084 +--rw suppression-interval? uint32 1085 +--rw threshold-out 1086 | +--rw one-way-delay? uint32 1087 | +--rw one-way-residual-bandwidth? 1088 | | rt-types:bandwidth-ieee-float32 1089 | +--rw one-way-available-bandwidth? 1090 | | rt-types:bandwidth-ieee-float32 1091 | +--rw one-way-utilized-bandwidth? 1092 | | rt-types:bandwidth-ieee-float32 1093 | +--rw two-way-delay? uint32 1094 | +--rw one-way-min-delay? uint32 1095 | +--rw one-way-max-delay? uint32 1096 | +--rw one-way-delay-variation? uint32 1097 | +--rw one-way-packet-loss? decimal64 1098 | +--rw two-way-min-delay? uint32 1099 | +--rw two-way-max-delay? uint32 1100 | +--rw two-way-delay-variation? uint32 1101 | +--rw two-way-packet-loss? decimal64 1102 +--rw threshold-in 1103 | +--rw one-way-delay? uint32 1104 | +--rw one-way-residual-bandwidth? 1105 | | rt-types:bandwidth-ieee-float32 1106 | +--rw one-way-available-bandwidth? 1107 | | rt-types:bandwidth-ieee-float32 1108 | +--rw one-way-utilized-bandwidth? 1109 | | rt-types:bandwidth-ieee-float32 1110 | +--rw two-way-delay? uint32 1111 | +--rw one-way-min-delay? uint32 1112 | +--rw one-way-max-delay? uint32 1113 | +--rw one-way-delay-variation? uint32 1114 | +--rw one-way-packet-loss? decimal64 1115 | +--rw two-way-min-delay? uint32 1116 | +--rw two-way-max-delay? uint32 1117 | +--rw two-way-delay-variation? uint32 1118 | +--rw two-way-packet-loss? decimal64 1119 +--rw threshold-accelerated-advertisement 1120 +--rw one-way-delay? uint32 1121 +--rw one-way-residual-bandwidth? 1122 | rt-types:bandwidth-ieee-float32 1123 +--rw one-way-available-bandwidth? 1124 | rt-types:bandwidth-ieee-float32 1125 +--rw one-way-utilized-bandwidth? 1126 | rt-types:bandwidth-ieee-float32 1127 +--rw two-way-delay? uint32 1128 +--rw one-way-min-delay? uint32 1129 +--rw one-way-max-delay? uint32 1130 +--rw one-way-delay-variation? uint32 1131 +--rw one-way-packet-loss? decimal64 1132 +--rw two-way-min-delay? uint32 1133 +--rw two-way-max-delay? uint32 1134 +--rw two-way-delay-variation? uint32 1135 +--rw two-way-packet-loss? decimal64 1136 augment /nw:networks/nw:network/nt:link/tet:te 1137 /tet:information-source-entry: 1138 +--ro performance-metrics-one-way 1139 | +--ro one-way-delay? uint32 1140 | +--ro one-way-delay-normality? 1141 | | te-types:performance-metrics-normality 1142 | +--ro one-way-residual-bandwidth? 1143 | | rt-types:bandwidth-ieee-float32 1144 | +--ro one-way-residual-bandwidth-normality? 1145 | | te-types:performance-metrics-normality 1146 | +--ro one-way-available-bandwidth? 1147 | | rt-types:bandwidth-ieee-float32 1148 | +--ro one-way-available-bandwidth-normality? 1149 | | te-types:performance-metrics-normality 1150 | +--ro one-way-utilized-bandwidth? 1151 | | rt-types:bandwidth-ieee-float32 1152 | +--ro one-way-utilized-bandwidth-normality? 1153 | | te-types:performance-metrics-normality 1154 | +--ro one-way-min-delay? uint32 1155 | +--ro one-way-min-delay-normality? 1156 | | te-types:performance-metrics-normality 1157 | +--ro one-way-max-delay? uint32 1158 | +--ro one-way-max-delay-normality? 1159 | | te-types:performance-metrics-normality 1160 | +--ro one-way-delay-variation? uint32 1161 | +--ro one-way-delay-variation-normality? 1162 | | te-types:performance-metrics-normality 1163 | +--ro one-way-packet-loss? decimal64 1164 | +--ro one-way-packet-loss-normality? 1165 | te-types:performance-metrics-normality 1166 +--ro performance-metrics-two-way 1167 | +--ro two-way-delay? uint32 1168 | +--ro two-way-delay-normality? 1169 | | te-types:performance-metrics-normality 1170 | +--ro two-way-min-delay? uint32 1171 | +--ro two-way-min-delay-normality? 1172 | | te-types:performance-metrics-normality 1173 | +--ro two-way-max-delay? uint32 1174 | +--ro two-way-max-delay-normality? 1175 | | te-types:performance-metrics-normality 1176 | +--ro two-way-delay-variation? uint32 1177 | +--ro two-way-delay-variation-normality? 1178 | | te-types:performance-metrics-normality 1179 | +--ro two-way-packet-loss? decimal64 1180 | +--ro two-way-packet-loss-normality? 1181 | te-types:performance-metrics-normality 1182 +--ro throttle 1183 +--ro one-way-delay-offset? uint32 1184 +--ro measure-interval? uint32 1185 +--ro advertisement-interval? uint32 1186 +--ro suppression-interval? uint32 1187 +--ro threshold-out 1188 | +--ro one-way-delay? uint32 1189 | +--ro one-way-residual-bandwidth? 1190 | | rt-types:bandwidth-ieee-float32 1191 | +--ro one-way-available-bandwidth? 1192 | | rt-types:bandwidth-ieee-float32 1193 | +--ro one-way-utilized-bandwidth? 1194 | | rt-types:bandwidth-ieee-float32 1195 | +--ro two-way-delay? uint32 1196 | +--ro one-way-min-delay? uint32 1197 | +--ro one-way-max-delay? uint32 1198 | +--ro one-way-delay-variation? uint32 1199 | +--ro one-way-packet-loss? decimal64 1200 | +--ro two-way-min-delay? uint32 1201 | +--ro two-way-max-delay? uint32 1202 | +--ro two-way-delay-variation? uint32 1203 | +--ro two-way-packet-loss? decimal64 1204 +--ro threshold-in 1205 | +--ro one-way-delay? uint32 1206 | +--ro one-way-residual-bandwidth? 1207 | | rt-types:bandwidth-ieee-float32 1208 | +--ro one-way-available-bandwidth? 1209 | | rt-types:bandwidth-ieee-float32 1210 | +--ro one-way-utilized-bandwidth? 1211 | | rt-types:bandwidth-ieee-float32 1212 | +--ro two-way-delay? uint32 1213 | +--ro one-way-min-delay? uint32 1214 | +--ro one-way-max-delay? uint32 1215 | +--ro one-way-delay-variation? uint32 1216 | +--ro one-way-packet-loss? decimal64 1217 | +--ro two-way-min-delay? uint32 1218 | +--ro two-way-max-delay? uint32 1219 | +--ro two-way-delay-variation? uint32 1220 | +--ro two-way-packet-loss? decimal64 1221 +--ro threshold-accelerated-advertisement 1222 +--ro one-way-delay? uint32 1223 +--ro one-way-residual-bandwidth? 1224 | rt-types:bandwidth-ieee-float32 1225 +--ro one-way-available-bandwidth? 1226 | rt-types:bandwidth-ieee-float32 1227 +--ro one-way-utilized-bandwidth? 1228 | rt-types:bandwidth-ieee-float32 1229 +--ro two-way-delay? uint32 1230 +--ro one-way-min-delay? uint32 1231 +--ro one-way-max-delay? uint32 1232 +--ro one-way-delay-variation? uint32 1233 +--ro one-way-packet-loss? decimal64 1234 +--ro two-way-min-delay? uint32 1235 +--ro two-way-max-delay? uint32 1236 +--ro two-way-delay-variation? uint32 1237 +--ro two-way-packet-loss? decimal64 1238 augment /nw:networks/tet:te/tet:templates/tet:link-template 1239 /tet:te-link-attributes 1240 /tet:interface-switching-capability: 1241 +--rw packet-switch-capable 1242 +--rw minimum-lsp-bandwidth? rt-types:bandwidth-ieee-float32 1243 +--rw interface-mtu? uint16 1244 augment /nw:networks/nw:network/nt:link/tet:te 1245 /tet:te-link-attributes 1246 /tet:interface-switching-capability: 1247 +--rw packet-switch-capable 1248 +--rw minimum-lsp-bandwidth? rt-types:bandwidth-ieee-float32 1249 +--rw interface-mtu? uint16 1250 augment /nw:networks/nw:network/nt:link/tet:te 1251 /tet:information-source-entry 1252 /tet:interface-switching-capability: 1253 +--ro packet-switch-capable 1254 +--ro minimum-lsp-bandwidth? rt-types:bandwidth-ieee-float32 1255 +--ro interface-mtu? uint16 1257 5. YANG Modules 1259 5.1. Layer 3 TE Topology Module 1261 This module references [RFC8345], [RFC8346], and 1262 [I-D.ietf-teas-yang-te-topo]. 1264 file "ietf-l3-te-topology@2019-06-28.yang" 1265 module ietf-l3-te-topology { 1266 yang-version 1.1; 1267 namespace "urn:ietf:params:xml:ns:yang:ietf-l3-te-topology"; 1268 prefix "l3tet"; 1270 import ietf-network { 1271 prefix "nw"; 1272 reference "RFC 8345: A YANG Data Model for Network Topologies"; 1273 } 1274 import ietf-network-topology { 1275 prefix "nt"; 1276 reference "RFC 8345: A YANG Data Model for Network Topologies"; 1277 } 1278 import ietf-l3-unicast-topology { 1279 prefix "l3t"; 1280 reference "RFC 8346: A YANG Data Model for Layer 3 Topologies"; 1281 } 1282 import ietf-te-topology { 1283 prefix "tet"; 1284 reference 1285 "I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic 1286 Engineering (TE) Topologies"; 1287 } 1289 organization 1290 "IETF Traffic Engineering Architecture and Signaling (TEAS) 1291 Working Group"; 1293 contact 1294 "WG Web: 1295 WG List: 1297 Editor: Xufeng Liu 1298 1300 Editor: Igor Bryskin 1301 1303 Editor: Vishnu Pavan Beeram 1304 1306 Editor: Tarek Saad 1307 1309 Editor: Himanshu Shah 1310 1312 Editor: Oscar Gonzalez De Dios 1313 "; 1315 description 1316 "YANG data model for representing and manipulating Layer 3 TE 1317 Topologies. 1319 Copyright (c) 2018 IETF Trust and the persons identified as 1320 authors of the code. All rights reserved. 1322 Redistribution and use in source and binary forms, with or 1323 without modification, is permitted pursuant to, and subject to 1324 the license terms contained in, the Simplified BSD License set 1325 forth in Section 4.c of the IETF Trust's Legal Provisions 1326 Relating to IETF Documents 1327 (http://trustee.ietf.org/license-info). 1329 This version of this YANG module is part of RFC XXXX; see the 1330 RFC itself for full legal notices."; 1332 revision 2019-06-28 { 1334 description 1335 "Initial revision"; 1336 reference "RFC XXXX: YANG Data Model for Layer 3 TE Topologies"; 1337 } 1339 grouping l3-te-topology-type { 1340 description 1341 "Identifies the L3 TE topology type."; 1342 container l3-te { 1343 presence "Indiates L3 TE Topology"; 1344 description 1345 "Its presence identifies the L3 TE topology type."; 1346 } 1347 } 1349 augment "/nw:networks/nw:network/nw:network-types/" 1350 + "l3t:l3-unicast-topology" { 1351 description 1352 "Defines the L3 TE topology type."; 1353 uses l3-te-topology-type; 1354 } 1356 augment "/nw:networks/nw:network/l3t:l3-topology-attributes" { 1357 when "../nw:network-types/l3t:l3-unicast-topology/l3tet:l3-te" { 1358 description 1359 "Augment only for L3 TE topology"; 1360 } 1361 description 1362 "Augment topology configuration"; 1363 uses l3-te-topology-attributes; 1364 } 1366 augment "/nw:networks/nw:network/nw:node/l3t:l3-node-attributes" { 1367 when "../../nw:network-types/l3t:l3-unicast-topology/" 1368 + "l3tet:l3-te" { 1369 description 1370 "Augment only for L3 TE topology"; 1371 } 1372 description 1373 "Augment node configuration"; 1375 uses l3-te-node-attributes; 1376 } 1378 augment "/nw:networks/nw:network/nw:node/nt:termination-point/" 1379 + "l3t:l3-termination-point-attributes" { 1380 when "../../../nw:network-types/l3t:l3-unicast-topology/" 1381 + "l3tet:l3-te" { 1382 description 1383 "Augment only for L3 TE topology"; 1384 } 1385 description 1386 "Augment termination point configuration"; 1387 uses l3-te-tp-attributes; 1388 } 1390 augment "/nw:networks/nw:network/nt:link/l3t:l3-link-attributes" { 1391 when "../../nw:network-types/l3t:l3-unicast-topology/" 1392 + "l3tet:l3-te" { 1393 description 1394 "Augment only for L3 TE topology"; 1395 } 1396 description 1397 "Augment link configuration"; 1398 uses l3-te-link-attributes; 1399 } 1401 grouping l3-te-topology-attributes { 1402 description 1403 "L3 TE topology scope attributes"; 1404 container l3-te-topology-attributes { 1405 must "/nw:networks/nw:network" 1406 + "[nw:network-id = current()/network-ref]/nw:network-types/" 1407 + "tet:te-topology" { 1408 error-message 1409 "The referenced network must be a TE topology."; 1410 description 1411 "The referenced network must be a TE topology."; 1412 } 1413 description 1414 "Containing TE topology references"; 1415 uses nw:network-ref; 1416 } // l3-te-topology-attributes 1417 } // l3-te-topology-attributes 1419 grouping l3-te-node-attributes { 1420 description 1421 "L3 TE node scope attributes"; 1422 container l3-te-node-attributes { 1423 must "/nw:networks/nw:network" 1424 + "[nw:network-id = current()/network-ref]/nw:network-types/" 1425 + "tet:te-topology" { 1426 error-message 1427 "The referenced network must be a TE topology."; 1428 description 1429 "The referenced network must be a TE topology."; 1430 } 1431 description 1432 "Containing TE node references"; 1433 uses nw:node-ref; 1434 } // l3-te 1435 } // l3-te-node-attributes 1437 grouping l3-te-tp-attributes { 1438 description 1439 "L3 TE termination point scope attributes"; 1440 container l3-te-tp-attributes { 1441 must "/nw:networks/nw:network" 1442 + "[nw:network-id = current()/network-ref]/nw:network-types/" 1443 + "tet:te-topology" { 1444 error-message 1445 "The referenced network must be a TE topology."; 1446 description 1447 "The referenced network must be a TE topology."; 1448 } 1449 description 1450 "Containing TE termination point references"; 1451 uses nt:tp-ref; 1452 } // l3-te 1453 } // l3-te-tp-attributes 1455 grouping l3-te-link-attributes { 1456 description 1457 "L3 TE link scope attributes"; 1458 container l3-te-link-attributes { 1459 must "/nw:networks/nw:network" 1460 + "[nw:network-id = current()/network-ref]/nw:network-types/" 1461 + "tet:te-topology" { 1462 error-message 1463 "The referenced network must be a TE topology."; 1464 description 1465 "The referenced network must be a TE topology."; 1466 } 1467 description 1468 "Containing TE link references"; 1469 uses nt:link-ref; 1470 } 1472 } // l3-te-link-attributes 1473 } 1474 1476 5.2. Packet Switching TE Topology Module 1478 This module references [RFC7471], [RFC7823], [RFC8294], [RFC8345], 1479 [RFC8346]. [RFC8570], [I-D.ietf-teas-yang-te-types], and 1480 [I-D.ietf-teas-yang-te-topo]. 1482 file "ietf-te-topology-packet@2019-06-28.yang" 1483 module ietf-te-topology-packet { 1484 yang-version 1.1; 1485 namespace "urn:ietf:params:xml:ns:yang:ietf-te-topology-packet"; 1487 prefix "tet-pkt"; 1489 import ietf-network { 1490 prefix "nw"; 1491 reference 1492 "RFC 8345: A YANG Data Model for Network Topologies"; 1493 } 1495 import ietf-network-topology { 1496 prefix "nt"; 1497 reference 1498 "RFC 8345: A YANG Data Model for Network Topologies"; 1499 } 1501 import ietf-routing-types { 1502 prefix "rt-types"; 1503 reference 1504 "RFC 8294: Common YANG Data Types for the Routing Area"; 1505 } 1507 import ietf-te-topology { 1508 prefix "tet"; 1509 reference 1510 "I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic 1511 Engineering (TE) Topologies"; 1512 } 1514 import ietf-te-types { 1515 prefix "te-types"; 1516 reference 1517 "I-D.ietf-teas-yang-te-types: Traffic Engineering Common YANG 1518 Types"; 1519 } 1521 import ietf-te-packet-types { 1522 prefix "te-packet-types"; 1523 reference 1524 "I-D.ietf-teas-yang-te-types: Traffic Engineering Common YANG 1525 Types"; 1526 } 1528 organization 1529 "Traffic Engineering Architecture and Signaling (TEAS) 1530 Working Group"; 1532 contact 1533 "WG Web: 1534 WG List: 1536 Editor: Xufeng Liu 1537 1539 Editor: Igor Bryskin 1540 1542 Editor: Vishnu Pavan Beeram 1543 1545 Editor: Tarek Saad 1546 1548 Editor: Himanshu Shah 1549 1551 Editor: Oscar Gonzalez De Dios 1552 "; 1554 description 1555 "YANG data model for representing and manipulating PSC (Packet 1556 Switching) TE Topologies. 1558 Copyright (c) 2018 IETF Trust and the persons identified as 1559 authors of the code. All rights reserved. 1561 Redistribution and use in source and binary forms, with or 1562 without modification, is permitted pursuant to, and subject to 1563 the license terms contained in, the Simplified BSD License set 1564 forth in Section 4.c of the IETF Trust's Legal Provisions 1565 Relating to IETF Documents 1566 (http://trustee.ietf.org/license-info). 1568 This version of this YANG module is part of RFC XXXX; see the 1569 RFC itself for full legal notices."; 1571 revision 2019-06-28 { 1572 description 1573 "Initial revision"; 1574 reference 1575 "RFC XXXX: YANG Data Model for Layer 3 TE Topologies"; 1576 } 1578 /* 1579 * Features 1580 */ 1582 feature te-performance-metric { 1583 description 1584 "This feature indicates that the system supports 1585 TE performance metric."; 1586 reference 1587 "RFC7471: OSPF Traffic Engineering (TE) Metric Extensions. 1588 RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions. 1589 RFC7823: Performance-Based Path Selection for Explicitly 1590 Routed Label Switched Paths (LSPs) Using TE Metric 1591 Extensions"; 1592 } 1594 /* 1595 * Groupings 1596 */ 1597 grouping packet-switch-capable-container { 1598 description 1599 "The container of packet switch capable attributes."; 1600 container packet-switch-capable { 1601 description 1602 "Interface has packet-switching capabilities."; 1603 leaf minimum-lsp-bandwidth { 1604 type rt-types:bandwidth-ieee-float32; 1605 description 1606 "Minimum LSP Bandwidth. Units in bytes per second"; 1607 } 1608 leaf interface-mtu { 1609 type uint16; 1610 description 1611 "Interface MTU."; 1612 } 1614 } 1615 } 1617 /* 1618 * Augmentations 1619 */ 1620 /* Augmentations to connectivity-matrix */ 1621 augment "/nw:networks/nw:network/nw:node/tet:te/" 1622 + "tet:te-node-attributes/tet:connectivity-matrices" { 1623 description 1624 "Parameters for PSC TE topology."; 1625 uses te-packet-types:performance-metrics-attributes-packet { 1626 if-feature te-performance-metric; 1627 refine performance-metrics-one-way { 1628 config false; 1629 } 1630 refine performance-metrics-two-way { 1631 config false; 1632 } 1633 } 1634 uses 1635 te-packet-types:performance-metrics-throttle-container-packet { 1636 if-feature te-performance-metric; 1637 } 1638 } 1640 augment "/nw:networks/nw:network/nw:node/tet:te/" 1641 + "tet:te-node-attributes/tet:connectivity-matrices/" 1642 + "tet:connectivity-matrix" { 1643 description 1644 "Parameters for PSC TE topology."; 1645 uses te-packet-types:performance-metrics-attributes-packet { 1646 if-feature te-performance-metric; 1647 refine performance-metrics-one-way { 1648 config false; 1649 } 1650 refine performance-metrics-two-way { 1651 config false; 1652 } 1653 } 1654 uses 1655 te-packet-types:performance-metrics-throttle-container-packet { 1656 if-feature te-performance-metric; 1657 } 1658 } 1660 augment "/nw:networks/nw:network/nw:node/tet:te/" 1661 + "tet:information-source-entry/tet:connectivity-matrices" { 1663 description 1664 "Parameters for PSC TE topology."; 1665 uses te-packet-types:performance-metrics-attributes-packet { 1666 if-feature te-performance-metric; 1667 } 1668 uses 1669 te-packet-types:performance-metrics-throttle-container-packet { 1670 if-feature te-performance-metric; 1671 } 1672 } 1674 augment "/nw:networks/nw:network/nw:node/tet:te/" 1675 + "tet:information-source-entry/tet:connectivity-matrices/" 1676 + "tet:connectivity-matrix" { 1677 description 1678 "Parameters for PSC TE topology."; 1679 uses te-packet-types:performance-metrics-attributes-packet { 1680 if-feature te-performance-metric; 1681 } 1682 uses 1683 te-packet-types:performance-metrics-throttle-container-packet { 1684 if-feature te-performance-metric; 1685 } 1686 } 1688 /* Augmentations to tunnel-termination-point */ 1689 augment "/nw:networks/nw:network/nw:node/tet:te/" 1690 + "tet:tunnel-termination-point/" 1691 + "tet:local-link-connectivities" { 1692 description 1693 "Parameters for PSC TE topology."; 1694 uses te-packet-types:performance-metrics-attributes-packet { 1695 if-feature te-performance-metric; 1696 refine performance-metrics-one-way { 1697 config false; 1698 } 1699 refine performance-metrics-two-way { 1700 config false; 1701 } 1702 } 1703 uses 1704 te-packet-types:performance-metrics-throttle-container-packet { 1705 if-feature te-performance-metric; 1706 } 1707 } 1709 augment "/nw:networks/nw:network/nw:node/tet:te/" 1710 + "tet:tunnel-termination-point/" 1711 + "tet:local-link-connectivities/" 1712 + "tet:local-link-connectivity" { 1713 description 1714 "Parameters for PSC TE topology."; 1715 uses te-packet-types:performance-metrics-attributes-packet { 1716 if-feature te-performance-metric; 1717 refine performance-metrics-one-way { 1718 config false; 1719 } 1720 refine performance-metrics-two-way { 1721 config false; 1722 } 1723 } 1724 uses 1725 te-packet-types:performance-metrics-throttle-container-packet { 1726 if-feature te-performance-metric; 1727 } 1728 } 1730 /* Augmentations to te-link-attributes */ 1731 augment "/nw:networks/tet:te/tet:templates/" 1732 + "tet:link-template/tet:te-link-attributes" { 1733 when "tet:interface-switching-capability " 1734 + "[tet:switching-capability = 'te-types:switching-psc1']" { 1735 description 1736 "Valid only for PSC"; 1737 } 1738 description 1739 "Parameters for PSC TE topology."; 1740 uses te-packet-types:performance-metrics-attributes-packet { 1741 if-feature te-performance-metric; 1742 refine performance-metrics-one-way { 1743 config false; 1744 } 1745 refine performance-metrics-two-way { 1746 config false; 1747 } 1748 } 1749 uses 1750 te-packet-types:performance-metrics-throttle-container-packet { 1751 if-feature te-performance-metric; 1752 } 1753 } 1755 augment "/nw:networks/nw:network/nt:link/tet:te/" 1756 + "tet:te-link-attributes" { 1757 when "tet:interface-switching-capability " 1758 + "[tet:switching-capability = 'te-types:switching-psc1']" { 1759 description 1760 "Valid only for PSC"; 1761 } 1762 description 1763 "Parameters for PSC TE topology."; 1764 uses te-packet-types:performance-metrics-attributes-packet { 1765 if-feature te-performance-metric; 1766 refine performance-metrics-one-way { 1767 config false; 1768 } 1769 refine performance-metrics-two-way { 1770 config false; 1771 } 1772 } 1773 uses 1774 te-packet-types:performance-metrics-throttle-container-packet { 1775 if-feature te-performance-metric; 1776 } 1777 } 1779 augment "/nw:networks/nw:network/nt:link/tet:te/" 1780 + "tet:information-source-entry" { 1781 when "tet:interface-switching-capability " 1782 + "[tet:switching-capability = 'te-types:switching-psc1']" { 1783 description 1784 "Valid only for PSC"; 1785 } 1786 description 1787 "Parameters for PSC TE topology."; 1788 uses te-packet-types:performance-metrics-attributes-packet { 1789 if-feature te-performance-metric; 1790 } 1791 uses 1792 te-packet-types:performance-metrics-throttle-container-packet { 1793 if-feature te-performance-metric; 1794 } 1795 } 1797 /* Augmentations to interface-switching-capability */ 1798 augment "/nw:networks/tet:te/tet:templates/" 1799 + "tet:link-template/tet:te-link-attributes/" 1800 + "tet:interface-switching-capability" { 1801 when "tet:switching-capability = 'te-types:switching-psc1' " { 1802 description 1803 "Valid only for PSC"; 1804 } 1805 description 1806 "Parameters for PSC TE topology."; 1808 uses packet-switch-capable-container; 1809 } 1811 augment "/nw:networks/nw:network/nt:link/tet:te/" 1812 + "tet:te-link-attributes/" 1813 + "tet:interface-switching-capability" { 1814 when "tet:switching-capability = 'te-types:switching-psc1' " { 1815 description 1816 "Valid only for PSC"; 1817 } 1818 description 1819 "Parameters for PSC TE topology."; 1820 uses packet-switch-capable-container; 1821 } 1823 augment "/nw:networks/nw:network/nt:link/tet:te/" 1824 + "tet:information-source-entry/" 1825 + "tet:interface-switching-capability" { 1826 when "tet:switching-capability = 'te-types:switching-psc1' " { 1827 description 1828 "Valid only for PSC"; 1829 } 1830 description 1831 "Parameters for PSC TE topology."; 1832 uses packet-switch-capable-container; 1833 } 1834 } 1835 1837 6. IANA Considerations 1839 RFC Ed.: In this section, replace all occurrences of 'XXXX' with the 1840 actual RFC number (and remove this note). 1842 This document registers the following namespace URIs in the IETF XML 1843 registry [RFC3688]: 1845 -------------------------------------------------------------------- 1846 URI: urn:ietf:params:xml:ns:yang:ietf-l3-te-topology 1847 Registrant Contact: The IESG. 1848 XML: N/A, the requested URI is an XML namespace. 1849 -------------------------------------------------------------------- 1850 -------------------------------------------------------------------- 1851 URI: urn:ietf:params:xml:ns:yang:ietf-l3-te-topology-state 1852 Registrant Contact: The IESG. 1853 XML: N/A, the requested URI is an XML namespace. 1854 -------------------------------------------------------------------- 1856 -------------------------------------------------------------------- 1857 URI: urn:ietf:params:xml:ns:yang:ietf-te-topology-packet 1858 Registrant Contact: The IESG. 1859 XML: N/A, the requested URI is an XML namespace. 1860 -------------------------------------------------------------------- 1862 -------------------------------------------------------------------- 1863 URI: urn:ietf:params:xml:ns:yang:ietf-te-topology-packet-state 1864 Registrant Contact: The IESG. 1865 XML: N/A, the requested URI is an XML namespace. 1866 -------------------------------------------------------------------- 1868 This document registers the following YANG modules in the YANG Module 1869 Names registry [RFC6020]: 1871 -------------------------------------------------------------------- 1872 name: ietf-l3-te-topology 1873 namespace: urn:ietf:params:xml:ns:yang:ietf-l3-te-topology 1874 prefix: l3te 1875 reference: RFC XXXX 1876 -------------------------------------------------------------------- 1878 -------------------------------------------------------------------- 1879 name: ietf-l3-te-topology-state 1880 namespace: urn:ietf:params:xml:ns:yang:ietf-l3-te-topology-state 1881 prefix: l3te-s 1882 reference: RFC XXXX 1883 -------------------------------------------------------------------- 1885 -------------------------------------------------------------------- 1886 name: ietf-te-topology-packet 1887 namespace: urn:ietf:params:xml:ns:yang:ietf-te-topology-packet 1888 prefix: tet-pkt 1889 reference: RFC XXXX 1890 -------------------------------------------------------------------- 1892 -------------------------------------------------------------------- 1893 name: ietf-te-topology-packet-state 1894 namespace: urn:ietf:params:xml:ns:yang:ietf-te-topology-packet-state 1895 prefix: tet-pkt-s 1896 reference: RFC XXXX 1897 -------------------------------------------------------------------- 1899 7. Security Considerations 1901 The YANG module specified in this document defines a schema for data 1902 that is designed to be accessed via network management protocols such 1903 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 1904 is the secure transport layer, and the mandatory-to-implement secure 1905 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 1906 is HTTPS, and the mandatory-to-implement secure transport is TLS 1907 [RFC8446]. 1909 The Network Configuration Access Control Model (NACM) [RFC8341] 1910 provides the means to restrict access for particular NETCONF or 1911 RESTCONF users to a preconfigured subset of all available NETCONF or 1912 RESTCONF protocol operations and content. 1914 There are a number of data nodes defined in this YANG module that are 1915 writable/creatable/deletable (i.e., config true, which is the 1916 default). These data nodes may be considered sensitive or vulnerable 1917 in some network environments. Write operations (e.g., edit-config) 1918 to these data nodes without proper protection can have a negative 1919 effect on network operations. These are the subtrees and data nodes 1920 and their sensitivity/vulnerability: 1922 /nw:networks/nw:network/nw:network-types/l3t:l3-unicast-topology/ 1923 l3-te 1924 This subtree specifies the layer 3 TE topology type. Modifying 1925 the configurations can make layer 3 TE topology type invalid and 1926 cause interruption to all layer 3 TE networks. 1928 /nw:networks/nw:network/l3t:l3-topology-attributes/l3-te-topology- 1929 attributes 1930 This subtree specifies the topology-wide configurations, including 1931 the reference to a TE topology from a layer 3 network topolopy. 1932 Modifying the configurations here can cause traffic disabled or 1933 rerouted in this topology and the connected topologies. 1935 /nw:networks/nw:network/nw:node/l3t:l3-node-attributes/l3-te-node- 1936 attributes 1937 This subtree specifies the configurations of layer 3 TE nodes. 1938 Modifying the configurations in this subtree can change the 1939 relationship between a TE node and a layer 3 node, causing traffic 1940 disabled or rerouted in the specified nodes and the related layer 1941 3 topologies. 1943 /nw:networks/nw:network/nw:node/nt:termination-point//l3t:l3- 1944 termination-point-attributes/l3-te-tp-attributes 1945 This subtree specifies the configurations of layer 3 TE link 1946 termination points. Modifying the configurations in this subtree 1947 can change the relationship between a TE link termination point 1948 and a layer 3 link termination point, causing traffic disabled or 1949 rerouted on the related layer 3 links and the related layer 3 1950 topologies. 1952 /nw:networks/nw:network/nt:link/l3t:l3-link-attributes/l3-te-link- 1953 attributes 1954 This subtree specifies the configurations of layer 3 TE links. 1955 Modifying the configurations in this subtree can change the 1956 relationship between a TE link and a layer 3 link, causing traffic 1957 disabled or rerouted on the specified layer 3 link and the related 1958 layer 3 topologies. 1960 performance-metric containers 1961 The container "performance-metric" is augmented to multiple 1962 locations of the base TE topology model, as specified in 1963 Section 3.2. Modifying the configuration in such a container can 1964 change the behavours of performance metric monitoring, causing 1965 traffic disabled or rerouted on the related layer 3 links, nodes, 1966 or topologies. 1968 Some of the readable data nodes in this YANG module may be considered 1969 sensitive or vulnerable in some network environments. It is thus 1970 important to control read access (e.g., via get, get-config, or 1971 notification) to these data nodes. These are the subtrees and data 1972 nodes and their sensitivity/vulnerability: 1974 /nw:networks/nw:network/nw:network-types/l3t:l3-unicast-topology/ 1975 l3-te 1976 Unauthorized access to this subtree can disclose the layer 3 TE 1977 topology type. 1979 /nw:networks/nw:network/l3t:l3-topology-attributes/l3-te-topology- 1980 attributes 1981 Unauthorized access to this subtree can disclose the topology-wide 1982 configurations, including the reference to a TE topology from a 1983 layer 3 network topolopy. 1985 /nw:networks/nw:network/nw:node/l3t:l3-node-attributes/l3-te-node- 1986 attributes 1987 Unauthorized access to this subtree can disclose the operational 1988 state information of layer 3 TE nodes. 1990 /nw:networks/nw:network/nw:node/nt:termination-point//l3t:l3- 1991 termination-point-attributes/l3-te-tp-attributes 1992 Unauthorized access to this subtree can disclose the operational 1993 state information of layer 3 TE link termination points. 1995 /nw:networks/nw:network/nt:link/l3t:l3-link-attributes/l3-te-link- 1996 attributes 1997 Unauthorized access to this subtree can disclose the operational 1998 state information of layer 3 TE links. 2000 performance-metric containers 2001 The container "performance-metric" is augmented to multiple 2002 locations of the base TE topology model, as specified in 2003 Section 3.2. Unauthorized access to this subtree can disclose the 2004 operational state information of performance metric monitoring. 2006 8. References 2008 8.1. Normative References 2010 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2011 Requirement Levels", BCP 14, RFC 2119, 2012 DOI 10.17487/RFC2119, March 1997, 2013 . 2015 [RFC3471] Berger, L., Ed., "Generalized Multi-Protocol Label 2016 Switching (GMPLS) Signaling Functional Description", 2017 RFC 3471, DOI 10.17487/RFC3471, January 2003, 2018 . 2020 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 2021 DOI 10.17487/RFC3688, January 2004, 2022 . 2024 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 2025 the Network Configuration Protocol (NETCONF)", RFC 6020, 2026 DOI 10.17487/RFC6020, October 2010, 2027 . 2029 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 2030 and A. Bierman, Ed., "Network Configuration Protocol 2031 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 2032 . 2034 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 2035 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 2036 . 2038 [RFC7074] Berger, L. and J. Meuric, "Revised Definition of the GMPLS 2039 Switching Capability and Type Fields", RFC 7074, 2040 DOI 10.17487/RFC7074, November 2013, 2041 . 2043 [RFC7471] Giacalone, S., Ward, D., Drake, J., Atlas, A., and S. 2044 Previdi, "OSPF Traffic Engineering (TE) Metric 2045 Extensions", RFC 7471, DOI 10.17487/RFC7471, March 2015, 2046 . 2048 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 2049 RFC 7950, DOI 10.17487/RFC7950, August 2016, 2050 . 2052 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 2053 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 2054 . 2056 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2057 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2058 May 2017, . 2060 [RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger, 2061 "Common YANG Data Types for the Routing Area", RFC 8294, 2062 DOI 10.17487/RFC8294, December 2017, 2063 . 2065 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 2066 Access Control Model", STD 91, RFC 8341, 2067 DOI 10.17487/RFC8341, March 2018, 2068 . 2070 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 2071 and R. Wilton, "Network Management Datastore Architecture 2072 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 2073 . 2075 [RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N., 2076 Ananthakrishnan, H., and X. Liu, "A YANG Data Model for 2077 Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March 2078 2018, . 2080 [RFC8346] Clemm, A., Medved, J., Varga, R., Liu, X., 2081 Ananthakrishnan, H., and N. Bahadur, "A YANG Data Model 2082 for Layer 3 Topologies", RFC 8346, DOI 10.17487/RFC8346, 2083 March 2018, . 2085 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 2086 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 2087 . 2089 [RFC8570] Ginsberg, L., Ed., Previdi, S., Ed., Giacalone, S., Ward, 2090 D., Drake, J., and Q. Wu, "IS-IS Traffic Engineering (TE) 2091 Metric Extensions", RFC 8570, DOI 10.17487/RFC8570, March 2092 2019, . 2094 [I-D.ietf-teas-yang-te-types] 2095 Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, 2096 "Traffic Engineering Common YANG Types", draft-ietf-teas- 2097 yang-te-types-09 (work in progress), May 2019. 2099 [I-D.ietf-teas-yang-te-topo] 2100 Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and 2101 O. Dios, "YANG Data Model for Traffic Engineering (TE) 2102 Topologies", draft-ietf-teas-yang-te-topo-22 (work in 2103 progress), June 2019. 2105 8.2. Informative References 2107 [RFC7823] Atlas, A., Drake, J., Giacalone, S., and S. Previdi, 2108 "Performance-Based Path Selection for Explicitly Routed 2109 Label Switched Paths (LSPs) Using TE Metric Extensions", 2110 RFC 7823, DOI 10.17487/RFC7823, May 2016, 2111 . 2113 [RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG", 2114 RFC 7951, DOI 10.17487/RFC7951, August 2016, 2115 . 2117 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 2118 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 2119 . 2121 Appendix A. Companion YANG Model for Non-NMDA Compliant Implementations 2123 The YANG modules ietf-l3-te-topology and ietf-te-topology-packet 2124 defined in this document are designed to be used in conjunction with 2125 implementations that support the Network Management Datastore 2126 Architecture (NMDA) defined in [RFC8342]. In order to allow 2127 implementations to use the model even in cases when NMDA is not 2128 supported, the following companion modules, ietf-l3-te-topology-state 2129 and ietf-te-topology-packet-state, are defined as state models, which 2130 mirror the modules ietf-l3-te-topology and ietf-te-topology-packet 2131 defined earlier in this document. However, all data nodes in the 2132 companion module are non-configurable, to represent the applied 2133 configuration or the derived operational states. 2135 The companion modules, ietf-l3-te-topology-state and ietf-te- 2136 topology-packet-state, are redundant and SHOULD NOT be supported by 2137 implementations that support NMDA. 2139 As the structure of the companion modules mirrors that of the 2140 coorespinding NMDA models, the YANG trees of the companion modules 2141 are not depicted separately. 2143 A.1. Layer 3 TE Topology State Module 2145 This module references [RFC8345], and [RFC8346]. 2147 file "ietf-l3-te-topology-state@2019-06-28.yang" 2148 module ietf-l3-te-topology-state { 2149 yang-version 1.1; 2150 namespace "urn:ietf:params:xml:ns:yang:ietf-l3-te-topology-state"; 2151 prefix "l3tet-s"; 2153 import ietf-l3-te-topology { 2154 prefix "l3tet"; 2155 } 2156 import ietf-network-state { 2157 prefix "nw-s"; 2158 reference "RFC 8345: A YANG Data Model for Network Topologies"; 2159 } 2160 import ietf-network-topology-state { 2161 prefix "nt-s"; 2162 reference "RFC 8345: A YANG Data Model for Network Topologies"; 2163 } 2164 import ietf-l3-unicast-topology-state { 2165 prefix "l3t-s"; 2166 reference "RFC 8346: A YANG Data Model for Layer 3 Topologies"; 2167 } 2168 organization 2169 "IETF Traffic Engineering Architecture and Signaling (TEAS) 2170 Working Group"; 2172 contact 2173 "WG Web: 2174 WG List: 2176 Editor: Xufeng Liu 2177 2179 Editor: Igor Bryskin 2180 2182 Editor: Vishnu Pavan Beeram 2183 2185 Editor: Tarek Saad 2186 2188 Editor: Himanshu Shah 2189 2191 Editor: Oscar Gonzalez De Dios 2192 "; 2194 description 2195 "YANG data model for representing operational state information 2196 of Layer 3 TE Topologies, when NMDA is not supported. 2198 Copyright (c) 2018 IETF Trust and the persons identified as 2199 authors of the code. All rights reserved. 2201 Redistribution and use in source and binary forms, with or 2202 without modification, is permitted pursuant to, and subject to 2203 the license terms contained in, the Simplified BSD License set 2204 forth in Section 4.c of the IETF Trust's Legal Provisions 2205 Relating to IETF Documents 2206 (http://trustee.ietf.org/license-info). 2208 This version of this YANG module is part of RFC XXXX; see the 2209 RFC itself for full legal notices."; 2211 revision 2019-06-28 { 2212 description 2213 "Initial revision"; 2214 reference "RFC XXXX: YANG Data Model for Layer 3 TE Topologies"; 2215 } 2216 augment "/nw-s:networks/nw-s:network/nw-s:network-types/" 2217 + "l3t-s:l3-unicast-topology" { 2218 description 2219 "Defines the L3 TE topology type."; 2220 uses l3tet:l3-te-topology-type; 2221 } 2223 augment "/nw-s:networks/nw-s:network/" 2224 + "l3t-s:l3-topology-attributes" { 2225 when "../nw-s:network-types/l3t-s:l3-unicast-topology/" 2226 + "l3tet-s:l3-te" { 2227 description 2228 "Augment only for L3 TE topology"; 2229 } 2230 description 2231 "Augment topology configuration"; 2232 uses l3tet:l3-te-topology-attributes; 2233 } 2235 augment "/nw-s:networks/nw-s:network/nw-s:node/" 2236 + "l3t-s:l3-node-attributes" { 2237 when "../../nw-s:network-types/l3t-s:l3-unicast-topology/" 2238 + "l3tet-s:l3-te" { 2239 description 2240 "Augment only for L3 TE topology"; 2241 } 2242 description 2243 "Augment node configuration"; 2244 uses l3tet:l3-te-node-attributes; 2245 } 2247 augment "/nw-s:networks/nw-s:network/nw-s:node/" 2248 + "nt-s:termination-point/" 2249 + "l3t-s:l3-termination-point-attributes" { 2250 when "../../../nw-s:network-types/l3t-s:l3-unicast-topology/" 2251 + "l3tet-s:l3-te" { 2252 description 2253 "Augment only for L3 TE topology"; 2254 } 2255 description 2256 "Augment termination point configuration"; 2257 uses l3tet:l3-te-tp-attributes; 2258 } 2260 augment "/nw-s:networks/nw-s:network/nt-s:link/" 2261 + "l3t-s:l3-link-attributes" { 2262 when "../../nw-s:network-types/l3t-s:l3-unicast-topology/" 2263 + "l3tet-s:l3-te" { 2264 description 2265 "Augment only for L3 TE topology"; 2266 } 2267 description 2268 "Augment link configuration"; 2269 uses l3tet:l3-te-link-attributes; 2270 } 2271 } 2272 2274 A.2. Packet Switching TE Topology State Module 2276 file "ietf-te-topology-packet-state@2019-06-28.yang" 2277 module ietf-te-topology-packet-state { 2278 yang-version 1.1; 2279 namespace 2280 "urn:ietf:params:xml:ns:yang:ietf-te-topology-packet-state"; 2282 prefix "tet-pkt-s"; 2284 import ietf-te-topology-packet { 2285 prefix "tet-pkt"; 2286 } 2288 import ietf-network-state { 2289 prefix "nw-s"; 2290 reference 2291 "RFC 8345: A YANG Data Model for Network Topologies"; 2292 } 2294 import ietf-network-topology-state { 2295 prefix "nt-s"; 2296 reference 2297 "RFC 8345: A YANG Data Model for Network Topologies"; 2298 } 2300 import ietf-te-topology-state { 2301 prefix "tet-s"; 2302 reference 2303 "I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic 2304 Engineering (TE) Topologies"; 2305 } 2307 import ietf-te-types { 2308 prefix "te-types"; 2309 reference 2310 "I-D.ietf-teas-yang-te-types: Traffic Engineering Common YANG 2311 Types"; 2312 } 2314 import ietf-te-packet-types { 2315 prefix "te-packet-types"; 2316 reference 2317 "I-D.ietf-teas-yang-te-types: Traffic Engineering Common YANG 2318 Types"; 2319 } 2321 organization 2322 "Traffic Engineering Architecture and Signaling (TEAS) 2323 Working Group"; 2325 contact 2326 "WG Web: 2327 WG List: 2329 Editor: Xufeng Liu 2330 2332 Editor: Igor Bryskin 2333 2335 Editor: Vishnu Pavan Beeram 2336 2338 Editor: Tarek Saad 2339 2341 Editor: Himanshu Shah 2342 2344 Editor: Oscar Gonzalez De Dios 2345 "; 2347 description 2348 "YANG data model for representing operational state information 2349 of PSC (Packet Switching) TE Topologies, when NMDA is not 2350 supported. 2352 Copyright (c) 2018 IETF Trust and the persons identified as 2353 authors of the code. All rights reserved. 2355 Redistribution and use in source and binary forms, with or 2356 without modification, is permitted pursuant to, and subject to 2357 the license terms contained in, the Simplified BSD License set 2358 forth in Section 4.c of the IETF Trust's Legal Provisions 2359 Relating to IETF Documents 2360 (http://trustee.ietf.org/license-info). 2362 This version of this YANG module is part of RFC XXXX; see the 2363 RFC itself for full legal notices."; 2365 revision 2019-06-28 { 2366 description 2367 "Initial revision"; 2368 reference 2369 "RFC XXXX: YANG Data Model for Layer 3 TE Topologies"; 2370 } 2372 /* 2373 * Augmentations 2374 */ 2375 /* Augmentations to connectivity-matrix */ 2376 augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/" 2377 + "tet-s:te-node-attributes/tet-s:connectivity-matrices" { 2378 description 2379 "Parameters for PSC (Packet Switching) TE topology."; 2380 uses te-packet-types:performance-metrics-attributes-packet { 2381 if-feature tet-pkt:te-performance-metric; 2382 } 2383 uses 2384 te-packet-types:performance-metrics-throttle-container-packet { 2385 if-feature tet-pkt:te-performance-metric; 2386 } 2387 } 2389 augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/" 2390 + "tet-s:te-node-attributes/tet-s:connectivity-matrices/" 2391 + "tet-s:connectivity-matrix" { 2392 description 2393 "Parameters for PSC TE topology."; 2394 uses te-packet-types:performance-metrics-attributes-packet { 2395 if-feature tet-pkt:te-performance-metric; 2396 } 2397 uses 2398 te-packet-types:performance-metrics-throttle-container-packet { 2399 if-feature tet-pkt:te-performance-metric; 2400 } 2401 } 2403 augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/" 2404 + "tet-s:information-source-entry/" 2405 + "tet-s:connectivity-matrices" { 2406 description 2407 "Parameters for PSC TE topology."; 2408 uses te-packet-types:performance-metrics-attributes-packet { 2409 if-feature tet-pkt:te-performance-metric; 2410 } 2411 uses 2412 te-packet-types:performance-metrics-throttle-container-packet { 2413 if-feature tet-pkt:te-performance-metric; 2414 } 2415 } 2417 augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/" 2418 + "tet-s:information-source-entry/" 2419 + "tet-s:connectivity-matrices/" 2420 + "tet-s:connectivity-matrix" { 2421 description 2422 "Parameters for PSC TE topology."; 2423 uses te-packet-types:performance-metrics-attributes-packet { 2424 if-feature tet-pkt:te-performance-metric; 2425 } 2426 uses 2427 te-packet-types:performance-metrics-throttle-container-packet { 2428 if-feature tet-pkt:te-performance-metric; 2429 } 2430 } 2432 /* Augmentations to tunnel-termination-point */ 2433 augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/" 2434 + "tet-s:tunnel-termination-point/" 2435 + "tet-s:local-link-connectivities" { 2436 description 2437 "Parameters for PSC TE topology."; 2438 uses te-packet-types:performance-metrics-attributes-packet { 2439 if-feature tet-pkt:te-performance-metric; 2440 } 2441 uses 2442 te-packet-types:performance-metrics-throttle-container-packet { 2443 if-feature tet-pkt:te-performance-metric; 2444 } 2445 } 2447 augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/" 2448 + "tet-s:tunnel-termination-point/" 2449 + "tet-s:local-link-connectivities/" 2450 + "tet-s:local-link-connectivity" { 2451 description 2452 "Parameters for PSC TE topology."; 2454 uses te-packet-types:performance-metrics-attributes-packet { 2455 if-feature tet-pkt:te-performance-metric; 2456 } 2457 uses 2458 te-packet-types:performance-metrics-throttle-container-packet { 2459 if-feature tet-pkt:te-performance-metric; 2460 } 2461 } 2463 /* Augmentations to te-link-attributes */ 2464 augment "/nw-s:networks/tet-s:te/tet-s:templates/" 2465 + "tet-s:link-template/tet-s:te-link-attributes" { 2466 when "tet-s:interface-switching-capability " 2467 + "[tet-s:switching-capability = 'te-types:switching-psc1']" { 2468 description 2469 "Valid only for PSC"; 2470 } 2471 description 2472 "Parameters for PSC TE topology."; 2473 uses te-packet-types:performance-metrics-attributes-packet { 2474 if-feature tet-pkt:te-performance-metric; 2475 } 2476 uses 2477 te-packet-types:performance-metrics-throttle-container-packet { 2478 if-feature tet-pkt:te-performance-metric; 2479 } 2480 } 2482 augment "/nw-s:networks/nw-s:network/nt-s:link/tet-s:te/" 2483 + "tet-s:te-link-attributes" { 2484 when "tet-s:interface-switching-capability " 2485 + "[tet-s:switching-capability = 'te-types:switching-psc1']" { 2486 description "Valid only for PSC"; 2487 } 2488 description 2489 "Parameters for PSC TE topology."; 2490 uses te-packet-types:performance-metrics-attributes-packet { 2491 if-feature tet-pkt:te-performance-metric; 2492 } 2493 uses 2494 te-packet-types:performance-metrics-throttle-container-packet { 2495 if-feature tet-pkt:te-performance-metric; 2496 } 2497 } 2499 augment "/nw-s:networks/nw-s:network/nt-s:link/tet-s:te/" 2500 + "tet-s:information-source-entry" { 2501 when "tet-s:interface-switching-capability " 2502 + "[tet-s:switching-capability = 'te-types:switching-psc1']" { 2503 description "Valid only for PSC"; 2504 } 2505 description 2506 "Parameters for PSC TE topology."; 2507 uses te-packet-types:performance-metrics-attributes-packet { 2508 if-feature tet-pkt:te-performance-metric; 2509 } 2510 uses 2511 te-packet-types:performance-metrics-throttle-container-packet { 2512 if-feature tet-pkt:te-performance-metric; 2513 } 2514 } 2516 /* Augmentations to interface-switching-capability */ 2517 augment "/nw-s:networks/tet-s:te/tet-s:templates/" 2518 + "tet-s:link-template/tet-s:te-link-attributes/" 2519 + "tet-s:interface-switching-capability" { 2520 when "tet-s:switching-capability = 'te-types:switching-psc1' " { 2521 description "Valid only for PSC"; 2522 } 2523 description 2524 "Parameters for PSC TE topology."; 2525 uses tet-pkt:packet-switch-capable-container; 2526 } 2528 augment "/nw-s:networks/nw-s:network/nt-s:link/tet-s:te/" 2529 + "tet-s:te-link-attributes/" 2530 + "tet-s:interface-switching-capability" { 2531 when "tet-s:switching-capability = 'te-types:switching-psc1' " { 2532 description "Valid only for PSC"; 2533 } 2534 description 2535 "Parameters for PSC TE topology."; 2536 uses tet-pkt:packet-switch-capable-container; 2537 } 2539 augment "/nw-s:networks/nw-s:network/nt-s:link/tet-s:te/" 2540 + "tet-s:information-source-entry/" 2541 + "tet-s:interface-switching-capability" { 2542 when "tet-s:switching-capability = 'te-types:switching-psc1' " { 2543 description 2544 "Valid only for PSC"; 2545 } 2546 description 2547 "Parameters for PSC TE topology."; 2548 uses tet-pkt:packet-switch-capable-container; 2549 } 2551 } 2552 2554 Appendix B. Data Tree Example 2556 This section contains an example of an instance data tree in the JSON 2557 encoding [RFC7951]. The example instantiates "ietf-l3-te-topology" 2558 for the topology that is depicted in the following diagram. 2560 +------------+ +------------+ 2561 | D1 | | D2 | 2562 /-\ /-\ (TE) /-\ /-\ 2563 | | 1-0-1 | |---------------->| | 2-1-1 | | 2564 | | 1-2-1 | |<----------------| | 2-0-1 | | 2565 \-/ 1-3-1 \-/ (TE) \-/ 2-3-1 \-/ 2566 | /----\ | | /----\ | 2567 +---| |---+ +---| |---+ 2568 \----/ \----/ 2569 A | A | 2570 (TE)| |(TE) (Non-TE)| |(Non-TE) 2571 | | | | 2572 | | +------------+ | | 2573 | | | D3 | | | 2574 | | /-\ /-\ | | 2575 | +----->| | 3-1-1 | |-------+ | 2576 +---------| | 3-2-1 | |<---------+ 2577 \-/ \-/ 2578 | | 2579 +------------+ 2581 The corresponding instance data tree is depicted below. Note that 2582 some lines have been wrapped to adhere to the 72-character line 2583 limitation of RFCs. 2585 { 2586 "ietf-network:networks": { 2587 "network": [ 2588 { 2589 "network-id":"example-topo-te", 2590 "network-types": { 2591 "ietf-te-topology:te-topology": { 2592 } 2593 }, 2594 "ietf-te-topology:te-topology-identifier": { 2595 "provider-id":200, 2596 "client-id":300, 2597 "topology-id":"example-topo-te" 2598 }, 2599 "ietf-te-topology:te": { 2600 }, 2601 "node": [ 2602 { 2603 "node-id":"D1", 2604 "ietf-te-topology:te-node-id":"2.0.1.1", 2605 "ietf-te-topology:te": { 2606 "te-node-attributes": { 2607 } 2608 }, 2609 "ietf-network-topology:termination-point": [ 2610 { 2611 "tp-id":"1-2-1", 2612 "ietf-te-topology:te-tp-id":10201, 2613 "ietf-te-topology:te": { 2614 "interface-switching-capability": [ 2615 { 2616 "switching-capability": 2617 "ietf-te-types:switching-psc1", 2618 "encoding": 2619 "ietf-te-types:lsp-encoding-ethernet" 2620 } 2621 ] 2622 } 2623 }, 2624 { 2625 "tp-id": "1-3-1", 2626 "ietf-te-topology:te-tp-id":10301, 2627 "ietf-te-topology:te": { 2628 "interface-switching-capability": [ 2629 { 2630 "switching-capability": 2631 "ietf-te-types:switching-psc1", 2632 "encoding": 2633 "ietf-te-types:lsp-encoding-ethernet" 2634 } 2635 ] 2636 } 2637 } 2638 ] 2639 }, 2640 { 2641 "node-id":"D2", 2642 "ietf-te-topology:te-node-id":"2.0.2.1", 2643 "ietf-te-topology:te": { 2644 "te-node-attributes": { 2645 } 2646 }, 2647 "ietf-network-topology:termination-point": [ 2648 { 2649 "tp-id":"2-1-1", 2650 "ietf-te-topology:te-tp-id":20101, 2651 "ietf-te-topology:te": { 2652 "interface-switching-capability": [ 2653 { 2654 "switching-capability": 2655 "ietf-te-types:switching-psc1", 2656 "encoding": 2657 "ietf-te-types:lsp-encoding-ethernet" 2658 } 2659 ] 2660 } 2661 } 2662 ] 2663 }, 2664 { 2665 "node-id":"D3", 2666 "ietf-te-topology:te-node-id":"2.0.3.1", 2667 "ietf-te-topology:te": { 2668 "te-node-attributes": { 2669 } 2670 }, 2671 "ietf-network-topology:termination-point": [ 2672 { 2673 "tp-id":"3-1-1", 2674 "ietf-te-topology:te-tp-id":30101, 2675 "ietf-te-topology:te": { 2676 "interface-switching-capability": [ 2677 { 2678 "switching-capability": 2679 "ietf-te-types:switching-psc1", 2680 "encoding": 2681 "ietf-te-types:lsp-encoding-ethernet" 2682 } 2683 ] 2684 } 2685 } 2686 ] 2687 } 2688 ], 2689 "ietf-network-topology:link": [ 2690 { 2691 "link-id":"D1,1-2-1,D2,2-1-1", 2692 "source": { 2693 "source-node":"D1", 2694 "source-tp":"1-2-1" 2695 }, 2696 "destination": { 2697 "dest-node":"D2", 2698 "dest-tp":"2-1-1" 2699 }, 2700 "ietf-te-topology:te": { 2701 "te-link-attributes": { 2702 "interface-switching-capability": [ 2703 { 2704 "switching-capability": 2705 "ietf-te-types:switching-psc1", 2706 "encoding":"ietf-te-types:lsp-encoding-ethernet" 2707 } 2708 ], 2709 "max-link-bandwidth": { 2710 "te-bandwidth": { 2711 "generic":"0x1p+18" 2712 } 2713 }, 2714 "te-default-metric":100 2715 } 2716 } 2717 }, 2718 { 2719 "link-id":"D2,2-1-1,D1,1-2-1", 2720 "source": { 2721 "source-node":"D2", 2722 "source-tp":"2-1-1" 2723 }, 2724 "destination": { 2725 "dest-node":"D1", 2726 "dest-tp":"1-2-1" 2727 }, 2728 "ietf-te-topology:te": { 2729 "te-link-attributes": { 2730 "interface-switching-capability": [ 2731 { 2732 "switching-capability": 2733 "ietf-te-types:switching-psc1", 2734 "encoding":"ietf-te-types:lsp-encoding-ethernet" 2735 } 2736 ], 2737 "max-link-bandwidth": { 2738 "te-bandwidth": { 2739 "generic":"0x1p+18" 2740 } 2741 }, 2742 "te-default-metric":100 2743 } 2744 } 2745 }, 2746 { 2747 "link-id":"D1,1-3-1,D3,3-1-1", 2748 "source": { 2749 "source-node":"D1", 2750 "source-tp":"1-3-1" 2751 }, 2752 "destination": { 2753 "dest-node":"D3", 2754 "dest-tp":"3-1-1" 2755 }, 2756 "ietf-te-topology:te": { 2757 "te-link-attributes": { 2758 "interface-switching-capability": [ 2759 { 2760 "switching-capability": 2761 "ietf-te-types:switching-psc1", 2762 "encoding":"ietf-te-types:lsp-encoding-ethernet" 2763 } 2764 ], 2765 "max-link-bandwidth": { 2766 "te-bandwidth": { 2767 "generic":"0x1p+18" 2768 } 2769 }, 2770 "te-default-metric":100 2771 } 2772 } 2773 }, 2774 { 2775 "link-id":"D3,3-1-1,D1,1-3-1", 2776 "source": { 2777 "source-node":"D3", 2778 "source-tp":"3-1-1" 2779 }, 2780 "destination": { 2781 "dest-node":"D1", 2782 "dest-tp":"1-3-1" 2783 }, 2784 "ietf-te-topology:te": { 2785 "te-link-attributes": { 2786 "interface-switching-capability": [ 2787 { 2788 "switching-capability": 2789 "ietf-te-types:switching-psc1", 2790 "encoding":"ietf-te-types:lsp-encoding-ethernet" 2791 } 2792 ], 2793 "max-link-bandwidth": { 2794 "te-bandwidth": { 2795 "generic":"0x1p+18" 2796 } 2797 }, 2798 "te-default-metric":100 2799 } 2800 } 2801 } 2802 ] 2803 }, 2804 { 2805 "network-id":"example-topo-l3-te", 2806 "network-types": { 2807 "ietf-l3-unicast-topology:l3-unicast-topology": { 2808 "ietf-l3-te-topology:l3-te": { 2809 } 2810 } 2811 }, 2812 "ietf-l3-unicast-topology:l3-topology-attributes": { 2813 "ietf-l3-te-topology:l3-te-topology-attributes": { 2814 "network-ref":"example-topo-te" 2815 } 2816 }, 2817 "node": [ 2818 { 2819 "node-id":"D1", 2820 "ietf-l3-unicast-topology:l3-node-attributes": { 2821 "router-id": [ 2822 "203.0.113.1" 2823 ], 2824 "prefix": [ 2825 { 2826 "prefix":"203.0.113.1/32" 2827 } 2828 ], 2829 "ietf-l3-te-topology:l3-te-node-attributes": { 2830 "node-ref":"D1", 2831 "network-ref":"example-topo-te" 2832 } 2833 }, 2834 "ietf-network-topology:termination-point": [ 2835 { 2836 "tp-id":"1-0-1", 2837 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 2838 "unnumbered-id":101 2839 } 2840 }, 2841 { 2842 "tp-id":"1-2-1", 2843 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 2844 "unnumbered-id":121, 2845 "ietf-l3-te-topology:l3-te-tp-attributes": { 2846 "network-ref":"example-topo-te", 2847 "tp-ref":"1-2-1" 2848 } 2849 } 2850 }, 2851 { 2852 "tp-id":"1-3-1", 2853 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 2854 "unnumbered-id":131, 2855 "ietf-l3-te-topology:l3-te-tp-attributes": { 2856 "network-ref":"example-topo-te", 2857 "tp-ref":"1-3-1" 2858 } 2859 } 2860 } 2861 ] 2862 }, 2863 { 2864 "node-id":"D2", 2865 "ietf-l3-unicast-topology:l3-node-attributes": { 2866 "router-id": [ 2867 "203.0.113.2" 2868 ], 2869 "prefix": [ 2870 { 2871 "prefix":"203.0.113.2/32" 2872 } 2873 ], 2874 "ietf-l3-te-topology:l3-te-node-attributes": { 2875 "node-ref":"D2", 2876 "network-ref":"example-topo-te" 2877 } 2878 }, 2879 "ietf-network-topology:termination-point": [ 2880 { 2881 "tp-id":"2-0-1", 2882 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 2883 "unnumbered-id":201 2884 } 2885 }, 2886 { 2887 "tp-id":"2-1-1", 2888 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 2889 "unnumbered-id":211, 2890 "ietf-l3-te-topology:l3-te-tp-attributes": { 2891 "tp-ref":"2-1-1", 2892 "network-ref":"example-topo-te" 2893 } 2894 } 2895 }, 2896 { 2897 "tp-id":"2-3-1", 2898 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 2899 "unnumbered-id":231 2900 } 2901 } 2902 ] 2903 }, 2904 { 2905 "node-id":"D3", 2906 "ietf-l3-unicast-topology:l3-node-attributes": { 2907 "router-id": [ 2908 "203.0.113.3" 2909 ], 2910 "prefix": [ 2911 { 2912 "prefix":"203.0.113.3/32" 2913 } 2914 ], 2915 "ietf-l3-te-topology:l3-te-node-attributes": { 2916 "node-ref":"D3", 2917 "network-ref":"example-topo-te" 2918 } 2919 }, 2920 "ietf-network-topology:termination-point": [ 2921 { 2922 "tp-id":"3-0-1", 2923 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 2924 "unnumbered-id":301 2925 } 2926 }, 2927 { 2928 "tp-id":"3-1-1", 2929 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 2930 "unnumbered-id":311, 2931 "ietf-l3-te-topology:l3-te-tp-attributes": { 2932 "tp-ref":"3-1-1", 2933 "network-ref":"example-topo-te" 2934 } 2935 } 2936 }, 2937 { 2938 "tp-id":"3-2-1", 2939 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 2940 "unnumbered-id":321 2941 } 2942 } 2943 ] 2944 } 2945 ], 2946 "ietf-network-topology:link": [ 2947 { 2948 "link-id":"D1,1-2-1,D2,2-1-1", 2949 "source": { 2950 "source-node":"D1", 2951 "source-tp":"1-2-1" 2952 }, 2953 "destination": { 2954 "dest-node":"D2", 2955 "dest-tp":"2-1-1" 2956 }, 2957 "ietf-l3-unicast-topology:l3-link-attributes": { 2958 "metric1":"100", 2959 "ietf-l3-te-topology:l3-te-link-attributes": { 2960 "link-ref":"D1,1-2-1,D2,2-1-1", 2961 "network-ref":"example-topo-te" 2962 } 2963 } 2964 }, 2965 { 2966 "link-id":"D2,2-1-1,D1,1-2-1", 2967 "source": { 2968 "source-node":"D2", 2969 "source-tp":"2-1-1" 2970 }, 2971 "destination": { 2972 "dest-node":"D1", 2973 "dest-tp":"1-2-1" 2974 }, 2975 "ietf-l3-unicast-topology:l3-link-attributes": { 2976 "metric1":"100", 2977 "ietf-l3-te-topology:l3-te-link-attributes": { 2978 "link-ref":"D2,2-1-1,D1,1-2-1", 2979 "network-ref":"example-topo-te" 2980 } 2981 } 2982 }, 2983 { 2984 "link-id":"D1,1-3-1,D3,3-1-1", 2985 "source": { 2986 "source-node":"D1", 2987 "source-tp":"1-3-1" 2988 }, 2989 "destination": { 2990 "dest-node":"D3", 2991 "dest-tp":"3-1-1" 2992 }, 2993 "ietf-l3-unicast-topology:l3-link-attributes": { 2994 "metric1":"100", 2995 "ietf-l3-te-topology:l3-te-link-attributes": { 2996 "link-ref":"D1,1-3-1,D3,3-1-1", 2997 "network-ref":"example-topo-te" 2998 } 2999 } 3000 }, 3001 { 3002 "link-id":"D3,3-1-1,D1,1-3-1", 3003 "source": { 3004 "source-node":"D3", 3005 "source-tp":"3-1-1" 3006 }, 3007 "destination": { 3008 "dest-node":"D1", 3009 "dest-tp":"1-3-1" 3010 }, 3011 "ietf-l3-unicast-topology:l3-link-attributes": { 3012 "metric1":"100", 3013 "ietf-l3-te-topology:l3-te-link-attributes": { 3014 "link-ref":"D3,3-1-1,D1,1-3-1", 3015 "network-ref":"example-topo-te" 3016 } 3017 } 3018 }, 3019 { 3020 "link-id":"D2,2-3-1,D3,3-2-1", 3021 "source": { 3022 "source-node":"D2", 3023 "source-tp":"2-3-1" 3024 }, 3025 "destination": { 3026 "dest-node":"D3", 3027 "dest-tp":"3-2-1" 3028 }, 3029 "ietf-l3-unicast-topology:l3-link-attributes": { 3030 "metric1":"100" 3031 } 3032 }, 3033 { 3034 "link-id":"D3,3-2-1,D2,2-3-1", 3035 "source": { 3036 "source-node":"D3", 3037 "source-tp":"3-2-1" 3038 }, 3039 "destination": { 3040 "dest-node":"D2", 3041 "dest-tp":"2-3-1" 3042 }, 3043 "ietf-l3-unicast-topology:l3-link-attributes": { 3044 "metric1":"100" 3045 } 3046 } 3047 ] 3048 } 3049 ] 3050 } 3051 } 3053 Authors' Addresses 3055 Xufeng Liu 3056 Volta Networks 3058 EMail: xufeng.liu.ietf@gmail.com 3060 Igor Bryskin 3061 Futurewei 3063 EMail: igor.bryskin@futurewei.com 3065 Vishnu Pavan Beeram 3066 Juniper Networks 3068 EMail: vbeeram@juniper.net 3069 Tarek Saad 3070 Juniper Networks 3072 EMail: tsaad@juniper.net 3074 Himanshu Shah 3075 Ciena 3077 EMail: hshah@ciena.com 3079 Oscar Gonzalez de Dios 3080 Telefonica 3082 EMail: oscar.gonzalezdedios@telefonica.com