Path Computation Element Communication Protocol (PCEP) Extensions for Associating Working and Protection Label Switched Paths (LSPs) with Stateful PCE
RFC 8745
Document | Type | RFC - Proposed Standard (March 2020; No errata) | |
---|---|---|---|
Authors | Hariharan Ananthakrishnan , Siva Sivabalan , Colby Barth , Ina Minei , Mahendra Negi | ||
Last updated | 2020-03-29 | ||
Replaces | draft-ananthakrishnan-pce-stateful-path-protection | ||
Stream | Internent Engineering Task Force (IETF) | ||
Formats | plain text html xml pdf htmlized (tools) htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Julien Meuric | ||
Shepherd write-up | Show (last changed 2019-06-18) | ||
IESG | IESG state | RFC 8745 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Deborah Brungard | ||
Send notices to | Julien Meuric <julien.meuric@orange.com> | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) H. Ananthakrishnan Request for Comments: 8745 Netflix Category: Standards Track S. Sivabalan ISSN: 2070-1721 Cisco C. Barth Juniper Networks I. Minei Google, Inc M. Negi Huawei Technologies March 2020 Path Computation Element Communication Protocol (PCEP) Extensions for Associating Working and Protection Label Switched Paths (LSPs) with Stateful PCE Abstract An active stateful Path Computation Element (PCE) is capable of computing as well as controlling via Path Computation Element Communication Protocol (PCEP) Multiprotocol Label Switching Traffic Engineering (MPLS-TE) Label Switched Paths (LSPs). Furthermore, it is also possible for an active stateful PCE to create, maintain, and delete LSPs. This document defines the PCEP extension to associate two or more LSPs to provide end-to-end path protection. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8745. Copyright Notice Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction 1.1. Requirements Language 2. Terminology 3. PCEP Extensions 3.1. Path Protection Association Type 3.2. Path Protection Association TLV 4. Operation 4.1. State Synchronization 4.2. PCC-Initiated LSPs 4.3. PCE-Initiated LSPs 4.4. Session Termination 4.5. Error Handling 5. Other Considerations 6. IANA Considerations 6.1. Association Type 6.2. Path Protection Association TLV 6.3. PCEP Errors 7. Security Considerations 8. Manageability Considerations 8.1. Control of Function and Policy 8.2. Information and Data Models 8.3. Liveness Detection and Monitoring 8.4. Verify Correct Operations 8.5. Requirements on Other Protocols 8.6. Impact on Network Operations 9. References 9.1. Normative References 9.2. Informative References Acknowledgments Contributors Authors' Addresses 1. Introduction [RFC5440] describes Path Computation Element Communication Protocol (PCEP) for communication between a Path Computation Client (PCC) and a PCE or between a pair of PCEs as per [RFC4655]. A PCE computes paths for MPLS-TE Label Switched Paths (LSPs) based on various constraints and optimization criteria. Stateful PCE [RFC8231] specifies a set of extensions to PCEP to enable stateful control of paths such as MPLS-TE LSPs between and across PCEP sessions in compliance with [RFC4657]. It includes mechanisms to affect LSP state synchronization between PCCs and PCEs, delegation of control of LSPs to PCEs, and PCE control of timing and sequence of path computations within and across PCEP sessions. The focus is on a model where LSPs are configured on the PCC, and control over them is delegated to the stateful PCE. Furthermore, [RFC8281] specifies a mechanism to dynamically instantiate LSPs on a PCC based on the requests from a stateful PCE or a controller using stateful PCE. Path protection [RFC4427] refers to a paradigm in which the working LSP is protected by one or more protection LSP(s). When the working LSP fails, protection LSP(s) is/are activated. When the working LSPsShow full document text