RE: EPON MIB document - alignment in the enumerations of the dot3EponFecAbility object to the equivalent IEEE802.3 attribute

Thanks Lior, for bringing this to the attention of the WG and the IESG.

I think this change (even at this late point in the process) makes
sense.
It is a somewhat technical change, so we need to make sure the WG=20
(and IESG) are OK with it.

Thanks for also copy-ing the IEEE 802.3 chair and vice-chair. I would
appreciate if they can also let us know if this change indeed makes
sense as we (Lior and I) think.

Therefor, (speaking as WG chair), I ask that HUBMIB WG members do indeed

speak up BEFORE April 10th if they see any issue with this proposal.

If nobody speaks up, then we will ask our AD to approve the change.

Bert Wijnen
HUBMIB WG chair.

> -----Original Message-----
> From: Lior Khermosh [mailto:[email protected]]=20
> Sent: dinsdag 3 april 2007 9:31
> To: '[email protected]'
> Cc: '[email protected]';=20
> '[email protected]'; '[email protected]';=20
> '[email protected]'; Wijnen, Bert (Bert);=20
> '[email protected]'; '[email protected]'
> Subject: EPON MIB document - alignment in the enumerations of=20
> the dot3EponFecAbility object to the equivalent IEEE802.3 attribute
>=20
> Hi all,
> In the EPON MIB document=20
> (draft-ietf-hubmib-efm-epon-mib-06.txt) there is a mismatch=20
> in the dot3EponFecAbility enumerations to the equivalent=20
> IEEE802.3 attribute.
>=20
> dot3EponFecAbility OBJECT-TYPE
>     SYNTAX  INTEGER {
>              unknown(1),
>              unsupported(2),
>              supported(3)
>=20
> In the IEEE spec the equivalent attribute has a different order:
> =20
> 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
>=20
> 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=20
> be better fixed. It was brought into my attention by some of=20
> the implementers of the MIB asking for the change and it has=20
> a lot of sense in keeping the same enumerations to avoid=20
> possible confusion in different implementations.
> The proposed change in the EPON MIB is:
>=20
>   dot3EponFecAbility OBJECT-TYPE
>      SYNTAX  INTEGER {
>               unknown(1),
>               unsupported(2),
>               supported(3)
>=20
> to be changed to:
>=20
>   dot3EponFecAbility OBJECT-TYPE
>      SYNTAX  INTEGER {
>               unknown(1),
>               supported(2),
>               unsupported(3)
>=20
> 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=20
> the 10th of April, I will proceed with the action.
>=20
> Sorry for the late change,
>=20
> Best regards,
> Lior
>=20