PCEP Extension for Transporting TE Data
draft-dhodylee-pce-pcep-te-data-extn-02
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Dhruv Dhody , Young Lee , Daniele Ceccarelli | ||
| Last updated | 2015-09-05 (Latest revision 2015-03-04) | ||
| Replaced by | draft-dhodylee-pce-pcep-ls | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-dhodylee-pce-pcep-ls | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-dhodylee-pce-pcep-te-data-extn-02.txt
Abstract
In order to compute and provide optimal paths, Path Computation Elements (PCEs) require an accurate and timely Traffic Engineering Database (TED). Traditionally this TED has been obtained from a link state routing protocol supporting traffic engineering extensions. This document extends the Path Computation Element Communication Protocol (PCEP) with TED population capability.
Authors
Dhruv Dhody
Young Lee
Daniele Ceccarelli
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)