Re: vacmViewTreeFamilySubtree missing SIZE restriction

Sorry, nevermind.  I misread the table in RFC 2578(9), which doesn't allow
any restrictions for OBJECT IDENTIFIER types.  My eyes lined up the (3)
with the wrong type when I was looking up object identifier refinements.

On Sat, 11 Jan 2003, Michael Kirkham wrote:

> Date: Sat, 11 Jan 2003 19:53:49 -0800 (PST)
> From: Michael Kirkham <[email protected]>
> To: [email protected]
> Subject: vacmViewTreeFamilySubtree missing SIZE restriction
>
>
> Hi, all.  My MIB compiler work picked upon the following error in RFC
> 3415, which is also present in 2575 and 2275:
>
> rfc3415.mib [SNMP-VIEW-BASED-ACM-MIB:vacmViewTreeFamilyEntry] : error :
> INDEX object 'vacmViewTreeFamilySubtree' value may exceed maximum of 128
> subidentifiers for OBJECT IDENTIFIER length.
>
> The RFC 3415 definition is:
>
> vacmViewTreeFamilySubtree OBJECT-TYPE
>     SYNTAX       OBJECT IDENTIFIER
>     MAX-ACCESS   not-accessible
>     STATUS       current
>     DESCRIPTION "The MIB subtree which when combined with the
>                  corresponding instance of vacmViewTreeFamilyMask
>                  defines a family of view subtrees.
>                 "
>     ::= { vacmViewTreeFamilyEntry 2
>
> I believe it should be:
>
>     SYNTAX       OBJECT IDENTIFIER (SIZE(2..84))
>
> --
> Michael Kirkham
> www.muonics.com
>
>

--
Michael Kirkham
www.muonics.com