Hi Malisa: Thanks for the discussion and sorry for my late answer. See inline.
> El 3 nov 2015, a las 15:19, Malisa Vucinic <[email protected]> escribió: > > >> On 02 Nov 2015, at 12:30, Rafa Marin Lopez <[email protected]> wrote: > >> Yes, I think we are aligned. That is why we proposed EAP over CoAP (you >> reuse CoAP). And as Robert mentioned certain EAP methods can re-use source >> code. >> >> On the other hand, I have some doubts this source code will be used only >> once. > > Could you elaborate? What I meant is that for security reasons we will have to refresh the keying material. For example, EAP Key Management Framework recommends 8 hours as default lifetime (this might be modified in this type of networks). Thus, I do not think the source code will be used only once. > > >> EAP-AKA has two messages + EAP Success : EAP-Req/AKA (4 bytes header EAP + 1 >> the type) + EAP-Resp/AKA (4 bytes header EAP +1 the type) + EAP success(4 >> bytes) = 14 overhead with respect to running “AKA" without EAP. > > Ok thanks. So, am I right if I say that this will trigger 3 additional frames > at L2 with additional CoAP / UDP-6LoWPAN-IPv6 / 15.4 overhead? Not sure about what you mean with 3 “additional" frames at L2. Additional to what else?. You also mention additional CoAP/UDP...? Are you assuming CoAP-EAP? Best Regards. > ------------------------------------------------------- Rafael Marin Lopez, PhD Dept. Information and Communications Engineering (DIIC) Faculty of Computer Science-University of Murcia 30100 Murcia - Spain Telf: +34868888501 Fax: +34868884151 e-mail: [email protected] ------------------------------------------------------- _______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
