IETF Logo Mail Archive

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

Willy Tarreau <w@1wt.eu> Thu, 19 March 2020 22:36 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 222FF3A114F for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 19 Mar 2020 15:36:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.631
X-Spam-Level:
X-Spam-Status: No, score=-2.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, T_SPF_HELO_TEMPERROR=0.01, T_SPF_TEMPERROR=0.01] 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 kek41walUTlu for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 19 Mar 2020 15:36:06 -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 48C853A114D for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 19 Mar 2020 15:35:55 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1jF3id-0000NT-Bj for ietf-http-wg-dist@listhub.w3.org; Thu, 19 Mar 2020 22:32:51 +0000
Resent-Date: Thu, 19 Mar 2020 22:32:51 +0000
Resent-Message-Id: <E1jF3id-0000NT-Bj@lyra.w3.org>
Received: from titan.w3.org ([128.30.52.76]) by lyra.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <w@1wt.eu>) id 1jF3ib-0000Mc-J6 for ietf-http-wg@listhub.w3.org; Thu, 19 Mar 2020 22:32:49 +0000
Received: from wtarreau.pck.nerim.net ([62.212.114.60] helo=1wt.eu) by titan.w3.org with esmtp (Exim 4.92) (envelope-from <w@1wt.eu>) id 1jF3iZ-0001tr-RE for ietf-http-wg@w3.org; Thu, 19 Mar 2020 22:32:49 +0000
Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id 02JMWV53020152; Thu, 19 Mar 2020 23:32:31 +0100
Date: Thu, 19 Mar 2020 23:32:31 +0100
From: Willy Tarreau <w@1wt.eu>
To: Martin Thomson <mt@lowentropy.net>
Cc: ietf-http-wg@w3.org
Message-ID: <20200319223231.GH20076@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> <20200319161130.GA19209@1wt.eu> <17396.1584635103@critter.freebsd.dk> <20200319162851.GB19209@1wt.eu> <08ccb5b3-a3e9-4c0a-a656-86cc70f458aa@www.fastmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <08ccb5b3-a3e9-4c0a-a656-86cc70f458aa@www.fastmail.com>
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: titan.w3.org 1jF3iZ-0001tr-RE 0c3a9f1f7d7cfc9b197fd942bab9256b
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/20200319223231.GH20076@1wt.eu>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/37468
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 Fri, Mar 20, 2020 at 08:34:08AM +1100, Martin Thomson wrote:
> Do we want approximation or a cap on size?
> 
> An upper bound is good for some of the use cases we see.  An estimate for the
> other cases.

In case of a stream it's not necessarily known in advance, think for
example of a postscript processor sending to a printer and used to
display the %complete on the printer's LCD. However if sent as a
rough estimate it can still be extremely wrong and suddenly catch
up when reachin the end. You don't mind if your printer's LCD
"%complete" is wrong as long as it continues to make progress.

Willy

v2.14.0 | Report a Bug | By Email