On Oct 8, 2024, at 2:39 AM, RAFAEL MARIN LOPEZ <r...@um.es> wrote: > Thank you so much for your review. Regarding about message correlation,
Message correlation is not an issue. You shouldn't spend any time worrying abut it. > In any case, let’s see what others opinions (because it is true that it might > be difficult to extract this conclusion from EAP RFC text based only with the > definition of the Identifier field). The lower layer is responsible for separating EAP sessions. EAP doesn't have to worry about it. Originally, EAP ran over PPP. The use-case here was a modem running PPP, talking to a server. i.e. there was a wire between the two systems, and they ran only one thing over it: PPP. And when PPP authenticated, it ran only one authentication at a time: EAP. Similar things happen today, even when modems aren't used. So for your use-use, it is the responsibility of CoAP to distinguish the different EAP authentications. To follow the processes used elsewhere, this should done by having some kind of session between CoAP client and CoAP server. Then, EAP is run over that session. There should only be one EAP authentication sent over a session at a time. So there's no problem distinguishing EAP authentications. Each CoAP session can be distinguished at the CoAP layer. So there's no problem distinguishing EAP authentications there, either. If we look at draft-ietf-ace-wg-coap-eap-11, Section 3.2, and Figure 3, we see that this is happening. The CoAP client and server have a shared connection (TCP / TLS). The EAP authentication is constrained to this connection. If the CoAP server turns EAP into RADIUS and sends Access-Request packets, it has to correlate the RADIUS packets to the CoAP connection. That can easily be done, and is really just an implementation detail. Perhaps CoAP has issues with one CoAP client doing multiple authentications at the same time. But that's a CoAP issue, and has nothing to do with EAP. Alan DeKok. _______________________________________________ Emu mailing list -- emu@ietf.org To unsubscribe send an email to emu-le...@ietf.org
