RFC 3936: Procedures for Modifying the Resource reSerVation Protocol (RSVP)
In plain English — editorial summary, not part of the RFC
This memo specifies procedures for modifying the Resource reSerVation Protocol (RSVP). This memo also lays out new assignment guidelines for number spaces for RSVP messages, object classes, class-types, and sub-objects. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC3936
- Published
- October 2004
- Authors
- K. Kompella; J. Lang
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- —
- Pages
- 7
- Also known as
- BCP96
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3210Applicability Statement for Extensions to RSVP for LSP-TunnelsCurrent
December 2001
- RFC 2380RSVP over ATM Implementation RequirementsCurrent
August 1998
- RFC 4124Protocol Extensions for Support of Diffserv-aware MPLS Traffic EngineeringCurrent
June 2005
- RFC 3726Requirements for Signaling ProtocolsCurrent
April 2004
- RFC 3477Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE)Updated
February 2003
- RFC 3182Identity Representation for RSVPCurrent
October 2001
- RFC 3181Signaled Preemption Priority Policy ElementCurrent
October 2001
- RFC 3175Aggregation of RSVP for IPv4 and IPv6 ReservationsUpdated
September 2001
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?