[Lake] EDHOC implementation status

["Sipos, Brian J." <[e-mail]>]

WG,

I am working on an embedding of EDHOC into a larger protocol, and very much
appreciate the design decisions which easily enable its embedding. Part of
my work is to validate the embedding with some examples and I would like to
base them off of the examples from RFC 9529 [1] for simplicity. In searching
for existing implementations I came across py-edhoc [2] and lakers [3] (with
its C and Python APIs). It appears that these are both based on earlier
draft revisions, behind the published EDHOC RFC, and seem to lack support
for some/many of the currently defined ciphersuites (specifically those for
less-constrained devices).

 

Is there any motivation for updating the Python-native implementation [2]
from others in the group (or elsewhere)?

I know I can always fork and edit myself but I'd rather only touch source
that is expected to have a longer lifetime than just my example generator
tooling.

 

Thanks for any info,

Brian S.

 

[1] https://www.rfc-editor.org/rfc/rfc9529.html

[2] https://github.com/openwsn-berkeley/py-edhoc

[3] https://github.com/openwsn-berkeley/lakers