Re: [Disman] another error in the examples in rfc3877

"Randy Presuhn" <randy_presuhn@mindspring.com> Sat, 10 January 2009 00:35 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 CFC8E3A6B07; Fri, 9 Jan 2009 16:35:36 -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 7139A3A6A56 for <disman@core3.amsl.com>; Fri, 9 Jan 2009 16:35:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[AWL=-0.909, BAYES_20=-0.74]
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 LOc5oz0mtcJh for <disman@core3.amsl.com>; Fri, 9 Jan 2009 16:35:34 -0800 (PST)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by core3.amsl.com (Postfix) with ESMTP id 1C7A93A6B07 for <disman@ietf.org>; Fri, 9 Jan 2009 16:35:34 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=oYWsK9yHtn5anBI0NunZkje7smoja8f9SbEk4Tj/EoQFOu8plN8UwmLhn3TtafkU; 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 [68.165.5.216] (helo=oemcomputer) by elasmtp-banded.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1LLRou-0002hW-Al for disman@ietf.org; Fri, 09 Jan 2009 19:35:20 -0500
Message-ID: <001b01c972bb$b96318e0$6801a8c0@oemcomputer>
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: disman@ietf.org
References: <4963D735.4@redback.com>
Date: Fri, 09 Jan 2009 16:38:13 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8886924630f8852f173b78a396c154bb03301d407fec1c01630350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 68.165.5.216
Subject: Re: [Disman] another error in the examples in rfc3877
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 -

> From: "Michael Thatcher" <thatcher@redback.com>
> To: <disman@ietf.org>
> Sent: Tuesday, January 06, 2009 2:12 PM
> Subject: [Disman] another error in the examples in rfc3877
>
> in section 6.1, the values given for alarmModelSpecificPointer and
>  ituAlarmGenericModel are, respectively, "ituAlarmEntry.x.y" and
> "alarmModelEntry.x.y".
> However, alarmModelSpecificPointer and ituAlarmGenericModel
> are type RowPointer so they should point to the 1st available object
> in the row which are, respectively, ituAlarmEventType and alarmModelNotificationId.
...

My recollection (which may be faulty) was that this was deliberate, to
illustrate the concept of the pointer, rather than the detail.  While
"ituAlarmEventType.x.y" might be more correct, I'm not sure that
it's more enlightening.  But I'd love to hear from the authors and
folks who have (tried) to implement this spec.

Randy