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

stefan vallin <stefan@wallan.se> Tue, 19 March 2019 15:30 UTC

Return-Path: <stefan@wallan.se>
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 70C91127978 for <ccamp@ietfa.amsl.com>; Tue, 19 Mar 2019 08:30:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=wallan-se.20150623.gappssmtp.com
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 j0bZMfJ2bpD7 for <ccamp@ietfa.amsl.com>; Tue, 19 Mar 2019 08:30:26 -0700 (PDT)
Received: from mail-lj1-x22e.google.com (mail-lj1-x22e.google.com [IPv6:2a00:1450:4864:20::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8213D13140D for <ccamp@ietf.org>; Tue, 19 Mar 2019 08:30:24 -0700 (PDT)
Received: by mail-lj1-x22e.google.com with SMTP id p20so4888334lji.10 for <ccamp@ietf.org>; Tue, 19 Mar 2019 08:30:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wallan-se.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=uJIJjipvxRfQhw4Ox9WvNr+obybAfmK3e90QVc8fn/k=; b=I+8uIzRQBGaIpsTzBUdjEkwVewGepvtIbXLDn0z9w7SArashfcZYieaeZ0w3vDISHH I9PBbkYdLwUdbGgmZcJv8W6DtjrXYyYhOBuIoydOy4WNywmbiPahs6jPnrGjRxXUq+Id 8y4Ogio2QbMgEoJW2wKJKoajnbTR3scM9Rp+ahNJ5KUOXXrLPQetAvTgdh2oNNyzaVr/ 7aM4HM2nh1BEb8UMldED44hRtpQDFQDPeEABLCotrtGeohq8jdOAovIflVRCDtHanGWn uICNiHx+3tUbdx+724Po6P5f0QOpjAvNNvUfY6SQ4N8s2KNkSS9oD2SK6LLtvTRIR9O8 wBAQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=uJIJjipvxRfQhw4Ox9WvNr+obybAfmK3e90QVc8fn/k=; b=Dqqp/4XFkp8CbC4voVYZ2T7laDXKI6TfQM62+zBOlYKHysjs5gb49B1fW/STd+8zYI fB8xJiUy2U2gvrDeXqDZnHDXIMToPSgmnNpVFt4TifKwhXSVlEfoZxwsBA5URT0w456K OPAABIQPu2TvOxtr/r+cb/fmQur0xYNwwx0uLLsaU3mF1zh2U9K/FsQRk1qdiorSwqEV JpsSKe3QRNDR9gxM0Jnj4CxY4+ahQ2wIF1Vi9+/2jINPKfc0BpRcdpre3y/KHCSHop4v dAilLcEWcGBpnM7HWXoUvS5NPYIIIHHss13AxNmBsff17JlD11BYzokmI6u7SbnxUG/A Ju+g==
X-Gm-Message-State: APjAAAX1pinnRwmWnJy5xJgPN8qd8jfERhY8Ixo1KRZ/9zuiu2+CdsQK apOSq9Sqn62e2gzjmwodhXBW8g==
X-Google-Smtp-Source: APXvYqwobH0zuid5EMTwJLoNceeBHe4qDSTPV44VxfKra7VQhAcu01nLk6wkbk7+L3jgQhUPwuHmSQ==
X-Received: by 2002:a2e:3e11:: with SMTP id l17mr14247726lja.172.1553009422645; Tue, 19 Mar 2019 08:30:22 -0700 (PDT)
Received: from [192.168.8.34] ([195.234.15.130]) by smtp.gmail.com with ESMTPSA id p10sm2774622lfk.35.2019.03.19.08.30.21 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Mar 2019 08:30:22 -0700 (PDT)
From: stefan vallin <stefan@wallan.se>
Message-Id: <425F5BB9-DAF8-401C-A048-5BC00BD9EC23@wallan.se>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0CFCB043-B088-4F0D-B50C-5ECA12818178"
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Date: Tue, 19 Mar 2019 16:30:21 +0100
In-Reply-To: <0b559129-fc1f-c4b0-eaf6-4a03780e93f1@cisco.com>
Cc: ops-dir@ietf.org, draft-ietf-ccamp-alarm-module.all@ietf.org, ccamp@ietf.org, ietf@ietf.org
To: Joe Clarke <jclarke@cisco.com>
References: <155292844015.26147.11067773612585181394@ietfa.amsl.com> <22EBF1ED-7CE4-4A4F-A105-C76D17D2F2DA@wallan.se> <15ac10fa-db49-df31-c532-03a3692a2ca2@cisco.com> <556B8CFB-E3E0-44AB-B82B-9E60CE4C0FF5@wallan.se> <0b559129-fc1f-c4b0-eaf6-4a03780e93f1@cisco.com>
X-Mailer: Apple Mail (2.3445.100.39)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/mYG10BJ_GcnYtPSNkBIqHBoaQtk>
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: Tue, 19 Mar 2019 15:30:28 -0000

Hi!

> On 19 Mar 2019, at 16:23, Joe Clarke <jclarke@cisco.com> wrote:
> 
> Do you
> envision a non-shelved alarm to periodically generate notifications
> while active, or is it one-and-done?
Oh yes, see
3.5.1.  Resource Alarm Life-Cycle

   From a resource perspective, an alarm can for example have the
   following life-cycle: raise, change severity, change severity, clear,
   being raised again etc.  All of these status changes can have 
   different alarm texts generated by the instrumentation


That is the purpose of having the resource and alarm-type as key
As long as you do not purge (delete) the alarm it can change:
* severity
* alarm-text
* is-cleared

Each of the generating a notification.

If that was your question….
/s