Re: [CCAMP] Opsdir last call review of draft-ietf-ccamp-alarm-module-07

"Adrian Farrel" <adrian@olddog.co.uk> Mon, 18 March 2019 17:13 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6BB9131295; Mon, 18 Mar 2019 10:13:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ex6kP7ODAdlf; Mon, 18 Mar 2019 10:13:04 -0700 (PDT)
Received: from mta7.iomartmail.com (mta7.iomartmail.com [62.128.193.157]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7318C13129C; Mon, 18 Mar 2019 10:13:01 -0700 (PDT)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta7.iomartmail.com (8.14.4/8.14.4) with ESMTP id x2IHCt4D019155; Mon, 18 Mar 2019 17:12:55 GMT
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 0BFDA22044; Mon, 18 Mar 2019 17:12:55 +0000 (GMT)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs2.iomartmail.com (Postfix) with ESMTPS id E9A8E2204C; Mon, 18 Mar 2019 17:12:54 +0000 (GMT)
Received: from LAPTOPK7AS653V ([87.114.144.161]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.4/8.14.4) with ESMTP id x2IHCr6q032304 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 18 Mar 2019 17:12:54 GMT
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Joe Clarke'" <jclarke@cisco.com>, <ops-dir@ietf.org>
Cc: <draft-ietf-ccamp-alarm-module.all@ietf.org>, <ccamp@ietf.org>, <ietf@ietf.org>
References: <155292844015.26147.11067773612585181394@ietfa.amsl.com>
In-Reply-To: <155292844015.26147.11067773612585181394@ietfa.amsl.com>
Date: Mon, 18 Mar 2019 17:12:53 -0000
Organization: Old Dog Consulting
Message-ID: <018701d4ddad$d34b5fc0$79e21f40$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
Thread-Index: AQLSCYPziQq/hk/4/fvbqLx+mstGzKQXRq3Q
X-Originating-IP: 87.114.144.161
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-24498.000
X-TM-AS-Result: No--7.031-10.0-31-10
X-imss-scan-details: No--7.031-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24498.000
X-TMASE-Result: 10--7.031300-10.000000
X-TMASE-MatchedRID: QW5G6BKkLTrxIbpQ8BhdbEyM6zQm0+tqc4Aeg/bYEgRLjXXGQy6nlFeh ickTy3zi9RMMteM9sxtiJrGbqHFK11oAJDUeotnEw69AIwXJn0bRahuPwaQ1Wg2G3vz8l/IEF84 GariLK4IRYCSAjdKh370Bw+lJpKcQRcriDaoCTGIzw5Ejs3g1lhYJNGTxAkrBdE0auG3MZh/uT6 3BVP2ztoYPzHvoX0gUagXsH547IxwWRNPYiDc0BG9UcS/LykY+Pj366R4tj3VUP3YCyXOh4MR9S PQVoSYgsJ/IH+mFUAxftuJwrFEhTf306Q4zhC4D3QfwsVk0UbtuRXh7bFKB7kHEhJ7ExrOFbGg5 x/IHN3UD9O5M9vyBG9AFhw5KQNI7CStjCuOR/hg=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/2RCn6JeeYWxWq7wUZvDZWV9wtdQ>
Subject: Re: [CCAMP] Opsdir last call review of draft-ietf-ccamp-alarm-module-07
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Mar 2019 17:13:09 -0000

Hi,

I see where Joe is coming from with the term 'Alarm Shelving', but I think it is a term of art in the alarm management world (entirely random example provided by duckduckgo... https://www.exida.com/Blog/Alarm-Shelving-Relieve-the-Symptoms-of-Nuisance-Alarms).

Actually, I found the term to be quite evocative of the process.

His point about the impact on server resources is worth exploring.

And finally, yes, it seems to me that shelving and suppression of notifications seem to be approaching orthogonal. That is, suppression of notifications is not the same as suppression of alarms.

> Broadly speaking, I found the term "Alarm Shelving" to
> be confusing.  You do define this, but it is not something that many operators
> are familiar with.  I had originally thought alarm suppression was better, but
> after I read more, I see what you're trying to do with this.
>
> Additionally, some of the features like alarm-history and alarm-shelving have a
> potential operational impact with respect to local server resources, and
> perhaps that's worth calling out.
>
> Finally, I can see where it might be desirable to suppress alarm notifications
> without shelving them per se.  That is, the alarm remains in the list, but
> notifications are not sent.  That doesn't seem possible, and I'm wondering if
> it's worth considering.

Cheers,
Adrian
--
Want to buy a signed copy of a book of fairy stories for adults of all ages?
Send me an email and I'll bring one to Prague for you.
"Tales from the Wood"
"More Tales from the Wood"
"Tales from Beyond the Wood"
https://www.feedaread.com/profiles/8604/