Re: [eman] A single OID for energy and the 3 EMAN MIBs (message to draft-ietf-eman-battery-mib authors)

Hi Jürgen, MIB doctors,

Jürgen,
I wish you had reacted when this email was posted: 
http://www.ietf.org/mail-archive/web/eman/current/msg02064.html, or 
during the WG meeting where it was discussed (too bad that the meeting 
minutes didn't cover that level of details).

While I understand that assigning a MODULE-IDENTITY descriptor could be 
problematic, here it's different: this unique MODULE-IDENTITY descriptor 
is for related MIB modules, and this happens to be a WG in this case.
We have 3 MIB documents containing 5 MIB modules, all related to Energy:
     2 are for Textual Conventions
     3 are interconnected: the second and third ones require some 
objects to be implemented in the first one.

MIB doctors,
Let us know your advice

Regards, Benoit

> Hi,
>
> in the past such registration spaces led to problems (I think RMON was
> the case) and I think because of that we moved pretty much all
> registrations below mib-2 and transmission. Bert Wijnen might recall
> the details. If we change our strategy, we should probably have strong
> reasons and understand the longer term implications. There is the relvant
> quote from RFC 4181:
>
>     - The value assigned to the MODULE-IDENTITY descriptor MUST be unique
>       and (for IETF standards-track MIB modules) SHOULD reside under the
>       mgmt subtree [RFC2578].  Most often it will be an IANA-assigned
>       value directly under mib-2 [RFC2578], although for media-specific
>       MIB modules that extend the IF-MIB [RFC2863] it is customary to use
>       an IANA-assigned value under transmission [RFC2578].  In the past,
>       some IETF working groups have made their own assignments from
>       subtrees delegated to them by IANA, but that practice has proven
>       problematic and is NOT RECOMMENDED.
>
> /js
>
> On Fri, Dec 13, 2013 at 11:31:23PM +0100, Benoit Claise wrote:
>> Dear all,
>>
>> During the last IETF meeting, there was an agreement to go for a
>> single energyMIB OID under mib-2.
>>
>> energyObjectContextMIB MODULE-IDENTITY
>> (draft-ietf-eman-energy-aware-mib) is under energyMIB.1
>> ianaEnergyRelationMIB MODULE-IDENTITY
>> (draft-ietf-eman-energy-aware-mib) is under energyMIB.2
>> energyObjectMIB MODULE-IDENTITY
>> (draft-ietf-eman-energy-monitoring-mib) is under energyMIB.3
>> powerAttributesMIB MODULE-IDENTITY
>> (draft-ietf-eman-energy-monitoring-mib) is under energyMIB.4
>>
>> For draft-ietf-eman-battery-mib, you can start with energyMIB.5
>> Note that draft-ietf-eman-energy-aware-mib requests:
>>
>>             Descriptor                      OBJECT IDENTIFIER value
>>             ----------                      -----------------------
>>
>>             energyMIB                         { mib-2 XXX }
>>
>>
>> Btw, both draft-ietf-eman-energy-aware-mib and
>> draft-ietf-eman-energy-monitoring-mib are ready for WGLC.
>>
>> Regards, Benoit
>>
>>
>> _______________________________________________
>> eman mailing list
>> eman@ietf.org
>> https://www.ietf.org/mailman/listinfo/eman