RE: Basic facts about EAP
From: Salowey, Joe (jsaloweycisco.com)
Date: Mon, 2 May 2005 22:30:33 -0400 (EDT)
 

> -----Original Message-----
> From: Jari Arkko [mailto:jari.arkko [at] piuha.net] 
<snip>
> I usually refer to the system as the "network access control 
> system", though this works only when EAP is used where it was 
> originally intended to be used. The system consists of 
> clients, NASes, proxies, and servers, and has three main
> protocols:
> 
> - First hop, either on L2 (e.g. 802.11i) or L3 (e.g. PANA, IKEv2)
> - AAA, running between NASes and servers in a fashion where
>   the existence of the proxies is visible and known to the protocol
> - EAP, running between the client and the servers, unaware
>   of NASes unless channel bindings are being provided
> 

[Joe] It would be better if EAP is unaware of NASes even if channel
bindings are being provided.  If EAP methods are going to remain
agnostic of their lower layers then this sort of information should be
passed out of the EAP method for the encapsulating layer to deal with.  

> --Jari
> 
> _______________________________________________
> eap mailing list
> eap [at] frascone.com
> http://mail.frascone.com/mailman/listinfo/eap
> 

Results generated by Tiger Technologies using MHonArc.