IETF Logo Mail Archive

Re: New Version Notification for draft-nottingham-bikeshed-length-00.txt

Willy Tarreau <w@1wt.eu> Thu, 19 March 2020 16:15 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 328C73A0872 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 19 Mar 2020 09:15:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.652
X-Spam-Level:
X-Spam-Status: No, score=-2.652 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 nSeCYQqu1S5y for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 19 Mar 2020 09:15:10 -0700 (PDT)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (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 7562C3A08CD for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 19 Mar 2020 09:15:10 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1jExm0-0003BP-OP for ietf-http-wg-dist@listhub.w3.org; Thu, 19 Mar 2020 16:11:56 +0000
Resent-Date: Thu, 19 Mar 2020 16:11:56 +0000
Resent-Message-Id: <E1jExm0-0003BP-OP@lyra.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by lyra.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <w@1wt.eu>) id 1jExlx-0003Ae-Fu for ietf-http-wg@listhub.w3.org; Thu, 19 Mar 2020 16:11:53 +0000
Received: from wtarreau.pck.nerim.net ([62.212.114.60] helo=1wt.eu) by mimas.w3.org with esmtp (Exim 4.92) (envelope-from <w@1wt.eu>) id 1jExlv-0007lT-Iz for ietf-http-wg@w3.org; Thu, 19 Mar 2020 16:11:53 +0000
Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id 02JGBUWA019214; Thu, 19 Mar 2020 17:11:30 +0100
Date: Thu, 19 Mar 2020 17:11:30 +0100
From: Willy Tarreau <w@1wt.eu>
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
Cc: Cory Benfield <cory@lukasa.co.uk>, Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <20200319161130.GA19209@1wt.eu>
References: <158449485958.32126.16514800548442242620@ietfa.amsl.com> <3DD75975-2CA3-4071-974C-922121689310@mnot.net> <CAH_hAJGU=2OG-QRKSiauTFzHxLXdUBAc4ngLy93b-b3MbNLiKA@mail.gmail.com> <17273.1584633212@critter.freebsd.dk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <17273.1584633212@critter.freebsd.dk>
User-Agent: Mutt/1.6.1 (2016-04-27)
Received-SPF: pass client-ip=62.212.114.60; envelope-from=w@1wt.eu; helo=1wt.eu
X-W3C-Hub-Spam-Status: No, score=-4.9
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1jExlv-0007lT-Iz 2111240a63bc1a250be397f6d8330a8b
X-Original-To: ietf-http-wg@w3.org
Subject: Re: New Version Notification for draft-nottingham-bikeshed-length-00.txt
Archived-At: <https://www.w3.org/mid/20200319161130.GA19209@1wt.eu>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/37461
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

On Thu, Mar 19, 2020 at 03:53:32PM +0000, Poul-Henning Kamp wrote:
> --------
> In message <CAH_hAJGU=2OG-QRKSiauTFzHxLXdUBAc4ngLy93b-b3MbNLiKA@mail.gmail.com>
> , Cory Benfield writes:
> 
> >As with Willy and Martin, I think it would be good for this draft to
> >explicitly allow fuzziness in the field value. Otherwise, the draft
> >seems reasonable, and I'd implement it.
> 
> We could make it explictly fuzzy, by definting it as kilobytes rounded down ?

I think it's an excellent idea, which even goes in the direction of
reducing the on-wire bytes. And given todays connections speeds, if we
use it only for progress bars it could even represent megabytes rounded
to the nearest. Less than 0.5 will usually not take more than a few
seconds and not deserve showing an accurate progress bar.

Willy

v2.14.0 | Report a Bug | By Email