Re: ATM connection management

Bob Stewart <rlstewart@eng.xyplex.com> Tue, 11 May 1993 20:30 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa14907; 11 May 93 16:30 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa14903; 11 May 93 16:30 EDT
Received: from thumper.bellcore.com by CNRI.Reston.VA.US id aa22909; 11 May 93 16:30 EDT
Received: from xap.xyplex.com by thumper.bellcore.com (4.1/4.7) id <AA09183> for ietf-archive@cnri.reston.va.us; Tue, 11 May 93 15:50:48 EDT
Received: by xap.xyplex.com id <AA19507@xap.xyplex.com>; Tue, 11 May 93 16:22:57 -0500
Date: Tue, 11 May 93 16:22:57 -0500
Message-Id: <9305112122.AA19507@xap.xyplex.com>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Bob Stewart <rlstewart@eng.xyplex.com>
To: WinSNMP@microdyne.com, atommib@thumper.bellcore.com, snmp@psi.com
In-Reply-To: Bob Natale's message of Tue, 11 May 1993 02:10:25 -0400 <9305110610.AA17639@nips.acec.com>
Subject: Re: ATM connection management

Don't blame me for the cross-post.  Natale started it.

Naw.  "Accounting purposes" isn't the same as "just interesting."  It's less
than that.

Joke.  Joke.  I didn't mean it.

I admit a strong bias toward fault management, somewhat on the basis that I'd
like to see us get that one a bit more right before we delve too far into the
others.  On the other hand, I readily concede the strong cross-purpose among
many MIB objects for all the OSI-enumerated management areas.

Rather than prioritize reasons, I'd rather restate a general principle.  Every
MIB object must pass the scrutiny of "so what."  You must be able to answer
why the network manager cares, and what he's supposed to do about it.  You
don't have to list every use of a given object, but you should be able to give
at least one clear, strong example of its value.  "Interesting" isn't
sufficient. 

	Bob