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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Author Yoav Nir 
Last updated 2011-11-19 (latest revision 2011-07-11)
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                             Y. Nir
Internet-Draft                                               Check Point
Intended status: Standards Track                                   Q. Wu
Expires: May 22, 2012                                             Huawei
                                                       November 19, 2011

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

Abstract

   This document describes an extension to the IKEv2 protocol that
   allows an IKE Security Association (SA) to be created and
   authenticated using the EAP Re-authentication Protocol extension as
   described in RFC 5296 and its bis document.

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 May 22, 2012.

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
   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 May 22, 2012                  [Page 1]
Internet-Draft                 ERX for IKE                 November 2011

1.  Introduction

   IKEv2, as specified in [RFC5996], allows authentication of the
   initiator using an EAP method.  This is described in section 2.16.
   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 descripted in
   [RFC5296bis], 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.

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

   Several scenarios motivated this proposal:
   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-2-site VPN), this is not
      efficient, and it is more desirable to have the client initiate
      three different tunnels.  It is, however, not desirable to have
      the user type in a password three times.
   o  Roaming.  In these days of mobile phones and tablets, users often
      move from the wireless LAN in their office, where access may be
      granted through 802.1x, to a cellular network where VPN is
      necessary and back again.  Both the VPN server and the 802.1x

Nir & Wu                  Expires May 22, 2012                  [Page 2]
Internet-Draft                 ERX for IKE                 November 2011

      access point are authenticators that connect to the same AAA
Show full document text