RE: proposal for OID root and branch assignments
Howard,
Why that root?
iso(1) member-body(2) us(840) ieee802dot3(10006) dot3dot1mibs(1)
When 802.1 repatriated their MIBs, we moved under the official IEEE-SA
OID arc. I would think 802.3 should do the same. So yours would be:
iso (1) iso-identified-organization (3) ieee (111)
standards-association-numbered-series-standards (2) lan-man-stds (802)
ieee802dot3(3) ieee802dot1mibs(1)
Cheers,
Glenn.
-----Original Message-----
From: stds-802-3-mib@xxxxxxxx [mailto:stds-802-3-mib@xxxxxxxx] On Behalf
Of Howard Frazier
Sent: Thursday, September 16, 2010 10:15 PM
To: STDS-802-3-MIB@xxxxxxxxxxxxxxxxx
Subject: proposal for OID root and branch assignments
Dear members of the IEEE 802.3.1 Ethernet MIB modules Task Force,
attached please find a proposal for the OID root and branch assignments
for the modules defined in IEEE P802.3.1. Our normal custom is to not
disclose these assignments until a project reaches the LMSC sponsor
ballot stage. Since that stage is rapidly approaching, we will need to
discuss this topic and reach agreement on the assignments when we meet
in Portland, OR next week.
This is a preliminary proposal, and subject to change.
The leaf assignments are already in the draft, and have not been changed
in the course of balloting, because we haven't added or removed any
objects.
Please review the proposal, and let me know what you think of it.
One item that might need further explanation is the addition of an OID
for "ieee8023efmcu". This node doesn't appear in the current draft. I
added it to the proposal so that I could branch the
"ieee8023ifCapStackMIB" and " ieee8023efmCuMIB" modules from it, both
modules being defined in Clause 11 of P802.3.1.
Howard Frazier
Broadcom Corporation
Chair, IEEE 802.3.1 Ethernet MIB modules Task Force