General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Vishal Misra <misra@cs.columbia.edu>
To: Dave Taht <dave.taht@gmail.com>
Cc: "aqm@ietf.org" <aqm@ietf.org>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] the cisco pie patent and IETF IPR filing
Date: Fri, 6 Mar 2015 14:46:14 -0500	[thread overview]
Message-ID: <FF2FCC82-97AB-4917-A33E-71357D7DE8BB@cs.columbia.edu> (raw)
In-Reply-To: <CAA93jw4p-jYt_XLN+NQbAGyLWVAHuRWcVab0CpJBkmpE5QoTBA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2424 bytes --]

Hi Dave,

> On Mar 5, 2015, at 8:58 AM, Dave Taht <dave.taht@gmail.com> wrote:
> 
> I let the data take me where it may. I (not) always have, but reformed
> about 15 years ago. [1] I hope that you and your students also,  do
> some experiments on the successors to PI and RED and DRR - and also
> follow the data where-ever it leads you.



In 2003 we had published a paper on STPI (Self-Tuning PI). The self-tuning design accounted for variations in link capacity, presence of cross traffic (i.e. unregulated UDP flows) and variations in the number of flows being controlled. We also proved the (local, exponential) stability of our self-tuning mechanism.

The paper is available at http://dna-pubs.cs.columbia.edu/citation/paperfile/79/GLOBECOM_2003_STAQM.pdf

This was an evolution over our first PI design where we introduced the concept of linear controllers for AQM.

BTW STPI is not PIE, the differences as I see them are

(1) STPI explicitly accounts for cross traffic.
(2) STPI tunes the parameters continuously, over the entire range of loss (marking) rates unlike PIE which seems to be doing it for 3 specific values chosen ahead of time.
(3) The stability of the adaptive mechanism of STPI was rigorously proven in a linearized setting. 
(4) The tradeoff between stability and responsiveness for the time constant of adaptation was made explicit.
(5) STPI does not, as the author of PIE stated recently "control the offset to the reference level and second moment of the latency independently”. STPI simply controls the latency, I don’t know of any way to control the second moment of any reference signal by a linear controller like PI(E), but then I do not know the details of PIE. It was a very deliberate design choice by us to introduce a linear controller like PI for AQM because of ease of implementation. We could’ve gone the route of optimal and/or non-linear controllers but we didn’t.

As a side note, we also designed a self-tuning version of RED that we called STRED (different from ARED) but RED suffers from some fundamental limitations so exploring that won’t be of interest.

So I am getting STPI and PI implemented as part of cerowrt and will release the code for anyone to play with/evaluate.

More than anything, it is the increased deployment of ECN that has revived an interest in AQM for me.

-Vishal
--
http://www.cs.columbia.edu/~misra/




[-- Attachment #2: Type: text/html, Size: 7203 bytes --]

  reply	other threads:[~2015-03-06 19:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04  6:07 Dave Taht
     [not found] ` <D11CA814.D0B3%ropan@cisco.com>
2015-03-04 23:37   ` [Bloat] [aqm] " Dave Taht
     [not found] ` <473265656416337848@unknownmsgid>
     [not found]   ` <D11C0740.3B84%kk@cs.ucr.edu>
2015-03-04  9:42     ` David Lang
2015-03-05 13:58   ` [Bloat] " Dave Taht
2015-03-06 19:46     ` Vishal Misra [this message]
     [not found]     ` <4077D77B-6C1A-47DF-989C-76B4B99AF863@icloud.com>
2015-04-09 19:24       ` [Bloat] [aqm] " Dave Taht
2015-04-09 19:27         ` Steinar H. Gunderson
2015-04-09 19:45           ` Dave Taht
2015-04-09 19:28       ` Dave Taht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=FF2FCC82-97AB-4917-A33E-71357D7DE8BB@cs.columbia.edu \
    --to=misra@cs.columbia.edu \
    --cc=aqm@ietf.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox