PCEP Extensions for RSVP-TE Local-Protection with PCE-Stateful
draft-cbrt-pce-stateful-local-protection-01

Document Type Active Internet-Draft (individual)
Last updated 2018-06-29
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
PCE Working Group                                               C. Barth
Internet-Draft                                                  R. Torvi
Intended status: Standards Track                        Juniper Networks
Expires: December 30, 2018                                 June 28, 2018

     PCEP Extensions for RSVP-TE Local-Protection with PCE-Stateful
              draft-cbrt-pce-stateful-local-protection-01

Abstract

   Stateful PCE [RFC8231] can apply global concurrent optimizations to
   optimize LSP placement.  In a deployment where a PCE is used to
   compute all the paths, it may be beneficial for the local protection
   paths to also be computed by the PCE.  This document defines
   extensions needed for the setup and management of RSVP-TE protection
   paths by the PCE.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 30, 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

Barth & Torvi           Expires December 30, 2018               [Page 1]
Internet-Draft    PCE-Stateful RSVP-TE Local-Protection        June 2018

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Architectural Overview  . . . . . . . . . . . . . . . . . . .   3
     3.1.  Local Protection Overview . . . . . . . . . . . . . . . .   3
   4.  Extensions for the LSPA object  . . . . . . . . . . . . . . .   4
     4.1.  The Preference TLV  . . . . . . . . . . . . . . . . . . .   4
     4.2.  The Bypass TLV  . . . . . . . . . . . . . . . . . . . . .   5
     4.3.  The LOCALLY-PROTECTED-LSPS TLV  . . . . . . . . . . . . .   6
   5.  IANA considerations . . . . . . . . . . . . . . . . . . . . .   8
     5.1.  PCEP-Error Object . . . . . . . . . . . . . . . . . . . .   8
     5.2.  PCEP TLV Type Indicators  . . . . . . . . . . . . . . . .   8
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   8
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Appendix A.  Additional Stuff . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   [RFC5440] describes the Path Computation Element Protocol PCEP.  PCEP
   defines the communication between a Path Computation Client (PCC) and
   a Path Control Element (PCE), or between PCE and PCE, enabling
   computation of Multi-protocol Label Switching (MPLS) for Traffic
   Engineering Label Switched Path (TE LSP) characteristics.

   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 effect LSP state synchronization between PCCs and PCEs
   and allow delegation of control of LSPs to PCEs.

   In a network where all LSPs have control delegated to a PCE, the PCE
   can apply global concurrent optimization to optimize LSP placement.
   The PCE can also control the timing and sequence of path computation
   and applying path changes.  In a deployment where a PCE is used to
   compute all the paths, it may be beneficial for the protection paths
   to also be controlled through the PCE.  This document defines
   extensions needed for the setup and management of protection paths by
   the PCE.

Barth & Torvi           Expires December 30, 2018               [Page 2]
Internet-Draft    PCE-Stateful RSVP-TE Local-Protection        June 2018
Show full document text