Re: ATM connection management

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

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa19753; 11 May 93 18:26 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa19749; 11 May 93 18:26 EDT
Received: from thumper.bellcore.com by CNRI.Reston.VA.US id aa27887; 11 May 93 18:26 EDT
Received: from xap.xyplex.com by thumper.bellcore.com (4.1/4.7) id <AA21400> for ietf-archive@cnri.reston.va.us; Tue, 11 May 93 17:31:11 EDT
Received: by xap.xyplex.com id <AA21414@xap.xyplex.com>; Tue, 11 May 93 18:03:27 -0500
Date: Tue, 11 May 93 18:03:27 -0500
Message-Id: <9305112303.AA21414@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: William Manning's message of Tue, 11 May 93 15:43:06 CDT <9305112043.AA11727@is.rice.edu>
Subject: Re: ATM connection management

>	2. there seems to be a feeling on those folks that are doing draft
>           reviews, that the SNMP MIB descriptions are the last things selected,
>	   since they are SOOOOO cryptic. or maybe just dry.

The DESCRIPTION clauses in SNMP MIBs are explicitly intended for the
implementor of the MIB, not the user.  We have no standard repository of user
explanations, and there has been little progress in supplying them.

Please don't suggest that we should require them.  Defining MIBs takes long
enough as it is.  I'm suggesting that anyone developing a MIB should at least
consider how you'd explain to a user which object to poke with what value when
which other object takes on what value.  Of course if it's that simple, it
should be imbedded operation, not MIB objects.

	Bob