[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RMONMIB] smilint messages for APM-MIB
At 04:49 PM 8/6/2002 -0700, Randy Presuhn wrote:
>Hi -
>
>> Message-Id: <4.3.2.7.2.20020806152246.01939df0@fedex.cisco.com>
>> Date: Tue, 06 Aug 2002 15:30:26 -0700
>> To: rmonmib@ietf.org
>> From: Andy Bierman <abierman@cisco.com>
>> Cc: waldbusser@nextbeacon.com
>> Subject: [RMONMIB] smilint messages for APM-MIB
>...
>> The 'must have a size restriction' messages are more controversial. I believe
>> the 128 sub-OID limit is artificial, arbitrary, and likely to be raised in the next
>> version of the SMI. These messages are showing up for OCTET STRING objects
>> in an INDEX. The length of these strings are actually constrained by the
>> semantics of the protocolDirEntry associated with the address string.
>...
>
>Even if the next version of the SMI eliminates this particular
>CLR, don't forget that RFC 1905 (protocol operations, clause
>4.1, last paragraph) imposes the same limit at the protocol
>level. The updates (awaiting publication as Standard) impose
>the same restriction.
good point.
general protocol issue:
Should the RFC 1905 update increase the limit to the same value the
SMIng WG will use? IMO, this CLR is too restrictive and has proven
to be too low a number considering current MIB design practices.
This CLR was added to SNMP to benefit MIB compiler and MIB engine
developers, at the expense of MIB designers.
Andy
> ------------------------------------------------------
> Randy Presuhn BMC Software, Inc. 1-3141
> randy_presuhn@bmc.com 2141 North First Street
> Tel: +1 408 546-1006 San José, California 95131 USA
> ------------------------------------------------------
> My opinions and BMC's are independent variables.
> ------------------------------------------------------
>
>_______________________________________________
>RMONMIB mailing list
>RMONMIB@ietf.org
>https://www1.ietf.org/mailman/listinfo/rmonmib