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

Re: Subtypes

I agree.  Since RADIUS only allows attributes of 253 octets, subtypes are
inherently limited in their functionality.  If it is necessary to support
grouping, the grouping mechanism specified in RFC 2867 can be used.  If
the issue is attribute space and the need can be proven, we can talk about
expansion.  So far I don't see a requirement to change the RADIUS
dictionary.

On Wed, 26 Nov 2003, Jari Arkko wrote:

> I would personally prefer that we stick to the simple
> and existing RADIUS AVP scheme. I am not convinced that
> there is such a large number of subtypes that it would
> have a big impact on performance if they were carried in
> separate AVPs.
>
> --Jari

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