RFC 4860: Generic Aggregate Resource ReSerVation Protocol (RSVP) Reservations
In plain English — editorial summary, not part of the RFC
RFC 3175 defines aggregate Resource ReSerVation Protocol (RSVP) reservations allowing resources to be reserved in a Diffserv network for a given Per Hop Behavior (PHB), or given set of PHBs, from a given source to a given destination. RFC 3175 also defines how end-to-end RSVP reservations can be aggregated onto such aggregate reservations when transiting through a Diffserv cloud. There are situations where multiple such aggregate reservations are needed for the same source IP address, destination IP address, and PHB (or set of PHBs). However, this is not supported by the aggregate reservations defined in RFC 3175. In order to support this, the present document defines a more flexible type of aggregate RSVP reservations, referred to as generic aggregate reservation. Multiple such generic aggregate reservations can be established for a given PHB (or set of PHBs) from a given source IP address to a given destination IP address. The generic aggregate reservations may be used to aggregate end-to-end RSVP reservations. This document also defines the procedures for such aggregation. The generic aggregate reservations may also be used end-to-end directly by end-systems attached to a Diffserv network. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4860
- Published
- May 2007
- Authors
- F. Le Faucheur; B. Davie; P. Bose; C. Christou; M. Davenport
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 32
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4542Implementing an Emergency Telecommunications Service (ETS) for Real-Time Services in the Internet Protocol SuiteUpdated
May 2006
- RFC 3308Layer Two Tunneling Protocol (L2TP) Differentiated Services ExtensionCurrent
November 2002
- RFC 3248A Delay Bound alternative revision of RFC 2598Current
March 2002
- RFC 3140Per Hop Behavior Identification CodesCurrent
June 2001
- RFC 4594Configuration Guidelines for DiffServ Service ClassesUpdated
August 2006
- RFC 8100Diffserv-Interconnection Classes and PracticeCurrent
March 2017
- RFC 3246An Expedited Forwarding PHB (Per-Hop Behavior)Current
March 2002
- RFC 2836Per Hop Behavior Identification CodesObsoleted
May 2000
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?