[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: predictable content
HI,
I think you accidentialy used an incorrect characterization
of SNMPv3's the (context-engine-id, context-name) pair.
It is not the identity of the "sender". It is the
source of the notification. An observer can send
a NOTIFICATION reporting that an event occured on
another system, and when so would use the that
system's identifier as the source.
A proxy also uses the identification of the source
system and not it's identity.
Regards,
/david t. perkins
On Thu, 30 Mar 2006, Juergen Schoenwaelder wrote:
> On Thu, Mar 30, 2006 at 11:58:57AM +0200, Balazs Lengyel wrote:
>
> > 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.)
>
> SNMPv1 indeed did this but the idea was weakened with the introduction
> of SNMPv2 PDU formats some 12+ years ago since only the notification
> name (its OID) and the sysUpTime timestamp is required to be shipped
> in the varbind list (and note that sysUpTime is the time since the
> network management portion of the system was last re-initialized).
> The identification of the sender got reintroduced in SNMPv3 by means
> of the (context-engine-id, context-name) pair, in particular to handle
> proxy situations (but I hope NETCONF avoids dealing with proxies).
>
> > 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.
>
> You are proposing to hard-wire a portion of a data model into the
> protocol. So far, NETCONF tried to avoid this and the question would
> be where to stop.
>
> /js
>
> --
> Juergen Schoenwaelder International University Bremen
> <http://www.eecs.iu-bremen.de/> P.O. Box 750 561, 28725 Bremen, Germany
>
> --
> 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/>
>
--
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/>