Applicability of Stateful Path Computation Element (PCE)
draft-zhang-pce-stateful-pce-app-04
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2013-11-26 (latest revision 2013-05-25) | ||
| Replaced by | draft-ietf-pce-stateful-pce-app | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-pce-stateful-pce-app | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-zhang-pce-stateful-pce-app-04.txt
Abstract
A stateful Path Computation Element (PCE) maintains information about Label Switched Path (LSP) characteristics and resource usage within a network in order to provide traffic engineering calculations for its associated Path Computation Clients (PCCs). This document describes general considerations for a stateful PCE deployment and examines its applicability and benefits through a number of use cases. Path Computation Element Protocol (PCEP) extensions required for stateful PCE usage are covered in separate documents.
Authors
Xian Zhang
(zhang.xian@huawei.com)
Ina Minei
(ina@juniper.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)