Skip to main content

Architecture and Requirement for Distribution of Link-State and TE Information via PCEP.
draft-leedhody-teas-pcep-ls-03

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Young Lee , Dhruv Dhody , Daniele Ceccarelli
Last updated 2017-03-27 (Latest revision 2016-09-14)
RFC stream (None)
Intended RFC status (None)
Formats
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, 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.

Authors

Young Lee
Dhruv Dhody
Daniele Ceccarelli

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