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

RE: Draft EOS minutes

Title: Draft EOS minutes
Hi Tom,
I'm a bit confused about your suggestion. Maybe you can reword so I can understand your point.
PDUs don't really deliver notifications. Messages deliver PDUs. PDUs may contain notifications.
Are you asking that each message be identified? That information is already available by checking the source address in the UDP packet. The message header includes a request ID, so duplicates can be detected. Snmpv3 supplements this with the contextEngineID to identify the engine that sourced the PDU.
Am I misunderstanding your question?
-----Original Message-----
From: Tom Petch [mailto:nwnetworks@dial.pipex.com]
Sent: Thursday, September 12, 2002 3:24 PM
To: Glenn Waters; eos@ops.ietf.org
Subject: Re: Draft EOS minutes

Following the work in Disman has highlighted a number of difficulties with the basic technology of SNMP but as has been pointed out to me, most of those are Mib-related,not SNMP-the-protocol-related.
But one that I see as SNMP (sensu stricto) and hence a possibility for this group, is the difficulty of identifying a PDU (as opposed to identifying a MIB object at which SNMP is very good).  Sometimes it matters to know where information came from eg which PDU delivered the Notification so as to track/correlate/eliminate duplicates etc.
As defined, SNMP does not seem to have any reliable way of doing so; any ideas?