Sam Hartman wrote: > I think this is true on the server. Yes.
> However, I'd really appreciate your thoughts on what will happen inside > the EAP peer itself? Ideally, code re-use. > My assumption is that outside of the guts of a TTLS implementation, EAP > peers today don't have knowledge either of RADIUS or DIAMETER. Largely, yes. > So, a > format that minimizes how much they need to understand either of these > protocols would be valuable. Valuable, yes. High value, perhaps not. There is plenty of BSD-licensed code available for packing and unpacking RADIUS attributes. There should be little cost to re-using that, and a larger cost in writing a new attribute packer. Alan DeKok. _______________________________________________ Emu mailing list Emu@ietf.org https://www.ietf.org/mailman/listinfo/emu
