Re: [MIB-DOCTORS] Questions on IEEE published mib modules vs IETF
Michael MacFaden <[email protected]> Wed, 17 Aug 2011 10:16:04 -0700
| Newsgroups | gmane.ietf.hubmib |
|---|---|
| Message-ID | <CAD3a8T=HEcLKf6HNmY2WxADVypQFfeQc9+mGt2fJHtYFQ5WhwQ@mail.gmail.com> |
On Wed, Aug 17, 2011 at 8:36 AM, Romascanu, Dan (Dan) <[email protected]> wrote: > There is no equivalent of the IETF maturity levels in the IEEE. There is > just one level of standards, and there is a re-affirmation process that > needs to happen every five years, unless the standard was updated > sooner. Ok, that's good to know. Unfortunately there is no README.txt file at this URL http://www.ieee802.org/1/files/public/MIBs to describe when files are posted here at what part of the standards process this is/such as being up for reaffirmation. Am going to the pdf's just to make sure. > The MIB modules defined in RFC 3635 and RFC 4836 (and a few more) are in > the scope of IEEE 802.3.1 which was approved as an IEEE standard a few > months ago. We entertained a discussion at and around the Quebec meeting > and decided to mark the RFCs as obsolete by the IEEE standards and point > to these, but not transit them to Historic (not yet in any case). Bert > will write when he gets some time a short Informational RFC to document > this transition. Makes sense to me, have already started using IEEE8021-BRIDGE-MIB, IEEE8021-Q-BRIDGE, and others in products so would prefer new to use correct IEEE versions when they become available. Thanks again, Mike MacFaden