Re: [bmwg] Comments on draft-ietf-bmwg-protection-meth-04.txt
Jerry Perser <jerry@perser.org> Sat, 28 February 2009 18:57 UTC
Return-Path: <jerry@perser.org>
X-Original-To: bmwg@core3.amsl.com
Delivered-To: bmwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7F1E63A68E8 for <bmwg@core3.amsl.com>; Sat, 28 Feb 2009 10:57:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 w8UVJaXf8O0Q for <bmwg@core3.amsl.com>; Sat, 28 Feb 2009 10:57:52 -0800 (PST)
Received: from mail384c25.carrierzone.com (mail384c25.carrierzone.com [209.235.146.154]) by core3.amsl.com (Postfix) with ESMTP id 850A63A6876 for <bmwg@ietf.org>; Sat, 28 Feb 2009 10:57:52 -0800 (PST)
X-Authenticated-User: jerry.perser.org
Received: from [10.88.2.80] (netblock-66-159-213-29.dslextreme.com [66.159.213.29]) (authenticated bits=0) by mail384c25.carrierzone.com (8.13.6/8.13.1) with ESMTP id n1SIwDeS031027 for <bmwg@ietf.org>; Sat, 28 Feb 2009 18:58:14 GMT
Message-ID: <49A98944.5000204@perser.org>
Date: Sat, 28 Feb 2009 10:58:12 -0800
From: Jerry Perser <jerry@perser.org>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: "bmwg@ietf.org" <bmwg@ietf.org>
References: <7.1.0.9.0.20090216121609.02224d60@att.com> <200902171614.n1HGEFd6026974@klph001.kcdc.att.com> <E1DB169CF43C174181F7147204E23D74017A4A34@neon.ALLOT.LOCAL><200902251927.n1PJR9ds031924@klph001.kcdc.att.com><1018233473-1235594212-cardhu_decombobulator_blackberry.rim.net-1603237059-@bxe1124.bisx.prod.on.blackberry> <49A5AD02.3020309@networktest.com> <E1DB169CF43C174181F7147204E23D74017A4ACF@neon.ALLOT.LOCAL>
In-Reply-To: <E1DB169CF43C174181F7147204E23D74017A4ACF@neon.ALLOT.LOCAL>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [bmwg] Comments on draft-ietf-bmwg-protection-meth-04.txt
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/bmwg>
List-Post: <mailto:bmwg@ietf.org>
List-Help: <mailto:bmwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Feb 2009 18:57:53 -0000
Scott, My view is both. One, the BWMG focus is on a SUT/DUT. If you can draw a box around what you are testing and some of the network is outside the box, then it falls under the BMWG. If you can't draw a box around what you are testing or none of the network is outside the box, then is falls under the IPPM. My notion of what a DUT is was destroyed by a company called Avici Systems. Those guys can take 14 routers, each in their own rack, and connect them to look like a single DUT. From the networks point of view, the routers look like a single DUT. If your draft can not support SUT, you should be clear about it. I assumed that the draft supported both SUT and DUT. Please clarify if we need another draft for SUT. Two, does Al's comment about a Node Crash also apply to SUT, but not a DUT? Jerry Perser Scott Poretsky wrote: > David, > > Are you making a general statement or a point relevant to this thread? > > Scott > > -----Original Message----- > From: bmwg-bounces@ietf.org [mailto:bmwg-bounces@ietf.org] On Behalf Of > David Newman > Sent: Wednesday, February 25, 2009 3:42 PM > To: bmwg@ietf.org > Subject: Re: [bmwg] Comments on draft-ietf-bmwg-protection-meth-04.txt > > On 2/25/09 12:38 PM, Scott Poretsky wrote: > >> Yes, but in the BMWG we focus on a single DUT >> > > Not necessarily. Many bmwg documents use the term DUT/SUT, where SUT may > be comprised of multiple systems (just not on a production network). > > dn > > _______________________________________________ > bmwg mailing list > bmwg@ietf.org > https://www.ietf.org/mailman/listinfo/bmwg > _______________________________________________ > bmwg mailing list > bmwg@ietf.org > https://www.ietf.org/mailman/listinfo/bmwg > > > -- Jerry Perser
- [bmwg] Comments on draft-ietf-bmwg-protection-met… Al Morton
- Re: [bmwg] Comments on draft-ietf-bmwg-protection… Al Morton
- Re: [bmwg] Comments on draft-ietf-bmwg-protection… Scott Poretsky
- Re: [bmwg] Comments on draft-ietf-bmwg-protection… Scott Poretsky
- Re: [bmwg] Comments on draft-ietf-bmwg-protection… Al Morton
- Re: [bmwg] Comments on draft-ietf-bmwg-protection… Al Morton
- Re: [bmwg] Comments on draft-ietf-bmwg-protection… Scott Poretsky
- Re: [bmwg] Comments on draft-ietf-bmwg-protection… Scott Poretsky
- Re: [bmwg] Comments on draft-ietf-bmwg-protection… David Newman
- Re: [bmwg] Comments on draft-ietf-bmwg-protection… Scott Poretsky
- Re: [bmwg] Comments on draft-ietf-bmwg-protection… Al Morton
- Re: [bmwg] Comments on draft-ietf-bmwg-protection… Scott Poretsky
- Re: [bmwg] Comments on draft-ietf-bmwg-protection… Al Morton
- Re: [bmwg] Comments on draft-ietf-bmwg-protection… Jerry Perser
- Re: [bmwg] Comments on draft-ietf-bmwg-protection… Scott Poretsky