Aggregation of RSVP for IPv4 and IPv6 Reservations
RFC 3175, “Aggregation of RSVP for IPv4 and IPv6 Reservations”, is a Proposed Standard document published in September 2001 by F. Baker, C. Iturralde, F. Le Faucheur, B. Davie. It has since been updated by RFC 5350. The canonical text is published by the RFC Editor.
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 3175 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3174 US Secure Hash Algorithm 1
- RFC 3176 InMon Corporation's sFlow: A Method for Monitoring Traffic in Switched and Routed Networks
- RFC 3173 IP Payload Compression Protocol
- RFC 3177 IAB/IESG Recommendations on IPv6 Address Allocations to Sites
- RFC 3172 Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain
- RFC 3178 IPv6 Multihoming Support at Site Exit Routers
- RFC 3171 IANA Guidelines for IPv4 Multicast Address Assignments
- RFC 3179 Script MIB Extensibility Protocol Version 1.1