While editing the Counter MIB, I found a serious flaw in the LCRC-21
and LCRC-22 issues/resolutions.
The abstract counters 'Local/RemoteStorageKOctets' should indeed
be moved _up_ from the Activity level (Work, Datastream, etc.) to the
Monitoring table in the Counter MIB (like the Counter spec).
But the abstract counters 'Input/OuputMessages' should be replicated at
_both_ the Activity level and the Monitoring (Service) level (just like
the comparable 'Input/OutputKOctets') because they're customer billing
counters (for message-oriented Services like EmailIn/Out, FaxIn/Out).
Customers will object (correctly) to be charged for Message traffic
for Maintenance jobs.
This may become slightly clearer than the above explanation when folks
review the revised Counter MIB, which I still hope to post sometime
this evening (possibly without a few body text updates).
Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221 Grand Marais, MI 49839
email: imcdonald at sharplabs.com