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

Yaron Sheffer <yaronf@checkpoint.com> Fri, 06 November 2009 17:53 UTC

Return-Path: <yaronf@checkpoint.com>
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 952343A6946 for <ipsec@core3.amsl.com>; Fri, 6 Nov 2009 09:53:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.349
X-Spam-Level:
X-Spam-Status: No, score=-3.349 tagged_above=-999 required=5 tests=[AWL=-0.350, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_LOW=-1]
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 48RumlUXdac7 for <ipsec@core3.amsl.com>; Fri, 6 Nov 2009 09:53:08 -0800 (PST)
Received: from michael.checkpoint.com (michael.checkpoint.com [194.29.32.68]) by core3.amsl.com (Postfix) with ESMTP id 222D23A68F7 for <ipsec@ietf.org>; Fri, 6 Nov 2009 09:53:07 -0800 (PST)
Received: from il-ex01.ad.checkpoint.com (localhost [127.0.0.1]) by michael.checkpoint.com (8.12.10+Sun/8.12.10) with ESMTP id nA6HrTc6015177 for <ipsec@ietf.org>; Fri, 6 Nov 2009 19:53:29 +0200 (IST)
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Fri, 6 Nov 2009 19:53:33 +0200
From: Yaron Sheffer <yaronf@checkpoint.com>
To: "ipsec@ietf.org" <ipsec@ietf.org>
Date: Fri, 6 Nov 2009 19:53:31 +0200
Thread-Topic: RFC 5685 on Redirect Mechanism for the Internet Key Exchange Protocol Version 2 (IKEv2)
Thread-Index: AcpedWniBLYGErp3ReWSoDx9L4qBRQAlFbLg
Message-ID: <7F9A6D26EB51614FBF9F81C0DA4CFEC801BDF872B99A@il-ex01.ad.checkpoint.com>
References: <20091106000514.E4A9F3607E5@bosco.isi.edu>
In-Reply-To: <20091106000514.E4A9F3607E5@bosco.isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [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 17:53:09 -0000

This is the first RFC produced by the IPsecME working group. Congratulations and a big thank you to Vijay and Kilian!

	Yaron

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of rfc-editor@rfc-editor.org
> Sent: Friday, November 06, 2009 2:05
> To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
> Cc: ipsec@ietf.org; rfc-editor@rfc-editor.org
> Subject: RFC 5685 on Redirect Mechanism for the Internet Key Exchange
> Protocol Version 2 (IKEv2)
> 
> 
> 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
> 
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
> 
> Scanned by Check Point Total Security Gateway.