[comp.protocols.tcp-ip] time to get the ol' MIBs in...

chris@SALT.ACC.COM (Chris VandenBerg) (04/07/90)

Ladies and Gentlemen,
		    The "collecting of the MIBs" continues on, but not at the
pace that I envisioned. When I raised this issue several weeks ago it seemed
that there were many who added their voices that this was a GOOD THING. But,
quite honestly, I've only gotten about 10 mibs so far. Now I know that some
vendors may not have everything RFC1066 compliant yet. If so, that's certainly
understandable but please let me know that you're going to be coming forth
at some point with your extensions so I can count you among those who recognize
this is good for everyone. Right know everyone is scrambling around to get
all the mibs they need, and this same scenario gets repeated in untold companiesday after day. Were wasting time tracking down mibs instead of enhancing our
products. So if we put them all on a central site who wins? Well, the users
get a product that is truly "interoperable" right out of the box and they
feel good about buying into the SNMP management scheme. The vendors win 
because we DON'T waste time looking for XYZ mib.We spend it, instead, putting the
features into our products that the users want.
	So please let me know if we can expect your mib. Joyce Reynolds at ISI
has been gracious enough to have the archive down at ISI but doesn't want to
add to her workload too much. I've tried to help out by funneling them down to
her once a week. If you have a problem sending them via me let's talk about it.
Users can help out too by asking your favorite vendors if they've put their 
mibs into the repository.
	We can really only realize the potential of "standard management" if
we get away from proprietary thinking in the area of mib info. Please direct
comments, flames and, yes, even mibs to me.
		Thanks in advance,
				Chris VandenBerg
				(chris@salt.acc.com)
				805-963-9431