[dmsc] Re: Fwd: New Version Notification for draft-feng-agentproto-idl-info-model-00.txt
Chris Hood <chris@nomotic.ai> Tue, 28 July 2026 01:08 UTC
Return-Path: <chris@nomotic.ai>
X-Original-To: dmsc@mail2.ietf.org
Delivered-To: dmsc@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 2EF5E11F86AF4; Mon, 27 Jul 2026 18:08:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1785200915; bh=2r41u52HGlQpm5wlHuTkWRrGBciMfWCs8mAclqZdmik=; h=Subject:In-Reply-To:From:To:Cc:Date; b=sjJPoRioXOie6VrIZcNC7QKWFJ0+fYP8PbvfASDJY1Sp2KKtGlnaOjJJ9AXBh7Ouc hcj4AuvTheJp0va3ja1oMGAfj2C4xdsg8FxK+vn2d1OfrE+fJ26mXyBxhs27ZdEPuc iqCR/bLGy6+UsdFIPsHmM8lGOlk35dsx0RG6j1wI=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=nomotic.ai
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E9yVda7PI-gM; Mon, 27 Jul 2026 18:08:34 -0700 (PDT)
Received: from cheetah.ash.relay.mailchannels.net (cheetah.ash.relay.mailchannels.net [23.83.222.34]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 1CDE711F86AED; Mon, 27 Jul 2026 18:08:32 -0700 (PDT)
X-Sender-Id: hostingeremail|x-authuser|chris@nomotic.ai
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 0D1C76270D; Tue, 28 Jul 2026 01:08:25 +0000 (UTC)
Received: from fr-int-smtpout19.hostinger.io (trex-green-8.trex.outbound.svc.cluster.local [100.103.96.220]) (Authenticated sender: hostingeremail) by relay.mailchannels.net (Postfix) with ESMTPA id A1B2062998; Tue, 28 Jul 2026 01:08:23 +0000 (UTC)
X-Sender-Id: hostingeremail|x-authuser|chris@nomotic.ai
X-MC-Relay: Neutral
X-MailChannels-SenderId: hostingeremail|x-authuser|chris@nomotic.ai
X-MailChannels-Auth-Id: hostingeremail
X-Turn-Minister: 28afbba45f0ce41a_1785200904924_4006532594
X-MC-Loop-Signature: 1785200904924:149628205
X-MC-Ingress-Time: 1785200904924
Received: from fr-int-smtpout19.hostinger.io (fr-int-smtpout19.hostinger.io [148.222.54.35]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.103.96.220 (trex/8.0.2); Tue, 28 Jul 2026 01:08:24 +0000
Received: from [IPv6:2600:381:a89b:9dbb:b07f:77b8:44a2:cdef] (unknown [IPv6:2600:381:a89b:9dbb:b07f:77b8:44a2:cdef]) (Authenticated sender: chris@nomotic.ai) by smtp.hostinger.com (smtp.hostinger.com) with ESMTPSA id 4h8HQY0KLjz1xnD; Tue, 28 Jul 2026 01:08:21 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomotic.ai; s=hostingermail-a; t=1785200901; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to; bh=2r41u52HGlQpm5wlHuTkWRrGBciMfWCs8mAclqZdmik=; b=eHNb5jwV9gAkIjU7sG534BDpFcw/NVNE69FtP2KWoLfAI5c+/EbfEua59mX/y7wYDJs6Sp T1Q05biTHbbiyWwRB++Trbg8ZRlR44QhNG+3d/ieZTkd1ar7rNs6hCfDWGCtKT3/lmrsFY E05SsuTR8TL40eK4KGyV9vQnEWOzkSyN6nuis8U0dDo14QdPtPwdW8wXpBb9sxnn1R7mAs ngF+7ZYWI/qjz7uS3i0JP+fi/WbW02tsGV8RdIqHWa4nCdXUE6Iux+YH2X1v0LeUwngUxO a6wEmQv8R5ZAiYhpgpBLwzJCgSiz5/NvwKrwccbngBFTBPtHyUQTvBbqztMcVA==
SavedFromEmail: chris@nomotic.ai
In-Reply-To: <CAMaYprtNwg251gF=QyHhWjEZf6FC_0CkPaivJdoYXtyn46Vo-Q@mail.gmail.com>
Importance: normal
From: Chris Hood <chris@nomotic.ai>
To: chong feng <fengchongllly@gmail.com>, agent2agent@ietf.org
MIME-Version: 1.0
Message-Id: <4h8HQY0KLjz1xnD@fr-int-smtpout19.hostinger.io>
Date: Tue, 28 Jul 2026 01:08:21 +0000
X-CM-Analysis: v=2.4 cv=BvrPwpX5 c=1 sm=1 tr=0 ts=6a680105 a=+EHdHApnEUPzevjOEc4Vag==:617 a=xqWC_Br6kY4A:10 a=48vgC7mUAAAA:8 a=pGLkceISAAAA:8 a=VaMHAfSVILNmDPPSVtgA:9 a=PRpDppDLrCsA:10 a=QEXdDO2ut3YA:10 a=fCWBfrJW_Y9vgyDu:21 a=_W_S_7VecoQA:10
X-CM-Envelope: MS4xfIn4UfF4oJ2HPb3iUXxLYn0ss/KXzXJ60497msfoj75AYRFRiRPaKxWVhZietklNCID4zTnPUG0HZ/hwGDcTlye4oNJGCMVLchnoLVUMGfMFgDI4wfRz tQo+Udq63bxsZfvH81ZEIoG4Lwo0N6FijCeMTq/9es7EOIasUWRSbsClMReWWdwWBYxIEqx+Ul8Hsx75AgrXyLKtjstJQuYr3eocCHtN4z7hkg1ZAmpYfU9J USNg9vEYSZox/AVDRWbbM6yr58llZjw7xxP2n9vSeellGfwB78ttdkiDPFrMe6iG/oALDN+sEVl/3DVihshZ81lkCX5MGCCz60ZSyk2Z65ZsuUzBNe1+NnZi 4qJHDrFziGRrCixW5sw+gSYl+8IVVm1Br8Riym3Jy4VsSuZ6teI=
X-AuthUser: chris@nomotic.ai
Message-ID-Hash: 56K7NT5KA5DAVYT5E3RKBZBXUYQQPP2R
X-Message-ID-Hash: 56K7NT5KA5DAVYT5E3RKBZBXUYQQPP2R
X-MailFrom: chris@nomotic.ai
X-Mailman-Rule-Hits: member-moderation
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"
X-Content-Filtered-By: Mailman/MimeDel 3.3.9rc6
CC: dawn@ietf.org, dmsc@ietf.org, ainetops@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [dmsc] Re: Fwd: New Version Notification for draft-feng-agentproto-idl-info-model-00.txt
List-Id: Dynamic Multi-agent Secured Collaboration <dmsc.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmsc/WSqcxPE2izy3AxhCKR_rSlZgHP0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmsc>
List-Help: <mailto:dmsc-request@ietf.org?subject=help>
List-Owner: <mailto:dmsc-owner@ietf.org>
List-Post: <mailto:dmsc@ietf.org>
List-Subscribe: <mailto:dmsc-join@ietf.org>
List-Unsubscribe: <mailto:dmsc-leave@ietf.org>
For your reference, review AGTP-API which places semantics inside of the methods on a dedicated transport. Benchmark tests show up to 29% improvement in accuracy for agent transaction. So the argument that agents need more than transport, endpoints, etc, is valid unless it's packaged as a first class citizen on the transfer layer. https://www.ietf.org/archive/id/draft-hood-agtp-apiChris -------- Original message --------From: chong feng <fengchongllly@gmail.com> Date: 7/27/26 4:47 PM (GMT-08:00) To: agent2agent@ietf.org Cc: dawn@ietf.org, dmsc@ietf.org, ainetops@ietf.org Subject: [dmsc] Fwd: New Version Notification for draft-feng-agentproto-idl-info-model-00.txt Hi all,I would like to share a new individual draft for review and discussion: IDL: A Semantic Information Model for Agent Communication draft-feng-agentproto-idl-info-model-00 https://datatracker.ietf.org/doc/draft-feng-agentproto-idl-info-model/IDL (Intent Description Language) is a protocol-independent semanticinformation model for communication among autonomous agents and betweenagents and tools.The motivation is that agent communication needs more than transport,message framing, endpoint discovery, or tool schemas. Before agents cancollaborate, they need a shared way to describe questions such as:* Who is the participating agent, and how is its identity bound to an authenticated principal?* What capabilities can it contribute to an intent?* Within what declared autonomy and authority boundaries may it act?* Which intent lifecycle roles and interaction patterns does it support?* What context does it require, maintain, or share?* Which observability, control, and intervention interfaces does it expose?The draft therefore defines an information model covering agent identity,capability declarations, autonomy envelopes, intent participation, context,and governance interfaces.IDL is intended to complement agent communication and discovery protocols,rather than define another transport or messaging protocol. It also doesnot standardize agent behavior, decision-making, planning, or reasoningalgorithms. The JSON representation and interaction sequences in the draftare currently illustrative.I believe this semantic layer may be relevant to several related discussions:* agentproto, for capability exchange, agent selection, context transfer, negotiation, and protocol-visible interaction semantics;* DAWN, for describing the semantics of discovered agents and workloads;* DMSC, for secure multi-agent collaboration and gateway-mediated interactions; and* AINETOPS, for autonomy, governance, and operational control of agents.Comments and suggestions would be very welcome, especially on:* whether this information-model layer fits the agentproto problem space;* overlap or alignment with existing agent description mechanisms;* the identity, credential-binding, and autonomy models;* missing semantics needed for agent selection and collaboration; and* how this model could be mapped to discovery or communication protocols.Best regards,Chong Feng---------- Forwarded message ---------发件人: <internet-drafts@ietf.org>Date: 2026年7月28日周二 07:40Subject: New Version Notification fordraft-feng-agentproto-idl-info-model-00.txtTo: Chong Feng <fengchongllly@gmail.com>A new version of Internet-Draft draft-feng-agentproto-idl-info-model-00.txthas been successfully submitted by Chong Feng and posted to theIETF repository.Name: draft-feng-agentproto-idl-info-modelRevision: 00Title: IDL: A Semantic Information Model for Agent CommunicationDate: 2026-07-28Group: Individual SubmissionPages: 41URL:https://www.ietf.org/archive/id/draft-feng-agentproto-idl-info-model-00.txtStatus:https://datatracker.ietf.org/doc/draft-feng-agentproto-idl-info-model/HTMLized:https://datatracker.ietf.org/doc/html/draft-feng-agentproto-idl-info-modelAbstract: This document defines the information model for IDL (Intent Description Language), a protocol-independent semantic model for communication among autonomous AI agents and between agents and tools. Autonomous agents are fundamentally different. An agent possesses its own reasoning, may negotiate parameters, may refuse or modify requests, and may initiate interactions on its own behalf. Describing an agent as if it were a deterministic endpoint loses exactly the properties that make it an agent. IDL answers: "what can this autonomous participant contribute to an intent, under what constraints, and through what interaction patterns?" IDL is not a transport, session, discovery, or messaging protocol. It is a semantic model that enables heterogeneous agents to describe identity, capabilities, autonomy boundaries, context requirements, governance interfaces, and intent participation before and during collaboration. This document defines the IDL information model and its relationship to agent communication protocols and governance frameworks. It does not define a normative JSON representation or a serialization-level conformance language. Protocol-specific mappings, including an AIN/ CDL profile, are informative.The IETF SecretariatDMSC mailing listTo subscribe or manage your subscription: https://mailman3.ietf.org/mailman3/lists/dmsc.ietf.org/