[Agentproto] Re: New I-D: Pulse (draft-effortel-pulse-00), real-time spend control for AI gateways
Nicholas Templeman <nicholas@csoai.org> Fri, 18 September 2026 08:22 UTC
Received: from out-2uec-a88.jellyfish.systems (out-2uec-a88.jellyfish.systems [63.250.43.88]) (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 BA30030 for <agentproto@ietf.org>; Fri, 18 Sep 2026 08:22:13 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=csoai.org header.s=default header.b=tsxsnrkv; dmarc=pass (policy=none) header.from=csoai.org; spf=pass (mx.ietf.org: domain of nicholas@csoai.org designates 63.250.43.88 as permitted sender) smtp.mailfrom=nicholas@csoai.org
Received: from MTA-09.privateemail.com (unknown [10.50.14.19]) (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 BSN-01.privateemail.com (Postfix) with ESMTPS id 4hmQZv08tdz3hhT9 for <agentproto@ietf.org>; Fri, 18 Sep 2026 04:21:59 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=csoai.org; s=default; t=1789719718; bh=d+7U15376tOOXlqSnVYt717UbWQv+NmxrMvepwKF0H8=; h=Date:From:To:In-Reply-To:References:Subject:From; b=tsxsnrkvtobZh/oTxm2+ol11pjEmqX9zMhVEk4jACjNxj8UQ7c4stbjm2g+2GIWkf o1zTV1diJilzKiE4Xd+WMlyjmXWJxw79P8V2F1LZXs9kwyP23oSsegIj4LiYSSryKo BXGNr69bJ0uE4Al1NgA30SNdQkSBdBj8f374KpndCj7B//WOVVodblS4uTpwBB/Ek6 3ch4/wbyJpxO5Khdhc48ehWwKsogU7lhQmuVQVqIWD8u0fmc0uf3TAxmaffPjgCA3D 8is3z1K2X2SHKjQIIUwdo2EU5hDKdvwwjnOpltMwxSoR0vQMKRbbOzHnaaKB1BUdSZ o4Wf22qvwMuoQ==
Received: from mta-09.privateemail.com (localhost [127.0.0.1]) by mta-09.privateemail.com (Postfix) with ESMTP id 4hmQZt6458z3hhTK for <agentproto@ietf.org>; Fri, 18 Sep 2026 04:21:58 -0400 (EDT)
Received: from APP-13 (unknown [10.50.14.213]) by mta-09.privateemail.com (Postfix) with ESMTPA for <agentproto@ietf.org>; Fri, 18 Sep 2026 04:21:58 -0400 (EDT)
Date: Fri, 18 Sep 2026 04:21:58 -0400
From: Nicholas Templeman <nicholas@csoai.org>
To: agentproto@ietf.org
Message-ID: <981690670.61187.1789719718540@privateemail.com>
In-Reply-To: <353FA6AE-F9E7-48F1-A023-D2AB5C7E45FA@mainlabs.ai>
References: <353FA6AE-F9E7-48F1-A023-D2AB5C7E45FA@mainlabs.ai>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.6-Rev95
X-Originating-Client: open-xchange-appsuite
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spamd-Bar: -
Message-ID-Hash: LWMKAXZVB5CG7CHKZH6FNSUJAN2COTYH
X-Message-ID-Hash: LWMKAXZVB5CG7CHKZH6FNSUJAN2COTYH
X-MailFrom: nicholas@csoai.org
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: [Agentproto] Re: New I-D: Pulse (draft-effortel-pulse-00), real-time spend control for AI gateways
List-Id: Agent Communication Protocols <agentproto.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/agentproto/pxaKfAVjBHuGY71ud_X9tcY-Krg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/agentproto>
List-Help: <mailto:agentproto-request@ietf.org?subject=help>
List-Owner: <mailto:agentproto-owner@ietf.org>
List-Post: <mailto:agentproto@ietf.org>
List-Subscribe: <mailto:agentproto-join@ietf.org>
List-Unsubscribe: <mailto:agentproto-leave@ietf.org>
Hi Martin, Sumit and all, Apologies for my earlier empty message on reserve, settle and evidence boundaries. Building on Sumit's point about the quota and receipt sides, I would keep three claims separate when linking Pulse to an evidence record: what consumption was authorised, what the charging server accepted and settled, and what was independently observed to execute or be delivered. The draft is explicit that gateway reports are attestations of consumption rather than independent proofs of the meter, and that no money crosses outward on the protocol. A linked evidence format should preserve those limits rather than turn a charging receipt into proof of delivery or an external payment. One useful cross-implementation example would be a final Report whose acknowledgement is lost and then retried. The retained record should distinguish the repeated transport attempt from a new settlement, while preserving the fresh envelope's current action state alongside any replayed result. Another would be a settled action for which the execution or delivery evidence is unavailable; the financial/accounting state and that evidence gap should remain visible separately. These are proposed integration checks, not claims that Pulse lacks these semantics. I have not run the implementation or established interoperability. I am also not asking to widen the agentproto charter to cover charging; the venue question you raised remains separate. Disclosure: I work on measurement and evidence tooling at CSOAI Ltd. The aim is a small, inspectable linkage between records, not a mandate for our implementation. Best regards, Nicholas Templeman CSOAI Ltd nicholas@csoai.org
- [Agentproto] New I-D: Pulse (draft-effortel-pulse… Martin Petkov
- [Agentproto] Re: New I-D: Pulse (draft-effortel-p… Sumit Ahuja
- [Agentproto] Re: New I-D: Pulse (draft-effortel-p… Nicholas Templeman
- [Agentproto] Re: New I-D: Pulse (draft-effortel-p… Bradley B
- [Agentproto] Re: New I-D: Pulse (draft-effortel-p… Martin Petkov
- [Agentproto] Re: New I-D: Pulse (draft-effortel-p… Girish Konda
- [Agentproto] Re: New I-D: Pulse (draft-effortel-p… Sumit Ahuja
- [Agentproto] Re: New I-D: Pulse (draft-effortel-p… Martin Petkov