Re: [Issue 248] Comments on EAP state machine v4
From: Nick Petroni (npetronics.umd.edu)
Date: Thu, 15 Jul 2004 02:45:00 -0400 (EDT)
Florent and all,

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 #5 - Technical
  No changes.

Comment #6 - Technical
  Request text to clarify the use the methodState variable in section
  4.2.

Comment #9 - Technical
  Request text amendments for policy functions to clarify that
  multiple authentication methods are not expected or propose
  alternate solution.

Comment #10 - Technical
  - change the text of TIMEOUT_FAILURE in section 5.5 and
    TIMEOUT_FAILURE2 in section 7.5 to the following:
  "A final state indicating failure because no response has been
   received. Because no response was received, no new message
   (including failure) should be sent to the peer."

Comment #12 - Technical
  Supersede by the resolution of Issue 251 (TBD).

Comment #14 - Technical
  Request text to describe the possible DoS issues and possible
  mitigation techniques. Specific changes to the SM necessary to
  achieve such mitigations would be great.

Comment #17 - Technical
  Request text for section 7 and/or section 8 to
  describe expected behavior when aaaEapRespData is NONE.


Results generated by Tiger Technologies using MHonArc.