PCEP Extensions for MPSL-TE LSP Path Protection with stateful PCE
draft-ananthakrishnan-pce-stateful-path-protection-01
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
---|---|---|---|
Authors | Hariharan Ananthakrishnan , Siva Sivabalan , Colby Barth , Raveendra Torvi , Ina Minei , Edward Crabbe | ||
Last updated | 2016-09-11 (Latest revision 2016-03-10) | ||
Replaced by | draft-ietf-pce-stateful-path-protection, RFC 8745 | ||
RFC stream | (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
A stateful Path Computation Element (PCE) is capable of computing as well as controlling via Path Computation Element Protocol (PCEP) Multiprotocol Label Switching Traffic Engineering Label Switched Paths (MPLS LSP). Furthermore, it is also possible for a stateful PCE to create, maintain, and delete LSPs. This document describes PCEP extension to associate two or more LSPs to provide end-to-end path protection.
Authors
Hariharan Ananthakrishnan
Siva Sivabalan
Colby Barth
Raveendra Torvi
Ina Minei
Edward Crabbe
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)