| RE: Authenticator versus AAA client | <– Date –> <– Thread –> |
|
From: Nakhjiri Madjid-MNAKHJI1 (Madjid.Nakhjiri |
|
| Date: Mon, 5 Dec 2005 15:30:27 -0800 (PST) | |
Hi Yoshiro, Ok, thanks for the clarification. Agreed. EAP pass-through authenticator does understand EAP Requests and Responses for matching the Requests with Responses. But EAP path-through authenticator does not need to understand the content of the Data field of the Requests and Responses. AAA client receives the master keys from AAA server, but it just passes the received keys to the EAP pass-through authenticator and never caches the keys. So I think the pass-through authenticator is the final receiver of the master keys. Madjid>> I can understand that this is a logical deduction, but is there anywhere it is stated that AAA client cannot cache the keys, but authenticator can? Madjid Yoshihiro Ohba > > Any guidance? > > Thanks, > > Madjid Nakhjiri > > _________________________________________________________________ > To unsubscribe or modify your subscription options, please visit: > http://lists.frascone.com/mailman/listinfo/eap > > Arhives: http://lists.frascone.com/pipermail/eap
-
Authenticator versus AAA client Nakhjiri Madjid-MNAKHJI1, November 30 2005
- Re: Authenticator versus AAA client Yoshihiro Ohba, December 5 2005
- Re: Authenticator versus AAA client Jari Arkko, December 13 2005
- RE: Authenticator versus AAA client Nakhjiri Madjid-MNAKHJI1, December 5 2005
- Re: Authenticator versus AAA client Yoshihiro Ohba, December 6 2005
- RE: Authenticator versus AAA client Nakhjiri Madjid-MNAKHJI1, March 1 2006
Results generated by Tiger Technologies using MHonArc.