RFC 4301: Security Architecture for the Internet Protocol
In plain English — editorial summary, not part of the RFC
This document describes an updated version of the "Security Architecture for IP", which is designed to provide security services for traffic at the IP layer. This document obsoletes RFC 2401 (November 1998). [STANDARDS-TRACK]
Document record
- Document ID
- RFC4301
- Published
- December 2005
- Authors
- S. Kent; K. Seo
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 101
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1825 (1995)
- RFC 2401 (1998)
- RFC 4301 (2005)
Read the full history of Security Architecture for the Internet Protocol →
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 4302IP Authentication HeaderCurrent
December 2005
- RFC 4303IP Encapsulating Security Payload (ESP)Current
December 2005
- RFC 4304Extended Sequence Number (ESN) Addendum to IPsec Domain of Interpretation (DOI) for Internet Security Association and Key Management Protocol (ISAKMP)Current
December 2005
- RFC 4305Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)Obsoleted
December 2005
- RFC 4835Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)Obsoleted
April 2007
- RFC 2857The Use of HMAC-RIPEMD-160-96 within ESP and AHCurrent
June 2000
- RFC 2406IP Encapsulating Security Payload (ESP)Obsoleted
November 1998
- RFC 2403The Use of HMAC-MD5-96 within ESP and AHCurrent
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?