RFC 7791 on Cloning the IKE Security Association in the Internet Key Exchange Protocol Version 2 (IKEv2)

rfc-editor@rfc-editor.org Thu, 03 March 2016 19:44 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A9D31B4226 for <ietf-announce@ietfa.amsl.com>; Thu, 3 Mar 2016 11:44:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.908
X-Spam-Level:
X-Spam-Status: No, score=-106.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.006, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BSIfh41IEatI for <ietf-announce@ietfa.amsl.com>; Thu, 3 Mar 2016 11:44:18 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0449C1B4220 for <ietf-announce@ietf.org>; Thu, 3 Mar 2016 11:44:16 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 8F56F180452; Thu, 3 Mar 2016 11:43:16 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7791 on Cloning the IKE Security Association in the Internet Key Exchange Protocol Version 2 (IKEv2)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160303194316.8F56F180452@rfc-editor.org>
Date: Thu, 03 Mar 2016 11:43:16 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/549jUAa9l2VO5lyD5mlur1MqjTM>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Mar 2016 19:44:23 -0000

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

        
        RFC 7791

        Title:      Cloning the IKE Security Association 
                    in the Internet Key Exchange Protocol 
                    Version 2 (IKEv2) 
        Author:     D. Migault, Ed.,
                    V. Smyslov
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2016
        Mailbox:    daniel.migault@ericsson.com, 
                    svan@elvis.ru
        Pages:      14
        Characters: 32532
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-mglt-ipsecme-clone-ike-sa-09.txt

        URL:        https://www.rfc-editor.org/info/rfc7791

        DOI:        http://dx.doi.org/10.17487/RFC7791

This document considers a VPN end user establishing an IPsec Security
Association (SA) with a Security Gateway using the Internet Key
Exchange Protocol version 2 (IKEv2), where at least one of the peers
has multiple interfaces or where Security Gateway is a cluster with
each node having its own IP address.

The protocol described allows a peer to clone an IKEv2 SA, where an
additional SA is derived from an existing one.  The newly created IKE
SA is set without the IKEv2 authentication exchange.  This IKE SA can
later be assigned to another interface or moved to another cluster
node.

This is now a Proposed Standard.

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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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
Association Management Solutions, LLC