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