PCEP Operational Clarification
draft-ietf-pce-operational-02
| Document | Type |
Expired Internet-Draft
(pce WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mike Koldychev , Siva Sivabalan , Shuping Peng , Diego Achaval , Hari Kotni , Andrew Stone | ||
| Last updated | 2026-06-25 (Latest revision 2025-12-22) | ||
| Replaces | draft-koldychev-pce-operational | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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 clarifies certain operational behavior aspects of the PCEP protocol. The content of this document has been compiled based on several interop exercises. Discussion Venues This note is to be removed before publishing as an RFC. Discussion of this document takes place on the Path Computation Element mailing list (pce@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/pce/. Source for this draft and an issue tracker can be found at https://github.com/ietf-wg-pce/draft-ietf-pce-operational.
Authors
Mike Koldychev
Siva Sivabalan
Shuping Peng
Diego Achaval
Hari Kotni
Andrew Stone
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)