Subject: RE: draft-ietf-disman-event-mib-v2-01.txt

From: "Chapman, Ken" <[email-masked]>
Date: Fri, 8 Nov 2002 09:50:30 -0500

Hi Ram,
Thanks.
Those were our thoughts as well.
	Ken

p.s.: What is Bob Stewarts opinion?

++++++++++++++++++++++++++++++++++++++++++++++++++ 
Ken Chapman              Juniper Networks, Inc. 
                         M/S 3136 
Tel: +1 978 589 0288     10 Technology Park Drive 
Fax: +1 978 589 0800     Westford, MA  01886-3410
[email-masked] <mailto:[email-masked]> 
++++++++++++++++++++++++++++++++++++++++++++++++++ 

-----Original Message-----
From: Ramanathan Kavasseri [mailto:[email-masked]]
Sent: Thursday, November 07, 2002 6:39 PM
To: Chapman, Ken
Cc: [email-masked]'
Subject: Re: draft-ietf-disman-event-mib-v2-01.txt

"Chapman, Ken" wrote:
> 
> Hi,
> We are trying to implement the DISMAN-EVENT-MIB and have come across an
> ambiguous situation (at least I can't find the answer in the ID).
> We are unable to find any text that says a triger for just 'existence' has
a
> SYNTAX restriction.
> If an owner specified an 'existence' triger on an object that has a syntax
> that does not evaluate to a 32 bit interger, what do we send in the for
> mteHotValue in the mteTriggerFired notification?
> Are we missing something?
> Thanks.
>         Ken

Ken,

looking over the draft, I have NO CLUE what the value
of mteHotValue should be when mteTriggerTest is fired for
instance creation or deletion. Further, if the value
of an object with syntax OCTET STRING changes, how can you
represent that in mteHotValue?

Should we send mteTriggerTest notifications
for thresholds and booleans only? This would mean adding
an mteTriggerExistenceTest notification - and we'll still
need to replace mteHotValue.

Ram