IEEE Interim Meeting - WG Last Call for Power Ethernet MIB

"Romascanu, Dan (Dan)" <[email protected]>
Newsgroups gmane.ietf.hubmib
Message-ID <AAB4B3D3CF0F454F98272CBE187FDE2F017B749F@is0004avexu1.global.avaya.com>
I attended last week one of the sessions of the IEEE 802.3af (Power Ethernet) interim meeting. I gave a short presentation focused on a outline of the last Power Ethernet MIB, which is now in WG Last Call. I received several comments which I would like to bring to the attention of the WG, and be considered as comments to the last call. At the same time I would like to re-iterate the invitation made to the IEEE 802.3af participants to have another read of the document (http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubmib-power-ethernet-mib-04.txt) and send their comments to [email protected]. The Last Call expires in two days.

Here are the IEEE folks comments:

1. Align the enumerated names for pethPsePortPowerPairs with the terminology used in the IEEE draft - alternativeA, alternativeB instead of spare, signal.
2. The capability to performed control of detection has been removed of the mandatory clauses of the IEEE standard, thus the object pethPsePortPowerDetectionControl should be removed.
3. The state test(7) in pethPsePortDetectionStatus needs to be removed
4. Typo in the enumerated of pethPsePortPowerMaintenanceStatus - it is meant to be overCurrent, and not underCurrent
5. Recommend a separate conformance clause for pethMainPseTable, which is a 'high-end' feature
6. For power management, it was suggested that the usage threshold comparison be made not with the measured, but rather with the consumption-based estimated usage, as devices may have a temporary usage below the power allowed by their class. 

After the meeting I learnt about another important change, which will impact the MIB:
7. The PD group is no longer mandatory - this actually means that the pethPfPortTable can be taken out of the MIB
Regards,

Dan
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.