[riot-notifications] [RIOT-OS/RIOT] RFC: Integration of (tiny)DTLS for RIOT O.S. (#7397)
notifications at github.com
Wed Sep 6 10:25:03 CEST 2017
> 1. asynchronous operations
After further reviewing this challenge, it's seems that the best route for the asynchronous communication relies on completing it inside of the `sock_udp`. Therefore, the `secure_sock` could be progressing in parallel to it.
As told before, I'm going to modify the API for `secure_sock` for considering asynchronous component.
> 2. generic read/write ```(sock_read((sock_t*)sock_udp)``` vs. ```sock_udp_read(sock_udp))```
This is in particular, I'm not sure if it can help us. Because of the following reasons:
I. Although `sock_udp_t` and `sock_ip_t` are exactly the [same structure](http://doc.riot-os.org/sock__types_8h_source.html), and [`sock_tcp_t`](doc.riot-os.org/group__net__sock__tcp.html#ga0144778bc074e291fcb0d43bd35c0179) seems to be only a proof of concept. The functions behind each type (such as `sock_udp_send` and `sock_udp_recv`) focus on checking the parsing and the components of the protocol (port address, ipv4/ipv6 address, tcp options, etc.) and eventually they call a generic `gnrc_sock_send` and `gnrc_sock_recv`. Therefore, I think that this suggested new raw functions will be more complex than they should be.
II. I find more intuitive to use `sock_udp` when we want to send a UDP message, and a `sock_ip` when we wish to send raw IPv6 messages (even if the payload is a raw UDP message). In a similar fashion, a `secure_sock` can be more intuitive for the user when he wants to establish a secure channel for its data.
> 3. scatter/gather operations
Probably this could help by improving some aspects of tinyDTLS. I don't have too much experience with it, but we could start discussions of its implementation in the next RIOT Summit :)
If it's OK for everyone, I'll update the original post for reflecting the changes to the API.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications