[Agentproto] Re: WG Review: Agent Communication Protocols (agentproto), comment in support with one request
Kehan Yao <khyao78@gmail.com> Tue, 22 September 2026 08:16 UTC
Received: from mail-wr2-x0f.google.com (mail-wr2-x0f.google.com [IPv6:2a00:1450:4864:30::f]) (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 7EA7E30 for <agentproto@ietf.org>; Tue, 22 Sep 2026 08:16:14 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=gmail.com header.s=20251104 header.b="RTM6/qtC"; arc=pass ("google.com:s=arc-20260327:i=1"); dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx.ietf.org: domain of khyao78@gmail.com designates 2a00:1450:4864:30::f as permitted sender) smtp.mailfrom=khyao78@gmail.com
Received: by mail-wr2-x0f.google.com with SMTP id ffacd0b85a97d-482f635552aso3147904f8f.2 for <agentproto@ietf.org>; Tue, 22 Sep 2026 01:16:14 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1790064967; cv=none; d=google.com; s=arc-20260327; b=NGwsGWjiQKW3ZV/NT8kB18QeJ1/lstpQsWVy9USZYZkNm257txxEuS9xffh5TSkFa2 t2qs71FvWsWca6NsZFy0KoTxcSctmy03rUdbzQ/Sj6iK9FFL4EDtD2oV5gWtq5cih5KC 7JbagWpf3fpdgoBvLw627qQ0dtSS9OZoWsO8KL/sBg1Z2EHXuUitv2SCGENKHTNE43UI 2mLPkQroiEJd+AJhknUQki6idERnQfE0sjrWGpRIiNewpwd2+nj24kEL9cSyNkKwOu/k fiy3g02wY7OEcdK9WNo8UfOEodtRnI7hGO607eG6mabIBA8BM2xnPjOZ8RKb0cJdgzrg 6//g==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=RL2Jz+ZxA1gTMCF3sqiex8SadLnsa/aEQVzAXlu0PxY=; fh=pxlnUmUV3VxWLXyrB/pTJVhTiNilOpC+QNQFHmr1kCU=; b=mNb7t/e2XNPAtuQHO75Tl7CyyUy8ZMOJM3bUxIWlmSd86XmlD4EEC7j7THnOWSpZGv hFQJ1vnsSAYTffIbZIDI9tPSZTx7DTYB4/u7xhZM9nva5Y+UT1OyXNSSRRD+Zli9aPvT i/I//BL+dQnYZ27rz8QlfBl33pQVqg5rz0qWqxbNB0Fe5KtpLaorvNpI2rCN6jnu6Yv7 LxjEt2Vgx6JRvOzo+dPQgKAYNvzcb9CpuqrK3RuRP6hL3ulKnb8vihn86YO0kC9PgzxI LCNeZ8CtRTW7k0LmmnBYnU5Kl1uUNv5qTZL8rBm15Kl0zfpr1nLpAgsi1RS3VgU7BVEJ aGxQ==; darn=ietf.org
ARC-Authentication-Results: i=1; mx.google.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1790064967; x=1790669767; darn=ietf.org; h=content-type:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:from:to:cc:subject:date:message-id:reply-to :content-type; bh=RL2Jz+ZxA1gTMCF3sqiex8SadLnsa/aEQVzAXlu0PxY=; b=RTM6/qtCFouRH+ciTTsbgzQ1FU89XtNlhilGWHefbic6jUSijFMw24qeCQCkpoi/e8 085Q+6cVZWwBOzOsYSeqX0oZdMqxV8shG6/qWVQbfvy5zz/oQfl3F2Nnp9RDrgGKrdWw Ev5iTmfco+uJXzaYT0TiN4tLkCcUl6qUgrmWdGT9ybm6jQZ6MZKru4u+gllPpMPgxs32 tmyYxh23hDfnRBEPGftQ9enl6R6blYi+ygN/PTHyTfpYVbC6Jni5BtEsWQV9vBdX63fR 2XWjYOBRE1EasCGpQkRaXCHrREzKGlDXXZtBdWXyJZ9h00gn3pocyCr2ukzD/4Ct7VzV ykTQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1790064967; x=1790669767; h=content-type:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:x-gm-gg:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to:content-type; bh=RL2Jz+ZxA1gTMCF3sqiex8SadLnsa/aEQVzAXlu0PxY=; b=gDMb28Coc6Fzxoj9QiYOc65Q1SAtpDUzZGzygTKjrQt4JzSHGZqt/1Q4tBVX+X0iPg HaNksC7I0GrwB6kK+2XNJJU43QV5bub6IiT4RcgiZgZ6GVwFOAGgsmCF1wYJqBnt91uq +RUhkcTTN7RcCA4rWzTHQ+B8uHJyFX1GwTFuzkLIr2nXqMNomUFZy1U8GxFHuCUC4Y1T BDDdyQyGEWHWSHFyHbZTdZ7s13LXF2lbLW+ZWPFzvYFyAiQVUHuRqEwWcVg0BOSP/bMq ax8EYhB9SBGDnRTl2xQKAS9f9CfBW0deqahFQ9FZGojWCGMkuoDZhYOCphwkkvbR2WxQ 3X0g==
X-Forwarded-Encrypted: i=1; AKwUvByfxVNzHBPQ+vE1SvexRuh3J/QHQhNPcffSzVQHL/OP/p8intcSMS5R9XDJ5tWayaAeTYXtlDs73RcL@ietf.org
X-Gm-Message-State: AFuF++kAoHln1Ysff37joEVAsl/4r5e8BCY+mNq6PEAJwydZDeXdYBHF zzTp38ePCHfDA8sziUamHykp6NEEA6ZLOFW0N/z9XTtGyo3rsfdkxE2CTJ/1YRd/m3cxxLCmLtB yWrc44SLE2EcZthNOnKENBjqP01PnnBk=
X-Gm-Gg: AYBFou1AFo1yzmfVFe69j9FdrGNfV64eT4UanGIuFEjEPcqoVpnBPqc0rcbG3wetvXd /z1bNhvntdr2sD2O0fzuqWIRPx21O47IY30wmgP9cWhB5wPNr22egGkXNMj2n1eyca2wpt9qkSV mtDAFAZs2kScdz8HYxXpnXU1i5hQxt3mf4dlxt7UJxW18ejv1sHZA8OZVngQtffxSD+5LTIjWKG lezfBq1rpoq7PGHe7d2g45Cr40NWGGct82LpR7eJjdcJaYjwu0wgSS3+hIZYPw25QL0S2mn79Xd X79LnVKf6tP9CdhfGgaA2im+9vjI2cisWna4A5x+F476+V6xAJt0tIrTj1LhNCZhsD4ucFsC2K7 aw+LZWCQwJ+KGrRm3F0oWss46FS9yZIyDL0Ye0h2zN3Y1et94yjVzSNsm
X-Received: by 2002:a05:6000:420a:b0:487:35c:6e6b with SMTP id ffacd0b85a97d-4871e244c95mr20299836f8f.12.1790064966735; Tue, 22 Sep 2026 01:16:06 -0700 (PDT)
MIME-Version: 1.0
References: <29283729.644.1790048687028@privateemail.com> <CAMW0qhi8aHuucZjCZ79r0L+koTk7__8qVvdqwooO24iADsJ-0A@mail.gmail.com>
In-Reply-To: <CAMW0qhi8aHuucZjCZ79r0L+koTk7__8qVvdqwooO24iADsJ-0A@mail.gmail.com>
From: Kehan Yao <khyao78@gmail.com>
Date: Tue, 22 Sep 2026 16:15:53 +0800
X-Gm-Features: AcwNN1XzKGFzdjLOUXdaLJTjDRbnaaUZJ9oJhYJGytbsi2a7uhcYk0tuj7RZB5k
Message-ID: <CABYiY4u+eZM_cBecG2nauRz3ug+Kw0-8Y0aDG8szbmATXniPBg@mail.gmail.com>
To: Girish Konda <girish.sai1@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000779cb2065c0dfa2e"
X-Spamd-Bar: --
Message-ID-Hash: C43P4DSBBGUHJKASUUWKETMFEQZUAS2Z
X-Message-ID-Hash: C43P4DSBBGUHJKASUUWKETMFEQZUAS2Z
X-MailFrom: khyao78@gmail.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
CC: Nicholas Templeman <nicholas@csoai.org>, iesg@ietf.org, agentproto@ietf.org
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [Agentproto] Re: WG Review: Agent Communication Protocols (agentproto), comment in support with one request
List-Id: Agent Communication Protocols <agentproto.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/agentproto/8FnuAkIoX1ISOraVgeXvjplGmk0>
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 Girish, Thanks for raising this. I agree with the underlying concern that confirmation of termination or revocation is important. My reading, though, is that the current charter text does not need to change to accommodate it. The bullet on managing the full dialog lifecycle, including establishment, modification, termination, and revocation of propagation relationships, is already broad enough to cover this. It does not exclude a requirement that a participant be able to distinguish termination/revocation that is confirmed from termination/revocation that is requested but unconfirmed. IMHO, what you're describing reads to me as a specific protocol requirement for termination/revocation behavior. That is better raised and settled during protocol design rather than enumerated in the charter. Best regards, Kehan Girish Konda <girish.sai1@gmail.com> 于2026年9月22日周二 15:46写道: > Hey Folks, > > I have been following this discussion since the charter went to external > review. I support the charter as scoped and have one comment on the dialog > lifecycle item. > > I agree with Sumit Ahuja's comment on 17 September that revocation is the > hard half of the lifecycle, and that a lifecycle which specifies revocation > but assumes a reachable, still-credentialed peer will not cover the cases > Pamela Dingle and Naveed Ihsanullah raised at the Vienna BoF. I would add > one thing to it. Once the peer may be unreachable, the participant that > asked for termination is in one of two states, and they are not the same > state. Either the termination took effect at every hop that was carrying > the dialog, or it was requested and the status at some hops is unknown. The > charter already commits the group to recovery from failures of network > paths and intermediaries and to handling unreachability, so both states are > in scope, but it does not say the protocol has to let a participant tell > them apart. > > That matters because the two states call for different behaviour. A > participant that knows termination is confirmed everywhere can release the > context and stop worrying about it. A participant that only knows the > request went out has to keep treating the dialog as possibly live, and has > to pass that uncertainty up to whatever is above it. If the protocol > carries no way to express the difference, implementations will report the > second state as the first, because that is the reporting that looks clean > and nothing on the wire contradicts it. > > I want to be clear that this is not a request to reopen audit. PR 120 ( > https://github.com/ietf-artarea/charters/pull/120) rules audit data > structures out of scope and I think that is right. Nicholas Templeman made > a related point on 21 September about audit records, that an absent record > should read as not observed rather than as nothing happened, and I am > asking for the same distinction one step earlier, at the moment the > participant is told what happened rather than only in the record that is > written afterwards. If the participant was told the wrong thing then the > record is faithful and still wrong. This sits closer to PR 123 ( > https://github.com/ietf-artarea/charters/pull/123) which separates agent > decision-making from protocol behaviour, because what I am describing is > squarely protocol behaviour. It is about what a peer is allowed to say back. > > I am not asking for a new deliverable or for new scope. One sentence in > the dialog lifecycle item, saying that a participant must be able to > distinguish termination that is confirmed from termination that is > requested but unconfirmed, would be enough to keep it in front of the group. > > Disclosure: I work on multi-tenant control plane infrastructure at > Microsoft, and in my personal time I build agentic and MCP tooling and > participate in a few MCP working groups. Peers that go unreachable and > sessions that may or may not still be alive are a daily problem for me. I > recently built mcp-pacemaker (https://github.com/girishkvs/mcp-pacemaker) > a supervised MCP bridge that keeps servers alive across host restarts, > machine reboots, token expiry and transport failures. This is my personal > opinion and does not reflect my employer's. > > Thanks, > Girish Konda > > On Mon, Sep 21, 2026 at 8:46 PM Nicholas Templeman <nicholas@csoai.org> > wrote: > >> Dear IESG, >> >> I support chartering agentproto as scoped in the 17 September text. The >> scope is >> well bounded: dialog identifiers, lifecycle semantics and context >> propagation, >> with the content exchanged with models expressly outside it, and changes >> to MCP >> and A2A left with their maintainers. >> >> One request on the reference architecture rather than the charter text. >> The key >> considerations name auditability of agent-initiated actions distinct from >> user-initiated actions as a reason for distinct agent identity, and dialog >> identifiers are what a later reader will use to correlate records. It >> would help >> if the reference architecture said plainly that a dialog identifier >> establishes >> correlation and not that an action occurred, so that a record which is >> absent is >> read as not observed rather than as nothing happened. That is a statement >> about >> what the protocol's artefacts can carry, not a new deliverable, and it >> does not >> require naming any effort that is not yet chartered. On that point I >> agree with >> Orie's note of 20 September: coordination with a group that may later >> exist is >> ordinary work with the ADs and does not belong in charter text. >> >> Disclosure: I work on measurement and evidence tooling at CSOAI Ltd. This >> is an >> individual comment, I hold no IPR relevant to the charter, and I am not >> asking >> for anything of ours to be referenced. >> >> Nicholas Templeman >> Council of AI (csoai.org) >> _______________________________________________ >> Agentproto mailing list -- agentproto@ietf.org >> To unsubscribe send an email to agentproto-leave@ietf.org >> > _______________________________________________ > Agentproto mailing list -- agentproto@ietf.org > To unsubscribe send an email to agentproto-leave@ietf.org >
- [Agentproto] WG Review: Agent Communication Proto… Nicholas Templeman
- [Agentproto] Re: WG Review: Agent Communication P… Girish Konda
- [Agentproto] Re: WG Review: Agent Communication P… Kehan Yao
- [Agentproto] Re: WG Review: Agent Communication P… Lionel Morand
- [Agentproto] Re: WG Review: Agent Communication P… Hesham Moussa
- [Agentproto] Re: WG Review: Agent Communication P… Girish Konda