The Scope Creep Automated reviews of new AI-related working group submissions

Update review · November 20, 2026

Using KYAPay Tokens Update

draft-skyfire-oauth-using-kyapay-tokens -03View on Datatracker →

Status: Individual draft (not adopted), Standards Track. Revision -03 published 16 November 2026. 45 pages, unchanged. Same three authors.

This is a sync revision. One sentence of body text changed, to match a privacy change in the KYAPay Token draft. The feedback from the previous review is not addressed, apart from a reference bump that is already out of date.

What changed

One sentence in Section 6.11. In -02, hid.id, sub and aid.id "differ at every other Target service." In -03 they "differ at every other Target." The word "service" is gone.

References were bumped. KYAPay Token moves from -02 to -03, KYAPay Token Exchange from -02 to -03, Identity Verification Methods from -03 to -04, and Client ID Metadata Document from -02 to -03.

That's the whole diff. No mechanisms were added or removed.

So what does dropping one word do?

It weakens the pairwise guarantee. The change comes from KYAPay Token -04, published the same day, which now says the identifiers differ at each other Target and that "whether the services of one Target share a value is left to the issuer."

A Target with several services can now receive the same hid.id at all of them. A recipient can no longer assume that two of its own services see unlinkable identifiers.

This matters for account linking. A CIAM system links an account to the stored iss plus hid.id. If an issuer shares hid.id across one Target's services, a link made at one service matches at the others. The draft doesn't say whether that is intended.

The rest of the document wasn't updated to match. Section 6.11 still says hid.id is stable "at a Target service" in the sentence before the changed one. Section 9.1 still says a bot manager can recognize a returning principal "at that Target service." Neither draft says what makes two services the same Target.

What got fixed

The normative reference, for about a day. The last review asked for the reference to move to draft-skyfire-oauth-kyapay-token-03. It did. But the changelog says this revision is "aligned with KYAPay Token," and the text it aligns with is in -04. The draft cites -03, which still says "every other Target service."

What didn't change

Everything else from the last review still stands:

  • The RFC 9421 profile is unfinished. Key source, keyid, tag, and error responses are still "expected to be specified in a future revision."
  • Accept-KYAPay-Token still can't express assurance. It lists claim names only. Its parameters are still recipient-defined.
  • SHOULD and MUST still disagree on signing. Section 5.1 says SHOULD, step 7 of the processing model says MUST reject.
  • An untrusted issuer is still undefined behavior. A valid token from an issuer the site hasn't configured may be declined where an anonymous bot gets through.
  • Section 4.4 is still inside a section marked informative, and still full of MUSTs.
  • Email matching is still a sufficient account link.
  • No Web Bot Auth.
  • Nothing was cut. Design Principles, the role-by-role guidance, Feedback to the Token Issuer, and Token Creation are all still there. So is the bot manager text that "gently encourages developers to adopt and implement the KYA standard."
  • The small issues stayed. Undefined values like document+biometric, the duplicate signature check in steps 3 and 4, the page-script header capture, and "human presence signal" for a principal who "need not be present."

Background of the Authors

No change. Ankit Agarwal, Michael B. Jones, and Srinivasa Thumma are still the authors. See the earlier reviews for their backgrounds.

Suggested Feedback

  1. Cite KYAPay Token -04. The one substantive change in this revision depends on it.

  2. Finish the "Target" alignment. Fix the remaining "Target service" wording in Sections 6.11 and 9.1, or explain why those sentences are different.

  3. Say what a shared hid.id means for account linking. If one Target's services can share a value, state whether an account link at one service carries to the others, and how a recipient knows which behavior its issuer chose.

  4. The feedback on -02 is all still open. The RFC 9421 profile, assurance in Accept-KYAPay-Token, untrusted issuer handling, and the cuts are the ones that matter most. The Web Bot Auth WG is still the place to look for the signature profile.

For related reading, see KYAPay Token -04, which made the identifier change this revision follows and adds a new Issuer Records section.