| RE: Resolution of 802.1X/EAP-SM issue | <– Date –> <– Thread –> |
|
From: Bernard Aboba (aboba |
|
| Date: Tue, 13 Jan 2004 18:28:35 -0500 (EST) | |
Thanks, Paul. The IETF Internet-Draft submission is coming up very soon, and hopefully we will have an EAP-State Machine revision in by then incorporating the proposed fix. Assuming that this happens, will there be time to get a fix applied to IEEE 802.1X-REV? On Tue, 13 Jan 2004, CONGDON,PAUL (HP-Roseville,ex1) wrote: > > Well, I'm not sure that is exactly how I read it. We could still update > 802.1X during the sponsor ballot. That update would likely only involve a > discussion within the annex about the new variable that the EAP-SM document > added. If the EAP-SM document doesn't have this new variable > (eapRemoteSuccess) nailed prior to the sponsor ballot close, then nothing > will be added to 802.1X. It would still be helpful to have the variable > documented in the EAP-SM document if this deadline isn't met. The sponsor > ballot for 802.1X will likely run in 1 month to 6 weeks time. We don't want > to make comments during recirculation ballot since we would have to run > another circulation ballot after that. We expect comments in sponsor > ballot, so we could slip the changes in there, but only if they are stable > in EAP-SM. > > Paul
-
RE: Resolution of 802.1X/EAP-SM issue CONGDON,PAUL (HP-Roseville,ex1), January 13 2004
- RE: Resolution of 802.1X/EAP-SM issue Bernard Aboba, January 13 2004
-
RE: Resolution of 802.1X/EAP-SM issue CONGDON,PAUL (HP-Roseville,ex1), January 13 2004
-
RE: Resolution of 802.1X/EAP-SM issue Bernard Aboba, January 13 2004
- RE: Resolution of 802.1X/EAP-SM issue John Vollbrecht, January 13 2004
- Re: Resolution of 802.1X/EAP-SM issue Yoshihiro Ohba, January 13 2004
-
RE: Resolution of 802.1X/EAP-SM issue Bernard Aboba, January 13 2004
Results generated by Tiger Technologies using MHonArc.