Document Action: 'IPv6 Configuration in IKEv2' to Experimental RFC

The IESG <> Sun, 08 November 2009 04:35 UTC

Return-Path: <>
Received: by (Postfix, from userid 30) id D4B403A68CB; Sat, 7 Nov 2009 20:35:44 -0800 (PST)
X-idtracker: yes
From: The IESG <>
To: IETF-Announce <>
Subject: Document Action: 'IPv6 Configuration in IKEv2' to Experimental RFC
Message-Id: <>
Date: Sat, 07 Nov 2009 20:35:44 -0800
Cc: ipsecme mailing list <>, ipsecme chair <>, Internet Architecture Board <>, RFC Editor <>
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 08 Nov 2009 04:35:44 -0000

The IESG has approved the following document:

- 'IPv6 Configuration in IKEv2 '
   <draft-ietf-ipsecme-ikev2-ipv6-config-03.txt> as an Experimental RFC

This document is the product of the IP Security Maintenance and Extensions Working Group. 

The IESG contact persons are Tim Polk and Pasi Eronen.

A URL of this Internet-Draft is:

Technical Summary

This document describes new IKEv2 configuration attributes that let an
IPsec security gateway assign IPv6 prefixes to a VPN client clients. This
is needed because IKEv2 currently does not handle all features of IPv6
that it should, such as enabling a virtual link.

Working Group Summary

The document has light consensus of the IPsecME WG with no objections to
publication as an Experimental RFC.

Document Quality

There was initial interest in this protocol from many participants, but
only a few seem to have done an in-depth review. Despite that, the
document has no obvious problems and could turn out to be quite useful as
there is greater deployment of IPsec in IPv6 environments. This document
should be revisited as more implementations of remote access IPv6 IPsec
are created and deployed.


   Paul Hoffman is the Document Shepherd; Tim Polk is the 
   Responsible Area Director.