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

Michael Thatcher <thatcher@redback.com> Sat, 10 January 2009 01:16 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 12E923A6B09; Fri, 9 Jan 2009 17:16:48 -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 D2C7E3A6B09 for <disman@core3.amsl.com>; Fri, 9 Jan 2009 17:16:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.984
X-Spam-Level:
X-Spam-Status: No, score=-1.984 tagged_above=-999 required=5 tests=[AWL=0.615, 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 QTS3BB7ohCjn for <disman@core3.amsl.com>; Fri, 9 Jan 2009 17:16:46 -0800 (PST)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9]) by core3.amsl.com (Postfix) with ESMTP id 2A3383A6767 for <disman@ietf.org>; Fri, 9 Jan 2009 17:16:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id CB68081F90B; Fri, 9 Jan 2009 17:16:32 -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 07011-06; Fri, 9 Jan 2009 17:16:32 -0800 (PST)
Received: from [155.53.44.238] (nurnberg.redback.com [155.53.44.238]) by prattle.redback.com (Postfix) with ESMTP id AB50A81F909; Fri, 9 Jan 2009 17:16:32 -0800 (PST)
Message-ID: <4967F6F0.3020806@redback.com>
Date: Fri, 09 Jan 2009 17:16:32 -0800
From: Michael Thatcher <thatcher@redback.com>
User-Agent: Thunderbird 2.0.0.6 (X11/20070728)
MIME-Version: 1.0
To: Randy Presuhn <randy_presuhn@mindspring.com>
References: <4963D735.4@redback.com> <001b01c972bb$b96318e0$6801a8c0@oemcomputer>
In-Reply-To: <001b01c972bb$b96318e0$6801a8c0@oemcomputer>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at redback.com
Cc: disman@ietf.org
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

well the rfc says it's an "example".  I expect the example to use valid 
values unless otherwise documented.   Particularly when someone (like a 
test group) may use it to generate tests for validity. 

miket
Randy Presuhn wrote:
> 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
>
>
>