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

Please find below my comments wrt. draft-ietf-hubmib-efm-epon-mib-00.txt.

Regards,

Dan

A. Technical

A1. It is recommended to use Integer32 or Unsigned32 rather than INTEGER for objects which indicate an integer value, with the exception of enumeration objects.

A2. unknown object identifier label `dot3EfmeponMIB' in the first MIB module.

A3. There is a left-over bracket in the definition of eponDeviceObjectOnuLoopback which prevents correct compilation of the MIB module. 

A4 It would be very useful to add a section defining the relationship between the objects in this MIB and the management objects defined in IEEE 802.3 ah

A5. The MIB content needs to be aligned with the latest IEEE 802.3ah draft (3.1?)




B. Editorial - major

B1. The formatting instructions have not been followed in a manner consistent with other Internet-Drafts. For example - left side alignment of text

B2. Each MIB module should be contained in one document section or subsection and not be divided in subsections.

B3. There should be both a copyright notice at the beginning of the document, and a copyright section at the end of the document.

B4. The abstract section should not include references

B5. The Security section needs to include the complete and explicit list of writeable objects, not only examples.







C. Editorial - minor

C1. Expiration date is typically six month after publication. There is no reason to take an earlier date.

C2. WG Chair affiliation needs to be changed from Avaya Inc. to Avaya