Re: [Disman] another question about alarmMib..

"Randy Presuhn" <randy_presuhn@mindspring.com> Tue, 23 December 2008 19:20 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 54F7E3A67FD; Tue, 23 Dec 2008 11:20:26 -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 5836E3A67FD for <disman@core3.amsl.com>; Tue, 23 Dec 2008 11:20:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.308
X-Spam-Level:
X-Spam-Status: No, score=-2.308 tagged_above=-999 required=5 tests=[AWL=0.291, BAYES_00=-2.599]
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 393Wa0rt5mTc for <disman@core3.amsl.com>; Tue, 23 Dec 2008 11:20:24 -0800 (PST)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by core3.amsl.com (Postfix) with ESMTP id 702283A67D0 for <disman@ietf.org>; Tue, 23 Dec 2008 11:20:24 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=T/h1nt0NEajCTRK8ZTbFulMUqMfvmPn/zOIL3XLrH6wxzFHzJFZQZAYK6lgJ88Gt; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [69.3.26.128] (helo=oemcomputer) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1LFCnf-0008Ia-0j for disman@ietf.org; Tue, 23 Dec 2008 14:20:15 -0500
Message-ID: <002501c96533$c9bcc960$6801a8c0@oemcomputer>
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: disman@ietf.org
References: <4946D492.5070107@redback.com><004701c95fb1$c30f9c00$6801a8c0@oemcomputer><49481B7C.1060301@redback.com> <000301c95fc7$8b51e320$6801a8c0@oemcomputer> <EDC652A26FB23C4EB6384A4584434A040122F5F8@307622ANEX5.global.avaya.com>
Date: Tue, 23 Dec 2008 11:22:24 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8886924630f8852f17374f5b27aaee32413829845de1f116b5a350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 69.3.26.128
Subject: Re: [Disman] another question about alarmMib..
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

Hi -

Dan's suggestion makes sense to me.

Randy

----- Original Message ----- 
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Randy Presuhn" <randy_presuhn@mindspring.com>; <disman@ietf.org>
Sent: Tuesday, December 23, 2008 7:00 AM
Subject: RE: [Disman] another question about alarmMib..


Hi,

Thanks to Michael for catching an d reporting this. I apologize for the
late response. All excuses related to a busy end of the year and a
holiday season that already begun in some legislations apply. 

There is a problem with this erratum and with the document itself. There
are actually two problems. 

1. The original erratum submitted by Andreas.Politze@keymile.com was
reporting that the mapping 

     alarmModelState -> ituAlarmPerceivedSeverity
            1 -> clear (1)
            2 -> indeterminate (2)
            3 -> warning (6)
            4 -> minor (5)
            5 -> major (4)
            6 -> critical (3) 

is not applied consistently in the examples. 

This is correct, and we acknowledged this problem. The RFC Editor
however inserted a different resolution in the RFC Errata that was
published. 

Right now I see such problems in the examples in 6.1 to 6.3. 

2. In examples 6.2 and 6.3 ituPerceivedSeverity is used instead of
ituAlarmPerceivedSeverity

My proposal is to issue a new erratum to correct the above and to ask
the RFC Editor to cancel or reject the current erratum. 

With everybody's permission we shall do this in the first few weeks of
the new year. 

I hope this helps. 

Happy Holidays,

Dan