Character MIB Issues

Bob Stewart <rlstewart@eng.xyplex.com> Fri, 11 June 1993 16:11 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09507; 11 Jun 93 12:11 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa09503; 11 Jun 93 12:11 EDT
Received: from inet-gw-2.pa.dec.com by CNRI.Reston.VA.US id aa16915; 11 Jun 93 12:11 EDT
Received: by inet-gw-2.pa.dec.com; id AA12206; Fri, 11 Jun 93 09:11:03 -0700
Received: by nsl.pa.dec.com; id AA10802; Fri, 11 Jun 93 08:25:19 -0700
Received: by nsl.pa.dec.com; id AA10798; Fri, 11 Jun 93 08:25:18 -0700
Received: by inet-gw-2.pa.dec.com; id AA09505; Fri, 11 Jun 93 08:25:17 -0700
Received: by xap.xyplex.com id <AA02149@xap.xyplex.com>; Fri, 11 Jun 93 11:25:38 -0500
Date: Fri, 11 Jun 93 11:25:38 -0500
Message-Id: <9306111625.AA02149@xap.xyplex.com>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Bob Stewart <rlstewart@eng.xyplex.com>
To: char-mib@pa.dec.com
Subject: Character MIB Issues

I already asked for specific implementation experience.  Here are 
the issues I know of, based on a review of our email and other 
events since our RFCs came out.


Relationship to Interface MIB WG

This may be a barrier until the Interface MIB WG gets their model 
sorted out.  All three of our MIBs have problems in their 
relationship to the Interface group and ifIndexes.  I believe we 
should resolve those before we go to Draft. 


Character MIB

The object charPortHardware is an AutonomousType, pointing to an 
entire subtree, which doesn't help find the right entry in, say, 
the RS-232 tables.

Proposed values enqHost(6) and enqTerm(7) for charPortInFlowType 
and charPortOutFlowType, for ENQ/ACK flow control as found in HP 
terminals:

    'enqHost' indicates ENQ characters (05) from the device are requests
    to input up to 80 characters.  They are responded to with an ACK (06)
    when at least 80 characters can be received.

    `enqTerm' indicates ACK (06) characters from the device are sent when
    at least 80 characters can be received.

Are flow control types mutually exclusive?  Should this be a bit 
string?


RS-232 MIB

Clarify if signal tables are mandatory.

Clarify intention for unimplemented signals.

Can't implement rs232SyncPortInterruptedFrames due to chip.  
Deprecate?

Can't implement rs232InSigChanges or rs232OutSigChanges because 
chip handles them.  Should say include only signals useful to 
monitor, such as DTR and DSR.

Do we need additional counters for messages or missed modem signal 
transitions?

How are table entries related to higher level entities?


Parallel MIB

No issues.