PCEP Extensions for Stateful PCE
draft-crabbe-pce-stateful-pce-02

Document Type Replaced Internet-Draft (individual)
Last updated 2012-04-11 (latest revision 2012-01-22)
Replaced by draft-ietf-pce-stateful-pce
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-pce-stateful-pce
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-crabbe-pce-stateful-pce-02.txt

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 synchronization or 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 this functionality, providing stateful control of Multiprotocol Label Switching (MPLS) Traffic Engineering Label Switched Paths (TE LSP) via PCEP.

Authors

Jan Medved (jmedved@cisco.com)
Ina Minei (ina@juniper.net)
Edward Crabbe (edc@google.com)
Robert Varga (robert.varga@pantheon.sk)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)