Re: [tsvwg] plan for L4S issue #29
Ingemar Johansson S <ingemar.s.johansson@ericsson.com> Mon, 28 September 2020 09:27 UTC
Return-Path: <ingemar.s.johansson@ericsson.com>
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 D8D733A0A69 for <tsvwg@ietfa.amsl.com>; Mon, 28 Sep 2020 02:27:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.3
X-Spam-Level:
X-Spam-Status: No, score=-3.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.2, 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_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=ericsson.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 4k8cHZm5XC8N for <tsvwg@ietfa.amsl.com>; Mon, 28 Sep 2020 02:27:47 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-eopbgr150043.outbound.protection.outlook.com [40.107.15.43]) (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 4195B3A0A4F for <tsvwg@ietf.org>; Mon, 28 Sep 2020 02:27:47 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=CQlE3cCHiXg0cyG1VW3lP3zqe2aZdyM0nCL9gnPmMV4AHGmc0hEU0Xti8dTLn+6LKvMgEPuGmiozm857JEtDKK9V+pywlikz0xeBF+dgFgMUKEU7zO8bhXzNmEkR59ev/H5Y9PvS0BF66DKncMcQvqWBt2QmS1C9/9KVCtOzprjHJzi2eNGVWz0AJ8zqUxEa3YlXTPE6OoDHQX2XDasbN9orVHTt4NwjnuNxNzTbYrQmxNtbBRIpq251dJxdYiJWP9hQSeSXegltvW5WUXE0RdVgp0p5YDUoul5sTNRwbTZowCkS7OH/Qp7hIfifPgaX2WSQyudxIO/be8YNiPyUUQ==
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=GdSbn9yI+cb4Ya305pgq/0lGwYqq1cm8dlyMJNBeEgs=; b=JeDacsK04DSLHc9+xaoiC8jAqYCCxUGdu8lB18plVhUezNCJ0Ew4mO88UQsAeFAougHnCLXW7FkrWPri+oF5/O2X+3R6o5SvVProwOTCgkEyEIBTMiNtua1umecReZy3Tp8Cz/HNvL+6/htXSP4S3Izg6pE6bZYzHVJ40E6yK35fGLY1OsJokqLxMuVnt2DlrZJwzQgJQwD2BWPRq//IZG1h2XwlJrx+cVIzfl2SADCqOMEAuDnBuoVIw4bniRUnQZUTPgrweK1zPU4/xjkR3fEUsREQQ7+38bhPo/jGPWjmNiQcjSmcIkxyrCyC4PxHwQckjTlW9BTv8d0TGbWTIQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=GdSbn9yI+cb4Ya305pgq/0lGwYqq1cm8dlyMJNBeEgs=; b=q4rQ9e26Zy7xQgeP7J3p3yG19Ud0KgC3BGZiDDmN96mYwXin0c6JCYp5XJdjz9GzaDJmVwNjLFND2vb8q9hAJzYecXrNuSRNdCPHKFLRoW97/zio/xfMfRBAHKSvwAg0a0aeqBTdhYSD6r1sS2fJMGfcFGI8I0clYYm1K4xIIwQ=
Received: from HE1PR0701MB2876.eurprd07.prod.outlook.com (2603:10a6:3:56::8) by HE1PR07MB3146.eurprd07.prod.outlook.com (2603:10a6:7:2c::31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.14; Mon, 28 Sep 2020 09:27:42 +0000
Received: from HE1PR0701MB2876.eurprd07.prod.outlook.com ([fe80::a4a1:d6b5:1254:923a]) by HE1PR0701MB2876.eurprd07.prod.outlook.com ([fe80::a4a1:d6b5:1254:923a%11]) with mapi id 15.20.3433.030; Mon, 28 Sep 2020 09:27:42 +0000
From: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
CC: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
Thread-Topic: Re: [tsvwg] plan for L4S issue #29
Thread-Index: AdaVd95MWgOwz22fS0mXaP/Lm4YXZQ==
Date: Mon, 28 Sep 2020 09:27:42 +0000
Message-ID: <HE1PR0701MB2876929767C6813B42460238C2350@HE1PR0701MB2876.eurprd07.prod.outlook.com>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [192.176.1.80]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 8204eb1c-f99d-4cec-e078-08d86390c065
x-ms-traffictypediagnostic: HE1PR07MB3146:
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <HE1PR07MB3146CCA50B8180B04E529BDBC2350@HE1PR07MB3146.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:3968;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: dwL+Pep/+pWrLl/KZxaYy5Kuk45gUWZF1UXE05OOTutqwV8ESDLRZ4cwc9i4N/LFgH6/j89txKis6uFApq/sOQEZSFAYiUbgGQ/3HT7hUvH1JtZB6psvWywmOqvn3UbR0IT9ot351GibpTja3MmASPtR0mtTBmRMccpTgO+F74pUzRlftDpWxrYFpy6Ec1MSVn4aM18shD/khbDQu0S1wy/JVfmL9PHB9xKq2zPytg6xB0pEl+uKA5FMeckhLaNnlhSoz83LrUxST9UHnami2enhwUJD1Wj9JD1X4dBtlqgtihtQfDpmq2dlQPe3ENrLRH6R61xQLtO7+RRU0StLgI7bCzoMmAja8E3nJdWxedKuSF6Al3qvrzqcR/zRVSachsjuiNbNBYbwk7dWWfnZSg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:HE1PR0701MB2876.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(39860400002)(376002)(346002)(396003)(136003)(366004)(9326002)(8936002)(6916009)(478600001)(4326008)(186003)(66446008)(64756008)(66556008)(66476007)(33656002)(316002)(71200400001)(76116006)(66946007)(66616009)(5660300002)(52536014)(26005)(166002)(66574015)(2906002)(55016002)(86362001)(83380400001)(9686003)(6506007)(7696005)(99936003)(107886003)(83080400001)(8676002); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: BUKzAm8r2/X1arRmNiHmEJsxEySNqhA+HO2IvJW++DQ8U9VEd7SCTLX1PQFrnfXkuZ2ZG4uSY3JYvjGsU4BTI0bDFXX3qrAQupIIwr3FbeGKrxCn44Gu6neJgFezeptqoMK2we8Zu68b0wLzgRAI74s0LG+PyOQEVu95Cplge2f8Ah0m0hm9zEA1fzfKj9U5VUedBCbzO8JN+YUOvI+NgGm08/Ny1TY8mL/JcnrRD2snQ9HdlPXzZ88VVWdlCTjkz/O/Zr6orwMiSBtCT2Wbs7EavKzBFk0V0LKPTEqJRo2Nq+XtAz+axOLIT2Bz5PD0cgwrIeeiq4wERM0R8PntJzCIOhmkfKx9X8YXTHJuFGRfIseZnmtzpyPL3a/9ygOnWc2pWVaYn20w6rWkvaEfY9fJYV6PMbelIuJY08kSA4W0ksbJAaRkpfcrPoefzKIOzLPi35zXEMrQTS28lRSB3boY98TLXkq4OlKb/gtMB+129X+mDdjGu41UZz4zHiXFlodtKKR3XM0OzBSSb+jTCOt8Ma/Q/RuzZtTWaG0hvjpwhzSJJjmFigpd4yhSL3oD4QeQFi4ziL6OHQQ6sNNlVc89NPHWmu3xHZtotYgXh0zBzA/oLQkCOB/6tZH6Q+Vu3/IuTRlBCfCV1k20Agiq5w==
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="SHA1"; boundary="----=_NextPart_000_0702_01D6958A.606FBF50"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HE1PR0701MB2876.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 8204eb1c-f99d-4cec-e078-08d86390c065
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Sep 2020 09:27:42.4618 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: E56FbV8ykEMh/O8NuLum7rE1zeYnLaFGubbE5ZfHWjiq9QeqVCFmCr7nh7WT+P7lB1K/BfVBoCD/9CEHY18hE6q4rBynXcCusPaSl/5zynlVS280L/6jORVHLo/jAOP5
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB3146
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/9iE7vwgsLn7jZHkwwJI-sAT1Nmo>
Subject: Re: [tsvwg] plan for L4S issue #29
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: Mon, 28 Sep 2020 09:27:52 -0000
Hi I think that this issue can be closed and moved to ICCRG. My impression, based on earlier discussions on this mailing list is that possible RFC3168 bottlenecks such as home gateways can be updated to support L4S alongside with other necessary updates that are done to block e.g. security threats. In addition, this discussion is a non-issue for 4G/5G access as RFC3168 ECN is AFAIK not at all implemented. Also think that it is reasonable to go for algorithms that can do detection rather than fall back. This can possibly be documented/referenced to in the L4S ops draft started by Greg White, that is published later on. The important thing is that I dont see any reasons why L4S issue #29 should block WGLC for the L4S drafts. Regards /Ingemar ================================ Ingemar Johansson M.Sc. Master Researcher Ericsson Research RESEARCHER GFTL ER NAP NCM Netw Proto & E2E Perf Labratoriegränd 11 977 53, Luleå, Sweden Phone +46-1071 43042 SMS/MMS +46-73 078 3289 ingemar.s.johansson@ericsson.com www.ericsson.com <http://www.ericsson.com/> Talk about a dream, try to make it real Bruce Springsteen =================================
- [tsvwg] plan for L4S issue #29 Wesley Eddy
- Re: [tsvwg] plan for L4S issue #29 Rodney W. Grimes
- Re: [tsvwg] plan for L4S issue #29 Jonathan Morton
- Re: [tsvwg] plan for L4S issue #29 Pete Heist
- Re: [tsvwg] plan for L4S issue #29 De Schepper, Koen (Nokia - BE/Antwerp)
- Re: [tsvwg] plan for L4S issue #29 Bob Briscoe
- Re: [tsvwg] plan for L4S issue #29 Pete Heist
- Re: [tsvwg] plan for L4S issue #29 De Schepper, Koen (Nokia - BE/Antwerp)
- Re: [tsvwg] plan for L4S issue #29 Rodney W. Grimes
- Re: [tsvwg] plan for L4S issue #29 Gorry Fairhurst
- Re: [tsvwg] plan for L4S issue #29 Sebastian Moeller
- Re: [tsvwg] plan for L4S issue #29 Sebastian Moeller
- Re: [tsvwg] plan for L4S issue #29 Jonathan Morton
- Re: [tsvwg] plan for L4S issue #29 Ingemar Johansson S
- Re: [tsvwg] plan for L4S issue #29 De Schepper, Koen (Nokia - BE/Antwerp)
- Re: [tsvwg] plan for L4S issue #29 De Schepper, Koen (Nokia - BE/Antwerp)
- Re: [tsvwg] plan for L4S issue #29 De Schepper, Koen (Nokia - BE/Antwerp)
- Re: [tsvwg] plan for L4S issue #29 Sebastian Moeller
- Re: [tsvwg] plan for L4S issue #29 Sebastian Moeller
- Re: [tsvwg] plan for L4S issue #29 Jonathan Morton
- Re: [tsvwg] plan for L4S issue #29 Gorry (erg)
- Re: [tsvwg] plan for L4S issue #29 Mikael Abrahamsson
- Re: [tsvwg] plan for L4S issue #29 Jonathan Morton
- Re: [tsvwg] plan for L4S issue #29 Pete Heist
- Re: [tsvwg] plan for L4S issue #29 Rodney W. Grimes
- Re: [tsvwg] plan for L4S issue #29 Gorry Fairhurst
- Re: [tsvwg] plan for L4S issue #29 Greg White
- Re: [tsvwg] plan for L4S issue #29 Jonathan Morton
- Re: [tsvwg] plan for L4S issue #29 Gorry Fairhurst
- Re: [tsvwg] plan for L4S issue #29 Sebastian Moeller
- Re: [tsvwg] plan for L4S issue #29 Ruediger.Geib
- Re: [tsvwg] plan for L4S issue #29 Gorry Fairhurst
- Re: [tsvwg] plan for L4S issue #29 Ingemar Johansson S
- Re: [tsvwg] plan for L4S issue #29 Sebastian Moeller
- Re: [tsvwg] plan for L4S issue #29 Sebastian Moeller
- Re: [tsvwg] plan for L4S issue #29 Ingemar Johansson S
- Re: [tsvwg] plan for L4S issue #29 Ingemar Johansson S
- Re: [tsvwg] plan for L4S issue #29 Sebastian Moeller
- Re: [tsvwg] plan for L4S issue #29 Mikael Abrahamsson
- Re: [tsvwg] plan for L4S issue #29 Sebastian Moeller
- Re: [tsvwg] plan for L4S issue #29 Wesley Eddy
- Re: [tsvwg] plan for L4S issue #29 Sebastian Moeller
- Re: [tsvwg] plan for L4S issue #29 Pete Heist
- Re: [tsvwg] plan for L4S issue #29 Gorry Fairhurst
- Re: [tsvwg] plan for L4S issue #29 Mikael Abrahamsson
- Re: [tsvwg] plan for L4S issue #29 Gorry Fairhurst
- Re: [tsvwg] plan for L4S issue #29 Jonathan Morton
- Re: [tsvwg] plan for L4S issue #29 Sebastian Moeller
- Re: [tsvwg] plan for L4S issue #29 Jonathan Morton
- Re: [tsvwg] plan for L4S issue #29 Pete Heist
- Re: [tsvwg] plan for L4S issue #29 Sebastian Moeller
- Re: [tsvwg] plan for L4S issue #29 Wesley Eddy
- Re: [tsvwg] plan for L4S issue #29 Wesley Eddy
- Re: [tsvwg] plan for assessing L4S safety [was: p… Sebastian Moeller
- Re: [tsvwg] plan for L4S issue #29 Rodney W. Grimes