Path Computation Element Communication Protocol (PCEP) Extensions for Establishing Relationships between Sets of Label Switched Paths (LSPs)
RFC 8697

Document Type RFC - Proposed Standard (January 2020; No errata)
Last updated 2020-01-31
Replaces draft-minei-pce-association-group
Stream IETF
Formats plain text html xml pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Julien Meuric
Shepherd write-up Show (last changed 2019-06-06)
IESG IESG state RFC 8697 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Deborah Brungard
Send notices to Julien Meuric <julien.meuric@orange.com>
IANA IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack


Internet Engineering Task Force (IETF)                          I. Minei
Request for Comments: 8697                                  Google, Inc.
Category: Standards Track                                      E. Crabbe
ISSN: 2070-1721                                   Individual Contributor
                                                            S. Sivabalan
                                                     Cisco Systems, Inc.
                                                      H. Ananthakrishnan
                                                                 Netflix
                                                                D. Dhody
                                                                  Huawei
                                                               Y. Tanaka
                                          NTT Communications Corporation
                                                            January 2020

 Path Computation Element Communication Protocol (PCEP) Extensions for
 Establishing Relationships between Sets of Label Switched Paths (LSPs)

Abstract

   This document introduces a generic mechanism to create a grouping of
   Label Switched Paths (LSPs) in the context of a Path Computation
   Element (PCE).  This grouping can then be used to define associations
   between sets of LSPs or between a set of LSPs and a set of attributes
   (such as configuration parameters or behaviors), and it is equally
   applicable to the stateful PCE (active and passive modes) and the
   stateless PCE.

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/rfc8697.

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.  Architectural Overview
     3.1.  Motivations
     3.2.  Relationship to the SVEC List
     3.3.  Operational Overview
     3.4.  Operator-Configured Association Range
   4.  Discovery of Supported Association Types
     4.1.  ASSOC-Type-List TLV
       4.1.1.  Procedure
   5.  Operator-Configured Association Range TLV
     5.1.  Procedure
   6.  ASSOCIATION Object
     6.1.  Object Definition
       6.1.1.  Global Association Source TLV
       6.1.2.  Extended Association ID TLV
       6.1.3.  Association Source
       6.1.4.  Unique Identification for an Association Group
     6.2.  Relationship to the RSVP ASSOCIATION Object
     6.3.  Object Encoding in PCEP Messages
       6.3.1.  Stateful PCEP Messages
       6.3.2.  Request Message
       6.3.3.  Reply Message
     6.4.  Processing Rules
   7.  IANA Considerations
     7.1.  PCEP Object
     7.2.  PCEP TLV
     7.3.  Association Flags
     7.4.  Association Type
     7.5.  PCEP-Error Object
   8.  Security Considerations
   9.  Manageability Considerations
     9.1.  Control of Function and Policy
     9.2.  Information and Data Models
     9.3.  Liveness Detection and Monitoring
     9.4.  Verifying Correct Operation
     9.5.  Requirements on Other Protocols
     9.6.  Impact on Network Operations
   10. References
     10.1.  Normative References
     10.2.  Informative References
   Appendix A.  Example of an Operator-Configured Association Range
   Acknowledgments
   Contributors
   Authors' Addresses

1.  Introduction

   [RFC5440] describes the Path Computation Element (PCE) Communication
   Protocol (PCEP).  PCEP enables communication between a Path
   Computation Client (PCC) and a PCE, or between a PCE and another PCE,
   for the purpose of the computation of Multiprotocol Label Switching
   (MPLS) as well as Generalized MPLS (GMPLS) Traffic Engineering Label
   Switched Path (TE LSP) characteristics.

   [RFC8231] specifies a set of extensions to PCEP to enable stateful
   control of TE LSPs within and across PCEP sessions in compliance with
   [RFC4657].  It includes mechanisms to effect LSP State
Show full document text