Re: [bmwg] Summary of changes to mcast .12 rev
Scott Poretsky <sporetsky@avici.com> Tue, 01 July 2003 18:49 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10590 for <bmwg-archive@lists.ietf.org>; Tue, 1 Jul 2003 14:49:02 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XQAc-0001Hx-0x; Tue, 01 Jul 2003 14:48:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XQ9S-0001GT-T1 for bmwg@optimus.ietf.org; Tue, 01 Jul 2003 14:47:41 -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 OAA09399 for <bmwg@ietf.org>; Tue, 1 Jul 2003 14:00:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XPQJ-0006gK-00 for bmwg@ietf.org; Tue, 01 Jul 2003 14:00:11 -0400
Received: from [12.38.212.174] (helo=maildev.avici.com) by ietf-mx with esmtp (Exim 4.12) id 19XPQI-0006gE-00 for bmwg@ietf.org; Tue, 01 Jul 2003 14:00:10 -0400
Received: from sporetsky-lt.avici.com ([10.2.104.236]) by maildev.avici.com (8.11.0/8.11.0) with ESMTP id h61HxQ323237; Tue, 1 Jul 2003 13:59:26 -0400 (EDT)
Message-Id: <5.0.2.1.2.20030701140032.02312b98@pop.avici.com>
X-Sender: sporetsky@pop.avici.com
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Tue, 01 Jul 2003 14:01:02 -0400
To: Debby Stopp <dstopp@ixiacom.com>, "Bmwg (E-mail)" <bmwg@ietf.org>
From: Scott Poretsky <sporetsky@avici.com>
Subject: Re: [bmwg] Summary of changes to mcast .12 rev
Cc: "Hickman, Brooks" <brooks.hickman@spirentcom.com>, 'Kevin Dubray' <kdubray@juniper.net>, Al Morton <acmorton@att.com>
In-Reply-To: <15FDCE057B48784C80836803AE3598D501C5FA59@racerx.ixiacom.co m>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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>
Looks good to me. Changes match as was discussed. Scott At 08:58 AM 6/30/2003 -0700, Debby Stopp wrote: >Here's a summary of the changes from .12 rev to .13 rev: > >1) o The DUT/SUT MUST learn the appropriate unicast addresses; and" > to: > o The DUT/SUT MUST learn the appropriate unicast and multicast >addresses; and" > > >2) "The following results MUST be reflected in the test report: > > o The Max/Min value > o The set of all latencies with respective time units >related to the >tested ingress and each tested egress DUT/SUT interface." > > to: > > "The following results MUST be reflected in the test report: > o The Max/Min value > > The following results SHOULD be reflected in the test report: > o The set of all latencies with respective time units >related to the >tested ingress and each tested egress DUT/SUT interface." > > >3) "Mixed class throughput measurement is defined in RFC2432 [Du98]. A >search algorithm MUST be utilized to determine the Mixed >Class Throughput." > > to: > > "Mixed class throughput measurement is defined in RFC2432 [Du98]. A >search algorithm MUST be utilized to determine the Mixed >Class Throughput. > The ratio of unicast to multicast frames MUST remain the same when >varying the intended load." > > >4)from section 4.1: >"The unicast class frames MUST be configured to transmit in a round-robin >fashion to all of the destination ports." > > to: > >"The unicast class frames MUST be configured to transmit in an unweighted >round-robin fashion to all of the destination ports." > > > >5) Modified text for Join Delay text to include ref of state 0/1: >Method A: > >Method A assumes that the Multicast Forwarding Database <MFDB> of the >DUT/SUT does not contain or has not learned the specified >multicast group >address; specifically, the MFDB MUST be in State 0. In this >scenario, the >metric represents the time the DUT/SUT takes to add the >multicast address to >the MFDB and begin forwarding the multicast packet. Only one >ingress and >one egress MUST be used to determine this metric. > >Prior to sending any IGMP Group Membership Reports used to >calculate the >Multicast Group Join Delay, it MUST be verified through externally >observable means that the destination test port is not >currently a member of >the specified multicast group. In addition, it MUST be >verified through >externally observable means that the MFDB of the DUT/SUT does >not contain >the specified multicast address. > > >Method B: > >Method B assumes that the MFDB of the DUT/SUT does contain >the specified >multicast group address; specifically, the MFDB MUST be in >State 1. In this >scenario, the metric represents the time the DUT/SUT takes to >update the >MFDB with the additional nodes and their corresponding >interfaces and to >begin forwarding the multicast packet. One or more egress >ports MAY be used >to determine this metric. > >Prior to sending any IGMP Group Membership Reports used to >calculate the >Group Join Delay, it MUST be verified through externally >observable means >that the MFDB contains the specified multicast group address. > A single >un-instrumented test port MUST be used to join the specified >multicast group >address prior to sending any test traffic. This port will be >used only for >insuring that the MFDB has been populated with the specified >multicast group >address and can successfully forward traffic to the >un-instrumented port. > >6) In section 6.1, change this text <add method to MUST >config params>: > >"Similar to Section 6.1, the following configuration >parameters MUST be >reflected in the test report: > >o Frame size(s) >o Number of tested egress interfaces on the DUT/SUT >o IGMP version >o Offered load to ingress interface >o Total number of multicast groups >o Offered load to burdening ports >o Total number of burdening ports" > > to: > >"Similar to Section 6.1, the following configuration >parameters MUST be >reflected in the test report: > >o Frame size(s) >o Number of tested egress interfaces on the DUT/SUT >o IGMP version >o Offered load to ingress interface >o Total number of multicast groups >o Offered load to burdening ports >o Total number of burdening ports >o Method used to measure the join delay metric" > > >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 >http://www.ixiacom.com > > >_______________________________________________ >bmwg mailing list >bmwg@ietf.org >https://www1.ietf.org/mailman/listinfo/bmwg _______________________________________________ bmwg mailing list bmwg@ietf.org https://www1.ietf.org/mailman/listinfo/bmwg
- [bmwg] Summary of changes to mcast .12 rev Debby Stopp
- Re: [bmwg] Summary of changes to mcast .12 rev Scott Poretsky