| < draft-dhody-pce-stateful-pce-vendor-13.txt | draft-dhody-pce-stateful-pce-vendor-14.txt > | |||
|---|---|---|---|---|
| PCE Working Group C. Li | PCE Working Group C. Li | |||
| Internet-Draft H. Zheng | Internet-Draft H. Zheng | |||
| Intended status: Standards Track Huawei Technologies | Intended status: Standards Track Huawei Technologies | |||
| Expires: 23 April 2022 S. Sivabalan | Expires: 21 October 2022 S. Sivabalan | |||
| Ciena | Ciena | |||
| S. Sidor | S. Sidor | |||
| Z. Ali | Z. Ali | |||
| Cisco Systems, Inc. | Cisco Systems, Inc. | |||
| 20 October 2021 | 19 April 2022 | |||
| Conveying Vendor-Specific Information in the Path Computation Element | Conveying Vendor-Specific Information in the Path Computation Element | |||
| (PCE) Communication Protocol (PCEP) extensions for Stateful PCE. | (PCE) Communication Protocol (PCEP) extensions for Stateful PCE. | |||
| draft-dhody-pce-stateful-pce-vendor-13 | draft-dhody-pce-stateful-pce-vendor-14 | |||
| Abstract | Abstract | |||
| A Stateful Path Computation Element (PCE) maintains information on | A Stateful Path Computation Element (PCE) maintains information on | |||
| the current network state, including: computed Label Switched Path | the current network state, including: computed Label Switched Path | |||
| (LSPs), reserved resources within the network, and the pending path | (LSPs), reserved resources within the network, and the pending path | |||
| computation requests. This information may then be considered when | computation requests. This information may then be considered when | |||
| computing new traffic engineered LSPs, and for the associated and the | computing new traffic engineered LSPs, and for the associated and the | |||
| dependent LSPs, received from a Path Computation Client (PCC). | dependent LSPs, received from a Path Computation Client (PCC). | |||
| skipping to change at page 1, line 46 ¶ | skipping to change at page 1, line 46 ¶ | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at https://datatracker.ietf.org/drafts/current/. | Drafts is at https://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on 23 April 2022. | This Internet-Draft will expire on 21 October 2022. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2021 IETF Trust and the persons identified as the | Copyright (c) 2022 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents (https://trustee.ietf.org/ | Provisions Relating to IETF Documents (https://trustee.ietf.org/ | |||
| license-info) in effect on the date of publication of this document. | license-info) in effect on the date of publication of this document. | |||
| Please review these documents carefully, as they describe your rights | Please review these documents carefully, as they describe your rights | |||
| and restrictions with respect to this document. Code Components | and restrictions with respect to this document. Code Components | |||
| extracted from this document must include Simplified BSD License text | extracted from this document must include Revised BSD License text as | |||
| as described in Section 4.e of the Trust Legal Provisions and are | described in Section 4.e of the Trust Legal Provisions and are | |||
| provided without warranty as described in the Simplified BSD License. | provided without warranty as described in the Revised BSD License. | |||
| Table of Contents | Table of Contents | |||
| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | |||
| 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 | 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 | |||
| 2. Procedures for the Vendor Information Object . . . . . . . . 3 | 2. Procedures for the Vendor Information Object . . . . . . . . 3 | |||
| 3. Procedures for the Vendor Information TLV . . . . . . . . . . 6 | 3. Procedures for the Vendor Information TLV . . . . . . . . . . 6 | |||
| 4. Vendor Information Object and TLV . . . . . . . . . . . . . . 6 | 4. Vendor Information Object and TLV . . . . . . . . . . . . . . 6 | |||
| 5. Manageability Considerations . . . . . . . . . . . . . . . . 7 | 5. Manageability Considerations . . . . . . . . . . . . . . . . 7 | |||
| 5.1. Control of Function and Policy . . . . . . . . . . . . . 7 | 5.1. Control of Function and Policy . . . . . . . . . . . . . 7 | |||
| skipping to change at page 10, line 17 ¶ | skipping to change at page 10, line 17 ¶ | |||
| 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>. | |||
| 10.2. Informative References | 10.2. Informative References | |||
| [I-D.ietf-pce-pcep-yang] | [I-D.ietf-pce-pcep-yang] | |||
| Dhody, D., Hardwick, J., Beeram, V. P., and J. Tantsura, | Dhody, D., Hardwick, J., Beeram, V. P., and J. Tantsura, | |||
| "A YANG Data Model for Path Computation Element | "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-16, 22 February | Internet-Draft, draft-ietf-pce-pcep-yang-18, 25 January | |||
| 2021, <https://datatracker.ietf.org/doc/html/draft-ietf- | 2022, <https://datatracker.ietf.org/doc/html/draft-ietf- | |||
| pce-pcep-yang-16>. | pce-pcep-yang-18>. | |||
| [RFC5925] Touch, J., Mankin, A., and R. Bonica, "The TCP | [RFC5925] Touch, J., Mankin, A., and R. Bonica, "The TCP | |||
| Authentication Option", RFC 5925, DOI 10.17487/RFC5925, | Authentication Option", RFC 5925, DOI 10.17487/RFC5925, | |||
| June 2010, <https://www.rfc-editor.org/info/rfc5925>. | June 2010, <https://www.rfc-editor.org/info/rfc5925>. | |||
| [RFC6952] Jethanandani, M., Patel, K., and L. Zheng, "Analysis of | [RFC6952] Jethanandani, M., Patel, K., and L. Zheng, "Analysis of | |||
| BGP, LDP, PCEP, and MSDP Issues According to the Keying | BGP, LDP, PCEP, and MSDP Issues According to the Keying | |||
| and Authentication for Routing Protocols (KARP) Design | and Authentication for Routing Protocols (KARP) Design | |||
| Guide", RFC 6952, DOI 10.17487/RFC6952, May 2013, | Guide", RFC 6952, DOI 10.17487/RFC6952, May 2013, | |||
| <https://www.rfc-editor.org/info/rfc6952>. | <https://www.rfc-editor.org/info/rfc6952>. | |||
| End of changes. 7 change blocks. | ||||
| 11 lines changed or deleted | 11 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||