From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from louie.mork.no (louie.mork.no [IPv6:2001:41c8:51:8a:feff:ff:fe00:e5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id B36833B29E for ; Wed, 23 Mar 2022 08:34:38 -0400 (EDT) Received: from canardo.dyn.mork.no ([IPv6:2a01:799:c9f:8600:0:0:0:1]) (authenticated bits=0) by louie.mork.no (8.15.2/8.15.2) with ESMTPSA id 22NCYXk5588770 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=OK); Wed, 23 Mar 2022 12:34:35 GMT Received: from miraculix.mork.no ([IPv6:2a01:799:95f:8b0a:1e21:3a05:ad2e:f4a6]) (authenticated bits=0) by canardo.dyn.mork.no (8.15.2/8.15.2) with ESMTPSA id 22NCYX9r1566169 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=OK); Wed, 23 Mar 2022 13:34:33 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mork.no; s=b; t=1648038873; bh=E4L0gPUq8VnoZP7AU/lKimvSVQp789q9mw2BkXdBorQ=; h=From:To:Cc:Subject:References:Date:Message-ID:From; b=huISusYnGD9cl3AUv4QWmp/UNMyk2Q5Wam/cHv3qB/IRhfEUWKRq7/9vREJbJrY3P HhdkBuQgydo0jdVntPldAcCTYZWX7l8xkw+haL1H4C2qwQL8vvrSD/iRyiOO2zfuVo repOCvfy585PyYAzP1icBdL7dxcTLy/wAzDsc9oA= Received: (nullmailer pid 1106888 invoked by uid 1000); Wed, 23 Mar 2022 12:34:28 -0000 From: =?utf-8?Q?Bj=C3=B8rn_Mork?= To: Paul Spooren Cc: Rich Brown , openwrt-devel@lists.openwrt.org, Rpm Organization: m References: <94079409-E562-40E6-BF4E-A0A94A926A76@gmail.com> <230DF5D9-1784-4077-819D-B4128CB08686@aparcar.org> Date: Wed, 23 Mar 2022 13:34:28 +0100 In-Reply-To: <230DF5D9-1784-4077-819D-B4128CB08686@aparcar.org> (Paul Spooren's message of "Wed, 23 Mar 2022 12:05:09 +0000") Message-ID: <87mthg4zl7.fsf@miraculix.mork.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: clamav-milter 0.103.3 at canardo X-Virus-Status: Clean 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 12:34:38 -0000 Paul Spooren writes: > The spec wants a 8GB file which seems a bit much for common home > routers. We could look into reading from /dev/zero since the body > content isn=E2=80=99t relevant but still the device is likely slower at > offering the content than your laptop can chew. A dedicated device > could be required. There is no need to read anything from a file or device. You can just serve the same memory buffer in a loop. 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 - not defining ciphers or any other TLS options, despite the rather restrictive TLSv1.3 requirment - no config examples for common web servers - no actual client algorithm 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. 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. Bj=C3=B8rn