The Scope Creep Automated reviews of new AI-related working group submissions

Meeting · IETF 127

WIMSE WG at IETF 127

San Francisco, US · November 14 to 20, 2026

13 drafts on the agenda, 13 reviewed here. Reviewed drafts have a short summary and a link to the full review. The rest show the draft's own abstract. Official agenda →

Agenda as of November 16, 2026. It can change before the meeting.

Session A 8 slots

  • Chair Updates

    Chairs · 10 min
  • Workload Proof Token

    Arndt · 10 min

    draft-ietf-wimse-wpt -02

    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.

    The Workload Proof Token (WPT) is that proof. It is a short-lived JWT, signed with the WIT's key, sent with each HTTP request.

  • WIMSE Architecture

    Joe · 10 min

    draft-ietf-wimse-arch -08

    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 defined.

    It also describes the components around a workload and the scenarios the protocol drafts are meant to serve.

  • AI Identity Management System (AIMS)

    Brian · 30 min

    draft-ietf-wimse-aims -01

    AI Identity Management System (AIMS)

    People keep inventing new authentication and authorization schemes for AI agents. Most of them rebuild things that already exist.

    This draft argues that an agent is a workload (Section 4). It then shows how WIMSE, SPIFFE, OAuth and OpenID Shared Signals already cover agent identity, credentials, authentication, authorization and monitoring. It defines no new protocol.

  • Workload Authorization Grant

    Paul · 30 min

    draft-carleton-workload-authz-grant -02

    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. So every agent in an installation ends up sharing one credential, and nobody can tell which agent did what (Section 1).

    This draft lets an authorization server trust the platform once. After that, any agent the platform vouches for gets an access token on its first request, with its own stable identifier.

  • Workload Identity Metadata

    Yaroslav · 10 min

    draft-heigh-wimse-workload-identity-metadata -00

    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 parse the path and authorize on the pieces.

    The draft says to stop doing that. The identifier names the workload. Group, role, and entitlements travel separately as Workload Metadata, either as claims in a JWT credential or from an authenticated lookup API.

  • Cross-Organizational Delegation Requirements

    Reese · 10 min

    draft-reece-wimse-cross-org-delegation -02

    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 invoking a tool at Company B on behalf of a human at Company A. Existing workload identity and token mechanisms (including OAuth and RFC 8693 token exchange) were designed for shallow, intra-organization delegation to a known authorization server. This draft argues they cannot handle: recursive authority attenuation across multiple hops, cross-org verification without pre-provisioned federation, and offline verification without per-request callbacks.

    This is a problem statement and requirements document only — it does not propose a solution.

  • AOB

    Chairs · 10 min

Session B, joint with OAuth (Thursday) 11 slots