Re: mteTriggerDeltaDiscontinuityIDWildcard question
"mark kaplun" <[email protected]> Mon, 31 Oct 2005 17:34:31 +0200
| Newsgroups | gmane.ietf.disman |
|---|---|
| Message-ID | <[email protected]> |
----- Original Message ----- From: "Randy Presuhn" <[email protected]> To: "Disman" <[email protected]> Sent: Saturday, October 29, 2005 9:02 PM Subject: Re: [Disman] mteTriggerDeltaDiscontinuityIDWildcard question > Hi - > >> From: "mark kaplun" <[email protected]> >> To: <[email protected]> >> Sent: Saturday, October 29, 2005 10:42 AM >> Subject: [Disman] mteTriggerDeltaDiscontinuityIDWildcard question >> >> Hi, >> >> By the description of the object it is possible to conclude that there is >> no >> difference between this object and mteTriggerValueIDWildcard, so why does >> it >> exist? am I missing something? > ... > > Some discontinuity indicators, e.g. sysUpTime, are scalars. Others are > in tables. Consequently, whether a given object can be monitored > using wildcarding cannot be used to infer whether wildcarding would be > appropriate for its discontinuity indicator. > > Randy Makes sense, but the description says "Note that the value of this object will be the same as that of the corresponding instance of mteTriggerValueIDWildcard when the corresponding mteTriggerSampleType is 'deltaValue'." My understanding is that mteTriggerDeltaDiscontinuityIDWildcard MUST be false when mteTriggerValueIDWildcard is false, but can take ANY value when mteTriggerValueIDWildcard is true. This is IMHO in contradiction with the use of the word "same" in the description. Mark -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.361 / Virus Database: 267.12.6/151 - Release Date: 28.10.2005