WIMSE Applicability for AI Agents#

Yuan Ni, Chunchi Peter Liu (Huawei) — draft-ni-wimse-ai-agent-identity

• Why: Agentic identity made explicit in a standards body: AI agents blur network boundaries, exhibit unpredictable access patterns, arrive over-privileged, and escape accountability — "no identity → no access control → no accountability."
• What: Applies the WIMSE architecture to AI agents: an identity server issues agent credentials via an identity proxy with attestation evidence, with requirements for bootstrapping-independent trustworthy identities, automated credential management, minimal-privilege access tokens, and explicit workflows.
• How: The core proposal is a dual-identity credential — the agent's identity bound to its owner's (a user or an organization admin) as the input to access control — instantiated through a credential-request / user-confirmation-and-signature flow. Open questions include counter-signing design choices, credential-format extensions, whether hardware roots of trust in user devices should anchor the process, and initial trust establishment between identity server and proxy. Positioned against CHEQ's per-task double-confirmation tokens: this is per-identity credentials instead.
• Where applicable: Any trust domain hosting agent workloads (API agents, MCP-style clients). Huawei-driven individual contribution asking to become a WIMSE WG item — early, but agentic identity is moving from blog posts to standards requirements here.