RE: proposal for OID root and branch assignments
Glenn and Geoff,
We discussed this in the 802.3.1 Ethernet MIB modules
Task Force meeting. There was no objection to using the root:
iso (1) iso-identified-organization (3) ieee (111)
standards-association-numbered-series-standards (2) lan-man-stds (802)
ieee802dot3(3) ieee802dot3dot1mibs(1)
provided that the parent OID for 802.3:
iso (1) iso-identified-organization (3) ieee (111)
standards-association-numbered-series-standards (2) lan-man-stds (802)
is added to the OID repository at http://www.oid-info.com/
Currently, it is not there. In fact, there seems to be quite a
bit of information missing from the OID repository for this branch.
iso(1) identified-organization(3) 111
is described as:
SMPTE 298M Universal Labels for Unique Identification of Digital Data an ISO/ITU based identifier hierarchy registration system. Display Requirements: None Description of organizations covered by the coding system: IEEE, including RAC (registration authority committee) and other sub-entities Notes on use of the code: Primary application is SMPTE 298M Universal Labels. Other applications may also be supported. Additional comments: None
and
iso(1) identified-organization(3) 111 2 [or 1.3.111.2]
is not described in the repository, nor are any of its child OIDs
This was one of the reasons that I proposed using:
iso(1) member-body(2) us(840) ieee802dot3(10006) dot3dot1mibs(1)
At least the parent OID is already known to the OID repository.
It would seem that there needs to be a series of actions taken to update the OID
repository. It seems that ISO needs to update the repository entry
for 1.3.111 to make the IEEE more prominent. Then the IEEE RA needs to update the
repository to add a description of 1.3.111.2 (and the other OIDs it is responsible
for). The LMSC needs to add a description of 1.3.111.2.802, and the 802.3
WG needs to add a description of 1.3.111.2.802.3, and then the MIB modules
Task Force can add a description of 1.3.111.2.802.3.1.
Note that 1.3.111.2.802.1 doesn't have a description in the OID repository
either.
Howard Frazier
Chair IEEE 802.3.1 Ethernet MIB modules Task Force
-----Original Message-----
From: Glenn Parsons [mailto:gparsons@xxxxxxxxxx]
Sent: Sunday, September 19, 2010 5:27 PM
To: Howard Frazier
Cc: STDS-802-3-MIB@xxxxxxxxxxxxxxxxx; glenn.parsons@xxxxxxxxxxxx
Subject: 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