Experimental Codepoint Allocation for Path Computation Element communication Protocol (PCEP)
draft-dhody-pce-pcep-exp-codepoints-03
| Document | Type | Replaced Internet-Draft (pce WG) | |
|---|---|---|---|
| Last updated | 2017-04-24 (latest revision 2017-03-27) | ||
| Replaced by | RFC 8356 | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-pce-pcep-exp-codepoints | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-dhody-pce-pcep-exp-codepoints-03.txt
Abstract
IANA assigns values to the Path Computation Element (PCE) communication Protocol (PCEP) parameters (messages, objects, TLVs). IANA established a new top-level registry to contain all PCEP codepoints and sub-registries. The allocation policy for each new registry is by IETF Consensus. This document seeks to mark some codepoints for experimental usage of PCEP.
Authors
Dhruv Dhody
(dhruv.ietf@gmail.com)
Daniel King
(d.king@lancaster.ac.uk)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)