Entity mib views?

VisiSoft <70650.3316@compuserve.com> Thu, 15 April 1993 16:58 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10292; 15 Apr 93 12:58 EDT
Received: from CS.UTK.EDU by IETF.CNRI.Reston.VA.US id aa10288; 15 Apr 93 12:58 EDT
Received: from localhost by CS.UTK.EDU with SMTP (5.61+IDA+UTK-930125/2.8s-UTK) id AA12477; Thu, 15 Apr 93 12:19:08 -0400
X-Resent-To: chassismib@CS.UTK.EDU ; Thu, 15 Apr 1993 12:19:07 EDT
Errors-To: owner-chassismib@CS.UTK.EDU
Received: from ihc.compuserve.com by CS.UTK.EDU with SMTP (5.61+IDA+UTK-930125/2.8s-UTK) id AA12469; Thu, 15 Apr 93 12:19:03 -0400
Received: by ihc.compuserve.com (5.65/5.930129sam) id AA04526; Thu, 15 Apr 93 12:19:01 -0400
Date: 15 Apr 93 12:10:53 EDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: VisiSoft <70650.3316@compuserve.com>
To: chassismib@cs.utk.edu
MMDF-Warning: Parse error in original version of preceding line at IETF.CNRI.Reston.VA.US
Subject: Entity mib views?
Message-Id: <930415161053_70650.3316_EHD35-5@CompuServe.COM>

In section 5.3 of the draft, it indicates that the table defines means to
access a mib
view for each such entity and contains either party or community/address
information.
 
What is in such a mib view?
 
Is it the subchassis example you talk about elsewhere (where one chassis's
slots
refer to another chassis mib?)?  Something else?
 
Please respond directly to me at address in signature below, I am not on the
chassismib mailing list.
 
Thanks,
mlk@bir.com