eap-22----Page:7
1  2  3  4  5  6  7  8  9  10  11 

97 - Strict mode
Problem:
Should a method be able to disable "other inputs" while working?
Type (sequences etc)
Code (success, failure)
Arguments:
Disabling useful or not? Full Denial-of-Service protection not achievable?
Many implementations do this, but built into the EAP MUX, not method specific
Resolution:
1) No strict mode
2) Limited strict mode, in the state machine
3) Limited strict mode, method specific
Methods may to go into "strict mode” where state machine discards other inputs
RFC 2284 methods do not use strict mode
4) General filters
PPT Version