Re: [aqm] WGLC on draft-ietf-aqm-eval-guidelines

Roland Bless <roland.bless@kit.edu> Fri, 21 August 2015 20:19 UTC

Return-Path: <roland.bless@kit.edu>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99A701ACDC3 for <aqm@ietfa.amsl.com>; Fri, 21 Aug 2015 13:19:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.15
X-Spam-Level:
X-Spam-Status: No, score=-1.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JZP2R6g9Itzn for <aqm@ietfa.amsl.com>; Fri, 21 Aug 2015 13:18:59 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 949CA1ACDBF for <aqm@ietf.org>; Fri, 21 Aug 2015 13:18:58 -0700 (PDT)
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=i72vorta.tm.kit.edu) by iramx2.ira.uni-karlsruhe.de with esmtp port 25 iface 141.3.10.81 id 1ZSsm3-0002hK-2c; Fri, 21 Aug 2015 22:18:51 +0200
Received: from [IPv6:::1] (localhost [127.0.0.1]) by i72vorta.tm.kit.edu (Postfix) with ESMTPS id BCE2CB0036B; Fri, 21 Aug 2015 22:18:50 +0200 (CEST)
Message-ID: <55D787AA.6050809@kit.edu>
Date: Fri, 21 Aug 2015 22:18:50 +0200
From: Roland Bless <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology (KIT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: Wesley Eddy <wes@mti-systems.com>, "aqm@ietf.org" <aqm@ietf.org>, "\"Scheffenegger, Richard\" " <rs@netapp.com>
References: <55C8AA8E.4000802@mti-systems.com> <55D3AB99.3090405@kit.edu> <55D3EF7F.1040600@mti-systems.com>
In-Reply-To: <55D3EF7F.1040600@mti-systems.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1440188331.
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/PK4xaVguRdJp9E7SrdyqMi0wUZs>
Subject: Re: [aqm] WGLC on draft-ietf-aqm-eval-guidelines
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Aug 2015 20:19:01 -0000

Hi Wes,

On 19.08.2015 at 04:52 Wesley Eddy wrote:
> There were only a couple of the "major issues" that I thought I should
> comment on as a co-chair of the WG:
> 
> 
>> 3) the overall number of tests and parameter combinations is really
>>   high
> 
> Are there particular permutations (or classes of permutations) that you
> can suggest to remove?  There's a balancing act between including enough
> to satisfy people that want to find edge cases and thoroughly
> characterize an algorithm, and the desire for a more easily tractable
> suite of tests.

Right now, I can't, it was merely an observation...

>> 4) from the discussed end-to-end metrics only latency/goodput metrics
>>   are used in the scenarios and for some of the scenarios these metrics
>>   are not suitable to show the desired behavior
> 
> It would be easier for the editors to improve this if you could suggest
> specific metrics to add to specific scenarios, I think.

We included some considerations in the comments to the individual
sections already. As a general notice, The document could benefit
by cross-referencing the scenarios against the documents referenced in
Major Issue 6.  Regarding particular metrics, suggesting one
would require exact understanding of particular test goals, proper
argumentation, and thus more time than LC deadline allowed.

Regards,
 Roland