Re: [radext] Fwd: New Version Notification for draft-ietf-radext-radius-fragmentation-05.txt

Hi,
> As agreed during last RADEXT meeting on Tuesday, we've submitted a new 
> version (05) of the draft, where we have added the following text, 
> related to the no-inclusion of authentication attributes in the first 
> fragment of the pre-authentication phase:
>
> The
>     authors acknowledge this is formally violating [RFC2865], but there
>     are no known operational issues with it.
because ... ? I believe it deserves a little bit more information.

My meeting minutes tells me: because all implementations don't do this 
"An Access-request MUST contain either a User-Password or a 
CHAP-passwork or a State"

Regards, Benoit
> Once this document goes
>     beyond being considered as experimental, it will state it updates
>     [RFC2865].
> Regards,
> Alejandro
>
>
>
> -------- Mensaje original --------
> Asunto: 	New Version Notification for 
> draft-ietf-radext-radius-fragmentation-05.txt
> Fecha: 	Thu, 06 Mar 2014 23:51:26 -0800
> De: 	internet-drafts@ietf.org
> Para: 	Alejandro Perez-Mendez <alex@um.es>, "Alejandro Perez-Mendez" 
> <alex@um.es>, Diego R. Lopez <diego@tid.es>, "Alan DeKok" 
> <aland@networkradius.com>, Alan DeKok <aland@networkradius.com>, 
> "Rafael Lopez" <rafa@um.es>, "Gabriel Lopez-Millan" <gabilm@um.es>, 
> Gabriel Lopez-Millan <gabilm@um.es>, Fernando Pereniguez-Garcia 
> <pereniguez@um.es>, Rafa Marin-Lopez <rafa@um.es>, "Diego R. Lopez" 
> <diego@tid.es>, "Fernando Pereniguez-Garcia" <pereniguez@um.es>
>
>
>
> A new version of I-D, draft-ietf-radext-radius-fragmentation-05.txt
> has been successfully submitted by Alejandro Perez-Mendez and posted to the
> IETF repository.
>
> Name:		draft-ietf-radext-radius-fragmentation
> Revision:	05
> Title:		Support of fragmentation of RADIUS packets
> Document date:	2014-03-07
> Group:		radext
> Pages:		28
> URL:http://www.ietf.org/internet-drafts/draft-ietf-radext-radius-fragmentation-05.txt
> Status:https://datatracker.ietf.org/doc/draft-ietf-radext-radius-fragmentation/
> Htmlized:http://tools.ietf.org/html/draft-ietf-radext-radius-fragmentation-05
> Diff:http://www.ietf.org/rfcdiff?url2=draft-ietf-radext-radius-fragmentation-05
>
> Abstract:
>     The Remote Authentication Dial-In User Service (RADIUS) protocol is
>     limited to a total packet size of 4096 octets.  Provisions exist for
>     fragmenting large amounts of authentication data across multiple
>     packets, via Access-Challenge.  No similar provisions exist for
>     fragmenting large amounts of authorization data.  This document
>     specifies how existing RADIUS mechanisms can be leveraged to provide
>     that functionality.  These mechanisms are largely compatible with
>     existing implementations, and are designed to be invisible to
>     proxies, and "fail-safe" to legacy clients and servers.
>
>                                                                                    
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>
>
>
>
> _______________________________________________
> radext mailing list
> radext@ietf.org
> https://www.ietf.org/mailman/listinfo/radext