Re: [bmwg] Meeting Minutes Review: IPsec Terminology

Tim Van Herck <herckt@cisco.com> Wed, 29 October 2003 00:21 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10351 for <bmwg-archive@odin.ietf.org>; Tue, 28 Oct 2003 19:21:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEe5A-0005QQ-Md for bmwg-archive@odin.ietf.org; Tue, 28 Oct 2003 19:21:04 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9T0L4Ed020828 for bmwg-archive@odin.ietf.org; Tue, 28 Oct 2003 19:21:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEe58-0005P1-1Z; Tue, 28 Oct 2003 19:21:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEe4h-0005M2-Au for bmwg@optimus.ietf.org; Tue, 28 Oct 2003 19:20:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10281 for <bmwg@ietf.org>; Tue, 28 Oct 2003 19:20:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEe4f-0003gE-00 for bmwg@ietf.org; Tue, 28 Oct 2003 19:20:33 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1AEe4f-0003fA-00 for bmwg@ietf.org; Tue, 28 Oct 2003 19:20:33 -0500
Received: from cisco.com (171.71.177.238) by sj-iport-3.cisco.com with ESMTP; 28 Oct 2003 16:22:17 -0800
Received: from mira-sjc5-f.cisco.com (IDENT:mirapoint@mira-sjc5-f.cisco.com [171.71.163.13]) by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id h9T0K1QY016688; Tue, 28 Oct 2003 16:20:01 -0800 (PST)
Received: from cisco.com (dhcp-10-34-44-35.cisco.com [10.34.44.35]) by mira-sjc5-f.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id ALY96419; Tue, 28 Oct 2003 16:25:23 -0800 (PST)
Message-ID: <3F9F07B0.3040909@cisco.com>
Date: Tue, 28 Oct 2003 16:20:00 -0800
From: Tim Van Herck <herckt@cisco.com>
Organization: Cisco Systems, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Scott Bradner <sob@harvard.edu>
CC: bmwg@ietf.org
Subject: Re: [bmwg] Meeting Minutes Review: IPsec Terminology
References: <200310290007.h9T0796l005753@newdev.harvard.edu>
In-Reply-To: <200310290007.h9T0796l005753@newdev.harvard.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: bmwg-admin@ietf.org
Errors-To: bmwg-admin@ietf.org
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Post: <mailto:bmwg@ietf.org>
List-Help: <mailto:bmwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

	Scott,

>>What if we do something like this :
>>
>>A prerequisite will be that ingress and egress MTU have to be identical.
>>
>>Then we send a round robin stream of the following packets :
>>  - TCP (minimum allowed packetsize on PHY) bytes
>>  - UDP 128 bytes
>>  - TCP 256 bytes
>>  - UDP 512 bytes
>>  - keep on alternating UDP/TCP, increase by 256 bytes
>>  - ....
>>  - UDP (max MTU) bytes
> 
> 
> that is about what I used to do (modulo alternating protocols 
> within a packet size, I ran all the sizes then changed protocols but
> I do not see any reason to do it one way or another)
> 
> but I do not see how that gets one closer to a single magic number
> (which the BMWG designated a "millstone" after Dave Mills)

Would you agree that we try a middleground solution where we stay away 
from IMIX and redefine -a- general mix where we only suggest a potential 
mix format but require the mix to be reported in any of the documented 
results.

	Thanks,
	Tim-


_______________________________________________
bmwg mailing list
bmwg@ietf.org
https://www1.ietf.org/mailman/listinfo/bmwg