Re: [Emu] EAP and authorization

To: david at mitton.com
Subject: Re: [Emu] EAP and authorization
From: Alan DeKok <aland at deployingradius.com>
Date: Sun, 16 Aug 2009 10:30:07 +0200
Cc: emu at ietf.org
Delivered-to: emu at core3.amsl.com
In-reply-to: <2018380107.9112.1250262806060.JavaMail.mail at webmail04>
List-archive: <http://www.ietf.org/mail-archive/web/emu>
List-help: <mailto:emu-request@ietf.org?subject=help>
List-id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-post: <mailto:emu@ietf.org>
List-subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
References: <2018380107.9112.1250262806060.JavaMail.mail at webmail04>
User-agent: Thunderbird 2.0.0.22 (Macintosh/20090605)

David Mitton wrote:
>> The main limitation on bulk data transfer is that most EAP to
>> RADIUS gateways (AP's, etc.) will terminate an EAP session after ~50
>> packets.
> 
> This kind of thing drives me crazy.  Why are their such policies?

  To prevent bulk transfer of data over EAP, among others.

> Please do not build EAP session breaking assumptions into AAA implementations.

  It would be useful to codify these experiences into an EAP "best
practices" document.

  Alan DeKok.

Follow-Ups:
- Re: [Emu] EAP and authorization
  - From: David Mitton

References:
- Re: [Emu] EAP and authorization
  - From: David Mitton

Prev by Date: Re: [Emu] EAP and authorization
Next by Date: Re: [Emu] EAP and authorization
Previous by thread: Re: [Emu] EAP and authorization
Next by thread: Re: [Emu] EAP and authorization
Index(es):
- Date
- Thread

Re: [Emu] EAP and authorization

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.