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

Preethi Natarajan <preethi.cis@gmail.com> Fri, 15 November 2013 01:33 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 6778321E80F1 for <aqm@ietfa.amsl.com>; Thu, 14 Nov 2013 17:33:41 -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 UGT7UWfldwI9 for <aqm@ietfa.amsl.com>; Thu, 14 Nov 2013 17:33:40 -0800 (PST)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id B0AE021E80EC for <aqm@ietf.org>; Thu, 14 Nov 2013 17:33:40 -0800 (PST)
Received: by mail-pd0-f170.google.com with SMTP id q10so2809735pdj.1 for <aqm@ietf.org>; Thu, 14 Nov 2013 17:33:40 -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=ZBuDahNjzos8nlG92ibdYh8nTZjrp99jWgbZ56cWy3I=; b=nBniZ13rhR9A8L5l6mD98Gu3ax7B37fSthBcOLVPPUWEA2LuhIT1lB+X5TN8oyXNOD mwGHwHVCvObDIwLbOAMqmvd0VBhaNRGhFW5SykuEWi7H9bXqCVC/mt1AJZa10MrC1Kgk 8J9a/PxtzxA/gchGd+1cGQBvFV8vyRH8hWteiUPP4woYTVJjTI3zjRIfwPe5w2Jrv9n9 Hu8aUDQxhdS1kpdTda195EaKR20OwRhovZqOJUldqVilb3/ryNhXiN+3ujslBpmOINYV kNE7Ua5kyxvNQQ/B7YTbnIUtcfHpIeOGUEUG4iHb9IOs4l+n76BgwE7DurP/wb+5jUo6 AcMg==
X-Received: by 10.66.216.162 with SMTP id or2mr306172pac.179.1384479219381; Thu, 14 Nov 2013 17:33:39 -0800 (PST)
Received: from [10.21.113.167] (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPSA id pl1sm619614pbb.20.2013.11.14.17.33.37 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 14 Nov 2013 17:33:38 -0800 (PST)
User-Agent: Microsoft-MacOutlook/14.2.1.120420
Date: Thu, 14 Nov 2013 17:33:35 -0800
From: Preethi Natarajan <preethi.cis@gmail.com>
To: Naeem Khademi <naeem.khademi@gmail.com>
Message-ID: <CEAAB727.4B5D1%prenatar@cisco.com>
Thread-Topic: [aqm] AQM schemes: Queue length vs. delay based
In-Reply-To: <CAEjQQ5WpeB0L7pN3joh233QgvNV2VMkN2U9BPCwFmBYjoVCrAQ@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3467295218_8405811"
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: Fri, 15 Nov 2013 01:33:41 -0000


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

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


Just pointing out the evidence here --
http://www.ietf.org/proceedings/86/slides/slides-86-iccrg-5.pdf

The slides contain preliminary results from DC scenarios, showing PIE's
parameters and adaptability to DC scenarios. Thank god for the IETF archives
:)

Thanks,
Preethi