On Sep 27, 2021, at 1:18 PM, Yuan Tian <[email protected]> wrote: > And I checked AVP lists, there is an “EAP” AVP available and but it seems to > be designed for AAA and needs to be always used with RADIUS > access-request/access-challenge (is that okay if I do not allow the server to > forwards the message in Radius access-request?).
RFC 5281 Section 10 says that the inner data is in Diameter format, and uses the RADIUS / Diameter attribute space. So just use EAP-Message. > Upon receipt of the tunneled EAP-Response/Identity, the TTLS server > forwards it to the AAA/H in a RADIUS Access-Request. > > So my question is, besides EAP-TTLS, is there an EAP protocol that is widely > supported and can be used for piggybacking a customized protocol? > Thanks,. TTLS seems like the best approach. Inside of that you can use EAP-Message, and a vendor-specific EAP type. Alan DeKok. _______________________________________________ Emu mailing list [email protected] https://www.ietf.org/mailman/listinfo/emu
