Path Computation Element Communication Protocol (PCEP) Extensions for remote-initiated LSP Usage
draft-ali-pce-remote-initiated-lsp-usage-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Zafar Ali , Siva Sivabalan , Clarence Filsfils , Victor Lopez , Oscar Gonzalez de Dios , Xian Zhang | ||
| Last updated | 2014-04-24 (Latest revision 2013-10-21) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
When active stateful PCE is used for managing PCE-initiated LSP, PCC may not be aware of the intended usage of the LSP (e.g., in a multi-layer network). PCEP Extensions for PCE-initiated MPLS and GMPLS LSP Setup specifications do not address this requirement. This draft addresses the requirement to specify on how PCC should use the remote initiated LSPs.
Authors
Zafar Ali
Siva Sivabalan
Clarence Filsfils
Victor Lopez
Oscar Gonzalez de Dios
Xian Zhang
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)