RFC 4230: RSVP Security Properties
In plain English — editorial summary, not part of the RFC
This document summarizes the security properties of RSVP. The goal of this analysis is to benefit from previous work done on RSVP and to capture knowledge about past activities. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4230
- Published
- December 2005
- Authors
- H. Tschofenig; R. Graveman
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 48
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3726Requirements for Signaling ProtocolsCurrent
April 2004
- RFC 3175Aggregation of RSVP for IPv4 and IPv6 ReservationsUpdated
September 2001
- RFC 3097RSVP Cryptographic Authentication -- Updated Message Type ValueCurrent
April 2001
- RFC 2997Specification of the Null Service TypeCurrent
November 2000
- RFC 2996Format of the RSVP DCLASS ObjectCurrent
November 2000
- RFC 2961RSVP Refresh Overhead Reduction ExtensionsUpdated
April 2001
- RFC 2814SBM (Subnet Bandwidth Manager): A Protocol for RSVP-based Admission Control over IEEE 802-style networksCurrent
May 2000
- RFC 2747RSVP Cryptographic AuthenticationUpdated
January 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?