include_length and EAP-TTLS

2008-12-04 Thread Gong Cheng 
I wonder if this is a small violation of the EAP-TTLS RFC (5281).

In RFC 5281 http://tools.ietf.org/html/rfc5281#section-9.2.2, it states:

   Fragments other than the first MUST NOT have the L
   bit set. ...


while this behavior is configurable in eap.conf:


#  include_length is a flag which is
#  by default set to yes If set to
#  yes, Total Length of the message is
#  included in EVERY packet we send.
#  If set to no, Total Length of the
#  message is included ONLY in the
#  First packet of a fragment series.
#
#   include_length = yes


I understand that it is for EAP-TLS (which does not have this restriction) but 
I think EAP-TTLS is controlled by the same line. (?)

I confess that I only actually SEE the behavior in the now ancient 1.1.6 
version, and only took a quick look at the 2.1.0 config file and source code. I 
apologize if  I missed something or this had been brought up before.

-gong
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Re: include_length and EAP-TTLS

2008-12-04 Thread Alan DeKok 
Gong Cheng wrote:
 I wonder if this is a small violation of the EAP-TTLS RFC (5281).
 
 In RFC 5281 http://tools.ietf.org/html/rfc5281#section-9.2.2, it states:
 
    Fragments other than the first MUST NOT have the L
bit set. ...
 
 
 while this behavior is configurable in eap.conf:
...
 I confess that I only actually SEE the behavior in the now ancient 1.1.6 
 version, and only took a quick look at the 2.1.0 config file and source code. 
 I apologize if  I missed something or this had been brought up before.

  I don't think it's serious.  I don't know why this is a MUST NOT,
because it makes very little difference to the protocol.  And
supplicants that break if the L bit is set on second fragments are badly
written.

  Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Re: include_length and EAP-TTLS

2008-12-04 Thread Gong Cheng 
(sorry i still don't know how to reply into a thread from yahoo web mail)
Yeah I agree. All the supplicants I used are ok with that. I just thought I 
might point it out ... Thanks for your reply Alan.





Re: include_length and EAP-TTLS

 
* To: FreeRadius users mailing list 
freeradius-users@lists.freeradius.org
* Subject: Re: include_length and EAP-TTLS
* From: Alan DeKok [EMAIL PROTECTED]
* Date: Fri, 05 Dec 2008 07:58:14 +0100
* In-reply-to: [EMAIL PROTECTED]
* References: [EMAIL PROTECTED]
* Reply-to: FreeRadius users mailing list 
freeradius-users@lists.freeradius.org
* User-agent: Thunderbird 2.0.0.18 (Macintosh/20081105)

 
Gong Cheng wrote:
 I wonder if this is a small violation of the EAP-TTLS RFC (5281).
 
 In RFC 5281 http://tools.ietf.org/html/rfc5281#section-9.2.2, it states:
 
    Fragments other than the first MUST NOT have the L
bit set. ...
 
 
 while this behavior is configurable in eap.conf:
...
 I confess that I only actually SEE the behavior in the now ancient 1.1.6 
 version, and only took a quick look at the 2.1.0 config file and source code. 
 I apologize if  I missed something or this had been brought up before.

  I don't think it's serious.  I don't know why this is a MUST NOT,
because it makes very little difference to the protocol.  And
supplicants that break if the L bit is set on second fragments are badly
written.

  Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html