Alper Yegin wrote: > Then it is hard to be evaluating cost of PANA implementation/deployment > versus dhcp-auth.
I've read the drafts enough to be somewhat familiar with PANA. Even without that, the server-side analysis is simple. > I have a feeling that you are only looking at this from RADIUS perspective. > Yes, from RADIUS perspective, EAP arrives on another protocol, be it EAPOL, > PANA, or DHCP. I'm looking at it from a deployment perspective. New servers are expensive, even if the source code is available for free... which it isn't with PANA. > Indeed! There is no reason for that EAP transport be DHCP. I'll leave that argument to others. My point is simple: DHCP and RADIUS are already deployed on the server side. PANA isn't. > Again, this is just the RADIUS angle... Translating EAP/foo to EAP/RADIUS is > trivial, for all cases. Are there EAP to PANA gateways? That would seem to be hard, given the state machine requirements of PANA. The EAPoL state machine seems to be simpler than the PANA one... and it's already deployed. > Yes, it has nothing to do with DHCP. I'm glad we agree on that. Alan DeKok. _______________________________________________ Int-area mailing list [email protected] https://www.ietf.org/mailman/listinfo/int-area
