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

[Jari Arkko <jari.arkko@piuha.net>]

Bernard Aboba wrote:

>>- 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) 
>
Are you sure you included MIP6? The discussion we had on this
previously had to do with MIP4 WG, which also has RADIUS work.

>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. 
>  
>
And Dave wrote:

>I think, therefore, that the answer is (b).  The October date might be
>achieved with some concerted effort.  A later milestone date in MIP6
>would be advisable.   
>
Ok. So both of you seem to be saying option b. (The
dates you give are somewhat different, however. )

The MIP6 charter item is targeted for Feb 2007, and
could probably be postponed. But I worry that if we are
to align (and I see no reason to NOT align the attributes
if we are doing both anyway) then both RADIUS *and* Diameter
work will depend on the delivery of the RADEXT extension design.

My preliminary conclusion is that the MIP6 charter
item should stay but we need to discuss the timing
between all three WGs (mip6, dime, radext).

--Jari