Re: Advice on restricting SIZE of InetAddress in INDEX?

[Keith McCloghrie <kzm@cisco.com>]

> Oops, when I did the first calculation my brain misfired and I used
> 256 instead of 128 as the max OID len.  So, I guess the choices are:
> 
> 1. Use the max that will fit (in this case, SIZE(1..57), since
>    msdpRequestsEntry is .1.3.6.1.3.92.1.2.1 and there are 3 other values
>    in the INDEX)?
> 2. Pick some arbitrary nice-looking number, like 32 or 48?
> 3. Limit the length to the values that I expect
> 
> #3 is probably out, since it doesn't allow for *any* extensibility.
> #2 is prettier (and allows a little room for relocating the MIB lower
>    in the tree, if required) but allows for less extensibility.
> #1 gives the most room.  (Although requires looking ahead, since if the
>    DRAFT-MSDP-MIB were under mib-2 it'd have to be SIZE(1..56))
 
Of course, there's also a fourth choice:

4. change your mind and use an arbitrary integer as the INDEX :-).

Keith.