Re: [tcpm] TCP-AO Option Layout - Alignment and Padding

Ron Bonica <rbonica@juniper.net> Fri, 01 August 2008 15:13 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 A0D833A695F; Fri, 1 Aug 2008 08:13:03 -0700 (PDT)
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 BF4343A6949 for <tcpm@core3.amsl.com>; Fri, 1 Aug 2008 08:13:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.269
X-Spam-Level:
X-Spam-Status: No, score=-6.269 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 US+NSiWd-Ww4 for <tcpm@core3.amsl.com>; Fri, 1 Aug 2008 08:13:01 -0700 (PDT)
Received: from exprod7og114.obsmtp.com (exprod7ob114.obsmtp.com [64.18.2.214]) by core3.amsl.com (Postfix) with ESMTP id 0C1BC3A6827 for <tcpm@ietf.org>; Fri, 1 Aug 2008 08:12:59 -0700 (PDT)
Received: from source ([66.129.228.6]) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP; Fri, 01 Aug 2008 08:12:07 PDT
Received: from antipi.jnpr.net ([10.10.2.34]) by p-emsmtp03.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 1 Aug 2008 08:11:36 -0700
Received: from proton.jnpr.net ([10.10.2.37]) by antipi.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Fri, 1 Aug 2008 11:11:29 -0400
Received: from [172.23.1.182] ([172.23.1.182] RDNS failed) by proton.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Fri, 1 Aug 2008 11:08:15 -0400
Message-ID: <489326B2.4090204@juniper.net>
Date: Fri, 01 Aug 2008 11:07:30 -0400
From: Ron Bonica <rbonica@juniper.net>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@linux-ipv6.org>
References: <20080729.060448.112613043.yoshfuji@linux-ipv6.org> <488EF15F.4070302@isi.edu> <20080729.065149.22600370.yoshfuji@linux-ipv6.org>
In-Reply-To: <20080729.065149.22600370.yoshfuji@linux-ipv6.org>
X-Enigmail-Version: 0.95.6
X-OriginalArrivalTime: 01 Aug 2008 15:08:15.0831 (UTC) FILETIME=[6C7F6670:01C8F3E8]
Cc: tcpm@ietf.org, touch@ISI.EDU
Subject: Re: [tcpm] TCP-AO Option Layout - Alignment and Padding
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-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

YOSHIFUJI Hideaki / 吉藤英明 wrote:
> 
> We have 256 keys, and it is not enough.


Folks,

Most of the time, the TSAD contains exactly one key for each directions. 
  (That is, the key currently in use). During periods of transition, the 
TSAD can contain two keys in each direction. (That is, the old one and 
the new one). So, a one-bit key-id is really big enough. But, if there 
is any thought of reserving keyid==0, we had better reserve 2 bits. I 
don't think that there is a need for more.

An application may want to maintain a larger keychain (possibly 
containing hundreds of keys). If that is the case, a user-land 
application should maintain that large keychain. The application will 
also send keys to and from the TSAD as apropriate.

                                      Ron

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm