Re: Digests: deprecating parameters?

Roberto Polli <robipolli@gmail.com> Tue, 18 August 2020 15:57 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 AABF93A0DDA for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 18 Aug 2020 08:57:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.997
X-Spam-Level:
X-Spam-Status: No, score=-2.997 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.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 QvH-_1hb9qDM for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 18 Aug 2020 08:57:19 -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 45C1E3A0DD9 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 18 Aug 2020 08:57:17 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1k83wO-0003Q1-2b for ietf-http-wg-dist@listhub.w3.org; Tue, 18 Aug 2020 15:54:24 +0000
Resent-Date: Tue, 18 Aug 2020 15:54:24 +0000
Resent-Message-Id: <E1k83wO-0003Q1-2b@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 1k83wN-0003PO-BQ for ietf-http-wg@listhub.w3.org; Tue, 18 Aug 2020 15:54:23 +0000
Received: from mail-io1-xd44.google.com ([2607:f8b0:4864:20::d44]) by mimas.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <robipolli@gmail.com>) id 1k83wL-0007bT-Jl for ietf-http-wg@w3.org; Tue, 18 Aug 2020 15:54:22 +0000
Received: by mail-io1-xd44.google.com with SMTP id g13so7380453ioo.9 for <ietf-http-wg@w3.org>; Tue, 18 Aug 2020 08:54:21 -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=QsrnhBkld2sATVqq6C3MZmhn+umKREh/2cK74G5EbJs=; b=DX8q1vEpsPEhfDVTWyP9EaXqCgNfeVy2znDDreleld8bimZU2YqBJBGso7YHaLfpe9 Qsg9ljfvAgm2i/h5XT/969+Pklbao093EKCh6rcyISLkPJNPQWdqUqpZU2Yvr58tTeFK NtVv3IlduB18qnb5PcgAHafsr6+cQ5EUYxidyDF23kdTz0REa+r6vF/jzH+DXgPdSNt1 ki84dc3vsZeMLXLC9Sf9NuXwjQSCBQyDG17aw4p2UwfLMChFVitE3244emkBeBNNgRKv PIveKLrJ3gfAueez9uPeyoRrnR1muEE+CcMdhhYp8V5Kfx8eKs2gfswyJq87B+xLiRrP E1Kw==
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=QsrnhBkld2sATVqq6C3MZmhn+umKREh/2cK74G5EbJs=; b=t17LfWSnPCgpS9vhIifhhs9uQD98lTAK+pBYs1isadRDpV9k5b+Y0InZQ2XU872CU8 kqIvJVPkUwkRMHsznDdZoiNIoh/stKh3o5mdB3I9Hpa6HhOZOAW4ea1Wx3/hQifXiDWv uMmbw6yn8tueov1XCN+wvVLTLQp9gEkoRsuZl8loxv2apJ+v5lt1hM8vy3plRBySm611 Bx1dfV/0rztrI2cRz6/scYYP2WWSBleLHowYwRz4A7cA2csYFeottaS6aF7xAd3mumaQ KB5U2NsppGwWFu+goynlXM1LI5T9zOh6L8vSkxjuwpGfhAgY5eAFH1B2rdHi6LVKyZJE rgqA==
X-Gm-Message-State: AOAM532uTKQ1UJPeMMmkyE6lTgTafUKMEc4fE5D+cu3cVVy17RR88kot GnpcPt4srZkZg4jh/TlKVCBpzlVM61oA9K32UiE=
X-Google-Smtp-Source: ABdhPJywts9gW3QdNbeepHshodYEDt5cmx5Oq+5jSqFYoRBWp7ytLzI+cyjqkbYBppRCOk5aXH/MRyf/eUztghqnnNs=
X-Received: by 2002:a02:17c2:: with SMTP id 185mr20007042jah.65.1597766050483; Tue, 18 Aug 2020 08:54:10 -0700 (PDT)
MIME-Version: 1.0
References: <CALGR9oYCU2b3wiTFV8uNO37opK0XMgq_=D0sTyZVw8kVuKG+4g@mail.gmail.com> <c71669f6-bb90-1952-7ca4-2db42a64fe55@treenet.co.nz> <CAP9qbHUWV+bpoUYBD6ckD36i=uFOkkrQRB=zmNCLER2d4M+K8w@mail.gmail.com> <7025.1597764267@critter.freebsd.dk>
In-Reply-To: <7025.1597764267@critter.freebsd.dk>
From: Roberto Polli <robipolli@gmail.com>
Date: Tue, 18 Aug 2020 17:53:58 +0200
Message-ID: <CAP9qbHWCZRYY76+z124sCCwtdoA1+H6L-Wkkx4wgtbrtWBGQwQ@mail.gmail.com>
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
Cc: Amos Jeffries <squid3@treenet.co.nz>, Lucas Pardue <lucaspardue.24.7@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Received-SPF: pass client-ip=2607:f8b0:4864:20::d44; envelope-from=robipolli@gmail.com; helo=mail-io1-xd44.google.com
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, 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 1k83wL-0007bT-Jl a2fa0b13474c9d340058201dc936289e
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Digests: deprecating parameters?
Archived-At: <https://www.w3.org/mid/CAP9qbHWCZRYY76+z124sCCwtdoA1+H6L-Wkkx4wgtbrtWBGQwQ@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/37936
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>

Il giorno mar 18 ago 2020 alle ore 17:24 Poul-Henning Kamp
<phk@phk.freebsd.dk> ha scritto:
> > Can be a solution, but how can we express this field-value with
> > structured headers?
> >
> > Digest: sha-256=ababbababab;q=1,  sha-512=bfbfbfbfbf
>
> almost exactly the way you did (with OWS for clarity):
>
>         Digest: sha-256 = :ababbababab=: ; q=1 , sha-512 = :bfbfbfbfbf==:
>
> sf-binary is there for precisely a use-case like this.

While I like sf-binary, actual digest-algorithms define their own serialization
method (in this case it's accidentally the same of structured headers) but other
algorithms use eg. integer.

To support SF we could say that digest-algorithms like sha-256 and
sha-512 should be supported
in both sf-binary and the traditional token format.

I don't know if this can bring confusion or not though.

R: