Re: [aqm] Immediate ECN: Autotuning AQM for RTT
John Leslie <john@jlc.net> Fri, 08 November 2013 01:05 UTC
Return-Path: <john@jlc.net>
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 5DC3121E814B for <aqm@ietfa.amsl.com>; Thu, 7 Nov 2013 17:05:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.279
X-Spam-Level:
X-Spam-Status: No, score=-106.279 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
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 bbZBSutHF2C4 for <aqm@ietfa.amsl.com>; Thu, 7 Nov 2013 17:05:47 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id C712C21E8121 for <aqm@ietf.org>; Thu, 7 Nov 2013 17:05:46 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 1785CC94C1; Thu, 7 Nov 2013 20:05:38 -0500 (EST)
Date: Thu, 07 Nov 2013 20:05:38 -0500
From: John Leslie <john@jlc.net>
To: Bob Briscoe <bob.briscoe@bt.com>
Message-ID: <20131108010538.GD70761@verdi>
References: <201311072003.rA7K38dj008566@bagheera.jungle.bt.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <201311072003.rA7K38dj008566@bagheera.jungle.bt.co.uk>
User-Agent: Mutt/1.4.1i
Cc: AQM IETF list <aqm@ietf.org>
Subject: Re: [aqm] Immediate ECN: Autotuning AQM for RTT
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, 08 Nov 2013 01:05:51 -0000
Bob Briscoe <bob.briscoe@bt.com> wrote: > > "Immediate ECN" slides: > > <http://bobbriscoe.net/presents/1311ietf/1311tsvarea-iecn.pdf> > > PS. This talk fell off the end of the TSVAREA agenda. It's mostly > relevant to AQM, but I didn't originally bring it to AQM, because it > affects 3 wgs: tsvwg, aqm & tcpm. (responding only on AQM...) > In the AQM wg, there was dismay about CableLabs not including > anything about ECN in DOCSIS3.1. This talk is about AQM dynamics; and > how ECN can take out the 100ms of delay that CoDel and PIE introduce > - it's essentially about auto-tuning for RTT. I don't entirely follow what Bob is proposing; but in essence he proposes that packets which would _not_ otherwise be dropped get an ECN mark, and let the transport apply "smoothing" to correct for the RTT of buffering necessary to fill the available bandwidth. There are various ways to accomplish this, and I won't consider them here: the essential question is whether we consider latency important enough to diddle with ECN signaling to allow short-RTT flows to react to congestion sooner than long-RTT flows (rather than have the forwarding node guess what RTT is proper). I strongly endorse work in that direction. > It gives an interim recommendation for hardware designers that there > should be a second instance of the AQM algo for ECN packets so that > it can be configured with different parameters (think of WRED instead of > RED). > > Specifically, for ECN packets: > interval = 0 (for CoDel) > max_burst = 0 (for PIE) As I understand it, Bob wishes to apply different parameters for ECN-capable packets in order to remove the allowance for buffering sufficient to cover the RTT. This is definitely not the only way to think about the issue; and Bob could do a very good job of explaining other ways (which I likely would prefer). But at this point, Bob is simply asking whether the whole idea is worth talking about in the IETF... ==== The AQM Friday agenda looks tight; so I'm not expecting Bob's slides to be covered then. To be blunt, I will attend CLUE instead unless ECN issues will be covered Friday... Regardless, I intend to follow the AQM list carefully. -- John Leslie <john@jlc.net>
- [aqm] Immediate ECN: Autotuning AQM for RTT Bob Briscoe
- Re: [aqm] Immediate ECN: Autotuning AQM for RTT John Leslie
- Re: [aqm] [tsvwg] Immediate ECN: Autotuning AQM f… Greg White
- Re: [aqm] Immediate ECN: Autotuning AQM for RTT Rong Pan (ropan)
- Re: [aqm] Immediate ECN: Autotuning AQM for RTT Bob Briscoe
- Re: [aqm] [tsvwg] Immediate ECN: Autotuning AQM f… Bob Briscoe
- Re: [aqm] [tsvwg] Immediate ECN: Autotuning AQM f… Greg White
- Re: [aqm] [tsvwg] Immediate ECN: Autotuning AQM f… Scheffenegger, Richard
- Re: [aqm] [tsvwg] Immediate ECN: Autotuning AQM f… Bob Briscoe
- Re: [aqm] [tsvwg] Immediate ECN: Autotuning AQM f… Bob Briscoe
- Re: [aqm] [tsvwg] Immediate ECN: Autotuning AQM f… Ilpo Järvinen
- Re: [aqm] [tsvwg] Immediate ECN: Autotuning AQM f… Fred Baker (fred)
- Re: [aqm] [tsvwg] Immediate ECN: Autotuning AQM f… Fred Baker (fred)
- Re: [aqm] [tsvwg] Immediate ECN: Autotuning AQM f… Fred Baker (fred)