Skip to main content

IPv6 Configuration in IKEv2

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Pasi Eronen , Julien Laganier , Cheryl R. Madson
Last updated 2008-12-01 (Latest revision 2008-10-28)
Replaced by RFC 5739
RFC stream (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-ipsecme-ikev2-ipv6-config
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


When 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 describes the limitations of current IKEv2 configuration payloads for IPv6, and explores possible solutions that would allow IKEv2 to set up full- featured virtual IPv6 interfaces.


Pasi Eronen
Julien Laganier
Cheryl R. Madson

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