Re: draft-winter-radsec-01 published

[Alan DeKok <aland@nitros9.org>]

Stefan Winter wrote:
> I'm also about to write a draft for one of the EAP issues, about the problem 
> that it is sub-optimal to find out how much EAP payload exactly to put into a 
> RADIUS packet so that it doesn't fragment on the way but still fills the 
> available space. Currently, this is determined by guessing

  ?

 RFC 3579, Section 2.4 says that the NAS should Framed-MTU.  All servers
I know of use this to determine EAP payload.  If the Framed-MTU isn't
sent, then a "safe" assumption of normal Ethernet is used.

  i.e. eap_payload = Framed-MTU - eapol_header

  This calculation is extended to the contents of EAP types, by
accounting for known, and fixed, EAP-type headers.

> and 
> better-safe-than-sorry underestimations on the server side, and not at all 
> done on the supplicant side.

  ?

  If the supplicant doesn't know what the local L2 MTU is, it's
completely broken.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>