Re: RADIUS attribute space situation and WGs wanting to add attributes

[Bernard Aboba <aboba@internaut.com>]

> - What is the state of RADIUS attribute space?
>   Perhaps you can answer with one of the following
>   conclusions:
> 
>      (1) Used up, no near-term possibility to rectify
>          the situation. Please don't charter any new
>          RADIUS work.

At IETF 66, an analysis was presented of the currently allocatable RADIUS 
attribute space.  It appears that currently chartered work 
(which includes MIPv6 attributes) could exhaust the RADIUS attribute 
space.

>      (2) Used up but a solution will appear. Feel free
>          to recharter, but don't put a milestone until
>          MM, YYYY.

Currently, the RADEXT WG is debating potential solutions to the 
problem.  At IETF 66, there appeared to be consensus to address the issue, 
but the mechanism is currently under discussion.  Part of the debate is 
whether the solution should be compatible with existing RADIUS servers, or 
whether it will require new code.  Obviously requiring new code would 
delay deployment. 

There is also the issue of Diameter compatibility.  Whatever mechanism is 
created for extending the RADIUS attribute space, it will need to be 
supported in Diameter and RADIUS/Diameter gateways.  So addressing 
the compatibility issues will require additional work, which is not yet 
chartered. 

My guess is that the RADEXT WG will choose a direction relatively soon, 
but getting all the required documents through the IETF process could take 
18-24 months. 

Until then, it is possible that new work could complete the 
IETF process, but block on an IANA allocation.