[riot-notifications] [RIOT-OS/RIOT] sock/dtls: add function to retrieve epoch of session (#15881)

chrysn notifications at github.com
Fri Jan 29 16:06:37 CET 2021


>From a first look, I'd need a better understanding of what "current" means w/rt received and sent messages. For example, if I receive a message and then call `sock_dtls_session_get_epoch`, can I be sure that the message I "just" received was from that epoch, or did maybe the epoch just change after that?

Sockets now have an auxiliary data API (since #14703: sock_udp_recv_aux & co). Would using those solve the abovementioned issue? There could be a field for epoch in the sock_dtls_aux_rx_t. Possibly also in sock_dtls_aux_tx_t, either to be populated by the library and read after sending, or to be set / forcing the library to send it in that epoch or not at all.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/15881#issuecomment-769859516
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20210129/383ed6de/attachment.htm>


More information about the notifications mailing list