rfc9752v2.txt | rfc9752.txt | |||
---|---|---|---|---|
skipping to change at line 29 ¶ | skipping to change at line 29 ¶ | |||
specific information in stateful Path Computation Element (PCE) | specific information in stateful Path Computation Element (PCE) | |||
operations. These extensions allow vendors to incorporate | operations. These extensions allow vendors to incorporate | |||
proprietary data within PCEP messages, facilitating enhanced network | proprietary data within PCEP messages, facilitating enhanced network | |||
optimization and functionality in environments requiring vendor- | optimization and functionality in environments requiring vendor- | |||
specific features. The extensions maintain compatibility with | specific features. The extensions maintain compatibility with | |||
existing PCEP implementations and promote interoperability across | existing PCEP implementations and promote interoperability across | |||
diverse network deployments. RFC 7470 defines a facility to carry | diverse network deployments. RFC 7470 defines a facility to carry | |||
vendor-specific information in stateless PCEP messages. This | vendor-specific information in stateless PCEP messages. This | |||
document extends this capability for the stateful PCEP messages. | document extends this capability for the stateful PCEP messages. | |||
This document updates RFC 7470 to specify that Enterprise numbers are | This document updates RFC 7470 to specify that Enterprise Numbers are | |||
managed through the "Private Enterprise Numbers (PENs)" registry. | managed through the "Private Enterprise Numbers (PENs)" registry. | |||
Status of This Memo | Status of This Memo | |||
This is an Internet Standards Track document. | This is an Internet Standards Track document. | |||
This document is a product of the Internet Engineering Task Force | This document is a product of the Internet Engineering Task Force | |||
(IETF). It represents the consensus of the IETF community. It has | (IETF). It represents the consensus of the IETF community. It has | |||
received public review and has been approved for publication by the | received public review and has been approved for publication by the | |||
Internet Engineering Steering Group (IESG). Further information on | Internet Engineering Steering Group (IESG). Further information on | |||
skipping to change at line 452 ¶ | skipping to change at line 452 ¶ | |||
Acknowledgments | Acknowledgments | |||
Thanks to Dhruv Dhody for shepherding the document and for their | Thanks to Dhruv Dhody for shepherding the document and for their | |||
significant contributions and suggestions. | significant contributions and suggestions. | |||
Thanks to Adrian Farrel, Avantika, Deb Cooley, Éric Vyncke, Gunter | Thanks to Adrian Farrel, Avantika, Deb Cooley, Éric Vyncke, Gunter | |||
Van de Velde, John Scudder, Mahendra Singh Negi, Mahesh Jethanandani, | Van de Velde, John Scudder, Mahendra Singh Negi, Mahesh Jethanandani, | |||
Mike McBride, Murray Kucherawy, Orie Steele, Paul Wouters, Roman | Mike McBride, Murray Kucherawy, Orie Steele, Paul Wouters, Roman | |||
Danyliw, Susan Hares, Swapna K, Udayasree Palle, Warren Kumari, | Danyliw, Susan Hares, Swapna K, Udayasree Palle, Warren Kumari, | |||
Wassim Haddad, and Xiao Min for their reviews, comments and | Wassim Haddad, and Xiao Min for their reviews, comments, and | |||
suggestions. | suggestions. | |||
Contributors | Contributors | |||
Dhruv Dhody | Dhruv Dhody | |||
Huawei | Huawei | |||
India | India | |||
Email: dhruv.ietf@gmail.com | Email: dhruv.ietf@gmail.com | |||
Mike Koldychev | Mike Koldychev | |||
End of changes. 2 change blocks. | ||||
2 lines changed or deleted | 2 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |