2.4.4 Bridge MIB (bridge)

NOTE: This charter is a snapshot of the 51st IETF Meeting in London, England. It may now be out-of-date. Last Modified: 31-Jul-01

Chair(s):

Les Bell <les_bell@3com.com>

Operations and Management Area Director(s):

Randy Bush <randy@psg.com>
Bert Wijnen <bwijnen@lucent.com>

Operations and Management Area Advisor:

Bert Wijnen <bwijnen@lucent.com>

Mailing Lists:

General Discussion:bridge-mib@ietf.org
To Subscribe: bridge-mib-request@ietf.org
In Body: subscribe your_email_address
Archive: ftp://ftp.ietf.org/ietf-mail-archive/bridge/

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 standards for MAC-layer bridges.

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

The set of objects should not duplicate, nor conflict with any MIB object definitions defined by the IEEE 802.1 standards themselves.

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:

Done

  

Publish initial proposal.

Done

  

Submit an Internet-Draft.

Done

  

Submit draft for RFC publication.

Done

  

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

Done

  

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

Done

  

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

Done

  

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

Jul 01

  

Submit new I-D for RFC 1493 in SMIv2 form

Jul 01

  

Submit new I-D for RFC 1525 in SMIv2 format

Aug 01

  

Evaluate status of RFC 1493 and the SMIv2 versio and get WG consensus if it should be recycled a Draft or can be elevated to Full Standard

Aug 01

  

Evaluate status of RFC 1525 and the SMIv2 versio and get WG consensus if it should be recycled a Draft or can be elevated to Full Standard

Aug 01

  

Evaluate status of RFC 2674 an get WG consensus if it should be recycled at Proposed or can be elevated to Draft Standard

Aug 01

  

Submit an Internet-Draft (or drafts) with MI support for extensions to the Bridge standards defined in 802.1t, 802.1u, 802.1v and 802.1w

Sep 01

  

Submit SMIv2 version of RFC 1493 to IESG fo consideration as Full Standard.

Sep 01

  

Submit SMIv2 version of RFC 1525 to IESG fo consideration as Full Standard.

Sep 01

  

Submit RFC 2674 (or new I-D if clarifications had to be made) to IESG for consideration as Draft Standard

Dec 01

  

Revise the Internet-Draft(s) with MIB support for extensions to the Bridge standards defined in 802.1t, 802.1u, 802.1v and 802.1w.

Mar 02

  

Submit completed draft(s) with MIB support for extensions to 802.1w to the IESG, for consideration as a Proposed Standard.

Internet-Drafts:
Request For Comments:

RFC

Status

Title

RFC1493

DS

Definitions of Managed Objects for Bridges

RFC1525

PS

Definitions of Managed Objects for Source Routing Bridges

RFC2674

PS

Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN Extensions

Current Meeting Report

Meeting minutes for the Bridge MIB WG, 51st IETF

Tuesday August 7, 2001, 1700

1.) Overview

There are three drafts in progress.

Bert W.: Currently the chair is authoring documents. Can we get co-editors?

John Flick & K.C. Norseth volunteered.

RFCs 1493, 1525, & 2674 need to progress. RFCs 1493 & 1525 are being updated to SMIv2.

There are some new 802.1 MIBs

Implementation reports are needed for RFCs:
1493 - currently draft
1525 - currently proposed
2674 - currently proposed
Please submit implkementation reports! If you do not wish to submit your report to the group at large, you may submit privately to Les or Bert (addresses?)

2.) SMIv2 Bridge MIB Draft

draft-ietf-bridge-bridgemib-smiv2.txt

This is a direct translation of RFC1493 into SMIv2. However, a few issues have arisen:

a.) The object dot1dBasePortIfIndex should be of type InterfaceIndex, but is currently Integer32.

Bert W.: We can progress the IF MIB and use InterfaceIndex.

Les: We should also change "traps" to "notifications" in a comment.

All: OK

b.) There are still problems with logical link aggregation.

c.) Is dot1dStdPortEnable redundant?

Mike A.: No, a port may not have a unique ifIndex.

dot1dStdPortEnable remains.

d.) Some (many?) implementations permit spanning tree to be turned off an a per-port basis. Should we standardize this?

Many questions were raised about why this would be done and what the default behavior could be. The group sought a rationale for doing this, but could not find one. Therefore no action will be taken.

e.) Should we add an object to give the time of last change for dot1dBasePortTable?

Mike A.: Why make a change like this now?

Bert W.: We would have to recycle.

Les: Does anyone think that we should do this?

(silence).

f.) Smilint complained about some notification definitions.

3.) SMIv2 Source Routing Bridge MIB Draft

Another direct translation of an SMIv1 MIB.

No comments have been received yet. Is anyone using the source routing bridge MIB anymore?

Bert W.: Why advance what nobody is currently implementing?

(name?): This is like the FDDI MIB, which needs no advancement.

4.) 802.1 Standards

802.1w - Rapid reconfiguration
802.1t - Update to 802.1d
802.1u - Update to 802.1q
802.1v - VLAN classification by port/protocol

802.1 documents are available at
http://grouper.ieee.org/groups/802/1/index.html,
username: p8021
password: go_wildcats

5.) New MIBs

Rapid Spanning Tree Protocol MIB (RSTPMIB):

Involves changes to the bridge MIB. We don't need to change the syntax, but there may be interoperability issues.

U-bridge MIB:

Only one new item. This can be merged with 2674.

John F.: Can we merge all new MIBs with 2674?

Mike A.: If we merge them, will we just split them out again?

6.) 802.1 Standards, part 2

Updates on 802.1t, 802.1w, 802.1u, 802.1v, and 802.1s (per-VLAN spanning trees)

For 802.1x, IEEE wrote their own MIB - should we publish it as an informational RFC?

Bert W.: Do we want to?

Mike A.: We would then have all the bridge docs in one place.

Les: 802.1x is not just a bridge.

Bert W.: Then we'd best take this to the mailing list.

7.) Close

A.) Action Items

Mike A.: Write up explanation of the port/ifIndex issue for the list.

_______________________________________________
Bridge-mib mailing list
Bridge-mib@ietf.org
https://www1.ietf.org/mailman/listinfo/bridge-mib

Slides

Agenda