Hi all,

"AI for ANIMA" is a topic well worth in-depth discussion.

To differentiate from the general concept of "Agent," we have proposed the term 
"AI-ASA", which might better align with the research scope of the anima WG. We 
are also actively exploring how the introduction of AI might impact existing 
protocols and mechanisms such as GRASP and ACP.

I also agree with the view that AI is more of an application-level issue and 
may not need to be explicitly defined at the protocol level. However, it is 
undeniable that the introduction of AI or Agent brings many uncontrollable 
factors to current systems, especially the uncertainties related to 
decision-making that everyone has mentioned.

In IETF community, current Agents typically involve a "human in the loop." 
Perhaps within the ANIMA ACP framework, we could try to have the ACP replace 
the human role to some extent, becoming a trustworthy decision-making 
participant (or "trusted execution entity").

Regards,
Mengyao

 
 
------------------ Original ------------------
From: &nbsp;"Bless, Roland (TM)"<[email protected]&gt;;
Date: &nbsp;Thu, Jul 9, 2026 04:11 PM
To: &nbsp;"Artur Hecker"<[email protected]&gt;; 
"anima"<[email protected]&gt;; 

Subject: &nbsp;[Anima] Re: I-D Action: draft-eckert-anima-ai4an-00.txt

&nbsp;
  
【本邮件为外部邮件,请注意核实发件人身份,并谨慎处理邮件内容中的链接及附件】
Hi Artur,

On 08.07.26 at 15:22 Artur Hecker wrote:
&gt; - if we are serious about ACP/GRASP/BRSKI as foundation, we would need to 
show that, even in spite of potential misjudgments by LLM or programming errors 
done by it, ACP would always remain "the last Mohican": ACP should be the last 
to fail, i.e. in presence of a potentially unverified programs produced at will 
by the LLM/foundation model, the ACP must act like an implementation of a 
protected mode in an OS, like an OS kernel if you will, preserving the 
possibility to repair/remove/terminate misbehaving programs. Such that we can 
have a bunch of simple yet reliable tools on top of ACP to clean away any 
nonsense introduced by LLM/foundation models, and, also very important, to be 
able to isolate the effects of such programs by separating concerns and 
enforcing "control app manifests" in a distributed system.

+1

That is quite along the lines what I wrote up here:
https://labs.ripe.net/author/roland-bless/how-to-never-lose-control-over-your-network/

However, ACP should actually not fail unless the underlay connectivity 
isn't available anymore...

Regards,
&nbsp; Roland

&gt; -----Original Message-----
&gt; From: Brian E Carpenter <[email protected]&gt;
&gt; Sent: Monday, July 6, 2026 3:50 AM
&gt; To: [email protected]; Anima WG <[email protected]&gt;
&gt; Subject: [Anima] Re: I-D Action: draft-eckert-anima-ai4an-00.txt
&gt; 
&gt; Hi,
&gt; 
&gt; I'm all for what you are saying in this draft, but I think you also have 
to address it to the DAWN people and everybody working on agentic 
communications. Look at draft-he-dawn-ipv6-agent-aware-framework, for example; 
it has very little to do with IPv6. Maybe you should ask for a slot at the DAWN 
BOF? (DAWN = Discovery of Agents, Workloads, and Named Entities.) At least 
point out that ANIMA/GRASP has been working on discovery of agents since the 
dawn of time (pun intended).
&gt; 
&gt; Also, the trust boundary issue we just discussed re 
draft-soulard-anima-grasp-router-problem-statement is going to be relevant. I 
see a clear clash between the type of trust boundary that BRSKI provides and 
how the agentic community is looking at trust.
&gt; 
&gt; Nit: s/autonomous/autonomic/ globally
&gt; 
&gt; (We chose "autonomic" at the beginning of ANIMA, by analogy with the 
autonomic nervous system, so I think we need to be consistent.)
&gt; 
&gt; Regards/Ngā mihi
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Brian
&gt; 
&gt; On 06-Jul-26 11:28, [email protected] wrote:
&gt;&gt; Internet-Draft draft-eckert-anima-ai4an-00.txt is now available.
&gt;&gt;
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Title:&nbsp;&nbsp; AI for Autonomous 
Networking
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Authors: Toerless Eckert
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 Alexander Clemm
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Name:&nbsp;&nbsp;&nbsp; 
draft-eckert-anima-ai4an-00.txt
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Pages:&nbsp;&nbsp; 17
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dates:&nbsp;&nbsp; 2026-07-05
&gt;&gt;
&gt;&gt; Abstract:
&gt;&gt;
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This document builds on the 
architectural foundation of the IETF
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ANIMA "Autonomous Network 
Infrastructure" to propose an architecture
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for in-network intelligence in support 
of network automation.
&gt;&gt;
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The key aspect of this architecture is 
the use of AI programmed and
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; validated software running decentralized 
on the network.
&gt;&gt;
&gt;&gt; The IETF datatracker status page for this Internet-Draft is:
&gt;&gt; https://datatracker.ietf.org/doc/draft-eckert-anima-ai4an/
&gt;&gt;
&gt;&gt; There is also an HTMLized version available at:
&gt;&gt; https://datatracker.ietf.org/doc/html/draft-eckert-anima-ai4an-00
&gt;&gt;
&gt;&gt; Internet-Drafts are also available by rsync at:
&gt;&gt; rsync.ietf.org::internet-drafts
&gt;&gt;
&gt;&gt;
&gt;&gt; _______________________________________________
&gt;&gt; I-D-Announce mailing list -- [email protected] To unsubscribe send
&gt;&gt; an email to [email protected]
&gt; _______________________________________________
&gt; Anima mailing list -- [email protected]
&gt; To unsubscribe send an email to [email protected]
&gt; _______________________________________________
&gt; Anima mailing list -- [email protected]
&gt; To unsubscribe send an email to [email protected]

_______________________________________________
Anima mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
Anima mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to