Re: [Emu] RFC5216 - L-Flag in the fragment packets (fwd)

2009-05-07 Thread Alan DeKok
Bernard Aboba wrote: > In the FreeRadius implementation, there is an option called > “include_length” in the tls module configuration section of eap.conf > file, its default value is set to “yes”, and with this configuration the > server sends the L-flag in each fragment, this is not consistent wi

Re: [Emu] RFC5216 - L-Flag in the fragment packets (fwd)

2009-05-05 Thread Jonathan Rausch
r Networks, Inc. From: emu-boun...@ietf.org [mailto:emu-boun...@ietf.org] On Behalf Of Bernard Aboba Sent: Tuesday, May 05, 2009 4:11 AM To: emu@ietf.org Subject: [Emu] RFC5216 - L-Flag in the fragment packets (fwd) From: Mur

Re: [Emu] RFC5216 - L-Flag in the fragment packets (fwd)

2009-05-05 Thread Jouni Malinen
> From: Murat Sezgin [msez...@ubicom.com] > In the “2.1.5 Fragmentation” section of the RFC5216, it is written that “The > L flag is set to indicate the presence of the four-octet TLS Message Length > field, and MUST be set for the first fragment of a fragmented TLS message or > set of message

[Emu] RFC5216 - L-Flag in the fragment packets (fwd)

2009-05-05 Thread Bernard Aboba
From: Murat Sezgin [msez...@ubicom.com] Sent: Tuesday, May 05, 2009 3:27 AM To: Dan Simon; Bernard Aboba; Ryan Hurst Subject: RFC5216 - L-Flag in the fragment packets Hi Mr.Simon, Mr.Aboba and Mr.Hurst In the “2.1.5 Fragmentation” section of t