Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload and Authentication Header
RFC 8221, “Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload and Authentication Header”, is a Proposed Standard document published in October 2017 by P. Wouters, D. Migault, J. Mattsson, Y. Nir, T. Kivinen. It obsoletes RFC 7321. It has since been updated by RFC 9395. The canonical text is published by the RFC Editor.
Abstract
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8221 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8220 Protocol Independent Multicast over Virtual Private LAN Service
- RFC 8222 Selecting Labels for Use with Conventional DNS and Other Resolution Systems in DNS-Based Service Discovery
- RFC 8219 Benchmarking Methodology for IPv6 Transition Technologies
- RFC 8223 Application-Aware Targeted LDP
- RFC 8218 Multipath Extension for the Optimized Link State Routing Protocol Version 2
- RFC 8217 Clarifications for When to Use the name-addr Production in SIP Messages
- RFC 8216 HTTP Live Streaming
- RFC 8215 Local-Use IPv4/IPv6 Translation Prefix