hubmib-2----Page:21
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41
|
Comments – Dan Romascanu 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?) |