IETF Logo Mail Archive

Re: Future

Andrew Bierman <abierman@synoptics.com> Thu, 09 June 1994 16:55 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06522; 9 Jun 94 12:55 EDT
Received: from CS.UTK.EDU by IETF.CNRI.Reston.VA.US id aa06518; 9 Jun 94 12:55 EDT
Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id MAA04609; Thu, 9 Jun 1994 12:24:48 -0400
X-Resent-To: chassismib@CS.UTK.EDU ; Thu, 9 Jun 1994 12:24:47 EDT
Errors-to: owner-chassismib@CS.UTK.EDU
Received: from SynOptics.COM by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id MAA04602; Thu, 9 Jun 1994 12:24:45 -0400
Received: from donatello (donatello.synoptics.com) by SynOptics.COM (4.1/SMI-4.1) id AA10321; Thu, 9 Jun 94 09:22:28 PDT
Received: by donatello (4.1/2.0N) id AA12416; Thu, 9 Jun 94 09:22:29 PDT
Message-Id: <9406091622.AA12416@donatello>
Date: Thu, 09 Jun 1994 09:22:29 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Andrew Bierman <abierman@synoptics.com>
To: chassismib@cs.utk.edu, arneson@ctron.com
Subject: Re: Future

> Well another IETF is comming up on us.  I guess I would like to find
> out if there is interest in getting together to discuss where we are
> going with the chassis MIB.
> ...
> /David Arneson [arneson@ctron.com] [ (603)337-5238 ]
> 
I'm interested in a chassis MIB that provides:
   1) a good definition of a chassis
   2) an inventory of physical components in a chassis
   3) a fix for the "Repeater ID" problem
   4) an indication of the SNMP capabilities of each component 
      (i.e. pointers to MIBs, other agents in the chassis)
   5) a physical sub-component hierarchy

I hope you can get a BOF scheduled soon...

--andy;

v2.23.0 | Report a Bug | By Email