Re: RS-232 Interface Type MIB

Bob Stewart <rlstewart@eng.xyplex.com> Fri, 02 October 1992 16:11 UTC

Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa06077; 2 Oct 92 12:11 EDT
Received: from NRI.RESTON.VA.US by IETF.NRI.Reston.VA.US id ab06072; 2 Oct 92 12:11 EDT
Received: from inet-gw-2.pa.dec.com by NRI.Reston.VA.US id aa12386; 2 Oct 92 12:16 EDT
Received: by inet-gw-2.pa.dec.com; id AA28031; Fri, 2 Oct 92 09:16:29 -0700
Received: by nsl.pa.dec.com; id AA13455; Fri, 2 Oct 92 09:02:27 -0700
Received: by nsl.pa.dec.com; id AA13451; Fri, 2 Oct 92 09:02:26 -0700
Received: by inet-gw-2.pa.dec.com; id AA27178; Fri, 2 Oct 92 09:02:22 -0700
Received: by xap.xyplex.com id <AA19757@xap.xyplex.com>; Fri, 2 Oct 92 12:00:41 -0500
Date: Fri, 2 Oct 92 12:00:41 -0500
Message-Id: <9210021700.AA19757@xap.xyplex.com>
Sender: ietf-archive-request@IETF.NRI.Reston.VA.US
From: Bob Stewart <rlstewart@eng.xyplex.com>
To: snmp@psi.com, char-mib@pa.dec.com
In-Reply-To: Dave Cullerot's message of Thu, 1 Oct 92 17:37:11 EDT <9210012137.AA11927@ctron.ctron>
Subject: Re: RS-232 Interface Type MIB

A single object to indicate the intended use of a port is a nice idea, but I
don't believe the RS-232 MIB is the right place for it.  The RS-232 MIB is
used for both character ports and network interfaces, so such an object would
have to work for both of those, but it wouldn't extend to non-RS-232
instances.  If there is to be such an object, it should be more central.

There's been ongoing talk of a need to revamp the MIB-II Interface group to
account for logical and physical and stacks thereof, and perhaps to include
character ports, which become network interfaces when they run SLIP or PPP.
Such a revamped group might be the right place for the object you suggest.

In the meantime, it would have to be in enterprise space, and experience with
it's position there would be valuable in deciding where it should really be.

	Bob