Re: [iccrg] [tsvwg] L4S related activity in 3GPP

"Holland, Jake" <jholland@akamai.com> Sat, 09 November 2019 22:45 UTC

Return-Path: <jholland@akamai.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 C63601200E5; Sat, 9 Nov 2019 14:45:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 3tJ79KPgYKeu; Sat, 9 Nov 2019 14:45:10 -0800 (PST)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (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 C767A120058; Sat, 9 Nov 2019 14:45:10 -0800 (PST)
Received: from pps.filterd (m0122331.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id xA9Mf8K9023040; Sat, 9 Nov 2019 22:44:57 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=f0O9DJsQkUu91qaxo6Qh8A/6tPqrPDoZg8Xqf3szttY=; b=GyhtiQyenPnTA/jOajyMz1lCwlXr8Mo7Wjh1yYHrWYyQyvwiE0ejzNxQQnVZgkoIMchC i5v0VkTQQiYHqwGSFkoxdhlG3CZFzL72gucJgsMt9e8qEonk4JtTm0enRAqszQySDpBR gRLGvsyfnB9l7hOTQ7HkaV1fd3FyWY+lttOGzYma3XPW27fBl7P5vfQ2uXdw03jf1OdG 66Y3g7Tmozobe/xCTH9fSzg9PIf8ew6TR75CNA0DS2A9gGNZ6wvvS1dyNwUzRuFtBSL5 D3fCcq5/hbHjAMOIlUHoxGiMeDrdrkMZXJn+FiHqui30V0J2ijPvbumDvfOU6V3zf1Yk Dg==
Received: from prod-mail-ppoint4 (prod-mail-ppoint4.akamai.com [96.6.114.87] (may be forged)) by mx0b-00190b01.pphosted.com with ESMTP id 2w5p6djufw-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 09 Nov 2019 22:44:57 +0000
Received: from pps.filterd (prod-mail-ppoint4.akamai.com [127.0.0.1]) by prod-mail-ppoint4.akamai.com (8.16.0.27/8.16.0.27) with SMTP id xA9MWjb1023915; Sat, 9 Nov 2019 17:44:56 -0500
Received: from email.msg.corp.akamai.com ([172.27.165.116]) by prod-mail-ppoint4.akamai.com with ESMTP id 2w5sp2sjpv-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Sat, 09 Nov 2019 17:44:56 -0500
Received: from USTX2EX-DAG1MB4.msg.corp.akamai.com (172.27.165.122) by ustx2ex-dag1mb6.msg.corp.akamai.com (172.27.165.124) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sat, 9 Nov 2019 14:44:55 -0800
Received: from USTX2EX-DAG1MB4.msg.corp.akamai.com ([172.27.165.122]) by ustx2ex-dag1mb4.msg.corp.akamai.com ([172.27.165.122]) with mapi id 15.00.1473.005; Sat, 9 Nov 2019 16:44:55 -0600
From: "Holland, Jake" <jholland@akamai.com>
To: Ingemar Johansson S <ingemar.s.johansson=40ericsson.com@dmarc.ietf.org>, Sebastian Moeller <moeller0@gmx.de>
CC: "tcpm@ietf.org" <tcpm@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "iccrg@irtf.org" <iccrg@irtf.org>, Ingemar Johansson S <ingemar.s.johansson@ericsson.com>, "koen.de_schepper@nokia.com" <koen.de_schepper@nokia.com>
Thread-Topic: [tsvwg] L4S related activity in 3GPP
Thread-Index: AQHVlyEOqflbeAGZskqQkrD3bd7kSaeDnOaA//+x64A=
Date: Sat, 9 Nov 2019 22:44:54 +0000
Message-ID: <764B1E43-7B86-4BAE-9FA2-CA5B56A73047@akamai.com>
References: <HE1PR07MB4425A148B5BB1E6FD8E5A3FBC27A0@HE1PR07MB4425.eurprd07.prod.outlook.com> <2083E62F-0E6D-40B1-B726-A198BFA36220@gmx.de> <HE1PR07MB4425DD6FE15DB130B24BCEA1C27A0@HE1PR07MB4425.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR07MB4425DD6FE15DB130B24BCEA1C27A0@HE1PR07MB4425.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1e.0.191013
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.80.233]
Content-Type: text/plain; charset="utf-8"
Content-ID: <46FEED6D1AD1464C949A3943206DFF0D@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-11-09_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=737 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1910280000 definitions=main-1911090231
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572 definitions=2019-11-09_09:2019-11-08,2019-11-09 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 adultscore=0 lowpriorityscore=0 bulkscore=0 malwarescore=0 priorityscore=1501 impostorscore=0 phishscore=0 mlxscore=0 mlxlogscore=691 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000 definitions=main-1911090232
Archived-At: <https://mailarchive.ietf.org/arch/msg/iccrg/CeiAO6ASnvRWlh7ZzWMAXNhmCZY>
Subject: Re: [iccrg] [tsvwg] L4S related activity in 3GPP
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: Sat, 09 Nov 2019 22:45:12 -0000

On 2019-11-09, 11:24, "Ingemar Johansson S" <ingemar.s.johansson=40ericsson.com@dmarc.ietf.org> wrote:
> One being that it can enable congestion control algorithms to
> quickly grab free capacity. 5G access can have large variations
> in link throughput for example related to dual connectivity and
> L4S can be helpful here as well.

Hi Ingemar,

Not sure how closely you've been following, but the L4S team recently
reported fixing a bug in their implementation that might change this
conclusion, and you probably should be aware of it if that's part of
the driver here.  Specifically the alpha was set to 1 instead of 0.
https://l4s.cablelabs.com/

Changing this to avoid some problematic behavior also causes a  more
gradual throughput ramp instead, so you might want to re-test your
conclusions about how fast it can converge on the fluctuating capacity
after that bug-fix is applied.

The charts show some example differences on startup throughput (along
with the problematic RTT response that was fixed by this).

With the fix:
https://l4s.cablelabs.com/l4s-testing/key_plots/batch-l4s-s6-1-prague-50Mbit-80ms_var.png

Without the fix:
https://l4s.cablelabs.com/l4s-testing/key_plots/batch-l4s-s6-prague_alpha-prague-50Mbit-80ms-alpha0_var.png

Cheers and HTH,
Jake