CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 17:06:09 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=bKFyaLe2IJ4.S2iAJH3hKsP5EyK18wMhWm_os9rq2dQ-1760115969-1.0.1.1-W6Db6jZIFgpTNx5UAimRpysfE3h6d.RlP9t09pbt.hIy_tsw5c3x4t6ThIKmT8bXN6unSS_rgHAlEJ0abaPSHFU7qVHPlzCNS4k1YEbZ1WU; path=/; expires=Fri, 10-Oct-25 17:36:09 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c7b4e33dedea32-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 2401 » RFC Editor
Search RFCs
RFC 2401
Security Architecture for the Internet Protocol, November 1998
- File formats:
- Status:
- PROPOSED STANDARD
- Obsoletes:
- RFC 1825
- Obsoleted by:
- RFC 4301
- Updated by:
- RFC 3168
- Authors:
- S. Kent
R. Atkinson - Stream:
- IETF
- Source:
- ipsec (sec)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC2401
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 2401
Abstract
This memo specifies the base architecture for IPsec compliant systems. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us