From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay12.mail.gandi.net (relay12.mail.gandi.net [217.70.178.232]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 68BBE3B29E for ; Wed, 23 Mar 2022 09:02:40 -0400 (EDT) Received: from smtpclient.apple (bl11-88-34.dsl.telepac.pt [85.244.88.34]) (Authenticated sender: mail@aparcar.org) by mail.gandi.net (Postfix) with ESMTPSA id 7ACEE20000C; Wed, 23 Mar 2022 13:02:38 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\)) From: Paul Spooren In-Reply-To: Date: Wed, 23 Mar 2022 13:02:37 +0000 Cc: =?utf-8?Q?Bj=C3=B8rn_Mork?= , openwrt-devel , Rpm Content-Transfer-Encoding: quoted-printable Message-Id: <5099D842-68F6-469F-9B54-6E996F669B61@aparcar.org> References: <94079409-E562-40E6-BF4E-A0A94A926A76@gmail.com> <230DF5D9-1784-4077-819D-B4128CB08686@aparcar.org> <87mthg4zl7.fsf@miraculix.mork.no> To: Rich Brown X-Mailer: Apple Mail (2.3696.80.82.1.1) Subject: Re: [Rpm] Seeking RPM Server package for OpenWrt X-BeenThere: rpm@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: revolutions per minute - a new metric for measuring responsiveness List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Mar 2022 13:02:40 -0000 > On 23. Mar 2022, at 12:57, Rich Brown wrote: >=20 > Bj=C3=B8rn, >=20 > Thanks for these comments. >=20 >> On Mar 23, 2022, at 8:34 AM, Bj=C3=B8rn Mork wrote: >>=20 >> There is no need to read anything from a file or device. You can = just >> serve the same memory buffer in a loop. Thanks, I=E2=80=99ll check that in case I work on a server for OpenWrt. >=20 > That might satisfy Paul Spooren's concern. >=20 >> I did a quick look at the document and it seems under-specified. = Page >> after page with blah-blah, but >> - not defining Content-Type for any of the URLs I guess it simply don=E2=80=99t matter, just like the content itself? In = their demo setups they host either a single `x` (small file) or 4G times = `x` (large file). >> - not defining ciphers or any other TLS options, despite the rather >> restrictive TLSv1.3 requirment >> - no config examples for common web servers https://github.com/network-quality/server >> - no actual client algorithm I found this implementation but din=E2=80=99t skim through the full code = yet: = https://github.com/network-quality/goresponsiveness/blob/main/networkQuali= ty.go >>=20 >> The last point is obviously the biggest problem. You can do whatever >> you want when implementng this, so the results from different clients >> will not be comparable at all. >>=20 >> IMHO it's better let this soak for a while until they've reversed the >> blah-blah to content ratio. This doesn't look like a finished = protocol. >=20 > Although I took an editorial pass over an earlier version of the RFC, = I'm not in a position to address your questions.=20 >=20 > Let me propose this process for continuing the conversation. With this = response, I'm cc'ing: >=20 > - openwrt-devel > - RPM mailing list > - named individuals >=20 > Not everyone is subscribed to both lists, but cc'ing everyone who = responds should keep everyone included. >=20 > Thank you. >=20 > Rich