metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 4303: IP Encapsulating Security Payload (ESP)

In plain English — editorial summary, not part of the RFC

This document describes an updated version of the Encapsulating Security Payload (ESP) protocol, which is designed to provide a mix of security services in IPv4 and IPv6. ESP is used to provide confidentiality, data origin authentication, connectionless integrity, an anti-replay service (a form of partial sequence integrity), and limited traffic flow confidentiality. This document obsoletes RFC 2406 (November 1998). [STANDARDS-TRACK]

Document record

Document ID
RFC4303
Published
December 2005
Authors
S. Kent
Status
PROPOSED STANDARD
Stream
IETF
Area
sec
Pages
44
Also known as
—
Obsoletes:
RFC 2406

Topics

Standards lineage

This document is one revision in a chain of 10 RFCs, each formally replacing the one before it.

  1. RFC 1826 (1995)
  2. RFC 1827 (1995)
  3. RFC 2402 (1998)
  4. RFC 2406 (1998)
  5. RFC 4302 (2005)
  6. RFC 4303 (2005)
  7. RFC 4305 (2005)
  8. RFC 4835 (2007)
  9. RFC 7321 (2014)
  10. RFC 8221 (2017) ✓

Read the full history of Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload (ESP) and Authentication Header (AH) →

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/4303-ip-encapsulating-security-payload-esp