This maintenance request has been entered in response to message [802.1 - 10573] on the IEEE 802.1
email reflector from Mark van Tol (mtol@AIMVALLEY.NL). Paraphrased, he states
1. The first issue looks like the following old issue:
http://www.ietf.org/mail-archive/web/bridge-mib/current/msg00194.html
2. The second issue causes the MIB validation tool (SimpleWeb) to give a severity level 5 warning
on this : "implicit node definition". Using "ieee802dot3" instead of "802dot3" (like in old MIB) solves this.
This looks to be an old issue described in http://www.psg.com/lists/ietfmibs/ietfmibs.2003/msg00193.html
There is a long history with these changes. The originally approved MIB from 802.3ad-2000 used the 0..255 range.
However when this was rolled into the next revision of 802.3, this was changed (without voting or approval as far
as I can tell) to 0..65536. Quite a few other changes were made at the same time, and the resulting MIB
(which eventually ended up in 802.1AX-2008) does not compile. When we were preparing 802.1AXbk (Link
Aggregation Addressing Amendment) we balloted and made changes to that MIB, undoing the changes made when
it was rolled into 802.3, on the basis that it was invalid because the changes in the rolled-up 802.3 standard
"should not have been made". These changes are described in detail in the editor's forward notes to 802.1AXbk
draft 1.2 (which can be seen in this draft: http://www.ieee802.org/1/files/private/axbk-drafts/d1/802-1AXbk-d1-3.pdf).
However it may be that some of the changes we made at that time were ill-advised.