IETF Logo Mail Archive

Re: [httpapi] Link Hints?

Herbert Van de Sompel <hvdsomp@gmail.com> Thu, 20 July 2023 06:15 UTC

Return-Path: <hvdsomp@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 C6A10C151711 for <httpapi@ietfa.amsl.com>; Wed, 19 Jul 2023 23:15:38 -0700 (PDT)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 OmwGi0PQtDOy for <httpapi@ietfa.amsl.com>; Wed, 19 Jul 2023 23:15:34 -0700 (PDT)
Received: from mail-yw1-x112c.google.com (mail-yw1-x112c.google.com [IPv6:2607:f8b0:4864:20::112c]) (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 74AC3C151077 for <httpapi@ietf.org>; Wed, 19 Jul 2023 23:15:34 -0700 (PDT)
Received: by mail-yw1-x112c.google.com with SMTP id 00721157ae682-57026f4bccaso5107267b3.2 for <httpapi@ietf.org>; Wed, 19 Jul 2023 23:15:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1689833733; x=1690438533; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=MVN51YRMmiyf7F3jyAdOS4cYXi7+/UBmAwWqfpUttxo=; b=ceex1KiiTa7h2KDaf2U5IlooytRQPXLh+czzO9HbEc4Xan2ue0a5eEXwKrKGUEZqhl u5jIdtV1e3H6ZVOcqkQnhMyS3en0i2kreCA5rvwy6Fr+bfYYxY6QpVgRhFs05gcwhptU SqA7HdvysQQL4LM0cy6WP77Iutn4nI3Ry05NX7zAlMqUWvNUpzjD1pcl/xAe8F2iNIKX EhDpo7F37K0zJS73thCqFlXLanyCJlbNQ9vm1b+xvqlDymIblrlDs2/Ye6VdO/J6F8Ve DTIrQqcG8tXgm1qEvmCIQPqPf6tAojyKRhMmgxkrEjepGeoH5CpBkq2HXv/5s07jVQEX h0Ig==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689833733; x=1690438533; 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=MVN51YRMmiyf7F3jyAdOS4cYXi7+/UBmAwWqfpUttxo=; b=fGe5psNAl/dvwl9H7nDqTXFlW2daHR83QPiB6fGQInTRc03lnz3MSxaOmfpIgJnfUm bW25tP2SM8KnOh4kQVXV8PfCEKAEd6K7rzST3vQ6nUE1b4XwJQClEbzniARPh4cwRpuV 3prs8kLueGdl/dilYbfG7AyZig3eLc7ZWw/TCYqeukkbzqTNeXgPuBM1R1EuGY0OrOKE CBQYnMO5EqhC7gdkoyp5zoHGv/ZMBluRtrlebZoBvFlqcR+FCXYcWL6MeyGkAd4Kfabc gNxICncUt08Bd4ig4rZdvKyDC99JjaIGJZDxqpZMNCOl6PPL6eMsvvMIUVqTL8VVDaPd Z+xA==
X-Gm-Message-State: ABy/qLYcsNMOl9nEgaWfeovDngpkh+c57NE+U91HdCoJ1cCdMgddKWX7 o4+OZDV+T5/UUKQP7FwaIIA1mgUtZdXBn2bm5L8=
X-Google-Smtp-Source: APBJJlHdzyj+SoyxKe/wQAj3MLYhHLVWICxAty4091qnplXZ490BuBlNjGmXKBpigWnBu5O0wvziACmVMBYcL3d08Go=
X-Received: by 2002:a81:9251:0:b0:581:2887:22be with SMTP id j78-20020a819251000000b00581288722bemr1297613ywg.37.1689833733439; Wed, 19 Jul 2023 23:15:33 -0700 (PDT)
MIME-Version: 1.0
References: <10303857-C095-44BB-850F-0F6B09D9C875@mnot.net>
In-Reply-To: <10303857-C095-44BB-850F-0F6B09D9C875@mnot.net>
From: Herbert Van de Sompel <hvdsomp@gmail.com>
Date: Thu, 20 Jul 2023 08:15:22 +0200
Message-ID: <CAOywMHfHBbi=BtG+vxZvxg+r075cyLQu1d8YwJ-Be7jRnUNXwA@mail.gmail.com>
To: Mark Nottingham <mnot=40mnot.net@dmarc.ietf.org>
Cc: HTTP APIs Working Group <httpapi@ietf.org>, Herbert Van de Sompel <hvdsomp@gmail.com>
Content-Type: multipart/alternative; boundary="00000000000069480b0600e513ff"
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/HO5-YJXuFF-c_1Y50Bikm7lfgUI>
Subject: Re: [httpapi] Link Hints?
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: Thu, 20 Jul 2023 06:15:38 -0000

On Wed, Jul 19, 2023 at 11:03 PM Mark Nottingham <mnot=
40mnot.net@dmarc.ietf.org> wrote:

> Hi HTTP API folks,
>
> A longish time ago, I wrote a spec for 'HTTP link hints' that describe
> aspects of a HTTP resource in a fashion that's suitable for adorning links.
> For example, the media type(s) available on the other end, and the HTTP
> method(s) it might support.
>
>   https://datatracker.ietf.org/doc/draft-nottingham-link-hint/
>
> This is to a large degree paving the cowpaths that have been created in
> HTTP (e.g., the Allow header) and HTML (e.g., the 'type' attribute on
> links) in a way that they can be used in anyplace a link can. It's also a
> way of coordinating common link attributes, because RFC8288 makes
> attributes per-format.
>
> I didn't push for standardisation because I wanted to make sure there was
> actual need for it / interest in it. I've heard some of that in backchannel
> recently, and was wondering what the WG thought about adopting this (or
> something like it).
>
>
Link Hints is a building block in the Profile Negotiation I-D (
https://datatracker.ietf.org/doc/draft-svensson-profiled-representations/)
of which I am a co-author. The I-D is expired but we plan to resume work on
it. So, we're definitely interested in Link Hints because, without it, we
would need to look for another approach to handle functionality that is
currently covered by Link Hints.

And, since I am on the topic of the Profile Negotiation I-D: I was
wondering whether there are any new insights regarding the WG it would best
fit in. There was some back and forth about this quite a while ago that
didn't yield an outcome.

Greetings

Herbert



> Cheers,
>
>
> P.S. Chairs I'm happy to chat about this for a few minutes next week if
> there's time in the meeting. If not, no worries.
>
> --
> Mark Nottingham   https://www.mnot.net/
>
> --
> httpapi mailing list
> httpapi@ietf.org
> https://www.ietf.org/mailman/listinfo/httpapi
>


-- 
==================
Herbert Van de Sompel
https://hvdsomp.info
https://orcid.org/0000-0002-0715-6126

v2.23.0 | Report a Bug | By Email