2.4.2 Bridge MIB (bridge)

NOTE: This charter is a snapshot of the 61st IETF Meeting in Washington, DC USA. It may now be out-of-date.

Last Modified: 2004-10-20

Chair(s):

Dan Romascanu <dromasca@avaya.com>
David Harrington <dbharrington@comcast.net>

Operations and Management Area Director(s):

Bert Wijnen <bwijnen@lucent.com>
David Kessens <david.kessens@nokia.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: http://www.ietf.org/mail-archive/web/bridge/index.html

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:

  • draft-ietf-bridge-bridgemib-smiv2-07.txt
  • draft-ietf-bridge-rstpmib-05.txt

    Request For Comments:

    RFCStatusTitle
    RFC1286 PS Definitions of Managed Objects for Bridges
    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

    IETF 61 – 11/9/04 Bridge MIB WG Minutes:

    Chairs: David Harrington, Dan Romascanu

    Agenda:

    • 5 min - Administrivia
    o Blue sheets
    o Minutes
    • 5 min - Agenda bashing
    • 20 min - WG Status Report
    • 20 min - Transition mibs to IEEE 802.1 WG
    • 5 min - Administrivia


    Agenda bashing

    WG status (see presentation Document Status ietf61.ppt)

    • No meetings planned for IETF 62, 63
    • No new work items will be accepted by the WG
    • With respect to the current documents in works, the consensus of the participants was that the documents will be submitted for consideration as Proposed Standards, with the currently included fixes to synchronize content with the evolution of the IEEE 802.1 standard – the issue will be taken to the list to verify consensus to the proposal of the participants in the meeting

    Transition to the IEEE 802.1 (see presentation Transition to IEEE 802.ppt)

    • The presentation will be also given in the next week IEEE 802.1 Plenary meeting
    • Question regarding the procedure of interacting with the IEEE 802.1 WG – IEEE process requires comments to be provided in a formal manner. In general, IETF participants will need to follow the design and comments process in the WG
    • MIB reviews guidelines are written with orientation for IETF documents – there is a need to ‘port’ some of the MIB review aspects to the IEEE. The WG chairs will contact the guidelines author on this issue
    • The IEEE 802.1 WG will accept advice from MIB advisors The IEEE 802.1 editors and MIB advisors will mediate on this respect

    Meeting adjourned – this may have been the last Bridge MIB WG meeting

    Slides

    Bridge WG Status Report
    IETF Bridge WG Transition to IEEE 802.1 WG