eap Mailing List: Re: Proposed resolution of Issue 198: Other EAP Peer SM Issues

[John Vollbrecht (jrv]

--On Wednesday, November 19, 2003 11:52 AM +0200 Pasi.Eronen [at] nokia.com 
wrote:

> Proposed resolution to issue 198: Other EAP Peer SM issues
>
> - Remove all references to EapTunnelled (it does not adequately
>   define behavior of existing tunneled methods, and we don't even
>   need to describe their behavior in this document).
I like all the changes except the removing of EapTunnelled.  It is set if 
EAP is running in tunnelled mode and hence allowed to do method sequencing. 
I think this is a marker that says that sequences are not allowed on 
unprotected connections, but are (or are not forbidden) in protected 
connections.  I see no reason to take this out.  EAP is not constrained to 
run in an unprotected mode, and this indicates that everything should be 
the same in protected mode, except that method sequences are possible.




> - Change in Section 4.1.1 (portEnabled) from:
>
>   "Indicates that there is a valid port to use for the
>   communication.  If at any point the port is not available,
>   portEnabled is set to FALSE and the state machine transitions
>   to DISABLED (or BACKEND_DISABLED)."
>
>   to
>
>   "Indicates that the EAP peer state machine should be ready for
>   communication. This is set to TRUE when the EAP conversation is
>   started by the lower layer. If at any point the communication
>   port or session is not available, portEnabled is set to FALSE
>   and the state machine transitions to DISABLED."
>
> - Change in Section 5.1.1 (portEnabled) from
>
>   "Indicates that there is a valid port to use for the
>   communication.  If at any point the port is not available,
>   portEnabled is set to FALSE and the state machine transitions
>   to DISABLED."
>
>   to
>
>   "Indicates that the EAP authenticator state machine should be
>   ready for communication.  This is set to TRUE when the EAP
>   conversation is started by the lower layer. If at any point
>   the communication port or session is not available,
>   portEnabled is set to FALSE and the state machine transitions
>   to DISABLED."
>
> - Change in Section 4.1.3 (ClientTimeout) from:
>
>   "Configurable amount of time to wait for a valid request
>   before aborting."
>
>   to
>
>   "Configurable amount of time to wait for a valid request
>   before aborting, initialized by implementation-specific
>   means (e.g. a configuration setting)."
>
> - Change in Section 4.2 from
>
>   "methodState=DONE: The method always continues at this point,
>   (or the peer sees no point in continuing it)."
>
>   to
>
>   "methodState=DONE: The method never continues at this point
>   (or the peer sees no point in continuing it)."
>
> - Add to Section 8 (implementation considerations):
>
>   "Implementations may define an additional interfaces to pass
>   method-specific information between methods and lower layers.
>   These interfaces are beyond the scope of this document."
>
> Best regards,
> Pasi
> _______________________________________________
> eap mailing list
> eap [at] frascone.com
> http://mail.frascone.com/mailman/listinfo/eap