Bridge MIB (bridge)
Last Modified: 2005-06-21
Chair(s):
Operations and Management Area Director(s):
Operations and Management Area Advisor:
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-mib/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. |
| Done |
|
Submit new I-D for RFC 1493 in SMIv2 form |
| Done |
|
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 |
| Done |
|
Evaluate status of RFC 2674 an get WG consensus if it should be
recycled at Proposed or can be elevated to Draft Standard |
| Done |
|
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 |
| Done |
|
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. |
| Done |
|
Submit SMIv2 version of RFC 1493 to IESG fo consideration as
Full Standard. |
| Done |
|
Submit completed draft(s) with MIB support for extensions to
802.1w to the IESG, for consideration as a Proposed Standard. |
| Done |
|
Submit RFC 2674 (or new I-D if clarifications had to be made)
to IESG for consideration as Draft Standard |
No Current Internet-Drafts
Request For Comments:
Definitions of Managed Objects for Bridges (RFC 1286) (79104 bytes)
obsoleted by RFC 1493,RFC 1525
Definitions of Managed Objects for Bridges (RFC 1493) (74493 bytes)
obsoletes RFC 1286/
obsoleted by RFC 4188
Definitions of Managed Objects for Source Routing
Bridges (RFC 1525) (38100 bytes)
obsoletes RFC 1286
Definitions of Managed Objects for Bridges with Traffic
Classes, Multicast Filtering and Virtual LAN Extensions (RFC 2674) (159971 bytes)
obsoleted by RFC 4363
Definitions of Managed Objects for Bridges (RFC 4188) (86877 bytes)
obsoletes RFC 1493
Definitions of Managed Objects for Bridges with Rapid
Spanning Tree Protocol (RFC 4318) (28124 bytes)
Definitions of Managed Objects for Bridges with Traffic
Classes, Multicast Filtering and Virtual LAN Extensions (RFC 4363) (188981 bytes)
obsoletes RFC 2674
