Re: [radext] I-D Action: draft-ietf-radext-radius-fragmentation-03.txt

"Jim Schaad" <ietf@augustcellars.com> Mon, 17 February 2014 16:14 UTC

Return-Path: <ietf@augustcellars.com>
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 7D8481A03F6 for <radext@ietfa.amsl.com>; Mon, 17 Feb 2014 08:14:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 iCRIo0AJyths for <radext@ietfa.amsl.com>; Mon, 17 Feb 2014 08:14:42 -0800 (PST)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id B6BAE1A00B8 for <radext@ietf.org>; Mon, 17 Feb 2014 08:14:42 -0800 (PST)
Received: from Philemon (c-24-17-142-118.hsd1.wa.comcast.net [24.17.142.118]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id E5C9A38F10; Mon, 17 Feb 2014 08:14:39 -0800 (PST)
From: Jim Schaad <ietf@augustcellars.com>
To: 'Alejandro Perez Mendez' <alex@um.es>, radext@ietf.org
References: <20140214132532.1455.32665.idtracker@ietfa.amsl.com> <52FE19C1.7050003@um.es> <051c01cf2a8d$11ff8ef0$35feacd0$@augustcellars.com> <5301BE65.1020607@um.es>
In-Reply-To: <5301BE65.1020607@um.es>
Date: Mon, 17 Feb 2014 08:12:59 -0800
Message-ID: <067201cf2bfb$2064db20$612e9160$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0673_01CF2BB8.12478E90"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLpjyC8xye9Uj5nztA7A+WPyCGywwIUmCWYAnPyS44BLj2e85hXIXCA
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/radext/-CkY_YHDQZ6K_9Pwfzm8e5JmW6s
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 <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/radext/>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 16:14:46 -0000

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.

 

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,  <mailto:internet-drafts@ietf.org> 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> 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> 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> 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/> ftp://ftp.ietf.org/internet-drafts/

> >

> > _______________________________________________

> > radext mailing list

> >  <mailto:radext@ietf.org> radext@ietf.org

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

> 

> _______________________________________________

> radext mailing list

>  <mailto:radext@ietf.org> radext@ietf.org

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






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