RFC 5996: Internet Key Exchange Protocol Version 2 (IKEv2)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7296.
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 document describes version 2 of the Internet Key Exchange (IKE) protocol. IKE is a component of IPsec used for performing mutual authentication and establishing and maintaining Security Associations (SAs). This document replaces and updates RFC 4306, and includes all of the clarifications from RFC 4718. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5996
- Published
- September 2010
- Authors
- C. Kaufman; P. Hoffman; Y. Nir; P. Eronen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 138
- Also known as
- —
- Obsoleted by:
- RFC 7296
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
3 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 4301Security Architecture for the Internet ProtocolUpdated
December 2005
- RFC 7018Auto-Discovery VPN Problem Statement and RequirementsCurrent
September 2013
- RFC 7427Signature Authentication in the Internet Key Exchange Version 2 (IKEv2)Current
January 2015
- RFC 7634ChaCha20, Poly1305, and Their Use in the Internet Key Exchange Protocol (IKE) and IPsecCurrent
August 2015
- RFC 4307Cryptographic Algorithms for Use in the Internet Key Exchange Version 2 (IKEv2)Obsoleted
December 2005
- RFC 4303IP Encapsulating Security Payload (ESP)Current
December 2005
- RFC 4302IP Authentication HeaderCurrent
December 2005
- RFC 8221Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload (ESP) and Authentication Header (AH)Updated
October 2017
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?