Extensions to the Path Computation Element Protocol (PCEP) for residual path bandwidth support
draft-lazzeri-pce-residual-bw-01
| Document | Type | Expired Internet-Draft (candidate for pce WG) | |
|---|---|---|---|
| Last updated | 2019-02-11 (latest revision 2018-02-26) | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-lazzeri-pce-residual-bw-01.txt
Abstract
The PCEP protocol has objective functions to optimize path attributes like the residual bandwidth. While this is enough for some applications, it's not possible to return the computed values of such attributes to the PCC, or put bounds on them. This document describes extensions to the PCE Communication Protocol (PCEP) providing new path-related bandwidth metrics allowing a PCE to compute paths taking into account and returning to the PCC information about the remaining bandwidth along the computed paths.
Authors
Francesco Lazzeri
(francesco.lazzeri@ericsson.com)
Daniele Ceccarelli
(daniele.ceccarelli@ericsson.com)
Young Lee
(leeyoung@huawei.com)
Dhruv Dhody
(dhruv.ietf@gmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)