Re: [iccrg] Following up with (r)LEDBAT(++) presentations

Praveen Balasubramanian <pravb@microsoft.com> Mon, 04 November 2019 23:55 UTC

Return-Path: <pravb@microsoft.com>
X-Original-To: iccrg@ietfa.amsl.com
Delivered-To: iccrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3B37120812 for <iccrg@ietfa.amsl.com>; Mon, 4 Nov 2019 15:55:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 wzhZ7mgsJskt for <iccrg@ietfa.amsl.com>; Mon, 4 Nov 2019 15:55:47 -0800 (PST)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-eopbgr760122.outbound.protection.outlook.com [40.107.76.122]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 292CE1201EF for <iccrg@irtf.org>; Mon, 4 Nov 2019 15:55:47 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=oLu2x9kO1e2UphbONz11CBeSf9z0acs+cn1Gv5oQrIDiyIrt4hzPxKfMPePpPdxNuZxPw6ZULg+kT93eyS/2Y5VfSwps0uFDNmtFrp2xRcmeOhg0yzg2io/fWAYPMpIkJ6lXyI/pdUB/anQf32n7AFnDnDW5o9WJTaJeKuHVjINJp7VpPn7xvCbJTHF2NdMTx3Kvn8HMD66ujSRXuQZszMD3z+PE/C4CN1rMXcmTBw/UU7qyQEf8va7vIIFn35UQq36y21UFAeBBYmrBd6u7rLW7NRm+vE+bFnjmi75VGP7698+jL6VWJ25Ki36XDSfcTwMtvLzVMn6Nq/Uu3yhWaQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=rZ+GmFo+iDtFY0YkBgQVFo0tHLGigTIDrBRrEwsrl3Y=; b=XfflJlzhtMLzPg4/FTmd/zdDfwercbZT3VDmHSESim8HNEohnaGmZLpEd11IY2arkJji6PMDNiVefwKvtgqjOEbZUb/eG/xjj0Dos5/6sXHeLkGtXiDYyjTDOf7wrIN8YmlcYzNUYVvXbQI8JmJo4xRb09YPm9q8uyo4Jwkwqs08mqXmferLukq87eEUvZHbga8L16swryWwmYpWDXPpbTy8a0ayTi/WnriEzZhNJD7lFTfi3ECP7+aUuUB1mEhuslhjMy1BD4isT0r+EuFcuAN6xNRjVV5jrtmzEanYflGr4NIyYf/rlDNMm35ej1Cje5xvHSHjszU683CeTLeIcA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=rZ+GmFo+iDtFY0YkBgQVFo0tHLGigTIDrBRrEwsrl3Y=; b=E4c+EryFFcknSkxIZcLvVWzsJsHiW7lbPUBIshybx1ep82PmXeFf79lCsCWlO7kfdh8teHvr4ErUYPz7cWkqISR5KNGLFQh/bK339b46oMjxIvdcCqxHK+0MQ5PLpftarixqQespzW3CNnzBGtKQtN7QLG6S9Q2bj8gX8H8bgmw=
Received: from MW2PR2101MB1049.namprd21.prod.outlook.com (52.132.149.13) by MW2PR2101MB1018.namprd21.prod.outlook.com (52.132.146.31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2430.19; Mon, 4 Nov 2019 23:55:45 +0000
Received: from MW2PR2101MB1049.namprd21.prod.outlook.com ([fe80::d90d:509a:e6c8:9c19]) by MW2PR2101MB1049.namprd21.prod.outlook.com ([fe80::d90d:509a:e6c8:9c19%7]) with mapi id 15.20.2430.014; Mon, 4 Nov 2019 23:55:45 +0000
From: Praveen Balasubramanian <pravb@microsoft.com>
To: Kuhn Nicolas <Nicolas.Kuhn@cnes.fr>, "iccrg@irtf.org" <iccrg@irtf.org>
Thread-Topic: Following up with (r)LEDBAT(++) presentations
Thread-Index: AdVBoRtOiBYn2SLUTXKZEtZhVHp42xRxxQlA
Date: Mon, 04 Nov 2019 23:55:45 +0000
Message-ID: <MW2PR2101MB104938A51CCA113E55218480B67F0@MW2PR2101MB1049.namprd21.prod.outlook.com>
References: <F3B0A07CFD358240926B78A680E166FF1EC2505B@TW-MBX-P03.cnesnet.ad.cnes.fr>
In-Reply-To: <F3B0A07CFD358240926B78A680E166FF1EC2505B@TW-MBX-P03.cnesnet.ad.cnes.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Owner=pravb@ntdev.microsoft.com; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2019-11-04T23:55:44.1273314Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=General; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Application=Microsoft Azure Information Protection; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=f182c278-6747-464f-8439-0ae7e0a56fd1; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Extended_MSFT_Method=Automatic
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pravb@microsoft.com;
x-originating-ip: [2001:4898:80e8:0:6c7e:cda3:12a0:f9f8]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 2218bea9-347d-4073-3ff5-08d761828240
x-ms-traffictypediagnostic: MW2PR2101MB1018:
x-microsoft-antispam-prvs: <MW2PR2101MB101899F8F379044AB2F84051B67F0@MW2PR2101MB1018.namprd21.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0211965D06
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(136003)(39860400002)(396003)(366004)(376002)(189003)(199004)(51444003)(469094003)(51914003)(53484002)(86362001)(229853002)(9326002)(606006)(81156014)(33656002)(66574012)(8676002)(8936002)(81166006)(7696005)(236005)(52536014)(5660300002)(6246003)(25786009)(6436002)(10290500003)(9686003)(478600001)(2906002)(54896002)(55016002)(71200400001)(71190400001)(6306002)(2501003)(6116002)(790700001)(186003)(10090500001)(966005)(14454004)(7736002)(74316002)(8990500004)(316002)(76116006)(22452003)(64756008)(46003)(256004)(561944003)(14444005)(6506007)(66476007)(76176011)(66556008)(110136005)(53546011)(476003)(66946007)(66446008)(486006)(102836004)(99286004)(11346002)(446003); DIR:OUT; SFP:1102; SCL:1; SRVR:MW2PR2101MB1018; H:MW2PR2101MB1049.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: fxxKh71BLZT48+A1cy+Cnrppbcix5rpt4rjBL/IiIsp6dneQQlvSlPyQYwWweB+/umBZODWUlC+Cbv6w9AxfYbxTk6RgYI4QAGk4rjT+13hBWtpkzo5m8FybPPwfaWfKspfKpZFtYCBLCBvhhHFmhnuxPYf+BYGB6LEfrhRg8atIJWy8f7iosLLzne90ZWgW9NKomHlYR+824XvcXnvg2+w4UH7Ve2W/W69KyYfeb5pBrVNnRsnPC7xCYnMIIcWXuiLGqnsBOws5M3+MJ77wy7WgBv5MjbHZ9g7g8HIILyCIWACDrGluoa2WZ7SDnPk6gIjYywoXRdc+Q6DdrQASytG5Nk9F7K9jCPifBdZROLqsrtccZoeiXTmh6aki8R882FzHOSckSrVWmLEASW2uoiGXuWjkBlRt3WkK5EzMm7NC32UC3Up/QgGoifAOlzApL4jbrc3MKTHyCPBQ9W/v4Q==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MW2PR2101MB104938A51CCA113E55218480B67F0MW2PR2101MB1049_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 2218bea9-347d-4073-3ff5-08d761828240
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Nov 2019 23:55:45.3716 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 78ZyfjXC3iuTyy7tsaQKNQocVjqQfybfVpIsV6G09/8KHn44T7iBvC1XH7B/vqs9FT7CJ9fgqTFNBPKnsD7KGMmNmIq0VVpmg2tzq5MAa7Y=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MW2PR2101MB1018
Archived-At: <https://mailarchive.ietf.org/arch/msg/iccrg/Tpifr-o9bhxp5wbCfxlXpGIBPnk>
Subject: Re: [iccrg] Following up with (r)LEDBAT(++) presentations
X-BeenThere: iccrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussions of Internet Congestion Control Research Group \(ICCRG\)" <iccrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/iccrg>, <mailto:iccrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iccrg/>
List-Post: <mailto:iccrg@irtf.org>
List-Help: <mailto:iccrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/iccrg>, <mailto:iccrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Nov 2019 23:55:50 -0000

Hi Nico,

Re. fixed TARGET. There will be bottlenecks where additional TARGET delay cannot be added and there will be drops much before delay build up. In these cases LEDBAT++ will still do less than best effort compared to Reno. Please see the "Low latency competition" section. We default TARGET to 60 msec because that provided us the best trade-offs in all the lab measurements. Agreed that the choice of TARGET may vary in some networks so in our implementation it's a configurable parameter.

Thanks for the pointers to CDG and prior work on interaction between LBE and AQM!

From: iccrg <iccrg-bounces@irtf.org> On Behalf Of Kuhn Nicolas
Sent: Tuesday, July 23, 2019 3:14 PM
To: iccrg@irtf.org
Subject: [iccrg] Following up with (r)LEDBAT(++) presentations

Hi,

Thanks for the presentations on LEDBAT-related work.
I think that further evaluations of the proposals are required to better assess their relevance and their parameters.

Most of the content of this email was sent after the first presentation of LEDBAT++ but the points that are mentioned there seems still valid.
I hope this helps.

- Multiple LEDBAT-like protocols
There are multiple "lower than best effort" protocols in the wild that seems relevant (e.g. CDG [1][2], FLOWER [3]) since they consider LEDBAT's issues in their state-of-the art.  Moreover, it is worth pointing out that CDG is in the Linux kernel and has a "lower than best effort" option. You may want to consider them in your evaluations.

- Interactions between LBE and AQM
Authors of [4] and [5] showed that there can be important issues when LBE schemes cohabit with AQM mechanisms. It may be worth considering AQM in your evaluations.

- On the rationale of using fixed target delays
Using 'fixed' target delays does not seem to be a good option if protocols are to somehow be 'network independent' - unless the selected timers are relevant for data-centers and satellite corner cases ?
It may be worth considering various deployment scenarios in the assessment of the proposal.

[1] David A. Hayes, Grenville Armitage (May 2011). Revisiting TCP congestion control using delay gradients.. 10th International IFIP TC 6 Networking Conference (NETWORKING 2011)
[2] Tangenes, Tor Christian, David A. Hayes, Andreas Petlund and David Ros. "Evaluating CAIA Delay Gradient as a Candidate for Deadline-Aware Less-than-Best-Effort Transport." (2017).
[3] Trang, Si Quoc Viet and Lochin, Emmanuel and Baudoin, Cédric and Dubois, Emmanuel and Gelard, Patrick FLOWER - Fuzzy Lower-than-Best-Effort Transport Protocol (2015) In: The 40th IEEE Conference on Local Computer Networks (LCN), 26 October 2015 - 29 October 2015
[4] Y. Gong, D. Rossi, C. Testa, S. Valenti and M. D. Täht, "Fighting the bufferbloat: On the coexistence of AQM and low priority congestion control," 2013 Proceedings IEEE INFOCOM, Turin, 2013, pp. 3291-3296.
[5] https://www.ietf.org/proceedings/93/slides/slides-93-iccrg-2.pdf

Cheers,

Nico