[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

NETCONF Notifications

Hi,

Let's start a thread to see if we agree on the problem we're trying to solve.
First, let's remember where we left off.

Here's what I remember:

 - we wanted to simply adopt RFC 3195 for notifications but decided
   that this was a problem because it was BEEP-only
 - our solutions for mapping multiple channels to SSH and SOAP mappings
   was not approved by the WG and dropped. Notifications over SOAP/HTTP
   were particularly clumsy (IMO).
 - the lack of any notification filtering (i.e., default is get-all)
   was a concern, but so was simply providing a proprietary hook instead
   of a standard solution for notification filtering.

What did I forget (or remember wrong)?

IMO, it's important that the NM application not have to use
notifications differently (via capabilities) depending on
the NETCONF application mapping in use for a particular session.
I could live with a BEEP-only notification solution too, to solve
this problem in minutes instead of weeks.

I want to know what the WG thinks...

Andy



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