Re: [aqm] Benoit Claise's Discuss on draft-ietf-aqm-eval-guidelines-11: (with DISCUSS and COMMENT)

"MORTON, ALFRED C (AL)" <acmorton@att.com> Fri, 20 May 2016 12:53 UTC

Return-Path: <acmorton@att.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EA2312D90E; Fri, 20 May 2016 05:53:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.627
X-Spam-Level:
X-Spam-Status: No, score=-5.627 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001] autolearn=ham autolearn_force=no
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 WAe4RgOeIsqh; Fri, 20 May 2016 05:53:46 -0700 (PDT)
Received: from mail-pink.research.att.com (mail-pink.research.att.com [204.178.8.22]) by ietfa.amsl.com (Postfix) with ESMTP id 2E2BD12D914; Fri, 20 May 2016 05:53:46 -0700 (PDT)
Received: from mail-blue.research.att.com (unknown [135.207.178.11]) by mail-pink.research.att.com (Postfix) with ESMTP id 97CC71217A8; Fri, 20 May 2016 09:01:53 -0400 (EDT)
Received: from exchange.research.att.com (njfpsrvexg0.research.att.com [135.207.255.124]) by mail-blue.research.att.com (Postfix) with ESMTP id 8A30AF3E6F; Fri, 20 May 2016 08:53:45 -0400 (EDT)
Received: from NJFPSRVEXG0.research.att.com ([fe80::108a:1006:9f54:fd90]) by NJFPSRVEXG0.research.att.com ([fe80::108a:1006:9f54:fd90%25]) with mapi; Fri, 20 May 2016 08:53:45 -0400
From: "MORTON, ALFRED C (AL)" <acmorton@att.com>
To: Benoit Claise <bclaise@cisco.com>, The IESG <iesg@ietf.org>
Date: Fri, 20 May 2016 08:53:44 -0400
Thread-Topic: Benoit Claise's Discuss on draft-ietf-aqm-eval-guidelines-11: (with DISCUSS and COMMENT)
Thread-Index: AdGxsjVF1YO00Z+zR2CPQdmcLm258QA4PhFQ
Message-ID: <4AF73AA205019A4C8A1DDD32C034631D458D3D3108@NJFPSRVEXG0.research.att.com>
References: <20160519093824.17314.65212.idtracker@ietfa.amsl.com>
In-Reply-To: <20160519093824.17314.65212.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/OsLlAddUyurQq9VGhrogPBnGHLY>
Cc: "wes@mti-systems.com" <wes@mti-systems.com>, linda Dunbar <linda.dunbar@huawei.com>, "aqm-chairs@ietf.org" <aqm-chairs@ietf.org>, "draft-ietf-aqm-eval-guidelines@ietf.org" <draft-ietf-aqm-eval-guidelines@ietf.org>, "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] Benoit Claise's Discuss on draft-ietf-aqm-eval-guidelines-11: (with DISCUSS and COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.17
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, 20 May 2016 12:53:49 -0000

All,
a few replies in-line below,
Al

> -----Original Message-----
> From: Benoit Claise [mailto:bclaise@cisco.com]
> Sent: Thursday, May 19, 2016 5:38 AM
> To: The IESG
> Cc: draft-ietf-aqm-eval-guidelines@ietf.org; wes@mti-systems.com; aqm-
> chairs@ietf.org; wes@mti-systems.com; aqm@ietf.org; linda Dunbar;
> MORTON, ALFRED C (AL)
> Subject: Benoit Claise's Discuss on draft-ietf-aqm-eval-guidelines-11:
> (with DISCUSS and COMMENT)
> 
> Benoit Claise has entered the following ballot position for
> draft-ietf-aqm-eval-guidelines-11: Discuss
> 
...
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> Has a RFC6390 performance directorate review done for the 2.X metrics?
> It
> should.
[ACM] 
I reviewed this draft about 18 months ago.
Mostly, it points to existing RFCs for fundamental metrics,
and discusses others.  I read this:
   ...This document provides characterization guidelines that
   can be used to assess the deployability of an AQM, whether it is
   candidate for standardization at IETF or not.
as restricted to lab testing.

> See http://www.ietf.org/iesg/directorate/performance-metrics.html
> I guess that the metrics will be recorded in the future (See
> draft-ietf-ippm-metric-registry-06
> ), right?
[ACM] 
That's up to the authors, they might simply point to 
metrics in the registry contributed by others 
(when following these guidelines at a future time).
 
> For example, Flow Completion Time and Packet Loss Synchronization are
> new, I believe.
[ACM] 
Flow Completion Time is close to a definition for a new metric,
and could benefit from more attention, perhaps a few more details.
RFC6390 will provide some areas for improvement.

Packet loss sync full methodology is described in [JAY006],
according to the text. 

> And some other metrics are already documented in RFC6390 compliant
> documents. Pointers should be provided.
[ACM] 
Most others are discussion sections and provide references.

> See
> https://tools.ietf.org/html/draft-ietf-xrblock-independent-burst-gap-
> discard-01#appendix-A
> for an example
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> - Random Early Detection (RED), BLUE, and Proportional Integral
> controller (PI)
> Would you have references?
> 
> - BDP is mentioned a few times. Please expand.
> 
> - Glossary section = terminology section, right? If we want to be
> consistent across documents
> 
> - section 12.2. Why not a MUST below?
>    In order to understand an AQM's deployment considerations and
>    performance under a specific environment, AQM proposals SHOULD
>    describe the parameters that control the macroscopic AQM behavior,
>    and identify any parameters that require tuning to operational
>    conditions.
>