[IPsec] RFC 5739 on IPv6 Configuration in Internet Key Exchange Protocol Version 2 (IKEv2)
rfc-editor@rfc-editor.org Thu, 18 February 2010 18:21 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipsec@core3.amsl.com
Delivered-To: ipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 89E5128C315; Thu, 18 Feb 2010 10:21:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level:
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[AWL=-0.023, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DBNLVM6d5Pjc; Thu, 18 Feb 2010 10:21:28 -0800 (PST)
Received: from rfc-editor.org (rfcpa [64.170.98.47]) by core3.amsl.com (Postfix) with ESMTP id 44FE728C313; Thu, 18 Feb 2010 10:21:28 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 02C2D130018; Thu, 18 Feb 2010 10:23:11 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20100218182312.02C2D130018@rfc-editor.org>
Date: Thu, 18 Feb 2010 10:23:11 -0800
Cc: ipsec@ietf.org, rfc-editor@rfc-editor.org
Subject: [IPsec] RFC 5739 on IPv6 Configuration in Internet Key Exchange Protocol Version 2 (IKEv2)
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipsec>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Feb 2010 18:21:29 -0000
A new Request for Comments is now available in online RFC libraries. RFC 5739 Title: IPv6 Configuration in Internet Key Exchange Protocol Version 2 (IKEv2) Author: P. Eronen, J. Laganier, C. Madson Status: Experimental Date: February 2010 Mailbox: pasi.eronen@nokia.com, julienl@qualcomm.com, cmadson@cisco.com Pages: 32 Characters: 67691 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ipsecme-ikev2-ipv6-config-03.txt URL: http://www.rfc-editor.org/rfc/rfc5739.txt 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". This document defines an Experimental Protocol for the Internet community. This document is a product of the IP Security Maintenance and Extensions Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC