Browse Prior Art Database

A Quick Crash Detection Method for the Internet Key Exchange Protocol (IKE) (RFC6290)

IP.com Disclosure Number: IPCOM000208076D
Original Publication Date: 2011-Jun-01
Included in the Prior Art Database: 2011-Jun-22
Document File: 44 page(s) / 49K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

Y. Nir: AUTHOR [+5]

Abstract

IKEv2, as described in [RFC5996] and its predecessor RFC 4306, has a method for recovering from a reboot of one peer. As long as traffic flows in both directions, the rebooted peer should re-establish the tunnels immediately. However, in many cases, the rebooted peer is a VPN gateway that protects only servers, so all traffic is inbound. In other cases, the non-rebooted peer has a dynamic IP address, so the rebooted peer cannot initiate IKE because its current IP address is unknown. In such cases, the rebooted peer will not be able to re-establish the tunnels. Section 2 describes how recovery works under RFC 5996, and explains why it may take several minutes.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 6% of the total text.

Internet Engineering Task Force (IETF)                       Y. Nir, Ed. Request for Comments: 6290                                   Check Point Category: Standards Track                                  D. Wierbowski ISSN: 2070-1721                                                      IBM                                                              F. Detienne                                                                 P. Sethi                                                                    Cisco                                                                June 2011

                  A Quick Crash Detection Method for the                   Internet Key Exchange Protocol (IKE)

Abstract

   This document describes an extension to the Internet Key Exchange    Protocol version 2 (IKEv2) that allows for faster detection of    Security Association (SA) desynchronization using a saved token.

   When an IPsec tunnel between two IKEv2 peers is disconnected due to a    restart of one peer, it can take as much as several minutes for the    other peer to discover that the reboot has occurred, thus delaying    recovery.  In this text, we propose an extension to the protocol that    allows for recovery immediately following the restart.

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/rfc6290.

Copyright Notice

   Copyright (c) 2011 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

Nir, et al.                  Standards Track                    [Page 1]
 RFC 6290                  Quick Crash Detection                June 2011

    carefully, as they describe your rights and restrictions with respect   ...