RFC 2208: Resource ReSerVation Protocol (RSVP) -- Version 1 Applicability Statement Some Guidelines on Deployment
In plain English — editorial summary, not part of the RFC
This document describes the applicability of RSVP along with the Integrated Services protocols and other components of resource reservation and offers guidelines for deployment of resource reservation at this time. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2208
- Published
- September 1997
- Authors
- A. Mankin; F. Baker; B. Braden; S. Bradner; M. O'Dell; A. Romanow; A. Weinrib; L. Zhang
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2205Resource ReSerVation Protocol (RSVP) -- Version 1 Functional SpecificationUpdated
September 1997
- RFC 2380RSVP over ATM Implementation RequirementsCurrent
August 1998
- RFC 2745RSVP Diagnostic MessagesCurrent
January 2000
- RFC 2746RSVP Operation Over IP TunnelsCurrent
January 2000
- RFC 2747RSVP Cryptographic AuthenticationUpdated
January 2000
- RFC 2814SBM (Subnet Bandwidth Manager): A Protocol for RSVP-based Admission Control over IEEE 802-style networksCurrent
May 2000
- RFC 2961RSVP Refresh Overhead Reduction ExtensionsUpdated
April 2001
- RFC 2996Format of the RSVP DCLASS ObjectCurrent
November 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?