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

Preethi Natarajan <preethi.cis@gmail.com> Thu, 14 November 2013 01:18 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 E528521E80BF for <aqm@ietfa.amsl.com>; Wed, 13 Nov 2013 17:18:03 -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 NBYnWMwbrr76 for <aqm@ietfa.amsl.com>; Wed, 13 Nov 2013 17:18:03 -0800 (PST)
Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 5BA7021E8098 for <aqm@ietf.org>; Wed, 13 Nov 2013 17:18:03 -0800 (PST)
Received: by mail-pb0-f47.google.com with SMTP id rq2so1242496pbb.20 for <aqm@ietf.org>; Wed, 13 Nov 2013 17:18:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :in-reply-to:mime-version:content-type; bh=hPa6pKkLLGKLG4DZBnYH+X8dJiKLJUb9M65AWv4DQa0=; b=r0yiIrWOSNyeTbYrWAnt5maU5nrHuOuhtPV1IM1xbfAnVEL6fHNq5TwfGgzdbWCiGu bD7fTp8BJUaxZmhM3ObcKI5uw1R6n1UR9OBSNN9IUrGFVlPbu45o5sgfCwxCnztp4UqM MKGUdfUbgM8+0y8a/bXbXgeW+sy7jRbgeoP8IGN+tDoeMQpKsKAmLayte9whzrdQuK2+ tVnEuzgcWVNN5Hd9XXKHct7efKcn80a0v1MWKi9xxSHtyOdZ/D5IuRdIuHpgWD3ahYW8 VRnH13MrjzSboxIc3ezLOkanaImo8Ie3jkT7PGeluYHU+uKfgVy/6PnsnonisyJSDvpe 6j7A==
X-Received: by 10.66.118.129 with SMTP id km1mr17543914pab.127.1384391880796; Wed, 13 Nov 2013 17:18:00 -0800 (PST)
Received: from [10.21.148.218] (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPSA id ry4sm55038132pab.4.2013.11.13.17.17.58 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 13 Nov 2013 17:17:59 -0800 (PST)
User-Agent: Microsoft-MacOutlook/14.2.1.120420
Date: Wed, 13 Nov 2013 17:17:56 -0800
From: Preethi Natarajan <preethi.cis@gmail.com>
To: Naeem Khademi <naeem.khademi@gmail.com>
Message-ID: <CEA961B1.4B416%prenatar@cisco.com>
Thread-Topic: [aqm] AQM schemes: Queue length vs. delay based
In-Reply-To: <CAEjQQ5XrRX=hTP9csoRJ04cK_6MAaMWA9o1Cwwqbm3RHRdBxpw@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3467207879_6500777"
Cc: "aqm@ietf.org" <aqm@ietf.org>, Michael Welzl <michawe@ifi.uio.no>
Subject: Re: [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: Thu, 14 Nov 2013 01:18:04 -0000


From:  Naeem Khademi <naeem.khademi@gmail.com>
Date:  Wednesday, November 13, 2013 12:14 PM
To:  Preethi Natarajan <preethi.cis@gmail.com>
Cc:  Michael Welzl <michawe@ifi.uio.no>, "aqm@ietf.org" <aqm@ietf.org>
Subject:  Re: [aqm] AQM schemes: Queue length vs. delay based

> 
> Very true, though that's what ARED *is* with very low thresholds (e.g.
> resonate between 1 or 2 packets on the average in the queue). Indeed there can
> possibly be some future work on ARED's (or any other similar AQM) burst
> allowance but I don't think e.g. letting a 100 ms burst of packets to pass
> through can be a good way of fixing it as this can lead to massive variance in
> overall RTT distribution.

If you are referring to the burst_allowance parameter in PIE, this parameter
allows burst to go through when a system goes from an idle state into some
congestion state. The one we are talking about is accommodating bursts when
the system is in equilibirum -- how does the AQM scheme accommodate bursts
when already operating around target delay or congestion? Delay-based ARED
behaves similar to tail drop at max threshold. This is unacceptable of an
AQM even for max thresholds around 50ms.
Clearly delay-based ARED needs significant and careful redesign. I suppose
one can argue this task is as laborious as designing a new AQM scheme as
opposed to previous notions that delay-based ARED would work right out of
the box. 
Preethi