IETF Logo Mail Archive

RE: [bmwg] Is the BMWG a proper home for this I-D?

"Henk Uijterwaal (RIPE NCC)" <henk@ripe.net> Wed, 06 October 2004 09:00 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03933 for <bmwg-archive@lists.ietf.org>; Wed, 6 Oct 2004 05:00:46 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CF7a3-0000SO-65; Wed, 06 Oct 2004 04:55:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CF7Pb-00074J-3n for bmwg@megatron.ietf.org; Wed, 06 Oct 2004 04:44:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02518 for <bmwg@ietf.org>; Wed, 6 Oct 2004 04:44:36 -0400 (EDT)
Received: from postman.ripe.net ([193.0.0.199]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CF7Z2-00013Z-KO for bmwg@ietf.org; Wed, 06 Oct 2004 04:54:25 -0400
Received: by postman.ripe.net (Postfix, from userid 8) id 398DD4E57D; Wed, 6 Oct 2004 10:44:04 +0200 (CEST)
Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by postman.ripe.net (Postfix) with ESMTP id C87F54E146; Wed, 6 Oct 2004 10:44:03 +0200 (CEST)
Received: from x49.ripe.net (x49.ripe.net [193.0.1.49]) by birch.ripe.net (8.12.10/8.11.6) with ESMTP id i968i3rL004233; Wed, 6 Oct 2004 10:44:03 +0200
Received: from localhost (henk@localhost) by x49.ripe.net (8.12.10/8.12.6) with ESMTP id i968i3Ns018438; Wed, 6 Oct 2004 10:44:03 +0200
X-Authentication-Warning: x49.ripe.net: henk owned process doing -bs
Date: Wed, 06 Oct 2004 10:44:03 +0200
From: "Henk Uijterwaal (RIPE NCC)" <henk@ripe.net>
To: "Howard C. Berkowitz" <hcb@gettcomm.com>
Subject: RE: [bmwg] Is the BMWG a proper home for this I-D?
In-Reply-To: <p06110415bd88dcb3b421@[192.168.0.4]>
Message-ID: <Pine.LNX.4.58.0410061040440.16218@x49.ripe.net>
References: <20041005231733.62400C7D72@newdev.harvard.edu> <p06110415bd88dcb3b421@[192.168.0.4]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-RIPE-Spam-Status: N 0.000011 / 0.0 / 0.0 / disabled
X-RIPE-Signature: c8f1e6d7c6426ab9cf46f02e3a211b71
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: scott bradner <sob@harvard.edu>, bmwg@ietf.org
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
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>
Sender: bmwg-bounces@ietf.org
Errors-To: bmwg-bounces@ietf.org

Hi all,

I missed the start of this thread and cannot find it in the archives, but:
which draft are we talking about?




On Tue, 5 Oct 2004, Howard C. Berkowitz wrote:
> At 7:17 PM -0400 10/5/04, scott bradner wrote:

> >bmwg was for boxes, ippm was for networks

Exactly.


> Which brings up the question: where does a box belong when its
> performance can be tested only by interaction with other like boxes
> (i.e., iBGP)?

Still BMWG, one is looking at properties of the box, not of the network.




Henk (IPPM co-chair).

------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.net
RIPE Network Coordination Centre          http://www.amsterdamned.org/~henk
P.O.Box 10096          Singel 258         Phone: +31.20.5354414
1001 EB Amsterdam      1016 AB Amsterdam  Fax: +31.20.5354445
The Netherlands        The Netherlands    Mobile: +31.6.55861746
------------------------------------------------------------------------------

In a room with a window in the corner, I found truth.            (Ian Curtis)

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

v2.23.0 | Report a Bug | By Email