Rick Royston's MIB Comments
"Royston, Rick" <rroyston@usr.com> Tue, 25 January 1994 15:30 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa02787; 25 Jan 94 10:30 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa02783; 25 Jan 94 10:30 EST
Received: from apache.telebit.com by CNRI.Reston.VA.US id aa03561; 25 Jan 94 10:30 EST
Received: from america.Sunnyvale.Telebit.CO (america-bb.sunnyvale.telebit.com) by apache (4.1/SMI-4.1/Telebit-Apache-Brent-930718) id AA21688 to ietf-archive@cnri.reston.va.us; Tue, 25 Jan 94 07:21:56 PST
Received: from apache by america.Sunnyvale.Telebit.COM (4.0/america.telebit.com-DBC-930718) id AA10205 to modemmgt@apache.Sunnyvale.Telebit.COM; Tue, 25 Jan 94 07:21:54 PST
Received: from usr.com (INTERGATE.USR.COM) by apache (4.1/SMI-4.1/Telebit-Apache-Brent-930718) id AA21685 to modemmgt@Telebit.COM; Tue, 25 Jan 94 07:21:49 PST
Received: from robogate.usr.com by usr.com (4.1/3.1.090690-US Robotics ) id AA11072; Tue, 25 Jan 94 09:21:39 CST
Received: from ccMail by robogate.usr.com id AA759518695 Tue, 25 Jan 94 09:24:55 CDT
Date: Tue, 25 Jan 1994 09:24:55 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Royston, Rick" <rroyston@usr.com>
Message-Id: <9400257595.AA759518695@robogate.usr.com>
To: modemmgt@telebit.com
Subject: Rick Royston's MIB Comments
Here are my comments to the 1/4/94 MIB 1. Royston, not Roysten 2. mdmLineCarrierLossControl - why not assign mdmLineCarrierLossTime a value of 0 and delete this object? 3. mdmLineCapabilities - what about V.25 bis, V.32 terbo ? Also who is the keeper of the protocol list? 4. mdmDTEActionOnDTROffToOn - if an object is defined for a DialNumber, it can be treated as other objects with a RAM copy and NVRAM copy(ies). Then enableDial and establishConnection are the same. I suggest that they be replaced by DialmdmPhoneNumber(2) where mdmPhoneNumber is the name of the preconfigured object 5. mdmDTEInactivityTimeOut - reference to start/stop switched, changed to async dial 6. mdmAutoAnswerEnable - this object duplicated the function of mdmRingsBeforeAnswer when its value is 0. Delete ? 7. mdmCallProgressDetect - this object is a mess in current modems. I wonder if an enumeration of EverthingInTheModem(5) is reasonable? 8. mdmResultCodeEnable - replace enable(1) with enableNumeric and enableVerbose. 9. mdmStoredDialString - should we define a max length. I think we use 30 or 40. Comments? 10. mdmCCConnectFailReason - add text to state that not all devices can or will return all of these possible values. I have problems with this object, but have no good solutions as of now. Maybe we should minimize this list? 11. mdmCCErrorControlUsed - in description value '{0 0}' ? 12. mdmStatsIncomingConnectionsRequest - rename to mdmStatsIncomingConnectionsAccepted and change desc. 13. mdmStatsIncomingAbnormalTerminations - how is this different from failed connection requests. All connections abnormally terminate by loss of DCD, or some other means. 14. mdmStatsOutgoingConnectionRequests - rename to mdmStatsOutgoingConnectionsAccepted. 15. mdmStatsRingNoAnswer - description ",but the call was not answered". If the ring detect is separate, the DSP may be ill. 16. mdmStatsSentDataFrames |Recieved DataFrames - line and NOT DTE Please comment on my comments asap. We need to get some concensus before Jan 31. Rick
- Rick Royston's MIB Comments Royston, Rick
- Re: Rick Royston's MIB Comments Rozman, Chris