| RE: Issue 204: Peer-to-peer operation | <– Date –> <– Thread –> |
|
From: Bernard Aboba (aboba |
|
| Date: Tue, 25 Nov 2003 08:05:18 -0600 (CST) | |
> Hmm, I'm not sure if I understand this... Is this issue about the > case when there are two independent EAP conversations (i.e. both > parties act as peers and authenticators), or ordinary mutual > authentication with only a single EAP conversation? I assume it is the latter. > The latter case should be rather simple, since setting the > controlled port to "authorized" when eapSuccess is set > seems to be exactly the right thing to do (and the lower > layer doesn't really need to know anything else). The claim in IEEE 802.1XD7.1's comment resolution is that the lower layer does indeed to know more. > In the former case, both parties have both peer and > authenticator state machines, and this is something that .1X > doesn't handle well (for instance, we have two separate > variables both named eapSuccess :-). Is this what you mean? It wasn't what I meant, but it might be what the comment is referring to :)
- RE: Issue 204: Peer-to-peer operation, (continued)
- RE: Issue 204: Peer-to-peer operation Bernard Aboba, November 26 2003
- RE: Issue 204: Peer-to-peer operation Joseph Salowey, November 26 2003
- RE: Issue 204: Peer-to-peer operation Bernard Aboba, November 26 2003
- RE: Issue 204: Peer-to-peer operation Bernard Aboba, November 25 2003
-
RE: Issue 204: Peer-to-peer operation Nick Petroni, December 3 2003
- RE: Issue 204: Peer-to-peer operation Bernard Aboba, December 3 2003
- Re: Issue 204: Peer-to-peer operation Jim Burns, December 3 2003
Results generated by Tiger Technologies using MHonArc.