Hi, all

I would like to say that this is very interesting and timely work. The draft 
provides a useful starting point for discussing how AI can be introduced into 
autonomic networking, especially when intelligence is expected to run in a 
decentralized way inside the network.


One question I would like to ask is how ANIMA plans to position this work going 
forward. For example, should AI4AN mainly be considered as an architectural 
discussion inside ANIMA, or should it also become a bridge between ANIMA, DAWN, 
and other agent communication efforts?


From our perspective, we also think that some work is needed at the 
infrastructure level, not only at the AI application level. For AI-based ASAs 
or agentic network functions to work in real networks.


So I would be very interested in seeing further ANIMA discussion on whether we 
need a clearer AI-ASA or AI4AN infrastructure framework, possibly aligned with 
DAWN but grounded in existing ANIMA concepts.


Regards,
Mengyao
 
------------------ Original ------------------
From: &nbsp;"Brian E Carpenter"<[email protected]&gt;;
Date: &nbsp;Mon, Jul 6, 2026 09:50 AM
To: &nbsp;"draft-eckert-anima-ai4an"<[email protected]&gt;; 
"anima"<[email protected]&gt;; 

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

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

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).

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.

Nit: s/autonomous/autonomic/ globally

(We chose "autonomic" at the beginning of ANIMA, by analogy with the autonomic 
nervous system, so I think we need to be consistent.)

Regards/Ngā mihi
&nbsp; &nbsp; Brian

On 06-Jul-26 11:28, [email protected] wrote:
&gt; Internet-Draft draft-eckert-anima-ai4an-00.txt is now available.
&gt; 
&gt;&nbsp;&nbsp; &nbsp; Title: &nbsp; AI for Autonomous Networking
&gt;&nbsp;&nbsp; &nbsp; Authors: Toerless Eckert
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; 
Alexander Clemm
&gt;&nbsp;&nbsp; &nbsp; Name:&nbsp; &nbsp; draft-eckert-anima-ai4an-00.txt
&gt;&nbsp;&nbsp; &nbsp; Pages: &nbsp; 17
&gt;&nbsp;&nbsp; &nbsp; Dates: &nbsp; 2026-07-05
&gt; 
&gt; Abstract:
&gt; 
&gt;&nbsp;&nbsp; &nbsp; This document builds on the architectural foundation of 
the IETF
&gt;&nbsp;&nbsp; &nbsp; ANIMA "Autonomous Network Infrastructure" to propose an 
architecture
&gt;&nbsp;&nbsp; &nbsp; for in-network intelligence in support of network 
automation.
&gt; 
&gt;&nbsp;&nbsp; &nbsp; The key aspect of this architecture is the use of AI 
programmed and
&gt;&nbsp;&nbsp; &nbsp; validated software running decentralized on the network.
&gt; 
&gt; The IETF datatracker status page for this Internet-Draft is:
&gt; https://datatracker.ietf.org/doc/draft-eckert-anima-ai4an/
&gt; 
&gt; There is also an HTMLized version available at:
&gt; https://datatracker.ietf.org/doc/html/draft-eckert-anima-ai4an-00
&gt; 
&gt; Internet-Drafts are also available by rsync at:
&gt; rsync.ietf.org::internet-drafts
&gt; 
&gt; 
&gt; _______________________________________________
&gt; I-D-Announce 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