rfc9753v3.txt   rfc9753.txt 
Internet Engineering Task Force (IETF) C. Li Internet Engineering Task Force (IETF) C. Li
Request for Comments: 9753 H. Zheng Request for Comments: 9753 H. Zheng
Updates: 8231 Huawei Technologies Updates: 8231 Huawei Technologies
Category: Standards Track S. Litkowski Category: Standards Track S. Litkowski
ISSN: 2070-1721 Cisco ISSN: 2070-1721 Cisco
March 2025 April 2025
Extension for Stateful PCE to Allow Optional Processing of Path Extension for Stateful PCE to Allow Optional Processing of Path
Computation Element Communication Protocol (PCEP) Objects Computation Element Communication Protocol (PCEP) Objects
Abstract Abstract
This document introduces a mechanism to mark some of the Path This document introduces a mechanism to mark some of the Path
Computation Element Communication Protocol (PCEP) objects as optional Computation Element Communication Protocol (PCEP) objects as optional
during PCEP message exchange, so the stateful Path Computation during PCEP message exchange, so the stateful Path Computation
Element (PCE) model can relax some constraints during path Element (PCE) model can relax some constraints during path
skipping to change at line 77 skipping to change at line 77
4. Security Considerations 4. Security Considerations
5. IANA Considerations 5. IANA Considerations
5.1. STATEFUL-PCE-CAPABILITY TLV 5.1. STATEFUL-PCE-CAPABILITY TLV
6. Manageability Considerations 6. Manageability Considerations
6.1. Control of Function and Policy 6.1. Control of Function and Policy
6.2. Information and Data Models 6.2. Information and Data Models
6.3. Liveness Detection and Monitoring 6.3. Liveness Detection and Monitoring
6.4. Verify Correct Operations 6.4. Verify Correct Operations
6.5. Requirements on Other Protocols 6.5. Requirements on Other Protocols
6.6. Impact on Network Operations 6.6. Impact on Network Operations
7. Acknowledgments 7. References
8. References 7.1. Normative References
8.1. Normative References 7.2. Informative References
8.2. Informative References Acknowledgments
Contributors Contributors
Authors' Addresses Authors' Addresses
1. Introduction 1. Introduction
[RFC5440] describes the Path Computation Element Communication [RFC5440] describes the Path Computation Element Communication
Protocol (PCEP), which enables communication between a Path Protocol (PCEP), which enables communication between a Path
Computation Client (PCC) and a Path Control Element (PCE), or between Computation Client (PCC) and a Path Control Element (PCE), or between
two PCEs based on the PCE architecture [RFC4655]. two PCEs based on the PCE architecture [RFC4655].
skipping to change at line 385 skipping to change at line 385
6.5. Requirements on Other Protocols 6.5. Requirements on Other Protocols
Mechanisms defined in this document do not imply any new requirements Mechanisms defined in this document do not imply any new requirements
on other protocols. on other protocols.
6.6. Impact on Network Operations 6.6. Impact on Network Operations
Mechanisms defined in this document do not have any impact on network Mechanisms defined in this document do not have any impact on network
operations in addition to those already listed in [RFC5440]. operations in addition to those already listed in [RFC5440].
7. Acknowledgments 7. References
Thanks to Jonathan Hardwick for the discussion and suggestions around
this document.
Thanks to Oscar Gonzalez de Dios, Mike Koldychev, Samuel Sidor, and
Peng Shaofu for their review comments.
8. References
8.1. Normative References 7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation [RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation
Element (PCE) Communication Protocol (PCEP)", RFC 5440, Element (PCE) Communication Protocol (PCEP)", RFC 5440,
DOI 10.17487/RFC5440, March 2009, DOI 10.17487/RFC5440, March 2009,
<https://www.rfc-editor.org/info/rfc5440>. <https://www.rfc-editor.org/info/rfc5440>.
skipping to change at line 429 skipping to change at line 421
Path Computation Element Communication Protocol (PCEP)", Path Computation Element Communication Protocol (PCEP)",
RFC 8253, DOI 10.17487/RFC8253, October 2017, RFC 8253, DOI 10.17487/RFC8253, October 2017,
<https://www.rfc-editor.org/info/rfc8253>. <https://www.rfc-editor.org/info/rfc8253>.
[RFC8281] Crabbe, E., Minei, I., Sivabalan, S., and R. Varga, "Path [RFC8281] Crabbe, E., Minei, I., Sivabalan, S., and R. Varga, "Path
Computation Element Communication Protocol (PCEP) Computation Element Communication Protocol (PCEP)
Extensions for PCE-Initiated LSP Setup in a Stateful PCE Extensions for PCE-Initiated LSP Setup in a Stateful PCE
Model", RFC 8281, DOI 10.17487/RFC8281, December 2017, Model", RFC 8281, DOI 10.17487/RFC8281, December 2017,
<https://www.rfc-editor.org/info/rfc8281>. <https://www.rfc-editor.org/info/rfc8281>.
8.2. Informative References 7.2. Informative References
[PCEP-YANG] [PCEP-YANG]
Dhody, D., Ed., Beeram, V. P., Hardwick, J., and J. Dhody, D., Ed., Beeram, V. P., Hardwick, J., and J.
Tantsura, "A YANG Data Model for Path Computation Element Tantsura, "A YANG Data Model for Path Computation Element
Communications Protocol (PCEP)", Work in Progress, Communications Protocol (PCEP)", Work in Progress,
Internet-Draft, draft-ietf-pce-pcep-yang-30, 26 January Internet-Draft, draft-ietf-pce-pcep-yang-30, 26 January
2025, <https://datatracker.ietf.org/doc/html/draft-ietf- 2025, <https://datatracker.ietf.org/doc/html/draft-ietf-
pce-pcep-yang-30>. pce-pcep-yang-30>.
[RFC4655] Farrel, A., Vasseur, J.-P., and J. Ash, "A Path [RFC4655] Farrel, A., Vasseur, J.-P., and J. Ash, "A Path
skipping to change at line 461 skipping to change at line 453
Protocol (PCEP) to Compute Service-Aware Label Switched Protocol (PCEP) to Compute Service-Aware Label Switched
Paths (LSPs)", RFC 8233, DOI 10.17487/RFC8233, September Paths (LSPs)", RFC 8233, DOI 10.17487/RFC8233, September
2017, <https://www.rfc-editor.org/info/rfc8233>. 2017, <https://www.rfc-editor.org/info/rfc8233>.
[RFC9325] Sheffer, Y., Saint-Andre, P., and T. Fossati, [RFC9325] Sheffer, Y., Saint-Andre, P., and T. Fossati,
"Recommendations for Secure Use of Transport Layer "Recommendations for Secure Use of Transport Layer
Security (TLS) and Datagram Transport Layer Security Security (TLS) and Datagram Transport Layer Security
(DTLS)", BCP 195, RFC 9325, DOI 10.17487/RFC9325, November (DTLS)", BCP 195, RFC 9325, DOI 10.17487/RFC9325, November
2022, <https://www.rfc-editor.org/info/rfc9325>. 2022, <https://www.rfc-editor.org/info/rfc9325>.
Acknowledgments
Thanks to Jonathan Hardwick for the discussion and suggestions around
this document.
Thanks to Oscar Gonzalez de Dios, Mike Koldychev, Samuel Sidor, and
Peng Shaofu for their review comments.
Contributors Contributors
Dhruv Dhody Dhruv Dhody
Huawei Huawei
India India
Email: dhruv.ietf@gmail.com Email: dhruv.ietf@gmail.com
Authors' Addresses Authors' Addresses
Cheng Li Cheng Li
 End of changes. 6 change blocks. 
16 lines changed or deleted 16 lines changed or added

This html diff was produced by rfcdiff 1.48.