[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Draft of extensions format

To: Alan DeKok <aland@deployingradius.com>
Subject: Re: Draft of extensions format
From: Peter Deacon <peterd@iea-software.com>
Date: Wed, 1 Sep 2010 09:53:18 -0700 (Pacific Daylight Time)
Cc: 'radext mailing list' <radiusext@ops.ietf.org>
In-reply-to: <alpine.WNT.2.00.1009010919470.3048@SMURF>
References: <4C7E6214.5090902@deployingradius.com> <alpine.WNT.2.00.1009010919470.3048@SMURF>
User-agent: Alpine 2.00 (WNT 1167 2008-08-23)

On Wed, 1 Sep 2010, Peter Deacon wrote:

On Wed, 1 Sep 2010, Alan DeKok wrote:

We are already set to run out of attribute space once. For that reasonallocating additional space on the same order could possibly lead to the sameproblems in the future.

My recommendation is to use a single extensions attribute and make length twobytes. Rob a couple of bits from the 16-bit length field for fragment andpossibly presence of an extra flags byte.


I apologize..

s/length/type

regards,
Peter

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

References:
- Draft of extensions format
  - From: Alan DeKok <aland@deployingradius.com>
- Re: Draft of extensions format
  - From: Peter Deacon <peterd@iea-software.com>

Prev by Date: Re: Draft of extensions format
Next by Date: [Technical Errata Reported] RFC5997 (2507)
Previous by thread: Re: Draft of extensions format
Next by thread: Re: Draft of extensions format
Index(es):
- Date
- Thread