Re: [RMONMIB] comments on draft-ietf-rmonmib-dsmon-mib-02.txt

[Andy Bierman <abierman@cisco.com>]

Michael MacFaden wrote:
> 
> At 08:24 AM 10/1/2000 -0700, Andy Bierman wrote:
>  > would like to propose that it is time to stop duplicating Counter64
>  >bjects in MIBs with a "Counter32/Overflow32 pair". It is time to
>  >equire SNMPv2C support in applications to access 64-bit counters.
> 
> I personally agree, but could you explain your rational in more detail
> for breaking  with the pack of mibs that have such objects such as
> 2674, 2863...?

I think the Bridge MIB Extensions (2674) & new IF-MIB (2863) are a little
late to the party ;-)  This "SNMPv1 to V2C transition period" started a long time
ago in the RMONMIB WG (e.g. HC-RMON). I put {Counter32, Rollover32, Counter64} 
tuples in the ATM-RMON MIB in 2/96 (draft-bierman-rmon-atmrmon-00.txt), although
there may be earlier examples out there.

I think we need to take steps to reduce MIB complexity, improve MIB readability,
and encourage adoption of the most current network management standards. That's
the detailed rationale for getting rid of the "overflow" counters.

> 
> Regards,
> Mike MacFaden
> www.riverstonenet.com

Andy