metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 8221: Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload (ESP) and Authentication Header (AH)

Still current, but amended. Parts of this document are changed or extended by RFC 9395. Read both.

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

This document replaces RFC 7321, "Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload (ESP) and Authentication Header (AH)". The goal of this document is to enable ESP and AH to benefit from cryptography that is up to date while making IPsec interoperable.

Document record

Document ID
RFC8221
Published
October 2017
Authors
P. Wouters; D. Migault; J. Mattsson; Y. Nir; T. Kivinen
Status
PROPOSED STANDARD
Stream
IETF
Area
sec
Pages
15
Also known as
—
Obsoletes:
RFC 7321
Updated by:
RFC 9395

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) →

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.

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/8221-cryptographic-algorithm-implementation-requirements-and-usage-guidance-for-encap