add(considered): IANA permanence is not adoption for webhook-authorized-senders - #157
Draft
jdevalk wants to merge 1 commit into
Draft
add(considered): IANA permanence is not adoption for webhook-authorized-senders#157jdevalk wants to merge 1 commit into
jdevalk wants to merge 1 commit into
Conversation
…ed-senders /.well-known/webhook-authorized-senders.json is registered permanent (change controller Intempus ApS, 2025-09-29), but the registered reference is that company's own page and we found no second implementer. Permanent status means the suffix is stable and will not be reassigned — not that anything reads it. Standard Webhooks, the multi-vendor effort over the same ground, verifies senders with HMAC/asymmetric signatures and an explicit trust list of public keys rather than a discovery document, so the pattern is contested as well as unadopted. Turned down on adoption grounds per the routine; recorded rather than dropped. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Deploying specification-website with
|
| Latest commit: |
ad562d1
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://383cdab0.specification-website.pages.dev |
| Branch Preview URL: | https://add-considered-webhook-autho.specification-website.pages.dev |
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
1 participant
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.
What changed
One new
/considered/entry:/.well-known/webhook-authorized-senders.json, turned down on adoption grounds. No spec page.Why now
Found in this run's IANA Well-Known URIs sweep. It is registered permanent — which is exactly the trap worth documenting, since permanent is a statement about the registry (stable spec, suffix will not be reassigned), not about the web.
The reasoning
revisit: a second, unrelated implementer.Status
N/A — register entry, not a spec page. Per the routine's "record every turn-down" rule, this is the output for a scan that found something real but premature.
npm run buildpasses.🤖 Generated with Claude Code