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

Willy Tarreau <w@1wt.eu> Thu, 19 March 2020 16:32 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 817983A08F8 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 19 Mar 2020 09:32:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level:
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=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 Col7e6us624U for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 19 Mar 2020 09:32:27 -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 A760A3A08EA for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 19 Mar 2020 09:32:27 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1jEy2h-0005ct-Br for ietf-http-wg-dist@listhub.w3.org; Thu, 19 Mar 2020 16:29:11 +0000
Resent-Date: Thu, 19 Mar 2020 16:29:11 +0000
Resent-Message-Id: <E1jEy2h-0005ct-Br@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 1jEy2f-0005bl-Qu for ietf-http-wg@listhub.w3.org; Thu, 19 Mar 2020 16:29:09 +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 1jEy2d-0008In-Vy for ietf-http-wg@w3.org; Thu, 19 Mar 2020 16:29:09 +0000
Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id 02JGSpjP019223; Thu, 19 Mar 2020 17:28:51 +0100
Date: Thu, 19 Mar 2020 17:28:51 +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: <20200319162851.GB19209@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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <17396.1584635103@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 1jEy2d-0008In-Vy 69d0a0cc1a903b0007303a81977fea6d
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/20200319162851.GB19209@1wt.eu>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/37463
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 04:25:03PM +0000, Poul-Henning Kamp wrote:
> --------
> In message <20200319161130.GA19209@1wt.eu>, Willy Tarreau writes:
> >On Thu, Mar 19, 2020 at 03:53:32PM +0000, Poul-Henning Kamp wrote:
> 
> >> 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.
> 
> I thought about that, but I know of applications where traffic is sorted
> in "small", "medium" and "huge", where "small" is significantly less than
> a megabyte, so I think the units should in the kilobytes rather than
> megabytes range.  Just to throw a number out there:  Smaller than 32k.

I'm fine with this anyway.

Willy