RFC 2406: IP Encapsulating Security Payload (ESP)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4303, RFC 4305.
Current document in this lineage: RFC 4302 — IP Authentication Header; RFC 4303 — IP Encapsulating Security Payload (ESP); RFC 8221 — Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload (ESP) and Authentication Header (AH)
In plain English — editorial summary, not part of the RFC
The Encapsulating Security Payload (ESP) header is designed to provide a mix of security services in IPv4 and IPv6. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2406
- Published
- November 1998
- Authors
- S. Kent; R. Atkinson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 22
- Also known as
- —
- Obsoletes:
- RFC 1827
Topics
Standards lineage
This document is one revision in a chain of 10 RFCs, each formally replacing the one before it.
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4835Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)Obsoleted
April 2007
- RFC 4302IP Authentication HeaderCurrent
December 2005
- RFC 2402IP Authentication HeaderObsoleted
November 1998
- RFC 1826IP Authentication HeaderObsoleted
August 1995
- RFC 1829The ESP DES-CBC TransformCurrent
August 1995
- RFC 4301Security Architecture for the Internet ProtocolUpdated
December 2005
- RFC 2407The Internet IP Security Domain of Interpretation for ISAKMPObsoleted
November 1998
- RFC 2401Security Architecture for the Internet ProtocolObsoleted
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?