Re: [tsvwg] plan for L4S issue #29
Mikael Abrahamsson <swmike@swm.pp.se> Wed, 30 September 2020 11:06 UTC
Return-Path: <swmike@swm.pp.se>
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 19F863A0B3D for <tsvwg@ietfa.amsl.com>; Wed, 30 Sep 2020 04:06:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=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=swm.pp.se
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 21chdH1kHfqk for <tsvwg@ietfa.amsl.com>; Wed, 30 Sep 2020 04:06:29 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (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 EF2243A0ADF for <tsvwg@ietf.org>; Wed, 30 Sep 2020 04:06:28 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id A6067AF; Wed, 30 Sep 2020 13:06:26 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1601463986; bh=rBoFP8Zh65UVav65wE8s6+Oo59COT3SsK8914JHuotg=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=KmEjKRYgWuKYGGhvew9UCeb85KcbBQxrtpsAa128BEyMt3EHhrTUwFauyvHBZuhF4 l4veZRuXswZodbxLz2RWpsUsp4vaQoFuPXngcpT+ebdzlxWSXqUDWb+O6w/W+4Ujcv A9JRjFOajrOP8XPI+CSXW6ryPba3O7uKAiU7NfpI=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id A39129F; Wed, 30 Sep 2020 13:06:26 +0200 (CEST)
Date: Wed, 30 Sep 2020 13:06:26 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ruediger.Geib@telekom.de
cc: ingemar.s.johansson=40ericsson.com@dmarc.ietf.org, tsvwg@ietf.org
In-Reply-To: <LEJPR01MB1116D7DFFADC28995CB6965F9C330@LEJPR01MB1116.DEUPRD01.PROD.OUTLOOK.DE>
Message-ID: <alpine.DEB.2.20.2009301256260.20021@uplift.swm.pp.se>
References: <HE1PR0701MB2876EE4CE6B71EEFA88A912AC2330@HE1PR0701MB2876.eurprd07.prod.outlook.com> <LEJPR01MB1116D7DFFADC28995CB6965F9C330@LEJPR01MB1116.DEUPRD01.PROD.OUTLOOK.DE>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/qBcfqtQeWaaygfb5JL0k-BQyby4>
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: Wed, 30 Sep 2020 11:06:31 -0000
On Wed, 30 Sep 2020, Ruediger.Geib@telekom.de wrote: > players may be useful too (e.g., I don't know whether an access router > vendor offers an L4S implementation, and availability of applications or > content expected to benefit from L4S transport certainly would be very > helpful). I participated in FQ_CODEL / CAKE evaluation which was easy to do because it was developed using a fork of OpenWrt which had readily available platforms/code/compilation environment etc and it was easy to get started because it was already packaged. There was also tools like Flent to evaluate performance in different combinations. All development was done on github etc and it was easy to follow. When searching for L4S patches I find https://github.com/L4STeam/linux I don't see much activity in the past 5 months, is this really where development is being done? -- Mikael Abrahamsson email: swmike@swm.pp.se
- [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