IETF Logo Mail Archive

Re: digest-headers-04: which digest is in the trailer?

Roberto Polli <robipolli@gmail.com> Sat, 13 February 2021 09:44 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 806AF3A0D96 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 13 Feb 2021 01:44:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.77
X-Spam-Level:
X-Spam-Status: No, score=-2.77 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, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=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 Nn4y4NeFHHdG for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 13 Feb 2021 01:44:18 -0800 (PST)
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 D088F3A0D93 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sat, 13 Feb 2021 01:44:18 -0800 (PST)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1lArQy-0005LR-CN for ietf-http-wg-dist@listhub.w3.org; Sat, 13 Feb 2021 09:41:48 +0000
Resent-Date: Sat, 13 Feb 2021 09:41:48 +0000
Resent-Message-Id: <E1lArQy-0005LR-CN@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 <robipolli@gmail.com>) id 1lArQw-0005Kj-BR for ietf-http-wg@listhub.w3.org; Sat, 13 Feb 2021 09:41:46 +0000
Received: from mail-il1-x129.google.com ([2607:f8b0:4864:20::129]) by mimas.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <robipolli@gmail.com>) id 1lArQs-0007Ix-IX for ietf-http-wg@w3.org; Sat, 13 Feb 2021 09:41:46 +0000
Received: by mail-il1-x129.google.com with SMTP id y15so1428339ilj.11 for <ietf-http-wg@w3.org>; Sat, 13 Feb 2021 01:41:42 -0800 (PST)
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=6tzGVRDaF03IyEShvFNhPb3STgNGQsVZ+3O6GT47P6g=; b=J+6pNO/+3EHWXEzTLnQqO0ikcsk1KISaJIioQH0N3JElG8Y2mdh8Uc7011BjoYrNpe DLzON6p+1XK+VW/DSTXHjP+kAityWl6F45YjQkeEdItYRkx9tUFFNYAz9NDoIgZVypqY yjBWEssHtCyAzBb8VdxQwJu3+08AdaF3uzyss3pZs/VeKh/GOUdCDiIole8txRGMHYbA xLE7xRwElY13R5uo/QwdnHLlVDIsruyuEO+psnhPDBRiNzgBzvzUe4XhV2fPQ1/5+fJg Ov2IOiSrssCdQOJ5fhanyz1wMD+P4lqztrXASAEWvKIZl9HhHtbd6l08uRzMahN8/dur L5Rw==
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=6tzGVRDaF03IyEShvFNhPb3STgNGQsVZ+3O6GT47P6g=; b=SdMk9AraBr4I5QuY+Mi+U+5gLtbbgCOmETu4/3z1M3TXbkhu7jJVi6XFZcWuidLIj8 ysLBCKFPAgUvGtHMfINDoFLZP7IeIuG6Ug2lccYP8tRsAtdkBaQT7DEGU9oFIzsgf8ce et4DQMO0iUvXTEXz3q9Ktfpa9vMuxxSd9e4seQqIF2fTPNay6cojw2YBQ1SctD6H0tG1 mwEXW5YrCe0oHgLA2Jscv2IU8V5lUST9//IWG4UyWEhwCgIKe09je3Pf/Yw2Vrzgw9EN xiUeTy1txB/jIxOXNJQCHXHoDUHMyV4EJ6jAefXJ40xtDoVjtFpgElnG+6byosZwe4WZ 2loQ==
X-Gm-Message-State: AOAM530CE6/+ciUMWUtlyO154Sb6yRBi7mdmi3iH4B5m9aL7WBeIa3rG HFw3EVgw7ebLR/s1I/Y8+8k/EQsg8lFiEObbP1o=
X-Google-Smtp-Source: ABdhPJw+vd+kw76vmZpIw+CgO6HZco6BuFsjsKt3SQJb4ThCvLZPhyIfpXkIGTqlHgfvyFziyHPkDla8eWYDv6pAwDI=
X-Received: by 2002:a05:6e02:1c8a:: with SMTP id w10mr5968990ill.127.1613209291732; Sat, 13 Feb 2021 01:41:31 -0800 (PST)
MIME-Version: 1.0
References: <20210208220246.GB1046058@okhta> <CALGR9oZR=8r5xrVE9OaE=t+ocyCykpjrsCLnRzgQaLKDE5kGWA@mail.gmail.com>
In-Reply-To: <CALGR9oZR=8r5xrVE9OaE=t+ocyCykpjrsCLnRzgQaLKDE5kGWA@mail.gmail.com>
From: Roberto Polli <robipolli@gmail.com>
Date: Sat, 13 Feb 2021 10:41:20 +0100
Message-ID: <CAP9qbHURYy4M7g5auaF6rCQSYJMuC1vCRN+nU5CwJdG6ekcn2A@mail.gmail.com>
To: Lucas Pardue <lucaspardue.24.7@gmail.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="000000000000c83c4a05bb348e37"
Received-SPF: pass client-ip=2607:f8b0:4864:20::129; envelope-from=robipolli@gmail.com; helo=mail-il1-x129.google.com
X-W3C-Hub-DKIM-Status: validation passed: (address=robipolli@gmail.com domain=gmail.com), signature is good
X-W3C-Hub-Spam-Status: No, score=-5.1
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, 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_DB=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1lArQs-0007Ix-IX ebf3a1f8a66a7f7a1ea4e5e4b9fc749b
X-Original-To: ietf-http-wg@w3.org
Subject: Re: digest-headers-04: which digest is in the trailer?
Archived-At: <https://www.w3.org/mid/CAP9qbHURYy4M7g5auaF6rCQSYJMuC1vCRN+nU5CwJdG6ekcn2A@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/38588
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>

Thanks Dimitri, good catch.

I agree with Lucas: a new header can work like

Has-Digest: sha-256, id-sha-256

If there's consensus it could be reasonable to include it into this spec.

Wdyt?
R

Il lun 8 feb 2021, 23:41 Lucas Pardue <lucaspardue.24.7@gmail.com> ha
scritto:

> Hey Dmitri,
>
> On Mon, Feb 8, 2021 at 10:06 PM Dmitri Tikhonov <
> dtikhonov@litespeedtech.com> wrote:
>
>> Hello,
>>
>> In the case where the digest is included in the trailer (Section 10.11
>> [1]), it may be beneficial for the client to know *which* digest the
>> server plans to include in the trailer.  This way, the client, too, can
>> calculate it in the streaming manner.  I wonder whether this use case
>> has been considered.
>>
>
> The use case probably has been considered but I'm not sure there is a
> simple solution that can already solve it. If someone knows HTTP-fu and
> wants to propose a valid way to do it with existing mechanisms, we could
> incorporate it into the example. Failing that, I think a new header,
> defined in a standalone document would be path forward.
>
> FWIW draft-thomson-http-mice-03 seems like it was part way to a solution
> [1]
>
> Cheers
> Lucas
>
> [1] https://tools.ietf.org/html/draft-thomson-http-mice-03#section-4.1
>
>

v2.23.0 | Report a Bug | By Email