Re: [CCAMP] Question on alarm-notification draft-ietf-ccamp-alarm-module-07.txt

Martin Bjorklund <mbj@tail-f.com> Mon, 04 March 2019 08:15 UTC

Return-Path: <mbj@tail-f.com>
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 BA9D7129A85 for <ccamp@ietfa.amsl.com>; Mon, 4 Mar 2019 00:15:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 JU_-Ydh37M4H for <ccamp@ietfa.amsl.com>; Mon, 4 Mar 2019 00:15:38 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 093A41292F1 for <ccamp@ietf.org>; Mon, 4 Mar 2019 00:15:37 -0800 (PST)
Received: from localhost (unknown [173.38.220.61]) by mail.tail-f.com (Postfix) with ESMTPSA id 6B0EC1AE0118; Mon, 4 Mar 2019 09:15:36 +0100 (CET)
Date: Mon, 04 Mar 2019 09:15:37 +0100
Message-Id: <20190304.091537.1434859750027847472.mbj@tail-f.com>
To: yves.beauville@nokia.com
Cc: ccamp@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <50762c99-ff06-e142-ae82-b8fccd75016a@nokia.com>
References: <50762c99-ff06-e142-ae82-b8fccd75016a@nokia.com>
X-Mailer: Mew version 6.7 on Emacs 25.2 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/bbRH3hDDxC5FvioCDvJRDapadDI>
Subject: Re: [CCAMP] Question on alarm-notification draft-ietf-ccamp-alarm-module-07.txt
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, 04 Mar 2019 08:15:40 -0000

Hi,

"Beauville, Yves (Nokia - BE/Antwerp)" <yves.beauville@nokia.com> wrote:
> Hello,
> 
> In the proposed YANG module, an alarm-notification conveys a single
> alarm state change.
> 
> There are scenarios where server may want to send a possibly large set
> of alarm state changes at the same time.

This is correct, but it is not limited to alarms; it applies to all
kinds of notifications.  The NETCONF WG is working on a more generic
solution to this problem, where a single notification message can
contain multiple notifications
(draft-ietf-netconf-notification-messages).   I think this is a more
flexible solution than coding this into every YANG-defined notification
(not just alarms).

> For example:
> 
>   *   re-configuration of severities
>   *   a transient network issue

I think Stefan will send some comments re these examples.


> Would we do this more efficiently by allowing the alarm-notification
> to convey a list of state changes rather than a single one?



/martin