RFC 2207: RSVP Extensions for IPSEC Data Flows
In plain English — editorial summary, not part of the RFC
This document presents extensions to Version 1 of RSVP. These extensions permit support of individual data flows using RFC 1826, IP Authentication Header (AH) or RFC 1827, IP Encapsulating Security Payload (ESP). [STANDARDS-TRACK]
Document record
- Document ID
- RFC2207
- Published
- September 1997
- Authors
- L. Berger; T. O'Malley
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2210The Use of RSVP with IETF Integrated ServicesCurrent
September 1997
- RFC 2379RSVP over ATM Implementation GuidelinesCurrent
August 1998
- RFC 2815Integrated Service Mappings on IEEE 802 NetworksCurrent
May 2000
- RFC 4094Analysis of Existing Quality-of-Service Signaling ProtocolsCurrent
May 2005
- RFC 1829The ESP DES-CBC TransformCurrent
August 1995
- RFC 2751Signaled Preemption Priority Policy ElementObsoleted
January 2000
- RFC 2752Identity Representation for RSVPObsoleted
January 2000
- RFC 3210Applicability Statement for Extensions to RSVP for LSP-TunnelsCurrent
December 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?