RE: Plans for this year?
"CLI-W-PERSTUP, Personal name too stupid to print." <firstname.lastname@example.org> Wed, 05 January 1994 15:21 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa05958;
5 Jan 94 10:21 EST
Received: from CS.UTK.EDU by IETF.CNRI.Reston.VA.US id aa05952; 5 Jan 94 10:21 EST
Received: from localhost by CS.UTK.EDU with SMTP (8.6.4/2.8s-UTK) id JAA18743; Wed, 5 Jan 1994 09:59:53 -0500
X-Resent-To: chassismib@CS.UTK.EDU ; Wed, 5 Jan 1994 09:59:51 EST
Received: from inet-gw-2.pa.dec.com by CS.UTK.EDU with SMTP (8.6.4/2.8s-UTK) id JAA18730; Wed, 5 Jan 1994 09:59:44 -0500
Received: by inet-gw-2.pa.dec.com; id AA15865; Wed, 5 Jan 94 06:50:33 -0800
Received: by us1rmc.bb.dec.com; id AA08648; Wed, 5 Jan 94 09:45:43 -0500
Received: from quiver.enet; by us1rmc.enet; Wed, 5 Jan 94 09:50:14 EST
Date: Wed, 5 Jan 94 09:50:14 EST
From: "CLI-W-PERSTUP, Personal name too stupid to print." <email@example.com>
Subject: RE: Plans for this year?
>1. Did anybody implement the chassis mib? > If so, I'd like to hear from you if you care to share your experiences. > We (Digital) have implemented a "chassis MIB" in our DEChub900 product. The MIB is similar a very early draft presented by the IETF Chassis MIB Working Group (a Cabletron/Synoptics/Hughes proposal). Our chassis MIB has a slot group, entity group, segment groups, power source group, power sink group, environmental group, and load group. The segment group is very product specific. The slot and entity groups are similar to what other hub vendors have implemented. Standardizing on objects which allow backplane LAN-hopping, port-switching, etc. seems to me to be very difficult. -Shawn