| RE: Resolution of 802.1X/EAP-SM issue | <– Date –> <– Thread –> |
|
From: Bernard Aboba (aboba |
|
| Date: Wed, 14 Jan 2004 19:47:02 -0500 (EST) | |
Thanks, Paul. Are there any objections to resolving the issue this way? On Wed, 14 Jan 2004, CONGDON,PAUL (HP-Roseville,ex1) wrote: > > I think, at the end of the day, concerning what documents needs what > changing... We could get away with no changes in either document, but since > EAP-SM is still in more of a development stage, it would be helpful to > include some discussion around the keyAvailable signal that indicates this > signal is sufficient for a pass-thru authenticator to know the remote peer > has accepted the mutual authentication (or something to that nature)... > > I believe we are all agreeing the eapRemoteSuccess is not needed, and thus, > 802.1X is not waiting for any specific updates to the EAP-SM document. The > above recommendation would simply help capture the conclusions we have come > to... > > Paul
- RE: Resolution of 802.1X/EAP-SM issue, (continued)
- RE: Resolution of 802.1X/EAP-SM issue John Vollbrecht, January 14 2004
-
RE: Resolution of 802.1X/EAP-SM issue CONGDON,PAUL (HP-Roseville,ex1), January 14 2004
-
RE: Resolution of 802.1X/EAP-SM issue John Vollbrecht, January 14 2004
- Re: Resolution of 802.1X/EAP-SM issue Jim Burns, January 14 2004
- RE: Resolution of 802.1X/EAP-SM issue Bernard Aboba, January 14 2004
- RE: Resolution of 802.1X/EAP-SM issue Nick Petroni, January 15 2004
-
RE: Resolution of 802.1X/EAP-SM issue John Vollbrecht, January 14 2004
- RE: Resolution of 802.1X/EAP-SM issue CONGDON,PAUL (HP-Roseville,ex1), January 14 2004
Results generated by Tiger Technologies using MHonArc.