idnits 2.17.1 draft-ietf-teas-yang-sr-te-topo-13.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 == Line 289 has weird spacing: '...r-bound uin...' == Line 290 has weird spacing: '...r-bound uin...' == Line 311 has weird spacing: '...r-bound uin...' == Line 312 has weird spacing: '...r-bound uin...' == Line 314 has weird spacing: '...r-bound uin...' == (7 more instances...) -- The document date (March 1, 2022) is 779 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-16) exists of draft-ietf-teas-yang-l3-te-topo-12 -- Obsolete informational reference (is this intentional?): RFC 7752 (Obsoleted by RFC 9552) Summary: 0 errors (**), 0 flaws (~~), 8 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group X. Liu 3 Internet-Draft IBM Corporation 4 Intended status: Standards Track I. Bryskin 5 Expires: September 2, 2022 Individual 6 V. Beeram 7 T. Saad 8 Juniper Networks 9 H. Shah 10 Ciena 11 S. Litkowski 12 Cisco 13 March 1, 2022 15 YANG Data Model for SR and SR TE Topologies on MPLS Data Plane 16 draft-ietf-teas-yang-sr-te-topo-13 18 Abstract 20 This document defines a YANG data model for Segment Routing (SR) 21 topology and Segment Routing (SR) traffic engineering (TE) topology, 22 using MPLS data plane. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at https://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on September 2, 2022. 41 Copyright Notice 43 Copyright (c) 2022 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (https://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 59 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 60 1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3 61 1.3. Prefixes in Data Node Names . . . . . . . . . . . . . . . 3 62 2. Modeling Considerations . . . . . . . . . . . . . . . . . . . 4 63 2.1. Segment Routing (SR) MPLS Topology . . . . . . . . . . . 4 64 2.2. Segment Routing (SR) MPLS TE Topology . . . . . . . . . . 4 65 2.3. Relations to ietf-segment-routing . . . . . . . . . . . . 7 66 2.4. Topology Type Modeling . . . . . . . . . . . . . . . . . 7 67 2.5. Topology Attributes . . . . . . . . . . . . . . . . . . . 7 68 2.6. Node Attributes . . . . . . . . . . . . . . . . . . . . . 7 69 2.7. Link Attributes . . . . . . . . . . . . . . . . . . . . . 9 70 3. Model Structure . . . . . . . . . . . . . . . . . . . . . . . 10 71 4. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 11 72 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 73 6. Security Considerations . . . . . . . . . . . . . . . . . . . 21 74 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 23 75 7.1. Normative References . . . . . . . . . . . . . . . . . . 23 76 7.2. Informative References . . . . . . . . . . . . . . . . . 25 77 Appendix A. Companion YANG Model for Non-NMDA Compliant 78 Implementations . . . . . . . . . . . . . . . . . . 26 79 A.1. SR MPLS Topology State Module . . . . . . . . . . . . . . 26 80 Appendix B. Data Tree Example . . . . . . . . . . . . . . . . . 29 81 B.1. SR MPLS Topology with TE Not Enabled . . . . . . . . . . 30 82 B.2. SR MPLS Topology with TE Enabled . . . . . . . . . . . . 37 83 Appendix C. Contributors . . . . . . . . . . . . . . . . . . . . 52 84 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 52 86 1. Introduction 88 This document defines a YANG [RFC7950] data model for describing the 89 presentations of Segment Routing (SR) topology and Segment Routing 90 (SR) traffic engineering (TE) topology. The version of the model 91 limits the transport type to an MPLS dataplane. 93 1.1. Terminology 95 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 96 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 97 "OPTIONAL" in this document are to be interpreted as described in BCP 98 14 [RFC2119] [RFC8174] when, and only when, they appear in all 99 capitals, as shown here. 101 The following terms are defined in [RFC7950] and are not redefined 102 here: 104 o augment 106 o data model 108 o data node 110 1.2. Tree Diagrams 112 Tree diagrams used in this document follow the notation defined in 113 [RFC8340]. 115 1.3. Prefixes in Data Node Names 117 In this document, names of data nodes, actions, and other data model 118 objects are often used without a prefix, as long as it is clear from 119 the context in which YANG module each name is defined. Otherwise, 120 names are prefixed using the standard prefix associated with the 121 corresponding YANG module, as shown in Table 1. 123 +--------+--------------------------+-------------------------------+ 124 | Prefix | YANG module | Reference | 125 +--------+--------------------------+-------------------------------+ 126 | nw | ietf-network | [RFC8345] | 127 | nt | ietf-network-topology | [RFC8345] | 128 | l3t | ietf-l3-unicast-topology | [RFC8346] | 129 | sr-cmn | ietf-segment-routing- | [RFC9020] | 130 | | common | | 131 | tet | ietf-te-topology | [RFC8795] | 132 | tet- | ietf-te-topology-packet | [I-D.ietf-teas-yang-l3-te-top | 133 | pkt | | o] | 134 +--------+--------------------------+-------------------------------+ 136 Table 1: Prefixes and Corresponding YANG Modules 138 2. Modeling Considerations 140 2.1. Segment Routing (SR) MPLS Topology 142 The Layer 3 network topology model is discussed in [RFC8346]. The 143 Segment Routing (SR) MPLS topology model proposed in this document 144 augments and uses the ietf-l3-unicast-topology module defined in 145 [RFC8346]. SR MPLS related attributes are covered in the ietf-sr- 146 mpls-topology module. 148 +------------------------------+ 149 | Layer 3 Network Topology | 150 | ietf-l3-unicast-topology | 151 +---------------^--------------+ 152 | 153 | 154 | 155 | 156 +------------^-----------+ 157 | SR MPLS Topology | 158 | ietf-sr-mpls-topology | 159 +------------------------+ 161 Figure 1: SR MPLS Topology Augmentation 163 2.2. Segment Routing (SR) MPLS TE Topology 165 A Segment Routing (SR) MPLS TE topology is an instance of SR MPLS 166 topology with TE enabled. In order to instantiate an SR MPLS TE 167 topology, the ietf-sr-mpls-topology module defined in this document 168 can be used together with the ietf-te-topology module defined in 169 [RFC8795] and the ietf-te-topology-packet module defined in 170 [I-D.ietf-teas-yang-l3-te-topo]. All these modules directly or 171 indirectly augment the ietf-network-topology module defind in 172 [RFC8345], as shown in Figure 2. 174 +---------------------------+ 175 | Network Topology | 176 | ietf-network-topology | 177 +-^-----------------------^-+ 178 / \ 179 / \ 180 / \ 181 / \ 182 +-------------^-------------+ +-------------^-------------+ 183 | Layer 3 Unicast Topology | | TE Topology | 184 | ietf-l3-unicast-topology | | ietf-te-topology | 185 +-------------^-------------+ +-------------^-------------+ 186 | | 187 | | 188 | | 189 | | 190 +-------------^-------------+ +-------------^-------------+ 191 | SR MPLS Topology | | TE Packet Topology | 192 | ietf-sr-mpls-topology | | ietf-te-topology-packet | 193 +---------------------------+ +---------------------------+ 195 Figure 2: SR TE Topology Instance Inheritance Relations 197 Figure 3 shows the data structure of an SR TE topology instance. 198 Because of the augmentation relationships shown in Figure 2, a data 199 instance of an SR MPLS TE topology contains the capabilities from all 200 these modules, so that the data includes the attributes from ietf- 201 network-topology, ietf-l3-unicast-topology, ietf-sr-mpls-topology, 202 ietf-te-topology, and ietf-te-topology-packet. 204 +--------------------------------------------------------+ 205 | ietf-network-topology: | 206 | network-id (key) | 207 | network-types: { | 208 | l3-unicast-topology: { | 209 | sr-mpls{} | 210 | } | 211 | te-topology: { | 212 | packet{} | 213 | } | 214 | } | 215 | | 216 +-----------------------------+--------------------------+ 217 | ietf-l3-unicast-topology: | ietf-te-topology: | 218 | | | 219 +-----------------------------+--------------------------+ 220 | ietf-sr-mpls-topology: | ietf-te-topology-packet: | 221 | | | 222 +-----------------------------+--------------------------+ 224 Figure 3: SR TE topology instance data structure 226 Each type of topology is indicated by a YANG presence container which 227 augments "network-types" as defined in [RFC8345].2 For the five types 228 of topologies above, the data representations are: 230 Base network topology [RFC8345]: 232 /nw:networks/nw:network/nw:network-types 234 Layer 3 Unicast Topology [RFC8346]: 236 /nw:networks/nw:network/nw:network-types/l3t:l3-unicast-topology 238 SR MPLS Topology (defined in this document): 240 /nw:networks/nw:network/nw:network-types/l3t:l3-unicast-topology/ 241 srmt:sr-mpls 243 TE Topology [RFC8795]: 245 /nw:networks/nw:network/nw:network-types/tet:te-topology 247 TE Packet Topology [I-D.ietf-teas-yang-l3-te-topo]: 249 /nw:networks/nw:network/nw:network-types/tet:te-topology/tet- 250 pkt:packet 252 2.3. Relations to ietf-segment-routing 254 [RFC9020] defines ietf-segment-routing that is a model intended to be 255 used on network elements to configure or operate segment routing; 256 ietf-sr-mpls-topology defined in this document is intended to be used 257 on a controller for the network-wide operations such as path 258 computation. 260 SR MPLS topology model shares many modeling constructs defined in 261 ietf-segment-routing. The module ietf-sr-mpls-topology uses the 262 types and groupings defined in ietf-segment-routing. 264 2.4. Topology Type Modeling 266 A new topology type is defined in this document, to indicate a 267 topology that is a Segment Routing (SR) topology on an MPLS 268 dataplane. 270 augment /nw:networks/nw:network/nw:network-types 271 /l3t:l3-unicast-topology: 272 +--rw sr-mpls! 274 Section 4.4.8 of RFC 8345 describes how network types are represented 275 using nested presence container. In this document, the presence 276 container sr-mpls is used for such a purpose. 278 2.5. Topology Attributes 280 The Segment Routing attributes with topology-wide impacts are modeled 281 by augmenting the container "l3-topology-attributes" in the L3 282 topology model [RFC8346]. SRGB (Segment Routing Global Block) is 283 covered in this augmentation. A SR domain is mapped to a topology in 284 this model. 286 augment /nw:networks/nw:network/l3t:l3-topology-attributes: 287 +--rw sr-mpls 288 +--rw srgb* [lower-bound upper-bound] 289 +--rw lower-bound uint32 290 +--rw upper-bound uint32 292 2.6. Node Attributes 294 The Segment Routing attributes within the node scope are modeled by 295 augmenting the sub tree /nw:networks/nw:network/nw:node/ in the L3 296 topology model [RFC8346]. 298 The SR attributes that have node-scope impact are modeled by 299 augmenting the container "l3-node-attributes" in the L3 topology 300 model, including the SR capabilities, SRGB (Segment Routing Global 301 Block), and SRLB (Segment Routing Local Block) specified on this 302 mode. This model also provides the information about how these SR 303 attributes are learned: 305 The presence container sr-mpls is used to indicate that SR MPLS is 306 enabled on this node when the container is present. 308 augment /nw:networks/nw:network/nw:node/l3t:l3-node-attributes: 309 +--rw sr-mpls! 310 +--rw srgb* [lower-bound upper-bound] 311 | +--rw lower-bound uint32 312 | +--rw upper-bound uint32 313 +--rw srlb* [lower-bound upper-bound] 314 | +--rw lower-bound uint32 315 | +--rw upper-bound uint32 316 +--rw msds {msd}? 317 | +--rw node-msd* [msd-type] 318 | +--rw msd-type identityref 319 | +--rw msd-value? uint8 320 +--ro information-source? enumeration 321 +--ro information-source-instance? string 322 +--ro information-source-state 323 +--ro credibility-preference? uint16 325 The SR attributes that are related to a IGP-Prefix segment are 326 modeled by augmenting the list entry "prefix" in the L3 topology 327 model: 329 augment /nw:networks/nw:network/nw:node/l3t:l3-node-attributes 330 /l3t:prefix: 331 +--rw sr-mpls! 332 +--rw sids 333 +--rw sid* [algorithm] 334 +--rw value-type? enumeration 335 +--rw start-sid uint32 336 +--rw range? uint32 337 +--rw algorithm identityref 338 +--rw last-hop-behavior? enumeration 339 | {sid-last-hop-behavior}? 340 +--rw is-local? boolean 341 +--rw is-node? boolean 342 +--ro is-readvertisment? boolean 344 2.7. Link Attributes 346 A link in the topology model connects the termination point on the 347 source node to the termination point on the destination node. When 348 such a link is instantiated, the bindings between the nodes and the 349 corresponding Adj-SIDs are formed, and the resulting FIB entries are 350 installed. 352 A link in the topology model is mapped to an SR Adjacency Segment, 353 formed by a pair of interfaces on two respective adjacent nodes. The 354 SR Adjacency Segment attributes are modeled by augmenting the link 355 attributes of the L3 topology model [RFC8346]. The modeling 356 structure is as follows: 358 augment /nw:networks/nw:network/nt:link/l3t:l3-link-attributes: 359 +--rw sr-mpls! 360 +--rw msds {msd}? 361 | +--rw link-msd* [msd-type] 362 | +--rw msd-type identityref 363 | +--rw msd-value? uint8 364 +--rw sids 365 | +--rw sid* [value-type sid] 366 | +--rw value-type enumeration 367 | +--rw sid uint32 368 | +--rw address-family? enumeration 369 | +--rw is-eligible-for-protection? boolean 370 | +--rw is-local? boolean 371 | +--rw is-part-of-set? boolean 372 | +--rw is-persistent? boolean 373 | +--rw is-on-lan? boolean 374 | +--rw weight? uint8 375 +--ro information-source? enumeration 376 +--ro information-source-instance? string 377 +--ro information-source-state 378 +--ro credibility-preference? uint16 380 IGPs [RFC8665] [RFC8666] [RFC8667] and BGP-LS [RFC7752] 381 [I-D.ietf-idr-bgp-ls-segment-routing-ext] can be supported by the 382 model, the leaf "information-source" is used to indicate where the 383 information is from. 385 The bundling capability of the Adjacency Segemnt is achieved by re- 386 using the existing modeling construct (i.e. "bundle-stack-level") 387 under /nw:networks/nw:network/nt:link/tet:te [RFC8795] 389 The presence container sr-mpls is used to indicate that SR SMPL is 390 enabled on this link when the container is present. 392 3. Model Structure 394 The model tree structure of the Segment Routing (SR) topology module 395 is as shown below: 397 module: ietf-sr-mpls-topology 398 augment /nw:networks/nw:network/nw:network-types 399 /l3t:l3-unicast-topology: 400 +--rw sr-mpls! 401 augment /nw:networks/nw:network/l3t:l3-topology-attributes: 402 +--rw sr-mpls 403 +--rw srgb* [lower-bound upper-bound] 404 +--rw lower-bound uint32 405 +--rw upper-bound uint32 406 augment /nw:networks/nw:network/nw:node/l3t:l3-node-attributes: 407 +--rw sr-mpls! 408 +--rw srgb* [lower-bound upper-bound] 409 | +--rw lower-bound uint32 410 | +--rw upper-bound uint32 411 +--rw srlb* [lower-bound upper-bound] 412 | +--rw lower-bound uint32 413 | +--rw upper-bound uint32 414 +--rw msds {msd}? 415 | +--rw node-msd* [msd-type] 416 | +--rw msd-type identityref 417 | +--rw msd-value? uint8 418 +--ro information-source? enumeration 419 +--ro information-source-instance? string 420 +--ro information-source-state 421 +--ro credibility-preference? uint16 422 augment /nw:networks/nw:network/nw:node/l3t:l3-node-attributes 423 /l3t:prefix: 424 +--rw sr-mpls! 425 +--rw sids 426 +--rw sid* [algorithm] 427 +--rw value-type? enumeration 428 +--rw start-sid uint32 429 +--rw range? uint32 430 +--rw algorithm identityref 431 +--rw last-hop-behavior? enumeration 432 | {sid-last-hop-behavior}? 433 +--rw is-local? boolean 434 +--rw is-node? boolean 435 +--ro is-readvertisment? boolean 436 augment /nw:networks/nw:network/nt:link/l3t:l3-link-attributes: 437 +--rw sr-mpls! 438 +--rw msds {msd}? 439 | +--rw link-msd* [msd-type] 440 | +--rw msd-type identityref 441 | +--rw msd-value? uint8 442 +--rw sids 443 | +--rw sid* [value-type sid] 444 | +--rw value-type enumeration 445 | +--rw sid uint32 446 | +--rw address-family? enumeration 447 | +--rw is-eligible-for-protection? boolean 448 | +--rw is-local? boolean 449 | +--rw is-part-of-set? boolean 450 | +--rw is-persistent? boolean 451 | +--rw is-on-lan? boolean 452 | +--rw weight? uint8 453 +--ro information-source? enumeration 454 +--ro information-source-instance? string 455 +--ro information-source-state 456 +--ro credibility-preference? uint16 458 4. YANG Module 460 This module references [RFC7752], [RFC8345], [RFC8346], [RFC8476], 461 [RFC8491], [RFC8665], [RFC8666], [RFC8667], [RFC8814], [RFC9020], and 462 [I-D.ietf-idr-bgp-ls-segment-routing-ext]. 464 file "ietf-sr-mpls-topology@2021-10-23.yang" 465 module ietf-sr-mpls-topology { 466 yang-version 1.1; 467 namespace "urn:ietf:params:xml:ns:yang:ietf-sr-mpls-topology"; 468 prefix "srmt"; 470 import ietf-network { 471 prefix "nw"; 472 reference "RFC 8345: A YANG Data Model for Network Topologies"; 473 } 474 import ietf-network-topology { 475 prefix "nt"; 476 reference "RFC 8345: A YANG Data Model for Network Topologies"; 477 } 478 import ietf-l3-unicast-topology { 479 prefix "l3t"; 480 reference "RFC 8346: A YANG Data Model for Layer 3 Topologies"; 481 } 482 import ietf-segment-routing-common { 483 prefix "sr-cmn"; 484 reference "RFC 9020: YANG Data Model for Segment Routing"; 486 } 488 organization 489 "IETF Traffic Engineering Architecture and Signaling (TEAS) 490 Working Group"; 492 contact 493 "WG Web: 494 WG List: 496 Editor: Xufeng Liu 497 499 Editor: Igor Bryskin 500 502 Editor: Vishnu Pavan Beeram 503 505 Editor: Tarek Saad 506 508 Editor: Himanshu Shah 509 511 Editor: Stephane Litkowski 512 "; 514 description 515 "YANG data model for representing and manipulating Segment 516 Routing Topologies on MPLS Data Plane. 518 Copyright (c) 2021 IETF Trust and the persons identified as 519 authors of the code. All rights reserved. 521 Redistribution and use in source and binary forms, with or 522 without modification, is permitted pursuant to, and subject to 523 the license terms contained in, the Simplified BSD License set 524 forth in Section 4.c of the IETF Trust's Legal Provisions 525 Relating to IETF Documents 526 (http://trustee.ietf.org/license-info). 528 This version of this YANG module is part of RFC XXXX; see the 529 RFC itself for full legal notices."; 531 revision 2021-10-23 { 532 description "Initial revision"; 533 reference 534 "RFC XXXX: YANG Data Model for SR and SR TE Topologies on MPLS 535 Data Plane"; 536 } 538 identity msd-base-type { 539 description 540 "Base identity for MSD Type"; 541 } 543 identity base-mpls-msd { 544 base msd-base-type; 545 description 546 "Base MPLS Imposition MSD."; 547 reference 548 "RFC 8491: Signaling Maximum SID Depth (MSD) Using IS-IS"; 549 } 551 identity erld-msd { 552 base msd-base-type; 553 description 554 "ERLD-MSD is defined to advertise the ERLD."; 555 reference 556 "RFC 8662: Entropy Label for Source Packet Routing in 557 Networking (SPRING) Tunnels"; 558 } 560 feature msd { 561 description 562 "Support of signaling MSD (Maximum SID Depth) in IGP."; 563 reference 564 "RFC 8476: Signaling Maximum SID Depth (MSD) Using OSPF. 565 RFC 8491: Signaling Maximum SID Depth (MSD) Using IS-IS. 566 RFC 8814: Signaling Maximum SID Depth (MSD) Using the Border 567 Gateway Protocol - Link State."; 568 } 570 grouping sr-mpls-topology-type { 571 description 572 "Identifies the SR-MPLS topology type. This type of network 573 topologies use Segment Routing (SR) technology over the MPLS 574 data plane"; 575 container sr-mpls { 576 presence "Indicates SR-MPLS topology"; 577 description 578 "Its presence identifies the SR MPLS topology type."; 579 } 580 } 581 augment "/nw:networks/nw:network/nw:network-types/" 582 + "l3t:l3-unicast-topology" { 583 description 584 "Defines the SR MPLS topology type."; 585 uses sr-mpls-topology-type; 586 } 588 augment "/nw:networks/nw:network/l3t:l3-topology-attributes" { 589 when "../nw:network-types/l3t:l3-unicast-topology/srmt:sr-mpls" { 590 description "Augment only for SR MPLS topology."; 591 } 592 description "Augment topology configuration"; 593 uses sr-mpls-topology-attributes; 594 } 596 augment "/nw:networks/nw:network/nw:node/l3t:l3-node-attributes" { 597 when "../../nw:network-types/l3t:l3-unicast-topology/" 598 + "srmt:sr-mpls" { 599 description "Augment only for SR MPLS topology."; 600 } 601 description "Augment node configuration."; 602 uses sr-node-attributes; 603 } 605 augment "/nw:networks/nw:network/nw:node/l3t:l3-node-attributes" 606 + "/l3t:prefix" { 607 when "../../../nw:network-types/l3t:l3-unicast-topology/" 608 + "srmt:sr-mpls" { 609 description "Augment only for SR MPLS topology."; 610 } 611 description "Augment node prefix."; 612 uses sr-node-prefix-attributes; 613 } 615 augment "/nw:networks/nw:network/nt:link/l3t:l3-link-attributes" { 616 when "../../nw:network-types/l3t:l3-unicast-topology/" 617 + "srmt:sr-mpls" { 618 description "Augment only for SR MPLS topology."; 619 } 620 description "Augment link configuration"; 621 uses sr-link-attributes; 622 } 624 grouping sr-mpls-topology-attributes { 625 description "SR MPLS topology scope attributes."; 626 container sr-mpls { 627 description 628 "Containing SR attributes."; 630 uses sr-cmn:srgb; 631 } // sr 632 } // sr-mpls-topology-attributes 634 grouping information-source-attributes { 635 description 636 "The attributes identifying source that has provided the 637 related information, and the source credibility."; 638 leaf information-source { 639 type enumeration { 640 enum "unknown" { 641 description "The source is unknown."; 642 } 643 enum "locally-configured" { 644 description "Configured entity."; 645 } 646 enum "ospfv2" { 647 description "OSPFv2."; 648 reference 649 "RFC 8665: OSPF Extensions for Segment Routing."; 650 } 651 enum "ospfv3" { 652 description "OSPFv3."; 653 reference 654 "RFC 8666: OSPFv3 Extensions for Segment Routing."; 655 } 656 enum "isis" { 657 description "ISIS."; 658 reference 659 "RFC 8667: IS-IS Extensions for Segment Routing."; 660 } 661 enum "bgp-ls" { 662 description "BGP-LS."; 663 reference 664 "RFC 7752: North-Bound Distribution of Link-State and 665 Traffic Engineering (TE) Information Using BGP. 666 I-D.ietf-idr-bgp-ls-segment-routing-ext: 667 BGP Link-State extensions for Segment Routing."; 668 } 669 enum "system-processed" { 670 description "System processed entity."; 671 } 672 enum "other" { 673 description "Other source."; 674 } 675 } 676 config false; 677 description 678 "Indicates the type of the information source."; 679 } 680 leaf information-source-instance { 681 type string; 682 config false; 683 description 684 "The name indicating the instance of the information 685 source."; 686 } 687 container information-source-state { 688 config false; 689 description 690 "The container contains state attributes related to 691 the information source."; 692 leaf credibility-preference { 693 type uint16; 694 description 695 "The preference value to calculate the traffic 696 engineering database credibility value used for 697 tie-break selection between different 698 information-source values. 699 Higher value is more preferable."; 700 } 701 } 702 } // information-source-attributes 704 grouping sr-node-attributes { 705 description "SR node scope attributes."; 706 container sr-mpls { 707 presence "Presence indicates SR is enabled."; 708 description 709 "Containing SR attributes."; 710 uses sr-cmn:srgb; 711 uses sr-cmn:srlb; 712 container msds { 713 if-feature "msd"; 714 description 715 "MSDs on the node."; 716 list node-msd { 717 key "msd-type"; 718 leaf msd-type { 719 type identityref { 720 base msd-base-type; 721 } 722 description 723 "MSD Type."; 724 } 725 leaf msd-value { 726 type uint8; 727 description 728 "MSD value, in the range of 0-255. Node MSD is the 729 lowest MSD supported by the node."; 730 } 731 description 732 "List of node MSDs. A node may have a list of MSD values, 733 with at most one value for each msd-type."; 734 reference 735 "RFC 8491: Signaling Maximum SID Depth (MSD) Using 736 IS-IS"; 737 } 738 } 739 // Operational state data 740 uses information-source-attributes; 741 } // sr 742 } // sr-node-attributes 744 grouping sr-node-prefix-attributes { 745 description "Containing SR attributes for a prefix."; 746 container sr-mpls { 747 presence "Presence indicates SR is enabled."; 748 description 749 "Containing SR attributes for a prefix."; 750 container sids { 751 description 752 "Containing Prefix SIDs assigned to this prefix."; 753 list sid { 754 key "algorithm"; 755 description 756 "A list of SIDs with their properties."; 757 uses sr-cmn:prefix-sid-attributes; 758 uses sr-cmn:last-hop-behavior; 759 leaf is-local { 760 type boolean; 761 default false; 762 description 763 "'true' if the SID is local."; 764 } 765 leaf is-node { 766 type boolean; 767 default false; 768 description 769 "'true' if the Prefix-SID refers to the router 770 identified by the prefix. Typically, the leaf 771 'is-node' (N-Flag) is set on Prefix-SIDs attached to a 772 router loopback address."; 773 } 774 leaf is-readvertisment { 775 type boolean; 776 config false; 777 description 778 "'true' if the prefix to which this Prefix-SID is 779 attached, has been propagated by the router from 780 another topology by redistribution."; 781 reference 782 "RFC 8667: IS-IS Extensions for Segment Routing. 783 Sec 2.1."; 784 } 785 } 786 } 787 } // sr 788 } // sr-node-prefix-attributes 790 grouping sr-link-attributes { 791 description "SR link scope attributes"; 792 container sr-mpls { 793 presence "Presence indicates SR is enabled."; 794 description 795 "Containing SR attributes."; 797 container msds { 798 if-feature "msd"; 799 description 800 "MSDs on the link."; 801 list link-msd { 802 key "msd-type"; 803 leaf msd-type { 804 type identityref { 805 base msd-base-type; 806 } 807 description 808 "MSD Type."; 809 } 810 leaf msd-value { 811 type uint8; 812 description 813 "MSD value, in the range of 0-255."; 814 } 815 description 816 "List of link MSDs. A link may have a list of MSD values, 817 with at most one value for each msd-type."; 818 reference 819 "RFC 8491: Signaling Maximum SID Depth (MSD) Using 820 IS-IS"; 821 } 823 } 824 container sids { 825 description 826 "Containing Adjacency SIDs assigned to this link."; 827 list sid { 828 key "value-type sid"; 829 description 830 "A list of SIDs with their properties."; 831 uses sr-cmn:sid-value-type; 832 leaf sid { 833 type uint32; 834 mandatory true; 835 description 836 "Adjacency SID, which can be either IGP-Adjacency SID 837 or BGP PeerAdj SID, depending on the context."; 838 } 839 leaf address-family { 840 type enumeration { 841 enum "ipv4" { 842 description 843 "The Adj-SID refers to an adjacency with outgoing 844 IPv4 encapsulation."; 845 } 846 enum "ipv6" { 847 description 848 "The Adj-SID refers to an adjacency with outgoing 849 IPv6 encapsulation."; 850 } 851 } 852 default "ipv4"; 853 description 854 "This leaf defines the F-Flag (Address-Family flag) of 855 the SID."; 856 } 857 leaf is-eligible-for-protection { 858 type boolean; 859 default false; 860 description 861 "'true' if the SID is is eligible for protection."; 862 reference 863 "RFC 8402: Segment Routing Architecture. Sec. 3.4."; 864 } 865 leaf is-local { 866 type boolean; 867 default false; 868 description 869 "'true' if the SID is local."; 870 } 871 leaf is-part-of-set { 872 type boolean; 873 default false; 874 description 875 "'true' if the SID is part of a set."; 876 } 877 leaf is-persistent { 878 type boolean; 879 default true; 880 description 881 "'true' if the SID is persistently allocated."; 882 } 883 leaf is-on-lan { 884 type boolean; 885 default false; 886 description 887 "'true' if on a lan."; 888 } 889 leaf weight { 890 type uint8; 891 description 892 "The value represents the weight of the SID for the 893 purpose of load balancing. The use of the weight 894 is defined in RFC 8402."; 895 reference 896 "RFC 8402: Segment Routing Architecture. Sec. 3.4."; 897 } 898 } 899 } 900 uses information-source-attributes; 901 } // sr 902 } // sr-tp-attributes 903 } 904 906 5. IANA Considerations 908 RFC Ed.: In this section, replace all occurrences of 'XXXX' with the 909 actual RFC number (and remove this note). 911 This document registers the following namespace URIs in the IETF XML 912 registry [RFC3688]: 914 -------------------------------------------------------------------- 915 URI: urn:ietf:params:xml:ns:yang:ietf-sr-mpls-topology 916 Registrant Contact: The IESG. 917 XML: N/A, the requested URI is an XML namespace. 918 -------------------------------------------------------------------- 920 -------------------------------------------------------------------- 921 URI: urn:ietf:params:xml:ns:yang:ietf-sr-mpls-topology-state 922 Registrant Contact: The IESG. 923 XML: N/A, the requested URI is an XML namespace. 924 -------------------------------------------------------------------- 926 This document registers the following YANG modules in the YANG Module 927 Names registry [RFC6020]: 929 -------------------------------------------------------------------- 930 name: ietf-sr-mpls-topology 931 namespace: urn:ietf:params:xml:ns:yang:ietf-sr-mpls-topology 932 prefix: srmt 933 reference: RFC XXXX 934 -------------------------------------------------------------------- 936 -------------------------------------------------------------------- 937 name: ietf-sr-mpls-topology-state 938 namespace: urn:ietf:params:xml:ns:yang:ietf-sr-mpls-topology-state 939 prefix: srmt-s 940 reference: RFC XXXX 941 -------------------------------------------------------------------- 943 6. Security Considerations 945 The YANG module specified in this document defines a schema for data 946 that is designed to be accessed via network management protocols such 947 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 948 is the secure transport layer, and the mandatory-to-implement secure 949 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 950 is HTTPS, and the mandatory-to-implement secure transport is TLS 951 [RFC8446]. 953 The Network Configuration Access Control Model (NACM) [RFC8341] 954 provides the means to restrict access for particular NETCONF or 955 RESTCONF users to a preconfigured subset of all available NETCONF or 956 RESTCONF protocol operations and content. 958 There are a number of data nodes defined in this YANG module that are 959 writable/creatable/deletable (i.e., config true, which is the 960 default). These data nodes may be considered sensitive or vulnerable 961 in some network environments. Write operations (e.g., edit-config) 962 to these data nodes without proper protection can have a negative 963 effect on network operations. These are the subtrees and data nodes 964 and their sensitivity/vulnerability: 966 /nw:networks/nw:network/nw:network-types/l3t:l3-unicast-topology/sr- 967 mpls 968 This subtree specifies the SR MPLS topology type. Modifying the 969 configurations can make SR MPLS topology type invalid and cause 970 interruption to all SR networks. 972 /nw:networks/nw:network/l3t:l3-topology-attributes/sr 973 This subtree specifies the topology-wide configurations, including 974 the SRGB (Segment Routing Global Block). Modifying the 975 configurations here can cause traffic disabled or rerouted in this 976 topology and the connected topologies. 978 /nw:networks/nw:network/nw:node/l3t:l3-node-attributes 979 This subtree specifies the SR configurations for nodes. Modifying 980 the configurations in this subtree can add, remove, or modify SR 981 nodes, causing traffic disabled or rerouted in the specified nodes 982 and the related TE topologies. 984 /nw:networks/nw:network/nt:link/l3t:l3-link-attributes/sr 985 This subtree specifies the configurations for SR Adjacency 986 Segments. Modifying the configurations in this subtree can add, 987 remove, or modify SR Adjacency Segments causing traffic disabled 988 or rerouted on the specified SR adjacencies, the related nodes, 989 and the related SR MPLS topologies. 991 Some of the readable data nodes in this YANG module may be considered 992 sensitive or vulnerable in some network environments. It is thus 993 important to control read access (e.g., via get, get-config, or 994 notification) to these data nodes. These are the subtrees and data 995 nodes and their sensitivity/vulnerability: 997 /nw:networks/nw:network/nw:network-types/l3t:l3-unicast-topology/sr- 998 mpls 999 Unauthorized access to this subtree can disclose the SR MPLS 1000 topology type. 1002 /nw:networks/nw:network/l3t:l3-topology-attributes/sr 1003 Unauthorized access to this subtree can disclose the topology-wide 1004 configurations, including the SRGB (Segment Routing Global Block). 1006 /nw:networks/nw:network/nw:node/l3t:l3-node-attributes 1007 Unauthorized access to this subtree can disclose the operational 1008 state information of the SR nodes. 1010 /nw:networks/nw:network/nt:link/l3t:l3-link-attributes/sr 1011 Unauthorized access to this subtree can disclose the operational 1012 state information of SR Adjacency Segments. 1014 7. References 1016 7.1. Normative References 1018 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1019 Requirement Levels", BCP 14, RFC 2119, 1020 DOI 10.17487/RFC2119, March 1997, 1021 . 1023 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1024 DOI 10.17487/RFC3688, January 2004, 1025 . 1027 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 1028 the Network Configuration Protocol (NETCONF)", RFC 6020, 1029 DOI 10.17487/RFC6020, October 2010, 1030 . 1032 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 1033 and A. Bierman, Ed., "Network Configuration Protocol 1034 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 1035 . 1037 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 1038 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 1039 . 1041 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 1042 RFC 7950, DOI 10.17487/RFC7950, August 2016, 1043 . 1045 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 1046 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 1047 . 1049 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 1050 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 1051 May 2017, . 1053 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 1054 Access Control Model", STD 91, RFC 8341, 1055 DOI 10.17487/RFC8341, March 2018, 1056 . 1058 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 1059 and R. Wilton, "Network Management Datastore Architecture 1060 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 1061 . 1063 [RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N., 1064 Ananthakrishnan, H., and X. Liu, "A YANG Data Model for 1065 Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March 1066 2018, . 1068 [RFC8346] Clemm, A., Medved, J., Varga, R., Liu, X., 1069 Ananthakrishnan, H., and N. Bahadur, "A YANG Data Model 1070 for Layer 3 Topologies", RFC 8346, DOI 10.17487/RFC8346, 1071 March 2018, . 1073 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 1074 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 1075 . 1077 [RFC8476] Tantsura, J., Chunduri, U., Aldrin, S., and P. Psenak, 1078 "Signaling Maximum SID Depth (MSD) Using OSPF", RFC 8476, 1079 DOI 10.17487/RFC8476, December 2018, 1080 . 1082 [RFC8491] Tantsura, J., Chunduri, U., Aldrin, S., and L. Ginsberg, 1083 "Signaling Maximum SID Depth (MSD) Using IS-IS", RFC 8491, 1084 DOI 10.17487/RFC8491, November 2018, 1085 . 1087 [RFC8814] Tantsura, J., Chunduri, U., Talaulikar, K., Mirsky, G., 1088 and N. Triantafillis, "Signaling Maximum SID Depth (MSD) 1089 Using the Border Gateway Protocol - Link State", RFC 8814, 1090 DOI 10.17487/RFC8814, August 2020, 1091 . 1093 [RFC9020] Litkowski, S., Qu, Y., Lindem, A., Sarkar, P., and J. 1094 Tantsura, "YANG Data Model for Segment Routing", RFC 9020, 1095 DOI 10.17487/RFC9020, May 2021, 1096 . 1098 [I-D.ietf-teas-yang-l3-te-topo] 1099 Liu, X., Bryskin, I., Beeram, V. P., Saad, T., Shah, H., 1100 and O. G. D. Dios, "YANG Data Model for Layer 3 TE 1101 Topologies", draft-ietf-teas-yang-l3-te-topo-12 (work in 1102 progress), October 2021. 1104 7.2. Informative References 1106 [RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and 1107 S. Ray, "North-Bound Distribution of Link-State and 1108 Traffic Engineering (TE) Information Using BGP", RFC 7752, 1109 DOI 10.17487/RFC7752, March 2016, 1110 . 1112 [RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG", 1113 RFC 7951, DOI 10.17487/RFC7951, August 2016, 1114 . 1116 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 1117 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 1118 . 1120 [RFC8665] Psenak, P., Ed., Previdi, S., Ed., Filsfils, C., Gredler, 1121 H., Shakir, R., Henderickx, W., and J. Tantsura, "OSPF 1122 Extensions for Segment Routing", RFC 8665, 1123 DOI 10.17487/RFC8665, December 2019, 1124 . 1126 [RFC8666] Psenak, P., Ed. and S. Previdi, Ed., "OSPFv3 Extensions 1127 for Segment Routing", RFC 8666, DOI 10.17487/RFC8666, 1128 December 2019, . 1130 [RFC8667] Previdi, S., Ed., Ginsberg, L., Ed., Filsfils, C., 1131 Bashandy, A., Gredler, H., and B. Decraene, "IS-IS 1132 Extensions for Segment Routing", RFC 8667, 1133 DOI 10.17487/RFC8667, December 2019, 1134 . 1136 [RFC8795] Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and 1137 O. Gonzalez de Dios, "YANG Data Model for Traffic 1138 Engineering (TE) Topologies", RFC 8795, 1139 DOI 10.17487/RFC8795, August 2020, 1140 . 1142 [I-D.ietf-idr-bgp-ls-segment-routing-ext] 1143 Previdi, S., Talaulikar, K., Filsfils, C., Gredler, H., 1144 and M. Chen, "Border Gateway Protocol - Link State (BGP- 1145 LS) Extensions for Segment Routing", draft-ietf-idr-bgp- 1146 ls-segment-routing-ext-18 (work in progress), April 2021. 1148 Appendix A. Companion YANG Model for Non-NMDA Compliant Implementations 1150 The YANG module ietf-sr-mpls-topology defined in this document is 1151 designed to be used in conjunction with implementations that support 1152 the Network Management Datastore Architecture (NMDA) defined in 1153 [RFC8342]. In order to allow implementations to use the model even 1154 in cases when NMDA is not supported, the following companion module, 1155 ietf-sr-mpls-topology-state, is defined as state model, which mirrors 1156 the module ietf-sr-mpls-topology defined earlier in this document. 1157 However, all data nodes in the companion module are non-configurable, 1158 to represent the applied configuration or the derived operational 1159 states. 1161 The companion module, ietf-sr-mpls-topology-state, is redundant and 1162 SHOULD NOT be supported by implementations that support NMDA. 1164 As the structure of the companion module mirrors that of the 1165 coorespinding NMDA model, the YANG tree of the companion module is 1166 not depicted separately. 1168 A.1. SR MPLS Topology State Module 1170 This module references [RFC8345] and [RFC8346]. 1172 file "ietf-sr-mpls-topology-state@2021-10-23.yang" 1173 module ietf-sr-mpls-topology-state { 1174 yang-version 1.1; 1175 namespace 1176 "urn:ietf:params:xml:ns:yang:ietf-sr-mpls-topology-state"; 1177 prefix "srmt-s"; 1179 import ietf-sr-mpls-topology { 1180 prefix "srmt"; 1181 } 1182 import ietf-network-state { 1183 prefix "nw-s"; 1184 reference "RFC 8345: A YANG Data Model for Network Topologies"; 1185 } 1186 import ietf-network-topology-state { 1187 prefix "nt-s"; 1188 reference "RFC 8345: A YANG Data Model for Network Topologies"; 1189 } 1190 import ietf-l3-unicast-topology-state { 1191 prefix "l3t-s"; 1192 reference "RFC 8346: A YANG Data Model for Layer 3 Topologies"; 1193 } 1194 import ietf-segment-routing-common { 1195 prefix "sr-cmn"; 1196 reference "RFC 9020: YANG Data Model for Segment Routing"; 1197 } 1199 organization 1200 "IETF Traffic Engineering Architecture and Signaling (TEAS) 1201 Working Group"; 1203 contact 1204 "WG Web: 1205 WG List: 1207 Editor: Xufeng Liu 1208 1210 Editor: Igor Bryskin 1211 1213 Editor: Vishnu Pavan Beeram 1214 1216 Editor: Tarek Saad 1217 1219 Editor: Himanshu Shah 1220 1222 Editor: Stephane Litkowski 1223 "; 1225 description 1226 "YANG data model for representing operational state information 1227 of Segment Routing Topologies on MPLS data plane, when NMDA is 1228 not supported. 1230 Copyright (c) 2021 IETF Trust and the persons identified as 1231 authors of the code. All rights reserved. 1233 Redistribution and use in source and binary forms, with or 1234 without modification, is permitted pursuant to, and subject to 1235 the license terms contained in, the Simplified BSD License set 1236 forth in Section 4.c of the IETF Trust's Legal Provisions 1237 Relating to IETF Documents 1238 (http://trustee.ietf.org/license-info). 1240 This version of this YANG module is part of RFC XXXX; see the 1241 RFC itself for full legal notices."; 1243 revision 2021-10-23 { 1244 description "Initial revision"; 1245 reference 1246 "RFC XXXX: YANG Data Model for SR and SR TE Topologies on MPLS 1247 Data Plane"; 1248 } 1250 augment "/nw-s:networks/nw-s:network/nw-s:network-types/" 1251 + "l3t-s:l3-unicast-topology" { 1252 description 1253 "Defines the SR MPLS topology type."; 1254 uses srmt:sr-mpls-topology-type; 1255 } 1257 augment "/nw-s:networks/nw-s:network/" 1258 + "l3t-s:l3-topology-attributes" { 1259 when "../nw-s:network-types/l3t-s:l3-unicast-topology/" 1260 + "srmt-s:sr-mpls" { 1261 description "Augment only for SR MPLS topology."; 1262 } 1263 description "Augment topology configuration"; 1264 uses srmt:sr-mpls-topology-attributes; 1265 } 1267 augment "/nw-s:networks/nw-s:network/nw-s:node/" 1268 + "l3t-s:l3-node-attributes" { 1269 when "../../nw-s:network-types/l3t-s:l3-unicast-topology/" 1270 + "srmt-s:sr-mpls" { 1271 description "Augment only for SR MPLS topology."; 1272 } 1273 description "Augment node configuration."; 1274 uses srmt:sr-node-attributes; 1275 } 1277 augment "/nw-s:networks/nw-s:network/nw-s:node/" 1278 + "l3t-s:l3-node-attributes/l3t-s:prefix" { 1279 when "../../../nw-s:network-types/l3t-s:l3-unicast-topology/" 1280 + "srmt-s:sr-mpls" { 1281 description "Augment only for SR MPLS topology."; 1282 } 1283 description "Augment node prefix."; 1284 uses srmt:sr-node-prefix-attributes; 1285 } 1287 augment "/nw-s:networks/nw-s:network/nt-s:link/" 1288 + "l3t-s:l3-link-attributes" { 1289 when "../../nw-s:network-types/l3t-s:l3-unicast-topology/" 1290 + "srmt-s:sr-mpls" { 1291 description "Augment only for SR MPLS topology."; 1292 } 1293 description "Augment link configuration"; 1294 uses srmt:sr-link-attributes; 1295 } 1297 grouping sr-mpls-topology-attributes { 1298 description "SR MPLS topology scope attributes."; 1299 container sr-mpls { 1300 description 1301 "Containing SR attributes."; 1302 uses sr-cmn:srgb; 1303 } // sr 1304 } // sr-mpls-topology-attributes 1305 } 1306 1308 Appendix B. Data Tree Example 1310 This section contains an example of an instance data tree in the JSON 1311 encoding [RFC7951]. The example instantiates "ietf-sr-mpls-topology" 1312 for the topology that is depicted in the following diagram. 1314 router-id: 203.0.113.1 router-id: 203.0.113.2 1315 +------------+ +------------+ 1316 | D1 | | D2 | 1317 /-\ /-\ /-\ /-\ 1318 | | 1-0-1 | |---------------->| | 2-1-1 | | 1319 | | 1-2-1 | |<----------------| | 2-0-1 | | 1320 \-/ 1-3-1 \-/ \-/ 2-3-1 \-/ 1321 | /----\ | | /----\ | 1322 +---| |---+ +---| |---+ 1323 \----/ \----/ 1324 A | A | 1325 | | | | 1326 | | router-id: 203.0.113.3 | | 1327 | | +------------+ | | 1328 | | | D3 | | | 1329 | | /-\ /-\ | | 1330 | +----->| | 3-1-1 | |-------+ | 1331 +---------| | 3-2-1 | |<---------+ 1332 \-/ \-/ 1333 | | 1334 +------------+ 1336 Figure 4: Example SR MPLS Topology 1338 The corresponding instance data tree is depicted below. Note that 1339 some lines have been wrapped to adhere to the 72-character line 1340 limitation of RFCs. 1342 B.1. SR MPLS Topology with TE Not Enabled 1344 { 1345 "ietf-network:networks": { 1346 "network": [ 1347 { 1348 "network-types": { 1349 "ietf-l3-unicast-topology:l3-unicast-topology": { 1350 "ietf-sr-mpls-topology:sr-mpls": {} 1351 } 1352 }, 1353 "network-id": "sr-mpls-topo-example", 1354 "ietf-l3-unicast-topology:l3-topology-attributes": { 1355 "ietf-sr-mpls-topology:sr-mpls": { 1356 "srgb": [ 1357 { 1358 "lower-bound": 16000, 1359 "upper-bound": 23999 1360 } 1362 ] 1363 } 1364 }, 1365 "node": [ 1366 { 1367 "node-id": "D1", 1368 "ietf-network-topology:termination-point": [ 1369 { 1370 "tp-id": "1-0-1", 1371 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 1372 "unnumbered-id": 101 1373 } 1374 }, 1375 { 1376 "tp-id": "1-2-1", 1377 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 1378 "unnumbered-id": 121 1379 } 1380 }, 1381 { 1382 "tp-id": "1-3-1", 1383 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 1384 "unnumbered-id": 131 1385 } 1386 } 1387 ], 1388 "ietf-l3-unicast-topology:l3-node-attributes": { 1389 "router-id": ["203.0.113.1"], 1390 "prefix": [ 1391 { 1392 "prefix": "203.0.113.1/32", 1393 "ietf-sr-mpls-topology:sr-mpls": { 1394 "sids": { 1395 "sid": [ 1396 { 1397 "algorithm": "prefix-sid-algorithm-shortest-path", 1398 "start-sid": 101, 1399 "range": 1, 1400 "is-local": false, 1401 "is-node": true 1402 } 1403 ] 1404 } 1405 } 1406 } 1407 ], 1408 "ietf-sr-mpls-topology:sr-mpls": { 1409 "srgb": [ 1410 { 1411 "lower-bound": 16000, 1412 "upper-bound": 23999 1413 } 1414 ], 1415 "srlb": [ 1416 { 1417 "lower-bound": 15000, 1418 "upper-bound": 15999 1419 } 1420 ] 1421 } 1422 } 1423 }, 1424 { 1425 "node-id": "D2", 1426 "ietf-network-topology:termination-point": [ 1427 { 1428 "tp-id": "2-0-1", 1429 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 1430 "unnumbered-id": 201 1431 } 1432 }, 1433 { 1434 "tp-id": "2-1-1", 1435 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 1436 "unnumbered-id": 211 1437 } 1438 }, 1439 { 1440 "tp-id": "2-3-1", 1441 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 1442 "unnumbered-id": 231 1443 } 1444 } 1445 ], 1446 "ietf-l3-unicast-topology:l3-node-attributes": { 1447 "router-id": ["203.0.113.2"], 1448 "prefix": [ 1449 { 1450 "prefix": "203.0.113.2/32", 1451 "ietf-sr-mpls-topology:sr-mpls": { 1452 "sids": { 1453 "sid": [ 1454 { 1455 "algorithm": "prefix-sid-algorithm-shortest-path", 1456 "start-sid": 102, 1457 "range": 1, 1458 "is-local": false, 1459 "is-node": true 1460 } 1461 ] 1462 } 1463 } 1464 } 1465 ], 1466 "ietf-sr-mpls-topology:sr-mpls": { 1467 "srgb": [ 1468 { 1469 "lower-bound": 16000, 1470 "upper-bound": 23999 1471 } 1472 ], 1473 "srlb": [ 1474 { 1475 "lower-bound": 15000, 1476 "upper-bound": 15999 1477 } 1478 ] 1479 } 1480 } 1481 }, 1482 { 1483 "node-id": "D3", 1484 "ietf-network-topology:termination-point": [ 1485 { 1486 "tp-id": "3-1-1", 1487 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 1488 "unnumbered-id": 311 1489 } 1490 }, 1491 { 1492 "tp-id": "3-2-1", 1493 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 1494 "unnumbered-id": 321 1495 } 1496 } 1497 ], 1498 "ietf-l3-unicast-topology:l3-node-attributes": { 1499 "router-id": ["203.0.113.3"], 1500 "prefix": [ 1501 { 1502 "prefix": "203.0.113.3/32", 1503 "ietf-sr-mpls-topology:sr-mpls": { 1504 "sids": { 1505 "sid": [ 1506 { 1507 "algorithm": "prefix-sid-algorithm-shortest-path", 1508 "start-sid": 103, 1509 "range": 1, 1510 "is-local": false, 1511 "is-node": true 1512 } 1513 ] 1514 } 1515 } 1516 } 1517 ], 1518 "ietf-sr-mpls-topology:sr-mpls": { 1519 "srgb": [ 1520 { 1521 "lower-bound": 16000, 1522 "upper-bound": 23999 1523 } 1524 ], 1525 "srlb": [ 1526 { 1527 "lower-bound": 15000, 1528 "upper-bound": 15999 1529 } 1530 ] 1531 } 1532 } 1533 } 1534 ], 1535 "ietf-network-topology:link": [ 1536 { 1537 "link-id": "D1,1-2-1,D2,2-1-1", 1538 "source": { 1539 "source-node": "D1", 1540 "source-tp": "1-2-1" 1541 }, 1542 "destination": { 1543 "dest-node": "D2", 1544 "dest-tp": "2-1-1" 1545 }, 1546 "ietf-l3-unicast-topology:l3-link-attributes": { 1547 "metric1": "100", 1548 "ietf-sr-mpls-topology:sr-mpls": { 1549 "sids": { 1550 "sid": [ 1551 { 1552 "value-type": "index", 1553 "sid": 121, 1554 "is-local": true 1555 } 1556 ] 1557 } 1558 } 1559 } 1560 }, 1561 { 1562 "link-id": "D2,2-1-1,D1,1-2-1", 1563 "source": { 1564 "source-node": "D2", 1565 "source-tp": "2-1-1" 1566 }, 1567 "destination": { 1568 "dest-node": "D1", 1569 "dest-tp": "1-2-1" 1570 }, 1571 "ietf-l3-unicast-topology:l3-link-attributes": { 1572 "metric1": "100", 1573 "ietf-sr-mpls-topology:sr-mpls": { 1574 "sids": { 1575 "sid": [ 1576 { 1577 "value-type": "index", 1578 "sid": 211, 1579 "is-local": true 1580 } 1581 ] 1582 } 1583 } 1584 } 1585 }, 1586 { 1587 "link-id": "D1,1-3-1,D3,3-1-1", 1588 "source": { 1589 "source-node": "D1", 1590 "source-tp": "1-3-1" 1591 }, 1592 "destination": { 1593 "dest-node": "D3", 1594 "dest-tp": "3-1-1" 1595 }, 1596 "ietf-l3-unicast-topology:l3-link-attributes": { 1597 "metric1": "100", 1598 "ietf-sr-mpls-topology:sr-mpls": { 1599 "sids": { 1600 "sid": [ 1601 { 1602 "value-type": "index", 1603 "sid": 131, 1604 "is-local": true 1605 } 1606 ] 1607 } 1608 } 1609 } 1610 }, 1611 { 1612 "link-id": "D3,3-1-1,D1,1-3-1", 1613 "source": { 1614 "source-node": "D3", 1615 "source-tp": "3-1-1" 1616 }, 1617 "destination": { 1618 "dest-node": "D1", 1619 "dest-tp": "1-3-1" 1620 }, 1621 "ietf-l3-unicast-topology:l3-link-attributes": { 1622 "metric1": "100", 1623 "ietf-sr-mpls-topology:sr-mpls": { 1624 "sids": { 1625 "sid": [ 1626 { 1627 "value-type": "index", 1628 "sid": 311, 1629 "is-local": true 1630 } 1631 ] 1632 } 1633 } 1634 } 1635 }, 1636 { 1637 "link-id": "D2,2-3-1,D3,3-2-1", 1638 "source": { 1639 "source-node": "D2", 1640 "source-tp": "2-3-1" 1641 }, 1642 "destination": { 1643 "dest-node": "D3", 1644 "dest-tp": "3-2-1" 1645 }, 1646 "ietf-l3-unicast-topology:l3-link-attributes": { 1647 "metric1": "100", 1648 "ietf-sr-mpls-topology:sr-mpls": { 1649 "sids": { 1650 "sid": [ 1651 { 1652 "value-type": "index", 1653 "sid": 231, 1654 "is-local": true 1655 } 1656 ] 1657 } 1658 } 1659 } 1660 }, 1661 { 1662 "link-id": "D3,3-2-1,D2,2-3-1", 1663 "source": { 1664 "source-node": "D3", 1665 "source-tp": "3-2-1" 1666 }, 1667 "destination": { 1668 "dest-node": "D2", 1669 "dest-tp": "2-3-1" 1670 }, 1671 "ietf-l3-unicast-topology:l3-link-attributes": { 1672 "metric1": "100", 1673 "ietf-sr-mpls-topology:sr-mpls": { 1674 "sids": { 1675 "sid": [ 1676 { 1677 "value-type": "index", 1678 "sid": 321, 1679 "is-local": true 1680 } 1681 ] 1682 } 1683 } 1684 } 1685 } 1686 ] 1687 } 1688 ] 1689 } 1690 } 1692 B.2. SR MPLS Topology with TE Enabled 1694 In this section, the example below shows an instance data of a 1695 overlay topology as shown in Figure 4. Some attributes are from the 1696 underlay topology shown in Figure 5. 1698 ............................. .................... 1699 . D1 . . D2 . 1700 . . . . 1701 . SID:17012 . . . 1702 . Base64:MTcwMTI= . . . 1703 . +---+ +---+ +---+ . . +---+ +---+ . 1704 -----|S11|----|S12|----|S15|---------|S23|----|S25|----- 1705 . +---+\ +---+ /+---+ . . +---+ /+---+ . 1706 . \ / . . / | . 1707 . \ / . . / | . 1708 . \+---+/ . . +---+/ +---+ . 1709 . |S14| . . |S24|----|S28| . 1710 . +---+ . . +---+ +---+ . 1711 ..............|.............. .....|.............. 1712 | | 1713 SID:17051 +---+ +---+ SID:17052 | 1714 Base64: |S51|----|S52| Base64: | 1715 MTcwNTE= +---+ /+---+ MTcwNTI= | 1716 | / / 1717 | / .........../ 1718 | / . D3 / 1719 | / . /. 1720 SID:17053 +---+ . +---+/ . 1721 Base64: |S53|-----------|S31| . 1722 MTcwNTM= +---+ . +---+ . 1723 ........... 1725 Figure 5: Example Underlay SR MPLS TE Toplogy 1727 { 1728 "ietf-network:networks": { 1729 "network": [ 1730 { 1731 "network-types": { 1732 "ietf-l3-unicast-topology:l3-unicast-topology": { 1733 "ietf-sr-mpls-topology:sr-mpls": {} 1734 }, 1735 "ietf-te-topology:te-topology": { 1736 "ietf-te-topology-packet:packet": {} 1737 } 1738 }, 1739 "network-id": "sr-mpls-te-topo-example", 1740 "ietf-l3-unicast-topology:l3-topology-attributes": { 1741 "ietf-sr-mpls-topology:sr-mpls": { 1742 "srgb": [ 1743 { 1744 "lower-bound": 16000, 1745 "upper-bound": 23999 1746 } 1747 ] 1748 } 1749 }, 1750 "ietf-te-topology:te-topology-identifier": { 1751 "provider-id": 0, 1752 "client-id": 0, 1753 "topology-id": "sr-mpls-te-topo-example" 1754 }, 1755 "ietf-te-topology:te": { 1756 "optimization-criterion": "ietf-te-types:of-minimize-cost-path" 1757 }, 1758 "node": [ 1759 { 1760 "node-id": "D1", 1761 "ietf-network-topology:termination-point": [ 1762 { 1763 "tp-id": "1-0-1", 1764 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 1765 "unnumbered-id": 101 1766 }, 1767 "ietf-te-topology:te-tp-id": 101, 1768 "ietf-te-topology:te": { 1769 "interface-switching-capability": [ 1770 { 1771 "switching-capability": "switching-psc1", 1772 "encoding": "lsp-encoding-packet", 1773 "max-lsp-bandwidth": [ 1774 { 1775 "priority": 7, 1776 "te-bandwidth": { 1777 "generic": "0x1p22" 1778 } 1779 } 1780 ] 1781 } 1782 ] 1783 } 1784 }, 1785 { 1786 "tp-id": "1-2-1", 1787 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 1788 "unnumbered-id": 121 1789 }, 1790 "ietf-te-topology:te-tp-id": 121, 1791 "ietf-te-topology:te": { 1792 "interface-switching-capability": [ 1793 { 1794 "switching-capability": "switching-psc1", 1795 "encoding": "lsp-encoding-packet", 1796 "max-lsp-bandwidth": [ 1797 { 1798 "priority": 7, 1799 "te-bandwidth": { 1800 "generic": "0x1p22" 1801 } 1802 } 1803 ] 1804 } 1805 ] 1806 } 1807 }, 1808 { 1809 "tp-id": "1-3-1", 1810 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 1811 "unnumbered-id": 131 1812 }, 1813 "ietf-te-topology:te-tp-id": 131, 1814 "ietf-te-topology:te": { 1815 "interface-switching-capability": [ 1816 { 1817 "switching-capability": "switching-psc1", 1818 "encoding": "lsp-encoding-packet", 1819 "max-lsp-bandwidth": [ 1820 { 1821 "priority": 7, 1822 "te-bandwidth": { 1823 "generic": "0x1p22" 1824 } 1825 } 1826 ] 1827 } 1828 ] 1829 } 1830 } 1831 ], 1832 "ietf-l3-unicast-topology:l3-node-attributes": { 1833 "router-id": ["203.0.113.1"], 1834 "prefix": [ 1835 { 1836 "prefix": "203.0.113.1/32", 1837 "ietf-sr-mpls-topology:sr-mpls": { 1838 "sids": { 1839 "sid": [ 1840 { 1842 "algorithm": "prefix-sid-algorithm-shortest-path", 1843 "start-sid": 101, 1844 "range": 1, 1845 "is-local": false, 1846 "is-node": true 1847 } 1848 ] 1849 } 1850 } 1851 } 1852 ], 1853 "ietf-sr-mpls-topology:sr-mpls": { 1854 "srgb": [ 1855 { 1856 "lower-bound": 16000, 1857 "upper-bound": 23999 1858 } 1859 ], 1860 "srlb": [ 1861 { 1862 "lower-bound": 15000, 1863 "upper-bound": 15999 1864 } 1865 ] 1866 } 1867 }, 1868 "ietf-te-topology:te-node-id": "203.0.113.1", 1869 "ietf-te-topology:te": { 1870 "te-node-attributes": { 1871 "admin-status": "up", 1872 "domain-id": 1001, 1873 "is-abstract": [null], 1874 "signaling-address": [ 1875 "203.0.113.1" 1876 ], 1877 "connectivity-matrices": { 1878 "is-allowed": true, 1879 "path-constraints": { 1880 "te-bandwidth": { 1881 "generic": "0x1p20" 1882 }, 1883 "path-metric-bounds": { 1884 "path-metric-bound": [ 1885 { 1886 "metric-type": "path-metric-delay-average", 1887 "upper-bound": 15000 1888 } 1889 ] 1891 } 1892 }, 1893 "ietf-te-topology-packet:throttle": { 1894 "threshold-out": { 1895 "two-way-delay": 18000 1896 } 1897 }, 1898 "connectivity-matrix": [ 1899 { 1900 "id": 1, 1901 "from": { 1902 "tp-ref": "1-0-1" 1903 }, 1904 "to": { 1905 "tp-ref": "1-2-1" 1906 }, 1907 "is-allowed": true, 1908 "underlay": { 1909 "enabled": true, 1910 "primary-path": { 1911 "network-ref": "underlay-example", 1912 "path-element": [ 1913 { 1914 "path-element-id": 1, 1915 "label-hop": { 1916 "te-label": { 1917 "generic": "MTcwMTI=", 1918 "direction": "forward" 1919 } 1920 } 1921 } 1922 ] 1923 } 1924 } 1925 }, 1926 { 1927 "id": 2, 1928 "from": { 1929 "tp-ref": "1-2-1" 1930 }, 1931 "to": { 1932 "tp-ref": "1-0-1" 1933 }, 1934 "is-allowed": true, 1935 "underlay": { 1936 "enabled": true, 1937 "primary-path": { 1938 "network-ref": "underlay-example", 1939 "path-element": [ 1940 { 1941 "path-element-id": 1, 1942 "label-hop": { 1943 "te-label": { 1944 "generic": "MTcwMTI=", 1945 "direction": "forward" 1946 } 1947 } 1948 } 1949 ] 1950 } 1951 } 1952 } 1953 ] 1954 } 1955 } 1956 } 1957 }, 1958 { 1959 "node-id": "D2", 1960 "ietf-network-topology:termination-point": [ 1961 { 1962 "tp-id": "2-0-1", 1963 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 1964 "unnumbered-id": 201 1965 }, 1966 "ietf-te-topology:te-tp-id": 201, 1967 "ietf-te-topology:te": { 1968 "interface-switching-capability": [ 1969 { 1970 "switching-capability": "switching-psc1", 1971 "encoding": "lsp-encoding-packet", 1972 "max-lsp-bandwidth": [ 1973 { 1974 "priority": 7, 1975 "te-bandwidth": { 1976 "generic": "0x1p22" 1977 } 1978 } 1979 ] 1980 } 1981 ] 1982 } 1983 }, 1984 { 1985 "tp-id": "2-1-1", 1986 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 1987 "unnumbered-id": 211 1988 }, 1989 "ietf-te-topology:te-tp-id": 211, 1990 "ietf-te-topology:te": { 1991 "interface-switching-capability": [ 1992 { 1993 "switching-capability": "switching-psc1", 1994 "encoding": "lsp-encoding-packet", 1995 "max-lsp-bandwidth": [ 1996 { 1997 "priority": 7, 1998 "te-bandwidth": { 1999 "generic": "0x1p22" 2000 } 2001 } 2002 ] 2003 } 2004 ] 2005 } 2006 }, 2007 { 2008 "tp-id": "2-3-1", 2009 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 2010 "unnumbered-id": 231 2011 } 2012 } 2013 ], 2014 "ietf-l3-unicast-topology:l3-node-attributes": { 2015 "router-id": ["203.0.113.2"], 2016 "prefix": [ 2017 { 2018 "prefix": "203.0.113.2/32", 2019 "ietf-sr-mpls-topology:sr-mpls": { 2020 "sids": { 2021 "sid": [ 2022 { 2023 "algorithm": "prefix-sid-algorithm-shortest-path", 2024 "start-sid": 102, 2025 "range": 1, 2026 "is-local": false, 2027 "is-node": true 2028 } 2029 ] 2030 } 2031 } 2032 } 2033 ], 2034 "ietf-sr-mpls-topology:sr-mpls": { 2035 "srgb": [ 2036 { 2037 "lower-bound": 16000, 2038 "upper-bound": 23999 2039 } 2040 ], 2041 "srlb": [ 2042 { 2043 "lower-bound": 15000, 2044 "upper-bound": 15999 2045 } 2046 ] 2047 } 2048 }, 2049 "ietf-te-topology:te-node-id": "203.0.113.2", 2050 "ietf-te-topology:te": { 2051 "te-node-attributes": { 2052 "admin-status": "up", 2053 "domain-id": 1001, 2054 "is-abstract": [null], 2055 "signaling-address": [ 2056 "203.0.113.2" 2057 ] 2058 } 2059 } 2060 }, 2061 { 2062 "node-id": "D3", 2063 "ietf-network-topology:termination-point": [ 2064 { 2065 "tp-id": "3-1-1", 2066 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 2067 "unnumbered-id": 311 2068 }, 2069 "ietf-te-topology:te-tp-id": 311, 2070 "ietf-te-topology:te": { 2071 "interface-switching-capability": [ 2072 { 2073 "switching-capability": "switching-psc1", 2074 "encoding": "lsp-encoding-packet", 2075 "max-lsp-bandwidth": [ 2076 { 2077 "priority": 7, 2078 "te-bandwidth": { 2079 "generic": "0x1p22" 2080 } 2081 } 2082 ] 2084 } 2085 ] 2086 } 2087 }, 2088 { 2089 "tp-id": "3-2-1", 2090 "ietf-l3-unicast-topology:l3-termination-point-attributes": { 2091 "unnumbered-id": 321 2092 } 2093 } 2094 ], 2095 "ietf-l3-unicast-topology:l3-node-attributes": { 2096 "router-id": ["203.0.113.3"], 2097 "prefix": [ 2098 { 2099 "prefix": "203.0.113.3/32", 2100 "ietf-sr-mpls-topology:sr-mpls": { 2101 "sids": { 2102 "sid": [ 2103 { 2104 "algorithm": "prefix-sid-algorithm-shortest-path", 2105 "start-sid": 103, 2106 "range": 1, 2107 "is-local": false, 2108 "is-node": true 2109 } 2110 ] 2111 } 2112 } 2113 } 2114 ], 2115 "ietf-sr-mpls-topology:sr-mpls": { 2116 "srgb": [ 2117 { 2118 "lower-bound": 16000, 2119 "upper-bound": 23999 2120 } 2121 ], 2122 "srlb": [ 2123 { 2124 "lower-bound": 15000, 2125 "upper-bound": 15999 2126 } 2127 ] 2128 } 2129 }, 2130 "ietf-te-topology:te-node-id": "203.0.113.3", 2131 "ietf-te-topology:te": { 2132 "te-node-attributes": { 2133 "admin-status": "up", 2134 "domain-id": 1001, 2135 "signaling-address": [ 2136 "203.0.113.3" 2137 ] 2138 } 2139 } 2140 } 2141 ], 2142 "ietf-network-topology:link": [ 2143 { 2144 "link-id": "D1,1-2-1,D2,2-1-1", 2145 "source": { 2146 "source-node": "D1", 2147 "source-tp": "1-2-1" 2148 }, 2149 "destination": { 2150 "dest-node": "D2", 2151 "dest-tp": "2-1-1" 2152 }, 2153 "ietf-l3-unicast-topology:l3-link-attributes": { 2154 "metric1": "100", 2155 "ietf-sr-mpls-topology:sr-mpls": { 2156 "sids": { 2157 "sid": [ 2158 { 2159 "value-type": "index", 2160 "sid": 121, 2161 "is-local": true 2162 } 2163 ] 2164 } 2165 } 2166 }, 2167 "ietf-te-topology:te": { 2168 "te-link-attributes": { 2169 "interface-switching-capability": [ 2170 { 2171 "switching-capability": "switching-psc1", 2172 "encoding": "lsp-encoding-packet", 2173 "ietf-te-topology-packet:packet-switch-capable": 2174 { 2175 "minimum-lsp-bandwidth": "0x1p20" 2176 } 2177 } 2178 ] 2179 } 2181 } 2182 }, 2183 { 2184 "link-id": "D2,2-1-1,D1,1-2-1", 2185 "source": { 2186 "source-node": "D2", 2187 "source-tp": "2-1-1" 2188 }, 2189 "destination": { 2190 "dest-node": "D1", 2191 "dest-tp": "1-2-1" 2192 }, 2193 "ietf-l3-unicast-topology:l3-link-attributes": { 2194 "metric1": "100", 2195 "ietf-sr-mpls-topology:sr-mpls": { 2196 "sids": { 2197 "sid": [ 2198 { 2199 "value-type": "index", 2200 "sid": 211, 2201 "is-local": true 2202 } 2203 ] 2204 } 2205 } 2206 }, 2207 "ietf-te-topology:te": { 2208 "te-link-attributes": { 2209 "interface-switching-capability": [ 2210 { 2211 "switching-capability": "switching-psc1", 2212 "encoding": "lsp-encoding-packet", 2213 "ietf-te-topology-packet:packet-switch-capable": 2214 { 2215 "minimum-lsp-bandwidth": "0x1p20" 2216 } 2217 } 2218 ] 2219 } 2220 } 2221 }, 2222 { 2223 "link-id": "D1,1-3-1,D3,3-1-1", 2224 "source": { 2225 "source-node": "D1", 2226 "source-tp": "1-3-1" 2227 }, 2228 "destination": { 2229 "dest-node": "D3", 2230 "dest-tp": "3-1-1" 2231 }, 2232 "ietf-l3-unicast-topology:l3-link-attributes": { 2233 "metric1": "100", 2234 "ietf-sr-mpls-topology:sr-mpls": { 2235 "sids": { 2236 "sid": [ 2237 { 2238 "value-type": "index", 2239 "sid": 131, 2240 "is-local": true 2241 } 2242 ] 2243 } 2244 } 2245 }, 2246 "ietf-te-topology:te": { 2247 "te-link-attributes": { 2248 "is-abstract": [null], 2249 "underlay": { 2250 "enabled": true, 2251 "primary-path": { 2252 "network-ref": "underlay-example", 2253 "path-element": [ 2254 { 2255 "path-element-id": 1, 2256 "label-hop": { 2257 "te-label": { 2258 "generic": "MTcwNTE=", 2259 "direction": "forward" 2260 } 2261 } 2262 }, 2263 { 2264 "path-element-id": 2, 2265 "label-hop": { 2266 "te-label": { 2267 "generic": "MTcwNTI=", 2268 "direction": "forward" 2269 } 2270 } 2271 }, 2272 { 2273 "path-element-id": 3, 2274 "label-hop": { 2275 "te-label": { 2276 "generic": "MTcwNTM=", 2277 "direction": "forward" 2278 } 2279 } 2280 } 2281 ] 2282 } 2283 }, 2284 "interface-switching-capability": [ 2285 { 2286 "switching-capability": "switching-psc1", 2287 "encoding": "lsp-encoding-packet", 2288 "ietf-te-topology-packet:packet-switch-capable": 2289 { 2290 "minimum-lsp-bandwidth": "0x1p20" 2291 } 2292 } 2293 ] 2294 } 2295 } 2296 }, 2297 { 2298 "link-id": "D3,3-1-1,D1,1-3-1", 2299 "source": { 2300 "source-node": "D3", 2301 "source-tp": "3-1-1" 2302 }, 2303 "destination": { 2304 "dest-node": "D1", 2305 "dest-tp": "1-3-1" 2306 }, 2307 "ietf-l3-unicast-topology:l3-link-attributes": { 2308 "metric1": "100", 2309 "ietf-sr-mpls-topology:sr-mpls": { 2310 "sids": { 2311 "sid": [ 2312 { 2313 "value-type": "index", 2314 "sid": 311, 2315 "is-local": true 2316 } 2317 ] 2318 } 2319 } 2320 }, 2321 "ietf-te-topology:te": { 2322 "te-link-attributes": { 2323 "is-abstract": [null], 2324 "interface-switching-capability": [ 2325 { 2326 "switching-capability": "switching-psc1", 2327 "encoding": "lsp-encoding-packet", 2328 "ietf-te-topology-packet:packet-switch-capable": 2329 { 2330 "minimum-lsp-bandwidth": "0x1p20" 2331 } 2332 } 2333 ] 2334 } 2335 } 2336 }, 2337 { 2338 "link-id": "D2,2-3-1,D3,3-2-1", 2339 "source": { 2340 "source-node": "D2", 2341 "source-tp": "2-3-1" 2342 }, 2343 "destination": { 2344 "dest-node": "D3", 2345 "dest-tp": "3-2-1" 2346 }, 2347 "ietf-l3-unicast-topology:l3-link-attributes": { 2348 "metric1": "100", 2349 "ietf-sr-mpls-topology:sr-mpls": { 2350 "sids": { 2351 "sid": [ 2352 { 2353 "value-type": "index", 2354 "sid": 231, 2355 "is-local": true 2356 } 2357 ] 2358 } 2359 } 2360 } 2361 }, 2362 { 2363 "link-id": "D3,3-2-1,D2,2-3-1", 2364 "source": { 2365 "source-node": "D3", 2366 "source-tp": "3-2-1" 2367 }, 2368 "destination": { 2369 "dest-node": "D2", 2370 "dest-tp": "2-3-1" 2371 }, 2372 "ietf-l3-unicast-topology:l3-link-attributes": { 2373 "metric1": "100", 2374 "ietf-sr-mpls-topology:sr-mpls": { 2375 "sids": { 2376 "sid": [ 2377 { 2378 "value-type": "index", 2379 "sid": 321, 2380 "is-local": true 2381 } 2382 ] 2383 } 2384 } 2385 } 2386 } 2387 ] 2388 } 2389 ] 2390 } 2391 } 2393 Appendix C. Contributors 2395 Jeff Tantsura 2396 Email: jefftant.ietf@gmail.com 2398 Yingzhen Qu 2399 Email: yingzhen.qu@huawei.com 2401 Authors' Addresses 2403 Xufeng Liu 2404 IBM Corporation 2406 EMail: xufeng.liu.ietf@gmail.com 2408 Igor Bryskin 2409 Individual 2411 EMail: i_bryskin@yahoo.com 2413 Vishnu Pavan Beeram 2414 Juniper Networks 2416 EMail: vbeeram@juniper.net 2417 Tarek Saad 2418 Juniper Networks 2420 EMail: tsaad@juniper.net 2422 Himanshu Shah 2423 Ciena 2425 EMail: hshah@ciena.com 2427 Stephane Litkowski 2428 Cisco 2430 EMail: slitkows.ietf@gmail.com