Path Computation Element (PCE) Database Requirements
draft-dugeon-pce-ted-reqs-03

 
Document Type Expired Internet-Draft (individual)
Last updated 2014-08-18 (latest revision 2014-02-14)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

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-dugeon-pce-ted-reqs-03.txt

Abstract

The Path Computation Element (PCE) working group (WG) has produced a set of RFCs to standardize the behavior of the Path Computation Element as a tool to help MPLS-TE and GMPLS LSP tunnels placement. In the PCE architecture, a main assumption has been done concerning the information that the PCE needs to perform its computation. In a fist approach, the PCE embeds a Traffic Engineering Database (TED) containing all pertinent and suitable information regarding the network that is in the scope of a PCE. Nevertheless, the TED requirements as well as the TED information have not yet been formalized. In addition, some recent RFC (like the Backward Recursive Path Computation procedure or PCE Hierarchy) or WG draft (like draft-ietf-pce-stateful-pce ...) suffer from a lack of information in the TED, leading to a non optimal result or to some difficulties to deploy them. This memo tries to identify some Database, at large, requirements for the PCE. It is split in two main sections: the identification of the specific information to be stored in the PCE Database and how it may be populated.

Authors

Olivier Dugeon (olivier.dugeon@orange.com)
Julien Meuric (julien.meuric@orange.com)
Richard Douville (richard.douville@alcatel-lucent.com)
Ramon Casellas (ramon.casellas@cttc.es)
Oscar Gonzalez de Dios (ogondio@tid.es)

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