What is the adoption and standardization status of Security Principal and Verifier Binding for Agent Communication Protocols?

Internet-Draft, Intended Status: Informational; expires 17 April 2027 — phase draft, governed by Individual Internet-Draft submitted under BCP 78 and BCP 79; listed under the Agent Communication Protocols workgroup label.. Adoption: unmeasured. Version: draft-bu-agentproto-security-principal-binding-08 (2026-10-14). Last verified 2026-10-18.

Security Principal and Verifier Binding for Agent Communication Protocols

2 · Identify

Candidate · auto-drafted, unreviewed · confidence 60%

Security Principal and Verifier Binding for Agent Communication Protocols
Category	Identify
Governed by	Individual Internet-Draft submitted under BCP 78 and BCP 79; listed under the Agent Communication Protocols workgroup label.
Status	Internet-Draft, Intended Status: Informational; expires 17 April 2027
Phase	draft
Implementation	none found
Adoption	unmeasured
Version	draft-bu-agentproto-security-principal-binding-08 (2026-10-14)
Specification	https://datatracker.ietf.org/doc/html/draft-bu-agentproto-security-principal-binding-08
Found at	none; a protocol-neutral review and specification-authoring model, not a wire protocol
Last checked	2026-10-18
Freshness	current · checked 2026-10-18
Solves	Prove an agent's identity, Delegate a user's authority to an agent, Audit what an agent did

Security Principal and Verifier Binding for Agent Communication Protocols is an agentic-web standard (document format) at step 2, Identify, governed by Individual Internet-Draft submitted under BCP 78 and BCP 79; its own status is "Internet-Draft, Intended Status: Informational; expires 17 April 2027" (draft). It answers: How can an agent communication protocol state, for each security-relevant claim (user authority, agent instance, tool identity, delegation, session, action evidence), which field carries it, which party verifies it, and what happens when it is absent, stale, or unverifiable? Adoption is unmeasured, last verified 2026-10-18.

Identify An individual IETF Internet-Draft that defines a protocol-neutral matrix format for separating security claims such as user authority, agent instance identity, tool identity, delegation, session binding and action evidence. For each claim, the matrix records the carrier field, the verifier, the binding and freshness rule, the failure behavior, and the accepted result. It also defines row-outcome semantics and dependency-closure rules so that composite results are not stronger than their verified inputs. It is Informational guidance and does not define a wire protocol.

Discovery and probe

none; a protocol-neutral review and specification-authoring model, not a wire protocol

NONE 
parse:     
on absent: Not applicable; no site-observable artifact is defined.

Not probed live: no-fixed-path. candidate record; probe rule pending

History

2026-10-16 — auto-drafted candidate from exa (https://datatracker.ietf.org/doc/html/draft-bu-agentproto-security-principal-binding-08)

Instances

No instances recorded yet.

References

Internet-Draft -08 published 14 October 2026, Intended Status Informational, defining a verifier-facing claim matrix format, row-outcome semantics (satisfied, unsatisfied, indeterminate, unsupported, not-evaluated, not-applicable) and dependency-closure rules for composed mappings. States it does not define a new agent protocol, token format, audit log or authorization system. — https://datatracker.ietf.org/doc/html/draft-bu-agentproto-security-principal-binding-08 (2026-10-14) REPORTED

JSON · Markdown