PCEP Extensions for Stateful PCE
draft-ietf-pce-stateful-pce-11

 
Document
Type Active Internet-Draft (pce WG)
Last updated 2015-04-20
Replaces draft-crabbe-pce-stateful-pce-mpls-te, draft-crabbe-pce-stateful-pce
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream
WG state WG Document
Document shepherd No shepherd assigned
IESG
IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR 2 References Referenced by Nits Search lists

PCE Working Group                                              E. Crabbe
Internet-Draft
Intended status: Standards Track                                I. Minei
Expires: October 22, 2015                                   Google, Inc.
                                                               J. Medved
                                                     Cisco Systems, Inc.
                                                                R. Varga
                                               Pantheon Technologies SRO
                                                          April 20, 2015

                    PCEP Extensions for Stateful PCE
                     draft-ietf-pce-stateful-pce-11

Abstract

   The Path Computation Element Communication Protocol (PCEP) provides
   mechanisms for Path Computation Elements (PCEs) to perform path
   computations in response to Path Computation Clients (PCCs) requests.

   Although PCEP explicitly makes no assumptions regarding the
   information available to the PCE, it also makes no provisions for PCE
   control of timing and sequence of path computations within and across
   PCEP sessions.  This document describes a set of extensions to PCEP
   to enable stateful control of MPLS-TE and GMPLS LSPs via PCEP.

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 http://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 October 22, 2015.

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Crabbe, et al.          Expires October 22, 2015                [Page 1]
Internet-Draft      PCEP Extensions for Stateful PCE          April 2015

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://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.  Motivation and Objectives for Stateful PCE  . . . . . . . . .   5
     3.1.  Motivation  . . . . . . . . . . . . . . . . . . . . . . .   5
       3.1.1.  Background  . . . . . . . . . . . . . . . . . . . . .   5
       3.1.2.  Why a Stateful PCE? . . . . . . . . . . . . . . . . .   6
       3.1.3.  Protocol vs. Configuration  . . . . . . . . . . . . .   7
     3.2.  Objectives  . . . . . . . . . . . . . . . . . . . . . . .   8
   4.  New Functions to Support Stateful PCEs  . . . . . . . . . . .   8
   5.  Overview of Protocol Extensions . . . . . . . . . . . . . . .   9
     5.1.  LSP State Ownership . . . . . . . . . . . . . . . . . . .   9
     5.2.  New Messages  . . . . . . . . . . . . . . . . . . . . . .   9
     5.3.  Capability Advertisement  . . . . . . . . . . . . . . . .  10
     5.4.  State Synchronization . . . . . . . . . . . . . . . . . .  11
     5.5.  LSP Delegation  . . . . . . . . . . . . . . . . . . . . .  14
       5.5.1.  Delegating an LSP . . . . . . . . . . . . . . . . . .  15
       5.5.2.  Revoking a Delegation . . . . . . . . . . . . . . . .  15
       5.5.3.  Returning a Delegation  . . . . . . . . . . . . . . .  17
       5.5.4.  Redundant Stateful PCEs . . . . . . . . . . . . . . .  17
       5.5.5.  Redelegation on PCE Failure . . . . . . . . . . . . .  18
     5.6.  LSP Operations  . . . . . . . . . . . . . . . . . . . . .  18
       5.6.1.  Passive Stateful PCE Path Computation
               Request/Response  . . . . . . . . . . . . . . . . . .  18
       5.6.2.  Active Stateful PCE LSP Update  . . . . . . . . . . .  20
     5.7.  LSP Protection  . . . . . . . . . . . . . . . . . . . . .  22
     5.8.  Transport . . . . . . . . . . . . . . . . . . . . . . . .  22
   6.  PCEP Messages . . . . . . . . . . . . . . . . . . . . . . . .  22
Show full document text