This Working Group did not meet
NOTE: This charter is a snapshot of the 56th IETF Meeting in San Francisco, California USA. It may now be out-of-date.
Last Modified: 2002-06-07
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.
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. |
RFC | Status | Title |
---|---|---|
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 |