[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: InetAddressType and InetAddress
On Sun, 17 Nov 2002, Wijnen, Bert (Bert) wrote:
> What do we do with this....
>
> If someone wants to limit the values for InetAddressType and
> InetAddress to a subset of those defined in INET-ADDRESS-MIB,
> then my current recommendation is this (example from diffserv)
[ snip ]
> Sofar so good. But now what if one wants to use the same thing for
> an InetAddressType and an InetAddress that are used as INDEX objects.
> Cause now:
> - one needs to limit the size of InetAddress to not go over 128 subids
> (I know some find this a CLR... so we could do away with it)
Actually the requirement is that the entire name (i.e., OID prefix plus
index components) not exceed 128 components. This is a restriction of
the SNMP. I don't think that we can just say that this is a CLR to be
ignored. A MIB that violates this rule cannot be used.
> - one cannot include INDEX objects (not-accessible) in the
> MODULE-COMPLIANCE.
>
> So what do we do about this. I thought I had brought this up with someone
> (Juergen? or mibs list) some time ago, but I cannot find the discussion
> and or outcome in my mail archives.
>
> The question is imminent, cause I have the malloc MIB on the IESG agenda
>
> draft-ietf-malloc-malloc-mib-07.txt
I was the reviewer of this module, and I strongly agreed with the author
that the right thing to do is put a range restriction on the length of
InetAddress objects that are used as index objects.
Regards,
Mike