| < draft-ietf-pce-association-policy-13.txt | draft-ietf-pce-association-policy-14.txt > | |||
|---|---|---|---|---|
| PCE Working Group S. Litkowski | PCE Working Group S. Litkowski | |||
| Internet-Draft Cisco Systems, Inc. | Internet-Draft Cisco Systems, Inc. | |||
| Intended status: Standards Track S. Sivabalan | Intended status: Standards Track S. Sivabalan | |||
| Expires: April 8, 2021 Ciena | Expires: June 11, 2021 Ciena | |||
| J. Tantsura | J. Tantsura | |||
| Apstra, Inc. | Apstra, Inc. | |||
| J. Hardwick | J. Hardwick | |||
| Metaswitch Networks | Metaswitch Networks | |||
| M. Negi | M. Negi | |||
| RtBrick Inc | RtBrick Inc | |||
| C. Li | C. Li | |||
| Huawei Technologies | Huawei Technologies | |||
| October 05, 2020 | December 08, 2020 | |||
| Path Computation Element (PCE) Communication Protocol (PCEP) extension | Path Computation Element (PCE) Communication Protocol (PCEP) extension | |||
| for associating Policies and Label Switched Paths (LSPs) | for associating Policies and Label Switched Paths (LSPs) | |||
| draft-ietf-pce-association-policy-13 | draft-ietf-pce-association-policy-14 | |||
| Abstract | Abstract | |||
| This document introduces a simple mechanism to associate policies to | This document introduces a simple mechanism to associate policies to | |||
| a group of Label Switched Paths (LSPs) via an extension to the Path | a group of Label Switched Paths (LSPs) via an extension to the Path | |||
| Computation Element (PCE) Communication Protocol (PCEP). The | Computation Element (PCE) Communication Protocol (PCEP). The | |||
| extension allows a PCEP speaker to advertise to a PCEP peer that a | extension allows a PCEP speaker to advertise to a PCEP peer that a | |||
| particular LSP belongs to a particular Policy Association Group. | particular LSP belongs to a particular Policy Association Group. | |||
| Status of This Memo | Status of This Memo | |||
| skipping to change at page 1, line 44 ¶ | skipping to change at page 1, line 44 ¶ | |||
| 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 April 8, 2021. | This Internet-Draft will expire on June 11, 2021. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2020 IETF Trust and the persons identified as the | Copyright (c) 2020 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 | Provisions Relating to IETF Documents | |||
| (https://trustee.ietf.org/license-info) in effect on the date of | (https://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| skipping to change at page 12, line 11 ¶ | skipping to change at page 12, line 11 ¶ | |||
| 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], | |||
| [RFC8231], and [RFC8281]. | [RFC8231], and [RFC8281]. | |||
| 10. Acknowledgments | 10. Acknowledgments | |||
| A special thanks to the authors of [RFC8697], this document borrowed | A special thanks to the authors of [RFC8697], this document borrowed | |||
| some of the text from it. The authors would like to thank Aijun | some of the text from it. The authors would like to thank Aijun | |||
| Wang, Peng Shuping, and Gyan Mishra for their useful comments. | Wang, Peng Shuping, and Gyan Mishra for their useful comments. | |||
| Thanks to Hari for shepherding this document. | Thanks to Hari for shepherding this document. Thanks to Deborah | |||
| Brungard for being the responsible AD for this document. | ||||
| Thanks to Nic Leymann for RTGDIR review. | ||||
| 11. References | 11. References | |||
| 11.1. Normative References | 11.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>. | |||
| skipping to change at page 14, line 15 ¶ | skipping to change at page 14, line 15 ¶ | |||
| [RFC8664] Sivabalan, S., Filsfils, C., Tantsura, J., Henderickx, W., | [RFC8664] Sivabalan, S., Filsfils, C., Tantsura, J., Henderickx, W., | |||
| and J. Hardwick, "Path Computation Element Communication | and J. Hardwick, "Path Computation Element Communication | |||
| Protocol (PCEP) Extensions for Segment Routing", RFC 8664, | Protocol (PCEP) Extensions for Segment Routing", RFC 8664, | |||
| DOI 10.17487/RFC8664, December 2019, | DOI 10.17487/RFC8664, December 2019, | |||
| <https://www.rfc-editor.org/info/rfc8664>. | <https://www.rfc-editor.org/info/rfc8664>. | |||
| [I-D.ietf-pce-pcep-yang] | [I-D.ietf-pce-pcep-yang] | |||
| Dhody, D., Hardwick, J., Beeram, V., and J. Tantsura, "A | Dhody, D., Hardwick, J., Beeram, V., and J. Tantsura, "A | |||
| YANG Data Model for Path Computation Element | YANG Data Model for Path Computation Element | |||
| Communications Protocol (PCEP)", draft-ietf-pce-pcep- | Communications Protocol (PCEP)", draft-ietf-pce-pcep- | |||
| yang-14 (work in progress), July 2020. | yang-15 (work in progress), October 2020. | |||
| Appendix A. Example of Policy Parameters | Appendix A. Example of Policy Parameters | |||
| An example could be a monitoring and telemetry policy P1 that is | An example could be a monitoring and telemetry policy P1 that is | |||
| dependent on a profile (GOLD/SILVER/BRONZE) as set by the operator. | dependent on a profile (GOLD/SILVER/BRONZE) as set by the operator. | |||
| The PCEP peers need to be aware of the policy P1 (and its associated | The PCEP peers need to be aware of the policy P1 (and its associated | |||
| characteristics) in advance as well the fact that the policy | characteristics) in advance as well the fact that the policy | |||
| parameter will encode the profile of type string in the POLICY- | parameter will encode the profile of type string in the POLICY- | |||
| PARAMETERS-TLV. As an example, LSP1 could encode the PAG with the | PARAMETERS-TLV. As an example, LSP1 could encode the PAG with the | |||
| POLICY-PARAMETERS-TLV with a string "GOLD". | POLICY-PARAMETERS-TLV with a string "GOLD". | |||
| End of changes. 6 change blocks. | ||||
| 6 lines changed or deleted | 9 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/ | ||||