From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qv1-xf32.google.com (mail-qv1-xf32.google.com [IPv6:2607:f8b0:4864:20::f32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id F146E3B29E for ; Wed, 23 Mar 2022 08:57:48 -0400 (EDT) Received: by mail-qv1-xf32.google.com with SMTP id hu11so1098003qvb.7 for ; Wed, 23 Mar 2022 05:57:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Vr/Y0h1kd4dqEJBykh8Fy52H3k3URSpJxo0/LmcUGsg=; b=OdcRl3uYP+uj92EY0yjvgsxqRWhAoOrCaaVOveWeO9bBQ8JP7fp/GoysdMYO3kpKE2 A8PvQ3nCc+XNAR7wQ8yJH+mWLCXV87LSpDpiL+JoLU+RJ2vVRLWhF9paRGlI7IBAYySy 4byqAsilqL21iOtd807I81CLcmFjOIm6rR+YVeI9j+RhmkKIjU5g771AB/c8zOKDR8fJ 6d9YL/yUUIuY4YfCqAqEK6ihuslAioqqjJFsvSlaviHmqgZa38bI+P0nZcSuLjZDUODG ArsZys3I0Y9IXkBeoR+j0PRAJQa/LqQx547+ptE02b7MPY0UOjrzPz2lkAQaJjc+UtZn Z/NA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Vr/Y0h1kd4dqEJBykh8Fy52H3k3URSpJxo0/LmcUGsg=; b=REEpHlENGAVBNlgH9adz/dDsTdD6ah7cLH7BEjKjvahdyD8jfHeZ4KaD1XMs0Tucqy EMke8dJhG6bbKsa5bxYt5Te6eSLrjKQ7+l0dvyQ5qRXIY0GfZYzv1FvXmAvlFKTvO24/ XFDx0TQuh19vHcdmhC7Ne5CHQ8Jg5zOOjqslp2iFQTrtO05Mzk6IF76qoEbf5iPS8REC UNpznEjU0MQD9KCNFJsmX6oQRl+CI2kR2nDX05r1sy+QOgKS/W3NEQuW9zs73UFMpd8R iLLiraoKbu0V94DsaIaG0UmF25v1eoXPKg/UeUwVU8kDM3z231Ff+TtgF4B9/8iK4yTL Uolw== X-Gm-Message-State: AOAM533a2L/aSL5RHOq4YixQpwKsFIj5y6Bh9hKBOIrHS4ihgmJ0AHvO 5DXe9M+Btaq6re39Eut3wJ4= X-Google-Smtp-Source: ABdhPJwuqQFOdZNIu+1YFOBERK0xDnym4FIpZN3k2ufbyS23/Lt3CfC7hm3PZXdAYwq1vrWHICzW3Q== X-Received: by 2002:ad4:5dc9:0:b0:441:56ad:8d93 with SMTP id m9-20020ad45dc9000000b0044156ad8d93mr3448830qvh.76.1648040268391; Wed, 23 Mar 2022 05:57:48 -0700 (PDT) Received: from [192.168.253.116] ([198.55.239.241]) by smtp.gmail.com with ESMTPSA id t7-20020a05622a01c700b002e1b3555c2fsm15355872qtw.26.2022.03.23.05.57.47 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 23 Mar 2022 05:57:48 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\)) From: Rich Brown In-Reply-To: <87mthg4zl7.fsf@miraculix.mork.no> Date: Wed, 23 Mar 2022 08:57:47 -0400 Cc: Paul Spooren , openwrt-devel@lists.openwrt.org, Rpm Content-Transfer-Encoding: quoted-printable Message-Id: References: <94079409-E562-40E6-BF4E-A0A94A926A76@gmail.com> <230DF5D9-1784-4077-819D-B4128CB08686@aparcar.org> <87mthg4zl7.fsf@miraculix.mork.no> To: =?utf-8?Q?Bj=C3=B8rn_Mork?= X-Mailer: Apple Mail (2.3608.120.23.2.7) 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:57:49 -0000 Bj=C3=B8rn, Thanks for these comments. > 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. That might satisfy Paul Spooren's concern. > 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 >=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. Although I took an editorial pass over an earlier version of the RFC, = I'm not in a position to address your questions.=20 Let me propose this process for continuing the conversation. With this = response, I'm cc'ing: - openwrt-devel - RPM mailing list - named individuals Not everyone is subscribed to both lists, but cc'ing everyone who = responds should keep everyone included. Thank you. Rich=