The "enhancement" link relation - #257
Merged
Merged
Conversation
Another ACME option. Fourth time's the charm? :-)
davidben
force-pushed
the
link-rel-enhancement
branch
from
June 24, 2026 00:01
1dbc067 to
58659cd
Compare
aarongable
approved these changes
Jun 24, 2026
Co-authored-by: Aaron Gable <aaron@aarongable.com>
lukevalenta
approved these changes
Jun 24, 2026
mcpherrinm
added a commit
to mcpherrinm/cactus
that referenced
this pull request
Jun 24, 2026
Re-introduce the landmark-relative cert over ACME using the new "enhancement" link relation (ietf-plants-wg/merkle-tree-certs#257), instead of the rel="alternate" form that was removed for stalling clients. The standalone /cert response advertises Link: <.../cert/{id}/landmark-relative/{number}>;rel="enhancement" An enhancement is an optional, non-blocking substitute: the URL returns HTTP 202 (Accepted) until the covering landmark is allocated, then the signature-free landmark-relative cert. Clients retry the 202 honouring Retry-After but never block deploying the standalone cert — so a not-yet-available landmark can't stall issuance the way the old alternate + 503 + Retry-After did (lego's go-retryablehttp treated that 503's Retry-After as a multi-hour blocking sleep). The URL pins the number of the single landmark the entry is relative to (ContainingIndex), making it an immutable resource: 202 until that landmark is allocated, the same cert bytes forever after, and a permanent 404 for any other number. Retry-After is derived from the remaining time in the §6.3.2 landmark interval, so it reflects when the cert is actually expected. Adds landmark.Sequence.NextNumber and TimeUntilNextLandmark; re-wires the acme.Config landmark fields; new tests acme/enhancement_test.go and integration/landmark_enhancement_test.go; updates README/MTC/test-instance.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Another ACME option. Fourth time's the charm? :-)