Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Authors:

F. Le Faucheur
B. Davie
P. Bose
C. Christou
M. Davenport

Stream:

IETF

Source:

tsvwg (wit)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC4860

Discuss this RFC: Send questions or comments to the mailing listtsvwg@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 4860

Abstract

RFC 3175 defines aggregate Resource ReSerVation Protocol (RSVP)reservations allowing resources to be reserved in a Diffserv networkfor a given Per Hop Behavior (PHB), or given set of PHBs, from agiven source to a given destination. RFC 3175 also defines howend-to-end RSVP reservations can be aggregated onto such aggregatereservations when transiting through a Diffserv cloud. There aresituations where multiple such aggregate reservations are needed forthe same source IP address, destination IP address, and PHB (or set ofPHBs). However, this is not supported by the aggregate reservationsdefined in RFC 3175. In order to support this, the present documentdefines a more flexible type of aggregate RSVP reservations, referredto as generic aggregate reservation. Multiple such generic aggregatereservations can be established for a given PHB (or set of PHBs) froma given source IP address to a given destination IP address. Thegeneric aggregate reservations may be used to aggregate end-to-endRSVP reservations. This document also defines the procedures for suchaggregation. The generic aggregate reservations may also be usedend-to-end directly by end-systems attached to a Diffserv network. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.