add(considered): cross-device flow security (RFC 10027) is an authorization-server property - #179
Draft
jdevalk wants to merge 1 commit into
Draft
add(considered): cross-device flow security (RFC 10027) is an authorization-server property#179jdevalk wants to merge 1 commit into
jdevalk wants to merge 1 commit into
Conversation
…r property RFC 10027 (BCP 247, August 2026) is real and well-aimed, but every mitigation lands inside an authorization server or a native client. Nothing surfaces at an origin, so there is nothing to describe or audit as a website property. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Deploying specification-website with
|
| Latest commit: |
ada5784
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://35774721.specification-website.pages.dev |
| Branch Preview URL: | https://add-considered-cross-device.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
Adds one entry to the
/considered/register: Cross-device flow security (RFC 10027 / BCP 247), turned down asout-of-scope.No spec page, no changelog entry — this records a decision, not a change to what the spec says.
Why now
The IETF published RFC 10027, "Best Current Practice for Security of Cross-Device Flows", on 11 August 2026 as BCP 247. It landed inside this run's scan window and is exactly the kind of topic that looks like it belongs here — it is security, it is authentication, and this spec already has
well-known/webauthn,well-known/change-passwordandaccessibility/accessible-authentication.It does not belong here. The RFC names its audience (architects, fraud analysts, engineers building authentication systems) and every mitigation it prescribes — proximity establishment, short-lived single-use codes, rate limiting, anomaly detection, preferring FIDO2/WebAuthn over the device authorization grant — executes inside an authorization server or a native client. Nothing surfaces at an origin: no header, no element, no published resource, so nothing an outside observer could check. A site that consumes a well-implemented IdP satisfies the BCP without doing anything at all.
That is the
auditable website outcome, not build techniquerule, and it is the same call already recorded for the HTTP QUERY method.Primary sources
Revisit condition
If a site-published artefact grows around it — a well-known document, a header, or metadata declaring which cross-device flows an origin will accept — that artefact becomes the topic and would earn a page under
well-knownorsecurity.Checks
npm run build,npm run lint,npm run format:checkall pass. Page count and categories unchanged (168 / 10), so no SKILL.md or digest change.🤖 Generated with Claude Code