[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
The RADIUS attribute space: an assessment
At various points, authors of extended attribute space proposals have
pointed out the potential for exhaustion of the RADIUS attribute space
defined in RFC 2865. Based on an examination of the attribute needs of
current and projected IETF WG work items, I believe this concern is quite
real.
Based on the IANA web page and RFC 3575, currently RADIUS attributes 123-191
are eligible for assignment. Of these, 5 attributes need to be allocated
for documents that have currently completed IETF last call (Delegated-Prefix
and VLAN/Priority attributes). An additional 5 attributes are required for
documents that have undergone WG last call (RADIUS GEOPRIV and filter
attributes). This will leave a total of 58 attributes unassigned (133-191).
A look at the remaining RADEXT WG work items seems to indicate that they
could consume somewhere between 25 and 35 attributes. This would leave
between 23 and 33 attributes remaining.
Recently, the MIPv4 WG submitted a request to charter work on MIPv4
attributes for RADIUS. The current draft requests the allocation of 31
attributes.
It would therefore appear that the need for additional attribute space is
quite real, and rather immediate (e.g. next 12-18 months).
--
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/>