documents in charter

Chuck Townsend <> Mon, 13 April 1992 12:52 UTC

Return-Path: <owner-chassismib>
Received: by CS.UTK.EDU (5.61++/2.8s-UTK) id AA20197; Mon, 13 Apr 92 08:52:57 -0400
Received: from by CS.UTK.EDU with SMTP (5.61++/2.8s-UTK) id AA20193; Mon, 13 Apr 92 08:52:54 -0400
Received: from by id aa25913; 13 Apr 92 8:52 EDT
Received: from king.ctron by (4.1/SMI-4.1) id AA13179; Mon, 13 Apr 92 08:47:40 EDT
Received: by king.ctron (4.1/SMI-4.1) id AA01848; Mon, 13 Apr 92 08:49:47 EDT
Date: Mon, 13 Apr 92 08:49:47 EDT
From: Chuck Townsend <>
Message-Id: <9204131249.AA01848@king.ctron>
Subject: documents in charter


   Below is the Chassis MIB Working Group Charter.  It seems as if
the goal scheduled "July 92" would be best achieved if attention
is given to documents (1) and maybe (2) before July.  I would
be in favor of spinning off separate working groups for documents
(2) and (3).  What are other people's thoughts on this subject?

	-Chuck Townsend

Chassis MIB (chassis)

     Bob Stewart  <>
     Jeffrey Case  <>
Mailing lists: 
     To Subscribe:

Description of Working Group:

This working group will produce a document describing MIB objects for
use in a "chassis" --- which is a collection of traditionally discrete
network devices packaged in a single cabinet and power supply. A
chassis may comprise, for example, combinations of layer 1 repeater
elements, MAC layer bridges, or internetwork layer routers.
The working group is chartered to produce up to three distinct
documents that define extensions to the SNMP MIB:
(1) The working group is chartered to define MIB objects that
represent the mapping of the logical functions of traditional network
devices onto particular, physical hardware resources within the
chassis. These MIB definitions will not address any aspects of the
network functions comprised by a chassis box that are shared with an
analogous collection of discrete network devices.
(2) The working group is chartered, at its option, to define MIB
objects that instrument the operational state of a power supply
element in a chassis.
(3) The working group is chartered, at its option, to define MIB
objects that represent aggregated information about collections of
network devices (e.g., aggregate information about devices attached to
a particular LAN), provided that this MIB specification is not
specific to chassis implementatons of such networks and is also
readily implementable for analogous collections of discrete network
The MIB object definitions produced will be for use by SNMP and will
be consistent with existing SNMP standards and framework.
Although the working group may choose to solicit input or expertise
from other relevant standards bodies, no extant standards efforts or
authorities are known with which alignment of this work is required.
Because the structure of chassis implementations varies widely, the 
working group shall take special care that its definitions reflect a 
generic and consistent architectural model of chassis management rather 
than the structure of particular chassis implementations.
Should the working group elect to define objects representing
aggregated information about collections of network devices, those
efforts will not compromise the operational robustness of the SNMP
that depends on its realization of management system function as
closely as possible to centers of responsible authority.

Goals and Milestones: 
     Mar 92 Discuss the charter and define the scope of the working group.  In 
            particular, review all contributed MIBs and agreement on plan for 
            producing baseline document(s).                                    

     Jul 92 Post the first draft of the Chassis MIB specification as an        
            Internet Draft.                                                    

     Jan 93 Submit the Chassis MIB to the IESG as a Proposed Standard.