Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

RE: [802.3.1_MIBS] proposal for OID root and branch assignments



Dan,

ieeeefmcu is an exception because it isn't the root object of a single module.
Rather it is merely a node from which two modules are branched.

At the IEEE 802.3.1 Ethernet MIB modules Task Force meeting in Portland, OR,
we agreed to:

Change the  name of the root object in Clause 7 from ieee8023snmpRptrMod to
ieee8023snmpRptrMIB

Change the name of the root object in Clause 12 from ieee8023mauMod to ieee8023mauMIB

So now all of the names of the root objects will end in "MIB".

Howard Frazier
Chair, IEEE 802.3.1 Ethernet MIB modules Task Force

-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@xxxxxxxxx] 
Sent: Sunday, September 19, 2010 2:12 AM
To: Howard Frazier; STDS-802-3-MIB@xxxxxxxxxxxxxxxxx
Subject: RE: [802.3.1_MIBS] proposal for OID root and branch assignments

Question - why are the names of the MIB root objects inconsistent - i.e.
some end in MIB, a couple end in Mod and one has neither of the
suffices? 

Thanks and Regards,

Dan
 

> -----Original Message-----
> From: Howard Frazier [mailto:hfrazier@xxxxxxxxxxxx] 
> Sent: Friday, September 17, 2010 4:15 AM
> To: STDS-802-3-MIB@xxxxxxxxxxxxxxxxx
> Subject: [802.3.1_MIBS] 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
> 
> 
>