Attention A T users. To access the menus on this page please perform the following steps. 1. Please switch auto forms mode to off. 2. Hit enter to expand a main menu option (Health, Benefits, etc). 3. To enter and activate the submenu links, hit the down arrow. You will now be able to tab or arrow up or down through the submenu options to access/activate the submenu links.

VA Technical Reference Model v 21.7

Internet Key Exchange (IKE)
Internet Key Exchange (IKE) Standard or Specification

General InformationGeneral Information help

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website: Go to site
Description: The Internet Key Exchange (IKE) is a protocol using part of Oakley and part of Secure Key Exchange Mechanism (SKEME) in conjunction with Internet Security Association and Key Management Protocol (ISAKMP) to obtain authenticated keying material for use with ISAKMP, and for other security associations such as Authentication Header (AH) and Encapsulating Security Payload (ESP) for the Internet Engineering Task Force (IETF) IPsec Domain of Interpretation (DOI).

IKE was updated to version two (IKEv2) in December 2005 by Request for Comment (RFC) 4306, followed by RFC 4718 on October 2006. These two documents were combined into the updated IKEv2 RFC 5996 published in September 2010. Also, an update for RFC 5996 was posted in July 2013 and is identified as RFC 6989; In October 2014, RFC 7296 obsoleted RFC 5996. In January 2015, RFC 7296 (also known as STD 79) was updated with Update identified as RFC 7427 and RFC 7670.
Technology/Standard Usage Requirements: Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:
Decision: View Decisions

Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v20.4
Decision Date: 04/16/2020
Introduced By: TRMSP
Standards Body: Internet Engineering Task Force (IETF)
- The information contained on this page is accurate as of the Decision Date (04/16/2020).