From the point of view of code reuse, DTLS seems to make sense but I think we would really need to find a way of getting rid of 10+ packets to get things going, particularly when we can leverage PSKs. Looking at draft-ietf-dice-profile, it seems that session resumption could help us for that. I am thinking whether it would make sense for the JN to initiate the handshake using session resumption without server-side state (RFC 5077) and get the handshake done in 1.5 exchanges when PSK is in place. Or in case we decide that JN should be a DTLS server and make itself visible by some other method, JCE would be initiating the abbreviated handshake with the ticket that JN is able to access locally as it is in possession of the PSK. Would that be any reasonable?
Regards, MaliĊĦa > On 27 Oct 2015, at 20:19, Michael Richardson <[email protected]> wrote: > > What I'm interested here is the ability to leverage the 802.15.9 KMP *code* > to assist with the join process. While I love IKEv2 and HIPDEX, I'm not > convinced that there is code+ram space for those KMPs as well as the DTLS > that 6top/CoAP is going to require. I'd like it to all converge :-) _______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
