I-D Action: draft-sato-soos-mjwt-04.txt

Internet-Draft draft-sato-soos-mjwt-04.txt is now available.

   Title:   The Mandate JWT (MJWT) for Agentic AI Systems
   Author:  Tom Sato
   Name:    draft-sato-soos-mjwt-04.txt
   Pages:   40
   Dates:   2026-08-13

Abstract:

   An AI agent that can act without a verifiable, human-traceable
   authorization record is an agent without an owner.  Existing
   authorization credentials tell you what an agent is permitted to do;
   none of them tell you who authorized it, on which specific object,
   under which mission, or how far that authority can be delegated
   before it reaches this agent.

   This document defines the Mandate JWT (MJWT): a WIMSE workload
   credential profile that binds an AI agent's authority to a specific
   Sovereign Object instance under a named human principal, with a
   cryptographically enforced delegation ceiling and a seven-dimensional
   Narrowing Property that prevents any sub-agent from exceeding the
   authority of the human principal at the root of the chain.  Version
   -02 adds a seventh narrowing dimension (consent scope), the
   consent_scope claim carrying data subject consent state for
   APPI/GDPR compliance, the sub_agent_scope claim for consent
   attenuation across delegation hops, a Purpose Code Registry, and
   HEM_CONSENT_REQUIRED integration for fail-closed consent enforcement.
   The MJWT is the authorization primitive referenced by
   [I-D.sato-soos-idp], [I-D.sato-soos-hem], [I-D.sato-soos-gar],
   [I-D.sato-soos-cap], and [I-D.sato-soos-sov].

   Version -03 corrects an IANA registration issue in Section 13
   (IANA notice #1456068): the two registries requested there are
   renamed to drop the redundant word "Registry" from the registry
   name itself, and each now includes the Designated Expert Guidance
   that a Specification Required registration policy requires per
   [RFC8126].  No new claims, codes, or normative behavior are
   introduced in -03; this is a registration-format correction only.

   Version -04 addresses four findings from a WIMSE security review
   checklist dry-run against -02/-03 (DR-MJWT-KIA-CHECKLIST-01):
   Section 8.1 Step 9's parent-mandate check is tightened from a
   disjunctive "retrieve or verify" to a mandatory live
   re-verification of the parent's current signature and revocation
   status, closing a parent-swap-class window (Section 11.8);
   Section 7.1's Revocation Registry is now stated explicitly to be
   the same Revocation Registry [I-D.sato-soos-kia] Section 8
   defines, and Section 7.2 now names the residual cross-instance
   propagation-lag risk this implies, mirroring how
   [I-D.sato-soos-kia] discloses its own XPID revocation gap
   (Section 7.5); and a new Security Considerations entry states
   plainly that MJWT does not itself establish or verify a
   human_principal_id's root authority (Section 11.9).

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-sato-soos-mjwt/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-sato-soos-mjwt-04

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-sato-soos-mjwt-04

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


_______________________________________________
I-D-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]