[dmsc] Re: [agent2agent] Re: AI Enablement Interface for Communication Services

Aijun Wang <wangaijun@tsinghua.org.cn> Wed, 15 July 2026 03:52 UTC

Return-Path: <wangaijun@tsinghua.org.cn>
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 C4C5A116F835E; Tue, 14 Jul 2026 20:52:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784087548; bh=BLtU9j/6K3whVGmEgnhHPrWqGsxTnylKtQPc/KoYi2Y=; h=From:To:Cc:References:In-Reply-To:Subject:Date; b=Wm5i0suIt27SvllaWMT2W5/qg22l92VfSbHnoVi8wVWIOGvLsxEnQfc9rOSL4lkyX tHlmengT+uyEJKIKYanEj1zZZuEBDP9q+26jpE9eVczu7Lmc+bpG0r4pdDIzqkOKXc jpgedwgm69EXqVWlafYvGPAyUfw/XiEbiTPqjOnU=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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
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 XCrGVjXxFLpC; Tue, 14 Jul 2026 20:52:27 -0700 (PDT)
Received: from mail-m49197.qiye.163.com (mail-m49197.qiye.163.com [45.254.49.197]) (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 BD63E116F8346; Tue, 14 Jul 2026 20:52:21 -0700 (PDT)
Received: from LAPTOP09T7970K (unknown [219.142.69.77]) by smtp.qiye.163.com (Hmail) with ESMTP id 4639b0e6a; Wed, 15 Jul 2026 11:52:11 +0800 (GMT+08:00)
From: Aijun Wang <wangaijun@tsinghua.org.cn>
To: R.Jesske=40telekom.de@dmarc.ietf.org, chris@nomotic.ai, agent2agent@ietf.org
References: <1783955686462061191.1783955686@nomotic.ai> <FR5P281MB5370C3646B0C171F52FF9F4DF9F92@FR5P281MB5370.DEUP281.PROD.OUTLOOK.COM>
In-Reply-To: <FR5P281MB5370C3646B0C171F52FF9F4DF9F92@FR5P281MB5370.DEUP281.PROD.OUTLOOK.COM>
Date: Wed, 15 Jul 2026 11:52:10 +0800
Message-ID: <01d101dd140d$511c1c30$f3545490$@tsinghua.org.cn>
MIME-Version: 1.0
Content-Type: multipart/related; boundary="----=_NextPart_000_01D2_01DD1450.5F3F5C30"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQF8x0YOD67Wa9LaUPFfK0U7anHh4AJkwFV6txtkIKA=
Content-Language: zh-cn
X-HM-Tid: 0a9f63e74eb703a2kunm1fc4a7e164191
X-HM-MType: 10
X-HM-Spam-Status: e1kfGhgUHx5ZQUpXWQgPGg8OCBgUHx5ZQUlOS1dZFg8aDwILHllBWSg2Ly tZV1koWUFKTEtLSjdXWRgWCB1ZQUpXWS1ZQUlXWQ8JGhUIEh9ZQVlDGRhOVhkYH0lDSExDTRpCGl YeHw5VEwETFhoSFyQUDg9ZV1kYEgtZQVlJSkJVSk9JVU1CVUxMWVdZFhoPEhUdFFlBWU9LSFVKS0 hLSkxLVUpLS1VLWQY+
Message-ID-Hash: OPDMCVNVIGMBU2XU46Y3YL4WRYN7MOMJ
X-Message-ID-Hash: OPDMCVNVIGMBU2XU46Y3YL4WRYN7MOMJ
X-MailFrom: wangaijun@tsinghua.org.cn
X-Mailman-Rule-Hits: member-moderation
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address
X-Content-Filtered-By: Mailman/MimeDel 3.3.9rc6
CC: dmsc@ietf.org, draft-yu-dmsc-ai-agent-use-cases-in-6g@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [dmsc] Re: [agent2agent] Re: AI Enablement Interface for Communication Services
List-Id: Dynamic Multi-agent Secured Collaboration <dmsc.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmsc/9DZeYmlSDPQTnZEgzfR4kXMIPjw>
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,  Roland:

 

I think the use cases and requirement described in your document are aligned
well with
https://datatracker.ietf.org/doc/html/draft-yu-dmsc-ai-agent-use-cases-in-6g
-01#name-network-application-collabo, we call the "collaboration between
network and application", which is one kind of uses cases types  that have
been discussed(almost finalized) in 3GPP.

 

Such use cases will be introduced briefly in the DMSC BoF(first topic, July
22, Wednesday, 9:00-11:00 AM, Vienna Time), wish you can attend it and share
your opinions.

We would also encourage you discuss the future solution in DMSC.

 

Aijun

 

From: forwardingalgorithm@ietf.org [mailto:forwardingalgorithm@ietf.org] On
Behalf Of R.Jesske=40telekom.de@dmarc.ietf.org
Sent: Tuesday, July 14, 2026 10:12 PM
To: chris@nomotic.ai; agent2agent@ietf.org
Subject: [agent2agent] Re: AI Enablement Interface for Communication
Services

 

Hi Chris,

many thanks for your mail and the references you mentioned to be looked on.
I went through the documents and they were very helpful.

 

My current understanding is that these efforts mainly focus on communication
between AI agents (or between AI agents and tools), also focusing on
discovery, identity, routing, transport, sessions, and interoperability.

 

The draft addresses a slightly different approach. The intention of the AI
Enablement Interface draft is to define a standardized interface between AI
applications/agents and communication platforms, enabling access to
communication capabilities such as voice, messaging, video,  and media
processing.

 

Typical examples are AI-assisted communication scenarios such as live
translation, call summarization, contextual assistance during a call, fraud
detection, or media enhancement. In these cases, the AI service is not
necessarily the communication endpoint itself. The AI service
enhances/processes the capabilities of an existing communication session.

 

>From that perspective, I currently see these efforts as complementary rather
than overlapping. The agent communication protocols define how agents
communicate with users, other agents, and tools, while the AI Enablement
Interface focuses on how communication services can be exposed in a
standardized way to those agents.

 

I would be interested to hear whether others see this as a distinct problem
space that would be valuable to be described and standardized.

 

Thanks again for pointing me to these documents.

 

Best Regards,

Roland

 

 

Von: Chris Hood <chris@nomotic.ai <mailto:chris@nomotic.ai> > 
Gesendet: Montag, 13. Juli 2026 17:15
An: Jesske, Roland <R.Jesske@telekom.de <mailto:R.Jesske@telekom.de> >;
agent2agent@ietf.org <mailto:agent2agent@ietf.org> 
Betreff: *****SUSPECTED SPAM***** Re: [agent2agent] AI Enablement Interface
for Communication Services

 

Roland,

 

There are three efforts worth reviewing as reference:

1) DMSC AI Agent Gateway. Focused on telco and cross-domain agent
coordination. Aijun Wang (China Telecom) and Linda Dunbar (Futurewei) are
proponents.

https://datatracker.ietf.org/group/dmsc/about/

https://datatracker.ietf.org/doc/draft-sz-dmsc-iaip/

https://datatracker.ietf.org/doc/draft-li-dmsc-mcps-agw/

2) AgentProto. Focused on agent communication protocols. 

https://datatracker.ietf.org/doc/bofreq-krishnan-agent-communication-protoco
ls/
https://github.com/jdrosen/aiproto-wg/blob/main/Charter_Merge.md

3) AGTP (Agent Transfer Protocol). Transport substrate carrying identity,
discovery, and semantic translation. Companion drafts include
AGTP-Communication and AGTP-Session for communication-specific concerns.

https://datatracker.ietf.org/doc/draft-hood-independent-agtp/
https://www.ietf.org/archive/id/draft-hood-agtp-communication-00.html

These three are each aligned with what you are searching for.

Chris

 

 

On Mon, Jul 13, 2026 at 4:13 AM <R.Jesske=40telekom.de@dmarc.ietf.org
<mailto:R.Jesske=40telekom.de@dmarc.ietf.org> > wrote:

Dear all,

as AI-based services continue to evolve rapidly, we as company looking at
solutions to enrich our multimedia communication platform with AI
capabilities such as live translation, call summaries, contextual
assistance,and other communication-related AI services.

Our idea is to define an enablement interface between communication
platforms and AI Service Providers and their LLM and Agentic service
offerings, providing guidance on the capabilities and interfaces that should
beconsidered for these kinds of use cases.

 

We have published an initial proposal describing this approach:

 
<https://www.ietf.org/archive/id/draft-jesske-ai-enablement-interface-00.txt
>
https://www.ietf.org/archive/id/draft-jesske-ai-enablement-interface-00.txt

 

We would appreciate your opinion on whether this topic fits within the scope
of this group, or whether you believe it would be better discussed in
another IETF group or context.

 

Any comments, suggestions, or feedback on the draft would also be highly
appreciated.

 

Thank you and Best Regards,

 

Roland

 

 



 

Deutsche Telekom Technik GmbH
Services & Platforms
Roland Jesske

Voice & Messaging, Squad Lead ONE VM Design
Deutsche-Telekom-Allee 9, 64295 Darmstadt
+49 6151 58-12766 (Tel.)
+49 171 8618-445 (Mobil) 

E-Mail:  <mailto:r.jesske@telekom.de> r.jesske@telekom.de

 

 <https://www.telekom.de/netz> www.telekom.de/netz




 

Die gesetzlichen Pflichtangaben finden Sie unter:
<https://www.telekom.de/pflichtangaben-dttechnik>
https://www.telekom.de/pflichtangaben-dttechnik