IETF Logo Mail Archive

Re: MIB Comments 14

Steven Waldbusser <waldbusser+@cmu.edu> Mon, 31 January 1994 22:41 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa17448; 31 Jan 94 17:41 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa17444; 31 Jan 94 17:41 EST
Received: from apache.telebit.com by CNRI.Reston.VA.US id aa17140; 31 Jan 94 17:41 EST
Received: from america.Sunnyvale.Telebit.CO (america-bb.sunnyvale.telebit.com) by apache (4.1/SMI-4.1/Telebit-Apache-Brent-930718) id AA14812 to ietf-archive@cnri.reston.va.us; Mon, 31 Jan 94 14:16:28 PST
Received: from apache by america.Sunnyvale.Telebit.COM (4.0/america.telebit.com-DBC-930718) id AA29459 to modemmgt@apache.Sunnyvale.Telebit.COM; Mon, 31 Jan 94 14:16:26 PST
Received: from po4.andrew.cmu.edu by apache (4.1/SMI-4.1/Telebit-Apache-Brent-930718) id AA14809 to modemmgt@Telebit.COM; Mon, 31 Jan 94 14:16:23 PST
Received: from localhost (postman@localhost) by po4.andrew.cmu.edu (8.6.4/8.6.4) id RAA01564 for modemmgt@telebit.com; Mon, 31 Jan 1994 17:16:11 -0500
Received: via switchmail; Mon, 31 Jan 1994 17:16:09 -0500 (EST)
Received: from zeus.net.cmu.edu via qmail ID </afs/andrew.cmu.edu/service/mailqs/testq0/QF.ghHM=hG00WArA0NbhH>; Mon, 31 Jan 1994 17:15:10 -0500 (EST)
Received: from zeus.net.cmu.edu via qmail ID </afs/andrew.cmu.edu/usr5/sw0l/.Outgoing/QF.YhHM=di00WAr1AGYk=>; Mon, 31 Jan 1994 17:15:06 -0500 (EST)
Received: from Messages.8.5.N.CUILIB.3.45.SNAP.NOT.LINKED.zeus.net.cmu.edu.sun4c.411 via MS.5.6.zeus.net.cmu.edu.sun4c_411; Mon, 31 Jan 1994 17:15:03 -0500 (EST)
Message-Id: <MhHM=bi00WArFAGYZ3@andrew.cmu.edu>
Date: Mon, 31 Jan 1994 17:15:03 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Steven Waldbusser <waldbusser+@cmu.edu>
To: modemmgt@telebit.com
Subject: Re: MIB Comments 14
In-Reply-To: <Macintosh*/PRMD=ILBE/ADMD=MOT/C=US/@ilbe>
References: <Macintosh*/PRMD=ILBE/ADMD=MOT/C=US/@ilbe>

Excerpts from mail: 31-Jan-94 MIB Comments 14 Les_Brown-LLB005@email.m (331)

> Concerning some of the mdmStats objects, I think the descriptions should 
> reference the connect fail reason(s) that are pertinent.

Sounds reasonable.

Excerpts from mail: 31-Jan-94 MIB Comments 14 Les_Brown-LLB005@email.m (331)

> For example, for 
> mdmIncomingConnectionFailures, it is not clear if this includes both of
> the ring 
> no answer counts. For mdmStatsIncomingAbnormalTerminations, what is the 
> definition of 'abnormal'.

I think the answers to both of these questions are pending the answers
to some questions I posed in my long message over the weekend.


Steve

v2.23.0 | Report a Bug | By Email