[aqm] AQM schemes: Queue length vs. delay based

Preethi Natarajan <preethi.cis@gmail.com> Fri, 08 November 2013 02:47 UTC

Return-Path: <preethi.cis@gmail.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 7C33221F9CA5 for <aqm@ietfa.amsl.com>; Thu, 7 Nov 2013 18:47:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.975
X-Spam-Level:
X-Spam-Status: No, score=-0.975 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, SARE_SUB_OBFU_Q1=0.227]
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 dJcCX9c7qUE6 for <aqm@ietfa.amsl.com>; Thu, 7 Nov 2013 18:47:08 -0800 (PST)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 76EAA21E80F4 for <aqm@ietf.org>; Thu, 7 Nov 2013 18:47:06 -0800 (PST)
Received: by mail-pd0-f172.google.com with SMTP id w10so1489580pde.31 for <aqm@ietf.org>; Thu, 07 Nov 2013 18:47:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=user-agent:date:subject:from:to:message-id:thread-topic:in-reply-to :mime-version:content-type; bh=WAejQoQ+Pnu7N0WV8qwNNQE39tHk6BHs1rgufb+7HWg=; b=DwbImV7Gj2Sq87rMwV5OmrXIPNiWKWB5M0yCBXKyWVEc8PTAdTgkfNnCHl+fSwgdQG h0oX4EmHC0BEbybQB0lJgL9gf4mRvdo4KD/qwvo7rKem7PRqIdIyt64DXoS9xcpwN9V6 Ep9FdSBChszemEYQHvlFX6KD4vp1GQXjimKgJx8+ikmYhCJnMF2her/7meTJwun079u2 J6qpFDGOrzr/CTHhz/M5gwGWugHvX39MmgspmWaJlRAcs72gpS6INYwom6EM1TjyKslE FPbnfih9pM7ROVzdt64TEbtK547qPggOssjnEpZNl4sODKfxQG2cvHK9EgBC2q9bpKkU Sxvg==
X-Received: by 10.68.179.4 with SMTP id dc4mr12263530pbc.45.1383878826037; Thu, 07 Nov 2013 18:47:06 -0800 (PST)
Received: from [192.168.1.105] (c-76-103-130-90.hsd1.ca.comcast.net. [76.103.130.90]) by mx.google.com with ESMTPSA id i10sm10149993pat.11.2013.11.07.18.46.56 for <aqm@ietf.org> (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 07 Nov 2013 18:47:05 -0800 (PST)
User-Agent: Microsoft-MacOutlook/14.2.1.120420
Date: Thu, 07 Nov 2013 18:46:39 -0700
From: Preethi Natarajan <preethi.cis@gmail.com>
To: aqm@ietf.org
Message-ID: <CEA1905E.4AE3B%prenatar@cisco.com>
Thread-Topic: AQM schemes: Queue length vs. delay based
In-Reply-To: <CEA17DD6.4AE2D%preethi.cis@gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3466694820_9734681"
Subject: [aqm] AQM schemes: Queue length vs. delay based
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.12
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: <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: Fri, 08 Nov 2013 02:47:09 -0000

Hello AQMers:

Just wanted to bring up the following item for discussion either as part of
the recommendations draft or the evaluation criteria during Friday's
session/mailing list.

In access, edge and core routers the draining rate of a queue is affected by
traffic on other queues and thus can vary a lot (depending on the deployment
and traffic conditions). A queue length based AQM scheme such as RED or
derivatives tries to maintain the average queue size around a predictable
value under these changing draining rates. However, this queue size
translates to high queuing delay under low draining rates and vice-versa.
The unpredictability in resulting queueing delay was one of the reasons why
we opted PIE to be a latency-based scheme.

A queue length based AQM scheme could be perfectly valid for certain
deployments. For deployments where predictable queuing delay is expected
under varying draining rates, a latency based AQM is critical. We believe
this should be brought about in discussions somewhere at AQM ‹ perhaps in
the recommendations draft or w.r.t evaluation criteria.

Thanks,
Preethi (on behalf of PIE team)