| Re: EAP-AKA Key derivation | <– Date –> <– Thread –> |
|
From: Bernard Aboba (bernard_aboba |
|
| Date: Mon, 9 Jan 2006 05:02:05 -0800 (PST) | |
It is very common for IETF specifications to reference cryptographic
functions defined outside of the IETF. Examples include AES and DES, both
of which are defined in NIST documents.
From: Jari Arkko <jari.arkko [at] piuha.net> To: Thomas Otto <t.otto [at] sharevolution.de> CC: eap [at] frascone.com Subject: Re: [eap] EAP-AKA Key derivation Date: Mon, 09 Jan 2006 10:03:22 +0200
Clarifying question:
Is the problem that the KDF specification is unclear, or that a NIST publication is needed to implement it?
Thomas Otto wrote:
Hi all,
EAP-AKA uses the DSS key derivation function (KDF) to derive export keying material.
Although the draft describes the KDF briefly (see below), I would not be able to ... say implement this function. Rather I would have to look in NIST publication what the SHS actually is ... :-(
So, does anyone know why this burden is in EAP-AKA?
_________________________________________________________________ To unsubscribe or modify your subscription options, please visit: http://lists.frascone.com/mailman/listinfo/eap
Arhives: http://lists.frascone.com/pipermail/eap
- Re: EAP-AKA Key derivation, (continued)
-
Re: EAP-AKA Key derivation Jari Arkko, January 9 2006
-
Re: EAP-AKA Key derivation Thomas Otto, January 9 2006
- Re: EAP-AKA Key derivation Bernard Aboba, January 9 2006
- Re: EAP-AKA Key derivation Thomas Otto, January 9 2006
-
Re: EAP-AKA Key derivation Thomas Otto, January 9 2006
- Re: EAP-AKA Key derivation Bernard Aboba, January 9 2006
- Re: EAP-AKA Key derivation Thomas Otto, January 9 2006
-
Re: EAP-AKA Key derivation Jari Arkko, January 9 2006
- Re: EAP-AKA Key derivation Thomas Otto, January 10 2006
Results generated by Tiger Technologies using MHonArc.