Re: [tcpm] question about TCP-AO and rekeying

Eric Rescorla <ekr@networkresonance.com> Wed, 17 June 2009 14:09 UTC

Return-Path: <ekr@networkresonance.com>
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA4153A6989 for <tcpm@core3.amsl.com>; Wed, 17 Jun 2009 07:09:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.018
X-Spam-Level:
X-Spam-Status: No, score=0.018 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, RDNS_DYNAMIC=0.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 AlHiNgMYOmhx for <tcpm@core3.amsl.com>; Wed, 17 Jun 2009 07:09:05 -0700 (PDT)
Received: from kilo.networkresonance.com (74-95-2-169-SFBA.hfc.comcastbusiness.net [74.95.2.169]) by core3.amsl.com (Postfix) with ESMTP id E6B973A6813 for <tcpm@ietf.org>; Wed, 17 Jun 2009 07:09:04 -0700 (PDT)
Received: from kilo.local (localhost [127.0.0.1]) by kilo.networkresonance.com (Postfix) with ESMTP id A3AB61BCC72; Wed, 17 Jun 2009 07:09:39 -0700 (PDT)
Date: Wed, 17 Jun 2009 07:09:39 -0700
From: Eric Rescorla <ekr@networkresonance.com>
To: Joe Touch <touch@ISI.EDU>
In-Reply-To: <4A388C37.3030703@isi.edu>
References: <4A2AB973.3030203@isi.edu> <20090616131807.75C481BC6EB@kilo.networkresonance.com> <4A37A202.9020500@isi.edu> <20090617054551.A4E0C1BCA23@kilo.networkresonance.com> <4A388C37.3030703@isi.edu>
User-Agent: Wanderlust/2.15.5 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20090617140939.A3AB61BCC72@kilo.networkresonance.com>
Cc: tcpm Extensions WG <tcpm@ietf.org>
Subject: Re: [tcpm] question about TCP-AO and rekeying
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jun 2009 14:09:05 -0000

At Tue, 16 Jun 2009 23:24:55 -0700,
Joe Touch wrote:
> Eric Rescorla wrote:
> ...
> >> However, the invariant is twofold:
> >>
> >> 	a) for a given packet, only one MKT applies
> >>
> >> 	b) for two endpoints with multiple MKTs,
> >> 	the *same* MKT applies.
> > 
> > I don't see that this is true. As I understand the current design
> > there's no reason that both sides can't use different MKTs
> > indefinitely.
> 
> Each side can use a different MKT to transmit. However, if side A uses
> MKT X to transmit, then side B needs to know to use MKT X to receive. If
> side A matches MKT X on transmit and side B matches MKT Y on receive,
> then there's a problem for that connection.
> 
> So let's rephrase, recognizing that there are two MKTs at any given time
> (one for transmit on each side, and the same pair for receive on the
> opposite side).
> 
> b) for two endpoints, if a given packet matches MKT on one side during
> transmit, it must match the corresponding MKT on the other side during
> receive.

Right, but this doesn't require ordering or non-overlapping, as far as
I can tell.  It merely requires that at any time there only be one MKT
corresponding to any given socketpair/key-id.
       
-Ekr