change(web-bot-auth): cite the IETF working-group draft - #200
Draft
jdevalk wants to merge 1 commit into
Draft
Conversation
The IETF chartered a Web Bot Auth working group, which adopted draft-ietf-webbotauth-httpsig-protocol-00 on 2026-09-01 and folded the separate draft-meunier-webbotauth-httpsig-directory into it (that draft is now expired). The page cited both individual submissions, one of which no longer exists. Swaps the two sources for the WG draft plus the WG charter page, rewrites the paragraph describing where the work lives, and adds the implementation detail the merged draft now pins down: the requested well-known URI, the JWKS media type, the signed Signature-Agent header, and the mandatory created/expires/keyid/tag parameters. Status stays optional — adoption is not publication. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Deploying specification-website with
|
| Latest commit: |
022df9d
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://394ee11f.specification-website.pages.dev |
| Branch Preview URL: | https://change-webbotauth-wg-adoptio.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
web-bot-authcited two individual IETF submissions. One of them no longer exists.draft-meunier-webbotauth-httpsig-protocol+draft-meunier-webbotauth-httpsig-directory→draft-ietf-webbotauth-httpsig-protocol+ the WG charter page.## What it is: the "the proposal lives in two IETF drafts" paragraph is rewritten. Adds a short paragraph distinguishing WG adoption from publication, so the page does not read as if the draft were settled.## How to implement: the bot-operator bullets now carry what the merged draft actually pins down — the/.well-known/http-message-signatures-directorysuffix, theapplication/http-message-signatures-directory+jsonmedia type, the signedSignature-Agentheader, the asymmetric-only rule, and the mandatorycreated/expires/keyid/tag=web-bot-authparameters. The old bullets named@methodand a barecreated, neither of which matches the draft.## Common mistakes:expiresadded to the replay bullet.well-known-overviewgainsweb-bot-authinrelatedSlugs(and vice versa), now that the draft names a well-known URI.Why now
webbotauth) working group under the WIT area (chairs David Schinazi and Rifaat Shekh-Yusef, AD Mike Bishop).draft-ietf-webbotauth-httpsig-protocol-00on 2026-09-01 — its first and so far only WG document.draft-meunier-webbotauth-httpsig-directoryis expired and marked replaced, so one of our two citations pointed at a dead document.Primary sources
Status
Stays
optional. WG adoption raises confidence in the direction, but the draft is pre-RFC, the well-known URI is requested rather than IANA-registered (I checked the Well-Known URIs registry — no entry yet), and the verifier ecosystem is still mostly CDNs. Nothing here meets therecommendedbar of "a modern site should do it". Open question for you in Slack: whether WG adoption plus CDN support is enough to move it, or whether that waits for the RFC.Changelog
Included a
changedentry — borderline by the CLAUDE.md test, so drop it if you read this as citation maintenance rather than a substantive rewrite.src/content/changelog/2026-09-06-web-bot-auth-wg-adoption.md(and rename the file) if this merges on a later day.npm run buildpasses; lint, format, andcheck:skillclean. Page count unchanged, so no SKILL.md or OG-image churn.🤖 Generated with Claude Code