Notification Requirements Consensus Points

[Andy Bierman <ietf@andybierman.com>]

Hi,

It is difficult to measure WG consensus.
It seems like no matter what the issue is,
there are about equal numbers of opinions on either side.

There seems to be consensus on these points:
- Top level message is <notification> (rpc-one-way is out)
- Separation of header and content-independent data is needed
- Both the manager subscription model and traditional agent-configured
  notification generator model should be supported
- The header should include some type of classification
  (e.g., event-class). 
- The ability to filter (i.e., drop) notifications at the source
  based on event class and notification data content is needed. 
  Access control is impacted by this feature.
- Named profiles (if kept) need to be fully specified in a
  standard read-create data model.
- There is no limit on the length of the notification data
  (same as for RPC data)

There does not seem to be consensus on these points:
- The specific role of notifications in the netconf protocol
  or whether a specific role is even needed
- The use of a read-only instead of a read-create data model
  for notification generation parameters
- The use of specialized RPCs instead of a standard data model
  to configure notification generation parameters
- The need for named profiles (issue is irrelevant if read-create
  data model approach is used)
- Multiple subscriptions per session are needed
- RPC operations and notifications should be mixed on the same session
- The specific list of event classes, or
  whether this document or IANA maintains the list, or
  whether we even need a list at all (i.e., just a string match).
- The need for a modify-subscription feature
  (Note that this is implicitly supported by edit-config if a
  read-create data model is used)
- The use of an endless-RPC model (which is only relevant if
  the WG decides mixed-mode sessions are not required)
- The specific standard notifications (if any) that an agent
  must support



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