IPv6 Configuration in IKEv2
draft-eronen-ipsec-ikev2-ipv6-config-05

 
Document Type Replaced Internet-Draft (individual)
Last updated 2008-12-01 (latest revision 2008-10-28)
Replaced by draft-ietf-ipsecme-ikev2-ipv6-config
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-ipsecme-ikev2-ipv6-config
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-eronen-ipsec-ikev2-ipv6-config-05.txt

Abstract

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.

Authors

Pasi Eronen (pe@iki.fi)
Julien Laganier (julien.ietf@gmail.com)
Cheryl Madson (cmadson@cisco.com)

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