Path Protection Enforcement in PCEP
draft-stone-pce-path-protection-enforcement-00
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2019-10-25 | ||
| Replaced by | draft-stone-pce-local-protection-enforcement | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-stone-pce-local-protection-enforcement | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-stone-pce-path-protection-enforcement-00.txt
Abstract
This document aims to clarify existing usage of the local protection desired bit signalled in Path Computation Element Protocol (PCEP). This document also introduces a new flag for signalling protection strictness in PCEP.
Authors
Andrew Stone
(andrew.stone@nokia.com)
Mustapha Aissaoui
(mustapha.aissaoui@nokia.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)