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

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

Ok. From the point of view of the MIP6 charter
I'm going to change the deadline of the RADIUS
work to be a couple of months later, say April
2007. There's no penalty for finishing early,
but at least we're recognizing the possible
effort in getting this, dime, and radext
synchronized.

--Jari

Bernard Aboba wrote:
>> Are you sure you included MIP6? The discussion we had on this
>> previously had to do with MIP4 WG, which also has RADIUS work.
>>     
>
> Oh.  I think you're right.  MIPv6 wasn't included in the original 
> estimate, just MIPv4. 
>
>   
>> Ok. So both of you seem to be saying option b. (The
>> dates you give are somewhat different, however. )
>>     
>
> I think we both agree that RADEXT WG work could wrap up relatively soon.  
> It's all the other associated items (such as Diameter/RADIUS gateway spec 
> updates) that will take most of the time. 
>
>   
>> 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.
>>     
>
> Actually, I think they are most likely to be held up by required changes 
> to Diameter, not RADIUS.  For example, Diameter will need to allocate 
> another space for extended RADIUS attributes, and describe how they are 
> translated. 
>
>
>
>