Re: [IPsec] synchronizing crypto state

"Dan Harkins" <dharkins@lounge.org> Mon, 22 March 2010 18:20 UTC

Return-Path: <dharkins@lounge.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 714A73A69CF for <ipsec@core3.amsl.com>; Mon, 22 Mar 2010 11:20:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.329
X-Spam-Level:
X-Spam-Status: No, score=-4.329 tagged_above=-999 required=5 tests=[AWL=-1.794, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
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 roUImVrTI5zf for <ipsec@core3.amsl.com>; Mon, 22 Mar 2010 11:20:03 -0700 (PDT)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174]) by core3.amsl.com (Postfix) with ESMTP id 32F213A67D3 for <ipsec@ietf.org>; Mon, 22 Mar 2010 11:20:03 -0700 (PDT)
Received: from www.trepanning.net (localhost [127.0.0.1]) by colo.trepanning.net (Postfix) with ESMTP id B80CC1022404A; Mon, 22 Mar 2010 11:20:20 -0700 (PDT)
Received: from 130.129.26.143 (SquirrelMail authenticated user dharkins@lounge.org) by www.trepanning.net with HTTP; Mon, 22 Mar 2010 11:20:20 -0700 (PDT)
Message-ID: <884e7195495b157f15c923c3ba660a99.squirrel@www.trepanning.net>
In-Reply-To: <B0463EF9-0942-4BA9-9228-D7A033054996@cisco.com>
References: <B0463EF9-0942-4BA9-9228-D7A033054996@cisco.com>
Date: Mon, 22 Mar 2010 11:20:20 -0700 (PDT)
From: "Dan Harkins" <dharkins@lounge.org>
To: "David McGrew" <mcgrew@cisco.com>
User-Agent: SquirrelMail/1.4.14 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: IPsecme WG <ipsec@ietf.org>, ynir@checkpoint.com
Subject: Re: [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 18:20:06 -0000

  Hi,

  Another solution is to use a cipher mode (like SIV) that does not lose
all security if a counter is reused. Then you don't have to worry at all
it.

  Dan.

On Mon, March 22, 2010 9:29 am, David McGrew wrote:
> 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
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec
>