RFC 2409: The Internet Key Exchange (IKE)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4306.
Current document in this lineage: RFC 7296 — Internet Key Exchange Protocol Version 2 (IKEv2)
In plain English — editorial summary, not part of the RFC
This memo describes a hybrid protocol. The purpose is to negotiate, and provide authenticated keying material for, security associations in a protected manner. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2409
- Published
- November 1998
- Authors
- D. Harkins; D. Carrel
- Status
- HISTORIC
- Stream
- IETF
- Area
- sec
- Pages
- 41
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 7 RFCs, each formally replacing the one before it.
- RFC 2407 (1998)
- RFC 2408 (1998)
- RFC 2409 (1998)
- RFC 4306 (2005)
- RFC 4718 (2006)
- RFC 5996 (2010)
- RFC 7296 (2014) ✓
Read the full history of Internet Key Exchange Protocol Version 2 (IKEv2) →
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 2407The Internet IP Security Domain of Interpretation for ISAKMPObsoleted
November 1998
- RFC 4302IP Authentication HeaderCurrent
December 2005
- RFC 4303IP Encapsulating Security Payload (ESP)Current
December 2005
- RFC 1828IP Authentication using Keyed MD5Current
August 1995
- RFC 4301Security Architecture for the Internet ProtocolUpdated
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 2408Internet Security Association and Key Management Protocol (ISAKMP)Obsoleted
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?