Re: Guidance on the "enhancement" link relation type for PLANTS

Mark Nottingham <mnot@mnot.net> Mon, 29 June 2026 23:37 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: link-relations@mail2.ietf.org
Delivered-To: link-relations@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 0017810A46D9F for <link-relations@mail2.ietf.org>; Mon, 29 Jun 2026 16:37:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1782776254; bh=kNUtRPq85B7AxcSyE+V3iTTRwYsgY1hbTDlGamrwBh8=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=Scj38kuMFLiJ466cZsASKylrrW0aYb55q/Ptx2oIqkqHh+WAY9vvwHevsCDoJXSyH +p/bGgGHww0LgwBHiIHg4jXpQF+g6Xfi6AiW8WA/57LnXjwapw4Q0eUiiUVa4WwXyk +x21QVyyHpEXKW5U4kHayvqGAT0vi9vglfANqoNA=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level:
X-Spam-Status: No, score=-2.799 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_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b="d4U6+gcK"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="iV5K/HKr"
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aMbzLlN3CySL for <link-relations@mail2.ietf.org>; Mon, 29 Jun 2026 16:37:32 -0700 (PDT)
Received: from fout-a2-smtp.messagingengine.com (fout-a2-smtp.messagingengine.com [103.168.172.145]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 5A3E110A46BF9 for <link-relations@ietf.org>; Mon, 29 Jun 2026 16:36:54 -0700 (PDT)
Received: from phl-compute-02.internal (phl-compute-02.internal [10.202.2.42]) by mailfout.phl.internal (Postfix) with ESMTP id 4120CEC01F4; Mon, 29 Jun 2026 19:36:48 -0400 (EDT)
Received: from phl-frontend-04 ([10.202.2.163]) by phl-compute-02.internal (MEProxy); Mon, 29 Jun 2026 19:36:48 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1782776208; x=1782862608; bh=AeJDtiQhCUtUIsfNofoOT3tYYW2xkJnWff/Uwiu1+Vs=; b= d4U6+gcKSfzpYoa4FtLM8EGfNW1D0AhmdN7k9dsbUypisZ+oMc1OXnRQOFgxg9V0 318vCCc9rUBKxxKRHvZi/H3uOxdazLwphLrX98/lbImAQHmHx76s1b/uzji5cdp4 7xVlpQ6teQPL/MdtK6H0fvyb/hJkF3H+oxLphsa8Lt0fAqk2X1G1AS1XtmbkwJr8 +WhtY2kGcA7fV5md3zdhphTykjWx6ugw3H1WOPOFErkg808n5S9wYEwCtcqYIMDB tbZY6l/IKOQ6vwcHnz7brLww2LHVh6SnyJGkDAfDeolD5hNhp7bX9avuiMeOYEQr UT7/mhFODqejVGS7NLcXxQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1782776208; x= 1782862608; bh=AeJDtiQhCUtUIsfNofoOT3tYYW2xkJnWff/Uwiu1+Vs=; b=i V5K/HKrgU/GNOGKor5a9OovSNm7Ol9ri3AejirAJZ30YczjVyzRsor4UpjcsCGsf aF8E1yLBV42oE58B5pJ9Y0xvSE4/bgr3rsU3xCErX7Ucsz8uClMABT24ovb2eQMx cFe43bNxAShcSpGZ8IYJO55Y6JXyMnlngiEChrdyEomXNuY0YoBjJWnDYR8PspiX oWu9srvons4WuxBK+ZnNYUknKB8NuCUhGMrDg+u5xCdwy90rnomd6V7JFdvlL1hh UZB1+5Uhc05Fjt3Lj85R5NmYD82dN2UyuGJhakOSouAcurAAgpi3+E6GnAEA8TVg lnbtyZNxVY4GGIAHZo4Lg==
X-ME-Sender: <xms:kAFDamTmg09FNS2u1t7Fc2jxmQBkJRXnucDizoeS9z9JkEk7c6mJHQ> <xme:kAFDaoHdATqJQNRvMms2e_q2va_2ckNdPODYR-QK2DO-mHGjeYZ9bcmB-6bBPTutv tCY6q_4LkYp3gaZgyXia_VmPXyIW55lRxf92Y0HGRgEEb966Sbz>
X-ME-Received: <xmr:kAFDamk_uH-b9W-Cv1adEx-7XSACDEQ3JTcLCTy-GnUjh_ZAoL4WUbkNU5jF4qdSnsc5Zsmp_uOWWRnnLBWkVA2719eKRQyO0HMWaSBwCrJTwNWVwPYU8Q>
X-ME-Proxy-Cause: dmFkZTEQ8Vd0oAzSymfeU+veXNUY5dvCkgJNS2SRHL3j8gQ4AdW1dZpA+pkGFa/Wgjyb/C L0eLay75JLBLR8AkjvOJfSCC7JtariKpyqTnwd1sJd8NYrOy9ViBsRFT/B3FElLuuH3/xB mTreFP7f8TwzHEck+OFk4ofRQUvOOZspmlbb/xpk0P/N/TUHCGv88D5eD7lUor92G1dEPE qlnc7r5zIvYHGKrR+Pd+2cUldVud/uQ2fNkQdNCctevTh0FzEt2yE+KnLAO2pEPar1zCIC l56aCZFAUylTCYfjWXia191/xvwi5148j2V0gb5CJFPQA9wlkzu2YWi8EUNhvCxJO+1TPp nNJzVgb2wnp0KT/NblikONdv9bBbO1Ro65pQloS2Fl7CFFxsjM6Etz9VvCdPTYETp9y9yT ci4D6EZwJH+4OiwRo3H37wLwOLreO2/VlpxMLWx3ttXZuDHcE/doGjJ53QBU16kHImKSsJ 3IwKIIgGsc4zfj0Br+OTX1nnKjnHFRY2ipfNSLnEV1BubJ9ExjFL8UpmYPFbtJb8Ky5LJp /BF6v1C/o2YspC8bWTVss7e6Ih24k1g6WJoh2CJNlgCk/O9ONVq1uD/ImkS/rKuVToeMBD WoZOc9byv2YyzXpwGq71m+GUIwvk8201xdC7CL6ofnJHuEWzZL+c/OLHfhmg
X-ME-Proxy: <xmx:kAFDaj31ykUYKgfr8Za2lM9kqMqAWMjLfFH-FdHzD7H6szA5bMH4Kg> <xmx:kAFDaiQvRD5CR5Vqvu9IWpVta-Rg4dViLtmfIZHkTJYTEg34Yg9ABQ> <xmx:kAFDaluzbJqhxjIiOv-BdEwG7LQYdp7i71DVF908o8RcVm-5chhihQ> <xmx:kAFDanadFpWn0qxLwdKTlRoKyAerdnSs4Q5qWNysMBv8kj5XtGySLA> <xmx:kAFDauHNTzpAxBsqCt3XxAibdFPagtkWLIoKsbuP4ocq1Zeiiega8P9G>
Feedback-ID: ie6694242:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 29 Jun 2026 19:36:46 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.600.51.1.1\))
Subject: Re: Guidance on the "enhancement" link relation type for PLANTS
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAF8qwaADRch=6yfKc8SfEZVoX48jTjwHTnvjpALUvGOGH3Mf+g@mail.gmail.com>
Date: Tue, 30 Jun 2026 09:36:41 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <8177B380-20C9-4549-A7A5-5482EF9FF02F@mnot.net>
References: <CAF8qwaADRch=6yfKc8SfEZVoX48jTjwHTnvjpALUvGOGH3Mf+g@mail.gmail.com>
To: David Benjamin <davidben@chromium.org>
X-Mailer: Apple Mail (2.3864.600.51.1.1)
Message-ID-Hash: EM3RW6XJ4652D5KIEQ37ITH75TCMXSLS
X-Message-ID-Hash: EM3RW6XJ4652D5KIEQ37ITH75TCMXSLS
X-MailFrom: mnot@mnot.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-link-relations.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: link-relations@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: Discussion of registration requests for link relation types <link-relations.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/link-relations/KCujQmQLTFlUKsrGvvW2zZXhSc0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/link-relations>
List-Help: <mailto:link-relations-request@ietf.org?subject=help>
List-Owner: <mailto:link-relations-owner@ietf.org>
List-Post: <mailto:link-relations@ietf.org>
List-Subscribe: <mailto:link-relations-join@ietf.org>
List-Unsubscribe: <mailto:link-relations-leave@ietf.org>

Hi David,

Generally, I see two kinds of link relations out there:

1) Generic, broad-semantic ones not attached to any particular protocol (e.g., "next", "alternate"). They need to be interpreted within the context of a specific protocol to interoperate.

 2) Protocol-specific link relations that do what they say on the tin. <https://www.youtube.com/watch?v=f8v_RqanM74>

My observation is that the first kind almost inevitably involve a certain amount of hand-wringing about whether the semantic fits, whether it's an appropriate use, and whether it will be interoperable. 

There are certainly cases where broad-semantic terms are useful, but they tend to be in cases where the semantics are more directed at human interpretation, not machine-to-machine interoperability. 

So, my advice to folks seeking a new link relation is to define a specific relation if they have a single use case and it's focused on protocol interoperability; it's only when you have multiple use cases *for humans* that you'd consider broadening to a generic term. It's true that a lot of existing link relations are broad, but I'd argue that's an artefact of history and ambition, not good protocol design.

Here, all of that would lead me to something like `acme-landmark-cert`. 

Just my .02.

Cheers,




> On 30 Jun 2026, at 4:42 am, David Benjamin <davidben@chromium.org> wrote:
> 
> Hi link-relations folks!
> 
> I wanted to get some feedback on the link relation we've added in PLANTS WG, for use in ACME. Particularly on whether defining a generic link relation type is appropriate here.
> https://ietf-plants-wg.github.io/merkle-tree-certs/draft-ietf-plants-merkle-tree-certs.html#name-link-relation-type
> https://ietf-plants-wg.github.io/merkle-tree-certs/draft-ietf-plants-merkle-tree-certs.html#enhancement-link-relation
> 
> Some broader context:
> 
> ACME an HTTP-based protocol for getting certificates. Sometimes, in response to one ACME order, an ACME server would want to send multiple certificate chains to the ACME client. We have two related, but subtly different use cases:
> 
> First, there is an existing ACME construction. It uses the "alternate" link for the ACME server to deliver an alternate certificate chain that, e.g., ends at a different trust anchor. This might be needed because, for example, the authenticating party needs to present different certificate chains to different relying parties. (Typically the authenticating party is a TLS server and the relying party is a TLS client.)
> https://www.rfc-editor.org/rfc/rfc8555.html#section-7.4.2
> 
> Then we have "landmark-relative" certificates from PLANTS. This is a slightly different signature over the same certificate, such that:
> - It is much smaller than the normal "standalone" certificate
> - It only works for up-to-date clients
> - It takes (e.g. an hour) before the certificate is available, due to some batch processing
> 
> On its face, this is a very similar use case to "alternate". However, existing ACME client software will error if it fails to fetch some alternate. That means trying to model the delayed response first poses a compatibility problem.
> 
> More than that, the compatibility problem perhaps points to a deeper distinction. The erroring behavior is defensible in this context. An ACME client is trying to provision the TLS server so that it is able to serve TLS clients. If the ACME server says "here are three chains that satisfy your order" and one is missing, the ACME client does not have the ACME server's complete response. Maybe this missing alternate was the one that this class of TLS client needed. (If you narrow to just how the TLS client trusts a given (identity, key) binding, you can think of the ACME client and TLS server as a funny intermediary in the overall CA / ACME Server -> ACME Client / TLS Server -> TLS Client communication flow.)
> 
> But, with a landmark-relative certificate, the certificate won't be available immediately, and we don't want to block the overall transaction on it. Proceeding without it is fine because it's the landmark-relative certificate is designed to be optional. Any TLS client that accepts the landmark-relative certificate is expected to also accept the standalone version.
> 
> And thus the idea that we use a new link relation, with similar semantics to alternate, but carrying this extra optionality semantic. With "alternate", the pattern is that we have a general link relation that ACME defines specifically how to use in its context. Patterning after that, we've tentatively called this "enhancement" and given it a general definition with separate guidance on how ACME specifically uses it.
> 
> Thoughts? Does all this seem reasonable to you all?
> 
> David
> _______________________________________________
> link-relations mailing list -- link-relations@ietf.org
> To unsubscribe send an email to link-relations-leave@ietf.org

--
Mark Nottingham   https://mnot.net/