Re: [ minutes]

Bob Stewart <> Wed, 14 April 1993 19:49 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa01978; 14 Apr 93 15:49 EDT
Received: from CS.UTK.EDU by IETF.CNRI.Reston.VA.US id aa01974; 14 Apr 93 15:49 EDT
Received: from localhost by CS.UTK.EDU with SMTP (5.61+IDA+UTK-930125/2.8s-UTK) id AA14732; Wed, 14 Apr 93 15:14:07 -0400
X-Resent-To: chassismib@CS.UTK.EDU ; Wed, 14 Apr 1993 15:14:06 EDT
Errors-To: owner-chassismib@CS.UTK.EDU
Received: from by CS.UTK.EDU with SMTP (5.61+IDA+UTK-930125/2.8s-UTK) id AA14724; Wed, 14 Apr 93 15:14:03 -0400
Received: by id <>; Wed, 14 Apr 93 14:14:38 -0500
Date: Wed, 14 Apr 1993 14:14:38 -0500
Message-Id: <>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Bob Stewart <>
In-Reply-To: {3COM/PDD/PeteW}'s message of Wed, 14 Apr 93 08:51 PDT <930414.010135@3Mail.3Com.COM>
Subject: Re: [ minutes]

In response to Pete's comments, with an addition from my own memory, and in
the interest of capital letters, here's my edit of Marshall's minutes for your



Minutes of the Chassis MIB WG
April 1, 1993
Chairs: Jeff Case, Bob Stewart
Scribe: Marshall Rose

1. Agenda approved.

2. Current draft is dated Jan 27, 1993.

3. Dave Arneson presented a revised model for the Chassis MIB.  It consists of
three kinds of things within a chassis - modules, resources, and entities.
Each resource is used to build up a single module; independently each resource
is used to build up a single entity.  The first relationship is used to
describe the physical location of a resource.  The second relationship is used
to describe the logical functional unit for management access.

There are three primary tables in the model:
    - a module table indexed by location type and slot number.
    - a resource table indexed by loc-type, slot-#, and resource-#.
    - a entity table indexed by entity number.

There was some discussion that the resource table should be two logical
tables: one indexed by module info, and the other indexed by entity info.

There was general consensus that the model is an improvement, and reasonably

There was a discussion of whether we are modeling chassis configuration or
network topology.  The general consensus seemed to be that network topology is
a general problem and is not part of our requirement.

A remaining question was what access information is necessary for v1 and v2.

4. Rick Royston discussed implementation experience.  He was concerned that
indexing was difficult, but thought that the new model would help.  He was
also concerned about keeping the mgmt application informed when the chassis
configuration changed.  Finally, there was concern about dynamic rules for
what card is allowed to go in which slots.

5. Actions:
    - Working group members are to apply the model to their own devices and
      report back.
    - Pete Wilson is to provide a set of examples.
    - Dave Arneson to revise draft based on model.
    - Jeff Case and Marshall rose to investigate entity access information.