datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

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

Document type: Active Internet-Draft (pce WG)
Document stream: IETF
Last updated: 2014-02-14
Intended RFC status: Unknown
Other versions: plain text, pdf, html

IETF State: WG Document
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

PCE Working Group                                              E. Crabbe
Internet-Draft                                              Google, Inc.
Intended status: Standards Track                               J. Medved
Expires: August 16, 2014                             Cisco Systems, Inc.
                                                                I. Minei
                                                            Google, Inc.
                                                                R. Varga
                                               Pantheon Technologies SRO
                                                       February 12, 2014

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

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.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

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 August 16, 2014.

Crabbe, et al.           Expires August 16, 2014                [Page 1]
Internet-Draft      PCEP Extensions for Stateful PCE       February 2014

Copyright Notice

   Copyright (c) 2014 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
   (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 . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Motivation and Objectives for Stateful PCE . . . . . . . . . .  5
     3.1.  Motivation . . . . . . . . . . . . . . . . . . . . . . . .  6
       3.1.1.  Background . . . . . . . . . . . . . . . . . . . . . .  6
       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.  Architectural Overview of Protocol Extensions  . . . . . . . .  9
     5.1.  LSP State Ownership  . . . . . . . . . . . . . . . . . . .  9
     5.2.  New Messages . . . . . . . . . . . . . . . . . . . . . . . 10
     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 . . . . . . . . . . . . . . . . . . . 19

[include full document text]