A datatracker search for "agent" now returns more than 200 active Internet-Drafts, and almost all of them are individual submissions with no IETF standing. Architects, product teams and buyers need to know which documents a working group has actually adopted, which are close to becoming RFCs, and which are one author's proposal that may expire in six months. This tracker lists the agent identity and authorisation drafts that matter, grouped by working group (WIMSE, OAuth, Web Bot Auth and SCIM), with the exact version, date and status shown on the IETF datatracker, followed by the most visible individual drafts. It complements the broader Agent Identity Standards Tracker, which covers MCP, A2A, OpenID, FIDO and government guidance; this page goes deeper on the IETF only. Every draft name links to the datatracker page we checked.
Last reviewed: 27 October 2026
Key takeaways
- Working group adoption is the signal that matters. A
draft-ietf-<wg>-name means a working group has adopted the work; any other name (draft-<author>-...) is an individual draft with no standing, however polished. - Three working groups carry most agent identity work. WIMSE (workload identity, now including the AI Identity Management System draft adopted in September 2026), OAuth (delegation, Transaction Tokens, cross-domain chaining) and Web Bot Auth (signed agent traffic to websites).
- Closest to RFC: OAuth Identity and Authorization Chaining Across Domains is in the RFC Editor queue as a Proposed Standard, and WIMSE Workload Identity Practices has been submitted to the IESG. Transaction Tokens and Attestation-Based Client Authentication have working group consensus and await write-up.
- Agent-specific WG drafts are new. draft-ietf-wimse-aims and draft-ietf-webbotauth-httpsig-protocol are both at revision -00. Design to their architecture, not to their header names.
- Individual drafts on agent delegation are multiplying. More than a dozen propose delegation chains, mandates, intent tokens and receipts. Read them for ideas; do not buy or build on the assumption that any one will become the standard.
Status key
- RFC Ed Queue: approved by the IESG and waiting for publication as an RFC. Content is effectively fixed.
- IESG review: submitted to the Internet Engineering Steering Group (for example AD Evaluation). Late-stage, but changes are still possible.
- WG consensus: the working group has agreed the document and it awaits the shepherd write-up before going to the IESG.
- WG document: adopted by a working group and under active development. Expect changes.
- Individual: submitted by its authors without working group adoption. No IETF standing; may expire after six months without a new revision.
- Replaced or expired: superseded by another draft or lapsed. Do not cite for current behaviour.
Versions and dates are as shown on the datatracker on 27 October 2026. "Intended status" is given where the datatracker or the draft states it; several drafts state Standards Track in their header while the datatracker field is still empty.
WIMSE working group (workload identity)
| Draft | Version and date | Status | Why it matters for agents |
|---|---|---|---|
| draft-ietf-wimse-aims (AI Identity Management System) | -00, 15 September 2026 | WG document, Informational; replaces draft-klrc-aiagent-auth | The first WG-adopted agent identity document. Treats agents as workloads and composes WIMSE identifiers and credentials with OAuth delegation, Transaction Tokens, CIBA and Shared Signals. |
| draft-ietf-wimse-workload-identity-practices | -07, 22 September 2026 | Submitted to IESG, AD Evaluation (AD Followup); Informational | Describes current workload identity practice; closest WIMSE document to publication |
| draft-ietf-wimse-arch | -08, 6 July 2026 | WG document, Informational | Architecture, including a section on AI and ML intermediaries as delegated workloads |
| draft-ietf-wimse-identifier | -04, 23 October 2026 | WG document | URI format for workload (and so agent) identifiers; SPIFFE IDs fit |
| draft-ietf-wimse-workload-creds | -02, 2 July 2026 | WG document | Workload Identity Token (WIT) and certificate: key-bound, short-lived agent credentials |
| draft-ietf-wimse-wpt | -02, 27 August 2026 | WG document | Per-request proof of possession; header usage changed in -02 |
| draft-ietf-wimse-http-signature | -08, 20 October 2026 | WG document, Proposed Standard intended | RFC 9421 profile for workload-to-workload requests through proxies |
| draft-ietf-wimse-mutual-tls | -03, 24 October 2026 | WG document | Transport-layer agent authentication with workload certificates |
See the WIMSE for AI Agents Guide for how these pieces fit together.
OAuth working group (delegation and tokens)
| Draft | Version and date | Status | Why it matters for agents |
|---|---|---|---|
| draft-ietf-oauth-identity-chaining | -17, 19 July 2026 | RFC Ed Queue, Proposed Standard | Carrying identity and authorisation across trust domains; the basis for agents calling partner APIs. See the OAuth Identity and Authorization Chaining Across Domains Guide. |
| draft-ietf-oauth-transaction-tokens | -11, 30 July 2026 | WG Consensus: Waiting for Write-Up; header Standards Track | Short-lived tokens carrying user and request context through internal call chains; the draft itself speaks of workloads, and AIMS applies it to agents. See the OAuth Transaction Tokens (Txn-Tokens) Guide. |
| draft-ietf-oauth-identity-assertion-authz-grant (ID-JAG) | -04, 21 May 2026 (expires 22 November 2026 without a new revision) | WG document | Enterprise IdP-mediated access between apps; includes an appendix on an AI agent using external tools. See Enterprise-Managed Authorisation for AI Agents (ID-JAG and Cross App Access). |
| draft-ietf-oauth-attestation-based-client-auth | -12, 12 October 2026 | WG Consensus: Waiting for Write-Up | Client authentication from an attested instance, relevant to agent runtimes. See the OAuth Attestation-Based Client Authentication Guide. |
| draft-ietf-oauth-spiffe-client-auth | -02, 15 June 2026 | WG document | SPIFFE credentials as OAuth client authentication, removing client secrets for agent workloads |
| draft-ietf-oauth-client-id-metadata-document | -02, 6 July 2026 | WG document | HTTPS URL as client ID; recommended by MCP for client registration. See the OAuth Client ID Metadata Documents (CIMD) Guide. |
| draft-ietf-oauth-refresh-token-expiration | -03, 6 July 2026 | WG document | Signalling refresh token and authorisation expiry, central to bounding long-running agent grants |
| draft-ietf-oauth-v2-1 | -16, 2 September 2026 | WG document | Consolidated OAuth that MCP authorisation builds on |
| draft-ietf-oauth-security-topics-update | -03, 5 July 2026 | WG document | Updates to RFC 9700, the security baseline for any agent OAuth deployment |
| draft-ietf-oauth-status-list | -21, 21 June 2026 | RFC Ed Queue, Proposed Standard | Token Status List for checking revocation status of issued tokens and credentials |
| draft-ietf-oauth-deferred-token-response | -00, 16 September 2026 | WG document | Token responses that arrive later, relevant where human approval gates an agent's request |
Published foundations that agent designs rely on today: RFC 8693 Token Exchange, RFC 8707 Resource Indicators, RFC 9449 DPoP, RFC 9700 Security BCP and RFC 7523 JWT grants. See the OAuth Token Exchange and Delegation Guide.
Web Bot Auth working group (signed agent traffic)
| Draft | Version and date | Status | Why it matters for agents |
|---|---|---|---|
| draft-ietf-webbotauth-httpsig-protocol | -00, 1 September 2026 | WG document; header Standards Track | How agents and crawlers sign requests to websites with RFC 9421, and how sites discover keys. The charter milestone for sending it to the IESG was 30 April 2026. |
| draft-meunier-webbotauth-registry | -03, 26 June 2026 | Individual | Signature Agent Cards describing an agent's purpose, trigger and rate expectations |
| draft-rescorla-anonymous-webbotauth | -01, 19 July 2026 | Individual | Anonymous bot authentication for rate limiting without revealing the operator |
| draft-meunier-web-bot-auth-architecture | -05, 2 March 2026 | Replaced by draft-meunier-webbotauth-httpsig-protocol (now the WG draft) | Older material still cites it; update references |
See Web Bot Auth and HTTP Message Signatures for Agents.
SCIM working group (provisioning agents)
| Draft | Version and date | Status | Why it matters for agents |
|---|---|---|---|
| draft-wzdk-scim-agent-resource | -00, 5 June 2026 | Individual | Proposes an agent resource type so agents can be provisioned like users and groups |
| draft-kushwaha-scim-agent-governance | -00, 27 July 2026 | Individual | Agent governance attributes in SCIM |
The SCIM working group's datatracker page showed no active WG drafts on 27 October 2026; its two WG documents had expired. Agent provisioning through SCIM is therefore at proposal stage only. See the SCIM Provisioning Guide.
Individual drafts worth watching
These have no working group adoption. They are listed because they are frequently referenced or address gaps the WG drafts leave open, not because they are likely to succeed.
| Draft | Version and date | Topic |
|---|---|---|
| draft-ni-wimse-ai-agent-identity | -03, 30 September 2026 | Binding agent identity to an accountable owner in WIMSE credentials |
| draft-asor-wimse-agent-delegation-chain | -02, 15 October 2026 | Verifiable attenuated delegation for agent chains |
| draft-reece-wimse-cross-org-delegation | -02, 31 August 2026 | Problem statement for cross-organisation agent delegation |
| draft-lee-wimse-local-tool-call-proof | -01, 11 October 2026 | Per-call proof for local tool invocation |
| draft-munoz-wimse-authorization-evidence | -01, 19 July 2026 | Signed authorisation-evidence records for agent actions |
| draft-chen-oauth-agent-authz-use-cases | -04, 11 October 2026 | Agent authorisation use cases and gap analysis |
| draft-hamr-oauth-agent-delegation | -03, 22 October 2026 | Attenuated delegation profile for automated agents |
| draft-araut-oauth-transaction-tokens-for-agents | -02, 21 May 2026 | Applying Transaction Tokens to agents |
| draft-chen-oauth-agent-intent-token | -00, 19 October 2026 | A credential for delegated user intent |
| draft-chen-oauth-agent-revocation | -00, 27 April 2026 (near expiry) | Explicit revocation of agent authorisation |
| draft-jia-oauth-scope-aggregation | -01, 14 August 2026 | Scope aggregation for multi-step agent workflows |
| draft-drake-agent-identity-registry | -05, 26 October 2026 | Agent identity registry |
| draft-nelson-agent-delegation-receipts | -15, 21 October 2026 | Delegation receipts; high revision count, no adoption |
| draft-anandakrishnan-rats-ptv-agent-identity | -01, 29 September 2026 | Attestation (RATS) for agent identity |
| draft-mcgraw-httpapi-agent-budget | -04, 10 September 2026 | Budgets for agent HTTP API use |
How to judge an individual draft: check whether it names a target working group, whether it has been presented at an IETF meeting, the number of distinct authors and organisations, whether it reuses published RFCs or invents new token formats, and whether its security considerations section is complete. A high revision number alone means activity, not consensus.
Identity and NHI implications
| Question | Where the IETF stands | What to do now |
|---|---|---|
| How should an agent be identified? | As a workload with a URI identifier (WIMSE identifier, SPIFFE compatible); AIMS adopts this | Give each agent its own workload identity; avoid shared service accounts |
| What credential should it hold? | Short-lived, key-bound credentials (WIT or certificate) with per-request proofs | Use SPIFFE or cloud workload identity now; prefer sender-constrained tokens (DPoP, mTLS) |
| How does it act for a user? | OAuth delegation, token exchange, Transaction Tokens; multi-hop delegation still open | Token exchange per hop with narrower scope and audience |
| How does it cross organisations? | Identity chaining near publication; ID-JAG for enterprise-managed access | Pilot chaining with partners that support it |
| How does a website recognise it? | Web Bot Auth WG draft at -00 | Sign traffic if you operate agents; verify in log-only mode if you run a site |
| How is it provisioned and governed? | SCIM agent drafts are individual only | Use your identity platform's agent registry and governance; track SCIM proposals |
See the Agentic AI Identity Guide for the architecture these standards support.
What to watch next
- RFC publication of identity chaining and Token Status List: both sit in the RFC Editor queue; expect RFC numbers soon.
- Transaction Tokens to the IESG: the OAuth WG list shows December 2026 against it; watch for the write-up and IESG review.
- AIMS -01 and beyond: the first revision after adoption will show how far the working group intends to go beyond composing existing standards.
- Web Bot Auth revisions: the protocol draft missed its April 2026 charter milestone; watch for -01 and for a directory draft becoming a WG document.
- Delegation chain adoption: whether WIMSE or OAuth adopts one of the competing agent delegation drafts, which would be the clearest sign of a future standard for multi-agent chains.
- ID-JAG renewal: revision -04 expires on 22 November 2026 unless a new version is posted.
- SCIM agent resources: whether the SCIM working group adopts any agent provisioning draft.
How to use this tracker
- Build on published RFCs and documents in the RFC Editor queue; their content is effectively fixed.
- Prototype against WG documents, isolating draft-specific headers and claims behind a library you can update.
- Treat individual drafts as research. Do not accept a vendor claim of "standards-based" when the only standard is an individual draft; ask which draft, which version and whether a working group has adopted it. See the AI Agent Identity Security Buyer's Guide.
- Re-check before decisions: drafts change and expire. Check the datatracker link in each row before an RFP, audit or architecture review, and record the version you relied on.
- Track by working group, not by keyword: the WIMSE, OAuth, Web Bot Auth and SCIM document pages are a better signal than a keyword search capped at 200 results.
Status information is taken from the linked IETF datatracker pages as at 27 October 2026 and may have changed since. Related NHI Mgmt Group resources: Agent Identity Standards Tracker · WIMSE for AI Agents Guide · Agent Identity and Access Guide · OAuth Token Exchange and Delegation Guide