standard notifications

[Andy Bierman <ietf@andybierman.com>]

Hi,

Although several WG members have expressed a wide spectrum
of opinions on notification content, I  think we need to keep trying
to find some consensus.

First, let's remember what we learned from SNMP.
The Trap and Inform PDUs are totally separate
(conceptually and in documentation) from the specific notification
message content defined in MIB modules.

The document we are producing first is the message processing part.
The data modeling requirements (e.g., XSD and RelaxNG templates)
need to be documented here, but we need a separate document for
standard notification content, such as "config-change", "capability-change".

We can work on both problems concurrently by starting a list
(then a document) of standard notifications.  This is a coupling
and cohesion issue -- I'm not trying to defer or avoid the
standard notification content issue.

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