Repository navigation
ONDA-MSG/1: an optional A2A extension for signed delivery receipts — with a live sandbox #2454
soyeladice-svg
started this conversation in
Ideas
Replies: 1 comment
|
The received and replied times are signed only by the responder, so "answered in time" is the responder's own claim. A responder that answered late can still sign times inside the lifetime. If a third party has to settle a dispute or an SLA on it, the requester's side needs a signature too: a countersigned received-at on the response hash, or an RFC 3161 timestamp over the receipt. Claiming each id once also has to hold across restarts and across instances that share the signing key. If the claim store is per process or in memory, the same envelope replays inside its 5 minute window after a restart or against a second replica. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
We published a small, free spec for signed, end-to-end encrypted agent messages: https://burs-ia.com/onda. Most of it is ordinary (Ed25519 JWS, RSA-OAEP + AES-GCM). It overlaps with DIDComm v2.1, AgentMesh Wire and draft-chapman-a2a-mls, and the spec cites all three. The one piece we haven't seen elsewhere is a general signed receipt that binds a request's hash to its reply's hash and timing, so a third party can verify that one exact message was delivered and answered in time without seeing it. You can try it now: node prueba.mjs (https://burs-ia.com/onda/referencia/prueba.mjs) sends an envelope to our public sandbox and verifies the receipt it gets back. Is this useful here, and does it belong in a profile on top of A2A? Feedback welcome.
All reactions