[Hubmib] EPON MIB document - alignment in the enumerations of the dot3Epon FecAbility object to the equivalent IEEE802.3 attribute

Hi all,
In the EPON MIB document (draft-ietf-hubmib-efm-epon-mib-06.txt) there is a mismatch in the dot3EponFecAbility enumerations to the equivalent IEEE802.3 attribute.

dot3EponFecAbility OBJECT-TYPE
    SYNTAX  INTEGER {
             unknown(1),
             unsupported(2),
             supported(3)

In the IEEE spec the equivalent attribute has a different order:

30.5.1.1.13 aFECAbility
ATTRIBUTE
APPROPRIATE SYNTAX:
A ENUMERATION that meets the requirement of the description below
unknown           initializing, true state not yet known
supported          FEC supported
not supported    FEC not supported

The document is in the AUTH48 stage in the RFC editing queue.
Although the document is in it's very final stages I think it be better fixed. It was brought into my attention by some of the implementers of the MIB asking for the change and it has a lot of sense in keeping the same enumerations to avoid possible confusion in different implementations.
The proposed change in the EPON MIB is:

  dot3EponFecAbility OBJECT-TYPE
     SYNTAX  INTEGER {
              unknown(1),
              unsupported(2),
              supported(3)

to be changed to:

  dot3EponFecAbility OBJECT-TYPE
     SYNTAX  INTEGER {
              unknown(1),
              supported(2),
              unsupported(3)

If there is any objection to this action please respond to this mail.
So unless there is any objection to this change by let's say the 10th of April, I will proceed with the action.

Sorry for the late change,

Best regards,
Lior

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib