[Audit] Re: Mandate freshness: when valid delegation outlives current human intent
Mohamad Khalil Yossif <mohamad@yuthent.com> Sat, 03 October 2026 14:04 UTC
Received: from out-2z4y-a154.jellyfish.systems (out-2z4y-a154.jellyfish.systems [198.54.127.154]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id 430F542 for <audit@ietf.org>; Sat, 03 Oct 2026 14:04:52 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=yuthent.com header.s=default header.b=0Jh7cZLy; spf=pass (mx.ietf.org: domain of mohamad@yuthent.com designates 198.54.127.154 as permitted sender) smtp.mailfrom=mohamad@yuthent.com; dmarc=pass (policy=reject) header.from=yuthent.com
Received: from mail.privateemail.com (unknown [147.235.219.226]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.privateemail.com (Postfix) with ESMTPSA id 4hxnTN6Z7Tz8sWV for <audit@ietf.org>; Sat, 03 Oct 2026 14:04:40 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yuthent.com; s=default; t=1791036282; bh=IHa+7iRaxGNtjS8Ea+kWiT54db51icFf20zadfo9G44=; h=From:Subject:Date:To:From; b=0Jh7cZLyJ8oT+qkqZtpRe8TTt5zmgs6CdaR5ihTrYLXU7HYcEBzRzfH7izxBF+3nQ s5sZ9GVQhWBxgLE8fhxd/i16w4ecYCch+qPZ2FcsUn62UtI72UsXLhL5u5oqXYsKKJ wbs9xwwguBHkKCdcnHjcSINb0m4nCrWiDBS/lRrNx4kATdw1MA9W+Ch4LanawY17uF UkYSJGvrZnUYFCZWEr8Mt/iZGtapei5iwI4+O5i304SFeCZ8cEhsJPP4i7ETEQyJ5z rqI6A3suYNmuWXDFYQHqUHY/uig+TGCCEEvMPUjSPMEn/x4j2FjC+QkuP5gRpetY50 qijTGfYC3C9Ig==
From: Mohamad Khalil Yossif <mohamad@yuthent.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4A666296-BF83-469D-809E-28CEA1BA577B"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3901.100.1.1.12\))
Message-Id: <44D03B6F-F0B2-4BB5-8600-B72AC35F004C@yuthent.com>
Date: Sat, 03 Oct 2026 17:04:30 +0300
To: audit@ietf.org
X-Mailer: Apple Mail (2.3901.100.1.1.12)
X-Envelope-From: mohamad@yuthent.com
X-Spam-Level: **
X-Spamd-Bar: ++
Message-ID-Hash: 2X4QWYSVBSAS4P2BTPXAYSCZZ3YTCBK7
X-Message-ID-Hash: 2X4QWYSVBSAS4P2BTPXAYSCZZ3YTCBK7
X-MailFrom: mohamad@yuthent.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [Audit] Re: Mandate freshness: when valid delegation outlives current human intent
List-Id: "Agent Use of Delegation and Interaction Traceability (AUDIT)" <audit.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/audit/_Hw42Fau5WY6JZMuKGEtjLkg5Yk>
List-Archive: <https://mailarchive.ietf.org/arch/browse/audit>
List-Help: <mailto:audit-request@ietf.org?subject=help>
List-Owner: <mailto:audit-owner@ietf.org>
List-Post: <mailto:audit@ietf.org>
List-Subscribe: <mailto:audit-join@ietf.org>
List-Unsubscribe: <mailto:audit-leave@ietf.org>
> Jiayu, > > The distinction you are drawing is real and it is not token expiry. > > A grant can be unexpired, unrevoked, and correctly scoped while the > objective behind it has moved. Nothing in the authorization state > records that, because the authorization state was never a record of > the objective. It was a record of what was permitted. > > I published a problem statement on this in July: > > https://datatracker.ietf.org/doc/draft-yossif-agent-mandate-problem/ > > It states requirements and proposes no mechanism, deliberately. It > does not cover the case you are naming — it treats the mandate as > fixed once signed and asks whether later actions stay inside it. The > question of whether the mandate still reflects current intent is a > different one, and the draft does not ask it. > > Andreas Ehstand raised an adjacent gap on the same draft last week: > whether the Principal held the authority to grant in the first place. > His view, which I think is right, is that these separate into a > grant-time question and a use-time question, and that a requirement > could ask a mandate to state which rule governs it rather than > choosing one. > > Yours sits with the use-time half. If a mandate declares that it is > governed at use time, something has to be checkable at that moment, > and "the objective has not changed" is harder to make checkable than > "the signer's authority has not been withdrawn." > > Whether that belongs in the AUDIT charter I do not know. It may be > closer to the authorization layer than to the audit layer. But the > distinction is worth keeping separate from expiry wherever it lands, > because a system that only checks expiry will report the stale case > as valid. > > Mohamad Khalil Yossif
- [Audit] Mandate freshness: when valid delegation … LIJIAYU LI
- [Audit] Re: Mandate freshness: when valid delegat… Mohamad Khalil Yossif