Proposed Modification to lanswitch-06
Kevin Dubray <kdubray@baynetworks.com> Tue, 19 August 1997 22:53 UTC
Received: from cnri by ietf.org id aa19650; 19 Aug 97 18:53 EDT
Received: from mailhost1.BayNetworks.COM (ext-ns2.baynetworks.com [134.177.3.16]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid SAA18752 for <ietfadm@cnri.reston.va.us>; Tue, 19 Aug 1997 18:56:39 -0400 (EDT)
Received: from ns2.BayNetworks.COM (screen2r.BayNetworks.COM [134.177.3.1]) by mailhost1.BayNetworks.COM (8.8.6/BNET-97/07/07-E) with ESMTP id PAA09976
Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.151.199]) by ns2.BayNetworks.COM (8.8.6/BNET-97/07/07-I) with ESMTP id PAA07335
Received: (majordom@localhost) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) id SAA03361; Tue, 19 Aug 1997 18:21:19 -0400 for bmwg-outgoing
Received: from ns2.BayNetworks.COM (ns2.baynetworks.com [134.177.1.109]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id SAA03354; Tue, 19 Aug 1997 18:21:18 -0400 for <bmwg@pobox.engeast>
Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.151.199]) by ns2.BayNetworks.COM (8.8.6/BNET-97/07/07-I) with ESMTP id PAA07047; Tue, 19 Aug 1997 15:21:16 -0700 (PDT) for <bmwg@baynetworks.com>
Posted-Date: Tue, 19 Aug 1997 15:21:16 -0700 (PDT)
Received: from pestilence.engeast (pestilence [192.32.180.194]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with SMTP id SAA03351; Tue, 19 Aug 1997 18:21:16 -0400 for <bmwg@baynetworks.com>
Date: Tue, 19 Aug 1997 18:21:16 -0400
From: Kevin Dubray <kdubray@baynetworks.com>
Message-Id: <199708192221.SAA03351@pobox.engeast.BayNetworks.COM>
To: bmwg@baynetworks.com
Subject: Proposed Modification to lanswitch-06
Sender: owner-bmwg@baynetworks.com
Precedence: bulk
Colleagues: Below are the modifications that Bob Mandeville is proposing to make to the latest LAN Switch Benchmarking Terminology draft, <draft-ietf-bmwg-lanswitch-06.txt>. Most, if not all, changes are based on comments from the Munich BMWG session. If there are no objections, Bob will incorporate the changes into the next version of the draft, which will become the basis of a WG Last Call. -Kevin ---------------------------------------------------------------------------- Modification 1 3.2.2 Bidirectional traffic 1. The wording of defintion is slighty changed to avoid the repetition of DUT/SUT. The original definition: "Frames presented to a DUT/SUT such that each of the interfaces of the DUT/SUT both receive and transmit." now reads: "Frames presented to a DUT/SUT such that every receiving interface also transmits." 2. Mention is now made of "forwarding rate" in addition to "throughput" as measurements requiring bidirectional traffic on full duplex devices. Modification 2 3.3.1 Non-meshed traffic 1. The term "non-meshed traffic" replaces the term "one-to-one mapped traffic" to give consistency to the three terms defined for traffic distribution: non-meshed, partially meshed and fully meshed. 2. The term "non-meshed" is substitued throughout the document. 3. The discussion section makes it clear that the intended meaning of the term is a one-to-one mapping of interfaces: "In the simplest instance of non-meshed traffic all frames are offered to a single input interface and addressed to a single output interface. The one-to-one mapping of input to output interfaces required by non-meshed traffic can be extended to multiple mutually exclusive pairs of input and output interfaces." Modification 3 3.3.2 Partially meshed traffic 1. The last paragraph regarding traffic orientation will be stricken from the text. 2. The section on testing backbone connections using partially meshed traffic was appropriately moved up from the discussion section on fully meshed traffic (3.3.3) to the discussion section on partially meshed traffic. Modification 4 3.3.3 Fully meshed traffic 1. The wording of the definition is modified to make it consistent with the wording for the other terms dealing with traffic distribution. The original definition: "Frames switched simultaneously between all of a designated number of interfaces of a DUT/SUT such that each of the interfaces under test will both forward frames to and receive frames from all of the other interfaces under test." now reads: "Frames offered to a designated number of interfaces of a DUT/SUT such that each one of the interfaces under test receives frames addressed to all of the other interfaces under test." Modification 5 3.5.2 Offered Load 1. The following statement is added: "Offered load MUST be indicated when reporting the results of forwarding rate meausurements." Modification 6 3.6.3 Maximum forwarding rate (MFR) 1. The label on column A of the table in the discussion section is corrected to read "Test Device Offered Load" in place of "Tets Device Offered Rate". Modification 7 5 References 1. Author names are added. Modification 8 6. Acknowledgements 1. The acknowledgements section is extended. <end of document> ----- End Included Message -----
- Proposed Modification to lanswitch-06 Kevin Dubray