Re: [Technical Errata Reported] RFC2981 (3798)

Randy Presuhn <[email protected]> Wed, 13 Nov 2013 19:59:49 -0800 (GMT-08:00)
Newsgroups gmane.ietf.disman
Message-ID <30428339.1384401589933.JavaMail.root@elwamui-little.atl.sa.earthlink.net>
Hi -

I think the existing text is correct, and that the
proposed erratum should be rejected.

The existing text effectively says that if neither the
boolean(1) bit nor the threshold(2) bit of mteTriggerTest
is set, then the value assigned to mteTriggerSampleType
doesn't matter.  This is indeed how it is intended to
function.

Of course, I invite others to examine the proposed erratum.

Randy

-----Original Message-----
>From: RFC Errata System <[email protected]>
>Sent: Nov 13, 2013 2:09 AM
>To: [email protected], [email protected], [email protected], [email protected]
>Cc: [email protected], [email protected]
>Subject: [Technical Errata Reported] RFC2981 (3798)
>
>The following errata report has been submitted for RFC2981,
>"Event MIB".
>
>--------------------------------------
>You may review the report below and at:
>http://www.rfc-editor.org/errata_search.php?rfc=2981&eid=3798
>
>--------------------------------------
>Type: Technical
>Reported by: shuaixiaojuan <[email protected]>
>
>Section: 7
>
>Original Text
>-------------
>mteTriggerSampleType's description:
>If only 'existence' is set in mteTriggerTest this object has
>no meaning."
>
>
>Corrected Text
>--------------
>If no 'boolean' is set in mteTriggerTest this object has
>no meaning."
>
>
>Notes
>-----
>mteTriggerThresholdDeltaRising was added to mteTriggerThresholdTable from the version draft-ietf-disman-event-mib-09.txt and mteTriggerThresholdTable can both deal 'absoluteValue' and 'deltaValue', so mteTriggerSampleType has mean for 'boolean' only. (mteTriggerSampleType has no changed from draft-ietf-disman-event-mib-06.txt)
>
> was added to
>
>Instructions:
>-------------
>This errata is currently posted as "Reported". If necessary, please
>use "Reply All" to discuss whether it should be verified or
>rejected. When a decision is reached, the verifying party (IESG)
>can log in to change the status and edit the report, if necessary. 
>
>--------------------------------------
>RFC2981 (draft-ietf-disman-event-mib-10)
>--------------------------------------
>Title               : Event MIB
>Publication Date    : October 2000
>Author(s)           : R. Kavasseri, Ed.
>Category            : PROPOSED STANDARD
>Source              : Distributed Management
>Area                : Operations and Management
>Stream              : IETF
>Verifying Party     : IESG