PCEP extensions for Distribution of Link-State and TE Information
draft-dhodylee-pce-pcep-ls-22
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Dhruv Dhody , Shuping Peng , Young Lee , Daniele Ceccarelli , Aijun Wang , Gyan Mishra , Siva Sivabalan | ||
| Last updated | 2022-02-26 (Latest revision 2021-08-25) | ||
| Replaces | draft-dhodylee-pce-pcep-te-data-extn | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
In order to compute and provide optimal paths, a Path Computation Elements (PCEs) require an accurate and timely Traffic Engineering Database (TED). Traditionally, this TED has been obtained from a link state (LS) routing protocol supporting the traffic engineering extensions. This document extends the Path Computation Element Communication Protocol (PCEP) with Link-State and TE Information as an experimental extension.
Authors
Dhruv Dhody
Shuping Peng
Young Lee
Daniele Ceccarelli
Aijun Wang
Gyan Mishra
Siva Sivabalan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)