IETF Logo Mail Archive

Re: [httpapi] Structured Fields for HTTP APIs

Roberto Polli <robipolli@gmail.com> Wed, 01 February 2023 13:12 UTC

Return-Path: <robipolli@gmail.com>
X-Original-To: httpapi@ietfa.amsl.com
Delivered-To: httpapi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 338BEC16952C for <httpapi@ietfa.amsl.com>; Wed, 1 Feb 2023 05:12:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 tagged_above=-999 required=5 tests=[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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 PHGYJvFkoi9Y for <httpapi@ietfa.amsl.com>; Wed, 1 Feb 2023 05:12:29 -0800 (PST)
Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFB91C14F731 for <httpapi@ietf.org>; Wed, 1 Feb 2023 05:12:29 -0800 (PST)
Received: by mail-pj1-x1036.google.com with SMTP id m11so17307541pji.0 for <httpapi@ietf.org>; Wed, 01 Feb 2023 05:12:29 -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=XhIhSNhRxT5t0notQFkQrGNB8T4cQ+CqpU1A24Hpk5I=; b=bFX3PI8ZFPz6DmFJRbcagqIItKMKEs/K+f6fCGeZnafg4UAKoRV6TyEhW7gdUMoHF6 ilWSmTjEADeSwrjdw9XbSfkZS/3aubSga2hmm2LxZVyNPVz5tZFda6nAZyf5UaFIwG/6 2pRwtNpx/0ir+m1KuLk+QHPM0UnFyw/vhKgZiF2w9KWLD2oMZ/MYFkJOFmR/Ni+Q5szw yciUBJa565qPCaoWv1vVIY75nzHpoo5Y+2t8j9TjjDh8yQH+YyQpGAuGecFtsfJtUUQU 81K+ORq9DL/SL0citeSVnfb5mLGFeSR8w5HnLtgBHRAEDWkJ5CnvK2RjXrNWQ4TcP9qx jKhA==
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=XhIhSNhRxT5t0notQFkQrGNB8T4cQ+CqpU1A24Hpk5I=; b=eX3Uy3Qm7DXTFIIK2w8YHbxZrXR3flbMqtDJ7tspawSZ1kMZ97i1LLec9GpxOwzJvy ZedOcHcQ2rMZtKGjVHOKqQy7zu/lOKcYzZzJaYaqvsxJCdZBJi6zc5ZHTdGYpvDjKzuE ne0km6LdBDW5mzYyaVGU7ob9uKs89lqEfo0xS2EPPeTJ7qX7YXOyHfxC4phF2gBIKL1L ugmz0b/1N3aa0YKswSP/X2RJXRUsI2GTXqe4z6wMd7HFQXM8RTyllkFXdMTs6F6HfUkb CdaR/tvwsKKMMn8dO6jUEuBFxAesidhFkGhXXLPKNDA6EydjzYtIGWKnSpm6SJlOL+3a Vxbw==
X-Gm-Message-State: AO0yUKWHsZCwrZWXHbMOpVb4GoL1sob2JwCVR5+mASQon1m9go4WPmkT XSGYr09xK17RpF6fgh/O3amPNL8Cm9kUgLvBeK8+hOne2S8=
X-Google-Smtp-Source: AK7set9gMuvwzqlTAXFjo/A8En0T42trhS+aK16oPLrOvJddACWl6o09RdNcai84SI5ZS2aNBw5Un4Qe+p8JSXdEdFM=
X-Received: by 2002:a17:90a:43a3:b0:22c:4d5:38be with SMTP id r32-20020a17090a43a300b0022c04d538bemr382666pjg.42.1675257149306; Wed, 01 Feb 2023 05:12:29 -0800 (PST)
MIME-Version: 1.0
References: <DM6PR01MB59649603A686559109383E41A3C89@DM6PR01MB5964.prod.exchangelabs.com> <479442be-2bd2-3e0c-9c75-655e62d3af26@gmx.de>
In-Reply-To: <479442be-2bd2-3e0c-9c75-655e62d3af26@gmx.de>
From: Roberto Polli <robipolli@gmail.com>
Date: Wed, 01 Feb 2023 14:12:17 +0100
Message-ID: <CAP9qbHU7DfPgHUP_GyvtJC1HfwMUj=rqZSR2c7U+yGho=JU0Ow@mail.gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: httpapi@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/sxzo2bTOgKXdJ3EKm9ftGqAZK3k>
Subject: Re: [httpapi] Structured Fields for HTTP APIs
X-BeenThere: httpapi@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Building Blocks for HTTP APIs <httpapi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/httpapi>, <mailto:httpapi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/httpapi/>
List-Post: <mailto:httpapi@ietf.org>
List-Help: <mailto:httpapi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/httpapi>, <mailto:httpapi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2023 13:12:35 -0000

Hi @all,

On Tue, 24 Jan 2023 at 11:04, Julian Reschke <julian.reschke@gmx.de> wrote:
> On 23.01.2023 14:51, Darrel Miller wrote:
> >  [..] If headers with unknown
> > syntax are a problem for existing tooling, how has that tooling survived
> > the introduction of any new header over the past decade? [...]

> the question in fact was a bit different - use SF to combine
> multiple related things into a single field, or use multiple fields so
> it's easier to extract the various parts.
> With the latter approach you actually do not need a new field value
> parser,

Yes Julian, you got the point.
In general, I question whether it is sensible to
enforce SF usage in API contexts where consolidated practices
(that we might like or not) already exist.

Similar considerations are ongoing during the dpop review in the oauth wg
https://www.mail-archive.com/oauth@ietf.org/msg22114.html

Have a nice day,
R.

v2.45.0 | Report a Bug | By Email | System Status