CTK: §9 authorization-token vectors; mark §9 reference-backed (0.3.3) - #11
Merged
Conversation
…d (0.3.3) The reference implements the §9 token profile from delego 0.3.3. Adds ctk/vectors/token.json (+ token_signing_key.pub) — verifier vectors for §9.1: valid token + alg=none (algorithm confusion), tampered signature, wrong audience, expired — wired into conformance.py (skipped on reference < 0.3.3). Flips §9's status tag from 'draft — not yet in reference' to reference-backed; no normative design text changed. Protocol version unchanged (token is additive).
koishore
added a commit
that referenced
this pull request
Aug 20, 2026
) A conformance review found spec.md contradicting itself after the reference shipped the §4.2 query-fold (delego 0.3.0, CTK regenerated in #9): §2.1's version table/tag legend, the §10 preamble, and the §10 'deferred (breaking)' block still called the fold deferred and said the reference implements 0.2, while §4.2 (normative), the CTK README, and conformance.py all treat it as 0.3 and reference-backed. - §2.1: 0.3 row is reference-complete/CTK-backed; the query-fold is the 0.3 breaking change (reference-backed since 0.3.0, hashing vectors on the 0.3 preimage, 0.2 preimage preserved as hashing-v0.2.json); the reference implements 0.3. Inline '(0.3, draft — additive)' tags become '(0.3 — additive)'. - §4.1: worked example regenerated on the 0.3 preimage (canonical JSON carries "query":[]; fingerprints match ctk/vectors/hashing.json). - §4.2/§10: the Broker query obligation is scoped to the ≤0.2 preimage (the fold supersedes it on 0.3); the §10 deferred block becomes the 0.3 breaking conformance line; the token line quotes §9's actual TTL rule (SHOULD ≤60s, MUST NOT exceed 300s). - examples/authorization-token.{md,json}: drop the stale 'not yet minted' note (reference-backed since 0.3.3, #11); fpr updated to the place-order's 0.3 fingerprint. - README: status section rewritten to match; repaired spec.md anchors (§7.1 retag; two §9 links broken since #11's heading change). No normative design text changed — same precedent as #11's §9 status flip. validate.py + conformance.py green; all spec.md anchors resolve.
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.
The reference now implements the §9 authorization-token profile (delego#17, 0.3.3). Per the spec-leads-reference model, §9 becomes reference-backed once the reference reproduces its CTK vectors — which it now does.
Changes
ctk/vectors/token.json+ctk/vectors/token_signing_key.pub— verifier (PEP) vectors for §9.1: a valid token, plusalg=none(algorithm confusion), tampered signature, wrongaud, and expired — each marked accept/reject. Wired intoconformance.py(skipped on a reference < 0.3.3).spec.md§9 status tag flipped from draft — not yet in reference → reference-backed (optional profile), since delego 0.3.3. No normative design text changed — this is the sanctioned §2.1 transition (a clause becomes reference-backed once its CTK vectors reproduce), not an edit to the frozen design.ctk/README.md+CHANGELOG.mdupdated.Protocol version unchanged (still 0.3): the token is additive and changes no hashed/signed bytes.
Verification
validate.pyandconformance.pyboth green locally against delego 0.3.3 — including the 5 new token cases. The conformance CI here installsdelego@main(now 0.3.3), so it will replay them.