Definition of the MPLS FlowSpec for RSVP-TE
draft-iovanna-rsvp-mpls-flowspec-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Paola Iovanna , Roberto Mameli , Giovanna Piantanida , Stefano Salsano | ||
| Last updated | 2001-10-15 | ||
| 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 support of QoS Differentiation in MPLS is based on the definition of two types of LSP, respectively E-LSP and L-LSP (see [11]). Both E-LSP and L-LSP can be established with bandwidth reservation. In this case bandwidth requirements for the LSP must be signaled at LSP establishment time, in order to perform admission control in the LSRs in the path. If RSVP-TE is used as setup protocol, it has to support the signaling of bandwidth requirements for the LSPs. In this document we extend the RSVP-TE capability by defining a new type of Sender_Tspec (and FlowSpec), explicitly designed to allow signaling of bandwidth requirements for E-LSP and L-LSP set up. This new type, called MPLS Sender_Tspec (MPLS FlowSpec), can include bandwidth requirements for different classes inside the LSP.
Authors
Paola Iovanna
Roberto Mameli
Giovanna Piantanida
Stefano Salsano
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)