Compartir a través de

3.3.3 Initialization

  • Artículo

PEAP MUST be initialized on the EAP server when it is invoked by EAP as an authentication method. This occurs when an EAP-enabled protocol (such as RADIUS [RFC2865]) invokes EAP, the EAP server proposes PEAP, and the peer agrees to perform a PEAP negotiation.

A PEAP implementation MUST have an implementation-specific way of specifying what EAP methods are supported for the inner EAP instance. The EapInitialize method SHOULD be called to initialize the inner EAP instance with the specified inner EAP methods as the parameter.

The PEAP server obtains the maximum EAP packet size using the GetMaxSendPacketSize method, and assigns the size to the MaxSendPacketSize field. isFastReconnectAllowed datum MUST be initialized to FALSE.

InnerEapType MUST be initialized with the first integer of the innerEAPAuthenticationMethods array as specified in section 3.3.1.

BypassCapNegotiation and AssumePhase2Frag are protocol configurations<15>, which can be initialized in an implementation-specific manner.<16>

isCapabilitiesSupported MUST be initialized to TRUE, if the PEAP method implementation supports Capabilities Method Negotiation (section 2.2.8.3) and BypassCapNegotiation is set to FALSE. Otherwise, it is initialized to FALSE.

isFragmentationAllowed MUST be initialized to TRUE, if the PEAP method implementation supports phase 2 fragmentation and BypassCapNegotiation and AssumePhase2Frag are set to TRUE. Otherwise initialize isFragmentationAllowed to FALSE.