Extensions to Path Computation Element Communication Protocol (PCEP) for handling the Link Bandwidth Utilization
draft-wu-pce-pcep-link-bw-utilization-03
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Qin Wu , Dhruv Dhody , Stefano Previdi | ||
| Last updated | 2014-12-15 (Latest revision 2014-06-24) | ||
| Replaced by | draft-ietf-pce-pcep-service-aware | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-pce-pcep-service-aware | |
| 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 Communication Protocol (PCEP) provides mechanisms for Path Computation Elements (PCEs) to perform path computations in response to Path Computation Clients (PCCs) requests. The Link bandwidth utilization (the total bandwidth of a link in current use for the forwarding) is an important factor to consider during path computation. [OSPF-TE-EXPRESS] and [ISIS-TE-EXPRESS] define mechanisms that distribute this information via OSPF and ISIS respectively. This document describes extensions to PCEP to use them as new constraints during path computation.
Authors
Qin Wu
Dhruv Dhody
Stefano Previdi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)