| < draft-ietf-pce-association-policy-08.txt | draft-ietf-pce-association-policy-09.txt > | |||
|---|---|---|---|---|
| PCE Working Group S. Litkowski | PCE Working Group S. Litkowski | |||
| Internet-Draft S. Sivabalan | Internet-Draft S. Sivabalan | |||
| Intended status: Standards Track Cisco Systems, Inc. | Intended status: Standards Track Cisco Systems, Inc. | |||
| Expires: September 10, 2020 J. Tantsura | Expires: October 22, 2020 J. Tantsura | |||
| Apstra, Inc. | Apstra, Inc. | |||
| J. Hardwick | J. Hardwick | |||
| Metaswitch Networks | Metaswitch Networks | |||
| M. Negi | M. Negi | |||
| C. Li | C. Li | |||
| Huawei Technologies | Huawei Technologies | |||
| March 9, 2020 | April 20, 2020 | |||
| Path Computation Element communication Protocol (PCEP) extension for | Path Computation Element communication Protocol (PCEP) extension for | |||
| associating Policies and Label Switched Paths (LSPs) | associating Policies and Label Switched Paths (LSPs) | |||
| draft-ietf-pce-association-policy-08 | draft-ietf-pce-association-policy-09 | |||
| 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). | Computation Element (PCE) Communication Protocol (PCEP). | |||
| Status of This Memo | Status of This Memo | |||
| This Internet-Draft is submitted in full conformance with the | This Internet-Draft is submitted in full conformance with the | |||
| skipping to change at page 1, line 40 ¶ | skipping to change at page 1, line 40 ¶ | |||
| 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 September 10, 2020. | This Internet-Draft will expire on October 22, 2020. | |||
| 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 2, line 22 ¶ | skipping to change at page 2, line 22 ¶ | |||
| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | |||
| 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 | 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 | |||
| 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 | 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 3. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 4 | 3. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 4 | |||
| 3.1. Policy based Constraints . . . . . . . . . . . . . . . . 5 | 3.1. Policy based Constraints . . . . . . . . . . . . . . . . 5 | |||
| 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 6 | 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 6 | |||
| 5. Policy Association Group . . . . . . . . . . . . . . . . . . 7 | 5. Policy Association Group . . . . . . . . . . . . . . . . . . 7 | |||
| 5.1. Policy Parameters TLV . . . . . . . . . . . . . . . . . . 7 | 5.1. Policy Parameters TLV . . . . . . . . . . . . . . . . . . 7 | |||
| 6. Implementation Status . . . . . . . . . . . . . . . . . . . . 8 | 6. Implementation Status . . . . . . . . . . . . . . . . . . . . 8 | |||
| 6.1. Cisco's Implementation . . . . . . . . . . . . . . . . . 9 | ||||
| 7. Security Considerations . . . . . . . . . . . . . . . . . . . 9 | 7. Security Considerations . . . . . . . . . . . . . . . . . . . 9 | |||
| 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 | 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 | |||
| 8.1. Association object Type Indicators . . . . . . . . . . . 9 | 8.1. Association object Type Indicators . . . . . . . . . . . 10 | |||
| 8.2. PCEP TLV Type Indicators . . . . . . . . . . . . . . . . 10 | 8.2. PCEP TLV Type Indicators . . . . . . . . . . . . . . . . 10 | |||
| 9. Manageability Considerations . . . . . . . . . . . . . . . . 10 | 9. Manageability Considerations . . . . . . . . . . . . . . . . 10 | |||
| 9.1. Control of Function and Policy . . . . . . . . . . . . . 10 | 9.1. Control of Function and Policy . . . . . . . . . . . . . 10 | |||
| 9.2. Information and Data Models . . . . . . . . . . . . . . . 10 | 9.2. Information and Data Models . . . . . . . . . . . . . . . 10 | |||
| 9.3. Liveness Detection and Monitoring . . . . . . . . . . . . 10 | 9.3. Liveness Detection and Monitoring . . . . . . . . . . . . 11 | |||
| 9.4. Verify Correct Operations . . . . . . . . . . . . . . . . 10 | 9.4. Verify Correct Operations . . . . . . . . . . . . . . . . 11 | |||
| 9.5. Requirements on Other Protocols . . . . . . . . . . . . . 11 | 9.5. Requirements on Other Protocols . . . . . . . . . . . . . 11 | |||
| 9.6. Impact on Network Operations . . . . . . . . . . . . . . 11 | 9.6. Impact on Network Operations . . . . . . . . . . . . . . 11 | |||
| 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11 | 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11 | |||
| 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 | 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 | |||
| 11.1. Normative References . . . . . . . . . . . . . . . . . . 11 | 11.1. Normative References . . . . . . . . . . . . . . . . . . 11 | |||
| 11.2. Informative References . . . . . . . . . . . . . . . . . 12 | 11.2. Informative References . . . . . . . . . . . . . . . . . 12 | |||
| Appendix A. Contributor Addresses . . . . . . . . . . . . . . . 14 | Appendix A. Contributor Addresses . . . . . . . . . . . . . . . 14 | |||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 | |||
| 1. Introduction | 1. Introduction | |||
| skipping to change at page 9, line 17 ¶ | skipping to change at page 9, line 17 ¶ | |||
| features. Readers are advised to note that other implementations may | features. Readers are advised to note that other implementations may | |||
| exist. | exist. | |||
| According to [RFC7942], "this will allow reviewers and working groups | According to [RFC7942], "this will allow reviewers and working groups | |||
| to assign due consideration to documents that have the benefit of | to assign due consideration to documents that have the benefit of | |||
| running code, which may serve as evidence of valuable experimentation | running code, which may serve as evidence of valuable experimentation | |||
| and feedback that have made the implemented protocols more mature. | and feedback that have made the implemented protocols more mature. | |||
| It is up to the individual working groups to use this information as | It is up to the individual working groups to use this information as | |||
| they see fit". | they see fit". | |||
| Currently there are no confirmed implementations, though vendors have | 6.1. Cisco's Implementation | |||
| shown interest in making this as part of their roadmap. More details | ||||
| to be added in a later revision. | o Organization: Cisco Systems, Inc. | |||
| o Implementation: IOS-XR PCE and PCC. | ||||
| o Description: The PCEP extension specified in this document is used | ||||
| to convey traffic steering policies. | ||||
| o Maturity Level: In shipping product. | ||||
| o Coverage: Partial. | ||||
| o Contact: msiva@cisco.com. | ||||
| 7. Security Considerations | 7. Security Considerations | |||
| This document defines one new type for association, which do not add | This document defines one new type for association, which do not add | |||
| any new security concerns beyond those discussed in [RFC5440], | any new security concerns beyond those discussed in [RFC5440], | |||
| [RFC8231] and [RFC8697] in itself. | [RFC8231] and [RFC8697] in itself. | |||
| Extra care needs to be taken by the implementation with respect to | Extra care needs to be taken by the implementation with respect to | |||
| POLICY-PARAMETERS-TLV while decoding, verifying and applying these | POLICY-PARAMETERS-TLV while decoding, verifying and applying these | |||
| policy variables. This TLV parsing could be exploited by an | policy variables. This TLV parsing could be exploited by an | |||
| skipping to change at page 14, line 23 ¶ | skipping to change at page 14, line 23 ¶ | |||
| EMail: dhruv.ietf@gmail.com | EMail: dhruv.ietf@gmail.com | |||
| Qin Wu | Qin Wu | |||
| Huawei Technologies | Huawei Technologies | |||
| 101 Software Avenue, Yuhua District | 101 Software Avenue, Yuhua District | |||
| Nanjing, Jiangsu 210012 | Nanjing, Jiangsu 210012 | |||
| China | China | |||
| EMail: sunseawq@huawei.com | EMail: sunseawq@huawei.com | |||
| Clarence Filsfils | ||||
| Cisco Systems, Inc. | ||||
| Pegasus Parc | ||||
| De kleetlaan 6a, DIEGEM BRABANT 1831 | ||||
| BELGIUM | ||||
| Email: cfilsfil@cisco.com | ||||
| Xian Zhang | Xian Zhang | |||
| Huawei Technologies | Huawei Technologies | |||
| Bantian, Longgang District | Bantian, Longgang District | |||
| Shenzhen 518129 | Shenzhen 518129 | |||
| P.R.China | P.R.China | |||
| EMail: zhang.xian@huawei.com | EMail: zhang.xian@huawei.com | |||
| Udayasree Palle | Udayasree Palle | |||
| EMail: udayasreereddy@gmail.com | EMail: udayasreereddy@gmail.com | |||
| Authors' Addresses | Authors' Addresses | |||
| Stephane Litkowski | Stephane Litkowski | |||
| Cisco Systems, Inc. | Cisco Systems, Inc. | |||
| 11 Rue Camille Desmoulins | ||||
| Issy-les-Moulineaux 92130 | ||||
| France | ||||
| EMail: slitkows.ietf@gmail.com | EMail: slitkows@cisco.com | |||
| Siva Sivabalan | Siva Sivabalan | |||
| Cisco Systems, Inc. | Cisco Systems, Inc. | |||
| 2000 Innovation Drive | 2000 Innovation Drive | |||
| Kanata, Ontario K2K 3E8 | Kanata, Ontario K2K 3E8 | |||
| Canada | Canada | |||
| EMail: msiva@cisco.com | EMail: msiva@cisco.com | |||
| Jeff Tantsura | Jeff Tantsura | |||
| Apstra, Inc. | Apstra, Inc. | |||
| End of changes. 11 change blocks. | ||||
| 20 lines changed or deleted | 27 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/ | ||||