[netmod] BBF alarm management YANG plans

William Lupton <wlupton@broadband-forum.org> Mon, 27 March 2017 16:09 UTC

Return-Path: <wlupton@broadband-forum.org>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A921129478 for <netmod@ietfa.amsl.com>; Mon, 27 Mar 2017 09:09:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 LVCMA3c--hDH for <netmod@ietfa.amsl.com>; Mon, 27 Mar 2017 09:09:51 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9476A129465 for <netmod@ietf.org>; Mon, 27 Mar 2017 09:09:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 7EA0F1E5693; Mon, 27 Mar 2017 09:09:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id wYdC9sGrss6k; Mon, 27 Mar 2017 09:09:14 -0700 (PDT)
Received: from [172.16.46.43] (dtrscolumbus03.d.subnet.rcn.com [207.229.135.146]) by c8a.amsl.com (Postfix) with ESMTPSA id 3D8DB1E568B; Mon, 27 Mar 2017 09:09:14 -0700 (PDT)
From: William Lupton <wlupton@broadband-forum.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_011DAB40-E1B9-4602-B6A4-F6955B80D6DC"
Date: Mon, 27 Mar 2017 11:09:51 -0500
To: netmod@ietf.org
Message-Id: <914D6A80-10BA-42A8-AC71-14BDD9E62A4C@broadband-forum.org>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/Vbxj4rITUAH7DQo3LgKPjEf1fgM>
Subject: [netmod] BBF alarm management YANG plans
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Mar 2017 16:09:53 -0000

All,

I believe that we last discussed alarms (and draft-vallin-netmod-alarm-module) back in October when the -01 draft was published. Alarm management has once again come to the fore in BBF and I wanted to give NETMOD an update on our plans.
We wish to base our alarm management support on draft-vallin-netmod-alarm-module
We request that it be adopted as a working group draft
We will have various comments, e.g.
Providing some means of overriding alarm severities
Adjusting the alarm-history feature to include some additional nodes that we believe should be within its scope
Various proposals to adjust node names that we feel will better reflect their usage and/or increase consistency
Individual contributors will bring detailed comments directly to the NETMOD list.

Thanks,
William