IETF Logo Mail Archive

[httpapi] Link Hints?

Mark Nottingham <mnot@mnot.net> Wed, 19 July 2023 21:03 UTC

Return-Path: <mnot@mnot.net>
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 6B736C151532 for <httpapi@ietfa.amsl.com>; Wed, 19 Jul 2023 14:03:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.796
X-Spam-Level:
X-Spam-Status: No, score=-2.796 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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=mnot.net header.b="oeYT8Mr8"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="gZJdQ6yk"
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 mh4uz-7Gz_4n for <httpapi@ietfa.amsl.com>; Wed, 19 Jul 2023 14:02:59 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 7A894C151546 for <httpapi@ietf.org>; Wed, 19 Jul 2023 14:02:59 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 0E1C45C0068 for <httpapi@ietf.org>; Wed, 19 Jul 2023 17:02:58 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Wed, 19 Jul 2023 17:02:58 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:message-id:mime-version:reply-to:sender :subject:subject:to:to; s=fm1; t=1689800578; x=1689886978; bh=rN wkJJWttCv4+p4ZrB+n9uv2r1+79DVPO9tLtdgDtOY=; b=oeYT8Mr84/wNOM7HUU fUZnoenG3oMJRVlp72mA2W+k1ns0Sn9pwnymLFgFotEjPEwypj98m8m7B5BqIn20 Xh4XZFHh2KxmPpszvP06yD/6WFwLPLXOB+fpXHFklo95QhnR9GT8rXzOiKrrQO1M ow13MDYvln9iZVajQdOmIVi4RcqwVK4eQxMueFQmnD/34/Xnbrgz9oeyk38Nj4+5 qjB7DoUkYEA0FvHhYOgTsfv5O0hUeUaR+14VTjMA23P/7DShNHf4CQ/KEg1ai5bA Ny0RtFm4e8E96WpPeSh0Mvw43OZUXzn3JvW3l2IfRI96F115s4TjwnWU1QLe+nK4 suag==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:message-id:mime-version:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; t=1689800578; x=1689886978; bh=rNwkJJWttCv4+ p4ZrB+n9uv2r1+79DVPO9tLtdgDtOY=; b=gZJdQ6yk5gLersTLqeHo3pfDAu3dL 7Jmk95GYnQH4HjfTEXplhvsIAPPuKoJrxy62GK4OKL4iwwz9r+/BMKmPUlu20/GM EJ9SuQXQIv3hL9kL0w4gyVTiRgDowGA2KSO+k8RCh4l2gWjCsLuiVgnT6rWP41il ftjjfXH/jaZX6Xk5p5QV1+MrvWPTLB7o4RUGMj7K2d8taRWSh7MlM9jkMpBEmKQm Ip3O5s5aSM22gP8btSul+qHOwXXifvlWQpa/CG/W1HGnNgcCyengarpHDadHSmzJ 60UNuYodEGGZw0mcIg7Yneom5izO0sYxUiZEiGZ/F0k+HjHHYRxQ7wO1Q==
X-ME-Sender: <xms:gU-4ZHt3V7xXq5gNVHfFQ06BVwcWXzHT0p-4cVdpvi0VHFxfJSA-rA> <xme:gU-4ZId98N3jRx3CDwkSfYXAa3p7xdjX1bsNuaK2vkx29x2HaM5L1XuLiujzldjaw -bTFuiaiXciz4yTeg>
X-ME-Received: <xmr:gU-4ZKwUAVIPT-o5h5XkQ6TCZi8H2BLjfH-9tp9XDQihPCacSj531GZiqzB7lvYcXYwqZhY0nLxavAAq8U9_1c5ttL4depvjUGYvvjs_uEap>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrgeekgddufeelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephfgtgfgguffkfffvofesthhqmhdthhdtvdenucfhrhhomhepofgrrhhkucfp ohhtthhinhhghhgrmhcuoehmnhhothesmhhnohhtrdhnvghtqeenucggtffrrghtthgvrh hnpeejveehgeekleduieegffdtudfghffhiedttdeigfevffdtudeiieffjeeggefghfen ucffohhmrghinhepihgvthhfrdhorhhgpdhmnhhothdrnhgvthenucevlhhushhtvghruf hiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmnhhothesmhhnohhtrdhnvght
X-ME-Proxy: <xmx:gk-4ZGPBe14c4wngk6Yr-D4UHe5CWYlySeJ6snTP46CzxGNMkj1NMQ> <xmx:gk-4ZH8N-McMqw7Y_wk_4-AOtUtWd_o48-orxAB1j7S56MUG5zLTEA> <xmx:gk-4ZGV1uBSWlR4hGGM_moLz6rEep_nFMLYHDl-bNJVuQjEJsN8txA> <xmx:gk-4ZEI6Pmdnv8L-EJ4-V97KExrm5uwlKlzb4DtwdnU5aJ80xmMguw>
Feedback-ID: ie6694242:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <httpapi@ietf.org>; Wed, 19 Jul 2023 17:02:57 -0400 (EDT)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\))
Message-Id: <10303857-C095-44BB-850F-0F6B09D9C875@mnot.net>
Date: Wed, 19 Jul 2023 14:02:57 -0700
To: HTTP APIs Working Group <httpapi@ietf.org>
X-Mailer: Apple Mail (2.3731.600.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/KB_ICqzR-BukYzlMfTWs5lP_JXc>
Subject: [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: Wed, 19 Jul 2023 21:03:04 -0000

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).

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/

v2.23.0 | Report a Bug | By Email