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

predictable content

For me this also means that the content of the notifications should be defined as well. A full definition is not possible but at least a set of basic data (notification type, category?, sender, timestamp, human readable info string ?, alarmID etc.) could be defined by the protocol. (Like sender, notification type and timestamp is included in SNMP as I remember.)
So even if the NMS doesn't know the specific data model he can do some useful things with it e.g. present it, search for specific string values etc. 

Balazs

Juergen Schoenwaelder wrote:

On Wed, Mar 29, 2006 at 12:17:05PM -0500, Sharon Chisholm wrote:

Predictable is that the consumer of the message based only on the
protocol definition and a definition of the data model associated with
the notification (XML Schema, for example) are able to predict what
information will be in the notification and how it will be formatted.


I assume that any reasonable data modeling language should have the
property that notifications defined with the data modeling language
are predictable.

I fail to see a requirement here for the development of a NETCONF
_protocol_ extension. If I am wrong, can you please help me phrase
this as a protocol requirement?



--
Balazs Lengyel                       Ericsson Hungary Ltd.
TSP System Manager
ECN: 831 7320                        Fax: +36 1 4377792
Tel: +36-1-437-7320     email: Balazs.Lengyel@ericsson.com

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