Share via

3.3.1 Abstract Data Model

  • Article

This section describes a model of possible data organization that a server-side implementation maintains to participate in this protocol. The described organization is provided to facilitate the explanation of how the protocol behaves. This specification does not mandate that an implementation adhere to this model as long as the external behavior of the implementation is consistent with what is described in this specification.

The server maintains the following datum:

innerEAPAuthenticationMethods: An array of unsigned integers whose values correspond to the EAP authentication method types ([IANA-EAP]) supported as inner EAP methods by the PEAP server implementation.

currentState: The currentState datum is initialized when the server starts the PEAP authentication and remains valid until the authentication is done. At any point in time, the currentState datum can have the following integer values, each of which represents a possible state of the server machine.

  • PEAP_PHASE1_INPROGRESS

  • WAIT_FOR_SOH_RESPONSE

  • WAIT_FOR_CAPABILITIES_RESPONSE

  • INNER_IDENTITY_REQ_SENT

  • PHASE2_EAP_INPROGRESS

  • SUCCESS_TLV_SENT

  • FAILURE_TLV_SENT

  • PEAP_SUCCESS

  • PEAP_FAILED

PEAP Server State Machine

Figure 5: PEAP Server State Machine