[riot-notifications] [RIOT-OS/RIOT] pkg/tinydtls: handling of close_notify (#16422)

Achim Kraus notifications at github.com
Tue Jul 6 09:11:35 CEST 2021

Let me ask about the motivation to "close" the session:

When/why is that done?
- at the end of a communication phase, in order to pause/end communication for longer?
- in order to execute a new handshake to overcome some NAT issues (and bugs in DTLS server side implementation according [RFC6347 - 4.2.8.  Establishing New Associations with Existing Parameters](https://datatracker.ietf.org/doc/html/rfc6347#section-4.2.8)) ?

The reason for this question is simple:
- yes the close should work proper and not cause additional trouble
- but, much more important: the server sides must implement 4.2.8! 

The close may get lost, and so doesn't really help. 4.2.8 is in my opinion the only right way to do it.
For tinydtls I therefore prepared [PR89](https://github.com/eclipse/tinydtls/pull/89) to fix the 4.2.8 behavior.

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...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20210706/f049bfec/attachment.htm>

More information about the notifications mailing list