Subject: Re: [Anima] I-D Action: draft-xiao-anima-event-service-00.txt

From: Brian E Carpenter <[email-masked]>
Date: Mon, 30 Oct 2017 11:45:20 +1300

Hi,

I've read this draft with interest. Let's assume for a moment that we agree
on the need for such a service, and that we agree that it would be a generic
service provided as part of the ANI. Then I would like to discuss the
concluding remarks:

>    This may involve slight extensions of the current ANI by integrating
>    the ES module. For example, the API set of GRASP [I-D.ietf-anima-
>    grasp-api] will need to be extended with new APIs to access ES
>    module. 

While I agree that an API would be needed, I'm not sure that it
should be an extension to the GRASP API. That's more a software
engineering question than a protocol design question, of course,
but I don't see a reason to mix the two APIs.

(We perhaps have a general question of how to support ASA-to-ASA
communication within a node, although "just use GRASP" might
be the answer.)

> GRASP itself will also need to be extended for ES module
>    signaling.

I would like to know more. What specific features do you need?
GRASP already provides unsolicited notifications (M_FLOOD)
and asynchronous notifications (M_REQ_SYN or M_REQ_NEG, which
both require the other end to be in a listening state for
incoming requests). What else do you need? Remember that a GRASP
objective can carry *any* data structure you want, up to the
maximum allowed size. So you can define any kind of content
for the notification messages without extending GRASP.

Regards
   Brian

On 28/10/2017 19:44, [email-masked] wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
>         Title           : Event Service in Autonomic Networking
>         Authors         : Xun Xiao
>                           Artur Hecker
>                           Zoran Despotovic
> 	Filename        : draft-xiao-anima-event-service-00.txt
> 	Pages           : 10
> 	Date            : 2017-10-27
> 
> Abstract:
>    Event service is an asynchronous communication model between
>    interacting parties, e.g. autonomic functions (AFs), instead of a
>    tightly coupled point-to-point (P2P) synchronous communication model.
>    Event service enables autonomic nodes in ANI to publish data
>    information, which will be made network distributable autonomously,
>    and subscribers who register interests to specific events will be
>    notified if the information is available. This draft describes how to
>    support event service (ES) for autonomic networking.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-xiao-anima-event-service/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-xiao-anima-event-service-00
> https://datatracker.ietf.org/doc/html/draft-xiao-anima-event-service-00
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>