Flow 1
Agent entry issues a Txn-Token
- 1
Agent authenticates as a workload and, if needed, as a user delegate.
- 2
Requests a Txn-Token with agent-appropriate purpose/context.
- 3
Tool calls inside the domain carry the Txn-Token. tctx stays immutable.
IETF · 21 May 2026
draft-araut-oauth-transaction-tokens-for-agents-02
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-02, 21 May 2026. Same TTS issuance as the WG draft, with agent-specific guidance for purpose and context fields.
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. 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-02, 21 May 2026. https://datatracker.ietf.org/doc/search/?name=transaction-tokens-for-agents
Individual draft. The WG document is the one that will likely become the RFC; this is a usage profile.