datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

IPv6 Configuration in Internet Key Exchange Protocol Version 2 (IKEv2)
RFC 5739

Internet Engineering Task Force (IETF)                         P. Eronen
Request for Comments: 5739                                         Nokia
Category: Experimental                                       J. Laganier
ISSN: 2070-1721                                           QUALCOMM, Inc.
                                                               C. Madson
                                                           Cisco Systems
                                                           February 2010

 IPv6 Configuration in Internet Key Exchange Protocol Version 2 (IKEv2)

Abstract

   When Internet Key Exchange Protocol version 2 (IKEv2) is used for
   remote VPN access (client to VPN gateway), the gateway assigns the
   client an IP address from the internal network using IKEv2
   configuration payloads.  The configuration payloads specified in RFC
   4306 work well for IPv4 but make it difficult to use certain features
   of IPv6.  This document specifies new configuration attributes for
   IKEv2 that allows the VPN gateway to assign IPv6 prefixes to clients,
   enabling all features of IPv6 to be used with the client-gateway
   "virtual link".

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for examination, experimental implementation, and
   evaluation.

   This document defines an Experimental Protocol for the Internet
   community.  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).  Not
   all documents approved by the IESG are a candidate for any level of
   Internet Standard; see 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/rfc5739.

Eronen, et al.                Experimental                      [Page 1]
RFC 5739               IPv6 Configuration in IKEv2         February 2010

Copyright Notice

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

Eronen, et al.                Experimental                      [Page 2]
RFC 5739               IPv6 Configuration in IKEv2         February 2010

Table of Contents

   1. Introduction and Problem Statement ..............................4
   2. Terminology .....................................................5
   3. Current Limitations and Goals ...................................6
      3.1. Multiple Prefixes ..........................................6
      3.2. Link-Local Addresses .......................................6
      3.3. Interface Identifier Selection .............................7
      3.4. Sharing VPN Access .........................................7
      3.5. General Goals ..............................................8
      3.6. Non-Goals ..................................................8
      3.7. Additional Information .....................................9
   4. Solution Details ................................................9
      4.1. Initial Exchanges ..........................................9
      4.2. Reauthentication ..........................................11
      4.3. Creating CHILD_SAs ........................................11
      4.4. Relationship to Neighbor Discovery ........................12

[include full document text]