RFC 2411: IP Security Document Roadmap
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6071.
Current version: RFC 6071 — IP Security (IPsec) and Internet Key Exchange (IKE) Document Roadmap
In plain English — editorial summary, not part of the RFC
This document is intended to provide guidelines for the development of collateral specifications describing the use of new encryption and authentication algorithms with the ESP protocol, described in and new authentication algorithms used with the AH protocol. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2411
- Published
- November 1998
- Authors
- R. Thayer; N. Doraswamy; R. Glenn
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 11
- Also known as
- —
- Obsoleted by:
- RFC 6071
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1828IP Authentication using Keyed MD5Current
August 1995
- RFC 4302IP Authentication HeaderCurrent
December 2005
- RFC 4303IP Encapsulating Security Payload (ESP)Current
December 2005
- RFC 4305Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)Obsoleted
December 2005
- RFC 4306Internet Key Exchange (IKEv2) ProtocolObsoleted
December 2005
- RFC 4835Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)Obsoleted
April 2007
- RFC 2409The Internet Key Exchange (IKE)Obsoleted
November 1998
- RFC 2407The Internet IP Security Domain of Interpretation for ISAKMPObsoleted
November 1998
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?