Current Meeting Report
2.3.6 Ethernet Interfaces and Hub MIB (hubmib)
NOTE: This charter is a snapshot of the 53rd IETF Meeting in Minneapolis, MN USA. It
may now be out-of-date. Last Modified:
Dan Romascanu <email@example.com>
Operations and Management Area Director(s):
Randy Bush <firstname.lastname@example.org>
Bert Wijnen <email@example.com>
Operations and Management Area Advisor:
Bert Wijnen <firstname.lastname@example.org>
To Subscribe: email@example.com
In Body: subscribe your_email_address
Description of Working Group:
The Ethernet Interfaces and Hub MIB WG is Chartered to define
a set of managed objects that instrument devices, MAUs and
interfaces that conform to the IEEE 802.3 standard for Ethernet.
This set of objects should be largely compliant with, and even
draw from IEEE 802.3, although there is no requirement that any
specific object be present or absent.
Close coordination with hardware standards development in
IEEE 802.3 will be followed. The WG chair will support the
communication with IEEE 802.3. When objects are added that
require hardware support, IEEE 802.3 shall be informed,
so that they consider to add them to their draft/standard.
The MIB object definitions produced will be for use by SNMP and
will be adequately consistent with other SNMP objects, standards
The WG will define new MIB objects to cover the following 802.3
P802.3ae - 10 Gb/s Ethernet
P802.3af - DTE Power via MDI
Goals and Milestones:
|Done||  || Meet at the 41st IETF to discuss implementation experience of RFC 2108 and RFC 2239, and to consider future extensions for Full Duplex operation and 1 Gigabit Ethernet Speeds|
|Done||  || Gather implementation experience feedback concerning RFC 2108 and RFC 2239|
|Done||  || Post Internet-Draft(s) for Full Duplex and 1 Gigabit Ethernet MIB extensions|
|Done||  || Meet at the 42nd IETF to discuss the Internet-Draft(s) and issue recomendations concerning advancement of RFC 2108 and RFC 2239 on the standards track|
|Done||  || Post revised Internet-Draft(s)|
|Done||  || Conduct WG Last Call on Internet-Draft(s)|
|Done||  || Submit final version of the Internet-Draft(s) to the IESG for consideration as Proposed Standards|
|Done||  || Submit revised version of the Internet-Drafts, following the Area Directorate review|
|Done||  || Submit final versions of the MAU MIB and Ethernet-like Interfaces MIB Internet-Draft(s) to the IESG for consideration as Proposed Standards|
|Done||  || Submit the Ethernet Chipsets document to IESG for consideration as an Informational RFC|
|Done||  || Begin identifying new work items for future work|
|Done||  || Issue WG Drafts for MIBs for P802.3ae & P802.3af|
|Done||  || Issue revised WG Drafts for MIBs for P802.3ae/P802.3af|
|Dec 01||  || Gather implementation experience concerning WG documents already on the standards track|
|Jan 02||  || Issue revised WG drafts for existing stds track documents if so required by the implementation reports|
|Jan 02||  || Forward Internet-Drafts to the AD/IESG Stds track considerations|
|Jan 02||  || WG Last Call All documents|
Request For Comments:
|RFC1515||PS||Definitions of Managed Objects for IEEE 802.3 Medium
Attachment Units (MAUs)
|RFC2108||PS||Definitions of Managed Objects for IEEE 802.3 Repeater
Devices using SMIv2
|RFC2665||PS||Definitions of Managed Objects for the Ethernet-like
|RFC2666|| ||Definitions of Object Identifiers for Identifying
Ethernet Chip Sets
|RFC2668||PS||Definitions of Managed Objects for IEEE 802.3 Medium
Attachment Units (MAUs) using SMIv2
Current Meeting Report
MINUTES OF THE JOINT MEETING OF THE HUBMIB AND ATOMMIB WG
TUESDAY, March 19, 2002
1700-1800 Afternoon Sessions IV
INT atommib &OPS &hubmib AToM MIB WG & Ethernet Interfaces and Hub MIB WG
Chairs: Dan Romascanu - firstname.lastname@example.org, Faye Ly - email@example.com, Nathan Kohn - firstname.lastname@example.org
Introductions, Agenda bashing, Minutes Taker - 5 min
IEEE 802.3 status - Dan Romascanu - 10 min
WIS MIB Status and Open Issues Resolution - Mike Heard and KC Norseth - 30 min
Next Steps, How to complete WGs Charter - 15 min
Minutes taken by Randy Presuhn - email@example.com
There were no major changes to the proposed agenda for the joint atommib / hubmib meeting.
There was a update on the IEEE 802.3ae activity. Problems had been identified in the conformance clauses, and a new internal letter is planned. Draft 4.1 is in ballot, and draft 4.2 is hoped for by March 18, with an IEEE interim planned in
April and completion targeted for June, 2002. Fortunately, all major management-related comments have already been resolved.
The status report on the WIS (WAN Interface Sublayer)
MIB presented at the IEEE 803.2ae interim meeting indicated that the IEEE liked it, and that there was no contention surrounding the resolution of issues.
Recent changes include the addition of a new test pattern type, changing some flags to enumerations, and trace object alignment.
The editors of the WIS MIB are aware of a few edits that will be needed, and the plan is to wait for the 4.2 update from the IEEE, do a sanity check between the MIB and the GDMO definitions, then issue a working group last call on a document with an annex identifying known problems.
The document forwarded to the IESG will need to be "clean".
The WG last call will be done in the hubmib WG, but will also be announced on the atommib WG mailing list.
A review of RFC 2558 implementations from five different vendors showed that, when taken together, every object was supported by at least two implementations. The plan is to recommend the document for advancement from Proposed to Draft Standard.
The final discussion concluded that those present did not see a need for another joint meeting.
Joint Hubmib & Atommib Session