Re: NETCONF Notifications: Consensus Points

["Randy Presuhn" <randy_presuhn@mindspring.com>]

Hi -

> From: "Andrea Westerinen (andreaw)" <andreaw@cisco.com>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>; <netconf@ops.ietf.org>
> Sent: Saturday, November 26, 2005 9:42 PM
> Subject: RE: NETCONF Notifications: Consensus Points
>

> One usage of application-level ACKs (by the sender) is to disable
> sending notifications/event messages until specifically re-enabled.  
...

That depends on how one structures the protocol.  My initial reaction to
such a proposed usage is, in admittedly non-technical terms, "Eww, gross!"
More to the point, if the protocol only permits a single notification
"in the pipe" at a time, it would be unsuitable for use in high-delay (think NASA)
environments.   Perhaps we can live with that; I don't know whether anyone
would use netconf in high-delay environments.

This is not a necessary property of application-level acknowledgements;
an example of a protocol that does not have this property is CMIP.

Randy


--
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/>