PCEP Extensions to support LSP parameters
draft-fizgeer-pce-lsp-parameters-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Orly Bachar , Marina Fizgeer | ||
| Last updated | 2022-12-01 | ||
| Replaced by | draft-fizgeer-pcep-bfd-parameters | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-fizgeer-pcep-bfd-parameters | |
| 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
This document proposes extension to PCEP to configure LSP parameters. Some of LSP parameters are needed to configure S-BFD for candidate paths. An SR policy is identified by <headend, color, endpoint> tuple. An SR policy can contain one or more candidate paths where each candidate path is identified in PCEP by its uniquely assigned PLSP-ID. The mechanism proposed in this document is applicable to both MPLS and IPv6 data planes of SR.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)