Re: RS-232-like MIB Required Implementation
Bob Stewart <rlstewart@eng.xyplex.com> Mon, 29 June 1992 16:30 UTC
Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa09108;
29 Jun 92 12:30 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa09104;
29 Jun 92 12:30 EDT
Received: from inet-gw-2.pa.dec.com by NRI.Reston.VA.US id aa06959;
29 Jun 92 12:31 EDT
Received: by inet-gw-2.pa.dec.com; id AA04719; Mon, 29 Jun 92 09:30:28 -0700
Received: by nsl.pa.dec.com; id AA09327; Mon, 29 Jun 92 09:29:20 -0700
Received: by inet-gw-2.pa.dec.com; id AA04649; Mon, 29 Jun 92 09:29:14 -0700
Received: by xap.xyplex.com id <AA21121@xap.xyplex.com>;
Mon, 29 Jun 92 12:11:41 -0500
Date: Mon, 29 Jun 92 12:11:41 -0500
Message-Id: <9206291711.AA21121@xap.xyplex.com>
From: Bob Stewart <rlstewart@eng.xyplex.com>
To: short@microcom.com
Cc: char-mib@pa.dec.com
In-Reply-To: Todd Short's message of Mon,
29 Jun 92 08:35:04 EDT <9206291235.AA08489@python.microcom.com>
Subject: Re: RS-232-like MIB Required Implementation
The intention iss that the Input and Output Signal tables are mandatory in the same way as the generic table. If you have none of the signals at all, the point is moot because you'll have empty tables and you can't tell an empty table from one that's not implemented. Some of that intent is visible in the descriptions of the objects that tell you how many entries are in the signal tables. Bob
- RS-232-like MIB Required Implementation Todd Short
- Re: RS-232-like MIB Required Implementation Bob Stewart
- Re: RS-232-like MIB Required Implementation Bob Stewart