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

Martin Thomson <mt@lowentropy.net> Thu, 19 March 2020 21:38 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 8F3203A0FD4 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 19 Mar 2020 14:38:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.751
X-Spam-Level:
X-Spam-Status: No, score=-2.751 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=fORfqyNn; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=D9ZNzgeZ
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 7htLn1-gauJO for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 19 Mar 2020 14:37:54 -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 70CEC3A0F89 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 19 Mar 2020 14:37:53 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1jF2oO-0004Gc-2L for ietf-http-wg-dist@listhub.w3.org; Thu, 19 Mar 2020 21:34:44 +0000
Resent-Date: Thu, 19 Mar 2020 21:34:44 +0000
Resent-Message-Id: <E1jF2oO-0004Gc-2L@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 <mt@lowentropy.net>) id 1jF2oL-0004Fq-Ri for ietf-http-wg@listhub.w3.org; Thu, 19 Mar 2020 21:34:41 +0000
Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by titan.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <mt@lowentropy.net>) id 1jF2oK-0000JV-23 for ietf-http-wg@w3.org; Thu, 19 Mar 2020 21:34:41 +0000
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 380B15C01A1 for <ietf-http-wg@w3.org>; Thu, 19 Mar 2020 17:34:28 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute2.internal (MEProxy); Thu, 19 Mar 2020 17:34:28 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm1; bh=iPvIszzN40t/KJR1e6X1K6rnW6hdlRK X3pSsfS/XhdU=; b=fORfqyNnx6Q1dEPzU/wh7+n2AJCfdCL2Fwt+piS1NzRLxxi Nf2c9V0RnMLHLfGzRHTab3PjMa/TOa44NxNU8C+y+qnLTunLba5LwcMQ0YHNGM1y Isa89XcaU9YRoLTgL2gSRkWISf68p1aC20tl9KIkHVPvKFE9Wg+I8hIswHwMNDnM rVSBm5CW9MR4E3J+r1aKuHsoChRhIpoNqyIRfdw8NgpiT+WJItw3ss/mc6rAfi0P SVG23Iheo3DmwYlAKtuOsf3djNP6BcOy3ouCns90O52Wg81H8M2yExIJKIYwHKAI iwwXKD5wAPMjAVRLwKDWVu/m8C8BdsEpr6PN+Pw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=iPvIsz zN40t/KJR1e6X1K6rnW6hdlRKX3pSsfS/XhdU=; b=D9ZNzgeZpMaBhXsoX4vM2X dJsMA3SQi85zi29Nq6QRQiSDydXQMB+4e5glMMBX+l2Ir94jE7xJ57iJzH03vtgp NOT4Q3G2jZ1JmsBjIkE+aANL4idLEC0//BjCtE/tFe94K1jR4sfWlceqMp14Vkjh eExDWdkKoZvb6J5J9S1XBuLguGAtKX+/LMXUIntAmhTFZPlPOng/pmsi5Ez0zeSh /4IKIrsCEnKbxCqf0IlaIZpuJ+RtSlrJeDnEckSKuH8t1BvlGv3LFX6cF+xyR+02 d6z/41L6VAn3QZi3xbhIfHY7Gk1sXsEeKzeuA1NzxbRW+5YJ9I9xlbxa9kzYhuiQ ==
X-ME-Sender: <xms:Y-VzXoHAsYB05CKJTOoZRMYlV1J45grcFLJDWExY7goD4KbcNLnwQw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrudefledgudeggecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesth dtredtreerjeenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehl ohifvghnthhrohhphidrnhgvtheqnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrg hmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:Y-VzXmp9inurV9z-S-WG1j2_TC_CtvFBpB-t5W2e64Q8yrX6vI-4lg> <xmx:Y-VzXiCz1vVupksPLrckEyNK4j7gfeO1oQZ1Q6AWYGgWWkKzrKGnFA> <xmx:Y-VzXqFQG_jp2-sufz__jqmTI3z8juz4ZOBg6DuQCz6qYN8eRhSfyg> <xmx:ZOVzXnoUwsYP-ktvv6VjjX-KkVps04KwVfDd_b-RLu5WcFJv-icIHg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id D3FD3E00C2; Thu, 19 Mar 2020 17:34:27 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-1021-g152deaf-fmstable-20200319v1
Mime-Version: 1.0
Message-Id: <08ccb5b3-a3e9-4c0a-a656-86cc70f458aa@www.fastmail.com>
In-Reply-To: <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> <20200319162851.GB19209@1wt.eu>
Date: Fri, 20 Mar 2020 08:34:08 +1100
From: Martin Thomson <mt@lowentropy.net>
To: ietf-http-wg@w3.org
Content-Type: text/plain
Received-SPF: pass client-ip=66.111.4.25; envelope-from=mt@lowentropy.net; helo=out1-smtp.messagingengine.com
X-W3C-Hub-Spam-Status: No, score=-9.8
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1jF2oK-0000JV-23 7b2d0dff09c6d01387aa9d01aa29ffe3
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/08ccb5b3-a3e9-4c0a-a656-86cc70f458aa@www.fastmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/37465
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>

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.

At the extreme, you might say X +/- Y with Z confidence.  With fields for each.

That sounds like overengineering, but it doesn't have to be complicated in common usage.  You could say that Y and Z are implied or have defaults to simplify the common case.  From that a recipient can build to whatever assumption they like.  Find a value of f(Z) for X + Y*f(Z) that suits you.  Just want to show a progress meter, then f(Z) = 0 is probably fine.  Want to allocate space with a low risk of overflow, then you might want something like f(Z) = 2/Z.


On Fri, Mar 20, 2020, at 03:28, Willy Tarreau wrote:
> 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
> 
>