RE: [802.1] RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-8021x-02.txt (fwd)
"C. M. Heard" <heard@pobox.com> Fri, 01 August 2003 05:23 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 BAA26980 for <bridge-archive@odin.ietf.org>; Fri, 1 Aug 2003 01:23:11 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19iSNI-0006KS-FW for bridge-archive@odin.ietf.org; Fri, 01 Aug 2003 01:22:44 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h715Mict024324 for bridge-archive@odin.ietf.org; Fri, 1 Aug 2003 01:22:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19iSMb-0006Jq-KC; Fri, 01 Aug 2003 01:22:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19iSMB-0006JT-LG for bridge-mib@optimus.ietf.org; Fri, 01 Aug 2003 01:21:35 -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 BAA26974 for <bridge-mib@ietf.org>; Fri, 1 Aug 2003 01:21:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19iSM8-0002So-00 for bridge-mib@ietf.org; Fri, 01 Aug 2003 01:21:32 -0400
Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 19iSM7-0002Sl-00 for bridge-mib@ietf.org; Fri, 01 Aug 2003 01:21:31 -0400
Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h715LVO17906 for <bridge-mib@ietf.org>; Thu, 31 Jul 2003 22:21:31 -0700
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Thu, 31 Jul 2003 22:21:30 -0700
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: bridge-mib@ietf.org
Subject: RE: [802.1] RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-8021x-02.txt (fwd)
Message-ID: <Pine.LNX.4.10.10307312218520.11354-110000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-2133786286-408399451-1059715139=:11354"
Content-ID: <Pine.LNX.4.10.10307312221170.11354@shell4.bayarea.net>
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 attached message was apparently trapped by the spam filters. -- cmh ]
--- Begin Message ---Hi folks, At the July Plenary we have decided to put the 802.1aa mib back to its original 802.1X state (or as close to it as we can achieve). Those values which are EAP or AAA related (counts of 'request ids' and 'response ids', etc) will have their text changed to indicate that these values will be filled by a functional entity other than the 802.1X PAE(the EAP entity for instance). The reason for this issue is that .1aa clearly dilineates labor between the 802.1X PAE and EAP and AAA. The guiding principle in .1aa is that it is to transport EAP and switch between controlled/uncontrolled port, not interpret EAP, this means it should not look at the EAP header, only the EAPOL header. With this principle, the PAE is unable to keep some MIB statistics and those need to be handled by the appropriate entities (although in actual implementations it is very likely that one piece of software is handling PAE and EAP on the authenticator, the standards are separate). Our options were to: 1. Alter the existing MIB to get the closest values to the current ones while only looking at the EAPOL header. 2. Remove all EAP related values and let the EAP group define their own MIB. 3. Leave the MIB alone and let the text indicate that some values need to be filled by entities other than the PAE. We chose #3 because we don't want to change the MIB for fear that the AP and Bridge manufacturers may not update their MIBs to the new one in a timely fashion and then management software will need to deal with these different MIBs leading to potential interoperability issues. The feeling is that it took a long time for the industry to get the current MIB implemented properly on their equipment, this MIB is extremely important to troubleshooting and we don't want to add yet another potential complexity to wireless access. So, the MIB remains the same, the definition for the values remain the same, but which functional entity is expected to fill some of the values is made more clear. The changes to bring the .1aa MIB back toward the original .1X MIB should be done soon. If you would like to review the changes please let me know and we can send them out to you as soon as we get them done. These will be 'beta' changes as they will still need to go through the IEEE balloting process, but it would allow you to track it and give input. Thanks, Jim B. -----Original Message----- From: owner-stds-802-1@majordomo.ieee.org [mailto:owner-stds-802-1@majordomo.ieee.org]On Behalf Of Les Bell Sent: Thursday, July 31, 2003 4:08 AM To: C. M. Heard Cc: bridge-mib@ietf.org; stds-802-1@ieee.org Subject: [802.1] RE: [Bridge-mib] 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" <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--- End Message ---
- [Bridge-mib] I-D ACTION:draft-ietf-bridge-8021x-0… Internet-Drafts
- Re: [Bridge-mib] I-D ACTION:draft-ietf-bridge-802… C. M. Heard
- Re: [Bridge-mib] I-D ACTION:draft-ietf-bridge-802… Les Bell
- RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-802… Wijnen, Bert (Bert)
- RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-802… C. M. Heard
- RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-802… C. M. Heard
- RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-802… Les Bell
- RE: [802.1] RE: [Bridge-mib] I-D ACTION:draft-iet… C. M. Heard
- RE: [802.1] RE: [Bridge-mib] I-D ACTION:draft-iet… Jim Burns
- Re: [802.1] RE: [Bridge-mib] I-D ACTION:draft-iet… K.C. Norseth
- Re: [802.1] RE: [Bridge-mib] I-D ACTION:draft-iet… C. M. Heard
- [Bridge-mib] I-D ACTION:draft-ietf-bridge-8021x-0… K.C. Norseth
- Re: [Bridge-mib] I-D ACTION:draft-ietf-bridge-802… C. M. Heard
- Re: [Bridge-mib] I-D ACTION:draft-ietf-bridge-802… C. M. Heard