An IKEv2 Extension for Supporting ERP
draft-nir-ipsecme-erx-08

The information below is for an old version of the document
Document Type Active Internet-Draft (individual in sec area)
Authors Yoav Nir  , Qin Wu 
Last updated 2012-12-04
Stream IETF
Intended RFC status Experimental
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state (None)
Document shepherd None
IESG IESG state Waiting for AD Go-Ahead::AD Followup
Consensus Boilerplate Unknown
Telechat date
Responsible AD Sean Turner
IESG note Yaron Sheffer (yaronf.ietf@gmail.com) is the document shepherd
Send notices to ynir@checkpoint.com, sunseawq@huawei.com, draft-nir-ipsecme-erx@tools.ietf.org, yaronf.ietf@gmail.com
Network Working Group                                             Y. Nir
Internet-Draft                                               Check Point
Updates: 5996 (if approved)                                        Q. Wu
Intended status: Experimental                                     Huawei
Expires: June 7, 2013                                   December 4, 2012

                 An IKEv2 Extension for Supporting ERP
                        draft-nir-ipsecme-erx-08

Abstract

   This document updates the IKEv2 protocol, described in RFC 5996.
   This extension allows an IKE Security Association (SA) to be created
   and authenticated using the EAP Re-authentication Protocol extension
   as described in RFC 6696.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on June 7, 2013.

Copyright Notice

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

Nir & Wu                  Expires June 7, 2013                  [Page 1]
Internet-Draft                 ERX for IKE                 December 2012

1.  Introduction

   IKEv2, as specified in section 2.16 of [RFC5996], allows
   authentication of the initiator using an EAP method.  Using EAP
   significantly increases the count of round-trips required to
   establish the IPsec SA, and also may require user interaction.  This
   makes it inconvenient to allow a single remote access client to
   create multiple IPsec tunnels with multiple IPsec gateways that
   belong to the same domain.

   The EAP Re-authentication Protocol (ERP), as described in [RFC6696],
   allows an EAP peer to authenticate to multiple authenticators, while
   performing the full EAP method only once.  Subsequent authentications
   require fewer round-trips and no user interaction.

   Bringing these two technologies together allows a remote access IPsec
   client to create multiple tunnels with different gateways that belong
   to a single domain, as well as using the keys from other contexts of
   using EAP, such as network access within the same domain, to
   transparently connect to VPN gateways within this domain.

   Additionally, it allows for faster setting up of new tunnels when
   previous tunnels have been torn down due to things like network
   outage, device suspension, or temporarily moving out of range.  This
   is similar to the session resumption mechanism described in
   [RFC5723], except that instead of a ticket stored on the gateway, the
   rMSK is used as the session key stored on the AAA server.

1.1.  Conventions Used in This Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.  Usage Scenarios

   This work is motivated by the following scenarios:
   o  Multiple tunnels for a single remote access VPN client.  Suppose a
      company has offices in New York City, Paris, and Shanghai.  For
      historical reasons, the email server is located in the Paris
      office, while most of the servers hosting the company's intranet
      are located in Shanghai, and the finance department servers are in
      NYC.  An employee using remote access VPN may need to connect to
      servers from all three locations.  While it is possible to connect
      to a single gateway, and have that gateway route the requests to
      the other gateways (perhaps through site to site VPN), this is not
      efficient, and it is more desirable to have the client initiate

Nir & Wu                  Expires June 7, 2013                  [Page 2]
Internet-Draft                 ERX for IKE                 December 2012

      three different tunnels.  It is, however, not desirable to have
Show full document text