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

Naeem Khademi <naeem.khademi@gmail.com> Thu, 14 November 2013 21:06 UTC

Return-Path: <naeem.khademi@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 30C1311E810D for <aqm@ietfa.amsl.com>; Thu, 14 Nov 2013 13:06:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.325
X-Spam-Level:
X-Spam-Status: No, score=-2.325 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, 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 YB4L-ZIZaHSA for <aqm@ietfa.amsl.com>; Thu, 14 Nov 2013 13:06:54 -0800 (PST)
Received: from mail-vb0-x232.google.com (mail-vb0-x232.google.com [IPv6:2607:f8b0:400c:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id 5B09011E80FA for <aqm@ietf.org>; Thu, 14 Nov 2013 13:06:54 -0800 (PST)
Received: by mail-vb0-f50.google.com with SMTP id x11so2136392vbb.23 for <aqm@ietf.org>; Thu, 14 Nov 2013 13:06:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WpHPFIyajG7ntPhLlQMxzihZgoRqFdyywGQi0LRiHJk=; b=Ej2rZa/fDSmkNgmiMaJT85Za0+OmoS+HcPH6mSIX+Xb1EnL1rzAFn9GiUYFfKTNywT du09IZVhAOBbWy+djgyROjND0+v9pgQn8jeJBxun6OVfw/bOPz4gO5DXuSyc3Rs6bS9g N6xW7IM2KXLBeqYi6sufGU4jfRvzd05O2ZP8RYIZLRqt5Bkoxs/rkDoh8sRugTAtS6gc hix1dw9jPw9q8HmKbDCpLpMqGR2xDSu5sRwsDJJXm2uCTuhHrLOmp7dEhWoazjgg3HWB a3rxxt0Ef+wy+Pq82ktelVcmhi2SvqZrMAhlFMy6twVyW8DFJezAp6q+DOVSd0MpN6ks qCBQ==
MIME-Version: 1.0
X-Received: by 10.221.16.200 with SMTP id pz8mr756574vcb.53.1384463211012; Thu, 14 Nov 2013 13:06:51 -0800 (PST)
Received: by 10.220.109.5 with HTTP; Thu, 14 Nov 2013 13:06:50 -0800 (PST)
In-Reply-To: <CEAA68B4.4B53A%prenatar@cisco.com>
References: <CAEjQQ5U+86aT=V9FxvSam9mQNzvUdtuf25HV55XXMQPE5095Og@mail.gmail.com> <CEAA68B4.4B53A%prenatar@cisco.com>
Date: Thu, 14 Nov 2013 22:06:50 +0100
Message-ID: <CAEjQQ5WpeB0L7pN3joh233QgvNV2VMkN2U9BPCwFmBYjoVCrAQ@mail.gmail.com>
From: Naeem Khademi <naeem.khademi@gmail.com>
To: Preethi Natarajan <preethi.cis@gmail.com>
Content-Type: multipart/alternative; boundary="001a11338bfee5a93c04eb297502"
Cc: Anoop Ghanwani <anoop@alumni.duke.edu>, "aqm@ietf.org" <aqm@ietf.org>, Michael Welzl <michawe@ifi.uio.no>, curtis <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 21:06:55 -0000

This should have probably been brought in different thread...

comments follow inline

On Thu, Nov 14, 2013 at 9:00 PM, Preethi Natarajan <preethi.cis@gmail.com>wrote:

>
>
> 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.
>

Taking what is mentioned in above sentence granted, there is no evidence if
it cannot or if it can and this point is also orthogonal to my response to
Anoop which was about his question at IETF about AQM deployment in general.



>
> Given that, its too early to "hope" that different network scenarios needdifferent 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.
>

It should have been on another thread. Sorry :-)


>
> Preethi
>

Naeem