PCEP Procedures and Protocol Extensions for Using PCE as a Central Controller (PCECC) of LSPs
draft-zhao-pce-pcep-extension-for-pce-controller-06
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
|
|
|---|---|---|---|
| Authors | Quintin Zhao , Zhenbin Li , Dhruv Dhody , Satish Karunanithi , Adrian Farrel , Chao Zhou | ||
| Last updated | 2017-10-27 | ||
| Replaced by | draft-ietf-pce-pcep-extension-for-pce-controller, RFC 9050 | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-zhao-pce-pcep-extension-for-pce-controller-06
Zhao, et al. Expires April 29, 2018 [Page 25] Internet-Draft PCECC October 2017 Error-value = TBD : Processing label update Failed during synchronization. Error-value = TBD : Internal PCE Error during synchronization. 11. Acknowledgments We would like to thank Robert Tao, Changjing Yan, Tieying Huang and Avantika for their useful comments and suggestions. 12. References 12.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-editor.org/info/rfc2119>. [RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation Element (PCE) Communication Protocol (PCEP)", RFC 5440, DOI 10.17487/RFC5440, March 2009, <https://www.rfc-editor.org/info/rfc5440>. [RFC7420] Koushik, A., Stephan, E., Zhao, Q., King, D., and J. Hardwick, "Path Computation Element Communication Protocol (PCEP) Management Information Base (MIB) Module", RFC 7420, DOI 10.17487/RFC7420, December 2014, <https://www.rfc-editor.org/info/rfc7420>. [RFC7525] Sheffer, Y., Holz, R., and P. Saint-Andre, "Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May 2015, <https://www.rfc-editor.org/info/rfc7525>. [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, <https://www.rfc-editor.org/info/rfc8174>. [RFC8231] Crabbe, E., Minei, I., Medved, J., and R. Varga, "Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE", RFC 8231, DOI 10.17487/RFC8231, September 2017, <https://www.rfc-editor.org/info/rfc8231>. Zhao, et al. Expires April 29, 2018 [Page 26] Internet-Draft PCECC October 2017 [RFC8233] Dhody, D., Wu, Q., Manral, V., Ali, Z., and K. Kumaki, "Extensions to the Path Computation Element Communication Protocol (PCEP) to Compute Service-Aware Label Switched Paths (LSPs)", RFC 8233, DOI 10.17487/RFC8233, September 2017, <https://www.rfc-editor.org/info/rfc8233>. [I-D.ietf-pce-pce-initiated-lsp] Crabbe, E., Minei, I., Sivabalan, S., and R. Varga, "PCEP Extensions for PCE-initiated LSP Setup in a Stateful PCE Model", draft-ietf-pce-pce-initiated-lsp-11 (work in progress), October 2017. 12.2. Informative References [RFC8253] Lopez, D., Gonzalez de Dios, O., Wu, Q., and D. Dhody, "PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)", RFC 8253, DOI 10.17487/RFC8253, October 2017, <https://www.rfc-editor.org/info/rfc8253>. [I-D.ietf-teas-pce-central-control] Farrel, A., Zhao, Q., Li, Z., and C. Zhou, "An Architecture for Use of PCE and PCEP in a Network with Central Control", draft-ietf-teas-pce-central-control-05 (work in progress), September 2017. [I-D.ietf-teas-pcecc-use-cases] Zhao, Q., Li, Z., Khasanov, B., Ke, Z., Fang, L., Zhou, C., Communications, T., and A. Rachitskiy, "The Use Cases for Using PCE as the Central Controller(PCECC) of LSPs", draft-ietf-teas-pcecc-use-cases-01 (work in progress), May 2017. [I-D.ietf-pce-lsp-setup-type] Sivabalan, S., Tantsura, J., Minei, I., Varga, R., and J. Hardwick, "Conveying path setup type in PCEP messages", draft-ietf-pce-lsp-setup-type-04 (work in progress), April 2017. [I-D.ietf-pce-pcep-yang] Dhody, D., Hardwick, J., Beeram, V., and j. jefftant@gmail.com, "A YANG Data Model for Path Computation Element Communications Protocol (PCEP)", draft-ietf-pce-pcep-yang-05 (work in progress), June 2017. Zhao, et al. Expires April 29, 2018 [Page 27] Internet-Draft PCECC October 2017 [I-D.zhao-pce-pcep-extension-pce-controller-sr] Zhao, Q., Li, Z., Dhody, D., Karunanithi, S., Farrel, A., and C. Zhou, "PCEP Procedures and Protocol Extensions for Using PCE as a Central Controller (PCECC) of SR-LSPs", draft-zhao-pce-pcep-extension-pce-controller-sr-00 (work in progress), June 2017. [I-D.palle-pce-controller-labeldb-sync] Palle, U., Dhody, D., and S. Karunanithi, "LABEL-DB Synchronization Procedures for a PCE as a central controller(PCECC)", draft-palle-pce-controller-labeldb- sync-01 (work in progress), June 2017. Zhao, et al. Expires April 29, 2018 [Page 28] Internet-Draft PCECC October 2017 Appendix A. Using existing PCEP message This is a temporary section added to this document, till the time a decision on the use of new messages v/s extending existing message is resolved. This section should be removed before the final publication of the document. The PCInitiate message can be used to download or remove the labels - <PCInitiate Message> ::= <Common Header> <PCE-initiated-lsp-list> Where: <Common Header> is defined in [RFC5440] <PCE-initiated-lsp-list> ::= <PCE-initiated-lsp-request> [<PCE-initiated-lsp-list>] <PCE-initiated-lsp-request> ::= (<PCE-initiated-lsp-instantiation>| <PCE-initiated-lsp-deletion>| <PCE-initiated-lsp-label-download>) <PCE-initiated-lsp-label-download> ::= <SRP> <LSP> <label-list> <label-list> ::= <LABEL> [<label-list>] Where: <PCE-initiated-lsp-instantiation> and <PCE-initiated-lsp-deletion> are as per [I-D.ietf-pce-pce-initiated-lsp]. The LSP and SRP object is defined in [RFC8231]. The PCRpt message can be used to report the labels that were allocated by the PCE, to be used during the state synchronization phase. Zhao, et al. Expires April 29, 2018 [Page 29] Internet-Draft PCECC October 2017 <PCRpt Message> ::= <Common Header> <state-report-list> Where: <state-report-list> ::= <state-report>[<state-report-list>] <state-report> ::= (<lsp-state-report>| <pce-label-report>) <lsp-state-report> ::= [<SRP>] <LSP> <path> <pce-label-report> ::= <pce-label-delegate> <pce-label-delegate> ::= <SRP> <LSP> <label-list> <label-list> ::= <LABEL> [<label-list>] Where: <path> is as per [RFC8231] and the LSP and SRP object are also defined in [RFC8231]. The procedure for LSP-DB synchronization would also change, in-case we use the existing message. It will be the PCCs that would first report all the labels downloaded by the PCE during the state synchronization from PCC towards PCE, and then in case of any discrepancies PCE would use the PCInitiate message to add/remove labels. Appendix B. Contributor Addresses Zhao, et al. Expires April 29, 2018 [Page 30] Internet-Draft PCECC October 2017 Udayasree Palle Huawei Technologies Divyashree Techno Park, Whitefield Bangalore, Karnataka 560066 India EMail: udayasreereddy@gmail.com Katherine Zhao Huawei Technologies 2330 Central Expressway Santa Clara, CA 95050 USA EMail: katherine.zhao@huawei.com Boris Zhang Telus Ltd. Toronto Canada EMail: boris.zhang@telus.com Authors' Addresses Quintin Zhao Huawei Technologies 125 Nagog Technology Park Acton, MA 01719 USA EMail: quintin.zhao@huawei.com Zhenbin Li Huawei Technologies Huawei Bld., No.156 Beiqing Rd. Beijing 100095 China EMail: lizhenbin@huawei.com Zhao, et al. Expires April 29, 2018 [Page 31] Internet-Draft PCECC October 2017 Dhruv Dhody Huawei Technologies Divyashree Techno Park, Whitefield Bangalore, Karnataka 560066 India EMail: dhruv.ietf@gmail.com Satish Karunanithi Huawei Technologies Divyashree Techno Park, Whitefield Bangalore, Karnataka 560066 India EMail: satishk@huawei.com Adrian Farrel Juniper Networks, Inc UK EMail: adrian@olddog.co.uk Chao Zhou Cisco Systems EMail: choa.zhou@cisco.com Zhao, et al. Expires April 29, 2018 [Page 32]