Subject: [eap] Issue 139: Response to duplicate requests

From: [email-masked] (Bernard Aboba)
Date: Sun, 18 May 2003 08:39:24 -0700 (PDT)

Submitter name: Nick Petroni
Submitter email address: [email-masked]
Date first submitted: May 14, 2003
Reference:
Document: EAP-03
Comment type: T
Priority: S
Section: 4.1
Rationale/Explanation of issue:

"If a peer receives a duplicate Request before it has
sent a Response, but after it has determined the initial Request
to be valid (i.e. it is waiting for user input), it MUST silently
discard the duplicate Request. "

Seems like the peer should
be able to send as many responses as it gets requests for the same
id.  It may not send a response for prior id after it has sent a
response to current id.  This is how the state machine works, and
hopefully the wording in 2284bis will be modified to match.