Hi Dear all, To response to the Chairs' calling, I'd like to firstly mention an existing work, draft-carpenter-anima-ani-objectives, which belongs to the first category as Sheng defined below: > Leveraging the Current ANI (GRASP, ACP & BRISK)
It is very specific technical details (just like "option names" in other protocols) related to all ANI components (BRSKI, ACP and GRASP), but necessary for interoperability. We used to have some discussion about whether to define these objectives in each ANI component. But there is two problems as I see: 1. This draft defines an additional value for GRASP message syntax to indicate transport-protocol. So far it is actually used for BRSKI to indicate IP-in-IP encapsulation. However, from definition perspective, this value is generic than BRSKI-specific, so I'm not very sure it is proper to defined it in BRSKI. 2. Technically, it is ok to define each GRASP-objective in each ANI document, but would it be a bit scattered? In any case, I think the ANI objective content should reach consensus and be published as soon as possible. Then, the problem again: shall we make it as a standalone draft, or incorporate them into each ANI draft? Best regards, Bing From: Anima [mailto:[email protected]] On Behalf Of Sheng Jiang Sent: Wednesday, September 20, 2017 5:39 PM To: Anima WG <[email protected]> Cc: [email protected] Subject: [Anima] Calling new works and discussion Hi, all ANIMA, As we are sending more documents to IESG for publication, the group has delivered most of our original milestones without boiling the ocean. We are now in a little bit more confidence to explore slightly wider area of autonomic networking. We are now calling new works/work proposals. We would like to start to discuss new potential works and whether they are doable, whether they are worth to solve by ANIMA WG, whether ANIMA is the right WG for it, etc. The below is three rough categories that may be interested by the group. - Leveraging the Current ANI (GRASP, ACP & BRISK) - ANI extension & other reusable components for AN - Autonomic Service Agents over ANI and other reusable components Thanks and regards, Sheng
_______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
