Generic Aggregate RSVP Reservations
draft-lefaucheur-rsvp-ipsec-02
| Document | Type |
Expired Internet-Draft
(individual in tsv area)
Expired & archived
|
|
|---|---|---|---|
| Author | François Le Faucheur | ||
| Last updated | 2015-10-14 (Latest revision 2005-10-21) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Stream | WG state | (None) | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Magnus Westerlund | ||
| IESG note | |||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
[RSVP-IPSEC] defines RSVP extensions for IPsec which permit support of reservations for individual IPsec flows, but it does not support aggregate reservations between the IPsec devices with Diffserv [DIFFSERV] classification and scheduling. Conversely, [RSVP-AGG] defines how to aggregate individual RSVP reservations over Aggregate IP reservations when the aggregation region supports Diffserv, but it does not address the case where the Aggregator and Deaggregator use IPsec. Also, [RSVP-AGG] does not address the case where multiple Aggregate reservations are needed for the same DSCP from the same Aggregator to the same Deaggregator. However, there are scenarios requiring aggregate reservations for IPsec tunnels or requiring multiple aggregate reservations for the same DSCP from a given Aggregator to a given Deaggregator. This document specifies the incremental RSVP extensions beyond those defined in [RSVP-IPSEC] and [RSVP-AGG] to support such reservations.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)