idnits 2.17.1 draft-li-pce-pcep-srv6-yang-02.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 (November 1, 2020) is 1262 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 (-23) exists of draft-ietf-pce-pcep-yang-14 == Outdated reference: A later version (-25) exists of draft-ietf-pce-segment-routing-ipv6-06 == Outdated reference: A later version (-03) exists of draft-ietf-spring-sr-policy-yang-00 Summary: 0 errors (**), 0 flaws (~~), 5 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: May 5, 2021 Ciena Corporation 6 S. Peng 7 Huawei Technologies 8 M. Koldychev 9 Cisco Systems, Inc. 10 L. Ndifor 11 MTN Cameroon 12 November 1, 2020 14 A YANG Data Model for Segment Routing in IPv6 (SRv6) support in Path 15 Computation Element Communications Protocol (PCEP) 16 draft-li-pce-pcep-srv6-yang-02 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. The data model includes configuration data and state data 25 (status information and counters for the collection of statistics). 27 Status of This Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at https://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on May 5, 2021. 44 Copyright Notice 46 Copyright (c) 2020 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (https://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified 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 4. The Design of PCEP-SRv6 Data Model . . . . . . . . . . . . . 4 67 4.1. The Overview of PCEP SRv6 Data Model . . . . . . . . . . 4 68 5. PCEP-SRv6 YANG Modules . . . . . . . . . . . . . . . . . . . 5 69 5.1. ietf-pcep-srv6 module . . . . . . . . . . . . . . . . . . 5 70 6. Security Considerations . . . . . . . . . . . . . . . . . . . 11 71 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 72 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 73 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 74 9.1. Normative References . . . . . . . . . . . . . . . . . . 13 75 9.2. Informative References . . . . . . . . . . . . . . . . . 15 76 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 78 1. Introduction 80 The Path Computation Element (PCE) defined in [RFC4655] is an entity 81 that is capable of computing a network path or route based on a 82 network graph, and applying computational constraints. A Path 83 Computation Client (PCC) may make requests to a PCE for paths to be 84 computed. 86 PCEP is the communication protocol between a PCC and PCE and is 87 defined in [RFC5440]. PCEP interactions include path computation 88 requests and path computation replies as well as notifications of 89 specific states related to the use of a PCE in the context of 90 Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) 91 Traffic Engineering (TE). [RFC8231] specifies extensions to PCEP to 92 enable stateful control of MPLS TE LSPs. 94 [I-D.ietf-pce-segment-routing-ipv6] extends [RFC8664] to support SR 95 for IPv6 data plane. 97 [I-D.ietf-pce-pcep-yang] defines a YANG [RFC7950] data model for the 98 management of PCEP speakers. This document contains a specification 99 of the PCEP-SRv6 YANG module, "ietf-pcep-srv6" which provides the 100 PCEP-SRv6 [I-D.ietf-pce-segment-routing-ipv6] data model. 102 The PCEP operational state is included in the same tree as the PCEP 103 configuration consistent with Network Management Datastore 104 Architecture [RFC8342]. The origin of the data is indicated as per 105 the origin metadata annotation. 107 2. Requirements Language 109 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 110 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 111 "OPTIONAL" in this document are to be interpreted as described in BCP 112 14 [RFC2119] [RFC8174] when, and only when, they appear in all 113 capitals, as shown here. 115 3. Terminology and Notation 117 This document also uses the following terms defined in [RFC7420]: 119 o PCEP entity: a local PCEP speaker. 121 o PCEP peer: to refer to a remote PCEP speaker. 123 o PCEP speaker: where it is not necessary to distinguish between 124 local and remote. 126 Further, this document also uses the following terms defined in 127 [RFC8231] : 129 o Stateful PCE, Passive Stateful PCE, Active Stateful PCE 131 o Delegation, Revocation, Redelegation 133 o LSP State Report, Path Computation Report message (PCRpt). 135 o LSP State Update, Path Computation Update message (PCUpd). 137 [RFC8281] : 139 o PCE-initiated LSP, Path Computation LSP Initiate Message 140 (PCInitiate). 142 [RFC8408] : 144 o Path Setup Type (PST). 146 [RFC8664] : 148 o Segment Routing (SR). 150 [I-D.ietf-pce-segment-routing-ipv6] : 152 o Segment Routing in IPv6 (SRv6). 154 3.1. Tree Diagrams 156 A simplified graphical representation of the data model is used in 157 this document. The meaning of the symbols in these diagrams is 158 defined in [RFC8340]. 160 3.2. Prefixes in Data Node Names 162 In this document, names of data nodes and other data model objects 163 are often used without a prefix, as long as it is clear from the 164 context in which YANG module each name is defined. Otherwise, names 165 are prefixed using the standard prefix associated with the 166 corresponding YANG module, as shown in Table 1. 168 +------------+-----------------+----------------------------------+ 169 | Prefix | YANG module | Reference | 170 +------------+-----------------+----------------------------------+ 171 | te-types | ietf-te-types | [RFC8776] | 172 | pcep | ietf-pcep | [I-D.ietf-pce-pcep-yang] | 173 | srv6-types | ietf-srv6-types | [I-D.raza-spring-srv6-yang] | 174 | sr-policy | ietf-sr-policy | [I-D.ietf-spring-sr-policy-yang] | 175 | rt | ietf-routing | [RFC8349] | 176 +------------+-----------------+----------------------------------+ 178 Table 1: Prefixes and corresponding YANG modules 180 4. The Design of PCEP-SRv6 Data Model 182 4.1. The Overview of PCEP SRv6 Data Model 184 The PCEP-SRv6 YANG module defined in this document has all the common 185 building blocks for the PCEP-SRv6 extension. 187 module: ietf-pcep-srv6 188 augment /pcep:pcep/pcep:entity/pcep:capability: 189 +--rw srv6 {srv6}? 190 +--rw enabled? boolean 191 +--rw msd-limit? boolean 192 +--rw srv6-msd* [msd-type] 193 +--rw msd-type uint8 194 +--rw msd-value? uint8 195 augment /pcep:pcep/pcep:entity/pcep:peers/pcep:peer 196 /pcep:capability: 197 +--rw srv6 {srv6}? 198 +--rw enabled? boolean 199 +--rw msd-limit? boolean 200 +--rw srv6-msd* [msd-type] 201 +--rw msd-type uint8 202 +--rw msd-value? uint8 203 augment /pcep:pcep/pcep:entity/pcep:lsp-db/pcep:lsp: 204 +--ro srv6 {srv6}? 205 | +--ro segment-list 206 | +--ro segment* [index] 207 | +--ro index uint32 208 | +--ro sid-value? srv6-types:srv6-sid 209 +--ro sr-policy 210 +--ro color? leafref 211 +--ro endpoint? leafref 212 +--ro protocol-origin? leafref 213 +--ro originator? leafref 214 +--ro discriminator? leafref 216 The sr-policy container is applicable for both SR-MPLS and SRv6. 218 5. PCEP-SRv6 YANG Modules 220 5.1. ietf-pcep-srv6 module 222 RFC Ed.: In this section, replace all occurrences of 'XXXX' with the 223 actual RFC number and all occurrences of the revision date below with 224 the date of RFC publication (and remove this note). 226 file "ietf-pcep-srv6@2020-10-31.yang" 227 module ietf-pcep-srv6 { 228 yang-version 1.1; 229 namespace "urn:ietf:params:xml:ns:yang:ietf-pcep-srv6"; 230 prefix pcep-srv6; 232 import ietf-srv6-types { 233 prefix srv6-types; 234 reference 235 "I-D.raza-spring-srv6-yang: YANG Data Model for SRv6 236 Base and Static"; 237 } 238 import ietf-te-types { 239 prefix te-types; 240 reference 241 "RFC 8776: Common YANG Data Types for Traffic Engineering"; 242 } 243 import ietf-pcep { 244 prefix pcep; 245 reference 246 "I-D.ietf-pce-pcep-yang: A YANG Data Model for Path 247 Computation Element Communications Protocol (PCEP)"; 248 } 249 import ietf-sr-policy { 250 prefix sr-policy; 251 reference 252 "I-D.ietf-spring-sr-policy-yang: YANG Data Model for 253 Segment Routing Policy"; 254 } 255 import ietf-routing { 256 prefix rt; 257 reference 258 "RFC 8349: A YANG Data Model for Routing Management"; 259 } 261 organization 262 "IETF PCE (Path Computation Element) Working Group"; 263 contact 264 "WG Web: 265 WG List: 266 Editor: Cheng Li 267 "; 268 description 269 "The YANG module augments the PCEP YANG operational 270 model with SRv6. 272 Copyright (c) 2020 IETF Trust and the persons identified as 273 authors of the code. All rights reserved. 275 Redistribution and use in source and binary forms, with or 276 without modification, is permitted pursuant to, and subject 277 to the license terms contained in, the Simplified BSD License 278 set forth in Section 4.c of the IETF Trust's Legal Provisions 279 Relating to IETF Documents 280 (https://trustee.ietf.org/license-info). 282 This version of this YANG module is part of RFC XXXX; see the 283 RFC itself for full legal notices."; 285 revision 2020-10-31 { 286 description 287 "Initial revision."; 288 reference 289 "RFC XXXX: A YANG Data Model for Path Computation 290 Element Communications Protocol 291 (PCEP) - Segement Routing in IPv6 292 (SRv6)"; 293 } 295 /* Features */ 297 feature srv6 { 298 description 299 "Support Segment Routing in IPv6 (SRv6) for PCE."; 300 reference 301 "I-D.ietf-pce-segment-routing-ipv6: PCEP Extensions 302 for Segment Routing leveraging the IPv6 data plane"; 303 } 305 /* Identity */ 307 identity path-setup-srv6 { 308 if-feature "srv6"; 309 base te-types:path-signaling-type; 310 description 311 "SRv6 path setup type"; 312 } 314 /* Groupings */ 316 grouping srv6-msd { 317 description 318 "SRv6 MSD"; 319 leaf msd-type { 320 type uint8; 321 description 322 "SRv6 Maximum Segment Depth (MSD) Type"; 323 } 324 leaf msd-value { 325 type uint8; 326 description 327 "SRv6 MSD value for the type"; 328 } 329 } 330 grouping srv6 { 331 description 332 "SRv6"; 333 container srv6 { 334 if-feature "srv6"; 335 description 336 "If SRv6 is supported"; 337 leaf enabled { 338 type boolean; 339 description 340 "Enabled or Disabled"; 341 } 342 leaf msd-limit { 343 type boolean; 344 default "false"; 345 description 346 "True indicates no limit on MSD, the 347 list srv6-msd is ignored"; 348 } 349 list srv6-msd { 350 key "msd-type"; 351 description 352 "list of SRv6 MSD"; 353 uses srv6-msd; 354 } 355 } 356 } 358 grouping segment-list { 359 description 360 "Segment list grouping"; 361 container segment-list { 362 description 363 "Segments for given segment list"; 364 list segment { 365 key "index"; 366 description 367 "Configure Segment/hop at the index"; 368 uses segment-properties; 369 } 370 } 371 } 373 grouping segment-properties { 374 description 375 "Segment properties grouping"; 376 leaf index { 377 type uint32; 378 description 379 "Segment index"; 380 } 381 leaf sid-value { 382 type srv6-types:srv6-sid; 383 description 384 "SRv6 SID value"; 385 } 386 } 388 grouping sr-policy { 389 description 390 "Segment Routing Policy grouping"; 391 // Editor's Note - headend is missig in SR Policy 392 // Yang mode 393 leaf color { 394 type leafref { 395 path "/rt:routing/sr-policy:segment-routing/" 396 + "sr-policy:traffic-engineering/sr-policy:" 397 + "policies/sr-policy:policy/sr-policy:" 398 + "color"; 399 } 400 description 401 "SR Policy Color"; 402 reference 403 "I-D.ietf-spring-segment-routing-policy: Segment 404 Routing Policy Architecture"; 405 } 406 leaf endpoint { 407 type leafref { 408 path "/rt:routing/sr-policy:segment-routing/" 409 + "sr-policy:traffic-engineering/sr-policy:" 410 + "policies/sr-policy:policy/sr-policy:" 411 + "endpoint"; 412 } 413 description 414 "SR Policy Endpoint"; 415 reference 416 "I-D.ietf-spring-segment-routing-policy: Segment 417 Routing Policy Architecture"; 418 } 419 leaf protocol-origin { 420 type leafref { 421 path "/rt:routing/sr-policy:segment-routing/" 422 + "sr-policy:traffic-engineering/sr-policy:" 423 + "policies/sr-policy:policy/sr-policy:" 424 + "candidate-paths/sr-policy:" 425 + "candidate-path/sr-policy:protocol-origin"; 427 } 428 must '(. = "pcep")' { 429 error-message "The protocol origin must be PCEP"; 430 } 431 description 432 "SR Policy Candidate Path Protocol"; 433 reference 434 "I-D.ietf-spring-segment-routing-policy: Segment 435 Routing Policy Architecture"; 436 } 437 leaf originator { 438 type leafref { 439 path "/rt:routing/sr-policy:segment-routing/" 440 + "sr-policy:traffic-engineering/sr-policy:" 441 + "policies/sr-policy:policy/sr-policy:" 442 + "candidate-paths/sr-policy:" 443 + "candidate-path/sr-policy:originator"; 444 } 445 description 446 "SR Policy Candidate Path Originator"; 447 reference 448 "I-D.ietf-spring-segment-routing-policy: Segment 449 Routing Policy Architecture"; 450 } 451 leaf discriminator { 452 type leafref { 453 path "/rt:routing/sr-policy:segment-routing/" 454 + "sr-policy:traffic-engineering/sr-policy:" 455 + "policies/sr-policy:policy/sr-policy:" 456 + "candidate-paths/sr-policy:" 457 + "candidate-path/sr-policy:discriminator"; 458 } 459 description 460 "SR Policy Candidate Path Discriminator"; 461 reference 462 "I-D.ietf-spring-segment-routing-policy: Segment 463 Routing Policy Architecture"; 464 } 465 } 467 /* 468 * Augment modules to add SRv6 469 */ 471 augment "/pcep:pcep/pcep:entity/pcep:capability" { 472 description 473 "Augmenting SRv6"; 474 uses srv6; 476 } 478 augment 479 "/pcep:pcep/pcep:entity/pcep:peers/pcep:peer/pcep:capability" { 480 description 481 "Augmenting SRv6"; 482 uses srv6; 483 } 485 augment "/pcep:pcep/pcep:entity/pcep:lsp-db/pcep:lsp" { 486 description 487 "Augmenting SRv6"; 488 container srv6 { 489 when "/pcep:pcep/pcep:entity/pcep:lsp-db/pcep:lsp/pcep:pst 490 = 'path-setup-srv6'" { 491 description 492 "For SRv6 path"; 493 } 494 if-feature "srv6"; 495 uses segment-list; 496 description 497 "SRv6"; 498 } 499 container sr-policy { 500 when "/pcep:pcep/pcep:entity/pcep:lsp-db/pcep:lsp/pcep:pst 501 = 'te-types:path-setup-sr' or 502 /pcep:pcep/pcep:entity/pcep:lsp-db/pcep:lsp/pcep:pst 503 = 'path-setup-srv6'" { 504 description 505 "Applicable for SR or SRv6"; 506 } 507 uses sr-policy; 508 description 509 "SR Policy"; 510 } 511 } 512 } 514 516 6. Security Considerations 518 The YANG module defined in this document is designed to be accessed 519 via network management protocol such as NETCONF [RFC6241] or RESTCONF 520 [RFC8040]. The lowest NETCONF layer is the secure transport layer 521 and the mandatory-to-implement secure transport is SSH [RFC6242]. 523 The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement 524 secure transport is TLS [RFC8446] 526 The NETCONF access control model [RFC8341] provides the means to 527 restrict access for particular NETCONF or RESTCONF users to a pre- 528 configured subset of all available NETCONF or RESTCONF protocol 529 operations and content. 531 There are a number of data nodes defined in the YANG module which are 532 writable/creatable/deletable (i.e., config true, which is the 533 default). These data nodes may be considered sensitive or vulnerable 534 in some network environments. Write operations (e.g., ) 535 to these data nodes without proper protection can have a negative 536 effect on network operations. These are the subtrees and data nodes 537 and their sensitivity/vulnerability: 539 /pcep:pcep/pcep:entity/pcep:capability/pcep-srv6:srv6 - configure 540 local SRv6 capability and parameters. 542 /pcep:pcep/pcep:entity/pcep:peers/pcep:peer/pcep:capability/pcep- 543 srv6:srv6 - configure peer's SRv6 capability and parameters. 545 Unauthorized access to above list can adversely affect the PCEP 546 session between the local entity and the peers. This may lead to 547 inability to compute new paths, stateful operations on the delegated 548 as well as PCE-initiated LSPs. 550 Some of the readable data nodes in this YANG module may be considered 551 sensitive or vulnerable in some network environments. It is thus 552 important to control read access (e.g., via get, get-config, or 553 notification) to these data nodes. These are the subtrees and data 554 nodes and their sensitivity/vulnerability: 556 /pcep:pcep/pcep:entity/pcep:lsp-db/pcep:lsp/pcep-srv6:srv6 - The 557 SRv6 SID in the network. Unauthorized access to this could 558 provide entire path and network usage information. 560 /pcep:pcep/pcep:entity/pcep:lsp-db/pcep:lsp/pcep-srv6:sr-policy - 561 The reference to SR Policy. Unauthorized access to this could 562 provide SR Policy usage information. 564 7. IANA Considerations 566 This document registers a URI in the "IETF XML Registry" [RFC3688]. 567 Following the format in RFC 3688, the following registration has been 568 made. 570 URI: urn:ietf:params:xml:ns:yang:ietf-pcep-srv6 571 Registrant Contact: The PCE WG of the IETF. 573 XML: N/A; the requested URI is an XML namespace. 575 This document registers a YANG module in the "YANG Module Names" 576 registry [RFC6020]. 578 Name: ietf-pcep-srv6 579 Namespace: urn:ietf:params:xml:ns:yang:ietf-pcep-srv6 580 Prefix: pcep-srv6 581 Reference: This I-D 583 8. Acknowledgements 585 The authors would like to thank Dhruv Dhody for the initial YANG 586 model. 588 9. References 590 9.1. Normative References 592 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 593 Requirement Levels", BCP 14, RFC 2119, 594 DOI 10.17487/RFC2119, March 1997, 595 . 597 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 598 DOI 10.17487/RFC3688, January 2004, 599 . 601 [RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation 602 Element (PCE) Communication Protocol (PCEP)", RFC 5440, 603 DOI 10.17487/RFC5440, March 2009, 604 . 606 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 607 the Network Configuration Protocol (NETCONF)", RFC 6020, 608 DOI 10.17487/RFC6020, October 2010, 609 . 611 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 612 and A. Bierman, Ed., "Network Configuration Protocol 613 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 614 . 616 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 617 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 618 . 620 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 621 RFC 7950, DOI 10.17487/RFC7950, August 2016, 622 . 624 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 625 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 626 . 628 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 629 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 630 May 2017, . 632 [RFC8231] Crabbe, E., Minei, I., Medved, J., and R. Varga, "Path 633 Computation Element Communication Protocol (PCEP) 634 Extensions for Stateful PCE", RFC 8231, 635 DOI 10.17487/RFC8231, September 2017, 636 . 638 [RFC8281] Crabbe, E., Minei, I., Sivabalan, S., and R. Varga, "Path 639 Computation Element Communication Protocol (PCEP) 640 Extensions for PCE-Initiated LSP Setup in a Stateful PCE 641 Model", RFC 8281, DOI 10.17487/RFC8281, December 2017, 642 . 644 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 645 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 646 . 648 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 649 Access Control Model", STD 91, RFC 8341, 650 DOI 10.17487/RFC8341, March 2018, 651 . 653 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for 654 Routing Management (NMDA Version)", RFC 8349, 655 DOI 10.17487/RFC8349, March 2018, 656 . 658 [RFC8408] Sivabalan, S., Tantsura, J., Minei, I., Varga, R., and J. 659 Hardwick, "Conveying Path Setup Type in PCE Communication 660 Protocol (PCEP) Messages", RFC 8408, DOI 10.17487/RFC8408, 661 July 2018, . 663 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 664 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 665 . 667 [RFC8664] Sivabalan, S., Filsfils, C., Tantsura, J., Henderickx, W., 668 and J. Hardwick, "Path Computation Element Communication 669 Protocol (PCEP) Extensions for Segment Routing", RFC 8664, 670 DOI 10.17487/RFC8664, December 2019, 671 . 673 [RFC8776] Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, 674 "Common YANG Data Types for Traffic Engineering", 675 RFC 8776, DOI 10.17487/RFC8776, June 2020, 676 . 678 [I-D.raza-spring-srv6-yang] 679 Raza, K., Agarwal, S., Liu, X., Hu, Z., Hussain, I., Shah, 680 H., Voyer, D., Matsushima, S., Horiba, K., Elmalky, H., 681 Abdelsalam, A., and J. Rajamanickam, "YANG Data Model for 682 SRv6 Base and Static", draft-raza-spring-srv6-yang-06 683 (work in progress), July 2020. 685 [I-D.ietf-pce-pcep-yang] 686 Dhody, D., Hardwick, J., Beeram, V., and J. Tantsura, "A 687 YANG Data Model for Path Computation Element 688 Communications Protocol (PCEP)", draft-ietf-pce-pcep- 689 yang-14 (work in progress), July 2020. 691 [I-D.ietf-pce-segment-routing-ipv6] 692 Li, C., Negi, M., Koldychev, M., Kaladharan, P., and Y. 693 Zhu, "PCEP Extensions for Segment Routing leveraging the 694 IPv6 data plane", draft-ietf-pce-segment-routing-ipv6-06 695 (work in progress), July 2020. 697 [I-D.ietf-spring-sr-policy-yang] 698 Raza, K., Sawaya, R., Shunwan, Z., Voyer, D., Durrani, M., 699 Matsushima, S., and V. Beeram, "YANG Data Model for 700 Segment Routing Policy", draft-ietf-spring-sr-policy- 701 yang-00 (work in progress), September 2020. 703 9.2. Informative References 705 [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation 706 Element (PCE)-Based Architecture", RFC 4655, 707 DOI 10.17487/RFC4655, August 2006, 708 . 710 [RFC7420] Koushik, A., Stephan, E., Zhao, Q., King, D., and J. 711 Hardwick, "Path Computation Element Communication Protocol 712 (PCEP) Management Information Base (MIB) Module", 713 RFC 7420, DOI 10.17487/RFC7420, December 2014, 714 . 716 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 717 and R. Wilton, "Network Management Datastore Architecture 718 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 719 . 721 Authors' Addresses 723 Cheng Li 724 Huawei Technologies 725 Huawei Campus, No. 156 Beiqing Rd. 726 Beijing 100095 727 China 729 EMail: c.l@huawei.com 731 Siva Sivabalan 732 Ciena Corporation 734 EMail: ssivabal@ciena.com 736 Shuping Peng 737 Huawei Technologies 738 Huawei Campus, No. 156 Beiqing Rd. 739 Beijing 100095 740 China 742 EMail: pengshuping@huawei.com 744 Mike Koldychev 745 Cisco Systems, Inc. 747 EMail: mkoldych@cisco.com 749 Luc-Fabrice Ndifor 750 MTN Cameroon 751 Cameroon 753 EMail: Luc-Fabrice.Ndifor@mtn.com