On Fri, Mar 28, 2008 at 5:38 PM, Dragos Vingarzan <Dragos.Vingarzan at fokus.fraunhofer.de> wrote: > Hi Benny, > > sorry for not replying sooner, but I have a question on the subject... > > Is there a specific reason why you don't want to enable AKA by default? > I mean, you can always tell what you need to do from the 401 - whether > it is MD5 or AKAv1-MD5 or AKAv2-MD5. So it is feasible to do > auto-detection and use the right method. Or am I missing something? Hi Dragos, True about auto-detection. Presently AKA is disabled by a compilation switch because it's a fairly new feature and some targets (e.g. Symbian) may not be updated yet to support it. Other reasons to have compilation switches are to keep the footprint low for applications that don't want to use it and to disable experimental features, although these are not the case with AKA since it will not increase footprint when application doesn't use it and it seems to be working okay. So once all targets are updated AKA will enabled by default. Cheers Benny
