Re: Updating Digest header RFC3230 using "selected representation"

Rob Sayre <sayrer@gmail.com> Tue, 23 July 2019 20:27 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 4C3BD1209AC for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 23 Jul 2019 13:27:56 -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, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 u4gvq33l3b9D for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 23 Jul 2019 13:27:55 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [IPv6:2603:400a:ffff:804:801e:34:0:38]) (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 01AF61209A4 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 23 Jul 2019 13:27:54 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1hq1MJ-0005Lj-Lv for ietf-http-wg-dist@listhub.w3.org; Tue, 23 Jul 2019 20:26:03 +0000
Resent-Date: Tue, 23 Jul 2019 20:26:03 +0000
Resent-Message-Id: <E1hq1MJ-0005Lj-Lv@frink.w3.org>
Received: from mimas.w3.org ([2603:400a:ffff:804:801e:34:0:4f]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <sayrer@gmail.com>) id 1hq1MH-0005Ky-Qf for ietf-http-wg@listhub.w3.org; Tue, 23 Jul 2019 20:26:01 +0000
Received: from mail-io1-xd34.google.com ([2607:f8b0:4864:20::d34]) by mimas.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from <sayrer@gmail.com>) id 1hq1MG-0000IR-Kq for ietf-http-wg@w3.org; Tue, 23 Jul 2019 20:26:01 +0000
Received: by mail-io1-xd34.google.com with SMTP id s7so84553981iob.11 for <ietf-http-wg@w3.org>; Tue, 23 Jul 2019 13:25:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=NrlQ/vQGD2H5YYAARWNFEhhQIRXQslmQeGK6AkFl6nk=; b=FcuwDVgJXyGvglPAZWPPjOXUj1UfMgvoGxFzYvMQB2S+gz4T944kOjDXkk/SjR0RjV j5jS4bMu2NbYxojEzG78F0jeELJBRKSZZxGcsTHXJEUszLJLRix4FAZzOzuW11NCf4BA VcokQeGfiDsyeWgwJV2xijbjpRZbVEtmyx222DP0o0AQwbx5Yurma8xzvqD6VrGGNykT kGIxpSQFSxNN8fbnXDAbg8yrWbzd2GwUtkXWu6MbKjtGsIiLRXN0ahmb+OINeEft3AZ6 tqIxwrBXNIFAASDYGIjD9v3e25LodWw5ULNQjpRKaKyr3DotPvcGAA1eZqOkjWxWcD6w Ds+A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=NrlQ/vQGD2H5YYAARWNFEhhQIRXQslmQeGK6AkFl6nk=; b=Mt6RiPsYRnXtZzaPeMJZkyV25td2kNtolaTTAhS64J1UcecrXjT0PWDZF35+IwKjDg skK1jDksfT3yOshnt5wFPigCJXfoJoS14Ru7bjhivxtKrfqgKyxW7+nbJVNccQ6bzbPt 867asOdi7fnKNlFBr+KZ4GAolNJMEL/HyXuX4OywR6CSncUFjifOmIjm67+MtB+4dycN W6LA/dvtNB1obOGv4okyMEe78uQPiJm2KEGbyeLgcCAO6FhwB1ifU5X2SbBQ5uj0Nk2K J80F+eXFRhfq4OVO59fCBRnUVIsVqQ2ykv/6R9yOyTueUkXjgixpeSN4oDLMN0tqJVuh dBvQ==
X-Gm-Message-State: APjAAAXpqiL0r9qGVbDtAdITWH2IUuRi3to5mZzzMNlCDxYaV/rSN1x+ suzOA7EgkGHkuiCTUM0OmLc07P8cgYllFGsf+IcTqXOiX9o=
X-Google-Smtp-Source: APXvYqxZFkPn4RnrCcCuJ/ExaLvLRGON+d4Zakq9AnENRZEgVjmIVTDe4cJZrzAka/Pj9P6sQkQUoaEI0J/xl47utN0=
X-Received: by 2002:a5e:9515:: with SMTP id r21mr39295051ioj.257.1563913538977; Tue, 23 Jul 2019 13:25:38 -0700 (PDT)
MIME-Version: 1.0
References: <CAMRHeuyk-xv2oRmcVrFaesneVi4F-EcuttsJU5PKtGrVtP+gSA@mail.gmail.com> <CALGR9obe6mPMCW2O1gf0muWgoT4Nusy8CsoixgENWKTSEf4rGA@mail.gmail.com> <CAMRHeux6=i0Xkg5XPXp8PCZiiLopGkYGTPWztghfzgUx+XF5=Q@mail.gmail.com> <CALGR9oYbZpKMThSJqSAheRfE8NVnDkhMYSbRP-gYnc5-5k8LmQ@mail.gmail.com> <CAChr6SyxGEfV1rHjX8oMLvB-osdgsbjWjkeWAWbPfGAFdC4Zwg@mail.gmail.com>
In-Reply-To: <CAChr6SyxGEfV1rHjX8oMLvB-osdgsbjWjkeWAWbPfGAFdC4Zwg@mail.gmail.com>
From: Rob Sayre <sayrer@gmail.com>
Date: Tue, 23 Jul 2019 13:25:27 -0700
Message-ID: <CAChr6SynBvPB+6yBnKk9z9FFZs0ZynremyntGGyT2Q3S0tmY1g@mail.gmail.com>
To: Lucas Pardue <lucaspardue.24.7@gmail.com>
Cc: Roberto Polli <roberto@teamdigitale.governo.it>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="000000000000f34471058e5efe22"
Received-SPF: pass client-ip=2607:f8b0:4864:20::d34; envelope-from=sayrer@gmail.com; helo=mail-io1-xd34.google.com
X-W3C-Hub-Spam-Status: No, score=-3.0
X-W3C-Hub-Spam-Report: AWL=1.141, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1hq1MG-0000IR-Kq 03819f978ebc7fb7fc04ca69ecc1d370
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Updating Digest header RFC3230 using "selected representation"
Archived-At: <https://www.w3.org/mid/CAChr6SynBvPB+6yBnKk9z9FFZs0ZynremyntGGyT2Q3S0tmY1g@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/36825
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 Tue, Jul 23, 2019 at 1:12 PM Rob Sayre <sayrer@gmail.com>; wrote:

> This draft looks good to me.
>
> One issue that prevented the adoption of this header and related ones
> (e.g. Content-MD5) was that HTTP/1.1 trailers had a lot of interoperability
> problems. This made it expensive for large files, or impossible to use for
> message bodies that couldn't be pre-calculated.
>

That last part is slightly wrong. I should have said it was impossible to
use for message bodies that couldn't be pre-calculated that were also
streamed. Roughly, these headers required a lot of buffering, and this
trade-off doesn't seem to be present anymore.

thanks,
Rob