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

RE: Questions on RADIUS Extended attributes



Alan DeKok <> supposedly scribbled:

> "Bernard Aboba" <bernard_aboba@hotmail.com> wrote:
>> a. Do we want an Extended-Type field of two or four octets?  If it is
>> four octets, this would seem to imply that RADIUS attributes and
>> Diameter AVPs share the same type space.  Will this work?  If it is
>> two octets, we could reserve 65535 values within the existing
>> Diameter attribute space for RADIUS Extended-Type attributes.  
>> Opinions solicited. 
> 
>   I think 2 octets is OK.  There are nowhere near 64k RADIUS
> attributes in existence today, even including VSA's.  So 64k would
> seem to be sufficient for a while.  

A master of understatement ;-).  Actually, I suspect that another 256 would be more than enough, if there was a rational (or any) AAA development strategy in the IETF; probably even without one.

Hope this helps,

~gwz

Why is it that most of the world's problems can't be solved by simply
  listening to John Coltrane? -- Henry Gabriel

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