metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 3175: Aggregation of RSVP for IPv4 and IPv6 Reservations

Still current, but amended. Parts of this document are changed or extended by RFC 5350. Read both.

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC3175
Published
September 2001
Authors
F. Baker; C. Iturralde; F. Le Faucheur; B. Davie
Status
PROPOSED STANDARD
Stream
IETF
Area
tsv
Pages
36
Also known as
—
Updated by:
RFC 5350

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/3175-aggregation-of-rsvp-for-ipv4-and-ipv6-reservations