RFC 2209: Resource ReSerVation Protocol (RSVP) -- Version 1 Message Processing Rules
In plain English — editorial summary, not part of the RFC
This memo contains an algorithmic description of the rules used by an RSVP implementation for processing messages. It is intended to clarify the version 1 RSVP protocol specification. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2209
- Published
- September 1997
- Authors
- R. Braden; L. Zhang
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 25
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2207RSVP Extensions for IPSEC Data FlowsCurrent
September 1997
- RFC 2212Specification of Guaranteed Quality of ServiceCurrent
September 1997
- RFC 2205Resource ReSerVation Protocol (RSVP) -- Version 1 Functional SpecificationUpdated
September 1997
- RFC 2215General Characterization Parameters for Integrated Service Network ElementsCurrent
September 1997
- RFC 2216Network Element Service Specification TemplateCurrent
September 1997
- RFC 2996Format of the RSVP DCLASS ObjectCurrent
November 2000
- RFC 2997Specification of the Null Service TypeCurrent
November 2000
- RFC 2998A Framework for Integrated Services Operation over Diffserv NetworksCurrent
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?