Re: another error in the examples in rfc3877

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" <[email protected]>
>> To: <[email protected]>
>> 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
>
>
>