IETF · 31 October 2026
draft-araut-oauth-transaction-tokens-for-agents-03
Transaction Tokens For Agents (draft-araut-oauth-transaction-tokens-for-agents-03) is Individual draft, 31 October 2026. Helps when you already run Txn-Tokens internally and the caller is now an LLM agent instead of a microservice.
At a glance
Actors
01
Apply the Transaction Token model to agent call chains so task context stays immutable as agents invoke tools and other agents inside a trust domain. Helps when you already run Txn-Tokens internally and the caller is now an LLM agent instead of a microservice.
02
Same as the WG transaction-tokens draft. The WG document is the one that will likely become the RFC; this is a usage profile.
03
draft-araut-oauth-transaction-tokens-for-agents-03, 31 October 2026, expires 4 May 2027. Same TTS issuance as the WG draft. The profile adds agentic_ctx (originator, proximate_agent, hop count, optional min_assurance_level) and looks agents up in an Agent Attribute Store.
04
Flow 1
Agent authenticates as a workload and, if needed, as a user delegate.
Requests a Txn-Token with agent-appropriate purpose/context.
Tool calls inside the domain carry the Txn-Token. The profile updates agentic_ctx at agent hops; parent tctx stays immutable.
05
Context propagation of identity and authorization purpose, not a user login protocol.
06
Parent WG document — implement that.
Fits the AIMS internal-chain guidance.
Possible A2A call-chain usage; not in A2A v1.0 core.
07
When they disagree, the WG document wins.
08
Individual draft-03, 31 October 2026, expires 4 May 2027. https://datatracker.ietf.org/doc/draft-araut-oauth-transaction-tokens-for-agents/
Pin draft-03 (31 October 2026, expires 4 May 2027). It renames the lookup role from Agent Registry to Agent Attribute Store and the current actor field to proximate_agent. The WG transaction-tokens draft is still the document that will likely become the RFC; this is a usage profile.
Deployment patterns