Re: Digests: deprecating parameters?

Roberto Polli <robipolli@gmail.com> Tue, 18 August 2020 15:04 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 15F033A0C30 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 18 Aug 2020 08:04:41 -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 eLkC9WJM8jeX for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 18 Aug 2020 08:04:39 -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 5FC3A3A0C4F for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 18 Aug 2020 08:04:39 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1k837X-0007PQ-QC for ietf-http-wg-dist@listhub.w3.org; Tue, 18 Aug 2020 15:01:51 +0000
Resent-Date: Tue, 18 Aug 2020 15:01:51 +0000
Resent-Message-Id: <E1k837X-0007PQ-QC@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 <robipolli@gmail.com>) id 1k837V-0007Oi-LM for ietf-http-wg@listhub.w3.org; Tue, 18 Aug 2020 15:01:49 +0000
Received: from mail-io1-xd29.google.com ([2607:f8b0:4864:20::d29]) by titan.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <robipolli@gmail.com>) id 1k837T-0000fU-Ku for ietf-http-wg@w3.org; Tue, 18 Aug 2020 15:01:49 +0000
Received: by mail-io1-xd29.google.com with SMTP id a5so21364905ioa.13 for <ietf-http-wg@w3.org>; Tue, 18 Aug 2020 08:01:47 -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=lb5WJx9Tbi35FEWTischOVU1uONtDOzEYM3FIGQhLn4=; b=hOs5r/kqa/kVH+XmJINIm0Q41Zcx9GORnkWLcp4ggHJyg8FP+2PeKzetFZnVfrqYsj U4gPRxILKKgj6qoMnKcFv99x4Dwq/HMr1TngqWx5wZIFN/mteWeYK1TsC1UOkca1jPD3 KI3MSzXmuFYChOdSjh9DM8h1Yi8ZowGh5/3UndJe5OMD65IKxuNsBQTiU/MYVvKDXUMU fCOhv1czKlu9W6l+CO7iZnxqtSIl01TqFJdFf/8H6nPRtuEGmmYoaKgvXwEylVVm3sSv aYGdAxejh5fu9lk3Ryv4xPVytLXGN21WicNI9vtXyg2u13Imp1tte/+5zJU/KMLGQAWl k2ug==
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=lb5WJx9Tbi35FEWTischOVU1uONtDOzEYM3FIGQhLn4=; b=iy9iUKFrkYdTxFDSaS5BjEUmwm4PYK2X3cfU7tasuizDL8ionQU1djg/hYm17kt6g0 8dFALyNHuui50JkOI4OSX7rRP1LgxK8H6PBytRZfrc738TLSdGaPeAHzNx8COSA5uEoV s2GTSJpgaN9tMZDF0EElj5mOrZn9ngNZzCY0UzPS6IegYeO6SXOQU8kOaoUb2ByYXhay lX/L7TQvyPeuOOPSiJrhseSmF2xxPPPKrlSqzCysy/ZYzjz2dPxLWK6uMwyXjRMHraHD KupnRtqevWLoQ9qAXEfWb+fcxIOFxnq3nD/D8U8W4X/C1vzplW3lPVOvSGgqkLNfgtQC e4Sw==
X-Gm-Message-State: AOAM530W7qE/liu7w/aXOawKxtZDgsUaOq4Y2dy9S2qex1HLfMZxmQVU DxH14qc6B2VIVPaYE1WYFgsd1cKZkpasobaD42Gz/WkjUUE1Kw==
X-Google-Smtp-Source: ABdhPJxyNAz9uiimaP69+JEtb4llHaxmtemtR/inaTAGY3lvcn8RwqgUk3Pu+vU1WOJ770QbGPx52HPOOMMd3gykepY=
X-Received: by 2002:a02:a389:: with SMTP id y9mr18890251jak.82.1597762895956; Tue, 18 Aug 2020 08:01:35 -0700 (PDT)
MIME-Version: 1.0
References: <CALGR9oYCU2b3wiTFV8uNO37opK0XMgq_=D0sTyZVw8kVuKG+4g@mail.gmail.com> <c71669f6-bb90-1952-7ca4-2db42a64fe55@treenet.co.nz>
In-Reply-To: <c71669f6-bb90-1952-7ca4-2db42a64fe55@treenet.co.nz>
From: Roberto Polli <robipolli@gmail.com>
Date: Tue, 18 Aug 2020 17:01:24 +0200
Message-ID: <CAP9qbHUWV+bpoUYBD6ckD36i=uFOkkrQRB=zmNCLER2d4M+K8w@mail.gmail.com>
To: Amos Jeffries <squid3@treenet.co.nz>
Cc: 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::d29; envelope-from=robipolli@gmail.com; helo=mail-io1-xd29.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: titan.w3.org 1k837T-0000fU-Ku 77012bdc76cf78df221ef78be8e018ab
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Digests: deprecating parameters?
Archived-At: <https://www.w3.org/mid/CAP9qbHUWV+bpoUYBD6ckD36i=uFOkkrQRB=zmNCLER2d4M+K8w@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/37934
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 14:42 Amos Jeffries
<squid3@treenet.co.nz> ha scritto:
> there could be a specification which defines
> a parameter which is relevant to all algorithms but is optional. Eg a
> "q=" or "charset=" parameters.

While this seems to me an overthought respect to RFC3230,
 I cannot exclude this remote possibility.

> I think this would be a good time to refer to the structured headers
> document as a syntax basis
> <https://tools.ietf.org/html/draft-ietf-httpbis-header-structure>.
> That documents the possible existence of parameters even when they are
> not specifically defined by the header document (eg RFC 3230

Can be a solution, but how can we express this field-value with
structured headers?

Digest: sha-256=ababbababab;q=1,  sha-512=bfbfbfbfbf

Thanks to everybody,
R.