RFC 2402: IP Authentication Header
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4302, 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 IP Authentication Header (AH) is used to provide connectionless integrity and data origin authentication for IP datagrams (hereafter referred to as just "authentication"), and to provide protection against replays. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2402
- Published
- November 1998
- Authors
- S. Kent; R. Atkinson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 22
- Also known as
- —
- Obsoletes:
- RFC 1826
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 4303IP Encapsulating Security Payload (ESP)Current
December 2005
- RFC 2406IP Encapsulating Security Payload (ESP)Obsoleted
November 1998
- RFC 4835Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)Obsoleted
April 2007
- RFC 1828IP Authentication using Keyed MD5Current
August 1995
- RFC 1827IP Encapsulating Security Payload (ESP)Obsoleted
August 1995
- RFC 4301Security Architecture for the Internet ProtocolUpdated
December 2005
- RFC 2401Security Architecture for the Internet ProtocolObsoleted
November 1998
- RFC 2407The Internet IP Security Domain of Interpretation for ISAKMPObsoleted
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?