| Re: Key derivation and the principle of equivalence | <– Date –> <– Thread –> |
|
From: Jari Arkko (jari.arkko |
|
| Date: Wed, 18 May 2005 09:59:03 -0400 (EDT) | |
Bernard Aboba wrote:
(Lets not delay Diameter EAP unless we really need to.)
--Jari
If I understand your comment correctly, even if the key Management
framework document defines EAP session-ID (or some other attribute
that servers as key versioning), if Diameter EAP needs to carry that
attribute, I think the attribute needs to be added in Diameter EAP
document and recycling would be needed anyways.
Yes, I think that's true.
I believe key phrase above (no pun intended) is "if ... needs to carry". Current usage of EAP does not really use key names at this level for anything. My suspicision is that we will only need the names when we go to the more interesting scenarios, like fast handoffs, or application usage of EAP keys. But these are likely to require new AAA support anyway.
(Lets not delay Diameter EAP unless we really need to.)
--Jari
- Re: Key derivation and the principle of equivalence, (continued)
- Re: Key derivation and the principle of equivalence Yoshihiro Ohba, May 17 2005
- Re: Key derivation and the principle of equivalence Bernard Aboba, May 17 2005
- Re: Key derivation and the principle of equivalence Yoshihiro Ohba, May 17 2005
- Re: Key derivation and the principle of equivalence Bernard Aboba, May 18 2005
- Re: Key derivation and the principle of equivalence Jari Arkko, May 18 2005
- Re: Key derivation and the principle of equivalence Bernard Aboba, May 18 2005
- Re: Key derivation and the principle of equivalence Yoshihiro Ohba, May 18 2005
- Re: Key derivation and the principle of equivalence Jari Arkko, May 12 2005
Results generated by Tiger Technologies using MHonArc.