Latest reviews
I read the drafts so you can skim them
165 reviews of 135 drafts. Find yours by draft name or author, or subscribe to the feed.
Nothing matches that filter.
November 16, 2026 37 reviews
The AUDIT BoF Charter, Agent Audit Records Without Saying Who Writes Them
AUDIT (Agent Use of Delegation and Interaction Traceability) is a working-group-forming BoF. It meets Tuesday November 17, 9:00am to 10:30am Pacific. No solution drafts will be presented.…
AGENTPROTO Use Cases and Requirements
AGENTPROTO is chartered to build one thing: a dialog management protocol. It carries dialog identifiers and lifecycle state across hops, trust boundaries and modalities. The charter says…
Transaction Tokens BCP Has Real Deployment Lessons and Several Conflicts With the Base Spec
Transaction Tokens define a token format and a request to the Transaction Token Service (TTS). They don't say how to roll that out across hundreds of services.
Common DNS Discovery Parameters for Agents
DAWN has two DNS-based discovery proposals. DNS-AID publishes agents in unicast DNS with SVCB records. Zero-Configuration Agent Discovery advertises them on the local link with mDNS and…
Agent Resource Discovery (ARD) Architecture
An agent cannot load every MCP server, A2A agent and skill into its context window. The tool list has to be found at runtime, across organizations, without one company running the directory.
ARD Manifest and Lookup for Agent Discovery
An agent needs to find MCP servers, A2A agents and skills it was not configured with. This draft defines the catalog format a publisher serves and the HTTP search API a registry exposes.
Workload Authorization Grant (WAG)
Agent platforms create and destroy agents constantly, one per channel, repository, or pipeline. Registering each one as an OAuth client at every SaaS authorization server does not scale.…
BEST, an Agent Interaction Protocol in a Discovery Slot
An AI agent that has never seen a service needs to be told, out of band, which operations it accepts, what the payloads look like, and how to get a credential.
WIMSE Workload Identity Metadata
Deployments stuff attributes into workload identifiers. The draft's own example is spiffe://example.com/ns/prod/team/payments/role/reconciler/service/reconciliation. Relying parties then…
OAuth Client ID Metadata Document (CIMD)
An OAuth client needs a clientid and registered metadata at every authorization server it talks to. A client that talks to servers it has no relationship with can't register manually.
Delegate SD-JWT, Holder-Signed Delegation Chains
A Holder of an SD-JWT (RFC 9901) can present it to a Verifier and prove possession of a key. The Holder can't hand that credential to someone else to present on its behalf.
Identity Assertion JWT Authorization Grant (ID-JAG)
Two apps both use the same IdP for SSO. One wants to call the other's API on behalf of the user. Today that takes an interactive OAuth flow between the two apps, and the IdP never sees it.
Identity Chaining Is in the RFC Editor Queue
A client in one trust domain needs to call an API in another. Each domain has its own authorization server. The second domain needs to know which user the request is for and what was…
OAuth SPIFFE Client Authentication
A workload running under SPIFFE already has an attested credential, its SVID. To call an OAuth token endpoint today it still needs a second credential, a client secret or a privatekeyjwt…
The OAuth 2.1 Authorization Framework
OAuth 2.0 is spread across too many documents. To build it correctly today you need RFC 6749, RFC 6750, PKCE, Native Apps, Browser-Based Apps, and the Security BCP.
AI Identity Management System (AIMS)
People keep inventing new authentication and authorization schemes for AI agents. Most of them rebuild things that already exist.
WIMSE Architecture
Every WIMSE protocol draft needs the same vocabulary: workload, trust domain, workload identifier, workload identity credential, security context. This document is where those terms are…
WIMSE Workload Proof Token Moves Into the Authorization Header
A Workload Identity Token (WIT) binds a public key to a workload identity. It must not be used as a bearer token. Something has to prove the sender holds the private key.
DAWN Use Case for Protocol-Layer AI Agents
An organization runs several AI agents that each help with one part of the network stack. One tunes application media. One helps with transport adaptation. One helps with routing. One…
ARD Initial Contact: Finding the Agent Manifest
ARD puts an organization's agents, MCP servers and skills in one JSON manifest. A client needs the URL of that manifest before it can do anything else.
Bounded Work Authorization, a Requirements Document for the Mission and Schemas Drafts
OAuth can revoke a token. It has no shared way to say "the task the user approved is over."
Agent Gateways as Discovery Proxies in DAWN
Agents behind a NAT or firewall cannot publish themselves in public DNS. Small agents may not be able to run wide-area discovery at all.
DNS for AI Discovery (DNS-AID) with SVCB Records
An agent wants to call another agent. It needs the endpoint, the agent protocol (MCP, A2A), and a pointer to the agent's descriptor. Today that comes from configuration or a third-party…
Registry-Assisted Resolution for Agents Without a DNS Anchor
Most DAWN proposals assume the publisher controls a DNS zone. Alice at [email protected] does not. Neither does a workload with a SPIFFE ID or a DID.
SCIM Events for Merged and Unmerged Users
A SCIM service provider finds that two User resources are the same person. It keeps one and retires the other.
A Two-Layer Agent Discovery Framework for DAWN
DAWN has many discovery proposals and no agreed picture of how they fit together. This draft offers that picture: local discovery inside a domain, DNS between domains, and a gateway in…
SCIM Group Membership Resource Type
A group with a million members does not fit in one HTTP response.
Personal Agent Protocol (Poppy) 1.0 Summary
A personal agent acts for one user at many companies. Today the company either lets the agent pretend to be the user, typing the user's password into its website, or it blocks the agent.
MDI Model -02, a Smaller Minimum With a Method Behind It Update
Almost everything. This is a rewrite, not a revision.
DAWN Terminology -07, Narrowed to AI Agents Update
The scope. DAWN used to stand for "Discovery of Agents, Workloads, and Named Entities." It now stands for "Discovery of Agents With Names," and the glossary was rewritten to match.
Deferred Token Response -01, Now With User Interaction Update
A lot. The document went from 38 pages to 47.
Zero-Configuration Agent Discovery -01, Now Built on the Common Parameters Update
Almost everything on the wire. The document went from 20 pages to 34.
DAWN Use Cases -01, Narrower Scope and Two Worked Examples Update
The document went from 14 pages to 26. Almost all of the growth is two new appendices.
Cross-Org Delegation -02, R10 Takes Over the Document Update
The document went from 11 pages to 17. Almost all of the growth is about one requirement.
DNS-Based Agent Naming (DAN) -01, the Index Moves to _agents Update
Very little. The document is still 21 pages. The diff is one design change, one new appendix section, and spelling fixes.
KYAPay Token -04 Update Update
Status: Individual draft (not adopted), Standards Track. Revision -04 published 16 November 2026, two weeks after -03. 49 pages, up from 46. Same two authors. It is on the IETF 127 OAuth…
SCIM Interoperability Profile -02, Now You Can Remove a Group Member Update
Most of the document. It went from 11 pages to 18, and almost every section was touched.
November 10, 2026 43 reviews
Transaction Tokens for Agents Adds an Agent Chain Claim to Txn-Tokens
Transaction Tokens carry user identity and transaction context through an internal call chain. They say nothing about whether an AI agent was involved.
The Intent Token Summary
A user tells an agent "plan my business trip to Singapore." The agent decides which scopes that requires. Nobody checks its work.
OAuth 2.0 Agent Authorization Explicit Revocation Summary
RFC 7009 revokes one token at a time. The caller has to hold the token to revoke it.
Independent Implementation and Formal Analysis of Attenuating Delegation Chains for AI Agents Summary
Two individual drafts propose offline-verifiable delegation chains for AI agents. Each token in the chain can only narrow the authority of the one before it. Nobody outside the authors had…
Agent Authorization Center Summary
A personal agent running on your phone wants to book a ticket on a site it has never used. Who approves that, and does the user have to be interrupted every time?
OAuth Authorization Server Metadata Parameter for Requiring DPoP
A client can tell from AS metadata that an authorization server supports DPoP. It cannot tell that the AS requires it.
OAuth User Authorization Management URI
Most authorization servers have a page where the user can see which apps have access to their account and revoke them. A client has no standard way to find that page.
User-Mediated Credential Delivery for AI Agents Summary
Most MCP servers today are configured with a static API key pasted into an environment variable. The key is long-lived, broadly scoped and hard to revoke.
"OAuth Client Metadata Lookup: Ask the AS What It Thinks of Your Client"
A Client ID Metadata Document (CIMD) is the client's description of itself. It says nothing about what a given authorization server will accept.
An Attenuated Delegation Profile for Automated Agents
An API can't tell whether an accountable person stands behind an agent. It also can't trust the agent to stay inside the task, because "only search" is a request to a model and not a limit…
OAuth 2.0 Delegated Authorization Summary
An orchestrator agent holds an access token and wants to hand part of that access to a sub-agent. Today it has two options. It can share the token, which gives away everything. Or it can…
Authorization Evidence and Audit Trail for OAuth 2.0 Access Tokens
When a user approves an agent's request, the AS knows what the user was shown and what they clicked. Nobody else does. The resource server gets a token, and an auditor gets nothing.
Delegation Chaining for the Identity Assertion JWT Authorization Grant
ID-JAG covers one hop: a client trades an identity assertion for a grant it redeems at another authorization server. It accepts an actortoken but says nothing about what to do with it.…
Scenario-Based Service Discovery and Authorization Protocol in Agent Environments
An agent lands on an application it has never seen. It doesn't know what the application lets agents do, which API or MCP server to call, or how to get a token for the user.
CIMD Software Statements, a Third-Party Review Pinned to the Exact Bytes of a Client's Metadata
A Client ID Metadata Document is self-asserted. The client publishes its own metadata at a URL and can change it at any time. An AS that allowlists the URL knows who the client is. It has…
CIMD Software Statement Lifecycle, Withdrawing and Replacing a Third-Party Review After the Grant Is Open
The CIMD Software Statement draft lets a third party sign off on one exact version of a client's Client ID Metadata Document. The AS checks that statement once, when the grant opens.…
CIMD Software Statement Registration, Putting a Reviewed Client ID Metadata Document Through Dynamic Client Registration
The CIMD Software Statement draft lets a third party sign a digest of one exact version of a client's Client ID Metadata Document. That statement carries no metadata, only the digest.
OAuth Client IP Range Metadata, Letting Clients Publish Their Egress IPs to the Authorization Server
Hosted OAuth clients usually call the token endpoint from a known set of IP addresses. Enterprises want to restrict access to those addresses. Today every vendor publishes its ranges in…
Grant Catalog, an Authenticated Feed That Tells the IdP What to Put in an ID-JAG
ID-JAG lets an enterprise IdP issue a grant that a SaaS application's authorization server redeems for an access token. The IdP has to know what that application will accept: the tenant…
Mission-Bound Authorization, a Task Record That Gates Every Token an Agent Gets
OAuth has grants and tokens. It has no object for "the task the user approved." An agent working on a multi-step job collects tokens for several audiences, refreshes them, and hands…
Mission Resource Access, a Generic RAR Type for Resources, Actions, and Constraints
Mission-Bound Authorization records what a user approved for an agent's task as RAR authorizationdetails entries. It defines no entry type of its own. Every example in it uses…
Resource Parameter in the Access Token Response, Telling the Client Which Resource a Token Is Good For
Resource Indicators lets a client say which resource it wants a token for. The AS never says what it actually did with that request. It can honor it, narrow it, swap it for a default, or…
RFC 9728bis, Relaxing the Protected Resource Metadata Resource Match to a Path Prefix
Protected Resource Metadata has a strict rule. When a client follows a WWW-Authenticate challenge to a metadata document, the resource value in it must be identical to the URL the client…
Attenuating Authorization Tokens for Agentic Delegation Chains Summary
An orchestrator agent holds a token that covers a whole workflow. Each sub-agent only needs a small piece of it. If the sub-agent gets the full token, a prompt injection or a hallucinated…
OAuth 2.0 JWT Authorization Grant with DPoP Binding
A JWT authorization grant under RFC 7523 is a bearer credential. Anyone who steals the assertion can redeem it for an access token.
AAuth Agentic Authorization OAuth 2.1 Extension Summary
This is the other AAuth. It shares a name with Dick Hardt's AAuth Protocol and nothing else. Where Hardt's draft replaces OAuth, this one is a 45-page OAuth extension: one grant type, one…
Transaction Authorization Challenge Lets a Resource Server Demand Approval for One Specific Operation
An access token says the caller is allowed to talk to an API. It doesn't say a human approved this particular $5,000 payment.
"Agent DNS-OAuth Link: Using an Access Token as Proof the Agent Hasn't Been Disabled"
An agent at company A calls a service at company B. B wants to know two things: is this really agent01.a.example, and has company A disabled it since yesterday?
KYAPay Token Exchange Summary
This draft lets an agent trade a KYAPay token for an OAuth access token at a service it has never registered with. It is the one draft in the Skyfire family that is actually an OAuth…
Proof-of-Intent (PoI) Chained State, Multi-Party Escalation, and Concurrency Extension Summary
An AI agent proposes a high-stakes action, like a loan or a prescription. A human has to approve it before the resource server executes it.
Cryptographic Proof-of-Intent (PoI) Core Protocol for Human-in-the-Loop (HITL) Step-Up Authorization Summary
An AI agent holds a valid access token and calls a high-consequence API, like originating a loan or writing a prescription. The resource server cannot tell whether a human reviewed those…
Agent Authorization Use Cases and Gap Analysis Update Update
Status: Individual draft (not adopted), Informational. Revision -05 published 27 October 2026, 16 days after -04. 51 pages, up from 48. 14 use cases, up from 13. Same six authors.
Transaction Token Chaining Profile Adds Transaction Context Update
This is a small update. Revision -01 was published October 26, six weeks after -00. Three things changed, and each one traces to a GitHub issue rather than to list feedback.
Authorization Schemas -01, Three New Authors and No Technical Changes Update
The -01 is an author list change and an IANA cleanup. Sections 1 through 11 are word-for-word identical to -00.
Client Attester Endorsement -01, an Alignment Update Update
This is a maintenance update. It catches up with ABCA -12 and SPIFFE Client Authentication -03. The mechanism is unchanged.
OAuth 2.0 Client Instance Identifiers -01, an Alignment Update Update
This is a maintenance update. It catches up with ABCA -12 and gets a shorter title. The mechanism is unchanged.
Actor Chain -03, One Version Number and a Copyedit Update
Very little. This revision arrived 19 days after -02 and is almost entirely a copyedit.
Actor Chain Overview -01, A Copyedit to Match Protocol -03 Update
Almost nothing. This revision arrived two weeks after -00 and is a copyedit that syncs the overview with Actor Chain -03.
Additional Authentication Method Reference Values Update (-03) Update
Revision -03 is a substantial rewrite. The -02 draft was a list of one-line definitions. This version adds a composition model, two appendices of examples, and real definitions for most…
Identity Verification Methods Values Update (-03) Update
Revision -03 adds five new ivm values for verifying organizations. Nothing else changed. None of the feedback from the previous review of -02 was addressed.
KYAPay Token Update Update
Status: Individual draft (not adopted), Standards Track. Revision -03 published 2 November 2026, one month after -02. 46 pages, up from 36. Same two authors.
Using KYAPay Tokens Update Update
Status: Individual draft (not adopted), Standards Track. Revision -02 published 2 November 2026. 45 pages, up from 32. Same three authors.
Revocation Closure and Authority Epochs for Agent Delegation Update Update
This update covers -01 to -03. The real changes landed in -02. The -03 revision is editorial only: author metadata, a reference bump and tooling fixes.
October 26, 2026 21 reviews
OAuth Scope Metadata Document Summary
OAuth scopes are opaque strings. When a client or an AS sees a scope it doesn't recognize, nothing tells it what that scope means.
Selective Disclosure for JWT Access Tokens, Without Changing the Token
JWT access tokens often carry user attributes like email and name. Once they're in the token, they show up everywhere the token goes: token stores, gateway logs, and every resource server…
AAuth Protocol Summary
AAuth is a new authorization protocol for AI agents, not an OAuth extension. At -11 it is 164 pages, defines five access modes, five token types, three HTTP headers, four metadata…
JWT Access Tokens as W3C Verifiable Credentials
OAuth access tokens and W3C Verifiable Credentials are both signed statements from an issuer about a subject, presented by someone holding a key. Today a deployment that wants both issues…
Domain-Specific Authorization Schemas for OAuth 2.0
Scopes don't work well for agent tasks. Take "help me find and buy a laptop." A broad scope like purchase gives the agent unchecked spending power. Narrow scopes mean the agent keeps…
One Profile for the act Claim Across Grants, Access Tokens, and Transaction Tokens
RFC 8693 defined the act claim and then left most of the hard parts open. It says an actor is identified by sub, mentions that iss "might be necessary" to disambiguate, and calls the…
Actor Proofs, Having Each Actor Sign Its Own Delegation Hop
The Actor Profile puts actors in the act claim. The Actor Receipts companion has the AS sign a record of each hop. Both are the AS's word. A compromised or dishonest AS can mint a token…
Actor Receipts, Having Each Authorization Server Sign the Hop It Added
The Actor Profile puts the delegation chain in the act claim. The whole chain is covered by one signature, the current token issuer's. A resource server reading a three-hop chain is taking…
Seven Strings to Say What Kind of Thing Is Calling
Nothing. The document history for -02 says "No changes" and a diff against -01 confirms it. This revision was posted on October 16, one day before -01 would have expired. It's a keepalive,…
Actor Chain -02, Six Profiles and a Bootstrap Endpoint for Multi-Hop Delegation
A request passes through services A, B, and C before reaching resource D. Token Exchange lets each hop add itself to a nested act claim, but RFC 8693 says earlier actors in that chain are…
Actor Chain Overview -00, A Ten-Page Map of the Actor Chain Protocol
This draft adds no new protocol. It is the Informational companion to Actor Chain -02, which was split out of the 109-page -01.
Anti-Money Laundering Methods Values
This draft defines a single JWT claim, aml, whose value is an array of short strings naming which Anti-Money Laundering (AML) and Countering the Financing of Terrorism (CFT) screening…
Additional Authentication Method Reference Values Summary
This draft adds nine new values to the IANA amr (Authentication Methods References) registry and rewrites the definition of one existing value, tel. That's the whole spec. There are no new…
Identity Verification Methods Values Summary
This draft defines one new JWT claim, ivm (Identity Verification Methods), plus a registry of eight values for it. The claim lists how a person's identity was proofed: a database check, a…
KYAPay Token Summary
This draft defines a JWT that an agent shows to websites and APIs. The token says who the human behind the agent is, which agent platform it runs on, and optionally carries a single-use…
Using KYAPay Tokens Summary
This draft goes with the KYAPay Token format. It defines a KYAPay-Token HTTP header for carrying the token. It defines a "recipient" role for the party that validates it. Most of the…
Revocation Closure for Agentic Authorization Systems Summary
Revoking a token doesn't mean the agent has stopped. By the time a user hits "revoke", an agent may have exchanged its token for downstream tokens, handed work to sub-agents, or queued…
OAuth 2.0 Authority Metadata
A scope name tells you nothing about what it actually does. payments.manage might cover reading, creating, executing, or deleting payments. You can't tell from the name.
Signed Delegation Chains for Brokered Authorization Requests
Brokered OAuth is everywhere. A client sends the user to broker A. Broker A is a client of broker B, which is a client of the authorization server that actually asks for consent and issues…
Agent Authorization Use Cases and Gap Analysis Update Update
Status: Individual draft (not adopted), Informational. Revision -04 published 11 October 2026. 48 pages, up from 40. Six authors, up from five. 13 use cases, up from 11. Seven gaps in the…
Authorization Posture Mechanism (APM) Update Summary Update
There's one big change. The draft now includes a patent licensing statement.
October 13, 2026 12 reviews
Taking a Transaction Token Across the Trust Boundary
Transaction Tokens carry the authorization context of a request through a company's internal call chain. They are deliberately scoped to one trust domain. The Txn-Token spec says a…
"AAuth -11: The Person Server Admits It's an Identity Provider"
AAuth is now at -11 and 164 pages long. The Document History says the revision was "restructured for readability," and the sections do now follow the order an implementer meets them. The…
Attestation-Based Client Authentication -12, What Changed and Is It Ready for Last Call?
Attestation-Based Client Authentication (ABCA) lets a client backend vouch for an individual client instance, like a specific install of a mobile app or wallet, without the backend ever…
"Deferred Token Response: authorization_pending for Every Grant"
Every OAuth grant today assumes the authorization server can decide on the spot. The client makes a token request, and it gets back a token or an error.
Per-Call Proofs for Local MCP Tools Are a Token Endpoint and Introspection in Disguise
MCP's authorization spec only covers HTTP. For the stdio transport, the MCP authorization spec says implementations "SHOULD NOT follow this specification, and instead retrieve credentials…
Making the act Claim Mean the Same Thing in Every Token
Alice tells an AI travel agent to book a trip. The agent gets a token from her enterprise IdP, trades it at the travel provider's AS for an access token, and calls a booking tool. The…
Client Attester Endorsement, the Missing Link Between ABCA and CIMD
This is one of two companion drafts published together on top of Attestation-Based Client Authentication (ABCA). The other is Client Instance Identification, reviewed in a separate post…
Client Instance Identification for Attestation-Based Client Authentication
This is the second of two companion drafts published together on top of Attestation-Based Client Authentication (ABCA). The first, Client Attester Endorsement, answers "who may attest for…
The OOB Flow Comes Back, Hosted by the Client This Time
A CLI running over SSH can't receive a redirect. The user's browser is on their laptop, the client is on a server somewhere, and http://127.0.0.1:port/callback points at the wrong machine.…
Transactional Access Tokens Bring Txn-Token Context to the Front Door
Transaction Tokens solve the inside of the house. An API gateway receives an external access token, swaps it at a Transaction Token Service for a short-lived txntoken+jwt, and every…
Letting the Audience Decide Who Can Exchange Its Tokens
A resource server receives an access token audienced to itself. It needs to call a downstream API. That token is no good downstream, so the resource server uses Token Exchange to swap it…
Personal Agent Protocol (Poppy) Draft 0.1 Summary
Personal agents are already showing up at companies' front doors. Today the company either lets the agent pretend to be the user, typing in the user's password and clicking through web…
September 9, 2026 1 review
Identity Continuation Assertion for OAuth 2.0 Token Exchange
A workload receives an access token and needs to call the next service for the user, possibly after the user is gone. It holds nothing the next authorization server will accept. When…
September 2, 2026 6 reviews
Requiring a Fingerprint Every Time You Click Send
SMTP AUTH proves a session was opened with valid credentials. It doesn't prove the human clicking Send owns them.
AuthZEN Profile for Authorization Claims in JWT Access Tokens
RFC 9068 registers three claims for JWT access tokens: groups, roles, and entitlements. It says what they're named and recommends drawing them from the SCIM user schema. It says nothing…
AuthZEN Profile for OAuth 2.0 Token Issuance
Every OAuth spec that defines a moment where the AS decides whether to mint a token describes the inputs carefully and then stops. RFC 8693 says the decision is governed by policy it…
AuthZEN Binding for OAuth 2.0 Token Exchange
RFC 8693 conditions a successful token exchange on the request meeting "all policy and other criteria of the authorization server." It defines neither. Identity chaining, the identity…
The X.509 Assertion the Authorization Server Isn't Allowed to Trust
Workloads already have certificates. SPIFFE/SPIRE and Athenz hand every service a short-lived X.509 cert with a spiffe:// URI SAN, rotate it automatically, and use it for mutual TLS…
Agent Delegation Profile Update Update
Two days after -00, this draft went from 28 pages to 48. The author answered one of the four questions from the previous review, added the asor comparison the WG was going to have to write…
September 1, 2026 2 reviews
Handing the Subject's Signing Key to the Resource Server
A user signs something. Not the client, the user. A payment instruction, a delegation constraint, some application-layer statement that narrows what the client is allowed to do on their…
Cursor-Based Pagination for Multi-Valued Attributes in SCIM (-01 update) Update
draft-kushwaha-scim-attr-cursor-pagination-01 — Saurabh Kushwaha (Oracle), submitted 30 August 2026. Same single author. Intended status changed from Informational to Standards Track, and…
August 31, 2026 2 reviews
An Attenuated Delegation Profile for Automated Agents
A person asks an agent to rent a car. That agent hires a second agent at a different company. The second agent calls the rental service's API. The rental service is now two hops from the…
OAuth Profile for Delegated AI Agent Authorization
AI agents call protected APIs for human users. The author's position is that this doesn't need new OAuth mechanisms, it needs fewer choices.
August 26, 2026 12 reviews
Agent Authorization Use Cases and Gap Analysis
Status: Individual draft (not adopted), Informational, 39 pages, 5 authors. Revision -03 published 25 August 2026.
SCIM Use Cases (draft-correia-scim-use-cases-03)
draft-correia-scim-use-cases-03 by Paulo Jorge Correia (Cisco) and Pamela Dingle (Microsoft).
SCIM Use Cases
draft-correia-scimusecases-00 by Paulo Jorge Correia (Cisco) and Pamela Dingle (Microsoft).
SCIM Agent Governance Extension
draft-kushwaha-scim-agent-governance-00 — Saurabh Kushwaha (Oracle), submitted 26 July 2026. SCIM working group, intended status Informational.
Cursor-Based Pagination for Multi-Valued Attributes in SCIM
draft-kushwaha-scim-attr-cursor-pagination-00 — Saurabh Kushwaha (Oracle), submitted 8 April 2026. Individual submission, intended status Informational.
SCIM DID/VC Binding Extension
draft-kushwaha-scim-didvc-binding-01, Saurabh Kushwaha (Oracle), submitted 24 August 2026. SCIM working group, intended status Standards Track. 45 pages.
SCIM Extension for Tenant-Aware Identity Provisioning
draft-kushwaha-scim-tenant-resource-00 — Saurabh Kushwaha (Oracle), submitted 25 August 2026. SCIM working group, individual submission, 29 pages.
OAuth 2.0 Policy-Based Anonymous Access Tokens
draft-li-oauth-policy-based-anonymous-tokens-00 — Kretzler, Li, Wang, Fressancourt (all Huawei), submitted 26 August 2026.
SCIM 2.0 IPSIE Profile
draft-schreiber-scim-ipsie-profile-00 is an individual submission from Jen Schreiber (CrowdStrike) and Danny Zollner (Okta). It's 13 pages, Informational, and it's the SCIM half of the…
AI Agent Resource Extension for SCIM
Enterprises already push human users into SaaS apps with SCIM. This draft says agents should ride the same rails.
SCIM Group Member Resource Type Extension
draft-zollner-scim-group-members-01 — Danny Zollner (Okta), submitted 15 April 2026. Individual submission, intended status Standards Track.
SCIM 2.0 Interoperability Profile
draft-zollner-scim-interop-profile-01 — Danny Zollner (Okta), submitted 15 April 2026. Individual submission, 11 pages, no working group adoption activity yet.
August 21, 2026 23 reviews
DAWN Problem Statement
The draft identifies a gap in the AI ecosystem: there is no standardized mechanism for discovering AI entities (agents, tasks, workloads, models, datasets, compute resources) across…
MDI Information Model for DAWN
The DAWN working group has defined a concept called Minimum Discoverable Information (MDI) — the minimal set of metadata a discovering party needs to identify, triage, and reach an entity…
DAWN Terminology (draft-farrel-dawn-terminology-04)
As distributed systems proliferate — including AI agents, cloud workloads, software services, and network functions — there is no consistent shared vocabulary for talking about how…
Agent-Awareness in IPv6 Networks (draft-he-dawn-ipv6-agent-aware-framework-00)
Standard IPv6 forwarding routes packets to reachable destinations. AI agent traffic requires more: a destination must not only be reachable but suitable — possessing the right model…
Privacy Considerations for DAWN
The core insight this draft is trying to document: the act of discovery itself leaks sensitive information. When an AI agent queries a discovery substrate for capabilities or resources,…
Zero-Configuration Agent Discovery via mDNS
Current agent-to-agent communication protocols (A2A, MCP) assume the connecting party already knows the agent's hostname or URL. This spec addresses the gap for local-network environments…
Heterogeneous Credential Verification for Workload and Agentic Systems
Modern workloads and AI agents increasingly present multiple credential types in a single request — workload identity tokens, OAuth access tokens, W3C Verifiable Presentations, X.509…
A Survey of AI Agent Discovery Mechanisms
This draft addresses the fragmented landscape of AI agent discovery: there are numerous competing mechanisms (from IETF drafts, industry consortia like AAIF, 3GPP, and open-source…
DAWN Use Cases
This draft catalogs use cases for the Discovery of Agents, Workloads, and Named Entities (DAWN) — the general problem of how one entity (an AI agent, workload, service, or human operator)…
Requirements for the Discovery of Agents, Workloads, and Named Entities (DAWN)
Modern distributed systems — including AI agent networks, cloud workloads, and software services — increasingly need to discover each other dynamically, across organizational and…
Carrying Remote Attestation Evidence in Workload Identity Tokens (WIT)
WIMSE defines Workload Identity Tokens (WITs) for conveying workload identity in service-to-service communication, but does not address how to prove that the workload is running in a…
DAWN Gap Analysis
DAWN (Discovery of Agents, Workloads, and Named entities) is a proposed IETF effort to define interoperable mechanisms for discovering AI agents, tools, compute resources, datasets, and…
Signed Authorization-Evidence Records for WIMSE-Authorized AI Agent Actions
This draft addresses a specific audit gap in the companion AI agent authentication and authorization draft (by Kasselman et al.): that draft specifies how AI agents obtain identity and…
Transitive Attestation for Sovereign Workloads — A WIMSE Profile
Bearer tokens and private keys are "context-agnostic" — a stolen credential works from any environment. This spec introduces a mechanism called Proof of Residency (PoR) to…
Execution Context Tokens (ECTs) for Distributed Agentic Workflows
WIMSE establishes who a workload is, but creates no record of what it did. ECTs fill this gap by providing a cryptographically signed, tamper-evident audit record of task execution in…
WIMSE Applicability for AI Agents
AI agents operate autonomously across multiple systems with minimal human oversight, but existing security models treat them as extensions of user or device identities rather than as…
WIMSE Workload Attestation Summary
WIMSE's existing workload-to-workload authentication (WIT + WPT) proves who a caller is and that it holds the right private key, but says nothing about where the workload is running or…
Cross-Organizational Delegation for Workload and Agent Identity: Problem Statement and Requirements
This draft addresses the authorization challenge that arises when autonomous AI agents delegate sub-tasks across organizational boundaries — for example, an orchestrator agent at Company A…
WIMSE Trust Domain Discovery
When a relying party receives a workload credential scoped to an unfamiliar trust domain, it currently has no standardized way to obtain the cryptographic trust anchors (signing keys or CA…
DNS-Based Agent Naming (DAN): AIDISCA and AIINDEX Resource Records
AI agents operating across different organizations and internet domains have no standardized mechanism to discover one another's network endpoints and capabilities. This draft addresses…
draft-sweeney-wimse-credential-delegation-00 Review
OAuth 2.0 was designed around human users interacting with browsers. Autonomous AI agents are ephemeral, potentially numerous, and—uniquely—adversarially promptable via prompt injection.…
Condition-Bounded Credentials
Current WIMSE deployments compensate for the risk of key exfiltration by using short-lived credentials that rotate frequently. This draft argues that if the binding key itself is…
DNS-like Agent Discovery Architecture
This draft proposes a three-tier hierarchical discovery architecture for the "Internet of Agents" (IoA) — an anticipated world of millions to billions of software agents that need to find…
August 20, 2026 5 reviews
Agent Authorization Profile (AAP) for OAuth 2.0
Draft: draft-aap-oauth-profile-01 Author: A. Cruz (Independent)
Government Content Access Control (GCAC) Summary
Governments increasingly mandate that online services restrict content based on user age or legal status, but existing mechanisms require personal data disclosure or enable cross-service…
PACT - Private Agent Consent and Trust Profile
PACT addresses the challenge of deploying an AI agent that simultaneously requires three distinct things: machine-verifiable identity, explicit human consent, and privacy-preserving…
Authorization Posture Mechanism (APM) Summary
Existing OAuth mechanisms (certificate binding, DPoP, step-up authentication) make security decisions at token issuance or at coarse session granularity. APM proposes to re-evaluate three…
Condition-Bound Keys for Mutual-TLS Client Authentication and DPoP
OAuth's sender-constraining mechanisms (mTLS, DPoP) prove only that a key was possessed at the time of a request — they say nothing about whether the user is still present or the platform…
August 19, 2026 1 review
Identity Continuation Assertion for OAuth 2.0 Token Exchange
The spec solves a narrow but real problem: how to continue a user's delegated identity across a chain of services when each service uses pairwise (audience-local) subject identifiers that…