[bmwg] Comments on draft-ietf-bmwg-ca-bench-meth-01
Al Morton <acmorton@att.com> Mon, 09 April 2012 19:07 UTC
Return-Path: <acmorton@att.com>
X-Original-To: bmwg@ietfa.amsl.com
Delivered-To: bmwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AE0321F87B5 for <bmwg@ietfa.amsl.com>; Mon, 9 Apr 2012 12:07:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.243
X-Spam-Level:
X-Spam-Status: No, score=-104.243 tagged_above=-999 required=5 tests=[AWL=1.553, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 82kG07hFdZIw for <bmwg@ietfa.amsl.com>; Mon, 9 Apr 2012 12:07:41 -0700 (PDT)
Received: from nbfkord-smmo03.seg.att.com (nbfkord-smmo03.seg.att.com [209.65.160.84]) by ietfa.amsl.com (Postfix) with ESMTP id 34B9A21F8782 for <bmwg@ietf.org>; Mon, 9 Apr 2012 12:07:41 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo03.seg.att.com(mxl_mta-6.11.0-8) over TLS secured channel with ESMTP id c73338f4.0.370424.00-443.1015380.nbfkord-smmo03.seg.att.com (envelope-from <acmorton@att.com>); Mon, 09 Apr 2012 19:07:41 +0000 (UTC)
X-MXL-Hash: 4f83337d5506f632-1bfcf230ac09cf592f8df9d09ddc2e544ade7d2c
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q39J7dWM023556 for <bmwg@ietf.org>; Mon, 9 Apr 2012 15:07:40 -0400
Received: from sflint01.pst.cso.att.com (sflint01.pst.cso.att.com [144.154.234.228]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q39J7Y1I023475 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <bmwg@ietf.org>; Mon, 9 Apr 2012 15:07:35 -0400
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by sflint01.pst.cso.att.com (RSA Interceptor) for <bmwg@ietf.org>; Mon, 9 Apr 2012 15:07:25 -0400
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q39J7OlG031591 for <bmwg@ietf.org>; Mon, 9 Apr 2012 15:07:25 -0400
Received: from mailgw1.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q39J7Gek031223 for <bmwg@ietf.org>; Mon, 9 Apr 2012 15:07:17 -0400
Message-Id: <201204091907.q39J7Gek031223@alpd052.aldc.att.com>
Received: from acmt.att.com (martym.mt.att.com[135.16.251.71](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20120409190419gw1004or4ke>; Mon, 9 Apr 2012 19:04:19 +0000
X-Originating-IP: [135.16.251.71]
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 09 Apr 2012 15:08:26 -0400
To: bmwg@ietf.org
From: Al Morton <acmorton@att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-RSA-Action: allow
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <acmorton@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=1.0 c=1 a=dit6Jc5sqrAA:10 a=okYqswJ-1YkA:10 a=ofMgfj31e3]
X-AnalysisOut: [cA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=ZRNLZ4dFUbCvG8]
X-AnalysisOut: [UMqPvVAA==:17 a=48vgC7mUAAAA:8 a=nDD7OEIXCd9TiC5ZxJIA:9 a=]
X-AnalysisOut: [7RZhSPuPspECN0-hYXIA:7 a=CjuIK1q_8ugA:10 a=GbL8SpxeVU4gwMA]
X-AnalysisOut: [y:21 a=ii2CeGh184rUI45H:21]
Cc: draft-ietf-bmwg-ca-bench-meth@tools.ietf.org
Subject: [bmwg] Comments on draft-ietf-bmwg-ca-bench-meth-01
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bmwg>
List-Post: <mailto:bmwg@ietf.org>
List-Help: <mailto:bmwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Apr 2012 19:07:42 -0000
Mike and Sarah, Comments below, some are purely editorial. Al (as a participant) -=-=-=-=-=-=- Section 1 Intro ... The end goal of this methodology is to generate performance metrics in a lab environment that will more closely relate to actual observed s/more closely/closely/ performance on production networks. By utilizing dynamic traffic patterns relevant to modern networks, this methodology should be able to more closely tie laboratory and production metrics. s/more closely/closely/ and a question about: ... It should be further noted than any metrics acquired from production networks SHOULD be captured according to the policies and procedures of the IPPM or PMOL working groups. What metrics are you thinking about here? -=-=-=-=-=-=- Section 3.2 ...Application Flows, as defined in RFC 2722 [9] are able to be well-defined without simply referring to a network capture. An example traffic template is defined and listed in Appendix A of this document. Actually, RFC 2722 defines a Traffic Flow, not application: 3 Traffic Flows and Reporting Granularity A flow was defined in section 2.1 above in abstract terms as follows: "A TRAFFIC FLOW is an artifical logical equivalent to a call or connection, belonging to a (user-specieied) METERED TRAFFIC GROUP." -=-=-=-=-=-=-=- Section 3.4 ... If we change the example slightly and increase the size of each datagram to 1312 bytes, then it becomes necessary to recompute the math. s/math/load/ -=-=-=-=-=-=-=- 3.7.3. TCP Stack Considerations The IETF has historically provided guidance and information on TCP stack considerations. This methodology is strictly focused on performance metrics at layers above 4, thus does not specifically define any TCP stack configuration parameters of either the tester or the DUTs. The TCP configuration of the tester MUST remain constant across all DUTs in order to ensure comparable results. While the following list of references is not exhaustive, each document contains a relevant discussion on TCP stack considerations. Congestion control algorithms are discussed in Section 2 of RFC 3148 [11] with even more detailed references. TCP receive and congestion window sizes are discussed in detail in RFC 6349 [12]. It would be useful to cite the TCP Raodmap in the first paragraph above: http://tools.ietf.org/html/rfc4614 -=-=-=-=-=-=-=-=-=- 4.1.3 Procedure It's worth noting that when the offered load results in 100% link utilization on all ingress links, then the DUT has achieved "wire-speed performance", or words to that effect. ... This procedure MAY be repeated any number of times with the results being averaged together. s/number/reasonable number/ -=-=-=-=-=-=-=-=-=- 4.1.4.3. Packet Loss The test tool SHOULD report the number of flow packets lost or dropped from source to destination. s/flow packets/packets/ (i think) -=-=-=-=-=-=-=-=-=- 4.2.4.5. Packet Loss The test tool SHOULD report the number of flow packets lost or dropped from source to destination. Remove - redundant with 4.2.4.2 -=-=-=-=-=-=-=-=-=- 4.2.4.6. Application Flow Latency The test tool SHOULD report the minimum, maximum and average amount of time an application flow member takes to traverse the DUT, as defined by RFC 1242 [3], Section 3.13. What is a "flow member"? Are these statistics calculated over all packets in a flow? ... This rate SHOULD be reported individually for each application protocol present within the traffic mix. Not a rate, latency is in units of seconds. -=-=-=-=-=-=-=-=-=- Appendix B Good!