RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-8021x-02.txt

"Les Bell" <Les_Bell@eur.3com.com> Thu, 31 July 2003 08:09 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15678 for <bridge-archive@odin.ietf.org>; Thu, 31 Jul 2003 04:09:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19i8Uj-0004Uk-VN for bridge-archive@odin.ietf.org; Thu, 31 Jul 2003 04:09:06 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6V895eq017273 for bridge-archive@odin.ietf.org; Thu, 31 Jul 2003 04:09:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19i8Ue-0004Tm-6B; Thu, 31 Jul 2003 04:09:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19i8Tl-0004QT-Eu for bridge-mib@optimus.ietf.org; Thu, 31 Jul 2003 04:08:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15614 for <bridge-mib@ietf.org>; Thu, 31 Jul 2003 04:08:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19i8Ti-0000ck-00 for bridge-mib@ietf.org; Thu, 31 Jul 2003 04:08:02 -0400
Received: from ip-161-71-171-238.corp-eur.3com.com ([161.71.171.238] helo=columba.www.eur.3com.com) by ietf-mx with esmtp (Exim 4.12) id 19i8Th-0000cg-00 for bridge-mib@ietf.org; Thu, 31 Jul 2003 04:08:02 -0400
Received: from toucana.eur.3com.com (toucana.EUR.3Com.COM [140.204.220.50]) by columba.www.eur.3com.com with ESMTP id h6V89SkC013184; Thu, 31 Jul 2003 09:09:28 +0100 (BST)
Received: from notesmta.eur.3com.com (eurmta1.EUR.3Com.COM [140.204.220.206]) by toucana.eur.3com.com with SMTP id h6V8A6d08304; Thu, 31 Jul 2003 09:10:07 +0100 (BST)
Received: by notesmta.eur.3com.com(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) id 80256D74.002CA985 ; Thu, 31 Jul 2003 09:07:49 +0100
X-Lotus-FromDomain: 3COM
From: "Les Bell" <Les_Bell@eur.3com.com>
To: "C. M. Heard" <heard@pobox.com>
cc: bridge-mib@ietf.org, stds-802-1@ieee.org
Message-ID: <80256D74.002CA874.00@notesmta.eur.3com.com>
Date: Thu, 31 Jul 2003 09:07:42 +0100
Subject: RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-8021x-02.txt
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: bridge-mib-admin@ietf.org
Errors-To: bridge-mib-admin@ietf.org
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>, <mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Id: <bridge-mib.ietf.org>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>, <mailto:bridge-mib-request@ietf.org?subject=subscribe>



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" <heard@pobox.com>@ietf.org on 30/07/2003 20:30:07

Sent by:  bridge-mib-admin@ietf.org


To:   bridge-mib@ietf.org
cc:   stds-802-1@ieee.org
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
Bridge-mib@ietf.org
https://www1.ietf.org/mailman/listinfo/bridge-mib





_______________________________________________
Bridge-mib mailing list
Bridge-mib@ietf.org
https://www1.ietf.org/mailman/listinfo/bridge-mib