CARVIEW |
Select Language
HTTP/2 200
date: Wed, 08 Oct 2025 10:13:02 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=LDdp3Let7eVe_TRb8iZY2AYuC2VfvMYILrZ3jNsvo7w-1759918382-1.0.1.1-bqGhNgXUH2cFMBwq92d5gN.VZaBuIpX2o4YAKyix_wjxt0s53UyIP8RWMXCxM9uwobnGyNbRnhRwoJhc.TSPdlDIek_biU8Ocm7CLREoQqg; path=/; expires=Wed, 08-Oct-25 10:43:02 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98b4dcf9cfdf9dfa-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 2408 » RFC Editor
Search RFCs
RFC 2408
Internet Security Association and Key Management Protocol (ISAKMP), November 1998
- File formats:
- Status:
- HISTORIC (changed from PROPOSED STANDARD)
- Obsoleted by:
- RFC 4306
- Authors:
- D. Maughan
M. Schertler
M. Schneider
J. Turner - Stream:
- IETF
- Source:
- ipsec (sec)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC2408
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 2408
Abstract
This memo describes a protocol utilizing security concepts necessary for establishing Security Associations (SA) and cryptographic keys in an Internet environment. [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