| Re: Resolution of 802.1X/EAP-SM issue | <– Date –> <– Thread –> |
|
From: Bernard Aboba (aboba |
|
| Date: Wed, 14 Jan 2004 03:22:21 -0500 (EST) | |
OK, now I understand. This makes sense. But we should document this reasoning somewhere in the state machine document. On Tue, 13 Jan 2004, Yoshihiro Ohba wrote: > I think John is right. The EAP state machine already has > eapKeyAvailable variable to indicate key possession status, which > means that a new eapRemoteSuccess variable is not needed if we have agreed > that key possession is sufficient information. > > Yoshihiro Ohba
- RE: Resolution of 802.1X/EAP-SM issue, (continued)
-
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 14 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 14 2004
- RE: Resolution of 802.1X/EAP-SM issue Nick Petroni, January 14 2004
- RE: Resolution of 802.1X/EAP-SM issue John Vollbrecht, January 14 2004
Results generated by Tiger Technologies using MHonArc.