[IPsec] synchronizing crypto state

David McGrew <mcgrew@cisco.com> Mon, 22 March 2010 16:31 UTC

Return-Path: <mcgrew@cisco.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 3244A3A693C for <ipsec@core3.amsl.com>; Mon, 22 Mar 2010 09:31:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.034
X-Spam-Level:
X-Spam-Status: No, score=-10.034 tagged_above=-999 required=5 tests=[AWL=-0.565, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, RCVD_IN_DNSWL_HI=-8]
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 XG9qG+sPDgFc for <ipsec@core3.amsl.com>; Mon, 22 Mar 2010 09:31:28 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 13F8F28C123 for <ipsec@ietf.org>; Mon, 22 Mar 2010 09:31:26 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAF84p0tAZnwN/2dsb2JhbACbJHOjfZgZhH0Egx4
X-IronPort-AV: E=Sophos;i="4.51,288,1267401600"; d="scan'208";a="95047266"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 22 Mar 2010 16:31:44 +0000
Received: from dhcp-wireless-open-abg-26-197.meeting.ietf.org (che-vpn-cluster-1-128.cisco.com [10.86.240.128]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o2MGVhdF012063; Mon, 22 Mar 2010 16:31:44 GMT
Message-Id: <B0463EF9-0942-4BA9-9228-D7A033054996@cisco.com>
From: David McGrew <mcgrew@cisco.com>
To: ynir@checkpoint.com
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 22 Mar 2010 09:29:05 -0700
X-Mailer: Apple Mail (2.936)
Cc: IPsecme WG <ipsec@ietf.org>
Subject: [IPsec] synchronizing crypto state
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: Mon, 22 Mar 2010 16:31:29 -0000

Hi Yoav,

another requirement for IPsec HA is to coordinate the use of distinct  
counters between multiple crypto engines.  The problem  (and a  
convenient solution) is described in http://tools.ietf.org/html/draft-ietf-msec-ipsec-group-counter-modes-05

David