RE: FW: [bmwg] WG Last Call: draft-ietf-bmwg-mcastm-10.txt

"David Newman" <dnewman@networktest.com> Fri, 31 January 2003 20:53 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 PAA18567 for <bmwg-archive@lists.ietf.org>; Fri, 31 Jan 2003 15:53:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0VKuiJ18888; Fri, 31 Jan 2003 15:56:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0VKtqJ18850 for <bmwg@optimus.ietf.org>; Fri, 31 Jan 2003 15:55:52 -0500
Received: from bobet.int.networktest.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18505 for <bmwg@ietf.org>; Fri, 31 Jan 2003 15:51:41 -0500 (EST)
Received: from DIDIER (dhcp66.int.networktest.com [128.0.0.66]) by bobet.int.networktest.com (8.12.5/8.12.5) with SMTP id h0VKvBQD027593; Fri, 31 Jan 2003 12:57:12 -0800
From: David Newman <dnewman@networktest.com>
To: Debby Stopp <debby@ixiacom.com>, bmwg@ietf.org
Subject: RE: FW: [bmwg] WG Last Call: draft-ietf-bmwg-mcastm-10.txt
Date: Fri, 31 Jan 2003 12:55:15 -0800
Message-ID: <BAEALKMNKLEELDKGBICPIEMFCNAA.dnewman@networktest.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 IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <00f501c2c8c2$478033b0$6700a8c0@borg0home>
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

Debby, I hope you're feeling better.

I've reread the old thread. Neither it nor your message below address the
issue raised -- namely, exactly what kind of traffic, in what proportions,
is offered to and received by which ports.

IMO it is not enough to say "if you combine this section and that section"
the test setup is "implied."

The best way to ensure repeatability is with explicit, not implicit,
declarations of all relevant test parameters.

I hadn't pointed this out earlier, but this comment holds true for the
reporting format sections as well as those on test setup.

dn

-----Original Message-----
From: bmwg-admin@ietf.org [mailto:bmwg-admin@ietf.org]On Behalf Of Debby
Stopp
Sent: Thursday, January 30, 2003 4:47 PM
To: bmwg@ietf.org
Subject: Re: FW: [bmwg] WG Last Call: draft-ietf-bmwg-mcastm-10.txt


I'm home sick today, so I can't respond to all comments but I did notice
something from a previous thread:

----- Original Message -----
From: "Hickman, Brooks" <brooks.hickman@spirentcom.com>

> "Throughput measurement is defined in RFC1242 [Br91]. A search algorithm
> MUST be utilized to determine the maximum offered frame rate with a zero
> frame loss rate."
>
> RFC1242 does not specifically address multiple classes of traffic. I would
> suggest elaborating on this a little. For example, are both the multicast
> traffic AND unicast traffic varied to find the throughput or only the
> multicast traffic? While it may be inferred by defining the ratio,
> specifying how the two classes of traffic are varied may make it a little
> less confusing.

This was discussed at length back in Oct 2001 - please see thread
http://www.ietf.org/mail-archive/working-groups/bmwg/current/thrd10.html for
details.  I believe that if you combine:
     The offered load per each DUT/SUT port MUST not exceed the maximum
     bandwidth capacity of any configured receive DUT/SUT ports.

with

     Throughput measurement is defined in RFC1242 [Br91]. A search
     algorithm MUST be utilized to determine the maximum offered frame
     rate with a zero frame loss rate.

it is implied that you must vary the offered load, & again, that would
depend on whether you were chosing:

          a) As an independent rate for unicast class and multicast
             class of traffic OR
          b) As an aggregate rate comprised of a ratio of multicast
             class to unicast class of traffic.

as to how that offered load was varied.



Debby Stopp
Principal Software Engineer
(818) 444-2365
IXIA
26601 W. Agoura Rd.
Calabasas
CA 91302
Tel: 818 871 1800 (US) +1 818 871 1800 (international)
debby@ixiacom.com


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