| RE: Basic facts about EAP | <– Date –> <– Thread –> |
|
From: Bernard Aboba (aboba |
|
| Date: Thu, 28 Apr 2005 13:29:52 -0400 (EDT) | |
> And there's no single correct system, either. For instance, it's > perfectly OK to have a system where both EAP server and RADIUS server > are considered to be parts of a single logical entity. But nothing > in the components (EAP or RADIUS) implies or forces this: it is > this unnamed system that is making this definition. But since we > don't have good names for these systems, it's easy to get a > disagreement when two people are, in fact, talking of two different > systems that happen to use EAP (or are arguing that there is or > should be a single correct system, and no other systems are allowed > to use EAP). Do you have a suggestion for how we might clarify the usage?
- Approach to channel bindings (Was; Re: [eap] Basic facts about EAP), (continued)
- Approach to channel bindings (Was; Re: [eap] Basic facts about EAP) Jari Arkko, May 3 2005
- Re: Approach to channel bindings (Was; Re: [eap] Basic facts about EAP) Yoshihiro Ohba, May 3 2005
- RE: Basic facts about EAP Alper Yegin, May 2 2005
- RE: Basic facts about EAP Bernard Aboba, April 28 2005
- Re: Basic facts about EAP Jari Arkko, April 29 2005
- Re: Basic facts about EAP Artur Hecker, April 29 2005
- Re: Basic facts about EAP John Vollbrecht, April 29 2005
- Re: Basic facts about EAP Jari Arkko, May 2 2005
Results generated by Tiger Technologies using MHonArc.