-
Notifications
You must be signed in to change notification settings - Fork 424
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RIOT support - why GNRC specific #581
Comments
@maribu Thank your for bringing this up! The reason for using GNRC was that I had to pick something instead of the BSD socket wrapper as that turned out to cause some issues that would have required changes to the socket wrapper itself (i.e., would have required adding more socket-layer options). I do not mind moving to the SOCK API if you think this is the proper way forward. Regarding the libcoap package in RIOT: I have started updating this in my own branch but did face some issues—possibly related to my use of GNRC. Therefore, I did not yet finish that work. I take it from your request that the work on the DTLS SOCK API has stabilized and is ready to use (this would be prerequisite for me as not having DTLS for CoAP is a dead end IMO). |
@pokgak and @miri64 should be able to give a more definite answer to that than I am. As far as I can see, only TinyDTLS currently implements that API - I personally would wait for a second implementation of that API before counting on it to be stable. (By "stable" I mean "not subject to API changes" here.) That said, I personally don't think that interfacing with the GNRC network stack below the SOCK API is more stable than DTLS SOCK API is. (Again, "stable" as in "not subject to API changes".) But @miri64 should be able to give a definite answer to that. |
The GNRC NETAPI basically did not change since my master thesis, while the SOCK API changed significantly (it did not even exist and there was its predecessor |
My experimental update of the libcoap package uses tinydtls via its internal bindings (configured via a pseudo module in RIOT). Would this be a useful contribution to RIOT? (Note that this is not only outdated since I have worked on that code but also has some flaws I would have to investigate.) |
I'd say yes :-) |
There is now support for the latest RIOT code, including a client and server example using TinyDTLS in (waiting to be merged) #1086. It makes use of |
I saw that https://github.com/obgm/libcoap/blob/develop/src/coap_io_riot.c support for RIOT was added. This raised two questions:
The text was updated successfully, but these errors were encountered: