idnits 2.17.1 draft-li-pce-pcep-srv6-yang-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (6 March 2022) is 753 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 (-03) exists of draft-ietf-spring-srv6-yang-01 == Outdated reference: A later version (-23) exists of draft-ietf-pce-pcep-yang-18 == Outdated reference: A later version (-22) exists of draft-ietf-pce-segment-routing-ipv6-11 == Outdated reference: A later version (-03) exists of draft-ietf-spring-sr-policy-yang-01 == Outdated reference: A later version (-22) exists of draft-ietf-spring-segment-routing-policy-18 == Outdated reference: A later version (-16) exists of draft-ietf-pce-binding-label-sid-14 Summary: 0 errors (**), 0 flaws (~~), 8 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 PCE Working Group C. Li 3 Internet-Draft Huawei Technologies 4 Intended status: Standards Track S. Sivabalan 5 Expires: 7 September 2022 Ciena Corporation 6 S. Peng 7 Huawei Technologies 8 M. Koldychev 9 Cisco Systems, Inc. 10 L. Ndifor 11 MTN Cameroon 12 6 March 2022 14 A YANG Data Model for Segment Routing (SR) Policy and SRv6 support in 15 Path Computation Element Communications Protocol (PCEP) 16 draft-li-pce-pcep-srv6-yang-06 18 Abstract 20 This document augments a YANG data model for the management of Path 21 Computation Element Communications Protocol (PCEP) for communications 22 between a Path Computation Client (PCC) and a Path Computation 23 Element (PCE), or between two PCEs in support for Segment Routing in 24 IPv6 (SRv6) and SR Policy. The data model includes configuration 25 data and state data (status information and counters for the 26 collection of statistics). 28 Status of This Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF). Note that other groups may also distribute 35 working documents as Internet-Drafts. The list of current Internet- 36 Drafts is at https://datatracker.ietf.org/drafts/current/. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 This Internet-Draft will expire on 7 September 2022. 45 Copyright Notice 47 Copyright (c) 2022 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 52 license-info) in effect on the date of publication of this document. 53 Please review these documents carefully, as they describe your rights 54 and restrictions with respect to this document. Code Components 55 extracted from this document must include Revised BSD License text as 56 described in Section 4.e of the Trust Legal Provisions and are 57 provided without warranty as described in the Revised BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 62 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 63 3. Terminology and Notation . . . . . . . . . . . . . . . . . . 3 64 3.1. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 4 65 3.2. Prefixes in Data Node Names . . . . . . . . . . . . . . . 4 66 3.3. References in the Model . . . . . . . . . . . . . . . . . 5 67 4. The Design of YANG Data Model . . . . . . . . . . . . . . . . 5 68 4.1. The Overview of PCEP SRv6 Data Model . . . . . . . . . . 5 69 4.2. The Overview of PCEP SR Policy Data Model . . . . . . . . 6 70 5. The YANG Modules . . . . . . . . . . . . . . . . . . . . . . 7 71 5.1. ietf-pcep-srv6 module . . . . . . . . . . . . . . . . . . 7 72 5.2. ietf-pcep-srpolicy module . . . . . . . . . . . . . . . . 12 73 6. Security Considerations . . . . . . . . . . . . . . . . . . . 16 74 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 75 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 76 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 77 9.1. Normative References . . . . . . . . . . . . . . . . . . 18 78 9.2. Informative References . . . . . . . . . . . . . . . . . 20 79 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 81 1. Introduction 83 The Path Computation Element (PCE) defined in [RFC4655] is an entity 84 that is capable of computing a network path or route based on a 85 network graph, and applying computational constraints. A Path 86 Computation Client (PCC) may make requests to a PCE for paths to be 87 computed. 89 PCEP is the communication protocol between a PCC and PCE and is 90 defined in [RFC5440]. PCEP interactions include path computation 91 requests and path computation replies as well as notifications of 92 specific states related to the use of a PCE in the context of 93 Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) 94 Traffic Engineering (TE). [RFC8231] specifies extensions to PCEP to 95 enable stateful control of MPLS TE LSPs. 97 [I-D.ietf-pce-segment-routing-ipv6] extends [RFC8664] to support SR 98 for IPv6 data plane. 100 [I-D.ietf-pce-pcep-yang] defines a YANG [RFC7950] data model for the 101 management of PCEP speakers. This document contains a specification 102 of the PCEP-SRv6 YANG module, "ietf-pcep-srv6" which provides the 103 PCEP-SRv6 [I-D.ietf-pce-segment-routing-ipv6] data model. This 104 document also contains the PCEP-SRPolicy YANG module, "ietf-pcep- 105 srpolicy" which provides a reference to SR Policy 106 [I-D.ietf-spring-segment-routing-policy]. 108 The PCEP operational state is included in the same tree as the PCEP 109 configuration consistent with Network Management Datastore 110 Architecture (NMDA) [RFC8342]. The origin of the data is indicated 111 as per the origin metadata annotation. 113 2. Requirements Language 115 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 116 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 117 "OPTIONAL" in this document are to be interpreted as described in BCP 118 14 [RFC2119] [RFC8174] when, and only when, they appear in all 119 capitals, as shown here. 121 3. Terminology and Notation 123 This document also uses the following terms defined in [RFC7420]: 125 * PCEP entity: a local PCEP speaker. 127 * PCEP peer: a remote PCEP speaker. 129 * PCEP speaker: where it is not necessary to distinguish between 130 local and remote. 132 Further, this document also uses the following terms defined in 133 [RFC8231] : 135 * Stateful PCE, Passive Stateful PCE, Active Stateful PCE. 137 * Delegation, Revocation, Redelegation. 139 * LSP State Report, Path Computation Report message (PCRpt). 141 * LSP State Update, Path Computation Update message (PCUpd). 143 [RFC8281] : 145 * PCE-initiated LSP, Path Computation LSP Initiate Message 146 (PCInitiate). 148 [RFC8408] : 150 * Path Setup Type (PST). 152 [RFC8664] : 154 * Segment Routing (SR). 156 [I-D.ietf-pce-segment-routing-ipv6] : 158 * Segment Routing in IPv6 (SRv6). 160 [I-D.ietf-spring-segment-routing-policy] : 162 * SR Policy. 164 3.1. Tree Diagrams 166 A simplified graphical representation of the data model is used in 167 this document. The meaning of the symbols in these diagrams is 168 defined in [RFC8340]. 170 3.2. Prefixes in Data Node Names 172 In this document, names of data nodes and other data model objects 173 are often used without a prefix, as long as it is clear from the 174 context in which YANG module each name is defined. Otherwise, names 175 are prefixed using the standard prefix associated with the 176 corresponding YANG module, as shown in Table 1. 178 +============+=================+==================================+ 179 | Prefix | YANG module | Reference | 180 +============+=================+==================================+ 181 | te-types | ietf-te-types | [RFC8776] | 182 +------------+-----------------+----------------------------------+ 183 | pcep | ietf-pcep | [I-D.ietf-pce-pcep-yang] | 184 +------------+-----------------+----------------------------------+ 185 | srv6-types | ietf-srv6-types | [I-D.ietf-spring-srv6-yang] | 186 +------------+-----------------+----------------------------------+ 187 | sr-policy | ietf-sr-policy | [I-D.ietf-spring-sr-policy-yang] | 188 +------------+-----------------+----------------------------------+ 189 | rt | ietf-routing | [RFC8349] | 190 +------------+-----------------+----------------------------------+ 192 Table 1: Prefixes and corresponding YANG modules 194 3.3. References in the Model 196 Following additional documents are referenced in the model defined in 197 this document - 199 +=====================+==========================================+ 200 | Title | Reference | 201 +=====================+==========================================+ 202 | PCEP Extensions for | [I-D.ietf-pce-segment-routing-ipv6] | 203 | Segment Routing | | 204 | leveraging the IPv6 | | 205 | data plane | | 206 +---------------------+------------------------------------------+ 207 | Carrying Binding | [I-D.ietf-pce-binding-label-sid] | 208 | Label/Segment | | 209 | Identifier (SID) in | | 210 | PCE-based Networks | | 211 +---------------------+------------------------------------------+ 212 | Segment Routing | [I-D.ietf-spring-segment-routing-policy] | 213 | Policy Architecture | | 214 +---------------------+------------------------------------------+ 216 Table 2: References in the YANG modules 218 4. The Design of YANG Data Model 220 4.1. The Overview of PCEP SRv6 Data Model 222 The PCEP-SRv6 YANG module defined in this document has all the common 223 building blocks for the PCEP-SRv6 extension. 225 module: ietf-pcep-srv6 227 augment /pcep:pcep/pcep:entity/pcep:capability: 228 +--rw srv6 {srv6}? 229 | +--rw enabled? boolean 230 | +--rw nai? boolean 231 | +--rw msd-limit? boolean 232 | +--rw srv6-msd* [msd-type] 233 | +--rw msd-type uint8 234 | +--rw msd-value? uint8 235 +--rw sid-str {sid-str}? 236 +--rw lb? uint8 237 +--rw ln? uint8 238 +--rw fn? uint8 239 +--rw an? uint8 240 augment /pcep:pcep/pcep:entity/pcep:peers/pcep:peer 241 /pcep:capability: 242 +--rw srv6 {srv6}? 243 +--rw enabled? boolean 244 +--rw nai? boolean 245 +--rw msd-limit? boolean 246 +--rw srv6-msd* [msd-type] 247 +--rw msd-type uint8 248 +--rw msd-value? uint8 249 augment /pcep:pcep/pcep:entity/pcep:lsp-db/pcep:lsp: 250 +--ro srv6 {srv6}? 251 +--ro segment-list 252 +--ro segment* [index] 253 +--ro index uint32 254 +--ro sid-value? srv6-types:srv6-sid 255 +--ro sid-str {sid-str}? 256 | +--ro lb? uint8 257 | +--ro ln? uint8 258 | +--ro fn? uint8 259 | +--ro an? uint8 260 +--ro endpoint-behavior? identityref 262 4.2. The Overview of PCEP SR Policy Data Model 264 The PCEP-SRPolicy YANG module defined in this document has all the 265 common building blocks for the PCEP-SR Policy extension. 267 module: ietf-pcep-srpolicy 269 augment /pcep:pcep/pcep:entity/pcep:lsp-db/pcep:lsp: 270 +--ro sr-policy 271 +--ro color? leafref 272 +--ro endpoint? leafref 273 +--ro protocol-origin? leafref 274 +--ro originator? leafref 275 +--ro discriminator? leafref 277 The sr-policy container is applicable for both SR-MPLS and SRv6. 279 5. The YANG Modules 281 5.1. ietf-pcep-srv6 module 283 RFC Ed.: In this section, replace all occurrences of 'XXXX' with the 284 actual RFC number and all occurrences of the revision date below with 285 the date of RFC publication (and remove this note). 287 file "ietf-pcep-srv6@2022-03-07.yang" 288 module ietf-pcep-srv6 { 289 yang-version 1.1; 290 namespace "urn:ietf:params:xml:ns:yang:ietf-pcep-srv6"; 291 prefix pcep-srv6; 293 import ietf-srv6-types { 294 prefix srv6-types; 295 reference 296 "I-D.ietf-spring-srv6-yang: YANG Data Model for SRv6 297 Base and Static"; 298 } 299 import ietf-te-types { 300 prefix te-types; 301 reference 302 "RFC 8776: Common YANG Data Types for Traffic Engineering"; 303 } 304 import ietf-pcep { 305 prefix pcep; 306 reference 307 "I-D.ietf-pce-pcep-yang: A YANG Data Model for Path 308 Computation Element Communications Protocol (PCEP)"; 309 } 311 organization 312 "IETF PCE (Path Computation Element) Working Group"; 313 contact 314 "WG Web: 315 WG List: 316 Editor: Cheng Li 317 318 Shuping Peng 319 "; 320 description 321 "The YANG module augments the PCEP YANG operational 322 model with SRv6. 324 Copyright (c) 2022 IETF Trust and the persons identified as 325 authors of the code. All rights reserved. 327 Redistribution and use in source and binary forms, with or 328 without modification, is permitted pursuant to, and subject 329 to the license terms contained in, the Revised BSD License 330 set forth in Section 4.c of the IETF Trust's Legal Provisions 331 Relating to IETF Documents 332 (https://trustee.ietf.org/license-info). 334 This version of this YANG module is part of RFC XXXX; see the 335 RFC itself for full legal notices."; 337 revision 2022-03-07 { 338 description 339 "Initial revision."; 340 reference 341 "RFC XXXX: A YANG Data Model for Segment Routing (SR) Policy 342 and SRv6 support in Path Computation Element Communications 343 Protocol (PCEP)"; 344 } 346 /* Features */ 348 feature srv6 { 349 description 350 "Support Segment Routing in IPv6 (SRv6) for PCE."; 351 reference 352 "I-D.ietf-pce-segment-routing-ipv6: PCEP Extensions 353 for Segment Routing leveraging the IPv6 data plane"; 354 } 356 feature bsid { 357 description 358 "Support Binding SID for PCE."; 359 reference 360 "I-D.ietf-pce-binding-label-sid: Carrying Binding 361 Label/Segment Identifier (SID) in PCE-based Networks."; 362 } 363 feature sid-str { 364 description 365 "Support for SID Structure"; 366 reference 367 "I-D.ietf-pce-segment-routing-ipv6: PCEP Extensions 368 for Segment Routing leveraging the IPv6 data plane"; 369 } 371 /* Identity */ 373 identity path-setup-srv6 { 374 if-feature "srv6"; 375 base te-types:path-signaling-type; 376 description 377 "SRv6 path setup type"; 378 } 380 /* Groupings */ 382 grouping srv6-msd { 383 description 384 "SRv6 MSD"; 385 leaf msd-type { 386 type uint8; 387 description 388 "SRv6 Maximum Segment Depth (MSD) Type"; 389 } 390 leaf msd-value { 391 type uint8; 392 description 393 "SRv6 MSD value for the type"; 394 } 395 reference 396 "I-D.ietf-pce-segment-routing-ipv6: PCEP Extensions 397 for Segment Routing leveraging the IPv6 data plane"; 398 } 400 grouping srv6 { 401 description 402 "SRv6"; 403 container srv6 { 404 if-feature "srv6"; 405 description 406 "If SRv6 is supported"; 407 leaf enabled { 408 type boolean; 409 description 410 "Enabled or Disabled; set to true when 411 Enabled"; 412 } 413 leaf nai { 414 type boolean; 415 default "false"; 416 description 417 "True indicates capability to resolve Node or 418 Adjacency Identifier (NAI) to SRv6 Segment 419 Identifier (SID)"; 420 } 421 leaf msd-limit { 422 type boolean; 423 default "false"; 424 description 425 "True indicates no limit on MSD, the 426 list srv6-msd is ignored"; 427 } 428 list srv6-msd { 429 key "msd-type"; 430 description 431 "list of SRv6 MSD"; 432 uses srv6-msd; 433 } 434 } 435 } 437 grouping segment-list { 438 description 439 "Segment list grouping"; 440 container segment-list { 441 description 442 "Segments for given segment list"; 443 list segment { 444 key "index"; 445 description 446 "Configure Segment/hop at the index"; 447 uses segment-properties; 448 } 449 } 450 } 452 grouping segment-properties { 453 description 454 "Segment properties grouping"; 455 leaf index { 456 type uint32; 457 description 458 "Segment index"; 460 } 461 leaf sid-value { 462 type srv6-types:srv6-sid; 463 description 464 "SRv6 SID value"; 465 } 466 uses sid-str; 467 leaf endpoint-behavior { 468 type identityref { 469 base srv6-types:srv6-endpoint-type; 470 } 471 description 472 "The behavior associated with the SRv6 SIDs."; 473 } 474 /*Query: Add NAI?*/ 475 } 477 grouping sid-str { 478 description 479 "The default SID Structure"; 480 container sid-str { 481 if-feature "sid-str"; 482 description 483 "The default SID Structure"; 484 leaf lb { 485 type uint8; 486 description 487 "SRv6 SID Locator Block length in bits"; 488 } 489 leaf ln { 490 type uint8; 491 description 492 "SRv6 SID Locator Node length in bits"; 493 } 494 leaf fn { 495 type uint8; 496 description 497 "SRv6 SID Function length in bits"; 498 } 499 leaf an { 500 type uint8; 501 description 502 "SRv6 SID Arguments length in bits"; 503 } 504 } 505 } 507 /* 508 * Augment modules to add SRv6 509 */ 511 augment "/pcep:pcep/pcep:entity/pcep:capability" { 512 description 513 "Augmenting SRv6"; 514 uses srv6; 515 uses sid-str; 516 } 518 augment "/pcep:pcep/pcep:entity/pcep:peers/pcep:peer" 519 + "/pcep:capability" { 520 description 521 "Augmenting SRv6"; 522 uses srv6; 523 } 525 augment "/pcep:pcep/pcep:entity/pcep:lsp-db/pcep:lsp" { 526 description 527 "Augmenting SRv6"; 528 container srv6 { 529 when 530 "derived-from-or-self 531 (/pcep:pcep/pcep:entity/pcep:lsp-db/pcep:lsp/pcep:pst, 532 'path-setup-srv6')" { 533 description 534 "For SRv6 path"; 535 } 536 if-feature "srv6"; 537 uses segment-list; 538 description 539 "SRv6"; 540 } 541 } 542 } 543 545 5.2. ietf-pcep-srpolicy module 547 RFC Ed.: In this section, replace all occurrences of 'XXXX' with the 548 actual RFC number and all occurrences of the revision date below with 549 the date of RFC publication (and remove this note). 551 file "ietf-pcep-srpolicy@2022-03-07.yang" 552 module ietf-pcep-srpolicy { 553 yang-version 1.1; 554 namespace "urn:ietf:params:xml:ns:yang:ietf-pcep-srpolicy"; 555 prefix pcep-srp; 557 import ietf-pcep { 558 prefix pcep; 559 reference 560 "I-D.ietf-pce-pcep-yang: A YANG Data Model for Path 561 Computation Element Communications Protocol (PCEP)"; 562 } 563 import ietf-sr-policy { 564 prefix sr-policy; 565 reference 566 "I-D.ietf-spring-sr-policy-yang: YANG Data Model for 567 Segment Routing Policy"; 568 } 569 import ietf-routing { 570 prefix rt; 571 reference 572 "RFC 8349: A YANG Data Model for Routing Management"; 573 } 575 organization 576 "IETF PCE (Path Computation Element) Working Group"; 577 contact 578 "WG Web: 579 WG List: 580 Editor: Cheng Li 581 582 Shuping Peng 583 "; 584 description 585 "The YANG module augments the PCEP YANG model with SR Policy. 587 Copyright (c) 2022 IETF Trust and the persons identified as 588 authors of the code. All rights reserved. 590 Redistribution and use in source and binary forms, with or 591 without modification, is permitted pursuant to, and subject 592 to the license terms contained in, the Revised BSD License 593 set forth in Section 4.c of the IETF Trust's Legal Provisions 594 Relating to IETF Documents 595 (https://trustee.ietf.org/license-info). 597 This version of this YANG module is part of RFC XXXX; see the 598 RFC itself for full legal notices."; 600 revision 2022-03-07 { 601 description 602 "Initial revision."; 603 reference 604 "RFC XXXX: A YANG Data Model for Segment Routing (SR) Policy 605 and SRv6 support in Path Computation Element Communications 606 Protocol (PCEP)"; 607 } 609 /* Groupings */ 611 grouping sr-policy-cp { 612 description 613 "Segment Routing Policy grouping"; 614 // Editor's Note - headend is missig in SR Policy 615 // Yang mode 616 leaf color { 617 type leafref { 618 path "/rt:routing/sr-policy:segment-routing/" 619 + "sr-policy:traffic-engineering/sr-policy:" 620 + "policies/sr-policy:policy/sr-policy:" 621 + "color"; 622 } 623 description 624 "SR Policy Color"; 625 reference 626 "I-D.ietf-spring-segment-routing-policy: Segment 627 Routing Policy Architecture"; 628 } 629 leaf endpoint { 630 type leafref { 631 path "/rt:routing/sr-policy:segment-routing/" 632 + "sr-policy:traffic-engineering/sr-policy:" 633 + "policies/sr-policy:policy/sr-policy:" 634 + "endpoint"; 635 } 636 description 637 "SR Policy Endpoint"; 638 reference 639 "I-D.ietf-spring-segment-routing-policy: Segment 640 Routing Policy Architecture"; 641 } 642 leaf protocol-origin { 643 type leafref { 644 path "/rt:routing/sr-policy:segment-routing/" 645 + "sr-policy:traffic-engineering/sr-policy:" 646 + "policies/sr-policy:policy/sr-policy:" 647 + "candidate-paths/sr-policy:" 648 + "candidate-path/sr-policy:protocol-origin"; 649 } 650 must '(. = "pcep")' { 651 error-message "The protocol origin must be PCEP"; 652 } 653 description 654 "SR Policy Candidate Path Protocol"; 655 reference 656 "I-D.ietf-spring-segment-routing-policy: Segment 657 Routing Policy Architecture"; 658 } 659 leaf originator { 660 type leafref { 661 path "/rt:routing/sr-policy:segment-routing/" 662 + "sr-policy:traffic-engineering/sr-policy:" 663 + "policies/sr-policy:policy/sr-policy:" 664 + "candidate-paths/sr-policy:" 665 + "candidate-path/sr-policy:originator"; 666 } 667 description 668 "SR Policy Candidate Path Originator"; 669 reference 670 "I-D.ietf-spring-segment-routing-policy: Segment 671 Routing Policy Architecture"; 672 } 673 leaf discriminator { 674 type leafref { 675 path "/rt:routing/sr-policy:segment-routing/" 676 + "sr-policy:traffic-engineering/sr-policy:" 677 + "policies/sr-policy:policy/sr-policy:" 678 + "candidate-paths/sr-policy:" 679 + "candidate-path/sr-policy:discriminator"; 680 } 681 description 682 "SR Policy Candidate Path Discriminator"; 683 reference 684 "I-D.ietf-spring-segment-routing-policy: Segment 685 Routing Policy Architecture"; 686 } 687 } 689 augment "/pcep:pcep/pcep:entity/pcep:lsp-db/pcep:lsp" { 690 description 691 "Augmenting SR Policy"; 692 container sr-policy { 693 when 694 "derived-from-or-self 695 (/pcep:pcep/pcep:entity/pcep:lsp-db/pcep:lsp/pcep:pst, 696 'path-setup-sr') or 697 derived-from-or-self 698 (/pcep:pcep/pcep:entity/pcep:lsp-db/pcep:lsp/pcep:pst, 699 'path-setup-srv6')" { 700 description 701 "Applicable for SR or SRv6"; 702 } 703 uses sr-policy-cp; 704 description 705 "SR Policy Candidate Path"; 706 } 707 } 708 } 709 711 6. Security Considerations 713 The YANG module defined in this document is designed to be accessed 714 via network management protocol such as NETCONF [RFC6241] or RESTCONF 715 [RFC8040]. The lowest NETCONF layer is the secure transport layer 716 and the mandatory-to-implement secure transport is SSH [RFC6242]. 717 The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement 718 secure transport is TLS [RFC8446] 720 The NETCONF access control model [RFC8341] provides the means to 721 restrict access for particular NETCONF or RESTCONF users to a pre- 722 configured subset of all available NETCONF or RESTCONF protocol 723 operations and content. 725 There are a number of data nodes defined in the YANG module which are 726 writable/creatable/deletable (i.e., config true, which is the 727 default). These data nodes may be considered sensitive or vulnerable 728 in some network environments. Write operations (e.g., ) 729 to these data nodes without proper protection can have a negative 730 effect on network operations. These are the subtrees and data nodes 731 and their sensitivity/vulnerability: 733 /pcep:pcep/pcep:entity/pcep:capability/pcep-srv6:srv6 - configure 734 local SRv6 capability and parameters. 736 /pcep:pcep/pcep:entity/pcep:peers/pcep:peer/pcep:capability/pcep- 737 srv6:srv6 - configure peer's SRv6 capability and parameters. 739 Unauthorized access to above list can adversely affect the PCEP 740 session between the local entity and the peers. This may lead to 741 inability to compute new paths, stateful operations on the delegated 742 as well as PCE-initiated LSPs. 744 Some of the readable data nodes in this YANG module may be considered 745 sensitive or vulnerable in some network environments. It is thus 746 important to control read access (e.g., via get, get-config, or 747 notification) to these data nodes. These are the subtrees and data 748 nodes and their sensitivity/vulnerability: 750 /pcep:pcep/pcep:entity/pcep:lsp-db/pcep:lsp/pcep-srv6:srv6 - The 751 SRv6 SID in the network. Unauthorized access to this could 752 provide entire path and network usage information. 754 /pcep:pcep/pcep:entity/pcep:lsp-db/pcep:lsp/pcep-srpolicy:sr- 755 policy - The reference to SR Policy. Unauthorized access to this 756 could provide SR Policy usage information. 758 7. IANA Considerations 760 This document registers a URI in the "IETF XML Registry" [RFC3688]. 761 Following the format in RFC 3688, the following registration has been 762 made. 764 URI: urn:ietf:params:xml:ns:yang:ietf-pcep-srv6 766 Registrant Contact: The PCE WG of the IETF. 768 XML: N/A; the requested URI is an XML namespace. 770 URI: urn:ietf:params:xml:ns:yang:ietf-pcep-srpolicy 772 Registrant Contact: The PCE WG of the IETF. 774 XML: N/A; the requested URI is an XML namespace. 776 This document registers a YANG module in the "YANG Module Names" 777 registry [RFC6020]. 779 Name: ietf-pcep-srv6 780 Namespace: urn:ietf:params:xml:ns:yang:ietf-pcep-srv6 781 Prefix: pcep-srv6 782 Reference: This I-D 784 Name: ietf-pcep-srpolicy 785 Namespace: urn:ietf:params:xml:ns:yang:ietf-pcep-srpolicy 786 Prefix: pcep-srp 787 Reference: This I-D 789 8. Acknowledgements 791 The authors would like to thank Dhruv Dhody for the initial YANG 792 model. 794 9. References 796 9.1. Normative References 798 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 799 Requirement Levels", BCP 14, RFC 2119, 800 DOI 10.17487/RFC2119, March 1997, 801 . 803 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 804 DOI 10.17487/RFC3688, January 2004, 805 . 807 [RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation 808 Element (PCE) Communication Protocol (PCEP)", RFC 5440, 809 DOI 10.17487/RFC5440, March 2009, 810 . 812 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 813 the Network Configuration Protocol (NETCONF)", RFC 6020, 814 DOI 10.17487/RFC6020, October 2010, 815 . 817 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 818 and A. Bierman, Ed., "Network Configuration Protocol 819 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 820 . 822 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 823 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 824 . 826 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 827 RFC 7950, DOI 10.17487/RFC7950, August 2016, 828 . 830 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 831 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 832 . 834 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 835 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 836 May 2017, . 838 [RFC8231] Crabbe, E., Minei, I., Medved, J., and R. Varga, "Path 839 Computation Element Communication Protocol (PCEP) 840 Extensions for Stateful PCE", RFC 8231, 841 DOI 10.17487/RFC8231, September 2017, 842 . 844 [RFC8281] Crabbe, E., Minei, I., Sivabalan, S., and R. Varga, "Path 845 Computation Element Communication Protocol (PCEP) 846 Extensions for PCE-Initiated LSP Setup in a Stateful PCE 847 Model", RFC 8281, DOI 10.17487/RFC8281, December 2017, 848 . 850 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 851 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 852 . 854 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 855 Access Control Model", STD 91, RFC 8341, 856 DOI 10.17487/RFC8341, March 2018, 857 . 859 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for 860 Routing Management (NMDA Version)", RFC 8349, 861 DOI 10.17487/RFC8349, March 2018, 862 . 864 [RFC8408] Sivabalan, S., Tantsura, J., Minei, I., Varga, R., and J. 865 Hardwick, "Conveying Path Setup Type in PCE Communication 866 Protocol (PCEP) Messages", RFC 8408, DOI 10.17487/RFC8408, 867 July 2018, . 869 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 870 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 871 . 873 [RFC8664] Sivabalan, S., Filsfils, C., Tantsura, J., Henderickx, W., 874 and J. Hardwick, "Path Computation Element Communication 875 Protocol (PCEP) Extensions for Segment Routing", RFC 8664, 876 DOI 10.17487/RFC8664, December 2019, 877 . 879 [RFC8776] Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, 880 "Common YANG Data Types for Traffic Engineering", 881 RFC 8776, DOI 10.17487/RFC8776, June 2020, 882 . 884 [I-D.ietf-spring-srv6-yang] 885 Raza, K., Agarwal, S., Liu, X., Hu, Z., Hussain, I., Shah, 886 H., Voyer, D., Matsushima, S., Horiba, K., Rajamanickam, 887 J., and A. AbdelSalam, "YANG Data Model for SRv6 Base and 888 Static", Work in Progress, Internet-Draft, draft-ietf- 889 spring-srv6-yang-01, 14 January 2022, 890 . 893 [I-D.ietf-pce-pcep-yang] 894 Dhody, D., Hardwick, J., Beeram, V. P., and J. Tantsura, 895 "A YANG Data Model for Path Computation Element 896 Communications Protocol (PCEP)", Work in Progress, 897 Internet-Draft, draft-ietf-pce-pcep-yang-18, 25 January 898 2022, . 901 [I-D.ietf-pce-segment-routing-ipv6] 902 Li, C., Negi, M., Sivabalan, S., Koldychev, M., 903 Kaladharan, P., and Y. Zhu, "PCEP Extensions for Segment 904 Routing leveraging the IPv6 data plane", Work in Progress, 905 Internet-Draft, draft-ietf-pce-segment-routing-ipv6-11, 10 906 January 2022, . 909 [I-D.ietf-spring-sr-policy-yang] 910 Raza, K., Sawaya, R., Shunwan, Z., Voyer, D., Durrani, M., 911 Matsushima, S., and V. P. Beeram, "YANG Data Model for 912 Segment Routing Policy", Work in Progress, Internet-Draft, 913 draft-ietf-spring-sr-policy-yang-01, 7 April 2021, 914 . 917 9.2. Informative References 919 [RFC4655] Farrel, A., Vasseur, J.-P., and J. Ash, "A Path 920 Computation Element (PCE)-Based Architecture", RFC 4655, 921 DOI 10.17487/RFC4655, August 2006, 922 . 924 [RFC7420] Koushik, A., Stephan, E., Zhao, Q., King, D., and J. 925 Hardwick, "Path Computation Element Communication Protocol 926 (PCEP) Management Information Base (MIB) Module", 927 RFC 7420, DOI 10.17487/RFC7420, December 2014, 928 . 930 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 931 and R. Wilton, "Network Management Datastore Architecture 932 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 933 . 935 [I-D.ietf-spring-segment-routing-policy] 936 Filsfils, C., Talaulikar, K., Voyer, D., Bogdanov, A., and 937 P. Mattes, "Segment Routing Policy Architecture", Work in 938 Progress, Internet-Draft, draft-ietf-spring-segment- 939 routing-policy-18, 17 February 2022, 940 . 943 [I-D.ietf-pce-binding-label-sid] 944 Sivabalan, S., Filsfils, C., Tantsura, J., Previdi, S., 945 and C. L. (editor), "Carrying Binding Label/Segment 946 Identifier (SID) in PCE-based Networks.", Work in 947 Progress, Internet-Draft, draft-ietf-pce-binding-label- 948 sid-14, 3 March 2022, . 951 Authors' Addresses 953 Cheng Li 954 Huawei Technologies 955 Huawei Campus, No. 156 Beiqing Rd. 956 Beijing 957 100095 958 China 959 Email: c.l@huawei.com 961 Siva Sivabalan 962 Ciena Corporation 963 Email: ssivabal@ciena.com 965 Shuping Peng 966 Huawei Technologies 967 Huawei Campus, No. 156 Beiqing Rd. 968 Beijing 969 100095 970 China 971 Email: pengshuping@huawei.com 973 Mike Koldychev 974 Cisco Systems, Inc. 976 Email: mkoldych@cisco.com 978 Luc-Fabrice Ndifor 979 MTN Cameroon 980 Cameroon 981 Email: Luc-Fabrice.Ndifor@mtn.com