Path Protection Enforcement in PCEP
draft-stone-pce-path-protection-enforcement-00
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Andrew Stone , Mustapha Aissaoui | ||
| Last updated | 2019-10-25 | ||
| Replaced by | draft-stone-pce-local-protection-enforcement | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
|
||
| 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 | (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 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
Mustapha Aissaoui
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)