Conveying path setup type in PCEP messages
draft-sivabalan-pce-lsp-setup-type-02
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2015-01-01 (latest revision 2014-06-30) | ||
| Replaced by | RFC 8408 | ||
| 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-lsp-setup-type | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-sivabalan-pce-lsp-setup-type-02.txt
Abstract
A Path Computation Element can compute traffic engineering paths (TE paths) through a network that are subject to various constraints. Currently, TE paths are label switched paths (LSPs) which are set up using the RSVP-TE signaling protocol. However, other TE path setup methods are possible within the PCE architecture. This document proposes an extension to PCEP to allow support for different path setup methods over a given PCEP session.
Authors
Siva Sivabalan
(msiva@cisco.com)
Jan Medved
(jmedved@cisco.com)
Ina Minei
(inaminei@google.com)
Edward Crabbe
(edc@google.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)