PCEP Extension for Transporting TE Data
draft-dhodylee-pce-pcep-te-data-extn-02

Document Type Replaced Internet-Draft (individual)
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
pdf htmlized 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
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
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 (dhruv.ietf@gmail.com)
Young Lee (leeyoung@huawei.com)
Daniele Ceccarelli (daniele.ceccarelli@ericsson.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)