Re: signatures vs sf-date

Watson Ladd <watsonbladd@gmail.com> Sun, 05 February 2023 20:40 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 F15CCC14EB1E for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 5 Feb 2023 12:40:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.751
X-Spam-Level:
X-Spam-Status: No, score=-7.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.25, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PX4253DfhGKo for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 5 Feb 2023 12:40:08 -0800 (PST)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA948C14E515 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sun, 5 Feb 2023 12:40:08 -0800 (PST)
Received: from lists by lyra.w3.org with local (Exim 4.94.2) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1pOllN-006IJq-7C for ietf-http-wg-dist@listhub.w3.org; Sun, 05 Feb 2023 20:37:25 +0000
Resent-Date: Sun, 05 Feb 2023 20:37:25 +0000
Resent-Message-Id: <E1pOllN-006IJq-7C@lyra.w3.org>
Received: from titan.w3.org ([128.30.52.76]) by lyra.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <watsonbladd@gmail.com>) id 1pOllL-006IIt-Er for ietf-http-wg@listhub.w3.org; Sun, 05 Feb 2023 20:37:24 +0000
Received: from mail-oi1-x231.google.com ([2607:f8b0:4864:20::231]) by titan.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from <watsonbladd@gmail.com>) id 1pOllF-00Aasv-2r for ietf-http-wg@w3.org; Sun, 05 Feb 2023 20:37:23 +0000
Received: by mail-oi1-x231.google.com with SMTP id 20so7506258oix.5 for <ietf-http-wg@w3.org>; Sun, 05 Feb 2023 12:37:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Nwftxrho3cwYokwUrxjkV1ufJ07dZuSyAfzlG8kfhzs=; b=i6ZC/mh88Gjjx32Qkn2ZEekNwaIf6X9tNkjh727B4bzpSgilD4cO1rm0/PiDNpnjNZ gcw2EkgKZ/yLefyTVZe3ab784lTaEGoYEvn6TyTSL0jgPRO2t348KVrvom2CBJyEp1Mm nWhQmDKv0E+WiiCZg4/mbzOz+nQtIyvAwibTCeUBEBlBm7rbJuGZPNmv3RI2bN+Nspvp 0Df3sRq+luUI7Jm6rISPo/cK/JqXL9jxS0Q+N8DTcYTtwpE/xf1EQUCD0nPR6fqncwqG jGLG92jpYU8n8duNoNv41f3ARg0D9E18I8OEFryf7f9XW01JEpFQbuS43wyG3XGqVGrF EkDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Nwftxrho3cwYokwUrxjkV1ufJ07dZuSyAfzlG8kfhzs=; b=V59HncSHzpT8yEFMZgFsnPfMIdFirwkf/THRZgn6dqnSgPrX6YQIo7+o9za0UsLe5c 9P+0235DkXosB90g+qYx/ZAeHvMGi6xdSDveenE8zMBXaOa/pED9R4lKLphvcm1LVnQi kzIwzjm2HTwMJPk/R1yjTa3oMFFMjT7MyKsLBjfvX9f5DUx1o5pKdZfKoGA7L0VfCtIy sgZkWYDJFMeeleIpgFVBDg2CLTriMb1kpp57zbHyU3VN3oo9Hsj1mowe/cmjMvwZtiVi BHzAa+aJnqzTu3gq19fPjxr9cShaxveZSPusKzJcRUlT2XW1RzkddBb/aXSE1i0CmMgu pcIw==
X-Gm-Message-State: AO0yUKXH04c64N0hlxJEfvpocixsp8VtuGb/Fs3JZyk5zCMxjNT3v63m MERp5s7sN6L2yWdwQK6LByDVpoQu7cGPLKAfoXM=
X-Google-Smtp-Source: AK7set+p2ZoJ8NwBj+PJypMQDOGc+Lmvtj0zspBI/f+l2jBbwcA2Z7+th+F0L/CHpYlR3WmlAe2U2Ich2QohP9Iw8FE=
X-Received: by 2002:a05:6808:499:b0:35e:166c:193b with SMTP id z25-20020a056808049900b0035e166c193bmr980034oid.84.1675629427618; Sun, 05 Feb 2023 12:37:07 -0800 (PST)
MIME-Version: 1.0
References: <9f446816-7588-46af-6501-3508c1993752@gmx.de> <3C1E02FA-C2AA-4420-B3E1-A482230E0BB7@mnot.net> <7e13ab91-0979-f545-7868-7991bc396490@gmx.de>
In-Reply-To: <7e13ab91-0979-f545-7868-7991bc396490@gmx.de>
From: Watson Ladd <watsonbladd@gmail.com>
Date: Sun, 05 Feb 2023 12:36:56 -0800
Message-ID: <CACsn0cmHeXw9jomcvuSWso24C0S-UHg2kVvHH7GYVxvHoM8ozg@mail.gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: Mark Nottingham <mnot@mnot.net>, Lucas Pardue <lucaspardue.24.7@gmail.com>, ietf-http-wg@w3.org
Content-Type: text/plain; charset="UTF-8"
Received-SPF: pass client-ip=2607:f8b0:4864:20::231; envelope-from=watsonbladd@gmail.com; helo=mail-oi1-x231.google.com
X-W3C-Hub-DKIM-Status: validation passed: (address=watsonbladd@gmail.com domain=gmail.com), signature is good
X-W3C-Hub-Spam-Status: No, score=-4.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_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1pOllF-00Aasv-2r 08b52c7341dbe4c1477b27a8484772ab
X-Original-To: ietf-http-wg@w3.org
Subject: Re: signatures vs sf-date
Archived-At: <https://www.w3.org/mid/CACsn0cmHeXw9jomcvuSWso24C0S-UHg2kVvHH7GYVxvHoM8ozg@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/50677
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 Mon, Jan 23, 2023 at 10:48 PM Julian Reschke <julian.reschke@gmx.de> wrote:
<snip much context>
>
> What I'm looking for is a strategy that avoid tons of flags in parsers,
> and confusing APIs when using them.

I'm a little confused by what you want. Is the situation the following:

I put in a new kind of field for a new field My-Field. That new kind
isn't understood by existing code, implementations that want My-Field
to be parsed need to update their parser to parse the new kind.

Because to me that's how everything should work. I'm not sure what the
alternative is: how do we expect to parse fields whose grammer is not
defined yet?

Sincerely,
Watson

-- 
Astra mortemque praestare gradatim