Re: RS-232 Interface Type MIB

Dave Cullerot <cullerot@ctron.ctron.com> Fri, 02 October 1992 18:11 UTC

Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa07565; 2 Oct 92 14:11 EDT
Received: from NRI.RESTON.VA.US by IETF.NRI.Reston.VA.US id aa07561; 2 Oct 92 14:11 EDT
Received: from inet-gw-2.pa.dec.com by NRI.Reston.VA.US id aa15118; 2 Oct 92 14:15 EDT
Received: by inet-gw-2.pa.dec.com; id AA05723; Fri, 2 Oct 92 11:15:59 -0700
Received: by nsl.pa.dec.com; id AA14509; Fri, 2 Oct 92 10:22:53 -0700
Received: by nsl.pa.dec.com; id AA14494; Fri, 2 Oct 92 10:20:51 -0700
Received: by inet-gw-1.pa.dec.com; id AA03679; Fri, 2 Oct 92 10:18:45 -0700
Received: from ctron.com by nic.near.net id aa22848; 2 Oct 92 13:18 EDT
Received: from ctron.ctron (ctron.ctron.com) by ctron.com (4.1/SMI-4.1)id AA02289; Fri, 2 Oct 92 13:26:12 EDT
Received: from crux.ctron by ctron.ctron (4.1/SMI-4.1)id AA18136; Fri, 2 Oct 92 13:12:37 EDT
Date: Fri, 2 Oct 92 13:12:37 EDT
Sender: ietf-archive-request@IETF.NRI.Reston.VA.US
From: Dave Cullerot <cullerot@ctron.ctron.com>
Message-Id: <9210021712.AA18136@ctron.ctron>
To: rlstewart@eng.xyplex.com
Subject: Re: RS-232 Interface Type MIB
Cc: char-mib@pa.dec.com, snmp@psi.com

Bob,

Thanks for your quick response.

> 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.
> 

I agree, but I thought a change would be more readily accepted by your WG.
Good intentions, wrong reason.

> 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.
> 

If you mean ifType being broken into logical and physical, I like the idea --
provided the ACCESS is changed to read-write, so that I may "legally" write 
to that leaf.

> 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
> 

Oh well, enterprise it is.  I'll give you feedback on our experience after
deployment.

Thanks,
	Dave