Architecture and Requirement for Distribution of Link-State and TE Information via PCEP.
|Document||Type||Expired Internet-Draft (individual)|
|Last updated||2017-03-27 (latest revision 2016-09-14)|
|Intended RFC status||(None)|
Expired & archivedplain text pdf html bibtex
|Stream||Stream state||(No stream defined)|
|RFC Editor Note||(None)|
|Send notices to||(None)|
In order to compute and provide optimal paths, Path Computation Elements (PCEs) require an accurate and timely Traffic Engineering Database (TED). Traditionally this Link State and TE information has been obtained from a link state routing protocol (supporting traffic engineering extensions). This document provides possible architectural alternatives for link- state and TE information distribution and their potential impacts on PCE, network nodes, routing protocols etc.
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)