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

"LAUTENSCHLAEGER, Wolfram (Wolfram)" <wolfram.lautenschlaeger@alcatel-lucent.com> Thu, 13 August 2015 11:58 UTC

Return-Path: <wolfram.lautenschlaeger@alcatel-lucent.com>
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 0BA581A1A27 for <aqm@ietfa.amsl.com>; Thu, 13 Aug 2015 04:58:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 fpbaQw8ps73j for <aqm@ietfa.amsl.com>; Thu, 13 Aug 2015 04:58:40 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpgre-esg-01.alcatel-lucent.com [135.245.210.22]) (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 9F16C1A1A28 for <aqm@ietf.org>; Thu, 13 Aug 2015 04:58:39 -0700 (PDT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (unknown [135.239.2.122]) by Websense Email Security Gateway with ESMTPS id BEE74D6476322 for <aqm@ietf.org>; Thu, 13 Aug 2015 11:58:33 +0000 (GMT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id t7DBwZuf032545 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <aqm@ietf.org>; Thu, 13 Aug 2015 13:58:35 +0200
Received: from FR712WXCHMBA13.zeu.alcatel-lucent.com ([169.254.5.200]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0195.001; Thu, 13 Aug 2015 13:58:35 +0200
From: "LAUTENSCHLAEGER, Wolfram (Wolfram)" <wolfram.lautenschlaeger@alcatel-lucent.com>
To: "aqm@ietf.org" <aqm@ietf.org>
Thread-Topic: [aqm] WGLC on draft-ietf-aqm-eval-guidelines
Thread-Index: AQHQ03Kg5cU2L4KeM025KFpwsGICuJ4JvNCA
Date: Thu, 13 Aug 2015 11:58:34 +0000
Message-ID: <0A452E1DADEF254C9A7AC1969B8781284A7D6F4D@FR712WXCHMBA13.zeu.alcatel-lucent.com>
References: <55C8AA8E.4000802@mti-systems.com>
In-Reply-To: <55C8AA8E.4000802@mti-systems.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.41]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="SHA1"; boundary="----=_NextPart_000_000E_01D0D5D0.2365EAA0"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/YHDP7JCZjRvCKs62cDIQ-oY4s-g>
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: Thu, 13 Aug 2015 11:58:42 -0000

Hi all,

I read the latest version of the draft, and I found it useful. The draft
addresses a comprehensive range of topics for AQM characterization. What I
am not so happy with, is the description of the corresponding experiments.
Some critical points of my first review
https://mailarchive.ietf.org/arch/msg/aqm/OwPTGmXLpEmCChpgE7ZFqFnnT64 still
persist. I would like to regard these experiments as initial proposals
(which is good to have) that might undergo substantial revision in practice
later on. In general I have the feeling that the combinatorial number of
mandatory experiments is close to infinity. Not only that I doubt this will
ever be done; but who is subsequently going to judge the huge amount of
results?

Here are some minor comments:

Section 2.7 defines goodput/delay scatter plots in two different ways: On
with reference to [HAYE2013], the other definition with reference to
[WINS2014]. I would prefer to have only one definition, namely [WINS2014]. 
- [HAYE2013] depends on a parameter variation across certain range (e.g.
traffic load, or buffer size) that is not defined in most of our
experiments.
- [WINS2014] depends only on randomized replication of otherwise identical
experiments. This should be applicable to any of the evaluation experiments.
(In fact, it is unavoidable anyway.)

Section 4.3: The term "long-lived non application-limited UDP" is somewhat
infinite bandwidth. What the authors probably mean is "long-lived UDP flow
from unresponsive application" to make it clear that no application layer
congestion control is present like in NFS.

Section 2.1: Formula on flow completion time: mismatch of dimensions (Byte
vs. Mbps)



Wolfram Lautenschlaeger



-----Ursprüngliche Nachricht-----
Von: aqm [mailto:aqm-bounces@ietf.org] Im Auftrag von Wesley Eddy
Gesendet: Montag, 10. August 2015 15:44
An: aqm@ietf.org
Betreff: [aqm] WGLC on draft-ietf-aqm-eval-guidelines

As chairs, Richard and I would like to start a 2-week working group last
call on the AQM characterization guidelines:

https://datatracker.ietf.org/doc/draft-ietf-aqm-eval-guidelines/

Please make a review of this, and send comments to the list or chairs.  Any
comments that you might have will be useful to us, even if it's just to say
that you've read it and have no other comments.

Thanks!

--
Wes Eddy
MTI Systems

_______________________________________________
aqm mailing list
aqm@ietf.org
https://www.ietf.org/mailman/listinfo/aqm