| Re: Proposed Resolution of Issue 253: AAA-Key Name is Misleading | <– Date –> <– Thread –> |
|
From: Bernard Aboba (aboba |
|
| Date: Wed, 30 Jun 2004 18:51:29 -0400 (EDT) | |
On Wed, 30 Jun 2004, Jari Arkko wrote: > > Since I agree with Joe's comments, it pains me that the term "AAA-Key" is > > used in RFC 3748, and therefore I don't feel we can change the term in the > > EAP Key Management framework document. > > > > However, we probably should expose language clarifying that the AAA-Key > > exists even where there is no AAA server (how is that for obfuscation?). > > I think that is all we can do. Too bad, but can't be helped. I looked at the definition of "AAA-Key". It says: "However, despite the name, the AAA-Key is computed regardless of whether a backend authentication server is present." So I'm not sure how much more we can do.
-
Proposed Resolution of Issue 253: AAA-Key Name is Misleading Bernard Aboba, June 30 2004
-
Re: Proposed Resolution of Issue 253: AAA-Key Name is Misleading Jari Arkko, June 30 2004
- Re: Proposed Resolution of Issue 253: AAA-Key Name is Misleading Bernard Aboba, June 30 2004
-
Re: Proposed Resolution of Issue 253: AAA-Key Name is Misleading Jari Arkko, June 30 2004
Results generated by Tiger Technologies using MHonArc.