[OAUTH-WG] Revocation closure semantics for delegated agents: scoping and queued effects
Deonté O’dell Watts <deonte@goodshyt.fun> Thu, 15 October 2026 07:35 UTC
Received: from cyan.elm.relay.mailchannels.net (cyan.elm.relay.mailchannels.net [23.83.212.47]) (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 CA06446 for <oauth@ietf.org>; Thu, 15 Oct 2026 07:35:52 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=goodshyt.fun header.s=hostingermail-a header.b=hFUsNxF8; spf=pass (mx.ietf.org: domain of deonte@goodshyt.fun designates 23.83.212.47 as permitted sender) smtp.mailfrom=deonte@goodshyt.fun; dmarc=pass (policy=none) header.from=goodshyt.fun
X-Sender-Id: hostingeremail|x-authuser|deonte@goodshyt.fun
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 94531381C82; Thu, 15 Oct 2026 07:35:45 +0000 (UTC)
Received: from de-fra-smtpout5.hostinger.io (100-96-2-108.trex-nlb.outbound.svc.cluster.local [100.96.2.108]) (Authenticated sender: hostingeremail) by relay.mailchannels.net (Postfix) with ESMTPA id F4073381F0E for <oauth@ietf.org>; Thu, 15 Oct 2026 07:35:44 +0000 (UTC)
X-Sender-Id: hostingeremail|x-authuser|deonte@goodshyt.fun
X-MC-Relay: Neutral
X-MC-Copy: exfiltrated-credentials
X-MailChannels-SenderId: hostingeremail|x-authuser|deonte@goodshyt.fun
X-MailChannels-Auth-Id: hostingeremail
X-Bitter-Rock: 7821c75c0c29bb00_1792049745397_2454392564
X-MC-Loop-Signature: 1792049745397:535430723
X-MC-Ingress-Time: 1792049745396
Received: from de-fra-smtpout5.hostinger.io (de-fra-smtpout5.hostinger.io [148.222.55.12]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.96.2.108 (trex/8.0.2); Thu, 15 Oct 2026 07:35:45 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=goodshyt.fun; s=hostingermail-a; t=1792049743; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=8kpaQoV1UB4CmqjabiORGVul0QY7dEpc/VZlDMpJmqc=; b=hFUsNxF8XjlT6YTa8FTxTPwBuHicI3QTdoyJ76ZqB5+dTJXCVSGTmsRaKtOb/z886V61iV QJ3C4mTy/kTIUPLgasdYXoHszO13Yq3r1sF4L3wau6vmnLQcJrBGCR4Pd2+wE9/u2EO8ao Sr3aPHtpr6+Aixi1A0caSafOuAWCtQr08qpN+W/XtjmF4ZuCO3vtQeY6KN7+1g9OAo092q 50Yy9Z+iHoaLWIIDHQL3KxnWzLHDjSenpKIsWEo4tjG7hZDlvC0jvHNpDEBpmwNoc4rgBR xb4r6FEMF1VkM7nZkjH+dONi9vF8Q3zuzzj0CI8jCHEivl9T1SW8NgTnm42Tmg==
Received: from localhost (117.138.230.35.bc.googleusercontent.com [172.206.38.251]) (Authenticated sender: deonte@goodshyt.fun) by smtp.hostinger.com (smtp.hostinger.com) with ESMTPSA id 4j50H265Dkz3wg9 for <oauth@ietf.org>; Thu, 15 Oct 2026 07:35:42 +0000 (UTC)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
From: Deonté O’dell Watts <deonte@goodshyt.fun>
Message-Id: <1792049742505717449.1792049742@goodshyt.fun>
Mime-Version: 1.0
To: oauth@ietf.org
Date: Thu, 15 Oct 2026 07:35:42 +0000
X-CM-Analysis: v=2.4 cv=etGNzZpX c=1 sm=1 tr=0 ts=6ad0824e a=nlulKshti6RtM0+kxUjmAA==:117 a=nlulKshti6RtM0+kxUjmAA==:17 a=IkcTkHD0fZMA:10 a=MKtGQD3n3ToA:10 a=1oJP67jkp3AA:10 a=M51BFTxLslgA:10 a=48vgC7mUAAAA:8 a=Vt9zUbIiGsN6ATniwc8A:9 a=QEXdDO2ut3YA:10 a=kXFT7po6Sud2k9_Qsw0N:22 a=NWVoK91CQySWRX1oVYDe:22
X-CM-Envelope: MS4xfJL3VHqCPuGQewbyh58V69AdBWKc71biF2aA0JgxwRuCClaZjSb9izi+2AV4rogQWwrVXWyHfMlwCZ0pf3yhiKff9sjYpJUZlimn4vuuGtealH/UqoVC mOcqrkjCzpXL31PxArvPhP7D9EJ/gtYc2sfldax9URfDi7rhrqvS3e4hZDT2s/D8BmwR2fyy6hWoOQ==
X-AuthUser: deonte@goodshyt.fun
X-Spamd-Bar: -------------------------
Message-ID-Hash: YTCEDY64QHUH7IAO4CI4U4QH32W7LFRQ
X-Message-ID-Hash: YTCEDY64QHUH7IAO4CI4U4QH32W7LFRQ
X-MailFrom: deonte@goodshyt.fun
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-oauth.ietf.org-0; 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: [OAUTH-WG] Revocation closure semantics for delegated agents: scoping and queued effects
List-Id: OAUTH WG <oauth.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/zb3FqNpEi8MgBSTWXMlx6wZYC7k>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Owner: <mailto:oauth-owner@ietf.org>
List-Post: <mailto:oauth@ietf.org>
List-Subscribe: <mailto:oauth-join@ietf.org>
List-Unsubscribe: <mailto:oauth-leave@ietf.org>
Hello OAuth WG, I would appreciate feedback on a narrow interoperability question connected to existing agent-authorization and revocation work. RFC 7009 addresses token revocation, and draft-chen-oauth-agent-revocation-00 explores agent-level cascade operations. My individual Informational draft, draft-watts-oauth-agent-revocation-closure-01, separates three events: receipt of a revocation request, invalidation of authority artifacts, and an evidence-backed claim that consequential operations within a declared scope can no longer commit using the revoked authority epoch. Document: https://datatracker.ietf.org/doc/draft-watts-oauth-agent-revocation-closure/ Concrete scenario: A delegated agent is revoked after an asynchronous operation has been queued and after a derived token has been issued. An upstream endpoint reports completed revocation, while a downstream job can still commit. The draft models this using scoped closure, enforcement cut sets, unresolved-path statuses, and authority epochs. This is intended to complement existing OAuth work, not change RFC 7009 or introduce a new grant type. I would value WG guidance on: 1. Whether any existing draft already defines the interoperable conditions for asserting downstream effect closure, as distinct from invalidating tokens or returning cascade counts. 2. Whether an interoperable scoped closure indication is useful across administrative domains, or whether it should remain implementation-local. 3. If this merits WG attention, whether narrow requirements and negative test vectors would be more valuable than a new protocol object. I am particularly interested in contrary examples or prior art demonstrating that current semantics already cover this case. The current document is an individual I-D, not a WG-adopted document. Regards, Deonté O’dell Watts Independent Researcher | GoodShyt Group Inc. ORCID: 0009-0005-8586-3650 https://datatracker.ietf.org/doc/draft-watts-oauth-agent-revocation-closure/
- [OAUTH-WG] Revocation closure semantics for deleg… Deonté O’dell Watts
- [OAUTH-WG] Re: Revocation closure semantics for d… Thilina Senarath
- [OAUTH-WG] Re: Revocation closure semantics for d… Lombardo, Jeff
- [OAUTH-WG] Re: Revocation closure semantics for d… Deonté O’dell Watts
- [OAUTH-WG] Re: Revocation closure semantics for d… Deonté O’dell Watts
- [OAUTH-WG] Re: Revocation closure semantics for d… Deonté O’dell Watts
- [OAUTH-WG] Re: Revocation closure semantics for d… caleb.dayton93
- [OAUTH-WG] Re: Revocation closure semantics for d… Caleb Dyer
- [OAUTH-WG] Re: Revocation closure semantics for d… Deonté O’dell Watts
- [OAUTH-WG] Re: Revocation closure semantics for d… Kieran Sweeney