eap Mailing List: draft-ietf-eap-statemachine-05.txt and Identifier in EAP-Success

[Jouni Malinen (jkmaline]

The Peer State Machine in draft-ietf-eap-statemachine-05.txt requires
that reqId == lastId when processing EAP-Success packet. However, I do
not see such requirement in RFC 3748. In addition, most (if not all)
existing RADIUS servers seem to implement EAP in a way that Identifier
in EAP-Success is actually incremented by one from the last EAP-Request.

draft-ietf-eap-statemachine-05.txt state machines for EAP authenticator
are indeed not incrementing Identifier for EAP-Success, but again, this
is not specified in RFC 3748. The only requirement for Identifier in
RFC 3748 seems to be that each EAP-Request is sent with different
Identifier than the previous EAP-Request. As far as I can tell, this
leaves it open to the implementation to decide which Identifier is used
in EAP-Success.

Should the (reqId == lastId) requirement be removed from the peer state
machine?

-- 
Jouni Malinen                                            PGP id EFC895FA