[bmwg] Summary of changes to mcast .12 rev
Debby Stopp <dstopp@ixiacom.com> Mon, 30 June 2003 16:20 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 MAA03956 for <bmwg-archive@lists.ietf.org>; Mon, 30 Jun 2003 12:20:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X1Nr-0001Bq-Lg; Mon, 30 Jun 2003 12:20:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X1Mw-00017Q-GZ for bmwg@optimus.ietf.org; Mon, 30 Jun 2003 12:19:36 -0400
Received: from racerx.ixiacom.com (64-60-75-69.cust.telepacific.net [64.60.75.69]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03819 for <bmwg@ietf.org>; Mon, 30 Jun 2003 12:18:47 -0400 (EDT)
Received: by racerx.ixiacom.com with Internet Mail Service (5.5.2653.19) id <N5C03Q37>; Mon, 30 Jun 2003 08:58:50 -0700
Message-ID: <15FDCE057B48784C80836803AE3598D501C5FA59@racerx.ixiacom.com>
From: Debby Stopp <dstopp@ixiacom.com>
To: "Bmwg (E-mail)" <bmwg@ietf.org>
Cc: "Hickman, Brooks" <brooks.hickman@spirentcom.com>, 'Kevin Dubray' <kdubray@juniper.net>, Al Morton <acmorton@att.com>
Date: Mon, 30 Jun 2003 08:58:50 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Subject: [bmwg] Summary of changes to mcast .12 rev
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>
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] Summary of changes to mcast .12 rev Debby Stopp
- Re: [bmwg] Summary of changes to mcast .12 rev Scott Poretsky