Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload (ESP) and Authentication Header (AH)
This specification has been revised 9 times since RFC 1826 (1995). Each document below formally obsoleted the one before it; the versions still in force are listed first.
Revision timeline
Current versions — implement against these
- RFC 4302IP Authentication HeaderCurrentDecember 2005proposed standard
- RFC 4303IP Encapsulating Security Payload (ESP)CurrentDecember 2005proposed standard
- RFC 8221Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload (ESP) and Authentication Header (AH)UpdatedOctober 2017proposed standard
Superseded versions — historical reference only
- RFC 1826IP Authentication HeaderObsoletedAugust 1995proposed standardreplaced by RFC2402
- RFC 1827IP Encapsulating Security Payload (ESP)ObsoletedAugust 1995proposed standardreplaced by RFC2406
- RFC 2402IP Authentication HeaderObsoletedNovember 1998proposed standardreplaced by RFC4302, RFC4305
- RFC 2406IP Encapsulating Security Payload (ESP)ObsoletedNovember 1998proposed standardreplaced by RFC4303, RFC4305
- RFC 4305Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)ObsoletedDecember 2005proposed standardreplaced by RFC4835
- RFC 4835Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)ObsoletedApril 2007proposed standardreplaced by RFC7321
- RFC 7321Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload (ESP) and Authentication Header (AH)ObsoletedAugust 2014proposed standardreplaced by RFC8221
This lineage is derived automatically from the “obsoletes” relationships recorded in the public RFC Editor index — no editorial judgement is applied to the ordering. The most recent document in the chain is RFC 8221 (October 2017).