[IPsec] RFC 5685 on Redirect Mechanism for the Internet Key Exchange Protocol Version 2 (IKEv2)

rfc-editor@rfc-editor.org Fri, 06 November 2009 00:08 UTC

Return-Path: <rfc-editor@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 9125828C165; Thu, 5 Nov 2009 16:08:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.933
X-Spam-Level:
X-Spam-Status: No, score=-16.933 tagged_above=-999 required=5 tests=[AWL=0.066, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
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 qTLo3u1bvcAi; Thu, 5 Nov 2009 16:08:35 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 9AAE628C149; Thu, 5 Nov 2009 16:08:35 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id E4A9F3607E5; Thu, 5 Nov 2009 16:05:14 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20091106000514.E4A9F3607E5@bosco.isi.edu>
Date: Thu, 5 Nov 2009 16:05:14 -0800 (PST)
Cc: ipsec@ietf.org, rfc-editor@rfc-editor.org
Subject: [IPsec] RFC 5685 on Redirect Mechanism for the 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: Fri, 06 Nov 2009 00:08:36 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5685

        Title:      Redirect Mechanism for the Internet 
                    Key Exchange Protocol Version 2 (IKEv2) 
        Author:     V. Devarapalli, K. Weniger
        Status:     Standards Track
        Date:       November 2009
        Mailbox:    vijay@wichorus.com, 
                    kilian.weniger@googlemail.com
        Pages:      15
        Characters: 35100
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ipsecme-ikev2-redirect-13.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5685.txt

The Internet Key Exchange Protocol version 2 (IKEv2) is a protocol
for setting up Virtual Private Network (VPN) tunnels from a remote
location to a gateway so that the VPN client can access services in
the network behind the gateway.  This document defines an IKEv2
extension that allows an overloaded VPN gateway or a VPN gateway that
is being shut down for maintenance to redirect the VPN client to
attach to another gateway.  The proposed mechanism can also be used
in Mobile IPv6 to enable the home agent to redirect the mobile node
to another home agent.  [STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  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
USC/Information Sciences Institute