idnits 2.17.1 draft-busizheng-teas-mpls-tp-yang-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 11, 2019) is 1872 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: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 TEAS Working Group Italo Busi 2 Internet Draft Haomian Zheng 3 Intended status: Standard Track Huawei 5 Expires: September 2019 March 11, 2019 7 YANG Data Models for Multiprotocol Label Switching - Transport Profile 9 draft-busizheng-teas-mpls-tp-yang-00.txt 11 Status of this Memo 13 This Internet-Draft is submitted to IETF in full conformance with 14 the provisions of BCP 78 and BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six 22 months and may be updated, replaced, or obsoleted by other documents 23 at any time. It is inappropriate to use Internet-Drafts as 24 reference material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on September 11, 2019. 34 Copyright Notice 36 Copyright (c) 2019 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with 44 respect to this document. Code Components extracted from this 45 document must include Simplified BSD License text as described in 46 Section 4.e of the Trust Legal Provisions and are provided without 47 warranty as described in the Simplified BSD License. 49 Abstract 51 Multi-protocol Label Switching - Transport Profile (MPLS-TP) is a 52 profile of the MPLS protocol that is used in packet switched 53 transport networks and operated in a similar manner to other 54 existing transport technologies (e.g., OTN), as described in 55 RFC5921. This document specifies YANG models for MPLS-TP, which have 56 not been covered by existing models so far. The gap analysis with 57 current relevant traffic-engineering (TE) and MPLS models is also 58 included. 60 Table of Contents 62 1. Introduction...................................................2 63 2. Considerations on the Augmentation.............................3 64 2.1. Modules Relationship......................................3 65 2.2. Prefixs in Model Names....................................4 66 3. Gap Analysis for MPLS-TP topology..............................4 67 3.1. TE Bandwidth Augmentations................................5 68 3.2. TE Label Augmentations....................................6 69 4. Gap Analysis for MPLS-TP Tunnel Configuration..................6 70 4.1. TE Bandwidth Augmentation.................................7 71 4.2. TE Label Augmentation.....................................7 72 5. Related YANG Code..............................................8 73 5.1. YANG Code for MPLS-TP Topology Augmentation...............8 74 5.2. YANG Code for MPLS-TP Tunnel Augmentation................11 75 5.3. MPLS-TP Specific YANG Types..............................13 76 6. Open Issues...................................................15 77 7. Security......................................................16 78 8. Acknowledgements..............................................16 79 9. References....................................................16 80 9.1. Normative References.....................................16 81 9.2. Informative References...................................16 82 Authors' Addresses...............................................17 84 1. Introduction 86 Multi-protocol Label Switching - Transport Profile (MPLS-TP) is a 87 packet switching technology intended operated in a similar manner to 88 other existing transport technologies (e.g., OTN), as described in 89 [RFC5921], which includes Traffic Engineering (TE) features. 91 Generic TE models, including the TE topology and tunnel, have been 92 defined in [TE-Topology] and [TE-Tunnel] using the YANG data 93 modeling language and are applicable to any TE technologies 94 including MPLS-TE and OTN and therefore also to MPLS-TP. 96 The YANG models for MPLS with TE features (MPLS-TE), are provided in 97 [TE-MPLS] as a technology-specific augmentations of the generic TE 98 models. However, technology-specific augmentations for TE label, and 99 TE bandwidth of TE Topology and Tunnel models, have not been covered 100 yet. 102 This document defines YANG data models for MPLS-TP topologies and 103 tunnels, providing the minimum set of attributes that are required 104 and not yet available in existing TE and MPLS YANG models. See 105 section 3 and 4 for more detailed gap analysis. 107 The proposed MPLS-TP YANG models can be used as an input to enhance 108 the current MPLS-TE YANG models. 110 2. Considerations on the Augmentation 112 2.1. Modules Relationship 114 In this draft two models are proposed: one MPLS-TP 115 technology-specific topology model that augments the ietf-te- 116 topology YANG module, defined in [TE-Topology], and another MPLS-TP 117 technology-specific tunnel model that augments the ietf-te YANG 118 module, defined in [TE-Tunnel]. 120 The following common fundamental models are imported: 122 o ietf-routing-types defined in [RFC8294] 124 TE generic +------------------+ +------------+ o: augment 125 module | ietf-te-topology | | ietf-te | 126 +------------------+ +------------+ 127 o o 128 | | 129 | | 130 | | 131 +----------------------+ +-------------------------+ 132 MPLS-TP | ietf-te-mpls-tp-topo | | ietf-te-mpls-tp-tunnel | 133 +----------------------+ +-------------------------+ 135 Figure 1: Relationship of MPLS-TP topology and tunnel module with TE 136 generic TE topology and tunnel YANG modules 138 2.2. Prefixs in Model Names 140 In this document, names of data nodes and other data model objects 141 are prefixed using the standard prefix associated with the 142 corresponding YANG imported modules, as shown in Table 1. 144 +---------------+----------------------+--------------------------+ 145 | Prefix | YANG module | Reference | 146 +---------------+----------------------+--------------------------+ 147 | yang | ietf-yang-types | [RFC6991] | 148 | inet | ietf-inet-types | [RFC6991] | 149 | rt-types | ietf-routing-types | [RFC8294] | 150 | tet | ietf-te-topology | [TE-Topology] | 151 | te | ietf-te | [TE-Tunnel] | 152 | te-mpls | ietf-te-mpls | [TE-MPLS] | 153 | mpls-tp-topo | ietf- mpls-tp-topo | This document | 154 | mpls-tp-tunnel|ietf- mpls-tp-tunnel | This document | 155 +---------------+----------------------+--------------------------+ 157 Table 1: Prefixes and corresponding YANG modules 159 3. Gap Analysis for MPLS-TP topology 161 There are no YANG models that provide MPLS-TE technology-specific 162 augmentations of the generic TE Topology model defined in 163 [TE-Topology]. 165 This section analyses the minimum set of attributes that are 166 required to be specified in an MPLS-TP technology-specific 167 augmentation. 169 Additional attributes that may be required to support a broader set 170 of MPLS-TP and/or MPLS-TE functions are for further study. 172 Given the guidance for augmentation in [TE-Topology], the following 173 technology-specific augmentations need to be provided: 175 - A network-type to indicate that the TE topology is an MPLS-TP 176 Topology, as follow: 178 augment /nw:networks/nw:network/nw:network-types/tet-te-topology: 179 +-- rw mpls-tp-topology! 181 - TE Bandwidth Augmentations a described in section 3.1; 182 - TE Label Augmentations as described in section 3.2; 184 3.1. TE Bandwidth Augmentations 186 Following TE Bandwidth attributes are needed to be augmented to the 187 module ietf-te-topology in [TE-Topology]: 189 - Augmentations for te-bandwidth in the max-link-bandwidth, max- 190 resv-link-bandwidth and unreserved-bandwidth attributes of MPLS-TP 191 TE Links are necessary for te-link-attributes and listed as 192 follow. It is worth noting that for te-bandwidth in other places, 193 this augment is not necessary. 195 augment /nw:networks/nw:network/nt:link/tet:te/tet:te-link- 196 attributes/tet:max-link-bandwidth/tet:te-bandwidth/tet:technology: 197 +--:(mpls-tp) 198 +--rw mpls-tp-bandwidth? uint64 200 augment /nw:networks/nw:network/nt:link/tet:te/tet:te-link- 201 attributes/tet:max-resv-link-bandwidth/tet:te- 202 bandwidth/tet:technology: 203 +--:(mpls-tp) 204 +--rw mpls-tp-bandwidth? uint64 206 augment /nw:networks/nw:network/nt:link/tet:te/tet:te-link- 207 attributes/tet:unreserved-bandwidth/tet:te- 208 bandwidth/tet:technology: 209 +--:(mpls-tp) 211 +--rw mpls-tp-bandwidth? uint64 213 - Augmentations for the max-lsp-bandwidth attribute are necessary 214 for MPLS-TP TE Links and TTPs and listed as following. It is worth 215 noting that for the other 'max-lsp-bandwidth', this augmentation 216 is not necessary. 218 augment /nw:networks/nw:network/nt:link/tet:te/tet:te-link- 219 attributes/tet:interface-switching-capability/tet:max-lsp- 220 bandwidth/tet:te-bandwidth/tet:technology: 221 +--:(mpls-tp) 222 +--rw bandwidth-profile-name? string 223 +--rw bandwidth-profile-type? identityref 224 +--rw CIR? uint64 225 +--rw EIR? uint64 226 +--rw CBS? uint64 227 +--rw EBS? uint64 229 augment /nw:networks/nw:network/nw:node/nt:termination- 230 point/tet:te/tet:interface-switching-capability/tet:max-lsp- 231 bandwidth/tet:te-bandwidth/tet:technology: 232 +--:(mpls-tp) 233 +--rw bandwidth-profile-name? string 234 +--rw bandwidth-profile-type? identityref 235 +--rw CIR? uint64 236 +--rw EIR? uint64 237 +--rw CBS? uint64 238 +--rw EBS? uint64 240 3.2. TE Label Augmentations 242 In MPLS-TP, the label allocation is done by NE, information about 243 label values availability is not necessary to be provided to the 244 controller. Moreover, MPLS-TP tunnels are currently established 245 within a single domain. 247 Therefore this document does not define any MPLS-TP 248 technology-specific augmentations, of the TE Topology model, for the 249 TE label since no TE label related attributes should be instantiated 250 for MPLS-TP Topologies. 252 4. Gap Analysis for MPLS-TP Tunnel Configuration 254 MPLS-TE technology-specific augmentations of the generic TE Tunnel 255 model defined in [TE-MPLS]. 257 This section analyses the minimum set of attributes that are 258 required to be specified in an MPLS-TP technology-specific 259 augmentation and not yet available in [TE-MPLS]. 261 Additional attributes that may be required to support a broader set 262 of MPLS-TP and/or MPLS-TE functions are for further study. 264 Although there are no guidance for augmentation in [TE-Tunnel], the 265 following technology-specific augmentations need to be provided: 267 - TE Bandwidth Augmentations as described in section 4.1 269 - TE Label Augmentations as described in section 4.2 271 4.1. TE Bandwidth Augmentation 273 Following TE Bandwidth attributes are needed to be augmented for 274 MPLS-TP to the to the module ietf-te in [TE-Tunnel], but are not yet 275 defined in [TE-MPLS]: 277 - Augmentations for the te-bandwdith attribute of TE Tunnels under 278 te/globals/tunnels are listed as follow. It is worth noting that 279 for te-bandwidth in other places, this augmentation is not 280 necessary. 282 augment /te:te/te:tunnels/te:tunnel/te:te-bandwidth/te:technology: 283 +--:(mpls-tp) 284 +--rw bandwidth-profile-name? string 285 +--rw bandwidth-profile-type? identityref 286 +--rw CIR? uint64 287 +--rw EIR? uint64 288 +--rw CBS? uint64 289 +--rw EBS? uint64 291 4.2. TE Label Augmentation 293 Following TE Label attributes are needed to be augmented for MPLS-TP 294 to the to the module ietf-te in [TE-Tunnel], but are not yet defined 295 in [TE-MPLS]: 297 - Augmentations for the te-label attribute of MPLS-TP label hops are 298 used to report the computed primary and secondary paths of MPLS-TP 299 TE Tunnels as well as the route and the path of the MPLS-TP LSPs 300 of the primary and secondary paths of MPLS-TP TE Tunnels. These 301 augmentations are listed as follow, and it is worth noting for te- 302 label in other places, there is no need to do the augmentation. 304 augment /te:te/te:tunnels/te:tunnel/te:p2p-primary-paths/te:p2p- 305 primary-path/te:computed-paths-properties/te:computed-path- 306 properties/te:path-properties/te:path-route-objects/te:path- 307 computed-route-object/te:type/te:label/te:label-hop/te:te- 308 label/te:technology: 309 +--:(mpls-tp) 310 +--ro mpls-label? rt-types:mpls-label 312 augment /te:te/te:tunnels/te:tunnel/te:p2p-primary-paths/te:p2p- 313 primary-path/te:lsps/te:lsp/te:path-properties/te:path-route- 314 objects/te:path-computed-route-object/te:type/te:label/te:label- 315 hop/te:te-label/te:technology: 317 +--:(mpls-tp) 318 +--ro mpls-label? rt-types:mpls-label 320 augment /te:te/te:tunnels/te:tunnel/te:p2p-secondary-paths/te:p2p- 321 secondary-path/te:computed-paths-properties/te:computed-path- 322 properties/te:path-properties/te:path-route-objects/te:path- 323 computed-route-object/te:type/te:label/te:label-hop/te:te- 324 label/te:technology: 325 +--:(mpls-tp) 326 +--ro mpls-label? rt-types:mpls-label 328 augment /te:te/te:tunnels/te:tunnel/te:p2p-secondary-paths/te:p2p- 329 secondary-path/te:lsps/te:lsp/te:path-properties/te:path-route- 330 objects/te:path-computed-route-object/te:type/te:label/te:label- 331 hop/te:te-label/te:technology: 332 +--:(mpls-tp) 333 +--ro mpls-label? rt-types:mpls-label 335 5. Related YANG Code 337 5.1. YANG Code for MPLS-TP Topology Augmentation 339 file "ietf-mpls-tp-topology@2019-03-11.yang" 340 module ietf-mpls-tp-topology { 341 //yang-version 1.1; 343 namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-tp-topology"; 344 prefix "mpls-tp-topo"; 346 import ietf-network { 347 prefix "nw"; 348 } 350 import ietf-network-topology { 351 prefix "nt"; 352 } 354 import ietf-te-topology { 355 prefix "tet"; 356 } 358 import ietf-mpls-tp-types { 359 prefix "mpls-tp-types"; 360 } 362 organization 363 "Internet Engineering Task Force (IETF) TEAS WG"; 364 contact 365 " 366 WG List: 368 ID-draft editor: 369 Italo Busi (italo.busi@huawei.com); 370 Haomian Zheng (zhenghaomian@huawei.com); 371 "; 373 description 374 "This module defines technology-specific MPLS-TP topology 375 data model."; 377 revision 2019-03-11 { 378 description 379 "version -00 as an I-D"; 380 reference 381 "draft-busizheng-teas-mpls-tp-yang"; 382 } 384 augment "/nw:networks/nw:network/nw:network-types/" 385 + "tet:te-topology" { 386 container mpls-tp-topology { 387 presence "indicates a topology type of MPLS-TP layer."; 388 description "mpls-tp te topology type"; 389 } 390 description "augment network types to include mpls-tp 391 newtork"; 392 } 394 augment "/nw:networks/nw:network/nt:link/tet:te/" 395 + "tet:te-link-attributes/" 396 + "tet:interface-switching-capability/tet:max-lsp- 397 bandwidth/" 398 + "tet:te-bandwidth/tet:technology" { 399 when "../../../../../../../nw:network-types/tet:te-topology/" 400 + "mpls-tp-topo:mpls-tp-topology" { 401 description "MPLS-TP TE bandwidth."; 402 } 403 description "MPLS-TP bandwidth."; 404 case mpls-tp { 405 uses mpls-tp-types:mpls-tp-path-bandwidth; 406 } 407 } 408 augment "/nw:networks/nw:network/nw:node/nt:termination-point/" 409 + "tet:te/tet:interface-switching-capability/" 410 + "tet:max-lsp-bandwidth/tet:te-bandwidth/tet:technology" 411 { 412 when "../../../../../../../nw:network-types/tet:te-topology/" 413 + "mpls-tp-topo:mpls-tp-topology" { 414 description "Augment MPLS-TP TE bandwidth"; 415 } 416 description "MPLS-TP bandwidth."; 417 case mpls-tp { 418 uses mpls-tp-types:mpls-tp-path-bandwidth; 419 } 420 } 422 augment "/nw:networks/nw:network/nt:link/tet:te/" 423 + "tet:te-link-attributes/tet:max-link-bandwidth/" 424 + "tet:te-bandwidth/tet:technology" { 425 when "../../../../../../nw:network-types/tet:te-topology/" 426 + "mpls-tp-topo:mpls-tp-topology" { 427 description "MPLS-TP TE bandwidth."; 428 } 429 description "MPLS-TP bandwidth."; 430 case mpls-tp { 431 uses mpls-tp-types:mpls-tp-bandwidth; 432 } 433 } 435 augment "/nw:networks/nw:network/nt:link/tet:te/" 436 + "tet:te-link-attributes/tet:max-resv-link-bandwidth/" 437 + "tet:te-bandwidth/tet:technology" { 438 when "../../../../../../nw:network-types/tet:te-topology/" 439 + "mpls-tp-topo:mpls-tp-topology" { 440 description "MPLS-TP TE bandwidth."; 441 } 442 description "MPLS-TP bandwidth."; 443 case mpls-tp { 444 uses mpls-tp-types:mpls-tp-bandwidth; 445 } 446 } 448 augment "/nw:networks/nw:network/nt:link/tet:te/" 449 + "tet:te-link-attributes/tet:unreserved-bandwidth/" 450 + "tet:te-bandwidth/tet:technology" { 451 when "../../../../../../nw:network-types/tet:te-topology/" 452 + "mpls-tp-topo:mpls-tp-topology" { 453 description "MPLS-TP TE bandwidth."; 454 } 455 description "MPLS-TP bandwidth."; 456 case mpls-tp { 457 uses mpls-tp-types:mpls-tp-bandwidth; 458 } 459 } 460 } 461 463 5.2. YANG Code for MPLS-TP Tunnel Augmentation 465 file "ietf-mpls-tp-tunnel@2019-03-11.yang" 466 module ietf-mpls-tp-tunnel { 467 //yang-version 1.1; 469 namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-tp-tunnel"; 470 prefix "mpls-tp-tunnel"; 472 import ietf-te { 473 prefix "te"; 474 } 476 import ietf-mpls-tp-types { 477 prefix "mpls-tp-types"; 478 } 479 organization 480 "Internet Engineering Task Force (IETF) TEAS WG"; 481 contact 482 " 483 WG List: 485 ID-draft editor: 486 Italo Busi (italo.busi@huawei.com); 487 Haomian Zheng (zhenghaomian@huawei.com); 488 "; 489 description 490 "This module defines technology-specific MPLS-TP tunnel 491 data model."; 492 revision 2019-03-11 { 493 description 494 "version -00 as an I-D"; 495 reference 496 "draft-busizheng-teas-mpls-tp-yang"; 497 } 499 augment "/te:te/te:tunnels/te:tunnel/" 500 + "te:te-bandwidth/te:technology" { 502 description "MPLS-TP bandwidth."; 503 case mpls-tp { 504 uses mpls-tp-types:mpls-tp-path-bandwidth; 505 } 506 } 508 augment "/te:te/te:tunnels/te:tunnel/" 509 + "te:p2p-primary-paths/te:p2p-primary-path/" 510 + "te:computed-paths-properties/" 511 + "te:computed-path-properties/" 512 + "te:path-properties/te:path-route-objects/" 513 + "te:path-computed-route-object/te:type/te:label/" 514 + "te:label-hop/te:te-label/te:technology" { 515 description "MPLS-TP label."; 516 case mpls-tp { 517 uses mpls-tp-types:mpls-tp-path-label; 518 } 519 } 521 augment "/te:te/te:tunnels/te:tunnel/" 522 + "te:p2p-primary-paths/te:p2p-primary-path/" 523 + "te:lsps/te:lsp/" 524 + "te:path-properties/te:path-route-objects/" 525 + "te:path-computed-route-object/te:type/te:label/" 526 + "te:label-hop/te:te-label/te:technology" { 527 description "MPLS-TP label."; 528 case mpls-tp { 529 uses mpls-tp-types:mpls-tp-path-label; 530 } 531 } 533 augment "/te:te/te:tunnels/te:tunnel/" 534 + "te:p2p-secondary-paths/te:p2p-secondary-path/" 535 + "te:computed-paths-properties/" 536 + "te:computed-path-properties/" 537 + "te:path-properties/te:path-route-objects/" 538 + "te:path-computed-route-object/te:type/te:label/" 539 + "te:label-hop/te:te-label/te:technology" { 540 description "MPLS-TP label."; 541 case mpls-tp { 542 uses mpls-tp-types:mpls-tp-path-label; 543 } 544 } 546 augment "/te:te/te:tunnels/te:tunnel/" 547 + "te:p2p-secondary-paths/te:p2p-secondary-path/" 548 + "te:lsps/te:lsp/" 549 + "te:path-properties/te:path-route-objects/" 550 + "te:path-computed-route-object/te:type/te:label/" 551 + "te:label-hop/te:te-label/te:technology" { 552 description "MPLS-TP label."; 553 case mpls-tp { 554 uses mpls-tp-types:mpls-tp-path-label; 555 } 556 } 557 } 558 560 5.3. MPLS-TP Specific YANG Types 562 file "ietf-mpls-tp-types@2019-03-11.yang" 563 module ietf-mpls-tp-types { 564 namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-tp-types"; 565 prefix "mpls-tp-types"; 567 import ietf-routing-types { 568 prefix "rt-types"; 570 } 571 import ietf-eth-tran-types { 572 prefix "etht-types"; 574 } 575 organization 576 "Internet Engineering Task Force (IETF) TEAS WG"; 577 contact 578 " 579 WG List: 581 ID-draft editor: 582 Italo Busi (italo.busi@huawei.com); 583 Haomian Zheng (zhenghaomian@huawei.com); 584 "; 585 description 586 "This module defines technology-specific MPLS-TP types 587 data model."; 588 revision 2019-03-11 { 589 description 590 "version -00 as an I-D"; 591 reference 592 "draft-busizheng-teas-mpls-tp-yang"; 593 } 594 grouping mpls-tp-path-bandwidth { 595 description 596 "Path bandwidth for MPLS-TP. "; 597 leaf bandwidth-profile-name{ 598 type string; 599 description "Name of Bandwidth Profile."; 600 } 601 leaf bandwidth-profile-type { 602 type identityref { 603 base etht-types:bandwidth-profile-type; 604 } 605 description "Type of Bandwidth Profile."; 606 } 608 leaf CIR { 609 type uint64; 610 description 611 "Committed Information Rate in Kbps"; 612 } 614 leaf EIR { 615 type uint64; 616 /* 617 Need to indicate that EIR is not supported by RFC 2697 619 must 620 '../bw-profile-type = "etht-types:mef-10-bwp" or ' + 621 '../bw-profile-type = "etht-types:rfc-2698-bwp" or ' + 622 '../bw-profile-type = "etht-types:rfc-4115-bwp"' 624 must 625 '../bw-profile-type != "etht-types:rfc-2697-bwp"' 626 */ 627 description 628 "Excess Information Rate in Kbps 629 In case of RFC 2698, PIR = CIR + EIR"; 630 } 632 leaf CBS { 633 type uint64; 634 description 635 "Committed Burst Size in in KBytes"; 636 } 638 leaf EBS { 639 type uint64; 640 description 641 "Excess Burst Size in KBytes. 642 In case of RFC 2698, PBS = CBS + EBS"; 643 } 644 } 646 grouping mpls-tp-bandwidth { 647 description 648 "Bandwidth for MPLS-TP. "; 649 leaf mpls-tp-bandwidth { 650 type uint64{ 651 range "0..10000000000"; 652 } 653 units "Kbps"; 654 description 655 "Available bandwith value expressed in kilobits per 656 second"; 657 } 658 } 660 grouping mpls-tp-path-label { 661 description 662 "Path Label for MPLS-TP. "; 663 leaf mpls-label { 664 type rt-types:mpls-label; 665 description 666 "MPLS-TP Label."; 667 } 668 } 669 } 670 672 6. Open Issues 674 A few open issues are listed in this section for discussion with the 675 WG experts: 677 - The value for 'encoding' in ietf-te-topology and ietf-te should be 678 configured as 'lsp-encoding-packet' for MPLS-TP; 679 - The value for 'switching-type' in ietf-te-topology and ietf-te 680 should be configured as 'switching-psc1' for MPLS-TP; 681 - There are still open issues for [TE-Tunnel], so the right 682 directory may need to be confirmed up to the latest module ietf-te 683 after maturity; 684 - Is it possible to integrate the proposal augmentation into [TE- 685 MPLS]? 687 If the answer is 'yes', the following open issues need to address in 688 the merged document. 690 - Some attributes will be needed to understand whether MPLS-TP 691 specific features (such as no ECMP, no PHP, bidirectional LSP and 692 GAL) are supported by the MPLS-TE topology and/or required to be 693 supported by the MPLS-TE tunnel to be setup 694 - Per Tunnel-Termination-Point(TTP) modeling, one TTP per physical 695 PE node should be sufficient for MPLS-TP; 696 - An empty container should be set for client-layer-adaption in the 697 topology model for MPLS-TP; 699 Finally, it is not clear how to generate the inter-layer-lock-id for 700 MPLS-TP and other layers, which may be considered in future. 702 7. Security 704 TBD. 706 8. Acknowledgements 708 We thank Loa Andersson and Igor Bryskin for providing useful 709 suggestions for this draft. 711 9. References 713 9.1. Normative References 715 [RFC6991] J. Schoenwaelder, "Common YANG Data Types", RFC6991. 717 [RFC8294] X. Liu, et. al., "Common YANG Data Types for the Routing 718 Area", RFC8294. 720 [TE-Topology] X. Liu, et. al., "YANG Data Model for TE Topologies", 721 draft-ietf-teas-yang-te-topo, work in progress. 723 [TE-Tunnel] T. Saad (Editor), "A YANG Data Model for Traffic 724 Engineering Tunnels and Interfaces", draft-ietf-teas-yang- 725 te, work in progress. 727 9.2. Informative References 729 [RFC5921] M. Bocci, et., al., "A Framework for MPLS in Transport 730 Networks", RFC5921. 732 [TE-MPLS] T. Saad, et. al., "A YANG Data Model for MPLS Traffic 733 Engineering Tunnels", draft-ietf-teas-yang-te-mpls, work 734 in progress. 736 Authors' Addresses 738 Italo Busi 739 Huawei Technologies 740 Email: Italo.Busi@huawei.com 742 Haomian Zheng 743 Huawei Technologies 744 Email: zhenghaomian@huawei.com