RE: Last Call: draft-arkko-eap-aka-kdf (ImprovedExtensible AuthenticationProtocol Method for 3rd Generation Authentication and KeyAgreement (EAP-AKA')) to Informational RFC

2008-10-16 Thread Joseph Salowey (jsalowey)
Hi Jari, -Original Message- From: Jari Arkko [mailto:[EMAIL PROTECTED] Sent: Thursday, October 16, 2008 2:24 AM To: Joseph Salowey (jsalowey) Cc: Pasi Eronen; ietf@ietf.org; [EMAIL PROTECTED] Subject: Re: Last Call: draft-arkko-eap-aka-kdf (ImprovedExtensible

Re: Last Call: draft-arkko-eap-aka-kdf (ImprovedExtensible AuthenticationProtocol Method for 3rd Generation Authentication and KeyAgreement (EAP-AKA')) to Informational RFC

2008-10-16 Thread Jari Arkko
Joe, First, after some discussion with some of the users of this spec from 3GPP, we have decided that AT_KDF=1 or the AKA fallback mode should be removed. AT_KDF_INPUT field values would indeed be dependent on which KDF is used. I will make the second change you suggested to fix this. On

RE: Last Call: draft-arkko-eap-aka-kdf (ImprovedExtensible AuthenticationProtocol Method for 3rd Generation Authentication and KeyAgreement (EAP-AKA')) to Informational RFC

2008-10-15 Thread Joseph Salowey (jsalowey)
Hi Jari, This discussion has prompted me to look at the spec again. Is there a need to fall back to the AKA derivation? It seems that the AAA providing AKA or AKA' support would know what is supported by the infrastructure. Having the fallback to AKA is confusing. If you chose the alternate