[Disman] some questions about rfc3877 (alarm mib)

Michael Thatcher <thatcher@redback.com> Fri, 12 December 2008 23:29 UTC

Return-Path: <disman-bounces@ietf.org>
X-Original-To: disman-archive@megatron.ietf.org
Delivered-To: ietfarch-disman-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 34A0E3A6A65; Fri, 12 Dec 2008 15:29:10 -0800 (PST)
X-Original-To: disman@core3.amsl.com
Delivered-To: disman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2F62F3A6B40 for <disman@core3.amsl.com>; Fri, 12 Dec 2008 10:56:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.057
X-Spam-Level:
X-Spam-Status: No, score=-1.057 tagged_above=-999 required=5 tests=[AWL=0.084, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YF3c3BelfAWf for <disman@core3.amsl.com>; Fri, 12 Dec 2008 10:56:39 -0800 (PST)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9]) by core3.amsl.com (Postfix) with ESMTP id 8ABCD3A6B22 for <disman@ietf.org>; Fri, 12 Dec 2008 10:56:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id BA715904A46; Fri, 12 Dec 2008 10:56:33 -0800 (PST)
Received: from prattle.redback.com ([127.0.0.1]) by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11168-04; Fri, 12 Dec 2008 10:56:33 -0800 (PST)
Received: from [155.53.44.238] (nurnberg.redback.com [155.53.44.238]) by prattle.redback.com (Postfix) with ESMTP id A22A7904A45; Fri, 12 Dec 2008 10:56:33 -0800 (PST)
Message-ID: <4942B3E1.4070503@redback.com>
Date: Fri, 12 Dec 2008 10:56:33 -0800
From: Michael Thatcher <thatcher@redback.com>
User-Agent: Thunderbird 2.0.0.6 (X11/20070728)
MIME-Version: 1.0
To: disman@ietf.org
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at redback.com
X-Mailman-Approved-At: Fri, 12 Dec 2008 15:29:08 -0800
Subject: [Disman] some questions about rfc3877 (alarm mib)
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/disman>, <mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/disman>, <mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

1. I don't understand the errata (http://www.rfc-editor.org/errata_search.php?rfc=3877" rel="nofollow">http://www.rfc-editor.org/errata_search.php?rfc=3877) which says that ituPerceivedSeverity must be changed to alarmModelState. Why this change? Isn't this just a typo where ituPerceivedSeverity should be ituAlarmPerceivedSeverity?  There are multiple occurrances of ituPerceivedSeverity in 6.2 & 6.3 which seem to me should be ituAlarmPerceivedSeverity.

2. None of the examples use the index attribute alarmListName for objects which have this as an index, such as the value for ituAlarmGenericModel.  To be complete shouldn't the examples define an alarmListName (or use 0 as the index value indicating no name)?

3. It's not clear to me how one matches a clear event to an existing active alarm so it can be removed from the active table and the alarmActiveIndex value used for the clear event in the clear table.  It's (relatively) easy if the notification and resource IDs are the same for the clear and current active. When the notification ids are different between clear and raise,
or if there are multiple active alarms, it seems that some other methodology is required which I don't particularly see.  Any insights would be appreciated.

miket