RFC 2205: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
In plain English — editorial summary, not part of the RFC
This memo describes version 1 of RSVP, a resource reservation setup protocol designed for an integrated services Internet. RSVP provides receiver-initiated setup of resource reservations for multicast or unicast data flows, with good scaling and robustness properties. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2205
- Published
- September 1997
- Authors
- R. Braden; L. Zhang; S. Berson; S. Herzog; S. Jamin
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 112
- Also known as
- —
Topics
Referenced by
6 later RFCs formally update or obsolete part of this document.
- RFC 2750RSVP Extensions for Policy ControlCurrent
January 2000
- RFC 3936Procedures for Modifying the Resource reSerVation Protocol (RSVP)Current
October 2004
- RFC 4495A Resource Reservation Protocol (RSVP) Extension for the Reduction of Bandwidth of a Reservation FlowCurrent
May 2006
- RFC 5946Resource Reservation Protocol (RSVP) Extensions for Path-Triggered RSVP Receiver ProxyCurrent
October 2010
- RFC 6437IPv6 Flow Label SpecificationCurrent
November 2011
- RFC 6780RSVP ASSOCIATION Object ExtensionsCurrent
October 2012
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3292General Switch Management Protocol (GSMP) V3Current
June 2002
- RFC 1946Native ATM Support for ST2+Current
May 1996
- RFC 2996Format of the RSVP DCLASS ObjectCurrent
November 2000
- RFC 2997Specification of the Null Service TypeCurrent
November 2000
- RFC 4094Analysis of Existing Quality-of-Service Signaling ProtocolsCurrent
May 2005
- RFC 7713Congestion Exposure (ConEx) Concepts, Abstract Mechanism, and RequirementsCurrent
December 2015
- RFC 2128Dial Control Management Information Base using SMIv2Current
March 1997
- RFC 2127ISDN Management Information Base using SMIv2Current
March 1997
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?