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

Preethi Natarajan <preethi.cis@gmail.com> Thu, 14 November 2013 20:00 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 3CDA421E8137 for <aqm@ietfa.amsl.com>; Thu, 14 Nov 2013 12:00:21 -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 bLYYy3yuaGLC for <aqm@ietfa.amsl.com>; Thu, 14 Nov 2013 12:00:20 -0800 (PST)
Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 7503D21E8134 for <aqm@ietf.org>; Thu, 14 Nov 2013 12:00:16 -0800 (PST)
Received: by mail-pa0-f45.google.com with SMTP id kx10so1788589pab.32 for <aqm@ietf.org>; Thu, 14 Nov 2013 12:00:16 -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=g6VkEVsQp5XOqAwQl3XQHaXtiTaIfL5CQdA4IhVAbWU=; b=axaEyLsORKhChhl+Ll122pyfrLawbb1LAqdg4gfvhXUk6uWF0fqFiFttRvHMRS0v9U uru5GK0Mm3k7XFsY4L8jH/ya77OGkxWS5FTvgMB6GZqywm4/a9BzBhG+FJB7rFui0INb KWbHKCf/l7JBPPwT9/IwmnJvVX5QydKFTxYFFdTbtBwHhQeJB0YBnRSGIXKkkmLGPo6y PpfoVE7yrxwDJSk9z/gLVu5d704xJA7sriDg9dG0DjYNlf3pax7Oo9OVuzr/nqiBfPcO lKIXUdJOZ9RmUZI3hUiRFXSXSMdPsgpupfNfKxfAvrYrssQQ2Iu9lElLqLDX4Q9BU1/R Q1bA==
X-Received: by 10.68.171.164 with SMTP id av4mr3214109pbc.94.1384459216151; Thu, 14 Nov 2013 12:00:16 -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 sg1sm53415406pbb.16.2013.11.14.12.00.14 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 14 Nov 2013 12:00:15 -0800 (PST)
User-Agent: Microsoft-MacOutlook/14.2.1.120420
Date: Thu, 14 Nov 2013 12:00:05 -0800
From: Preethi Natarajan <preethi.cis@gmail.com>
To: Naeem Khademi <naeem.khademi@gmail.com>
Message-ID: <CEAA68B4.4B53A%prenatar@cisco.com>
Thread-Topic: [aqm] AQM schemes: Queue length vs. delay based
In-Reply-To: <CAEjQQ5U+86aT=V9FxvSam9mQNzvUdtuf25HV55XXMQPE5095Og@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3467275215_7580249"
Cc: Anoop Ghanwani <anoop@alumni.duke.edu>, "aqm@ietf.org" <aqm@ietf.org>, Michael Welzl <michawe@ifi.uio.no>, curtis@ipv6.occnc.com
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 20:00:21 -0000


From:  Naeem Khademi <naeem.khademi@gmail.com>
Date:  Thursday, November 14, 2013 8:05 AM
To:  Anoop Ghanwani <anoop@alumni.duke.edu>
Cc:  <curtis@ipv6.occnc.com>, Michael Welzl <michawe@ifi.uio.no>,
"aqm@ietf.org" <aqm@ietf.org>, Preethi Natarajan <preethi.cis@gmail.com>
Subject:  Re: [aqm] AQM schemes: Queue length vs. delay based

> 
> 
> Below is my personal opinion, but hopefully Fred can clarify this better based
> on the AQM recommendations draft:
> 
> "applicability of AQM to all types of networks/switches" => "yes"
> 
> "applicability of *any* AQM to all types of networks/switches" => "no"
>  
>> Perhaps AQM cannot help this, but hopefully it won't hurt.  Trying to do
>> fancy things with small buffers is challenging.
> 
> AQM will most likely to help from data centers to the access links, and so on.
> But we may possibly need different AQMs for different network scenarios; The
> fact that an AQMs should be auto-tunable doesn't imply that it can be applied
> everywhere and we may need different auto-tunable AQMs specifically designed
> for different networks (ideally better if we could use fewer of them and they
> could work everywhere). I hope I'm not wrong.
>  

Again, please hold on. Even if its personal opinion, I would state facts
backed with evidence instead of "hopes", since the community's thought
process is at stake here.

>From the preliminary results we've seen, PIE has been able to address data
center issues quite well. There is no evidence thus far why PIE's control
law with auto-tuned parameters cannot adapt to data center or other network
environments. 

Given that, its too early to "hope" that different network scenarios need
different AQM schemes. Of course, different network environments may choose
to deploy different AQM schemes for various other reasons, which is not the
point of discussion here.

Preethi