RFC 7296 - Internet Key Exchange Protocol Version 2 (IKEv2)
- Status: Internet Standard
- Published: October 2014
- Stream: IETF
- Obsoletes: RFC 5996
- Errata: RFC 7296 Errata
Document Information
- RFC Number: 7296
- Title: Internet Key Exchange Protocol Version 2 (IKEv2)
- Authors: C. Kaufman, P. Hoffman, Y. Nir, P. Eronen, T. Kivinen
- Date: October 2014
- Category: Standards Track
- Obsoletes: RFC 5996
- ISSN: 2070-1721
Abstract
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 obsoletes RFC 5996, and includes all of the errata for it. It advances IKEv2 to be an Internet Standard.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7296.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.
Table of Contents
- 1. Introduction
- 1.1. Usage Scenarios
- 1.2. The Initial Exchanges
- 1.3. The CREATE_CHILD_SA Exchange
- 1.4. The INFORMATIONAL Exchange
- 1.5. Informational Messages outside of an IKE SA
- 1.6. Requirements Terminology
- 1.7. Significant Differences between RFC 4306 and RFC 5996
- 1.8. Differences between RFC 5996 and This Document
- 2. IKE Protocol Details and Variations
- 2.1. Use of Retransmission Timers
- 2.2. Use of Sequence Numbers for Message ID
- 2.3. Window Size for Overlapping Requests
- 2.4. State Synchronization and Connection Timeouts
- 2.5. Version Numbers and Forward Compatibility
- 2.6. IKE SA SPIs and Cookies
- 2.7. Cryptographic Algorithm Negotiation
- 2.8. Rekeying
- 2.9. Traffic Selector Negotiation
- 2.10. Nonces
- 2.11. Address and Port Agility
- 2.12. Reuse of Diffie-Hellman Exponentials
- 2.13. Generating Keying Material
- 2.14. Generating Keying Material for the IKE SA
- 2.15. Authentication of the IKE SA
- 2.16. Extensible Authentication Protocol Methods
- 2.17. Generating Keying Material for Child SAs
- 2.18. Rekeying IKE SAs Using a CREATE_CHILD_SA Exchange
- 2.19. Requesting an Internal Address on a Remote Network
- 2.20. Requesting the Peer's Version
- 2.21. Error Handling
- 2.22. IPComp
- 2.23. NAT Traversal
- 2.24. Explicit Congestion Notification (ECN)
- 2.25. Exchange Collisions
- 3. Header and Payload Formats
- 3.1. The IKE Header
- 3.2. Generic Payload Header
- 3.3. Security Association Payload
- 3.4. Key Exchange Payload
- 3.5. Identification Payloads
- 3.6. Certificate Payload
- 3.7. Certificate Request Payload
- 3.8. Authentication Payload
- 3.9. Nonce Payload
- 3.10. Notify Payload
- 3.11. Delete Payload
- 3.12. Vendor ID Payload
- 3.13. Traffic Selector Payload
- 3.14. Encrypted Payload
- 3.15. Configuration Payload
- 3.16. Extensible Authentication Protocol (EAP) Payload
- 4. Conformance Requirements
- 5. Security Considerations
- 6. IANA Considerations
- 7. References
- Acknowledgements
- Authors' Addresses