RFC 3175
Aggregation of RSVP for IPv4 and IPv6 Reservations, September 2001
- File formats:
- Status:
- PROPOSED STANDARD
- Updated by:
- RFC 5350
- Authors:
- F. Baker
C. Iturralde
F. Le Faucheur
B. Davie - Stream:
- IETF
- Source:
- issll (tsv)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC3175
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 3175
Abstract
This document describes the use of a single RSVP (Resource ReSerVation Protocol) reservation to aggregate other RSVP reservations across a transit routing region, in a manner conceptually similar to the use of Virtual Paths in an ATM (Asynchronous Transfer Mode) network. It proposes a way to dynamically create the aggregate reservation, classify the traffic for which the aggregate reservation applies, determine how much bandwidth is needed to achieve the requirement, and recover the bandwidth when the sub-reservations are no longer required. It also contains recommendations concerning algorithms and policies for predictive reservations. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.