RE: I-D ACTION:draft-ietf-bridge-8021x-02.txt

The changes to the MIB for IEEE 802.1aa include the corrections in
draft-ietf-bridge-8021x-02.txt.

There are also some other significant changes to be done for 802.1aa, due to
recent changes in the state machines and the managed objects that reflect this.
This work is not complete yet

Les....





"C. M. Heard" <[email protected]>@ietf.org on 30/07/2003 20:30:07

Sent by:  [email protected]


To:   [email protected]
cc:   [email protected]
Subject:  RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-8021x-02.txt


On Wed, 30 Jul 2003, Wijnen, Bert (Bert) wrote:
> An alternative option might be to publish the RFC without the MIB
> module and just include a pointer to the inline MIB module at the
> IEEE web site.

Actually, I rather like that idea.  It certainly ensures that the
stuff in the information RFC can't get out-of-sync with the IEEE's
official version.  The only problem with that

http://www.ieee802.org/1/files/public/MIBs/802-1x-2001-mib.txt

has some problems that make it fail to compile (an illegal expression
for the OID assigned as the MODULE-IDENTITY value, non-ascii quotes,
and the absence of dot1xPaePortReauthenticate and
dot1xAuthSessionUserName from conformance groups).  The version in
the -01 draft corrected these problems.

I see that the IEEE is in fact working on a maintenance release of
802.1X (see http://www.ieee802.org/1/pages/802.1aa.html, or look for
the 802.1aa link under http://grouper.ieee.org/groups/802/1/), and
one of the work items is a MIB module update.  However, this is in
the private area and I don't know whether it includes the
corrections mentioned above (nor how else it might differ from the
current published version of the IEEE8021-PAE-MIB).

Maybe someone from 802.1aa could comment?

//cmh


_______________________________________________
Bridge-mib mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/bridge-mib