[aqm] Benoit Claise's Discuss on draft-ietf-aqm-recommendation-09: (with DISCUSS and COMMENT)

"Benoit Claise" <bclaise@cisco.com> Wed, 18 February 2015 22:43 UTC

Return-Path: <bclaise@cisco.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 A327B1A1B47; Wed, 18 Feb 2015 14:43:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 P2rnAWYRZ5vG; Wed, 18 Feb 2015 14:43:25 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 522901A0113; Wed, 18 Feb 2015 14:43:25 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Benoit Claise" <bclaise@cisco.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150218224325.29443.89305.idtracker@ietfa.amsl.com>
Date: Wed, 18 Feb 2015 14:43:25 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/SLEI58o5-zKsWqIkZcVkamK5-aU>
Cc: mehmet.ersue@nsn.com, rs@netapp.com, aqm-chairs@ietf.org, aqm@ietf.org, draft-ietf-aqm-recommendation.all@ietf.org
Subject: [aqm] Benoit Claise's Discuss on draft-ietf-aqm-recommendation-09: (with DISCUSS and COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 18 Feb 2015 22:43:27 -0000

Benoit Claise has entered the following ballot position for
draft-ietf-aqm-recommendation-09: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Hopefully an easy DISCUSS.
  3.  The algorithms that the IETF recommends SHOULD NOT require
       operational (especially manual) configuration or tuning.

This sentence above could be understood in different ways. For example,
that any configuration is wrong. 
The ability to activate AQM is a good thing IMO. 
The section 4.3 title is closer to what you intend to say: "AQM
algorithms deployed SHOULD NOT require operational tuning"
The issue is that you only define what you mean by "operational
configuration" in section 4.3

Proposal:

OLD:
  3.  The algorithms that the IETF recommends SHOULD NOT require
       operational (especially manual) configuration or tuning.

NEW: 
  3.  AQM algorithm deployment SHOULD NOT require tuning of initial or
configuration parameters. 

OLD:
4.3 AQM algorithms deployed SHOULD NOT require operational tuning

NEW:
4.3 AQM algorithm deployment SHOULD NOT require tuning


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

- RFC 2309 introduced the concept of "Active Queue Management" (AQM), a
   > class of technologies that, by signaling to common congestion-
   controlled transports such as TCP, manages the size of queues that

Remove >


-
  Network devices SHOULD use an AQM algorithm to measure local local
   congestion 

local local