PCE Management Interface
draft-grampin-pce-mgmnt-if-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Eduardo Grampin | ||
| Last updated | 2005-07-05 | ||
| 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
The Path Computation Element (PCE) Architecture provide a framework to support the Constraint-Based Routing (CBR) functionality for traffic engineering systems in Multiprotocol Label Switching (MPLS) and Generalized Multiprotocol Label Switching (GMPLS) networks. The model define the PCC and PCE entities at the Control Plane, which communicate using a Request/Reply protocol. The PCE architecture enable network operators a tight control of the resource assignment by means of the administrative constraints that are included in the Traffic Enginnering Database (TED), and used in the path computation process. Moreover, appropriate objective funtions assist operators in the fulfillment of the overall network objectives. This document present a system architecture for the PCE, namely Routing and Management Agent (RMA), with a standard management interface, which permit established management frameworks to rely on the PCE for the CBR functionality and inject network-wide policies into the PCE path computation process. Some reliability issues of the PCE Architecture are addressed in the document.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)