| Re: [Issue 248] Comments on EAP state machine v4 | <– Date –> <– Thread –> |
|
From: Florent Bersani (florent.bersani |
|
| Date: Fri, 16 Jul 2004 11:31:49 -0400 (EDT) | |
Nick Petroni wrote:
Florent and all,It would be great if some luminaries could enlighten us on this!!!!
As Monday 7/19 is the cut-off for document submission, I would like to ask for help in resolving as much of the remaining issues as possible in the state machine document. Here is a list of necessary changes as I see them for Issue 248. Please let me know how these look in principle and contribute text if possible. I also will attempt to contribute text over the next couple of days.
Thanks, nick
Comment #12 - Technical
Supersede by the resolution of Issue 251 (TBD).
Florent, who hates to spend time to educate others but loves being educated ;-)
Comment #12 - Technical
This one is stupid but what happens, according to Figure 4, when the standalone authenticator fails directly, i.e. starts by INITIALIZE, transitions to SELECT_ACTION where Policy.getDecision replies FAILURE and thus transitions to FAILURE - in the FAILURE state, I bet there is some problem with eapReqData = buildFailure(currentId) since currentId=NONE
- Re: [Issue 248] Comments on EAP state machine v4, (continued)
- Re: [Issue 248] Comments on EAP state machine v4 Nick Petroni, July 16 2004
- Re: [Issue 248] Comments on EAP state machine v4 John Vollbrecht, July 22 2004
- Re: [Issue 248] Comments on EAP state machine v4 Nick Petroni, July 16 2004
- Re: [Issue 248] Comments on EAP state machine v4 Nick Petroni, July 16 2004
Results generated by Tiger Technologies using MHonArc.