A new object to specify a Traffic Engineering (TE) Label Switch Path (LSP) cost
draft-dolganow-pce-cost-object-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Andrew Dolganow , JP Vasseur | ||
| Last updated | 2005-10-17 | ||
| 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
This document proposes a new object (named the COST object) used to specify the cost of a Traffic Engineering (TE) Label Switched Path (LSP). The COST object can be carried within an RSVP message so as to record a TE LSP cost during LSP establishment or within a Path Computation Element (PCE) path computation protocol message so as to provide the cost of a computed path to a Path Computation Client (PCC).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)