RE: Comments on bmwg-secperf-04

"Mike Winslow" <mike_winslow@csi.com> Tue, 04 August 1998 01:22 UTC

Received: from ironbridgenetworks.com (helios.ironbridgenetworks.com [146.115.140.2]) by dokka.maxware.no (8.8.5/8.8.5) with SMTP id DAA24766 for <bmwg-archive@alvestrand.no>; Tue, 4 Aug 1998 03:22:58 +0200
Received: from NIH2WAAE by ironbridgenetworks.com (SMI-8.6/SMI-SVR4) id VAA26769; Mon, 3 Aug 1998 21:00:31 -0400
Received: from mail pickup service by csi.com with Microsoft SMTPSVC; Mon, 3 Aug 1998 21:00:29 -0400
Sender: mike_winslow@csi.com
Received: from mike_winslow (client-125-233.bellatlantic.net [151.198.125.233]) by hil-img-ims-3.compuserve.com (8.8.6/8.8.6/IMS-1.4) with SMTP id UAA01895; Mon, 3 Aug 1998 20:59:54 -0400 (EDT)
From: Mike Winslow <mike_winslow@csi.com>
To: Kevin Dubray <kdubray@ironbridgenetworks.com>, bmwg@ironbridgenetworks.com
Cc: dnewman@cmp.com
Subject: RE: Comments on bmwg-secperf-04
Date: Mon, 03 Aug 1998 21:02:24 -0400
Message-ID: <000501bdbf43$8ac7b5e0$0301a8c0@mike_winslow.compuserve.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
In-Reply-To: <199808031928_MC2-54E7-2FDD@compuserve.com>

Hi,  if I may comment:

Frame Relay congestion metrics Burst size and burst time both have bearing
on a per frame basis.

These are used to form the committed information rate.



-----Original Message-----
From: kdubray@ironbridgenetworks.com
[mailto:kdubray@ironbridgenetworks.com]
Sent: Monday, August 03, 1998 7:28 PM
To: bmwg@ironbridgenetworks.com
Cc: dnewman@cmp.com
Subject: Comments on bmwg-secperf-04


Sender: kdubray@ironbridgenetworks.com
Received: from ironbridgenetworks.com (helios.ironbridgenetworks.com
[146.115.140.2])
	by dub-img-7.compuserve.com (8.8.6/8.8.6/2.12) with SMTP id TAA05672;
	Mon, 3 Aug 1998 19:27:40 -0400 (EDT)
Received: from ironbridgenetworks.com by ironbridgenetworks.com
(SMI-8.6/SMI-SVR4)
	id SAA20643; Mon, 3 Aug 1998 18:52:06 -0400
Message-ID: <35C63EE4.CD5A641@ironbridgenetworks.com>
Date: Mon, 03 Aug 1998 18:51:16 -0400
From: Kevin Dubray <kdubray@ironbridgenetworks.com>
Organization: IronBridge Networks
X-Mailer: Mozilla 4.05 [en] (WinNT; I)
MIME-Version: 1.0
To: bmwg@ironbridgenetworks.com
CC: dnewman@cmp.com
Subject: Comments on bmwg-secperf-04
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi David,

In section 3.4, Bit Forwarding Rate, you write:  "...this
measurement counts bits per second rather than frames per
second.  Per-frame metrics are not meaningful in the context
of a flow of application data between endpoints."

Two comments.  First, if you leave the above declaration (i.e.,
per frame metrics are not meaningful), you may wish to offer a
explanation as to your rationale. This would help the reader
build an understanding as to your conclusion.

Second, if per-frame performance is meaningless in the firewall
context, (I'm not sure I _totally_ agree), why are you carrying the
frame overhead in the metric versus some sort of Effective Bit
Forwarding Rate (bit fwd rate of data payload component only?)


Section 3.7.  Connection.  I would move this wonderfully defined
abstration ahead of the connection-related metrics (e.g. concurrent
connections.)  I had lots of questions about section 3.6, concurrent
connections, until I read your definition of connection... ;-)


Section 1. Introduction.  "The primary metrics used in this document
are bit forwarding rate and connections."  A nit.  As you defined
in section 3.6, a connection is a abstraction, not a metric. Perhaps,
"... a bit forwarding rate metric and connection-related metrics."

Otherwise, this draft has come along nicely since LA!

-Kevin