[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Extending RADIUS Attribute Space
C) Optionally address the issue of how to extend a message again
again, which of the two critical target applications asked for
that, why, and can it be done with less change to existing
Almost all usage of EAP today is on link layers where the EAP
MTU is already constrained to a smaller value than the RADIUS
MTU. RFC 2869 enables the RADIUS peers to know what the link
MTU is, so that they can take this into account.
There are some new cases where we have discussed the possibility
of making the MTU larger, such as IKEv2, where making the MTU
larger would leave fragmentation to be handled by the IP layer,
presumably in a more efficient fashion than at EAP layer.
However, even in this case the controlling end of the EAP
"connection", the AAA server, would know that it is running
over RADIUS. So it could take this fact into account when choosing
Most EAP methods with long messages can fragment on their own --
otherwise they could not be run on popular link layers such as
In conclusion, as far as EAP goes, there does not appear to be
a critical need for extended message lengths.
to unsubscribe send a message to firstname.lastname@example.org with
the word 'unsubscribe' in a single line as the message text body.