eap Mailing List: RE: Resolution of 802.1X/EAP-SM issue

[CONGDON,PAUL (HP-Roseville,ex1) (paul.congdon]

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

> -----Original Message-----
> From: eap-admin [at] frascone.com [mailto:eap-admin [at] frascone.com] 
> On Behalf Of Bernard Aboba
> Sent: Tuesday, January 13, 2004 2:48 PM
> To: eap [at] frascone.com
> Subject: [eap] Resolution of 802.1X/EAP-SM issue
> 
> 
> IEEE 802.1X-REV met today, and my understanding is that the 
> resolution of the issue was that the changes required to 
> resolve this issue would be made solely within the EAP State 
> Machine document.  Since no new EAP-SM document was available 
> incorporating the changes, no reference was inserted in IEEE 
> 802.1X-REV.
> 
> As a result, this Issue exists only within the EAP WG, and 
> there is no need to cc: IEEE 802.1 on this issue discussion 
> any more. _______________________________________________
> eap mailing list
> eap [at] frascone.com
> http://mail.frascone.com/mailman/listinfo/eap
>