| Proposed Resolution to Issue 243: State Synchronization | <– Date –> <– Thread –> |
|
From: Bernard Aboba (aboba |
|
| Date: Fri, 9 Jul 2004 00:33:31 -0400 (EDT) | |
The proposed resolution is to change clause [4] of Section 2.2 to the
following:
[4] Synchronization of state. The EAP method state of the EAP peer and
server must be synchronized when the EAP method completes
successfully. This includes the internal state of the
authentication protocol but not the state external to the EAP
method, such as the negotiation occuring prior to initiation of
the EAP method. The exact state attributes that are shared may
vary from method to method but typically include the method version
number, what credentials were presented and accepted by both
parties, what cryptographic keys are shared and what EAP method
specific attributes were negotiated, such as ciphersuites and
limitations of usage on all protocol state. Both parties must be
able to distinguish this instance of the protocol from all other
instances of the protocol and they must share the same view of
which state attributes are public and which are private to the two
parties alone.
-
Proposed Resolution to Issue 243: State Synchronization Bernard Aboba, July 8 2004
- Re: Proposed Resolution to Issue 243: State Synchronization Florent Bersani, July 14 2004
-
RE: Proposed Resolution to Issue 243: State Synchronization Walker, Jesse, July 14 2004
- Re: Proposed Resolution to Issue 243: State Synchronization Florent Bersani, July 14 2004
- RE: Proposed Resolution to Issue 243: State Synchronization Walker, Jesse, July 14 2004
Results generated by Tiger Technologies using MHonArc.