FDDI MIB Working Group Minutes

case@snmp.com Wed, 28 July 1993 16:48 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08359; 28 Jul 93 12:48 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa08354; 28 Jul 93 12:48 EDT
Received: from CS.UTK.EDU by CNRI.Reston.VA.US id aa19908; 28 Jul 93 12:48 EDT
Received: from localhost by CS.UTK.EDU with SMTP (5.61+IDA+UTK-930125/2.8s-UTK) id AA16438; Wed, 28 Jul 93 12:28:17 -0400
X-Resent-To: fddi-mib@CS.UTK.EDU ; Wed, 28 Jul 1993 12:28:16 EDT
Errors-To: owner-fddi-mib@CS.UTK.EDU
Received: from seymour4.snmp.com by CS.UTK.EDU with SMTP (5.61+IDA+UTK-930125/2.8s-UTK) id AA16429; Wed, 28 Jul 93 12:28:14 -0400
Received: by seymour4.snmp.com (5.61++/2.8s-SNMP) id AA07315; Wed, 28 Jul 93 12:28:06 -0400
Date: Wed, 28 Jul 93 12:28:06 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: case@snmp.com
Message-Id: <9307281628.AA07315@seymour4.snmp.com>
To: minutes@CNRI.Reston.VA.US
Subject: FDDI MIB Working Group Minutes
Cc: fddi-mib@cs.utk.edu

        Minutes of the FDDI MIB Working Group  July 15, 1993

The FDDI MIB Working Group met on Thursday, July 15, 1993, at the 27th Meeting
of the Internet Engineering Task Force, in Amsterdam, the Netherlands.

The status of the current MIB draft was discussed.  It is progressing through
the Last Call, Directorate review, and IESG review with few comments, none
of which are substantive; all are editorial in nature.  If all continues as
anticipated, the document will soon become an RFC with Proposed Standard

RFC 1285 will continue to be a Proposed Standard for management of ANSI 6.2
based FDDI network devices; the new RFC will be for the mamagement of ANSI 7.x
based FDDI network devices.  RFC 1285 will expire at some point in the future
but does not need to be dealt with at this time.

The majority of the (short) meeting time was devoted to consideration of 
the trap document.  In a repetition of history (Atlanta IETF, July 30, 1991),
the net result was that there is no need for a trap document.  One reason for
this is the observation that the Alarms Group of the RMON MIB can be
implemented in the RMON device and thereby provide all of the functions
of all of the event notifications contained in the ANSI document.  The Working
Group decided at the Columbus meeting that there would need to be standard
mechanisms for enabling, disabling, and rate controlling any traps to be
generated.  Since the RMON MIB provides all of these capabilities and is
already progressing on the Standards track, the group concluded that there is
no need for additional work on traps.

Consequently, the work of the Working Group is finished, having concluded its
charter.  Members should anticipate the Working Group going dormant in the near
future, to be re-chartered when there are new work items.

Jeff Case