RE: notification charter proposal

["Glenn Waters" <gww@nortel.com>]

> I think the question to asked is whether a notification message needs
> an application layer acknowledgement and if so what the semantics are
> or whether we can get away without such an application layer
> acknowledgement. Some options are:
> 
> a) The notification sender sends a notification and hopes that it
>    will be understood by the receiver.

Unless we can identify value in (b) below then I would pick this method.

> b) The notification sender sends a notification and gets a
confirmation
>    that the notification was understood to the extend that it could be
>    handed over to an entity dealing with notifications. (This is what
>    SNMP notifications actually do.)

I don't think that there is enough value in sending a response in this
case since there is little recourse the sender can take to correct the
issue. There is the possibility the sender could reduce the message size
but that can be handled in other ways (such as the receiver
reconfiguring the max size the sender should send). I can't think of
what else a sender would possibly do with a response. Maybe it would
help to identify those items to help decide if a response would be
useful.

> 
> c) The notification sender sends a notification and gets a
confirmation
>    that an entity dealing with notifications actually understood the
>    semantics associated with the notification.

Same as above only worse.

> > Once we understand and agree on the semantics we want to have (at
the
> moment a) seems to be on the table), we know whether we need a
> response or if we can get away with a one-way message (in which case I
> agree that the so called RPC layer should be extended to support
> this).
> 
> /js
> 
> --
> Juergen Schoenwaelder		    International University Bremen
> <http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725
Bremen,
> Germany
> 
> --
> to unsubscribe send a message to netconf-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://ops.ietf.org/lists/netconf/>


--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>