Re: [bmwg] New WG Deliverable Proposal - Core Router Software Accelerated Life Testing

Kevin Dubray <kdubray@juniper.net> Wed, 07 May 2003 12:35 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28010 for <bmwg-archive@lists.ietf.org>; Wed, 7 May 2003 08:35:27 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h47CiE812094; Wed, 7 May 2003 08:44:14 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h47ChG812052 for <bmwg@optimus.ietf.org>; Wed, 7 May 2003 08:43:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27907 for <bmwg@ietf.org>; Wed, 7 May 2003 08:33:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DO9I-0000kU-00 for bmwg@ietf.org; Wed, 07 May 2003 08:35:52 -0400
Received: from natint.juniper.net ([207.17.136.129] helo=merlot.juniper.net) by ietf-mx with esmtp (Exim 4.12) id 19DO9H-0000kB-00 for bmwg@ietf.org; Wed, 07 May 2003 08:35:51 -0400
Received: from juniper.net (ssh.juniper.net [207.17.136.39]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id h47CaCu93338; Wed, 7 May 2003 05:36:12 -0700 (PDT) (envelope-from kdubray@juniper.net)
Message-ID: <3EB8FDBC.2040104@juniper.net>
Date: Wed, 07 May 2003 08:36:12 -0400
From: Kevin Dubray <kdubray@juniper.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 (CK-SillyDog)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: bmwg@ietf.org
CC: "SENGUPTA,ANANDA (A-NewEngland,ex1)" <ananda_sengupta@agilent.com>
Subject: Re: [bmwg] New WG Deliverable Proposal - Core Router Software Accelerated Life Testing
References: <0D9185CE635BD511ACA50090277A6FCF053E3337@axcs18.cos.agilent.com>
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

In section 3.4, the I-D proposes "evaluation benchmarks". (Since the
proponents produced an I-D, I'm going to assume the I-D's a more complete
statement of intent and scope. My question is, do these tests and
their collection scenario present good BMWG benchmarks?

Consider the ol' manual, cable pull test or its higher-end relative, the
module hotswap test. Experience tells us that these two tests are some
of the finest system-level tests known to routerkind.  You can even measure
some aspect of "recovery time".  But do they lend themselves to good 
"benchmarks"?

-Kevin



SENGUPTA,ANANDA (A-NewEngland,ex1) wrote:
> Well, this is the reason I was readily agreeing to the work on the nomenclature draft, and then debating what tests fit in this WG in the actual test plan draft. It is clear that there is value to this work, and though all the test cases may not fit in this WG, some will.
> Ananda

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