Re: ATM connection management

Bob Natale <natale@acec.com> Tue, 11 May 1993 11:06 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00844; 11 May 93 7:06 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id ac00828; 11 May 93 7:06 EDT
Received: from thumper.bellcore.com by CNRI.Reston.VA.US id aa00959; 11 May 93 5:02 EDT
Received: from uu3.psi.com by thumper.bellcore.com (4.1/4.7) id <AA13974> for hcb@world.std.com; Tue, 11 May 93 02:32:43 EDT
Received: from acec.com by uu3.psi.com (5.65b/4.0.071791-PSI/PSINet) via SMTP; id AA19646 for atommib@thumper.bellcore.com; Tue, 11 May 93 02:32:29 -0400
Date: Tue, 11 May 1993 02:10:25 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Bob Natale <natale@acec.com>
Received: by nips.acec.com (5.65/3.2.083191-American Computer and Electronics Corp. ) id AA17639; Tue, 11 May 1993 02:10:25 -0400
Message-Id: <9305110610.AA17639@nips.acec.com>
To: rlstewart@eng.xyplex.com
Subject: Re: ATM connection management
Cc: WinSNMP@microdyne.com, atommib@thumper.bellcore.com, snmp@psi.com

> Date: Mon, 10 May 93 16:13:17 -0500
> From: Bob Stewart <rlstewart@eng.xyplex.com>
> Subject: Re: ATM connection management
> 
> The most important (and too often unasked) question about MIB objects, is what
> is a network manager supposed to do about them?  Are they just interesting?
> For accounting purposes?  What?
> ^^^^^^^^^^^^^^^^^^^^^^^ 
> The best possible reason is that you know of a certain type of failure, and
> this is an easy-to-implement, relatively-easy-to-use object for detecting or
> correcting that failure.  ALL of our MIBs would be better if we applied that
> analysis rather than the "interesting" test.
> 
> 	Bob
> 
Bob,

It is unclear to me whether you are characterizing "accounting purposes"
as being in the same category as "just interesting"...?  I doubt that
you are, but please clarify.

Personally, I plan to work to get more and better MIB objects defined,
implemented, and supported "for accounting purposes".  Such objects
are needed not just for accounting/chargeback/billing activities, but
for performance and (to a lesser extent) configuration, security, and
even fault management too.

Your second paragraph seems to focus on facilitating fault management
as *the only* criterion for MIB object validity.  Did you mean to put
more emphasis on "the best possible reason" phrase than is apparent
from the rest of the text?  If so, could you please enumerate and
assign weights or priorities to the other criteria you consider valid
and useful.

Thanks.

BobN

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Bob Natale               American Computer           301-258-9850 [tel]
Director                 209 Perry Pkwy              301-921-0434 [fax]
Network Mgmt Products    Gaithersburg MD 20877          natale@acec.com