Hi,
I think it's a good idea to work out how "intent" can be objectified. I think
it would be better to do it in JSON, however, or CDDL if your target protocol is GRASP.
I appreciate the idea of "Intent Scope" but I think it introduces hard problems
- how do domains aquire a name, how is the border identified, can domains overlap, and
how do hosts know reliably which domains they are in? (These questions are not answered
by RFC 8799, but it may explain why the problem is hard.)
Regards/Ngā mihi
Brian
On 03-Mar-26 01:15, [email protected] wrote:
Internet-Draft draft-zhu-anima-service-intent-00.txt is now available.
Title: Definition of Service Intent in Autonomic Networks
Authors: Longwei Zhu
Bizhu Wang
Sheng Jiang
Name: draft-zhu-anima-service-intent-00.txt
Pages: 10
Dates: 2026-03-02
Abstract:
While ANIMA Intent enables goal-oriented control within an Autonomic
Domain, emerging services (e.g., AI inference) require a common,
interoperable representation for expressing service-level objectives
and constraints that span network, compute, and storage resources,
rather than connection-centric descriptions. This document defines
Service Intent for Autonomic Networks by specifying a structured
semantic model and a concise format with identification, scope,
versioning, and lifecycle semantics.
The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-zhu-anima-service-intent/
There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-zhu-anima-service-intent-00
Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts
_______________________________________________
I-D-Announce 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]
