Re: [Disman] 答复: [Technical Errata Reported] RFC2981 (3798)

Randy Presuhn <randy_presuhn@mindspring.com> Thu, 14 November 2013 16:56 UTC

DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=dTxGNHJfbYXPOJ+Gk35IEc6P7gmCYNurDGhBEdW10kCqQqTDwfLDzSZG6ZMbJ7V/; h=Message-ID:Date:From:Reply-To:To:Subject:Cc:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-ELNK-Trace:X-Originating-IP;
Message-ID: <20780676.1384448170260.JavaMail.root@elwamui-cypress.atl.sa.earthlink.net>
Date: Thu, 14 Nov 2013 08:56:09 -0800
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: 帅帅 <8500302@qq.com>, RFC Errata System <rfc-editor@rfc-editor.org>, "ramk@cisco.com" <ramk@cisco.com>, "bclaise@cisco.com" <bclaise@cisco.com>, "joelja@bogus.com" <joelja@bogus.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: "disman@ietf.org" <disman@ietf.org>, "rfc-editor@rfc-editor.org" <rfc-editor@rfc-editor.org>
Subject: Re: [Disman] 答复: [Technical Errata Reported] RFC2981 (3798)
Precedence: list
Reply-To: Randy Presuhn <randy_presuhn@mindspring.com>

Hi -

>From: 帅帅 <8500302@qq.com>
>Sent: Nov 14, 2013 1:55 AM
>To: Randy Presuhn <randy_presuhn@mindspring.com>, RFC Errata System <rfc-editor@rfc-editor.org>, "ramk@cisco.com" <ramk@cisco.com>, "bclaise@cisco.com" <bclaise@cisco.com>, "joelja@bogus.com" <joelja@bogus.com>
>Cc: "rfc-editor@rfc-editor.org" <rfc-editor@rfc-editor.org>, "disman@ietf.org" <disman@ietf.org>
>Subject:  答复: [Technical Errata Reported] RFC2981 (3798)
>
>Hi Randy:
>    Special delta parameters such as mteTriggerThresholdDeltaRising
> was added to mteTriggerThresholdTable, but no delta parameters for
> mteTriggerbooleanTable, why the difference?

See the DESCRIPTION of mteTriggerTest  for an outline of the
difference between boolean and threshold trigger types.
Perhaps the chart on page 5 will be helpful.  There are
several different kinds of triggers.  In addition to the
object monitored, some additional pieces of information
are needed.  Exactly *which* additional pieces of information
depends upon the trigger type.

The existing text mentioned in the proposed erratum merely
says that sample type is irrelevant for an existence trigger.
(I think it's obvious why that is true.)  It doesn't mention
the behaviour in the degenerate case where *none* of the bits
of mteTriggerTest happens to be set, but I think the Postel
Principle dictates that sample type would be irrelevant in that
case as well.

>     I think the auther's intention is to TEST both absoluteValue
> and deltaValue for threshold.

The SYNTAX of mteTriggerSampleType is INTEGER, so only one of
those values is possible for a given instance at any point in
time, so I think that interpretation is incorrect.

> Therefore mteTriggerSampleType is of no meaning for threshold,
> otherwise, when mteTriggerSampleType is set to deltaValue,
> mteTriggerThresholdRising and mteTriggerThresholdDeltaRising
> which one to use?

It's important to understand the explanatory text in the DESCRIPTION of 
mteTriggerThresholdStartup, but I think the key point is to
understand mteTriggerSampleType.  If it's absoluteValue(1),
(note well that it does NOT mean "absolute value" in the
mathematical sense!!!) it simply means that the raw value that
has been sampled is the input to the trigger evaluation funtion.
If it's deltaValue(2) then it means that we're talking about
the first derivative.

I still think the erratum should be rejected, but welcome others'
thoughts on the matter.

Randy

Re: [Disman] 答复: [Technical Errata Reported] RFC2… Randy Presuhn