[dmsc] Re: IICP follow-up: implementation experience with intent-based agent selection and routing
Aijun Wang <wangaijun@tsinghua.org.cn> Wed, 30 September 2026 02:41 UTC
Received: from mail-m155101.qiye.163.com (mail-m155101.qiye.163.com [101.71.155.101]) (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 E3E864B for <dmsc@ietf.org>; Wed, 30 Sep 2026 02:41:02 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=none; dmarc=none; spf=pass (mx.ietf.org: domain of wangaijun@tsinghua.org.cn designates 101.71.155.101 as permitted sender) smtp.mailfrom=wangaijun@tsinghua.org.cn
Received: from LAPTOP09T7970K (unknown [219.142.69.76]) by smtp.qiye.163.com (Hmail) with ESMTP id 4f91f289a; Wed, 30 Sep 2026 10:40:48 +0800 (GMT+08:00)
From: Aijun Wang <wangaijun@tsinghua.org.cn>
To: 'Roble Mumin' <mail@roblemumin.com>
References: <8C087A62-9947-402B-9D93-C4065C49C05A@roblemumin.com> <001201dd4eeb$724ccda0$56e668e0$@tsinghua.org.cn> <860E85B4-BDF6-4F3C-ACCF-50331CB30784@roblemumin.com> <003001dd4fdb$1e297b10$5a7c7130$@tsinghua.org.cn> <D6BDA136-C1DD-42FC-9E38-DF3B57BF5CD3@roblemumin.com>
In-Reply-To: <D6BDA136-C1DD-42FC-9E38-DF3B57BF5CD3@roblemumin.com>
Date: Wed, 30 Sep 2026 10:40:47 +0800
Message-ID: <000501dd5085$19a79b30$4cf6d190$@tsinghua.org.cn>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQKTiCAMxOwBScSb2i30banPNOzEJAIvkZVWAl00Y+8B+LIoNANYQhnJtSsJ9iA=
Content-Language: zh-cn
X-HM-Tid: 0aa0f02f9f7503a2kunmdf60aa89200f88
X-HM-MType: 10
X-HM-Spam-Status: e1kfGhgUHx5ZQUpXWQgPGg8OCBgUHx5ZQUlOS1dZFg8aDwILHllBWSg2Ly tZV1koWUFKTEtLSjdXWRgWCB1ZQUpXWS1ZQUlXWQ8JGhUIEh9ZQVkZSR4fVhpCHUtLGh1PGUIZSl YeHw5VEwETFhoSFyQUDg9ZV1kYEgtZQVlJSkJVSk9JVU1CVUxNWVdZFhoPEhUdFFlBWU9LSFVKS0 lPT09IVUpLS1VKQktLWQY+
X-Spamd-Bar: /
Message-ID-Hash: 4MDUZW6ADKXFO5TUPFPURF5L2RADKK4L
X-Message-ID-Hash: 4MDUZW6ADKXFO5TUPFPURF5L2RADKK4L
X-MailFrom: wangaijun@tsinghua.org.cn
X-Mailman-Rule-Hits: member-moderation
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="UTF-8"
X-Content-Filtered-By: Mailman/MimeDel 3.3.10
CC: dmsc@ietf.org
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [dmsc] Re: IICP follow-up: implementation experience with intent-based agent selection and routing
List-Id: Dynamic Multi-agent Secured Collaboration <dmsc.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmsc/iwlbbqqBQL_-kSy0FbV8d2KZdLM>
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>
Hi, Roble: Thanks for your preparation of the “IICP Overall Architecture and Component Interface”! I think it is one useful guide to digest deep into the current IICP status and future cooperation with the DMSC for the standardization of capabilities/intent based internet of AI agent. Especially, the Appendix D, “Path to the an IETF architecture draft” outlines the necessary step for our future work. We will digest it, and the related documents in the following days, and try to begin the discussions after our National Holiday(October 1-7, 2026). Any other interested experts can discuss the concepts and architecture of IICP in these days in advance. Best Regards Aijun Wang China Telecom From: Roble Mumin [mailto:mail@roblemumin.com] Sent: Tuesday, September 29, 2026 11:25 PM To: Aijun Wang <wangaijun@tsinghua.org.cn> Cc: dmsc@ietf.org Subject: Re: [dmsc] IICP follow-up: implementation experience with intent-based agent selection and routing Hi Aijun, hello DMSC, thank you again for suggesting a consolidated IICP architecture document. I have now prepared the updated v0.1.3 handover package of “IICP Overall Architecture and Component Interfaces” and attached it to this message. The document consolidates the existing IICP architecture, component responsibilities and interfaces into one reviewable reference, with a DMSC/IICP architectural crosswalk and source-linked evidence so that similarities, differences and possible standardization opportunities can be reviewed directly.
- [dmsc] IICP follow-up: implementation experience … Roble Mumin
- [dmsc] Re: IICP follow-up: implementation experie… Aijun Wang
- [dmsc] Re: IICP follow-up: implementation experie… Roble Mumin
- [dmsc] Re: IICP follow-up: implementation experie… Aijun Wang
- [dmsc] Re: IICP follow-up: implementation experie… Roble Mumin