datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

IPv6 Configuration in Internet Key Exchange Protocol Version 2 (IKEv2)
draft-ietf-ipsecme-ikev2-ipv6-config-03

RFC
Document Stream: IETF
Last updated: 2009-10-26
Replaces: draft-eronen-ipsec-ikev2-ipv6-config
Intended RFC status: Experimental
Other versions: (expired, archived): plain text, pdf, html

Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 5739
IANA Action State: RFC-Ed-Ack 
Responsible AD: Tim Polk
Send notices to: ipsecme-chairs@tools.ietf.org, draft-ietf-ipsecme-ikev2-ipv6-config@tools.ietf.org

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-ipsecme-ikev2-ipv6-config.

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". This document defines an Experimental Protocol for the Internet community.

Authors:
Cheryl Madson <cmadson@cisco.com>
Pasi Eronen <pasi.eronen@nokia.com>
Julien Laganier <julienl@qualcomm.com>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)