2.4.3 Bridge MIB (bridge)

NOTE: This charter is a snapshot of the 43rd IETF Meeting in Orlando, Florida. It may now be out-of-date. Last Modified: 25-Nov-98


Keith McCloghrie <kzm@cisco.com>

Operations and Management Area Director(s):

Harald Alvestrand <Harald.Alvestrand@maxware.no>
Bert Wijnen <wijnen@vnet.ibm.com>

Operations and Management Area Advisor:

Bert Wijnen <wijnen@vnet.ibm.com>

Mailing Lists:

General Discussion:bridge-mib@external.cisco.com
To Subscribe: bridge-mib-request@cisco.com
Archive: ftp://ftpeng.cisco.com/ftp/kzm/bridgemib/list-archive

Description of Working Group:

The Bridge MIB Working Group is chartered to define a set of managed objects that instrument devices that conform to the IEEE 802.1 standard for MAC-layer bridges.

This set of objects should be largely compliant with (and even draw from) IEEE 802.1(b), although there is no requirement that any specific object be present or absent.

The MIB object definitions produced will be for use by SNMP and will be consistent with other SNMP objects, standards, and conventions.

Goals and Milestones:



Publish initial proposal.



Submit an Internet-Draft.



Submit draft for RFC publication.



Publish a draft SNMP MIB that instruments functions specific to source routed bridges as an Internet-Draft.



Publish a draft revision to RFC 1286 that reflects implementation experience and the result of alignments with IEEE work as an Internet-Draft.



Submit a draft MIB for source routing bridge functions to the IESG for consideration as a Proposed Standard.

Aug 98


Evaluate status of RFC 1493 and report to the IESG if it should be recycled at Draft or can be elevated to Full Standard.

Aug 98


Evaluate status of RFC 1525 and report to the IESG if it should be recycled at Proposed or can be elevated to Draft Standard.

Jan 99


Submit a new MIB document with support for recently developed 802.1 specifications to the IESG for consideration as a Proposed Standard.


Request For Comments:







Definitions of Managed Objects for Bridges



Definitions of Managed Objects for Source Routing Bridges

Current Meeting Report

Bridge-MIB Meeting Minutes - 43rd IETF Plenary, Orlando, 9812

The meeting was chaired by Keith McCloghrie, cisco Systems.


New Issue [81] - David Melman has raised on the mailing list, the need for a "MustGoTo" equivalent to dot1qStaticUnicastAllowedToGoTo. This was previously discussed as part of issue 55, when the group did not accept the need to add another port list for "MustGoTo". Again, there was no support from the group to add another port list. The consensus was to leave the MIB as it is, with Andrew Smith to provide a clarification in the description of dot1qStaticUnicastAllowedToGoTo, for the case where a single bit is set, saying this is equivalent to "MustGoTo".

Issue [80] - Andrew Smith proposed specific text for two options for dot1qTpVlanPortInDiscards, saying this includes: (a) Discard Inbound and Discard On Ingress Filtering; or (b) Discard On Ingress Filtering as well as counters on egress filtering and Acceptable Frame Type that are not specified by IEEE 802.1Q. The group was concerned about defining counters not required by 802.1Q, even though this was probably just an omission from 802.1Q and it may corrected in the next revision to the standard. The first of Andrew's options was accepted, with a minor modification, as follows:

DESCRIPTION - The number of valid frames received by this port from its segment which were classified as belonging to this VLAN which were discarded due to VLAN-related reasons. Specifically, the IEEE 802.1Q counters for Discard Inbound and Discard on Ingress Filtering.

New Issue [82] - dot1qLearningConstraintsTable should be read-create only, not read-write. Editorial change only.

New Issue [83] - Should not reset counters when dot1dGmrpStatus and dot1qGvrpStatus is enabled. Remove text for "zeroing counters" for both. For GMRP, we need a read-only per VLAN "UpTime", in dot1qVlanCurrentTable. Also, fix names of dot1qVlanCurrentTable objects, for consistency.

The changes, described above, are to be mailed to the WG, and agreed before the next Internet-Draft is published, before Christmas, which will go to WG Last Call. It is expected to be able to submit the next draft for standardisation in mid to late January, 1999.

Proposed New Work item:

There has been a request on the mailing list to look at new work defining support for IEEE 802.1G Remote Bridging, from peter@aus.atmospherenet.com. No other members of the group expressed any interest in this work, so the group will not be pursuing it.


Bridge MIB Extensions - Open Issues