Return-Path: X-Original-To: radext@ietfa.amsl.com Delivered-To: radext@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F25B1A00FD for ; Mon, 17 Feb 2014 23:27:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.748 X-Spam-Level: X-Spam-Status: No, score=-4.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5bbUftgfRWom for ; Mon, 17 Feb 2014 23:26:57 -0800 (PST) Received: from xenon24.um.es (xenon24.um.es [155.54.212.164]) by ietfa.amsl.com (Postfix) with ESMTP id 350521A0043 for ; Mon, 17 Feb 2014 23:26:57 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by xenon24.um.es (Postfix) with ESMTP id 7C157CFD8 for ; Tue, 18 Feb 2014 08:26:53 +0100 (CET) X-Virus-Scanned: by antispam in UMU at xenon24.um.es Received: from xenon24.um.es ([127.0.0.1]) by localhost (xenon24.um.es [127.0.0.1]) (amavisd-new, port 10024) with LMTP id tMUxmtnlPRtI for ; Tue, 18 Feb 2014 08:26:53 +0100 (CET) Received: from [10.42.0.19] (84.124.131.72.dyn.user.ono.com [84.124.131.72]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: alex) by xenon24.um.es (Postfix) with ESMTPSA id 12F28CCC5 for ; Tue, 18 Feb 2014 08:26:52 +0100 (CET) Message-ID: <53030B3B.8070409@um.es> Date: Tue, 18 Feb 2014 08:26:51 +0100 From: Alejandro Perez Mendez User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: radext@ietf.org References: <20140214132532.1455.32665.idtracker@ietfa.amsl.com> <52FE19C1.7050003@um.es> <051c01cf2a8d$11ff8ef0$35feacd0$@augustcellars.com> <5301BE65.1020607@um.es> <067201cf2bfb$2064db20$612e9160$@augustcellars.com> In-Reply-To: <067201cf2bfb$2064db20$612e9160$@augustcellars.com> X-Enigmail-Version: 1.6 Content-Type: multipart/alternative; boundary="------------060509020600080304010508" Archived-At: http://mailarchive.ietf.org/arch/msg/radext/KiGxAN4NfWrj6MB_8f5AiJNO88g Subject: Re: [radext] I-D Action: draft-ietf-radext-radius-fragmentation-03.txt X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Feb 2014 07:27:02 -0000 This is a multi-part message in MIME format. --------------060509020600080304010508 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit > Yes -- because it was so wrong -- I thought about putting it in the > middle. But that seemed to be over kill. I was just trying to make > the point that the bit needed to be specified. > Ok, I got your point. That will be included. Regards, Alejandro > > > Jim > > > > > > *From:*radext [mailto:radext-bounces@ietf.org] *On Behalf Of > *Alejandro Perez Mendez > *Sent:* Sunday, February 16, 2014 11:47 PM > *To:* radext@ietf.org > *Subject:* Re: [radext] I-D Action: > draft-ietf-radext-radius-fragmentation-03.txt > > > > > > El 15/02/14 21:32, Jim Schaad escribió: > > So based on your document, I assume that this is correct > > > > 0 1 2 3 > > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 > > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > | Type | Length | Extended-Type |M| Reserved |T| > > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > | Value ... > > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > > That's right. Nice figure, btw :) > However, I'd rather put the T flag next to the M flag (offset 25). Did > you had any reason for not doing so? > > Regards, > Alejandro > > > > > > -----Original Message----- > > > From: radext [mailto:radext-bounces@ietf.org] On Behalf Of Alejandro > > > Perez Mendez > > > Sent: Friday, February 14, 2014 5:27 AM > > > To: radext@ietf.org > > > Subject: Re: [radext] I-D Action: > draft-ietf-radext-radius-fragmentation- > > > 03.txt > > > > > > Hi, > > > > > > we just submitted an updated version of the draft, taking into > account the > > > received comments. > > > > > > Regards, > > > Alejandro > > > > > > El 14/02/14 14:25, internet-drafts@ietf.org > escribi : > > > > A New Internet-Draft is available from the on-line Internet-Drafts > > > directories. > > > > This draft is a work item of the RADIUS EXTensions Working Group > of the > > > IETF. > > > > > > > > Title : Support of fragmentation of RADIUS packets > > > > Authors : Alejandro Perez-Mendez > > > > Rafa Marin-Lopez > > > > Fernando Pereniguez-Garcia > > > > Gabriel Lopez-Millan > > > > Diego R. Lopez > > > > Alan DeKok > > > > Filename : > draft-ietf-radext-radius-fragmentation-03.txt > > > > Pages : 28 > > > > Date : 2014-02-14 > > > > > > > > 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. > > > > > > > > > > > > The IETF datatracker status page for this draft is: > > > > https://datatracker.ietf.org/doc/draft-ietf-radext-radius-fragmentatio > > > > n/ > > > > > > > > There's also a htmlized version available at: > > > > http://tools.ietf.org/html/draft-ietf-radext-radius-fragmentation-03 > > > > > > > > A diff from the previous version is available at: > > > > http://www.ietf.org/rfcdiff?url2=draft-ietf-radext-radius-fragmentatio > > > > n-03 > > > > > > > > > > > > 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. > > > > > > > > Internet-Drafts are also available by anonymous FTP at: > > > > ftp://ftp.ietf.org/internet-drafts/ > > > > > > > > _______________________________________________ > > > > radext mailing list > > > > radext@ietf.org > > > > https://www.ietf.org/mailman/listinfo/radext > > > > > > _______________________________________________ > > > radext mailing list > > > radext@ietf.org > > > https://www.ietf.org/mailman/listinfo/radext > > > > > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext > > > > > > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext --------------060509020600080304010508 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit

Yes – because it was so wrong – I thought about putting it in the middle.  But that seemed to be over kill.  I was just trying to make the point that the bit needed to be specified.


Ok, I got your point. That will be included.

Regards,
Alejandro

 

Jim

 

 

From: radext [mailto:radext-bounces@ietf.org] On Behalf Of Alejandro Perez Mendez
Sent: Sunday, February 16, 2014 11:47 PM
To: radext@ietf.org
Subject: Re: [radext] I-D Action: draft-ietf-radext-radius-fragmentation-03.txt

 

 

El 15/02/14 21:32, Jim Schaad escribió:

So based on your document, I assume that this is correct

 

  0                   1                   2                   3

    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   |     Type      |    Length     | Extended-Type |M|  Reserved |T|

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   |     Value ...

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


That's right. Nice figure, btw :)
However, I'd rather put the T flag next to the M flag (offset 25). Did you had any reason for not doing so?

Regards,
Alejandro


 

> -----Original Message-----

> From: radext [mailto:radext-bounces@ietf.org] On Behalf Of Alejandro

> Perez Mendez

> Sent: Friday, February 14, 2014 5:27 AM

> To: radext@ietf.org

> Subject: Re: [radext] I-D Action: draft-ietf-radext-radius-fragmentation-

> 03.txt

>

> Hi,

>

> we just submitted an updated version of the draft, taking into account the

> received comments.

>

> Regards,

> Alejandro

>

> El 14/02/14 14:25, internet-drafts@ietf.org escribi :

> > A New Internet-Draft is available from the on-line Internet-Drafts

> directories.

> >   This draft is a work item of the RADIUS EXTensions Working Group of the

> IETF.

> >

> >          Title           : Support of fragmentation of RADIUS packets

> >          Authors         : Alejandro Perez-Mendez

> >                            Rafa Marin-Lopez

> >                            Fernando Pereniguez-Garcia

> >                            Gabriel Lopez-Millan

> >                            Diego R. Lopez

> >                            Alan DeKok

> >          Filename        : draft-ietf-radext-radius-fragmentation-03.txt

> >          Pages           : 28

> >          Date            : 2014-02-14

> >

> > 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.

> >

> >

> > The IETF datatracker status page for this draft is:

> > https://datatracker.ietf.org/doc/draft-ietf-radext-radius-fragmentatio

> > n/

> >

> > There's also a htmlized version available at:

> > http://tools.ietf.org/html/draft-ietf-radext-radius-fragmentation-03

> >

> > A diff from the previous version is available at:

> > http://www.ietf.org/rfcdiff?url2=draft-ietf-radext-radius-fragmentatio

> > n-03

> >

> >

> > 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.

> >

> > Internet-Drafts are also available by anonymous FTP at:

> > ftp://ftp.ietf.org/internet-drafts/

> >

> > _______________________________________________

> > radext mailing list

> > radext@ietf.org

> > https://www.ietf.org/mailman/listinfo/radext

>

> _______________________________________________

> radext mailing list

> radext@ietf.org

> https://www.ietf.org/mailman/listinfo/radext




_______________________________________________
radext mailing list
radext@ietf.org
https://www.ietf.org/mailman/listinfo/radext

 



_______________________________________________
radext mailing list
radext@ietf.org
https://www.ietf.org/mailman/listinfo/radext

--------------060509020600080304010508--