Re: [tcpm] TCP-AO: Text for New_Key Process

Eric Rescorla <ekr@networkresonance.com> Tue, 03 February 2009 03:56 UTC

Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0A75A3A6B46; Mon, 2 Feb 2009 19:56:08 -0800 (PST)
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 5C5073A6B46 for <tcpm@core3.amsl.com>; Mon, 2 Feb 2009 19:56:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.564
X-Spam-Level:
X-Spam-Status: No, score=-2.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599]
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 M6l7HKzt5wDz for <tcpm@core3.amsl.com>; Mon, 2 Feb 2009 19:56:06 -0800 (PST)
Received: from romeo.rtfm.com (romeo.rtfm.com [74.95.2.173]) by core3.amsl.com (Postfix) with ESMTP id A62533A699A for <tcpm@ietf.org>; Mon, 2 Feb 2009 19:56:06 -0800 (PST)
Received: from romeo.rtfm.com (localhost.rtfm.com [127.0.0.1]) by romeo.rtfm.com (Postfix) with ESMTP id 0584550823; Mon, 2 Feb 2009 20:12:29 -0800 (PST)
Date: Mon, 02 Feb 2009 20:12:29 -0800
From: Eric Rescorla <ekr@networkresonance.com>
To: Ron Bonica <rbonica@juniper.net>
In-Reply-To: <49876D92.6030701@juniper.net>
References: <7.1.0.9.2.20081219010400.02bfd3d8@gmail.com> <496d9941.18038e0a.5558.ffffd3a6@mx.google.com> <497F7DDC.70309@isi.edu> <5E6CB562-0495-4D2B-924E-AB4650924151@nokia.com> <49876D92.6030701@juniper.net>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Message-Id: <20090203041229.0584550823@romeo.rtfm.com>
Cc: "tcpm@ietf.org" <tcpm@ietf.org>, Allison Mankin <mankin@psg.com>, Joe Touch <touch@ISI.EDU>, "skonduru@juniper.net" <skonduru@juniper.net>
Subject: Re: [tcpm] TCP-AO: Text for New_Key Process
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: <https://www.ietf.org/mailman/private/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

As previously noted, you can do automatic switchover without 
changing the TCP state machine at all: you just opportunistically
encrypt the occasional packet that would be sent already.

-Ekr

At Mon, 2 Feb 2009 17:02:58 -0500,
Ron Bonica wrote:
> 
> +1
> 
> Lars Eggert wrote:
> > On 2009-1-27, at 23:34, Joe Touch wrote:
> >> I was under the assumption that our design space was as close to TCP
> >> MD5 as
> >> possible, i.e., augment existing segments with a new option, but neither
> >> generate nor consume new segments.
> > 
> > That's my recollection as well, and hopefully it's in the minutes of the
> > WG meeting where we adopted the work item. The idea was to be as
> > lightweight (in terms of changes to TCP) as possible, and changes to the
> > state machine, etc. seem rather heavyweight.
> > 
> > Lars
> > 
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm