The Internet Engineering Task Force (IETF) is developing guidance on how software workloads and agents identify themselves and receive permission to act. This page compares those concepts with AAES grants: permissions limited to a task and lifetime. AAES uses its own wire format, so the conceptual comparison does not establish interoperability.
These pages describe the product. They are not a certification or a legal opinion.
Reading this note
The datatracker is authoritative for the state of any IETF document, and drafts change between revisions. Each draft below has a date. AAES does not emit WIMSE tokens today, so nothing here is a protocol-compatibility statement.
Instrument identity
- Title
- WIMSE (Workload Identity in Multi System Environments): the Workload Identity Token (WIT) and Workload Proof Token (WPT) drafts, and the agent-identity track draft-ietf-wimse-aims (AIMS), adopted as a working-group document on 15 September 2026. Revision numbers and dates change between revisions; the working-group document list is authoritative for the current revision of each draft.
- Issuing body
- Internet Engineering Task Force (IETF), WIMSE working group
- Instrument type
- Working Internet-Drafts, subject to change. AIMS revision 01, dated 2 November 2026, states an intended status of Informational; it describes applying existing WIMSE and OAuth standards rather than defining a new protocol.
- Adjacent RFCs
- RFC 8693, OAuth 2.0 Token Exchange (delegation semantics) and RFC 9396, Rich Authorization Requests (fine-grained authorization detail)
- Official sources
- WIMSE working group and draft-ietf-wimse-aims (AI Identity Management System) on the IETF datatracker.
The AARM references below use row numbers from the AARM/CS 1 draft catalog AAES maps, whose numbering differs from public AARM v1.0.
AAES approvals are similar in shape to Client-Initiated Backchannel Authentication (CIBA): a person approves through a separate channel while the agent request waits, and the approval is bound to that request. AAES does not implement CIBA.
Question
How do AAES grants relate to these identity concepts, and what limits interoperability?
The comparison covers three concepts. AAES uses its own grant format for each, rather than WIMSE tokens:
- Proof and lifetime: a bearer-and-proof structure, with limits on freshness and revocation (AARM R6.03).
- Delegation: RFC 8693 act-as/on-behalf-of semantics, with permission narrowing verified at each handoff and recorded provenance for decision reasons (R6 delegation chains; R2 context accumulation across hops).
- Exact authorization: RFC 9396-style details describe a release by its action identifier, target, operation, and parameters. In AAES Govern, an approval is bound to the request payload; grants bind identity, capability and task, and parameter binding at the downstream API depends on the connector (R1.05, partial).
Selected contribution
| IETF semantic | What a reviewer can examine in AAES Govern | Boundary |
|---|---|---|
| WIT/WPT bearer-and-proof structure | Grants are task-scoped, time-limited, and non-transferable. They carry an expiry capped at 15 minutes. Revocation sweeps live grants, with a latency target that is not a measured bound. | AAES grants are not WIMSE tokens; no wire-format compatibility is claimed today. |
| RFC 8693 act-as / on-behalf-of | Delegation chains with verified per-hop narrowing: a delegated grant can only shrink in scope, and context accumulated across hops is recorded with the decision. | Recorded delegation shape does not establish that the underlying human decisions were correct. |
| RFC 9396 authorization detail | Approvals bind to the action identifier, target, operation and parameters of the exact request. Changing the request requires a new approval. | Binding is to the request as routed through AAES; activity outside AAES is visible only where telemetry is supplied. |
Preconditions and gaps
- AAES does not currently support WIMSE interoperability. A compatibility evaluation would need to identify concrete WIMSE and OAuth mechanisms, their versions, and executable interoperability tests. AIMS-01 is best-practice guidance using existing standards; it does not define a new AIMS token profile.
- Drafts move. The AIMS draft was adopted on 15 September 2026; cite it by name and date, and re-check the datatracker before relying on any section.
- Credential-path control is required. Activity outside AAES Govern is visible only where telemetry is supplied. Observation is not enforcement.
- No production adoption as of this review. Deployments are self-hosted or hosted by AAES.
For the exact record and export formats AAES Govern commits to, use the specification. For implementation and testing details, use Security and implementation posture and the evaluation page.
Client responsibility
The organization operates its own workload-identity infrastructure and evaluates the WIMSE and AIMS drafts against it. AAES's grant flows mirror RFC 8693 and RFC 9396 semantics; that resemblance does not make any deployment conformant with those drafts. The client remains the regulated entity.
Choose the tool actions to test, identify who holds their credentials, and list the questions the decision records should answer.