Re: [tsvwg] Fwd: Qs on your 5G L4S slides

Ruediger.Geib@telekom.de Tue, 16 March 2021 08:12 UTC

Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C89B3A1D40 for <tsvwg@ietfa.amsl.com>; Tue, 16 Mar 2021 01:12:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.345
X-Spam-Level:
X-Spam-Status: No, score=-2.345 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.248, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
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 K9U0OKDQTzmw for <tsvwg@ietfa.amsl.com>; Tue, 16 Mar 2021 01:12:20 -0700 (PDT)
Received: from mailout41.telekom.de (mailout41.telekom.de [194.25.225.151]) (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 65CE03A1D3E for <tsvwg@ietf.org>; Tue, 16 Mar 2021 01:12:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1615882339; x=1647418339; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=lOeNy7qotitYdTxAYnuxd6hfJkPJ7U+XSb6UhaA2bD8=; b=FQZyHc9lNFUAp2Hsa9YIgrZfiWzK2alS28BEbskDo2A6O2MXNjxm4ZuF 2+89HFylReBJnkSc6H5ArCNXnFZzkPbT+Hq26ImRiDasXYickqUFjXBm2 a3Y+3iAJth7yeBPJHO7kRZsILVszkRg4wIKmAoLxizWYQe/DDanQLPvR1 jDZHqQTE+0AgBDGjlj6l80TOHWrZxxDQ/hmOPs9MLmpKrLW9fry4vzCwR 50mIAoOHIHKD6tmbU75PXR2lVzfrkcsB9C590pZzudUN9Z9ILAJq1lCgy jABo4r5n958xc1PlfHWjVYFCnTNjk8biTcOddxB5M+8PCWAOz9iyGzqUl w==;
IronPort-SDR: pqZZU839ziX011FoVBhD4CORIrNAmrDLYUteiW6D6o806HEGggrbWqkMcyWZRUQ9NhaajiVAxJ MIFQjIHANbgg==
IronPort-HdrOrdr: =?us-ascii?q?A9a23=3A4nHvB6sT8auJntD0fdF0Utt87skCC4cji2?= =?us-ascii?q?hD6mlwRA09T+WxrOrrtOgH1BPylTYaUGwhn9fFA6WbXXbA7/dOkOssFJ+Ydk?= =?us-ascii?q?3DtHGzJI9vqbHjzTrpBjHk+odmpMRdWoBEIpnLAVB+5Pyb3CCRGdwt2cTC1a?= =?us-ascii?q?iui/vXwXsFd3AaV4hLxW5Ce3+mO2dxQxRLAod8MZKa6NZOqTbIQwVmUu2QAH?= =?us-ascii?q?4ZU+/f4+DajZ6OW29HOzcL4BSD5AnYlYLSPAOf2n4lIlRy6JcktVPIignoop?= =?us-ascii?q?ik2svLtCP093TU6K1Rg8ak8PZ5bfbmtuEwChHBzjmlf55gXbrqhkF3nMiK5E?= =?us-ascii?q?wxmNfB5zcMVv4Dl0/5RW2+rRvz1wSI6l9HhxCNqC788B/eiPf0Sz4gB81KiZ?= =?us-ascii?q?gxSGqn12MasMxhy6UO5mqFtvNsfE79tR7g7NvFXQwCrDvNnVMekPUeh3EacY?= =?us-ascii?q?wSZK45l/1kwGppEYwNFC+/1YY/EOMGNrCm2N9qdzqhHhbkl1gq4MerWU00BQ?= =?us-ascii?q?rDandqgKao+gkTuF5Qi1EFz8gehG0B8pVVcfR5ztWBFp4tuKBFT8cQY644Lv?= =?us-ascii?q?wGW9GLBmvERg+JGH6OIHz8fZt3eU7lmtrS2vEY9euqcJsHwN8Zg5LaSm5Vsm?= =?us-ascii?q?Y0ZgbHFdCO5ptW6RrAKV/NGAjF+4V73dxUq7f8TL3kPWmoU1Y1ifatpP0ZH4?= =?us-ascii?q?n9V+usPolVR9vuN3HnF4oM/wCWYegXFVAuFOku/vorUVOHpczGbqfwsPbATf?= =?us-ascii?q?rVLL3xVTk+XGfyBWYCQSjzKM1M4lvDYA6/vDHhH1fWPmDv95N5F6bXu8IJzp?= =?us-ascii?q?IWC4FKug8JzVS1j/v7cAFqg+gTRg9TMbnnmqS0qS2d5mDT9VhkPRJbEwJQ6L?= =?us-ascii?q?XkWHVauB8SPyrPAO4+kuTaXVoX8GqMJxd5Qc+TOhVYvU5L9aW+KIHVwzsjBd?= =?us-ascii?q?KhOmeTlGASu3qOUpcZlsS4lIDYU6J9KqxjdL16FA3NGRAwsx1tsn1/ZAgNQV?= =?us-ascii?q?KaCinjkry/jJsfBPjWct51hAvDG78OlVvv8WGn4e0/THoSWDCjFfONiQE1Xj?= =?us-ascii?q?xOmxla6KkEmoeNnj6pNEoyiOk1K0d3dWySGb5KZT71Prl8q/TOQkVQRX3PrS?= =?us-ascii?q?GGgxszE1CahHk6tyjEF2moXt3lRnBaoWtV16729kgcTBTuQ2tALlZgsYN8Em?= =?us-ascii?q?zavG1UyuHjXNvt70KhLmYnhts7DQuAWx8uG2pVtoyK/RaIhTePEmgnzJ0yPu?= =?us-ascii?q?rbSK8uaa3Xx2nFEvz8qYgWW/BT55prL9bor6sCVv+eYRacKHfiB/ouwBH9nA?= =?us-ascii?q?drBABk7H0lm+jvwhvr8Syx22M+G+PbJD1dNvwmCsDZ62jvXPCT1pplydozoO?= =?us-ascii?q?urK230LtqL07veYTIGKhTdpweNPq0VgIERuaI5r71oGZbHFTPOyXFcxR07aN?= =?us-ascii?q?7ui1l2etUy3JnRfot0O8ACcSNQ+VQk0NyJMUswqwTzRuszZ0skgXPXN86Aio?= =?us-ascii?q?C454YHEwmEvk/9KFOf+ypS87PeUyyP2aUTBqgwLW5VAXJMokhK7aeHbcndGQ?= =?us-ascii?q?+qf+ZM8B6mKXe7aqZaU7XAFrMKrBp2iuv43tO/Zm79wkTXsjR6KK4VrDriTs?= =?us-ascii?q?O2HQ6WGelHt9a9Ik+Bh6O24Mi1yDf7IAHLHXgwlMlAbwgXaM8GlzwpyIsw2S?= =?us-ascii?q?K2Qrbsok0kn0BFiAsX3WLFy8yj+iPDAUpCMQfFmZ1YUjlYL2iQga3+gJ+l/W?= =?us-ascii?q?W45CIAxILKG0hRdMxfAtQcToD4KCF1NMgb1YTYtpYHk2BEexchD2k1lTD70a?= =?us-ascii?q?dnxN6CqYHvZ9E=3D?=
Received: from qdefcs.de.t-internal.com ([10.171.254.41]) by MAILOUT41.dmznet.de.t-internal.com with ESMTP/TLS/ECDHE-RSA-AES128-GCM-SHA256; 16 Mar 2021 09:12:15 +0100
IronPort-SDR: sYnFmkUP4L5ba1jb5IQx7TrwyY2TFTpOpm7YaICDa6WQem4tGio6/HJh02sBVj2aNExPaRQwFN 8wWo++1+Ffx2mk+fC7WByeW+xXf5iN+j8=
X-IronPort-AV: E=Sophos;i="5.81,251,1610406000"; d="scan'208,217";a="299055728"
X-MGA-submission: =?us-ascii?q?MDFqTb/UzpfqLUzf23lFuU5w6XV4Lx9NUC53is?= =?us-ascii?q?aGHwJ7RflwAVYKs/s4VciWVWmysjM/EAVreMlIpMNgIQhQHU/MCS1dn2?= =?us-ascii?q?o9qiFV7SX5uEK554UV9YWplLmIxY8wd2VxlYc9aGPb95gU7Nm9qhnWDa?= =?us-ascii?q?AdI6fOiXkvLAp0e+RTvTAsVQ=3D=3D?=
Received: from he105716.emea1.cds.t-internal.com ([10.169.118.52]) by QDEFCV.de.t-internal.com with ESMTP/TLS/ECDHE-RSA-AES128-SHA256; 16 Mar 2021 09:12:16 +0100
Received: from HE105716.EMEA1.cds.t-internal.com (10.169.118.52) by HE105716.emea1.cds.t-internal.com (10.169.118.52) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 16 Mar 2021 09:12:14 +0100
Received: from HE104160.emea1.cds.t-internal.com (10.171.40.36) by HE105716.EMEA1.cds.t-internal.com (10.169.118.52) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Tue, 16 Mar 2021 09:12:14 +0100
Received: from DEU01-FR2-obe.outbound.protection.outlook.com (104.47.11.177) by O365mail03.telekom.de (172.30.0.232) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 16 Mar 2021 09:12:12 +0100
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=dOUKOSMH9qAP7b/+gP8b/mNEgo7yD7OhR2Bm429urZzPiatLceIIrHzvRMOrP45w5oRCdchkLm2fFWgkdWsL8lofYLsi66dSj6yrrXs6XPJ/osZ/K5Yh2nUhll7LeFiAJkZzxsuNZpJkLdi//lymtG+vVsJ4iJAecZL6lGoZiQXOHlSiCiirIRHDX9qUX9JuzjuWmykjXfZCx3BCGyxv3+Pl6OqJT1qW5tFDFr/yCF9zio+/ijPYSVIhRchJPUoB8pCAYhb0b+eiOWx2+L6W2X9LZdGqYsORXQ/thPq4nzhdabXn/umWPrug/Mobxypujzv6LNQPshC8qUz28i+9Bw==
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=lOeNy7qotitYdTxAYnuxd6hfJkPJ7U+XSb6UhaA2bD8=; b=EH+HKWF6tzlFpPX9I36nPK4e/kjj8nMeZNGSbDjx1Sx0YSgnR0Pv7TgY7ooHM1I+HycwiEsbh/dPe70k4op4QLh80QMTdHzjVlb0zoaoSqakhzwgzadXrR01T+Ej2TChI5JjLakXWwqsmCkP+kWq81cQ9hz69vH3t6NwCTYKlz+Mkj88sVUI6v/iE75iGfcr+FncsH5uqQaeFCcDLotb5hh62AL/4JxkRtJQfWKTOBAkaR2Mqi7kr4EKFwDktq+Iwt7xvzpD2Nc3doOMz31Q5wqolhiLLIimqoargvM9GpR3CvaltXx2i0IkbHFEbfPJxMLNSMoWaFJrgviigBYllg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=telekom.de; dmarc=pass action=none header.from=telekom.de; dkim=pass header.d=telekom.de; arc=none
Received: from FRYP281MB0112.DEUP281.PROD.OUTLOOK.COM (2603:10a6:d10:2::11) by FRYP281MB0030.DEUP281.PROD.OUTLOOK.COM (2603:10a6:d10:2::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3955.13; Tue, 16 Mar 2021 08:12:01 +0000
Received: from FRYP281MB0112.DEUP281.PROD.OUTLOOK.COM ([fe80::e40f:c4ab:db76:e885]) by FRYP281MB0112.DEUP281.PROD.OUTLOOK.COM ([fe80::e40f:c4ab:db76:e885%3]) with mapi id 15.20.3955.011; Tue, 16 Mar 2021 08:12:01 +0000
From: <Ruediger.Geib@telekom.de>
To: <ietf@bobbriscoe.net>, <g.white@CableLabs.com>
CC: <Kevin.Smith@vodafone.com>, <tsvwg@ietf.org>, <ingemar.s.johansson@ericsson.com>
Thread-Topic: AW: [tsvwg] Fwd: Qs on your 5G L4S slides
Thread-Index: AQHXFbPMumpcTzhMykiML1sdSgFD76p9PKwAgABBFQCAAuW6gIAEZCywgAAYqPCAAAeooIAABEBggAB0GQCAAN/foA==
Date: Tue, 16 Mar 2021 08:12:01 +0000
Message-ID: <FRYP281MB011207C06C3E2B1013CBAA8E9C6B9@FRYP281MB0112.DEUP281.PROD.OUTLOOK.COM>
References: <HE1PR0701MB22994BB36811BDAB98F464B9C2919@HE1PR0701MB2299.eurprd07.prod.outlook.com> <4cf84500-756f-9da9-81d2-b29e1aebad4a@bobbriscoe.net> <AM7PR05MB7090AB2C98F6EA6328DCFB75916F9@AM7PR05MB7090.eurprd05.prod.outlook.com> <HE1PR0701MB2299229839CFE56847FCAD2FC26C9@HE1PR0701MB2299.eurprd07.prod.outlook.com> <FRYP281MB0112A5CDAEFD57D3E935904C9C6C9@FRYP281MB0112.DEUP281.PROD.OUTLOOK.COM> <HE1PR0701MB2299F09181D3D4C9E150E3C5C26C9@HE1PR0701MB2299.eurprd07.prod.outlook.com> <FRYP281MB0112291B8CF0E0745660D8D59C6C9@FRYP281MB0112.DEUP281.PROD.OUTLOOK.COM> <2a79bd1d-dae9-6e91-55ee-0af586527fbd@bobbriscoe.net>
In-Reply-To: <2a79bd1d-dae9-6e91-55ee-0af586527fbd@bobbriscoe.net>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: bobbriscoe.net; dkim=none (message not signed) header.d=none;bobbriscoe.net; dmarc=none action=none header.from=telekom.de;
x-originating-ip: [87.147.145.163]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 913e920c-82ea-4c62-ad20-08d8e8532d7e
x-ms-traffictypediagnostic: FRYP281MB0030:
x-microsoft-antispam-prvs: <FRYP281MB003058E6EC7FF911B8DD22779C6B9@FRYP281MB0030.DEUP281.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:1051;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: H8kO4TPHLpQ93VBz0Q8Gtg4SSk9IbZesRL3ZYV5o5f2DaeEMpNyl8wUi30cEhGGuXLOkTSJRXzYAx2P2RbyqQpW9syXqQr3gEqCWSt5xl/fqiFVyPqI5s9ZpZ6NTaAH1Gc4zT+ir++CNYoVy6WAxKgScs8fpuURndgB9HoYdYWf4zJSqwLpcnKuYANvyXXIu6SMEofHhhlWwQW76Nf7diLsileD8XNfPixShYBsF+q1Ff3OYFVoBbFXctFoJPXyfPSkMUA0s+OXPS3uGlCWJw79bHAEIvNSlvYuA0GL47CmKdGTqI7JZESgVzTWkRtsG86Jcq00fu4w/KmK1+bbQpoa1KJcz4sdCVFZfGDnON1M2LkY0qWs3RB+yHg5prBfb59XjjqdVITtiBed/K34ClI2gQV/5U43asLI5JXI+USpxuK3jiq5FCn8fvItYy0BCKl0TAcxlZt47XAX0+Pwk353r6us4q7X/iyAl7COgsrzqLFhh0tjnMZpA6s0fHkwfmdYfH4sUxeny8BiChBsXJgiKOD4oUlCIHVk7GqiFvizSGXzTRKJgaqBp1de8WWXJOANAet1Dlu0TX2OjirfTb5DQBmqp6csgMO5hLTODfDE=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:FRYP281MB0112.DEUP281.PROD.OUTLOOK.COM; PTR:; CAT:NONE; SFS:(39860400002)(346002)(396003)(366004)(376002)(136003)(66574015)(166002)(83380400001)(2906002)(30864003)(8676002)(6506007)(186003)(110136005)(66446008)(316002)(54906003)(71200400001)(478600001)(966005)(66556008)(53546011)(8936002)(33656002)(66476007)(7696005)(55016002)(5660300002)(66946007)(26005)(76116006)(4326008)(64756008)(52536014)(9686003)(86362001); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: dW8obszH5bPErY4RVpAXiwPFb3V/JSlrqgXh2m7SCOWGHyf7XiIUFZzyJ/8pS29IzpLRLDjJbUfvK9MW7Q+HTaEXd2ca+A7DSRIfYDdyM9zyEn5rsylUKeDh7W2twVQb8Tyt3imc+af1oX7w2cnW+HVWjHaBszl0z9mtihTZIDMVgMWXCgC2ZrDE7iFlUf2HU51N+XiIEH6PRNraNy0gnEFe4SYN5NrjD30YMMsnNOLa82jIfjhGoxL+IlPYcfRd2vmHLCOrOOvZHWkSIxQfktK+CnFMK1cP/MtTko5krnkIny05/xqLQzjlt6ZwQ6PllDJwPNnSXqt4BhOoCRGVl2HeuE+3wjN51nhE4sBEusYLDg4ssek8ichGcTj2UfgDV4nu8fMmhTOrGXc7y6N4fknvB0eDBiBd7DRv3gt78LEVDoGiXv8ZZb6vVbIGByETZg+RkcamZOzvuLQpVNk0myi8iW/9NM3Kx5m5Gt7XoOu9mwKsK/TGmsYXTQ+BIDaNmW5GxX+ehYn2XYaGechBVDoRARHpBVY0ksJYYRfhFOpp1qySW0XPMwX1AhWjI+JLDIIMzhvnY2vVqzU2kP9pvkRUCMTpIGbbYZ2ndTQi6hZPklSqSsanLf8u8CqXGHwxF/UmKQpJIHmDX919bTaBTanQ3u8Z+qqsPBxrn8aPAQcjU4rwQbsVYz7pKVIHwhNb63IIwZNUz2Df7/f///w/9Vpxs5IMk/BoSFq7/sSsIc8=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_FRYP281MB011207C06C3E2B1013CBAA8E9C6B9FRYP281MB0112DEUP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: FRYP281MB0112.DEUP281.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 913e920c-82ea-4c62-ad20-08d8e8532d7e
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Mar 2021 08:12:01.5145 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: EDDDD/guZX5Q96jmzRSsreNOxG36tbBPNxPetEDESdXRsdsidd0sCiwonI/SZ6Y0XWl/gm5Yrk7x8DMOlHsT2IujyxqxC/eNJ6hf8/DHtjo=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: FRYP281MB0030
X-TM-SNTS-SMTP: 481BDD6FE26D439B5BE4951FAB78C934A98AFE4A63C0F36EB4E812A20EA7B8CF2000:8
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/b3a4ejLx3KzmMp3QTl8hMAcY40c>
Subject: Re: [tsvwg] Fwd: Qs on your 5G L4S slides
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Mar 2021 08:12:24 -0000

Bob, Greg

Thanks Bob, I'm having a clear perception. I appreciate that work is being done to implement an L4S WiFi scheduler by one vendor. An L4S scheduler is a requirement for all kinds of wireless access, I think.

I'm also having a clear perception about the fairness resulting if a classic transport flow scheduled default on a WiFi access competes with L4S being scheduled priority. While I understand that L4S won't perform as desired, if scheduled default on WiFi under adverse operational conditions, it's not a good idea to solve that issue by scheduling L4S by priority on WiFi. I however note that NQB PHB can support also non-L4S traffic and L4S and NQB don't have to be linked.

Having read also Greg's response, I'd like to add that the Home-Gateway market in Germany is deregulated and any WiFi scheduler configuration which isn't implemented by all vendors serving this market will best be expected absent. That is to say, no IETF standard should specify an undesired behaviour. Deutsche Telekom is able to control BNG policies and L4S might be relevant there, but as WiFi is customer premises, an IETF standardized NQB DSCP shouldn't result in a fair chance to busy the hotline. Looking at this market environment, Bob's statement applies in general, L4S requires appropriately adapted scheduling from BNG to Terminating Equipment, and prior art won't do. That's a long way to go.

Regards,

Ruediger

Von: Bob Briscoe <ietf@bobbriscoe.net>
Gesendet: Montag, 15. März 2021 19:06
An: Geib, Rüdiger <Ruediger.Geib@telekom.de>de>; ingemar.s.johansson@ericsson.com
Cc: Kevin.Smith@vodafone.com; tsvwg@ietf.org
Betreff: Re: AW: [tsvwg] Fwd: Qs on your 5G L4S slides

Ruediger,

==DOCSIS==
Whoa! NQB is not L4S traffic. NQB is a Diffserv codepoint. L4S is identified by the ECN field. In DOCSIS the NQB Diffserv codepoint classifies into the /same queue/ as L4S traffic (renamed the Low Latency queue due to its dual role). Allowing in unresponsive traffic was only considered in DOCSIS because there was already a sufficient policing function in front of the queue (per-flow queue protection).

==Mobile==
If a mobile operator (or in this case a masters student), uses the ECT(1) codepoint to classify traffic into a priority bearer, then it's not L4S. It's an ECN codepoint intended for L4S but used (abused?) in a Diffserv priority scheduler.

The problem that the DualQ Coupled AQM solved was how to isolate low latency flows without having to know how much bandwidth to set aside for them. So if there are M L4S flows and N Classic flows, M and N can take any value, including zero. That's because the coupling makes the two queues appear as one - from a bandwidth and congestion control perspective (approximately).

So, if you have a Diffserv scheduler and no L4S mechanism, you would need to go back to using traditional Diffserv techniques like guessing what M and N might be most of the time, to decide how much bandwidth to configure for a separate priority queue, then policing it.

To summarize, the answers to your question:

The underlying question is, to which extend does the end-to-end performance of L4S depend on suitable radio schedulers coupling two congestion control algos or queuing behaviours, like L4S standardises for fixed line schedulers. And how to operate a network, if these are absent.

An operator that wants to support any technology without deploying the technology isn't going to get very far! L4S depends on using an L4S mechanism (obviously), specifically the DualQ Coupled AQM (or FQ). How to operate a network if L4S is absent - well, you go back to what you had before. But then you can't support applications that need consistently low latency /and/ the full available bandwidth, which is the point of L4S.


==WiFi==
You say that the NQB draft "specifies mapping L4S to a priority bearer based PHB". This is because NQB is having to cope with the WiFi situation as it finds it. It's not ideal, but you'll see below how it could evolve to something better.
I understand that the video access category (AC_VI) was the only choice that offered decent enough latency without excessive bandwidth priority. NQB just needs to be isolated from bursty traffic - it didn't choose AC_VI because of any need for /bandwidth/ priority, per se. NQB should work with quite weakly weighted priority as long as it's isolated. But that wasn't available in current WiFI.


L4S is also walking into the WiFi environment as it finds it. With today's non-L4S products, I would also recommend that the L4S-ECN codepoints are mapped to the video access category, if possible.
Nokia's latest WiFi products (in the 'Beacon' range) already include an L4S DualQ Coupled AQM. And as other L4S WiFi products come out, the coupling will introduce the recommended congestion signals that can be used as back-pressure against the priority scheduler. Users don't want to abuse scheduling priority at the expense of the balance between their own applications. But they have no choice until there's a mechanism that allows their applications to balance against other apps.

Finally, once there's an L4S queue in WiFi kit, NQB traffic could be classified into it, as was done in DOCSIS.

FQ offers an alternative path for WiFi - neither precludes the other.

Does this help explain?


Bob
On 15/03/2021 11:19, Ruediger.Geib@telekom.de<mailto:Ruediger.Geib@telekom.de> wrote:
Hi Ingemar,

I'm not having trouble with wireless default scheduling. I'd favour the development of a DiffServ scheduler on packet layer combined with a default scheduler below. It seems to me that 3 GPP choose different approaches for 4G and 5G.

I wonder which scheduling was recommended for 3GPP access types, if there's an RFC recommending a priority bearer for L4S at WiFi interfaces.

Regards,

Ruediger

Von: Ingemar Johansson S <ingemar.s.johansson@ericsson.com><mailto:ingemar.s.johansson@ericsson.com>
Gesendet: Montag, 15. März 2021 12:08
An: Geib, Rüdiger <Ruediger.Geib@telekom.de><mailto:Ruediger.Geib@telekom.de>
Cc: Kevin.Smith@vodafone.com<mailto:Kevin.Smith@vodafone.com>; ietf@bobbriscoe.net<mailto:ietf@bobbriscoe.net>; tsvwg@ietf.org<mailto:tsvwg@ietf.org>; Ingemar Johansson S <ingemar.s.johansson@ericsson.com><mailto:ingemar.s.johansson@ericsson.com>
Betreff: RE: [tsvwg] Fwd: Qs on your 5G L4S slides

Hi Ruediger

I can't really comment on how this is handled for WiFi. But I also notice that DOCSIS has a mechanism that demotes misbehaving L4S flows into a classic queue.

For 3GPP access already L4S with default bearers gives quite some improvement.
The use of L4S with priority scheduling can enhance performance even more but poses some additional concerns, where the use of a DBS scheduler is one extreme in this context. There are other alternatives such as increased scheduling weight that has a more limited impact on other traffic that runs on default bearers.
But this problem is not unique to L4S. You would face the same issue with e.g., GBR bearers for the cases where an endpoint gets in bad coverage. Additional methods can be needed here to avoid that one bearer gets unduly large share of the radio resources.

/Ingemar

From: Ruediger.Geib@telekom.de<mailto:Ruediger.Geib@telekom.de> <Ruediger.Geib@telekom.de<mailto:Ruediger.Geib@telekom.de>>
Sent: den 15 mars 2021 11:48
To: Ingemar Johansson S <ingemar.s.johansson@ericsson.com<mailto:ingemar.s.johansson@ericsson.com>>
Cc: Kevin.Smith@vodafone.com<mailto:Kevin.Smith@vodafone.com>; ietf@bobbriscoe.net<mailto:ietf@bobbriscoe.net>; tsvwg@ietf.org<mailto:tsvwg@ietf.org>
Subject: AW: [tsvwg] Fwd: Qs on your 5G L4S slides

Hi Ingemar,

That depends. For WiFi, draft-ietf-tsvwg-nqb-05 specifies mapping L4S to a priority bearer based PHB. Then this stops to be an L4S problem. I'd like to be clear about that issue and the question is, whether there will be a recommendation to assign L4S traffic to a 4G or 5G priority bearer. If your answer is no, why is there a draft specifying a priority bearer for WiFi L4S traffic?

The underlying question is, to which extend does the end-to-end performance of L4S depend on suitable radio schedulers coupling two congestion control algos or queuing behaviours, like L4S standardises for fixed line schedulers. And how to operate a network, if these are absent.

Regards,

Ruediger

Von: tsvwg <tsvwg-bounces@ietf.org<mailto:tsvwg-bounces@ietf.org>> Im Auftrag von Ingemar Johansson S
Gesendet: Montag, 15. März 2021 10:55
An: Smith, Kevin, Vodafone Group <Kevin.Smith=40vodafone.com@dmarc.ietf.org<mailto:Kevin.Smith=40vodafone.com@dmarc.ietf.org>>; Bob Briscoe <ietf@bobbriscoe.net<mailto:ietf@bobbriscoe.net>>; tsvwg IETF list <tsvwg@ietf.org<mailto:tsvwg@ietf.org>>
Betreff: Re: [tsvwg] Fwd: Qs on your 5G L4S slides

Hi Kevin, Bob + others
CC Davide (thesis author)

Yes, there was a test with the use of the dedicated bearer (DBS) and no-L4S. This is exemplified in section 5.3.6 in the thesis report. In short the outcome is that the background traffic will be severely affected. The reason is that the DBS scheduler (originally devised for e.g. VoLTE) prioritizes a bearer when the queue delay exceeds a given low threshold (e.g 10ms). And because SCReAM without L4S targets larger queue delay, the outcome is that it will hog an unreasonable share of the available resourses.
What this means is that it is necessary to use some extra guard mechanism when prioritized bearers are used, but this is of course not only an L4S problem.

/Ingemar

* http://www.diva-portal.org/smash/record.jsf?pid=diva2%3A1484466&dswid=-2512


From: tsvwg <tsvwg-bounces@ietf.org<mailto:tsvwg-bounces@ietf.org>> On Behalf Of Smith, Kevin, Vodafone Group
Sent: den 12 mars 2021 14:56
To: Bob Briscoe <ietf@bobbriscoe.net<mailto:ietf@bobbriscoe.net>>; tsvwg IETF list <tsvwg@ietf.org<mailto:tsvwg@ietf.org>>
Subject: Re: [tsvwg] Fwd: Qs on your 5G L4S slides

Hi Ingemar,

Just to ask, was there also a variant of the test with no L4S but with the dedicated bearer? I'd be interested to see that comparison.

@Bob, regarding UPF placement: the ability to virtualise network functions in 5G Core allows easier scaling of UPFs as required.

All best,
Kevin





C2 General
From: tsvwg <tsvwg-bounces@ietf.org<mailto:tsvwg-bounces@ietf.org>> On Behalf Of Bob Briscoe
Sent: 10 March 2021 17:41
To: tsvwg IETF list <tsvwg@ietf.org<mailto:tsvwg@ietf.org>>
Subject: [tsvwg] Fwd: Qs on your 5G L4S slides

CYBER SECURITY WARNING: This email is from an external source - be careful of attachments and links. Please follow the Cyber Code and report suspicious emails.
tsvwg,

Fwd'ing to list, with permission...
In case anyone else had the same questions


-------- Forwarded Message --------
Subject:
RE: Qs on your 5G L4S slides
Date:
Wed, 10 Mar 2021 14:33:42 +0000
From:
Ingemar Johansson S <ingemar.s.johansson@ericsson.com><mailto:ingemar.s.johansson@ericsson.com>
To:
Bob Briscoe <research@bobbriscoe.net><mailto:research@bobbriscoe.net>
CC:
Ingemar Johansson S <ingemar.s.johansson@ericsson.com><mailto:ingemar.s.johansson@ericsson.com>


Hi
Please see inline [IJ]

/Ingemar
-----Original Message-----
From: Bob Briscoe <research@bobbriscoe.net><mailto:research@bobbriscoe.net>
Sent: den 10 mars 2021 14:46
To: Ingemar Johansson S <ingemar.s.johansson@ericsson.com><mailto:ingemar.s.johansson@ericsson.com>
Subject: Qs on your 5G L4S slides

Ingemar,

#5 "Dedicated bearer / QoS flow for L4S traffic"
Is this a per-app microflow or a per-user flow?
[IJ] It is per-user flows, i.e each bearer can handle many flows

And I think you'll need to explain where the UPF is typically located. I believe
it's close to the edge, isn't i?
Further into the network (beyond the UPF) these flows just become an
aggregate of all the users.
[IJ] The UPF is close to the edge somehow, it is hard to say for certain where they are located, they can be real close to the base stations or >100km away.

#6 Question:
Do you have any feel for qDelay & throughput if a "Classic ECN AQM" like PIE
or CoDel was used?
[IJ] No, it was not studied in the master thesis work.

#6 - #11:
Is the DBS scheduler between users, or between flows?
[IJ] Per user (bearer)

#12: L4S is meant to greatly reduce the throughput-delay tradeoff, and in our
results it did.
Any idea why not here? I guess, with video, it's the 'getting up to speed' fast
problem (that I'm working on with Joakim).
[IJ] One reason is the large variation in frame sizes that video coders generate.
Another is that SCReAM paces out the video frames as 50% higher rate than the nominal video target bitrate. This pacing overhead can be configured lower but then the video frames (RTP packets) are more likely to become queued up in the sender instead. I really believe that it can be done better, was hoping to have time to improve SCReAM in this respect but the work hours fly in other directions .
With that said. Also a DCTCP flow (with L4S) marking will get a reduced throughput compared to e.g a Cubic flow (without L4S) over cellular. The reason is that the large buffers with Cubic absorb the fast fading dips in LTE and NR. With DCTCP + L4S some extra headroom is needed to avoid queue build up.


Bob

--
__________________________________________________________
______
Bob Briscoe https://protect2.fireeye.com/v1/url?k=828d3ddc-
dd1604f1-828d7d47-8692dc8284cb-1ab58b5eb7943901&q=1&e=b0160f51-
6418-41ea-9221-efaca6b7cec8&u=http%3A%2F%2Fbobbriscoe.net%2F




--

________________________________________________________________

Bob Briscoe                               http://bobbriscoe.net/