Comments on draft-ietf-hubmib-efm-mib-00.txt

Here are my comments concerning draft-ietf-hubmib-efm-mib-00.txt.

Regards,

Dan

A. Technical

A1. The content of the MIB and all references need to be updated with the changes in IEEE 802.3 D3.1

A2. if row creation in dot3OamTable is automatic, there is no need for the dot3OamRowStatus object

A3. Need to specify what objects need to be stored in non-volatile memory in tables

A4. dot3OamMode has a MAX-ACCESS of read-write - thus it needs a default value at initialization

A5. If row creation in dot3OamPeerTable is automatic, there is no need for the dot3OamPeerRowStatus object

A6. Should not we add a timer that would limit the time between dot3OamLoopbackCommand sending a loopback OAMPDU with the loopback enable flags set and reset. The motivation is to avoid cases when the second command may be lost.


B. Editorial - major

B1 - There are still formatting problems, especially concerning the maximum number of characters per line. Such problems in the MIB definition section do not allow for clean compilation of the text as it is in the draft. 

B2. - The Formatted references section, besides being incomplete does not include all the documents required by the boilerplate. See http://www.ops.ietf.org/mib-boilerplate.html. Also missing are the other two EFM MIB documents referenced in Section 3.

B3. Missing - copyright notice on the front page. Also, the year needs to be updated in the copyright notice in Section 11.





C. Editorial - minor

C1. Make sure that the data in the REVISION clause is identical with the date in the adjoining comment

C2. DESCRIPTION clause of dot3OamTable - what does 'primary' mean?

C3. in DESCRIPTION clause of dot3OamEventConfigTable, first phrase, specify that we deal with OAM notifications, to avoid the confusion with SNMP notifications.

C4. The DESCRIPTION clauses of the event groups in the conformance section seem to be identical one with the other.