Conveying Path Setup Type in PCE Communication Protocol (PCEP) Messages
RFC 8408

Document Type RFC - Proposed Standard (July 2018; No errata)
Last updated 2018-07-24
Replaces draft-sivabalan-pce-lsp-setup-type
Stream IETF
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Julien Meuric
Shepherd write-up Show (last changed 2017-12-19)
IESG IESG state RFC 8408 (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)                      S. Sivabalan
Request for Comments: 8408                           Cisco Systems, Inc.
Category: Standards Track                                    J. Tantsura
ISSN: 2070-1721                                           Nuage Networks
                                                                I. Minei
                                                            Google, Inc.
                                                                R. Varga
                                               Pantheon Technologies SRO
                                                             J. Hardwick
                                                     Metaswitch Networks
                                                               July 2018

                       Conveying Path Setup Type
             in PCE Communication Protocol (PCEP) Messages

Abstract

   A Path Computation Element (PCE) can compute Traffic Engineering (TE)
   paths through a network; these paths are subject to various
   constraints.  Currently, TE paths are Label Switched Paths (LSPs)
   that are set up using the RSVP-TE signaling protocol.  However, other
   TE path setup methods are possible within the PCE architecture.  This
   document proposes an extension to the PCE Communication Protocol
   (PCEP) to allow support for different path setup methods over a given
   PCEP session.

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

Sivabalan, et al.            Standards Track                    [Page 1]
RFC 8408                   PCE Path Setup Type                 July 2018

Copyright Notice

   Copyright (c) 2018 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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Path Setup Type Capability TLV  . . . . . . . . . . . . . . .   4
   4.  Path Setup Type TLV . . . . . . . . . . . . . . . . . . . . .   6
   5.  Operation . . . . . . . . . . . . . . . . . . . . . . . . . .   7
   6.  Manageability Considerations  . . . . . . . . . . . . . . . .   8
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
     8.1.  Additions to PCEP TLV Type Indicators Registry  . . . . .   9
     8.2.  New PCEP Path Setup Types Registry  . . . . . . . . . . .   9
     8.3.  Additions to PCEP-ERROR Object Error Types and Values
           Registry  . . . . . . . . . . . . . . . . . . . . . . . .  10
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  11
   Contributors  . . . . . . . . . . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

Sivabalan, et al.            Standards Track                    [Page 2]
RFC 8408                   PCE Path Setup Type                 July 2018

1.  Introduction

   [RFC5440] describes the PCE Communication Protocol (PCEP) for
   communication between a Path Computation Client (PCC) and a Path
   Computation Element (PCE) or between a PCE and a PCE.  A PCC
   requests, from a PCE, a path subject to various constraints and
   optimization criteria.  The PCE responds to the PCC with a hop-by-hop
   path in an Explicit Route Object (ERO).  The PCC uses the ERO to set
   up the path in the network.

   [RFC8231] specifies extensions to PCEP that allow a PCC to delegate
   its LSPs to a PCE.  The PCE can then update the state of LSPs
Show full document text