
From nobody Tue Jan 10 08:08:32 2017
Return-Path: <dave.taht@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 A5D2C12952B for <aqm@ietfa.amsl.com>; Tue, 10 Jan 2017 08:08:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7-Bv7UZQbcvM for <aqm@ietfa.amsl.com>; Tue, 10 Jan 2017 08:08:29 -0800 (PST)
Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17A2E129418 for <aqm@ietf.org>; Tue, 10 Jan 2017 08:08:29 -0800 (PST)
Received: by mail-qt0-x236.google.com with SMTP id x49so103508297qtc.2 for <aqm@ietf.org>; Tue, 10 Jan 2017 08:08:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=5zquKaUMDIrdWZDK4X+4T8ql6Nxqg0kb+d9Hat2M1Mo=; b=s18NTWyNcTCdX+ykma+XGHWYonhXsE3NmfNJhrqETMet3uhR1ovxhRwCKX7G+Y+zXR jAKlNvqK+Y+EVOW1/n5jSF+QwStHQDwaRz0gbsR8w2jrNt3Y8HzeWZuzYv0dEWuAslW5 KkBjxLxFw0STqqMkEkll80mKVH0SIiD5bT+R+238Xr0Kb8pxXvkZNZsQvBOo+CAHgJCi sVRBV5CtYmlISEQgxwRiEOC7bt0Mh4d12ACt+Ey/C2D3szSVC+nYAWu26dkSnLxW3lgL DGQBuZ1J8xp89e6LpvUGtK8u21i0fTVeoAIdfKsPLEK5aSdy+FO9PS1+Z5TbL5RzKfuB S2EQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=5zquKaUMDIrdWZDK4X+4T8ql6Nxqg0kb+d9Hat2M1Mo=; b=MqpRXd21M9+ulRIPH/6jry+X+gMI+9wBIfPivLCqyLYR7uuKXvtzCb3YEz2u8QB8In gFO1sZxvhR7j9r6tiZA5R3Qmyqot9ErbzF/wVYy8pdM1tB4KXUwC/RyELjKFujr8R8l+ 51XtW4manm9F+XNngRRTz2iicfygFr3H3QnMDrK1NcaXA/42Z6/HUIPEu5d2MIyy0C/+ k6qdp9670+KzEwG84C/mfU2cxKkuqgd4tg31hNrwgUi9Jx5PCvWFGMO5r1hDzjLBaDyk xw37rZEiEpvnosOxfjNE6wTOL7JVQCAE/fT4MdDpffWZVxp4UZKklRcafkHYtqpeXVid MOBQ==
X-Gm-Message-State: AIkVDXIfs27tLPFbBb/OD6Db9ki9DdLWpqPLdcDKAg0cpUtauE5quBYFwBXpfXXz0gFc1RTN28g0O9NtpTD7uA==
X-Received: by 10.200.0.193 with SMTP id d1mr3200050qtg.275.1484064508189; Tue, 10 Jan 2017 08:08:28 -0800 (PST)
MIME-Version: 1.0
Received: by 10.12.152.197 with HTTP; Tue, 10 Jan 2017 08:08:27 -0800 (PST)
From: Dave Taht <dave.taht@gmail.com>
Date: Tue, 10 Jan 2017 08:08:27 -0800
Message-ID: <CAA93jw7kWJhmr-Su+BptKYo7P7DUmo5vsLDswBcpZSia+KvyjA@mail.gmail.com>
To: bloat <bloat@lists.bufferbloat.net>, "aqm@ietf.org" <aqm@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/aqm/Y7ZSEcAO_yr6AIpYFWcttb-sZSA>
Subject: [aqm] The Impact of Active Queue Management on DASH-based Content Delivery
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 10 Jan 2017 16:08:30 -0000

This was quite good. I particularly liked the invention of the
"instability index".

Jonathan Kua, Grenville Armitage and Philip Branch, "The Impact of
Active Queue Management on DASH-based Content Delivery," in 41st
Annual IEEE Conference on Local Computer Networks (LCN), Dubai, UAE, 7
- 10 November 2016,    https://doi.org/10.1109/LCN.2016.24

(more easily available via: http://sci-hub.bz/10.1109/LCN.2016.24# )

I hope a test like this gets repeated against BBR (and for that
matter, cake), and against a larger dynamic range of bandwidths (4k
video, anyone)?


From andrea.francini@nokia-bell-labs.com  Tue Jan 10 09:37:38 2017
Return-Path: <andrea.francini@nokia-bell-labs.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 0B9BF129D3B for <aqm@ietfa.amsl.com>; Tue, 10 Jan 2017 09:37:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.921
X-Spam-Level: 
X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6_xdVrhv1cZE for <aqm@ietfa.amsl.com>; Tue, 10 Jan 2017 09:37:36 -0800 (PST)
Received: from smtp-us.alcatel-lucent.com (us-hpswa-esg-02.alcatel-lucent.com [135.245.18.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37B9F128B44 for <aqm@ietf.org>; Tue, 10 Jan 2017 09:37:36 -0800 (PST)
Received: from us70uumx4.dmz.alcatel-lucent.com (unknown [135.245.18.16]) by Websense Email Security Gateway with ESMTPS id 4EAD853317B92; Tue, 10 Jan 2017 17:37:33 +0000 (GMT)
Received: from us70uusmtp4.zam.alcatel-lucent.com (us70uusmtp4.zam.alcatel-lucent.com [135.5.2.66]) by us70uumx4.dmz.alcatel-lucent.com (GMO) with ESMTP id v0AHbYGM031284 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 10 Jan 2017 17:37:35 GMT
Received: from US70UWXCHHUB01.zam.alcatel-lucent.com (us70uwxchhub01.zam.alcatel-lucent.com [135.5.2.48]) by us70uusmtp4.zam.alcatel-lucent.com (GMO) with ESMTP id v0AHbGpJ012387 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 10 Jan 2017 17:37:31 GMT
Received: from US70TWXCHMBA12.zam.alcatel-lucent.com ([169.254.6.35]) by US70UWXCHHUB01.zam.alcatel-lucent.com ([135.5.2.48]) with mapi id 14.03.0301.000; Tue, 10 Jan 2017 12:37:22 -0500
From: "Francini, Andrea (Nokia - US)" <andrea.francini@nokia-bell-labs.com>
To: Dave Taht <dave.taht@gmail.com>, bloat <bloat@lists.bufferbloat.net>, "aqm@ietf.org" <aqm@ietf.org>
Thread-Topic: [ALU] [aqm] The Impact of Active Queue Management on DASH-based ContentDelivery
Thread-Index: AQHSa1vMN6I8gSSxc0i/CMm7R5tPf6Ex9S2g
Date: Tue, 10 Jan 2017 17:37:22 +0000
Message-ID: <1BFAC0A1D7955144A2444E902CB628F8D641D35C@US70TWXCHMBA12.zam.alcatel-lucent.com>
References: <CAA93jw7kWJhmr-Su+BptKYo7P7DUmo5vsLDswBcpZSia+KvyjA@mail.gmail.com>
In-Reply-To: <CAA93jw7kWJhmr-Su+BptKYo7P7DUmo5vsLDswBcpZSia+KvyjA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.5.27.16]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/aqm/2zXHht8ixCerW-sIv3YBSQ_gIIE>
Subject: Re: [aqm] [ALU] The Impact of Active Queue Management on DASH-based ContentDelivery
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 10 Jan 2017 17:39:32 -0000

It looks like tcp_slow_start_after_idle was not disabled in the experiments=
. If this is indeed the case, it would be interesting to see what happens w=
hen the option is disabled at the server, so that the transmission of a new=
 chunk can start at a generally faster rate. 4K video makes this option eve=
n more relevant, especially when RTT is large.

With tcp_slow_start_after_idle disabled, the fq_nocodel scheme of Toke's st=
udy (http://dx.doi.org/10.1016/j.comnet.2015.07.014) would also be good to =
evaluate, especially with a total buffer size much larger than BDP: DASH do=
es not suffer from self-inflicted delay as much as it does from packet loss=
es, and empties its dedicated queue in between video chunks.

Andrea

-----Original Message-----
From: aqm [mailto:aqm-bounces@ietf.org] On Behalf Of Dave Taht
Sent: Tuesday, January 10, 2017 11:08 AM
To: bloat <bloat@lists.bufferbloat.net>; aqm@ietf.org
Subject: [ALU] [aqm] The Impact of Active Queue Management on DASH-based Co=
ntentDelivery

This was quite good. I particularly liked the invention of the
"instability index".

Jonathan Kua, Grenville Armitage and Philip Branch, "The Impact of
Active Queue Management on DASH-based Content Delivery," in 41st
Annual IEEE Conference on Local Computer Networks (LCN), Dubai, UAE, 7
- 10 November 2016,    https://doi.org/10.1109/LCN.2016.24

(more easily available via: http://sci-hub.bz/10.1109/LCN.2016.24# )

I hope a test like this gets repeated against BBR (and for that
matter, cake), and against a larger dynamic range of bandwidths (4k
video, anyone)?

_______________________________________________
aqm mailing list
aqm@ietf.org
https://www.ietf.org/mailman/listinfo/aqm

